Android 2.0, Revision 1 (October 2009)
- Dependencies:
-
Requires SDK Tools r3 or higher.
API Level: {@sdkPlatformApiLevel}
Android {@sdkPlatformVersion} is a {@sdkPlatformMajorMinor} platform release deployable to Android-powered handsets starting in November 2009. The release includes new features for users and developers, as well as changes in the Android framework API.
For developers, the Android {@sdkPlatformVersion} platform is available as a downloadable component for the Android SDK. The downloadable platform includes a fully compliant Android library and system image, as well as a set of emulator skins, sample applications, and more. The downloadable platform is fully compliant and includes no external libraries.
To get started developing or testing against the Android {@sdkPlatformVersion} platform, use the Android SDK and AVD Manager tool to download the platform into your SDK. For more information, see Adding SDK Components.
For a list of new user features and platform highlights, see the Android {@sdkPlatformVersion} Platform Highlights document.
The sections below provide notes about successive releases of the Android {@sdkPlatformVersion} platform component for the Android SDK, as denoted by revision number. To determine what revision(s) of the Android {@sdkPlatformVersion} platforms are installed in your SDK environment, refer to the "Installed Packages" listing in the Android SDK and AVD Manager.
Android 2.0, Revision 1 (October 2009)
Requires SDK Tools r3 or higher.
The system image included in the downloadable platform provides these built-in applications:
|
|
The system image included in the downloadable platform provides a variety of built-in locales. In some cases, region-specific strings are available for the locales. In other cases, a default version of the language is used. The languages that are available in the Android {@sdkPlatformVersion} system image are listed below (with language_country/region locale descriptor).
|
|
Localized UI strings match the locales that are accessible through Settings.
The downloadable platform includes a set of emulator skins that you can use for modeling your application in different screen sizes and resolutions. The emulator skins are:
For more information about how to develop an application that displays and functions properly on all Android-powered devices, see Supporting Multiple Screens.
The sections below provide information about new developer features offered by the downloadable Android 2.0 platform component.
zipalign optimization. For more information, see Signing Your Applications.The sections below provide information about the application framework API provided by the Android {@sdkPlatformVersion} platform.
The Android {@sdkPlatformVersion} platform delivers an updated version of the framework API. As with previous versions, the Android {@sdkPlatformVersion} API is assigned an integer identifier — {@sdkPlatformApiLevel} — that is stored in the system itself. This identifier, called the "API Level", allows the system to correctly determine whether an application is compatible with the system, prior to installing the application.
To use APIs introduced in Android {@sdkPlatformVersion} in your application, you need to
set the proper value, "{@sdkPlatformApiLevel}", in the attributes of the <uses-sdk>
element in your application's manifest.
For more information about how to use API Level, see the API Levels document.
Android 2.0 is designed to run on devices that use virtual keys for HOME, MENU, BACK, and SEARCH, rather than physical keys. To support the best user experience on those devices, the Android platform now executes these buttons at key-up, for a key-down/key-up pair, rather than key-down. This helps prevent accidental button events and lets the user press the button area and then drag out of it without generating an event.
This change in behavior should only affect your application if it is intercepting button events and taking an action on key-down, rather than on key-up. Especially if your application is intercepting the BACK key, you should make sure that your application is handling the key events properly.
In general, intercepting the BACK key in an application is not recommended, however, if your application is doing so and it invokes some action on key-down, rather than key-up, you should modify your code.
If your application will use APIs introduced in Android 2.0 (API Level 5), you can take advantage of new APIs for managing key-event pairs:
public boolean onKeyDown(int keyCode, KeyEvent event) {
if (keyCode == KeyEvent.KEYCODE_BACK
&& event.getRepeatCount() == 0) {
event.startTracking();
return true;
}
return super.onKeyDown(keyCode, event);
}
public boolean onKeyUp(int keyCode, KeyEvent event) {
if (keyCode == KeyEvent.KEYCODE_BACK && event.isTracking()
&& !event.isCanceled()) {
// *** DO ACTION HERE ***
return true;
}
return super.onKeyUp(keyCode, event);
}
If you want to update a legacy application so that its handling of the BACK key works properly for both Android 2.0 and older platform versions, you can use an approach similar to that shown above. Your code can catch the target button event on key-down, set a flag to track the key event, and then also catch the event on key-up, executing the desired action if the tracking flag is set. You'll also want to watch for focus changes and clear the tracking flag when gaining/losing focus.
For a detailed view of API changes in Android {@sdkPlatformVersion} (API Level {@sdkPlatformApiLevel}), as compared to the previous version, see the API Differences Report.