Skip to content

Most visited

Recently visited

navigation
Added in API level 4

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 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:

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!

int M

M is for Marshmallow!

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

  • Runtime permissions.

Public constructors

Build.VERSION_CODES()

Inherited methods

From class java.lang.Object

Constants

BASE

Added in API level 4
int BASE

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

Constant Value: 1 (0x00000001)

BASE_1_1

Added in API level 4
int BASE_1_1

February 2009: First Android update, officially called 1.1.

Constant Value: 2 (0x00000002)

CUPCAKE

Added in API level 4
int CUPCAKE

May 2009: Android 1.5.

Constant Value: 3 (0x00000003)

CUR_DEVELOPMENT

Added in API level 4
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

Added in API level 4
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 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 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

Added in API level 5
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 START_STICKY behavior instead of the old compatibility 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

Added in API level 6
int ECLAIR_0_1

December 2009: Android 2.0.1

Constant Value: 6 (0x00000006)

ECLAIR_MR1

Added in API level 7
int ECLAIR_MR1

January 2010: Android 2.1

Constant Value: 7 (0x00000007)

FROYO

Added in API level 8
int FROYO

June 2010: Android 2.2

Constant Value: 8 (0x00000008)

GINGERBREAD

Added in API level 9
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

Added in API level 10
int GINGERBREAD_MR1

February 2011: Android 2.3.3.

Constant Value: 10 (0x0000000a)

HONEYCOMB

Added in API level 11
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: 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 MODE_MULTI_PROCESS is used.
  • setMotionEventSplittingEnabled(boolean) will default to true.
  • 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

Added in API level 12
int HONEYCOMB_MR1

May 2011: Android 3.1.

Constant Value: 12 (0x0000000c)

HONEYCOMB_MR2

Added in API level 13
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 screenWidthDp, screenHeightDp, and smallestScreenWidthDp. Supplying these in <supports-screens> as per requiresSmallestWidthDp, compatibleWidthLimitDp, and 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:

Constant Value: 13 (0x0000000d)

ICE_CREAM_SANDWICH

Added in API level 14
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: Theme_DeviceDefault. This may be the holo dark theme or a different dark theme defined by the specific device. The 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 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 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

Added in API level 15
int ICE_CREAM_SANDWICH_MR1

December 2011: Android 4.0.3.

Constant Value: 15 (0x0000000f)

JELLY_BEAN

Added in API level 16
int JELLY_BEAN

June 2012: Android 4.1.

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

Constant Value: 16 (0x00000010)

JELLY_BEAN_MR1

Added in API level 17
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:

Constant Value: 17 (0x00000011)

JELLY_BEAN_MR2

Added in API level 18
int JELLY_BEAN_MR2

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

Constant Value: 18 (0x00000012)

KITKAT

Added in API level 19
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:

  • 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 READ_EXTERNAL_STORAGE permission is now always enforced.
  • Access to package-specific external storage directories belonging to the calling app no longer requires the READ_EXTERNAL_STORAGE or WRITE_EXTERNAL_STORAGE permissions.

Constant Value: 19 (0x00000013)

KITKAT_WATCH

Added in API level 20
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

Added in API level 21
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:

  • 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 BIND_DREAM_SERVICE permission to be usable.

Constant Value: 21 (0x00000015)

LOLLIPOP_MR1

Added in API level 22
int LOLLIPOP_MR1

March 2015: Lollipop with an extra sugar coating on the outside!

Constant Value: 22 (0x00000016)

M

Added in API level 23
int M

M is for Marshmallow!

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

Constant Value: 23 (0x00000017)

Public constructors

Build.VERSION_CODES

Added in API level 4
Build.VERSION_CODES ()

This site uses cookies to store your preferences for site-specific language and display options.

Hooray!

This class requires API level or higher

This doc is hidden because your selected API level for the documentation is . You can change the documentation API level with the selector above the left navigation.

For more information about specifying the API level your app requires, read Supporting Different Platform Versions.