Android Guides | Samples

Android.OS.BuildVersionCodes Enumeration

Enumerates values returned by several types and taken as a parameter of the EditorInfo.MakeCompatible member.

Syntax

public enum BuildVersionCodes

Remarks

Members

Member NameDescription
BaseOctober 2008: The original, first, version of Android. Yay!
Base11February 2009: First Android update, officially called 1.1.
CupcakeMay 2009: Android 1.5.
CurDevelopmentMagic version number for a current development build, which has not yet turned into an official release.
Donut

September 2009: Android 1.6.

  • They must explicitly request the Manifest+Permission.WriteExternalStorage 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.ReadPhoneState 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.

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

Eclair

November 2009: Android 2.0

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

Eclair01December 2009: Android 2.0.1
EclairMr1January 2010: Android 2.1
FroyoJune 2010: Android 2.2
Gingerbread

November 2010: Android 2.3

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

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

GingerbreadMr1February 2011: Android 2.3.3.
Honeycomb

February 2011: Android 3.0.

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

HoneycombMr1May 2011: Android 3.1.
HoneycombMr2

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 Build+VERSION_CODES.Honeycomb or later; it had been VERSION_CODES.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.FeatureScreenPortrait and PackageManager.FeatureScreenLandscape 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`3 will use the serial executor by default when calling AsyncTask`3.execute(Params...).

IceCreamSandwich

October 2011: Android 4.0.

  • 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 Attribute.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: Resource+Style.ThemeDeviceDefault. This may be the holo dark theme or a different dark theme defined by the specific device. The Style.ThemeHolo 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 Resource+Style.ThemeDeviceDefault 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(Intent,IServiceConnection,IServiceConnection) will not automatically add in Bind.WaivePriority.
  • 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(Boolean) is false by default.

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

IceCreamSandwichMr1December 2011: Android 4.0.3.
JellyBean

June 2012: Android 4.1.

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

JellyBeanMr1

Android 4.2: Moar jelly beans!

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

JellyBeanMr2Android 4.3: Jelly Bean MR2, the revenge of the beans.
Kitkat
KitkatWatch
L
Lollipop

Requirements

Namespace: Android.OS
Assembly: Mono.Android (in Mono.Android.dll)
Assembly Versions: 0.0.0.0

The members of Android.OS.BuildVersionCodes are listed below.

See Also: Enum

Public Fields

BaseBuildVersionCodes. October 2008: The original, first, version of Android. Yay!
Base11BuildVersionCodes. February 2009: First Android update, officially called 1.1.
CupcakeBuildVersionCodes. May 2009: Android 1.5.
CurDevelopmentBuildVersionCodes. Magic version number for a current development build, which has not yet turned into an official release.
DonutBuildVersionCodes.

September 2009: Android 1.6.

  • They must explicitly request the Manifest+Permission.WriteExternalStorage 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.ReadPhoneState 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.

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

EclairBuildVersionCodes.

November 2009: Android 2.0

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

Eclair01BuildVersionCodes. December 2009: Android 2.0.1
EclairMr1BuildVersionCodes. January 2010: Android 2.1
FroyoBuildVersionCodes. June 2010: Android 2.2
GingerbreadBuildVersionCodes.

November 2010: Android 2.3

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

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

GingerbreadMr1BuildVersionCodes. February 2011: Android 2.3.3.
HoneycombBuildVersionCodes.

February 2011: Android 3.0.

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

HoneycombMr1BuildVersionCodes. May 2011: Android 3.1.
HoneycombMr2BuildVersionCodes.

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 Build+VERSION_CODES.Honeycomb or later; it had been VERSION_CODES.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.FeatureScreenPortrait and PackageManager.FeatureScreenLandscape 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`3 will use the serial executor by default when calling AsyncTask`3.execute(Params...).

IceCreamSandwichBuildVersionCodes.

October 2011: Android 4.0.

  • 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 Attribute.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: Resource+Style.ThemeDeviceDefault. This may be the holo dark theme or a different dark theme defined by the specific device. The Style.ThemeHolo 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 Resource+Style.ThemeDeviceDefault 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(Intent,IServiceConnection,IServiceConnection) will not automatically add in Bind.WaivePriority.
  • 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(Boolean) is false by default.

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

IceCreamSandwichMr1BuildVersionCodes. December 2011: Android 4.0.3.
JellyBeanBuildVersionCodes.

June 2012: Android 4.1.

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

JellyBeanMr1BuildVersionCodes.

Android 4.2: Moar jelly beans!

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

JellyBeanMr2BuildVersionCodes. Android 4.3: Jelly Bean MR2, the revenge of the beans.
KitkatBuildVersionCodes.
KitkatWatchBuildVersionCodes.
LBuildVersionCodes.
LollipopBuildVersionCodes.