# Print output for @column tags ?>
Developers

- Design
- Develop
- Distribute

Developer Console

## Most visited

## Recently visited

## Results for

Summary: Constants | Ctors | Inherited Methods

# Build.VERSION_CODES

`public static class Build.VERSION_CODES`
`extends Object` ``

java.lang.Object
↳ | android.os.Build.VERSION_CODES

Enumeration of the currently known SDK version codes. These are the values that can be found in `VERSION#SDK`. Version numbers increment monotonically with each official platform release.

## Summary

### Constants
`int` | `BASE` October 2008: The original, first, version of Android.
`int` | `BASE_1_1` February 2009: First Android update, officially called 1.1.
`int` | `CUPCAKE` May 2009: Android 1.5.
`int` | `CUR_DEVELOPMENT` Magic version number for a current development build, which has not yet turned into an official release.
`int` | `DONUT` September 2009: Android 1.6.
`int` | `ECLAIR` November 2009: Android 2.0 Applications targeting this or a later release will get these new changes in behavior: The `Service.onStartCommand` function will return the new `Service.START_STICKY` behavior instead of the old compatibility `Service.START_STICKY_COMPATIBILITY`.
`int` | `ECLAIR_0_1` December 2009: Android 2.0.1
`int` | `ECLAIR_MR1` January 2010: Android 2.1
`int` | `FROYO` June 2010: Android 2.2
`int` | `GINGERBREAD` November 2010: Android 2.3 Applications targeting this or a later release will get these new changes in behavior: The application's notification icons will be shown on the new dark status bar background, so must be visible in this situation.
`int` | `GINGERBREAD_MR1` February 2011: Android 2.3.3.
`int` | `HONEYCOMB` February 2011: Android 3.0.
`int` | `HONEYCOMB_MR1` May 2011: Android 3.1.
`int` | `HONEYCOMB_MR2` June 2011: Android 3.2.
`int` | `ICE_CREAM_SANDWICH` October 2011: Android 4.0.
`int` | `ICE_CREAM_SANDWICH_MR1` December 2011: Android 4.0.3.
`int` | `JELLY_BEAN` June 2012: Android 4.1.
`int` | `JELLY_BEAN_MR1` November 2012: Android 4.2, Moar jelly beans! Applications targeting this or a later release will get these new changes in behavior: Content Providers: The default value of `android:exported` is now `false`.
`int` | `JELLY_BEAN_MR2` July 2013: Android 4.3, the revenge of the beans.
`int` | `KITKAT` October 2013: Android 4.4, KitKat, another tasty treat.
`int` | `KITKAT_WATCH` June 2014: Android 4.4W.
`int` | `LOLLIPOP` November 2014: Lollipop.
`int` | `LOLLIPOP_MR1` March 2015: Lollipop with an extra sugar coating on the outside! For more information about this release, see the Android 5.1 APIs.
`int` | `M` M is for Marshmallow! Applications targeting this or a later release will get these new changes in behavior.
`int` | `N` N is for Nougat.
`int` | `N_MR1` N MR1: Nougat++.
`int` | `O` O.
`int` | `O_MR1` O MR1.
`int` | `P` P.
`int` | `Q` Q.
`int` | `R` R.

### Public constructors
`VERSION_CODES()`

### Inherited methods
From class `java.lang.Object`
`Object` | `clone()` Creates and returns a copy of this object.
`boolean` | `equals(Object obj)` Indicates whether some other object is "equal to" this one.
`void` | `finalize()` Called by the garbage collector on an object when garbage collection determines that there are no more references to the object.
`final Class<?>` | `getClass()` Returns the runtime class of this `Object`.
`int` | `hashCode()` Returns a hash code value for the object.
`final void` | `notify()` Wakes up a single thread that is waiting on this object's monitor.
`final void` | `notifyAll()` Wakes up all threads that are waiting on this object's monitor.
`String` | `toString()` Returns a string representation of the object.
`final void` | `wait(long timeout, int nanos)` Causes the current thread to wait until another thread invokes the `notify()` method or the `notifyAll()` method for this object, or some other thread interrupts the current thread, or a certain amount of real time has elapsed.
`final void` | `wait(long timeout)` Causes the current thread to wait until either another thread invokes the `notify()` method or the `notifyAll()` method for this object, or a specified amount of time has elapsed.
`final void` | `wait()` Causes the current thread to wait until another thread invokes the `notify()` method or the `notifyAll()` method for this object.

## Constants

### BASE

    public static final int BASE

