The SDK includes a variety of tools for developing and debugging application code and designing an application UI. You can read about the tools in the +
The SDK includes a full set of tools for developing and debugging application code and designing an application UI. You can read about the tools in the
Dev Guide and access them in the <sdk>/tools/ directory.
-
The tools package included in this SDK includes many updates from that provided in the previous SDK and requires you to migrate your applications to the new development environment. For details, see the Upgrading the SDK document.
+The tools package in this SDK includes updates from those provided in the previous SDK. The tools also require a different project structure. To use the new tools, you need to migrate your applications to the new development environment. For more information about how to migrate, see Upgrading the SDK. -
For more information about the new tools features, see the SDK Release Notes. -
The Android system images listed below are included in this SDK. For more information about a system image — features, applications included, localizations, API changes, and so on — see its Version Notes.
+This SDK includes multiple Android platform versions that you use to develop applications. For each version, both a fully compliant Android library and system image are provided. The table below lists the platform versions included in this SDK. For more information about a platform version — features, applications included, localizations, API changes, and so on — see its Version Notes.
| Notes | Description | +Notes | Description | ||||
|---|---|---|---|---|---|---|---|
| 3 | Includes a set of standard development applications. | +Includes a standard Android 1.5 library and system image with a set of development applications. Does not include any external libraries (such as the Maps external library). | |||||
| 2 | Includes a set of standard development applications. | +Includes a compliant Android 1.1 library and system image with a set of development applications. Also includes the Maps external library (due to legacy build system issues). +external library. |
An SDK add-on provides a development environment for an Android external library or a customized (but fully compliant) Android system image. This SDK includes the SDK add-on listed below. The Android system API Level required by the add-on is noted.
+ +| Notes | Description | +||
|---|---|---|---|
| 3 | ++ | Includes the com.google.android.maps external library, a compliant +system image, a {@link android.location.Geocoder Geocoder} +backend service implementation, documentation, and sample code. | +
You can look at a variety of tutorials and samples in the Dev Guide and access the sample code itself
in the <sdk>/platforms/android-1.5/samples/ directory of the SDK package. Note the new location — the SDK now includes multiple platform versions that you can develop against and each has its own sample code directory.
This document provides version-specific information about Android SDK releases. For the latest known issues, please ensure that you're viewing this page at: http://developer.android.com/sdk/RELEASENOTES.html.
+This document provides version-specific information about Android SDK +releases. For the latest known issues, please ensure that you're viewing this +page at: +http://developer.android.com/sdk/RELEASENOTES.html.
+ +This SDK provides updates to the development tools and Android system that +you use to create applications for compliant Android-powered devices.
+ +This SDK release includes many new features for developers. Highlights of the +changes include:
+ +For details about the Android platforms included in the SDK — including +bug fixes, features, and API changes — please read the Version Notes +documents available at left. For a list of Android platforms included in this +release, see the Download +page.
+ +If you've been developing an application using an Android 1.1 SDK, you need +to make a few changes to your development environment to migrate to the new SDK. +Tools and documentation are provided to assist you. No changes to the source +code of an existing application should be needed, provided that your application +is not using Android internal structures or APIs.
+ +To ensure that your existing application will work properly on a device +running the latest version of the Android platform, you are strongly encouraged +to migrate the application to the new SDK, compile it using the platform +matching the application's original API Level, and run it against the most +current platform.
+ +If you're installing the Android SDK for the first time, please see +the instructions in Installing the SDK. + +
This version of the SDK introduces support for SDK add-ons, which extend the +Android SDK to give you access to one or more external Android libraries and/or +a customized (but compliant) system image that can run in the emulator. The +purpose of an SDK add-on is to give you a way to develop applications for a +specific actual device (or family of devices) that extends the APIs available to +Android applications through external libraries or system customizations.
+ +From the perspective of your Android development environment, an SDK add-on +is similar to any of the Android platform targets included in the SDK — it +includes an external library, a system image, as well as custom emulator skins +and system properties. The add-on differs in that the Android platform it +provides may include customized UI, resources, or behaviors, a different set of +preinstalled applications, or other similar modifications. + +
The SDK includes a single SDK add-on — the Google APIs add-on. The +Google APIs add-on gives your application access to the com.google.android.maps +external library that is included on many (if not most) Android-powered devices. +The Google APIs add-on also includes a {@link android.location.Geocoder Geocoder} +backend service implementation. For more information, see the "Maps External +Library" section below.
+ +The SDK now gives you the capability to compile an application against any +one of several system targets, then run it in the emulator on top of any +compatible system image. There are two types of targets:
+A new tool called "android" lets you discover what targets and AVDs are +available to use.
+ +For more information about AVDs, see Android Virtual Devices + +
Maps External Library
+ +In previous versions of the SDK, the com.google.android.maps package was +included in the standard Android library and system image. In the Android 1.5 +SDK, that is not the case. The Android 1.5 library and system image do not +include the Maps external library (com.google.android.maps). However, the Maps +external library is available as part of the Google APIs add-on for the Android +SDK, downloadable from this location:
+ +http://code.google.com +/android/add-ons/google-apis
+ +For your convenience, the Google APIs add-on is included in the SDK.
+ +For information about how to register for a Maps API Key, see + +Obtaining a Maps API Key.
+ +USB Drivers for Windows
+ +If you are using Windows and want to develop or test your application on an +Android-powered device (such as the T-Mobile G1), you need an appropriate USB +driver. For your convenience, the Windows version of the Android SDK includes +these USB drivers that you can install, to let you develop on the device:
+ +The USB driver files are located in the
+<SDK>/usb_driver directory. For details and
+installation instructions, see Setting Up a
+Device for Development.
Media
+Sensor problems in Emulator
+ +Other
+ +This SDK provides the development tools and Android system image you need to create applications for Android-powered devices. Applications developed on this SDK will be compatible with mobile devices running the Android 1.1 platform.
+This SDK provides the development tools and Android system image you need to +create applications for Android-powered devices. Applications developed on this +SDK will be compatible with mobile devices running the Android 1.1 platform. +
-This release provides an updated system image (Android 1.1), updated documentation, and the same set of development tools provided in the Android 1.0 r2 SDK. The updated system image includes bug fixes and some smaller features, as well as a few minor API changes from the 1.0 version.
+This release provides an updated system image (Android 1.1), updated +documentation, and the same set of development tools provided in the Android 1.0 +r2 SDK. The updated system image includes bug fixes and some smaller features, +as well as a few minor API changes from the 1.0 version.
-For details about the Android 1.1 system image included in the SDK — including bug fixes, features, and API changes — please read the Android 1.1 Version Notes.
+For details about the Android 1.1 system image included in the SDK — +including bug fixes, features, and API changes — please read the Android 1.1 Version Notes.
If you are using this SDK to build an application that is compatible only with Android-powered devices running the Android 1.1 platform, please note that you must set the the android:minSdkVersion attribute in the application's manifest to the API Level of Android 1.1 — "2".
If you are using this SDK to build an application that is compatible
+only with Android-powered devices running the Android 1.1 platform,
+please note that you must set the the
+android:minSdkVersion attribute in the application's manifest to
+the API Level of Android 1.1 — "2".
Specifically, you specify the android:minSdkVersion attribute in a <uses-sdk> element as a child of <manifest> in the manifest file. When set, the attribute looks like this:
Specifically, you specify the android:minSdkVersion attribute in
+a <uses-sdk> element as a child of
+<manifest> in the manifest file. When set, the attribute
+looks like this:
<manifest>
...
@@ -24,13 +212,29 @@ page.title=SDK Release Notes
</manifest>
By setting android:minSdkVersion in this way, you ensure that users will only be able to install your application if their devices are running the Android 1.1 platform. In turn, this ensures that your application will function properly on their devices, especially if it uses APIs introduced in Android 1.1.
By setting android:minSdkVersion in this way, you ensure that
+users will only be able to install your application if their devices are running
+the Android 1.1 platform. In turn, this ensures that your application will
+function properly on their devices, especially if it uses APIs introduced in
+Android 1.1.
If your application uses APIs introduced in Android 1.1 but does not declare <uses-sdk minSdkVersion="2" />, then it will run properly on Android 1.1 devices but not on Android 1.0 devices.
If your application uses APIs introduced in Android 1.1 but does not declare
+<uses-sdk minSdkVersion="2" />, then it will run properly on
+Android 1.1 devices but not on Android 1.0 devices.
If your application does not use any new APIs introduced in Android 1.1, you can indicate Android 1.0 compatibility by removing minSdkVersion or setting the attribute to "1". However, before publishing your application, you must make sure to compile your application against the Android 1.0 system image (available in the Android 1.0 SDK), to ensure that it builds and functions properly for Android 1.0 devices. You should test the application against system images corresponding to the API Levels that the application is designed to be compatible with.
If your application does not use any new APIs introduced in Android 1.1, you
+can indicate Android 1.0 compatibility by removing minSdkVersion or
+setting the attribute to "1". However, before publishing your application, you
+must make sure to compile your application against the Android 1.0 system image
+(available in the Android 1.0 SDK), to ensure that it builds and functions
+properly for Android 1.0 devices. You should test the application against system
+images corresponding to the API Levels that the application is designed to be
+compatible with.
If you are sure your application is not using Android 1.1 APIs and has no need to use them, you might find it easier to keep working in the Android 1.0 SDK, rather than migrating to the Android 1.1 SDK and having to do additional testing.
+If you are sure your application is not using Android 1.1 APIs and has no +need to use them, you might find it easier to keep working in the Android 1.0 +SDK, rather than migrating to the Android 1.1 SDK and having to do additional +testing.
If you're installing the Android SDK for the first time, please see the instructions in Installing the SDK. +href="{@docRoot}sdk/1.5_r1/installing.html">Installing the SDK.
This SDK release includes the Android 1.0 platform and application API. diff --git a/docs/html/sdk/adt_download.jd b/docs/html/sdk/adt_download.jd index 6e9eec4a2b736..6d46297830e8e 100644 --- a/docs/html/sdk/adt_download.jd +++ b/docs/html/sdk/adt_download.jd @@ -26,11 +26,18 @@ page.
+April 2009 +
+ + +The Android 1.5 platform introduces many new features for users and developers. +The list below provides an overview of the changes.
+ +Applications can now use a new element in their manifest files, <uses-
+configuration> to indicate to the Android system what hardware features
+they require in order to function properly. For example, an application might
+use the element to specify that it requires a physical keyboard or a particular
+navigation device, such as a trackball. Prior to installing the application, the
+Android system checks the attributes defined for the
+<uses-configuration> element and allows the installation to
+continue only if the required hardware is present.
Please see Download the Android 1.5 Early Look SDK for more information.
+This document provides version notes for the Android 1.5 system image included in the SDK.
+ +The Android 1.5 system delivered in the SDK (as library and system image) is +the development counterpart to the Android 1.5 production system image, +deployable to Android-powered handsets starting in May 2009. The system is fully +compliant and includes no external libraries. This is the first version of the +Android SDK that does not include the Maps external library.
+ +The Android 1.5 system delivers an updated version of the framework +API. As with previous versions, the Android 1.5 API +is assigned an integer identifier — 3 — 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.
+ +Applications can reference a specific API Level value in their
+manifest files, to indicate the minimum version of the Android system
+required to run the application. To reference a minimum API Level, applications
+can add a minSdkVersion attribute in their manifest files.
+The value of the attribute is an integer corresponding to an API Level
+identifier. Prior to installing an application, the system then checks the value of
+minSdkVersion and allows the install only
+if the referenced integer is less than or equal to the API Level integer stored
+in the system itself.
When you migrate your application to the new SDK, you will need to choose
+the platform version against which you will compile your application. In
+general, you should compile your application against the lowest possible
+version of the platform that your application can support. After you determine
+the lowest version, you should ensure that your application's manifest file
+defines the API Level of the lowest compatible platform version in the
+minSdkVersion attribute.
+
+
After compiling your application, you should make sure to test it on the
+platform specified in the application's minSdkVersion attribute. To
+ensure forward-compatibility, you should also run the application on platforms
+using a higher API Level than that used by your application. To run your
+application against different platform versions in the emulator, you create an
+AVD for each platform version that you want to test. For more information about
+AVDs, see Android Virtual
+Devices. If you are using a physical device for testing, ensure that you
+know the API Level of the Android platform it runs.
If you build an application using the Android 1.5 library and your
+application makes use of any APIs introduced in API Level 3, you must set the
+android:minSdkVersion attribute in the application's manifest to
+"3".
Specifically, you define the android:minSdkVersion
+attribute in a <uses-sdk> element as a child of
+<manifest> in the manifest file. When set, the
+attribute looks like this:
<manifest> + ... + <uses-sdk minSdkVersion="3" /> + ... +</manifest>+ +
By setting android:minSdkVersion in this way, you ensure that
+users will only be able to install your application if their devices are running
+a compatible version of the Android platform. In turn, this ensures that your
+application will function properly on their devices. This is especially
+important if your application uses APIs or system features
+introduced in Android 1.5.
If your application uses APIs introduced in Android 1.5 but does not
+declare <uses-sdk minSdkVersion="3" />, then it will
+run properly on Android 1.5 devices but not on Android 1.0
+devices. In the latter case, the application will crash at runtime when
+it tries to use the Android 1.5 APIs.
Conversely, if your application does not use any new APIs introduced in +Android 1.5, the application will in most cases function normally on devices +running a later version of the platform. However, if you have published +the application, you are strongly encouraged to install and test your +application on the Android 1.5 system image included in the SDK. This will +ensure a smooth transition for users, as they upgrade their devices to +the new version of the Android platform.
+ +Finally, if your application does not use any new APIs introduced since
+Android 1.1, you can indicate general Android 1.1 compatibility by
+setting the attribute to "2". If your application does not use any
+new APIs introduced since Android 1.0, you can remove the attribute or
+set it to "1". However,
+before publishing your application, you must make sure to compile your
+application against the Android library that corresponds to the application's
+minSdkVeresion value.
The system image includes these built-in applications:
+The system image 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 will be +available in the Android 1.5 system image are listed below (with +language_country/region locale descriptor).
+ +Localized UI strings match the locales that are displayable in +the emulator, accessible through the device Settings application.
+ + + +For a list of new system features, see the Android 1.5 Platform +Highlights document.
+ +Applications can now use a new element in their manifest files,
+<uses-configuration> to indicate to the Android system what hardware
+features they require in order to function properly. For example, an application
+might use the element to specify that it requires a physical keyboard or a
+particular navigation device, such as a trackball. Prior to installing the
+application, the Android system checks the attributes defined for the
+<uses-configuration> element and allows the installation to
+continue only if the required hardware is present.
For a detailed view of API changes in this platform (API Level 3), see the API Differences Report.
diff --git a/docs/html/sdk/sdk_toc.cs b/docs/html/sdk/sdk_toc.cs index 8c7a0a764fe65..1e5122ffb6443 100644 --- a/docs/html/sdk/sdk_toc.cs +++ b/docs/html/sdk/sdk_toc.cs @@ -2,17 +2,17 @@