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.
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:
|
|||||||||
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:
|
|||||||||
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 | Android 4.4W: KitKat for watches, snacks on the run. | |||||||||
int | LOLLIPOP | Lollipop. | |||||||||
int | LOLLIPOP_MR1 | Lollipop with an extra sugar coating on the outside! | |||||||||
int | M | M comes after L. |
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
java.lang.Object
|
October 2008: The original, first, version of Android. Yay!
February 2009: First Android update, officially called 1.1.
May 2009: Android 1.5.
Magic version number for a current development build, which has not yet turned into an official release.
September 2009: Android 1.6.
Applications targeting this or a later release will get these new changes in behavior:
WRITE_EXTERNAL_STORAGE
permission to be
able to modify the contents of the SD card. (Apps targeting
earlier versions will always request the 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.)
TabHost
will use the new dark tab
background design.
November 2009: Android 2.0
Applications targeting this or a later release will get these new changes in behavior:
Service.onStartCommand
function will return the new
START_STICKY
behavior instead of the
old compatibility START_STICKY_COMPATIBILITY
.
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.
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.
December 2009: Android 2.0.1
January 2010: Android 2.1
June 2010: Android 2.2
November 2010: Android 2.3
Applications targeting this or a later release will get these new changes in behavior:
February 2011: Android 2.3.3.
February 2011: Android 3.0.
Applications targeting this or a later release will get these new changes in behavior:
Theme_Holo
.
Activity
.
Activity.onPause()
method.
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.
May 2011: Android 3.1.
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:
New FEATURE_SCREEN_PORTRAIT
and 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 execute(Params...)
.
ActivityInfo.configChanges
will have the
CONFIG_SCREEN_SIZE
and
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.
October 2011: Android 4.0.
Applications targeting this or a later release will get these new changes in behavior:
android:hardwareAccelerated
to turn it off if needed, although this is strongly discouraged since
it will result in poor performance on larger screen devices.
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.
Context.bindService()
will not automatically add in BIND_WAIVE_PRIORITY
.
AnimationSet
will parse out
the duration, fillBefore, fillAfter, repeatMode, and startOffset
XML attributes that are defined.
ActionBar.setHomeButtonEnabled()
is false by default.
December 2011: Android 4.0.3.
June 2012: Android 4.1.
Applications targeting this or a later release will get these new changes in behavior:
READ_CALL_LOG
and/or WRITE_CALL_LOG
permissions;
access to the call log is no longer implicitly provided through
READ_CONTACTS
and
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.
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.
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.
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.
November 2012: Android 4.2, Moar jelly beans!
Applications targeting this or a later release will get these new changes in behavior:
android:exported
is now
false
. See
the android:exported section in the provider documentation for more details.View.getLayoutDirection()
can return different values than LAYOUT_DIRECTION_LTR
based on the locale etc.
WebView.addJavascriptInterface
requires explicit annotations on methods
for them to be accessible from Javascript.
July 2013: Android 4.3, the revenge of the beans.
October 2013: Android 4.4, KitKat, another tasty treat.
Applications targeting this or a later release will get these new changes in behavior:
PreferenceActivity.isValueFragment
becomes false instead of true.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 pageAlarmManager.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.READ_EXTERNAL_STORAGE
permission is now always enforced.READ_EXTERNAL_STORAGE
or
WRITE_EXTERNAL_STORAGE
permissions.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.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.Spinner
throws an exception if attaching an
adapter with more than one item type.LauncherApps
to correctly populate its
apps UI).Service.stopForeground
with removeNotification false will modify the still posted notification so that
it is no longer forced to be ongoing.DreamService
must require the
BIND_DREAM_SERVICE
permission to be usable.Lollipop with an extra sugar coating on the outside!