October 2008: The original, first, version of Android. Yay!

Constant Value: 1 (0x00000001)

### BASE_1_1

    public static final int BASE_1_1

February 2009: First Android update, officially called 1.1.

Constant Value: 2 (0x00000002)

### CUPCAKE

    public static final int CUPCAKE

May 2009: Android 1.5.

Constant Value: 3 (0x00000003)

### CUR_DEVELOPMENT

    public static final int CUR_DEVELOPMENT

Magic version number for a current development build, which has not yet turned into an official release.

Constant Value: 10000 (0x00002710)

### DONUT

    public static final int DONUT

September 2009: Android 1.6.

Applications targeting this or a later release will get these new changes in behavior:

- They must explicitly request the `Manifest.permission.WRITE_EXTERNAL_STORAGE` permission to be able to modify the contents of the SD card. (Apps targeting earlier versions will always request the permission.)
- They must explicitly request the `Manifest.permission.READ_PHONE_STATE` permission to be able to be able to retrieve phone state info. (Apps targeting earlier versions will always request the permission.)
- They are assumed to support different screen densities and sizes. (Apps targeting earlier versions are assumed to only support medium density normal size screens unless otherwise indicated). They can still explicitly specify screen support either way with the supports-screens manifest tag.
- `TabHost` will use the new dark tab background design.

Constant Value: 4 (0x00000004)

### ECLAIR

    public static final int ECLAIR

November 2009: Android 2.0

Applications targeting this or a later release will get these new changes in behavior:

- The `Service.onStartCommand` function will return the new `Service.START_STICKY` behavior instead of the old compatibility `Service.START_STICKY_COMPATIBILITY`.
- The `Activity` class will now execute back key presses on the key up instead of key down, to be able to detect canceled presses from virtual keys.
- The `TabWidget` class will use a new color scheme for tabs. In the new scheme, the foreground tab has a medium gray background the background tabs have a dark gray background.

Constant Value: 5 (0x00000005)

### ECLAIR_0_1

    public static final int ECLAIR_0_1

December 2009: Android 2.0.1

Constant Value: 6 (0x00000006)

### ECLAIR_MR1

    public static final int ECLAIR_MR1

January 2010: Android 2.1

Constant Value: 7 (0x00000007)

### FROYO

    public static final int FROYO

June 2010: Android 2.2

Constant Value: 8 (0x00000008)

### GINGERBREAD

    public static final int GINGERBREAD

November 2010: Android 2.3

Applications targeting this or a later release will get these new changes in behavior:

- The application's notification icons will be shown on the new dark status bar background, so must be visible in this situation.

Constant Value: 9 (0x00000009)

### GINGERBREAD_MR1

    public static final int GINGERBREAD_MR1

February 2011: Android 2.3.3.

Constant Value: 10 (0x0000000a)

### HONEYCOMB

    public static final int HONEYCOMB

February 2011: Android 3.0.

Applications targeting this or a later release will get these new changes in behavior:

- The default theme for applications is now dark holographic: `R.style.Theme_Holo`.
- On large screen devices that do not have a physical menu button, the soft (compatibility) menu is disabled.
- The activity lifecycle has changed slightly as per `Activity`.
- An application will crash if it does not call through to the super implementation of its `Activity.onPause()` method.
- When an application requires a permission to access one of its components (activity, receiver, service, provider), this permission is no longer enforced when the application wants to access its own component. This means it can require a permission on a component that it does not itself hold and still access that component.
- `Context.getSharedPreferences()` will not automatically reload the preferences if they have changed on storage, unless `Context.MODE_MULTI_PROCESS` is used.
- `ViewGroup.setMotionEventSplittingEnabled(boolean)` will default to true.
- `WindowManager.LayoutParams.FLAG_SPLIT_TOUCH` is enabled by default on windows.
- `PopupWindow.isSplitTouchEnabled()` will return true by default.
- `GridView` and `ListView` will use `View.setActivated` for selected items if they do not implement `Checkable`.
- `Scroller` will be constructed with "flywheel" behavior enabled by default.

Constant Value: 11 (0x0000000b)

### HONEYCOMB_MR1

    public static final int HONEYCOMB_MR1

May 2011: Android 3.1.

Constant Value: 12 (0x0000000c)

### HONEYCOMB_MR2

    public static final int HONEYCOMB_MR2

June 2011: Android 3.2.

Update to Honeycomb MR1 to support 7 inch tablets, improve screen compatibility mode, etc.

