sdk.rel.id=1
sdk.date=April 2009
-sdk.win_download=
+sdk.win_download=android-sdk-windows-1.5_r1.zip
sdk.win_bytes=
sdk.win_checksum=
-sdk.mac_download=
+sdk.mac_download=android-sdk-mac_x86-1.5_r1.zip
sdk.mac_bytes=
sdk.mac_checksum=
-sdk.linux_download=
+sdk.linux_download=android-sdk-linux_x86-1.5_r1.zip
sdk.linux_bytes=
sdk.linux_checksum=
-page.title=Download Android SDK
+page.title=Android 1.5 SDK, Release 1
@jd:body
<h2>SDK Contents</h2>
<h4>Development tools</h4>
-<p>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
+<p>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
<a href="{@docRoot}guide/developing/tools/index.html">Dev Guide</a> and access them in the <code><sdk>/tools/</code> directory.
-<p>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 <a href="upgrading">Upgrading the SDK</a> document.</p>
+<p>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 <a href="{@docRoot}sdk/1.5_r1/upgrading.html">Upgrading the SDK</a>.
-<h4 id="system_images">System Images</h4>
+<p>For more information about the new tools features, see the <a href="{@docRoot}sdk/RELEASENOTES.html">SDK Release Notes</a>.
-<p>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. </p>
+<h4 id="system_images">Android Platforms</h4>
+
+<p>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. </p>
<table style="margin-right:1em;" width="80%">
<tr>
-<th><nobr>System Image</nobr></th><th><nobr>API Level</nobr></th><th>Notes</th><th>Description</th>
+<th><nobr>Platform</nobr></th><th><nobr>API Level</nobr></th><th>Notes</th><th>Description</th>
</tr>
<tr>
<td width="5%"><nobr>Android 1.5</nobr></td>
<td width="5%">3</td>
<td width="5%"><nobr><a href="{@docRoot}sdk/android-1.5.html">Version Notes</a></nobr></td>
-<td>Includes a set of standard development applications. </td>
+<td>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).</td>
</tr>
<tr>
<td width="5%"><nobr>Android 1.1</nobr></td>
<td width="5%">2</td>
<td width="5%"><nobr><a href="{@docRoot}sdk/android-1.1.html">Version Notes</a></nobr></td>
-<td>Includes a set of standard development applications. </td>
+<td>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).</a>
+external library. </td>
+
+</tr>
+</table>
+
+<h4 id="system_images">SDK Add-Ons</h4>
+
+<p>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.</p>
+<table style="margin-right:1em;" width="80%">
+<tr>
+<th><nobr>Add-On</nobr></th><th><nobr>API Level</nobr></th><th>Notes</th><th>Description</th>
+</tr>
+<tr>
+<td width="5%"><nobr>Google APIs</nobr></td>
+<td width="5%">3</td>
+<td width="5%"> </td>
+<td>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. </td>
</tr>
</table>
<p>You can look at a variety of tutorials and samples in the <a href="{@docRoot}guide/samples/index.html">Dev Guide</a> and access the sample code itself
in the <code><sdk>/platforms/android-1.5/samples/</code> 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. </p>
-<!--
<h4>Documentation</h4>
<p>The SDK package includes a full set of local documentation. To view it, open the <code><sdk>/documentation.html</code> file in a web browser. If you are developing in an IDE such as Eclipse, you can also view the reference documentation directly in the IDE. </p>
<p>The most current documentation is always available on the Android Developers site:</p>
<p style="margin-left:2em;"><a href="http://developer.android.com/index.html">http://developer.android.com/</a></p>
--->
page.title=SDK Release Notes
@jd:body
-<p>This document provides version-specific information about Android SDK releases. For the latest known issues, please ensure that you're viewing this page at: <a href="http://developer.android.com/sdk/RELEASENOTES.html">http://developer.android.com/sdk/RELEASENOTES.html</a>.</p>
+<p>This document provides version-specific information about Android SDK
+releases. For the latest known issues, please ensure that you're viewing this
+page at:
+<a href="http://developer.android.com/sdk/RELEASENOTES.html">http://developer.android.com/sdk/RELEASENOTES.html</a>.</p>
+
+<h2 id="1.5_r1">Android 1.5 SDK, Release 1</h2>
+
+<p>This SDK provides updates to the development tools and Android system that
+you use to create applications for compliant Android-powered devices. </p>
+
+<h3>Release Overview</h3>
+
+<p>This SDK release includes many new features for developers. Highlights of the
+changes include: </p>
+
+ <ul>
+ <li>Multiple versions of the Android platform are included (Android 1.1,
+Android 1.5). The tools are updated to let you deploy your application
+on any platform in the SDK, which helps you ensure forward-compitility and,
+if applicable, backward-compatibility.</li>
+ <li>Introduces <a href="{@docRoot}guide/developing/tools/avd.html">Android
+Virtual Devices</a> — (AVD) configurations of options that you
+run in the emulator to better model actual devices. Each AVD gets its
+own dedicated storage area, making it much easier to work with multiple emulators
+that are running concurrently.</li>
+ <li>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. </li>
+ <li>The new Eclipse ADT plugin (version 0.9.0) offers new Wizards to let you
+create projects targetted for specific Android configurations, generate XML
+resources (such as layouts, animations, and menus), generate alternate layouts,
+and export and sign your application for publishing.</li>
+ <li>Improved JUnit support in ADT</li>
+ <li>Easier profiling of performance</li>
+ <li>Easier management of localized applications. You can now include or
+exclude locale resources when building your APK from a single
+Android project.</li>
+ <li>A new tool called "android" replaces the activitycreator script.</li>
+ </ul>
+
+<p>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 <a href="{@docRoot}sdk/1.5_r1/index.html">Download
+page</a>.</p>
+
+<h3>Installation and Upgrade Notes</h3>
+
+<p>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.</p>
+
+<p>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. </p>
+
+<p>If you're installing the Android SDK for the first time, please see
+the instructions in <a
+href="{@docRoot}sdk/1.5_r1/installing.html">Installing the SDK</a>.
+
+<h3>SDK Add-Ons</h3>
+
+<p>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. </p>
+
+<p>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.
+
+<p>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. </p>
+
+<h3>Android Virtual Devices (AVDs)</h3>
+
+<p>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:</p>
+<ul>
+<li>Targets that represent core Android platform versions. </li>
+<li>Targets that are SDK add-ons, which typically provide application access to
+one or more external libraries and/or a customized (but compliant) system image
+that can run in the emulator.
+</ul>
+
+<p>A new tool called "android" lets you discover what targets and AVDs are
+available to use.</p>
+
+<p>For more information about AVDs, see <a
+href="{@docRoot}guide/developing/tools/avd.html">Android Virtual Devices</a>
+
+<h3>Other Notes</h3>
+
+<p><strong>Maps External Library</strong></p>
+
+<p>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: </p>
+
+<p style="margin-left:2em;"><a
+href="http://code.google.com/android/add-ons/google-apis">http://code.google.com
+/android/add-ons/google-apis</a> </p>
+
+<p>For your convenience, the Google APIs add-on is included in the SDK. </p>
+
+<p>For information about how to register for a Maps API Key, see
+<a href="http://code.google.com/android/add-ons/google-apis/mapkey.html">
+Obtaining a Maps API Key</a>.</p>
+
+<p><strong>USB Drivers for Windows</strong></p>
+
+<p>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:</p>
+
+<ul>
+<li>USB driver for 32-bit XP and Vista</li>
+<li>USB driver for 64-bit Vista only</li>
+</ul>
+
+<p>The USB driver files are located in the
+<code><SDK>/usb_driver</code> directory. For details and
+installation instructions, see <a
+href="{@docRoot}guide/developing/device.html#setting-up">Setting Up a
+Device for Development</a>.</p>
+</p>
+
+<h3>Resolved Issues, Changes</h3>
+
+<p><strong>Media</strong></p>
+<ul>
+<li>Updated documentation for {@link android.media.SoundPool
+android.media.SoundPool}</li>
+<li>{@link android.webkit.WebView} objects no longer automatically save
+thumbnails. The {@link android.webkit.WebView#capturePicture() capturePicture()}
+method will need to be called manually.</li>
+</ul>
+
+<h3>Known Issues</h3>
+
+<p><strong>Sensor problems in Emulator</strong></p>
+
+<ul>
+<li>If your application uses the Sensor API and you are running it in the
+emulator on the Android 1.5 system image, you may experience problems. Your
+application may generate ANR messages or crash when using the sensors. The
+problem is being investigated.</li>
+</ul>
+
+<p><strong>Other</strong></p>
+
+<ul>
+<li>We regret to inform developers that Android 1.5 will not include support for
+the Zilog Z80 processor architecture.</li>
+</ul>
+
<h2 id="1.1_r1">Android 1.1 SDK, Release 1</h2>
-<p>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. </p>
+<p>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.
+</p>
-<p>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. </p>
+<p>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. </p>
-<p>For details about the Android 1.1 system image included in the SDK — including bug fixes, features, and API changes — please read the <a href="{@docRoot}sdk/android-1.1.html">Android 1.1 Version Notes</a>.</p>
+<p>For details about the Android 1.1 system image included in the SDK —
+including bug fixes, features, and API changes — please read the <a
+href="{@docRoot}sdk/android-1.1.html">Android 1.1 Version Notes</a>.</p>
<h3>App Versioning for Android 1.1</h3>
-<p>If you are using this SDK to build an application that is compatible <em>only</em> with Android-powered devices running the Android 1.1 platform, please note that you <strong>must</strong> set the the <code>android:minSdkVersion</code> attribute in the application's manifest to the API Level of Android 1.1 — "2".</p>
+<p>If you are using this SDK to build an application that is compatible
+<em>only</em> with Android-powered devices running the Android 1.1 platform,
+please note that you <strong>must</strong> set the the
+<code>android:minSdkVersion</code> attribute in the application's manifest to
+the API Level of Android 1.1 — "2".</p>
-<p>Specifically, you specify the <code>android:minSdkVersion</code> attribute in a <code><uses-sdk></code> element as a child of <code><manifest></code> in the manifest file. When set, the attribute looks like this: </p>
+<p>Specifically, you specify the <code>android:minSdkVersion</code> attribute in
+a <code><uses-sdk></code> element as a child of
+<code><manifest></code> in the manifest file. When set, the attribute
+looks like this: </p>
<pre><code><manifest>
...
</manifest></code>
</pre>
-<p>By setting <code>android:minSdkVersion</code> 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. </p>
+<p>By setting <code>android:minSdkVersion</code> 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. </p>
-<p>If your application uses APIs introduced in Android 1.1 but does not declare <code><uses-sdk minSdkVersion="2" /></code>, then it will run properly on Android 1.1 devices but <em>not</em> on Android 1.0 devices. </p>
+<p>If your application uses APIs introduced in Android 1.1 but does not declare
+<code><uses-sdk minSdkVersion="2" /></code>, then it will run properly on
+Android 1.1 devices but <em>not</em> on Android 1.0 devices. </p>
-<p>If your application does not use any new APIs introduced in Android 1.1, you can indicate Android 1.0 compatibility by removing <code>minSdkVersion</code> 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.</p>
+<p>If your application does not use any new APIs introduced in Android 1.1, you
+can indicate Android 1.0 compatibility by removing <code>minSdkVersion</code> 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.</p>
-<p>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.</p>
+<p>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.</p>
<h3>ADT Plugin Compatibility</h3>
<p>If you're installing the Android SDK for the first time, please see
the instructions in <a
-href="{@docRoot}sdk/1.1_r1/installing.html">Installing the SDK</a>.
+href="{@docRoot}sdk/1.5_r1/installing.html">Installing the SDK</a>.
<h3>Other Notes</h3>
</ul>
-
-
-
<h2 id="1.0_r2">Android 1.0 SDK, Release 2</h2>
<p>This SDK release includes the Android 1.0 platform and application API.
</tr>
<tr>
- <td style="background-color:#ffcccc;">0.8.0</td>
- <td style="background-color:#ffcccc;"><a href="http://dl-ssl.google.com/android/ADT-0.8.0.zip">ADT-0.8.0.zip</a></td>
- <td style="background-color:#ffcccc;">23 September 2008</td>
- <td style="background-color:#ffcccc;">Android 1.1 SDK, Release 1<br />Android 1.0 SDK, Release 1<br /></td>
- <td style="background-color:#ffcccc;">Required for users of Android 1.1 SDK, Release 1 and Android 1.0 SDK, Release 1<br /> </td>
+ <td style="background-color:#ffcccc;">0.9.0</td>
+ <td style="background-color:#ffcccc;"><a href="http://dl-ssl.google.com/android/ADT-0.9.0.zip">ADT-0.9.0.zip</a></td>
+ <td style="background-color:#ffcccc;"><nobr>27 April 2009</nobr></td>
+ <td style="background-color:#ffcccc;"><nobr>Android 1.5 SDK</td>
+ <td style="background-color:#ffcccc;"><nobr>Required for users of Android 1.5 SDK (and later releases)<br /> </td>
+ </tr>
+ <tr>
+ <td>0.8.0</td>
+ <td><a href="http://dl-ssl.google.com/android/ADT-0.8.0.zip">ADT-0.8.0.zip</a></td>
+ <td style="background-color:#ffcccc;"><nobr>23 September 2008</nobr></td>
+ <td style="background-color:#ffcccc;"><nobr>Android 1.1 SDK<br/>Android 1.0 SDK<br/></td>
+ <td style="background-color:#ffcccc;"><nobr>Required for users of Android 1.1 SDK and Android 1.0 SDK<br /> </td>
</tr>
<tr>
<td>0.7.1</td>
--- /dev/null
+page.title=Android 1.5 Platform Highlights
+sdk.version=1.5_r1
+@jd:body
+
+<p>
+<em>April 2009</em>
+</p>
+
+
+<p>The Android 1.5 platform introduces many new features for users and developers.
+The list below provides an overview of the changes. </p>
+
+<ul>
+<li><a href="#ui">UI Localizations</a>
+<li><a href="#perf">Resolved Issues</a>
+<li><a href="#features">Android 1.5 Platform Highlights</a>
+<li><a href="#apis">New APIs and manifest elements</a>
+</ul>
+
+<h2 id="ui">User interface refinements</h4>
+<ul>
+ <li>System-wide:
+ <ul>
+ <li>Refinement of all core UI elements</li>
+ <li>Animated window transitions (off by default)</li>
+ <li>Accelerometer-based application rotations</li>
+ </ul>
+ </li>
+ <li>UI polish for:
+ <ul>
+ <li>In-call experience</li>
+ <li>Contacts, Call log, and Favorites</li>
+ <li>SMS & MMS</li>
+ <li>Browser</li>
+ <li>Gmail</li>
+ <li>Calendar</li>
+ <li>Email</li>
+ <li>Camera & Gallery</li>
+ <li>Application management</li>
+ </ul>
+ </li>
+</ul>
+
+<h2 id="perf">Performance improvements</h2>
+
+<ul>
+<li>Faster Camera start-up and image capture</li>
+<li>Much faster acquisition of GPS location (powered by SUPL AGPS)</li>
+<li>Smoother page scrolling in Browser</li>
+<li>Speedier GMail conversation list scrolling</li>
+</ul>
+
+<h4 id="features">New features</h4>
+
+<ul>
+ <li>On-screen soft keyboard
+ <ul>
+ <li>Works in both portrait and landscape orientation</li>
+ <li>Support for user installation of 3rd party keyboards</li>
+ <li>User dictionary for custom words</li>
+ </ul>
+</li>
+
+<li>Home screen
+ <ul>
+ <li>Widgets
+ <ul>
+ <li>Bundled home screen widgets include: analog clock, calendar,
+ music player, picture frame, and search</li>
+ </ul></li>
+ <li>Live folders</li>
+ </ul>
+</li>
+
+<li>Camera & Gallery
+ <ul>
+ <li>Video recording</li>
+ <li>Video playback (MPEG-4 & 3GP formats)</li>
+ </ul>
+</li>
+
+<li>Bluetooth
+ <ul>
+ <li>Stereo Bluetooth support (A2DP and AVCRP profiles)</li>
+ <li>Auto-pairing</li>
+ <li>Improved handsfree experience</li>
+ </ul>
+</li>
+
+<li>Browser
+ <ul>
+ <li>Updated with latest Webkit browser & Squirrelfish Javascript engines</li>
+ <li>Copy 'n paste in browser</li>
+ <li>Search within a page</li>
+ <li>User-selectable text-encoding</li>
+ <li>UI changes include:
+ <ul>
+ <li>Unified Go and Search box</li>
+ <li>Tabbed bookmarks/history/most-visited screen</li>
+ </ul>
+ </li>
+ </ul>
+</li>
+
+<li>Contacts
+ <ul>
+ <li>Shows user picture for Favorites</li>
+ <li>Specific date/time stamp for events in call log</li>
+ <li>One-touch access to a contact card from call log event</li>
+ </ul>
+</li>
+
+<li>System
+<ul>
+ <li>New Linux kernel (version 2.6.27)</li>
+ <li>SD card filesystem auto-checking and repair</li>
+ <li>SIM Application Toolkit 1.0 </li>
+</ul>
+</li>
+
+<li>Google applications (not available in the Android 1.5 System Image that is
+included in the Android SDK)
+ <ul>
+ <li>View Google Talk friends' status in Contacts, SMS, MMS, GMail, and
+ Email applications</li>
+ <li>Batch actions such as archive, delete, and label on Gmail messages</li>
+ <li>Upload videos to Youtube</li>
+ <li>Upload photos on Picasa</li>
+ </ul>
+</li>
+</ul>
+
+<h4 id="apis">New APIs and manifest elements</h4>
+
+<ul>
+<li>UI framework
+ <ul>
+ <li>Framework for easier background/UI thread interaction</li>
+ <li>New {@link android.widget.SlidingDrawer SlidingDrawer} widget</li>
+ <li>New {@link android.widget.HorizontalScrollView HorizontalScrollview} widget</li>
+ </ul>
+</li>
+
+<li>AppWidget framework
+ <ul>
+ <li>APIs for creating secure home screen {@link android.appwidget app
+ widgets}. Also see the <a href="http://android-developers.blogspot.com/2009/04/introducing-home-screen-widgets-and.html">Introducing home screen widgets and the AppWidget
+ framework.</li>
+ <li>APIs for populating {@link android.provider.LiveFolders Live Folders}
+with custom content.</li>
+ </ul>
+</li>
+
+<li>Media framework
+ <ul>
+ <li>Raw audio recording and playback APIs</li>
+ <li>Interactive MIDI playback engine</li>
+ <li>{@link android.media.MediaRecorder Video Recording APIs} for developers (3GP format).</li>
+ <li>Video and photo sharing Intents</li>
+ <li>Media search Intent</li>
+ </ul>
+</li>
+
+<li>Input Method framework
+ <ul>
+ <li>{@link android.inputmethodservice.InputMethodService Input Method
+ Service} framework</li>
+ <li>Text-prediction engine</li>
+ <li>Ability to provide downloadable IMEs to users</li>
+ </ul>
+</li>
+
+<li>Application-defined hardware requirements
+ <p>Applications can now use a new element in their manifest files, <a
+href="{@docRoot}guide/topics/manifest/uses-configuration-element.html"><uses-
+configuration></a> 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
+<code><uses-configuration></code> element and allows the installation to
+continue only if the required hardware is present.</p>
+</li>
+
+<li>Speech recognition framework
+ <ul>
+ <li>Support for using speech recognition libraries via Intent. See {@link
+android.speech.RecognizerIntent Speech Recognition}.</li>
+ </ul>
+</li>
+
+<li>Misc API additions
+ <ul>
+ <li>LocationManager - Applications can get location change updates via
+ Intent</li>
+ <li>WebView - Touch start/end/move/cancel DOM event support</li>
+ <li>Redesigned {@link android.hardware.SensorManager Sensor Manager
+ APIs}</li>
+ <li>GLSurfaceView - convenience framework for creating OpenGL
+ applications</li>
+ <li>Broadcast Intent for app update install succeeded - for smoother app
+ upgrade experience</li>
+ </ul>
+</li>
+</ul>
<em>API Level:</em> <strong>3</strong></p>
-<p>Please see <a href="{@docRoot}sdk/preview/index.html">Download the Android 1.5 Early Look SDK</a> for more information. </p>
+<p>This document provides version notes for the Android 1.5 system image included in the SDK. </p>
+
+<ul>
+<li><a href="#overview">Overview</a>
+<li><a href="#overview">External Libraries</a>
+<li><a href="#comp">Device Compatibility</a>
+<li><a href="#apps">Built-in Applications</a>
+<li><a href="#locs">UI Localizations</a>
+<!-- <li><a href="#resolved-issues">Resolved Issues</a> -->
+<li><a href="#features">Android 1.5 Platform Highlights</a>
+<li><a href="#api-changes">API Changes</a>
+</ul>
+
+<h2 id="overview">Overview</h2>
+
+<p>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.</p>
+
+<p>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 — <strong>3</strong> — 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.</p>
+
+<p>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 <code>minSdkVersion</code> 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
+<code>minSdkVersion</code> and allows the install only
+if the referenced integer is less than or equal to the API Level integer stored
+in the system itself. </p>
+
+<p>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
+<code>minSdkVersion</code> attribute.
+
+<p>After compiling your application, you should make sure to test it on the
+platform specified in the application's <code>minSdkVersion</code> 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 <a href="{@docRoot}guide/developing/tools/avd.html">Android Virtual
+Devices</a>. If you are using a physical device for testing, ensure that you
+know the API Level of the Android platform it runs.</p>
+
+<p>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 <strong><span
+style="color:red;">must</span></strong> set the
+<code>android:minSdkVersion</code> attribute in the application's manifest to
+"3". </p>
+
+<p>Specifically, you define the <code>android:minSdkVersion</code>
+attribute in a <code><uses-sdk></code> element as a child of
+<code><manifest></code> in the manifest file. When set, the
+attribute looks like this: </p>
+
+<pre><manifest>
+ ...
+ <uses-sdk minSdkVersion="3" />
+ ...
+</manifest></pre>
+
+<p>By setting <code>android:minSdkVersion</code> 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 <a href="#apichange">APIs or system features
+introduced in Android 1.5</a>. </p>
+
+<p>If your application uses APIs introduced in Android 1.5 but does not
+declare <code><uses-sdk minSdkVersion="3" /></code>, then it will
+run properly on Android 1.5 devices but <em>not</em> 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.</p>
+
+<p>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. </p>
+
+<p>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
+<code>minSdkVeresion</code> value.</p>
+
+<h2 id="apps">Built-in Applications</h2>
+
+<p>The system image includes these built-in applications:</p>
+ <ul>
+ <li>Alarm Clock</li>
+ <li>Browser</li>
+ <li>Calculator</li>
+ <li>Camcorder</li>
+ <li>Camera</li>
+ <li>Contacts</li>
+ <li>Custom Locale (developer app)</li>
+ <li>Dev Tools (developer app)</li>
+ <li>Dialer</li>
+ <li>Email</li>
+ <li>Gallery</li>
+ <li>Messaging</li>
+ <li>Music</li>
+ <li>Settings</li>
+ <li>Spare Parts (developer app)</li>
+ </ul>
+
+<h2 id="locs">Locales</h2>
+
+<p>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
+<em>language</em>_<em>country/region</em> locale descriptor).</p>
+
+<div class="g-unit g-first" style="whitespace:nowrap;width:35%;">
+<ul>
+<li>Chinese, PRC (zh_CN)</li>
+<li>Chinese, Taiwan (zh_TW)</li>
+<li>Czech (cs_CZ)</li>
+<li>Dutch, Netherlands (nl_NL)</li>
+<li>Dutch, Belgium (nl_BE)</li>
+<li>English, US (en_US)</li>
+<li>English, Britain (en_GB)</li>
+<li>English, Canada(en_CA)</li>
+<li>English, Australia (en_AU)</li>
+<li>English, New Zealand (en_NZ)</li>
+<li>English, Singapore(en_SG)</li>
+<li>French, France (fr_FR)</li>
+</div>
+<div class="g-unit" style="whitespace:nowrap;">
+<li>French, Belgium (fr_BE)</li>
+<li>French, Canada (fr_CA)</li>
+<li>French, Switzerland (fr_CH)</li>
+<li>German, Germany (de_DE)</li>
+<li>German, Austria(de_AT)</li>
+<li>German, Switzerland (de_CH)</li>
+<li>German, Liechtenstein (de_LI)</li>
+<li>Italian, Italy (it_IT)</li>
+<li>Italian, Switzerland (it_CH)</li>
+<li>Japanese (ja_JP)</li>
+<li>Korean (ko_KR)</li>
+<li>Polish (pl_PL)</li>
+<li>Russian (ru_RU)</li>
+<li>Spanish (es_ES)</li>
+</ul>
+</div>
+
+<p>Localized UI strings match the locales that are displayable in
+the emulator, accessible through the device Settings application.</p>
+
+<!--
+<h2 id="resolved-issues">Resolved Issues</h2>
+<ul>
+<li><font color="red"><strong></strong></font></li>
+</ul>
+-->
+
+<h2 id="features">New Features</h2>
+
+<p>For a list of new system features, see the <a
+href="{@docRoot}sdk/android-1.5-highlights.html">Android 1.5 Platform
+Highlights</a> document.</p>
+
+<h2 id="api-changes">API Changes</h2>
+
+<h3>Overview</strong></h3>
+
+<ul>
+ <li>UI framework</li>
+ <ul>
+ <li>Framework for easier background/UI thread interaction</li>
+ <li>New SlidingDrawer widget</li>
+ <li>Horizontal ScrollView widget</li>
+ </ul>
+
+ <li>Home Screen framework</li>
+ <ul>
+ <li>APIs for creating secure home screen widgets</li>
+ <li>APIs for populating live folders with custom content</li>
+ </ul>
+
+ <li>Media framework</li>
+ <ul>
+ <li>Raw audio recording and playback APIs</li>
+ <li>Interactive MIDI playback engine</li>
+ <li>Video recording APIs for developers (3GP format)</li>
+ <li>Video and photo sharing Intents</li>
+ <li>Media search Intent</li>
+ </ul>
+ <li>Input Method framework </li>
+ <ul>
+ <li>Text prediction engine</li>
+ <li>Ability to provide downloadable IMEs to users</li>
+ </ul>
+<li>Application-defined hardware requirements
+<p>Applications can now use a new element in their manifest files, <a
+href="{@docRoot}guide/topics/manifest/uses-configuration-element.html">
+<uses-configuration></a> 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
+<code><uses-configuration></code> element and allows the installation to
+continue only if the required hardware is present.</p></li>
+ <li>Speech recognition framework</li>
+ <ul>
+ <li>Support for using speech recognition libraries via Intent</li>
+ </ul>
+ <li>Misc API additions</li>
+ <ul>
+ <li> LocationManager - Applications can get location change updates via
+Intent</li>
+ <li>WebView - Touch start/end/move/cancel DOM event support</li>
+ <li>SensorManager - redesigned sensor APIs</li>
+ <li>GLSurfaceView - convenience framework for creating OpenGL
+applications</li>
+ <li>Broadcast Intent for app update install succeeded - for smoother app
+upgrade experience</li>
+ </ul>
+
+</ul>
+
+<h3>API Change Details</h3>
+
+<p>For a detailed view of API changes in this platform (API Level 3), see the <a
+href="{@docRoot}sdk/api_diff/3/changes.html">API Differences Report</a>.</p>
<ul>
<li><?cs
if:android.whichdoc != "online" ?>
- <h2>Android 1.5 SDK, r1</h2><?cs
+ <h2>Android <?cs var:sdk.version ?> SDK, r<?cs var:sdk.rel.id ?></h2><?cs
else ?>
<h2>Current SDK Release</h2><?cs
/if ?>
<ul><?cs
if:android.whichdoc == "online" ?>
- <li><a href="<?cs var:toroot ?>sdk/1.1_r1/index.html">Download</a></li><?cs
+ <li><a href="<?cs var:toroot ?>sdk/<?cs var:sdk.current ?>/index.html">Download</a></li><?cs
/if ?>
- <li><a href="<?cs var:toroot ?>sdk/1.1_r1/installing.html">Installing</a></li>
- <li><a href="<?cs var:toroot ?>sdk/1.1_r1/upgrading.html">Upgrading</a></li>
- <li><a href="<?cs var:toroot ?>sdk/1.1_r1/requirements.html">System Requirements</a></li>
+ <li><a href="<?cs var:toroot ?>sdk/<?cs var:sdk.current ?>/installing.html">Installing</a></li>
+ <li><a href="<?cs var:toroot ?>sdk/<?cs var:sdk.current ?>/upgrading.html">Upgrading</a></li>
+ <li><a href="<?cs var:toroot ?>sdk/<?cs var:sdk.current ?>/requirements.html">System Requirements</a></li>
</ul>
<ul>
<li><a href="<?cs var:toroot ?>sdk/terms.html">SDK Terms and Conditions</a></li>
</ul><?cs
if:android.whichdoc == "online" ?>
<li>
- <h2>Android System Images</h2>
+ <h2>System Image Version Notes</h2>
<ul>
<li><a href="<?cs var:toroot ?>sdk/android-1.5.html">Android 1.5 Version Notes</a></li>
<li><a href="<?cs var:toroot ?>sdk/android-1.1.html">Android 1.1 Version Notes</a></li>
<li>
<h2>Previous SDK Releases</h2>
<ul>
- <li><a href="<?cs var:toroot ?>sdk/1.0_r2/index.html">Android 1.0 SDK, release 2</a></li>
- <li><a href="<?cs var:toroot ?>sdk/1.0_r1/index.html">Android 1.0 SDK, release 1</a></li>
+ <li><a href="<?cs var:toroot ?>sdk/1.1_r1/index.html">Android 1.1 SDK, r1</a></li>
+ <li><a href="<?cs var:toroot ?>sdk/1.0_r2/index.html">Android 1.0 SDK, r2</a></li>
+ <li><a href="<?cs var:toroot ?>sdk/1.0_r1/index.html">Android 1.0 SDK, r1</a></li>
<li><a href="<?cs var:toroot ?>sdk/older_releases.html">Older Releases</a></li>
</ul>
</li><?cs
OSDN Git Service
