android -版本更新信息

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: The Service.onStartCommand function will return the new START_STICKY behavior instead of the old compatibilitySTART_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!
int	M M is for Marshmallow! Applications targeting this or a later release will get these new changes in behavior: Runtime permissions.
int	N N is for Nougat.
int	N_MR1 N MR1: Nougat++.
int	O O.

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, andsmallestScreenWidthDp. 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.

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:

• You must explicitly request the READ_CALL_LOG and/or WRITE_CALL_LOG permissions; access to the call log is no longer implicitly provided throughREAD_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.
• 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 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

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:

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

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

• Runtime permissions. Dangerous permissions are no longer granted at install time, but must be requested by the application at runtime throughrequestPermissions(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 foreground, foregroundGravity, foregroundTint, andforegroundTintMode.
• MotionEvent.getButtonState will no longer report BUTTON_PRIMARY and BUTTON_SECONDARY as synonyms for BUTTON_STYLUS_PRIMARY andBUTTON_STYLUS_SECONDARY.
• ScrollView now respects the layout param margins when measuring.

Constant Value: 23 (0x00000017)

N

added in  API level 24

int N

N is for Nougat.

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

• DownloadManager.Request.setAllowedNetworkTypes will disable "allow over metered" when specifying only 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.
• MODE_WORLD_READABLE and MODE_WORLD_WRITEABLE are no longer supported.
• FileUriExposedException will be thrown to applications.
• Applications will see global drag and drops as per 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.
• 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 asLinearLayout.LayoutParams to RelativeLayout.LayoutParams).
• Your application processes will not be killed when the device density changes.
• Drag and drop. After a view receives the ACTION_DRAG_ENTERED event, when the drag shadow moves into a descendant view that can accept the data, the view receives the ACTION_DRAG_EXITED event and won’t receive ACTION_DRAG_LOCATION and 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

added in  API level 25

int N_MR1

N MR1: Nougat++.

Constant Value: 25 (0x00000019)

O

Android O Developer Preview

int O

O.

Constant Value: 10000 (0x00002710)

Public constructors

---

Build.VERSION_CODES

added in  API level 4

Build.VERSION_CODES ()