As of this version, applications that don't say whether they support XLARGE screens will be assumed to do so only if they target `HONEYCOMB` or later; it had been `GINGERBREAD` or later. Applications that don't support a screen size at least as large as the current screen will provide the user with a UI to switch them in to screen size compatibility mode.

This version introduces new screen size resource qualifiers based on the screen size in dp: see `Configuration.screenWidthDp`, `Configuration.screenHeightDp`, and `Configuration.smallestScreenWidthDp`. Supplying these in <supports-screens> as per `ApplicationInfo.requiresSmallestWidthDp`, `ApplicationInfo.compatibleWidthLimitDp`, and `ApplicationInfo.largestWidthLimitDp` is preferred over the older screen size buckets and for older devices the appropriate buckets will be inferred from them.

Applications targeting this or a later release will get these new changes in behavior:

- New `PackageManager.FEATURE_SCREEN_PORTRAIT` and `PackageManager.FEATURE_SCREEN_LANDSCAPE` features were introduced in this release. Applications that target previous platform versions are assumed to require both portrait and landscape support in the device; when targeting Honeycomb MR1 or greater the application is responsible for specifying any specific orientation it requires.

- `AsyncTask` will use the serial executor by default when calling `AsyncTask.execute(Params...)`.

- `ActivityInfo.configChanges` will have the `ActivityInfo.CONFIG_SCREEN_SIZE` and `ActivityInfo.CONFIG_SMALLEST_SCREEN_SIZE` bits set; these need to be cleared for older applications because some developers have done absolute comparisons against this value instead of correctly masking the bits they are interested in.

Constant Value: 13 (0x0000000d)

### ICE_CREAM_SANDWICH

    public static final int ICE_CREAM_SANDWICH

October 2011: Android 4.0.

Applications targeting this or a later release will get these new changes in behavior:

- For devices without a dedicated menu key, the software compatibility menu key will not be shown even on phones. By targeting Ice Cream Sandwich or later, your UI must always have its own menu UI affordance if needed, on both tablets and phones. The ActionBar will take care of this for you.
- 2d drawing hardware acceleration is now turned on by default. You can use `android:hardwareAccelerated` to turn it off if needed, although this is strongly discouraged since it will result in poor performance on larger screen devices.
- The default theme for applications is now the "device default" theme: `R.style.Theme_DeviceDefault`. This may be the holo dark theme or a different dark theme defined by the specific device. The `R.style.Theme_Holo` family must not be modified for a device to be considered compatible. Applications that explicitly request a theme from the Holo family will be guaranteed that these themes will not change character within the same platform version. Applications that wish to blend in with the device should use a theme from the `R.style.Theme_DeviceDefault` family.
- Managed cursors can now throw an exception if you directly close the cursor yourself without stopping the management of it; previously failures would be silently ignored.
- The fadingEdge attribute on views will be ignored (fading edges is no longer a standard part of the UI). A new requiresFadingEdge attribute allows applications to still force fading edges on for special cases.
- `Context.bindService()` will not automatically add in `Context.BIND_WAIVE_PRIORITY`.
- App Widgets will have standard padding automatically added around them, rather than relying on the padding being baked into the widget itself.
- An exception will be thrown if you try to change the type of a window after it has been added to the window manager. Previously this would result in random incorrect behavior.
- `AnimationSet` will parse out the duration, fillBefore, fillAfter, repeatMode, and startOffset XML attributes that are defined.
- `ActionBar.setHomeButtonEnabled()` is false by default.

Constant Value: 14 (0x0000000e)

### ICE_CREAM_SANDWICH_MR1

    public static final int ICE_CREAM_SANDWICH_MR1

December 2011: Android 4.0.3.

Constant Value: 15 (0x0000000f)

### JELLY_BEAN

    public static final int JELLY_BEAN

June 2012: Android 4.1.

Applications targeting this or a later release will get these new changes in behavior:

- You must explicitly request the `Manifest.permission.READ_CALL_LOG` and/or `Manifest.permission.WRITE_CALL_LOG` permissions; access to the call log is no longer implicitly provided through `Manifest.permission.READ_CONTACTS` and `Manifest.permission.WRITE_CONTACTS`.
- `RemoteViews` will throw an exception if setting an onClick handler for views being generated by a `RemoteViewsService` for a collection container; previously this just resulted in a warning log message.
- New `ActionBar` policy for embedded tabs: embedded tabs are now always stacked in the action bar when in portrait mode, regardless of the size of the screen.
- `WebSettings.setAllowFileAccessFromFileURLs` and `WebSettings.setAllowUniversalAccessFromFileURLs` default to false.
- Calls to `PackageManager.setComponentEnabledSetting` will now throw an IllegalArgumentException if the given component class name does not exist in the application's manifest.
- `NfcAdapter.setNdefPushMessage`, `NfcAdapter.setNdefPushMessageCallback` and `NfcAdapter.setOnNdefPushCompleteCallback` will throw IllegalStateException if called after the Activity has been destroyed.
- Accessibility services must require the new `Manifest.permission.BIND_ACCESSIBILITY_SERVICE` permission or they will not be available for use.
- `AccessibilityServiceInfo.FLAG_INCLUDE_NOT_IMPORTANT_VIEWS` must be set for unimportant views to be included in queries.

Constant Value: 16 (0x00000010)

### JELLY_BEAN_MR1

    public static final int JELLY_BEAN_MR1

November 2012: Android 4.2, Moar jelly beans!

Applications targeting this or a later release will get these new changes in behavior:

- Content Providers: The default value of `android:exported` is now `false`. See the android:exported section in the provider documentation for more details.
- `View.getLayoutDirection()` can return different values than `View.LAYOUT_DIRECTION_LTR` based on the locale etc.
- `WebView.addJavascriptInterface` requires explicit annotations on methods for them to be accessible from Javascript.

Constant Value: 17 (0x00000011)

### JELLY_BEAN_MR2

    public static final int JELLY_BEAN_MR2

July 2013: Android 4.3, the revenge of the beans.

Constant Value: 18 (0x00000012)

### KITKAT

    public static final int KITKAT

October 2013: Android 4.4, KitKat, another tasty treat.

Applications targeting this or a later release will get these new changes in behavior. For more information about this release, see the Android KitKat overview.

- The default result of `PreferenceActivity.isValueFragment` becomes false instead of true.
- In `WebView`, apps targeting earlier versions will have JS URLs evaluated directly and any result of the evaluation will not replace the current page content. Apps targetting KITKAT or later that load a JS URL will have the result of that URL replace the content of the current page
- `AlarmManager.set` becomes interpreted as an inexact value, to give the system more flexibility in scheduling alarms.
- `Context.getSharedPreferences` no longer allows a null name.
- `RelativeLayout` changes to compute wrapped content margins correctly.
- `ActionBar`'s window content overlay is allowed to be drawn.
- The `Manifest.permission.READ_EXTERNAL_STORAGE` permission is now always enforced.
- Access to package-specific external storage directories belonging to the calling app no longer requires the `Manifest.permission.READ_EXTERNAL_STORAGE` or `Manifest.permission.WRITE_EXTERNAL_STORAGE` permissions.

Constant Value: 19 (0x00000013)

### KITKAT_WATCH

    public static final int KITKAT_WATCH

June 2014: Android 4.4W. KitKat for watches, snacks on the run.

Applications targeting this or a later release will get these new changes in behavior:

- `AlertDialog` might not have a default background if the theme does not specify one.

Constant Value: 20 (0x00000014)

### LOLLIPOP

    public static final int LOLLIPOP

November 2014: Lollipop. A flat one with beautiful shadows. But still tasty.

Applications targeting this or a later release will get these new changes in behavior. For more information about this release, see the Android Lollipop overview.

- `Context.bindService` now requires an explicit Intent, and will throw an exception if given an implicit Intent.
- `Notification.Builder` will not have the colors of their various notification elements adjusted to better match the new material design look.
- `Message` will validate that a message is not currently in use when it is recycled.
- Hardware accelerated drawing in windows will be enabled automatically in most places.
- `Spinner` throws an exception if attaching an adapter with more than one item type.
- If the app is a launcher, the launcher will be available to the user even when they are using corporate profiles (which requires that the app use `LauncherApps` to correctly populate its apps UI).
- Calling `Service.stopForeground` with removeNotification false will modify the still posted notification so that it is no longer forced to be ongoing.
- A `DreamService` must require the `Manifest.permission.BIND_DREAM_SERVICE` permission to be usable.

Constant Value: 21 (0x00000015)

### LOLLIPOP_MR1

    public static final int LOLLIPOP_MR1

March 2015: Lollipop with an extra sugar coating on the outside! For more information about this release, see the Android 5.1 APIs.

Constant Value: 22 (0x00000016)

### M

    public static final int M

M is for Marshmallow!

Applications targeting this or a later release will get these new changes in behavior. For more information about this release, see the Android 6.0 Marshmallow overview.

- Runtime permissions. Dangerous permissions are no longer granted at install time, but must be requested by the application at runtime through `Activity.requestPermissions(String[], int)`.
- Bluetooth and Wi-Fi scanning now requires holding the location permission.
- `AlarmManager.setTimeZone` will fail if the given timezone is non-Olson.
- Activity transitions will only return shared elements mapped in the returned view hierarchy back to the calling activity.
- `View` allows a number of behaviors that may break existing apps: Canvas throws an exception if restore() is called too many times, widgets may return a hint size when returning UNSPECIFIED measure specs, and it will respect the attributes `R.attr.foreground`, `R.attr.foregroundGravity`, `R.attr.foregroundTint`, and `R.attr.foregroundTintMode`.
- `MotionEvent.getButtonState` will no longer report `MotionEvent.BUTTON_PRIMARY` and `MotionEvent.BUTTON_SECONDARY` as synonyms for `MotionEvent.BUTTON_STYLUS_PRIMARY` and `MotionEvent.BUTTON_STYLUS_SECONDARY`.
- `ScrollView` now respects the layout param margins when measuring.

Constant Value: 23 (0x00000017)

### N

    public static final int N

N is for Nougat.

Applications targeting this or a later release will get these new changes in behavior. For more information about this release, see the Android Nougat overview.

- `DownloadManager.Request.setAllowedNetworkTypes` will disable "allow over metered" when specifying only `DownloadManager.Request.NETWORK_WIFI`.
- `DownloadManager` no longer allows access to raw file paths.
- `Notification.Builder.setShowWhen` must be called explicitly to have the time shown, and various other changes in `Notification.Builder` to how notifications are shown.
- `Context.MODE_WORLD_READABLE` and `Context.MODE_WORLD_WRITEABLE` are no longer supported.
- `FileUriExposedException` will be thrown to applications.
- Applications will see global drag and drops as per `View.DRAG_FLAG_GLOBAL`.
- `WebView.evaluateJavascript` will not persist state from an empty WebView.
- `AnimatorSet` will not ignore calls to end() before start().
- `AlarmManager.cancel` will throw a NullPointerException if given a null operation.
- `FragmentManager` will ensure fragments have been created before being placed on the back stack.
- `FragmentManager` restores fragments in `Fragment.onCreate` rather than after the method returns.
- `R.attr.resizeableActivity` defaults to true.
- `AnimatedVectorDrawable` throws exceptions when opening invalid VectorDrawable animations.
- `ViewGroup.MarginLayoutParams` will no longer be dropped when converting between some types of layout params (such as `LinearLayout.LayoutParams` to `RelativeLayout.LayoutParams`).
- Your application processes will not be killed when the device density changes.
- Drag and drop. After a view receives the `DragEvent.ACTION_DRAG_ENTERED` event, when the drag shadow moves into a descendant view that can accept the data, the view receives the `DragEvent.ACTION_DRAG_EXITED` event and won’t receive `DragEvent.ACTION_DRAG_LOCATION` and `DragEvent.ACTION_DROP` events while the drag shadow is within that descendant view, even if the descendant view returns `false` from its handler for these events.

Constant Value: 24 (0x00000018)

### N_MR1

    public static final int N_MR1

N MR1: Nougat++. For more information about this release, see Android 7.1 for Developers.

Constant Value: 25 (0x00000019)

### O

    public static final int O

O.

Applications targeting this or a later release will get these new changes in behavior. For more information about this release, see the Android Oreo overview.

- Background execution limits are applied to the application.
- The behavior of AccountManager's `AccountManager.getAccountsByType(String)`, `AccountManager.getAccountsByTypeAndFeatures(String, String[], AccountManagerCallback, Handler)`, and `AccountManager.hasFeatures(Account, String[], AccountManagerCallback, Handler)` has changed as documented there.
- `ActivityManager.RunningAppProcessInfo.IMPORTANCE_PERCEPTIBLE_PRE_26` is now returned as `ActivityManager.RunningAppProcessInfo.IMPORTANCE_PERCEPTIBLE`.
- The `NotificationManager` now requires the use of notification channels.
- Changes to the strict mode that are set in `Application#onCreate` will no longer be clobbered after that function returns.
- A shared library apk with native code will have that native code included in the library path of its clients.
- `Context.getSharedPreferences` in credential encrypted storage will throw an exception before the user is unlocked.
- Attempting to retrieve a `Context#FINGERPRINT_SERVICE` on a device that does not support that feature will now throw a runtime exception.
- `Fragment` will stop any active view animations when the fragment is stopped.
- Some compatibility code in Resources that attempts to use the default Theme the app may be using will be turned off, requiring the app to explicitly request resources with the right theme.
- `ContentResolver.notifyChange` and `ContentResolver.registerContentObserver` will throw a SecurityException if the caller does not have permission to access the provider (or the provider doesn't exit); otherwise the call will be silently ignored.
- `CameraDevice.createCaptureRequest` will enable `CaptureRequest.CONTROL_ENABLE_ZSL` by default for still image capture.
- WallpaperManager's `WallpaperManager.getWallpaperFile(int)`, `WallpaperManager.getDrawable()`, `WallpaperManager.getFastDrawable()`, `WallpaperManager.peekDrawable()`, and `WallpaperManager.peekFastDrawable()` will throw an exception if you can not access the wallpaper.
- The behavior of `UsbDeviceConnection.requestWait` is modified as per the documentation there.
- `StrictMode.VmPolicy.Builder#detectAll` will also enable `StrictMode.VmPolicy.Builder#detectContentUriWithoutPermission` and `StrictMode.VmPolicy.Builder#detectUntaggedSockets`.
- `StrictMode.ThreadPolicy.Builder#detectAll` will also enable `StrictMode.ThreadPolicy.Builder#detectUnbufferedIo`.
- `DocumentsContract`'s various methods will throw failure exceptions back to the caller instead of returning null.
- `View#hasFocusable` now includes auto-focusable views.
- `SurfaceView` will no longer always change the underlying Surface object when something about it changes; apps need to look at the current state of the object to determine which things they are interested in have changed.
- `WindowManager.LayoutParams.TYPE_APPLICATION_OVERLAY` must be used for overlay windows, other system overlay window types are not allowed.
- `ViewTreeObserver.addOnDrawListener` will throw an exception if called from within onDraw.
- `Canvas.setBitmap` will no longer preserve the current matrix and clip stack of the canvas.
- `ListPopupWindow.setHeight` will throw an exception if a negative height is supplied.
- `TextView` will use internationalized input for numbers, dates, and times.
- `Toast` must be used for showing toast windows; the toast window type can not be directly used.
- `WifiManager.getConnectionInfo` requires that the caller hold the location permission to return BSSID/SSID
- `WifiP2pManager.requestPeers` requires the caller hold the location permission.
- `R.attr.maxAspectRatio` defaults to 0, meaning there is no restriction on the app's maximum aspect ratio (so it can be stretched to fill larger screens).
- `R.attr.focusable` defaults to a new state (`auto`) where it will inherit the value of `R.attr.clickable` unless explicitly overridden.
- A default theme-appropriate focus-state highlight will be supplied to all Views which don't provide a focus-state drawable themselves. This can be disabled by setting `R.attr.defaultFocusHighlightEnabled` to false.

Constant Value: 26 (0x0000001a)

### O_MR1

    public static final int O_MR1

O MR1.

Applications targeting this or a later release will get these new changes in behavior. For more information about this release, see Android 8.1 features and APIs.

- Apps exporting and linking to apk shared libraries must explicitly enumerate all signing certificates in a consistent order.
- `R.attr.screenOrientation` can not be used to request a fixed orientation if the associated activity is not fullscreen and opaque.

Constant Value: 27 (0x0000001b)

### P

    public static final int P

P.

Applications targeting this or a later release will get these new changes in behavior. For more information about this release, see the Android 9 Pie overview.

- `Service.startForeground` requires that apps hold the permission `Manifest.permission.FOREGROUND_SERVICE`.
- `LinearLayout` will always remeasure weighted children, even if there is no excess space.

Constant Value: 28 (0x0000001c)

### Q

    public static final int Q

Q.

Applications targeting this or a later release will get these new changes in behavior. For more information about this release, see the Android 10 overview.

- Behavior changes: all apps
- Behavior changes: apps targeting API 29+

Constant Value: 29 (0x0000001d)

### R

    public static final int R

R.

Applications targeting this or a later release will get these new changes in behavior. For more information about this release, see the Android 11 overview.

- Behavior changes: all apps
- Behavior changes: Apps targeting Android 11
- Updates to non-SDK interface restrictions in Android 11

Constant Value: 30 (0x0000001e)

## Public constructors

### VERSION_CODES

    public VERSION_CODES ()

Full name *
Email address *
Company / developer name
One of your Play Store app URLs *
Which best describes your business:*
Apps
Games
Apps & Games
*
*