From 3f9de8b6caa3fe9119b363c64e79d13bb72aec76 Mon Sep 17 00:00:00 2001 From: Dirk Dougherty Date: Fri, 22 May 2009 16:04:18 -0700 Subject: AI 149211: Doc updates for Android 1.5 SDK, r2. BUG=1790234 Automated import of CL 149211 --- docs/html/sdk/1.5_r2/index.jd | 87 +++++++ docs/html/sdk/1.5_r2/installing.jd | 332 +++++++++++++++++++++++++++ docs/html/sdk/1.5_r2/requirements.jd | 39 ++++ docs/html/sdk/1.5_r2/upgrading.jd | 395 ++++++++++++++++++++++++++++++++ docs/html/sdk/RELEASENOTES.jd | 12 +- docs/html/sdk/android-1.5-highlights.jd | 1 - docs/html/sdk/older_releases.jd | 107 +++++---- docs/html/sdk/preview/features.html | 21 +- docs/html/sdk/sdk_toc.cs | 9 +- 9 files changed, 932 insertions(+), 71 deletions(-) create mode 100644 docs/html/sdk/1.5_r2/index.jd create mode 100644 docs/html/sdk/1.5_r2/installing.jd create mode 100644 docs/html/sdk/1.5_r2/requirements.jd create mode 100644 docs/html/sdk/1.5_r2/upgrading.jd (limited to 'docs/html/sdk') diff --git a/docs/html/sdk/1.5_r2/index.jd b/docs/html/sdk/1.5_r2/index.jd new file mode 100644 index 000000000000..15342a433992 --- /dev/null +++ b/docs/html/sdk/1.5_r2/index.jd @@ -0,0 +1,87 @@ +sdk.version=1.5 +sdk.rel.id=2 +sdk.date=May 2009 + +sdk.win_download=android-sdk-windows-1.5_r2.zip +sdk.win_bytes=178346828 +sdk.win_checksum=ba54ac6bda45921d442b74b6de6ff6a9 + +sdk.mac_download=android-sdk-mac_x86-1.5_r2.zip +sdk.mac_bytes=169945128 +sdk.mac_checksum=f4e06a5194410243f213d0177713d6c9 + +sdk.linux_download=android-sdk-linux_x86-1.5_r2.zip +sdk.linux_bytes=165035130 +sdk.linux_checksum=1d3c3d099e95a31c43a7b3e6ae307ed3 + +page.title=Android 1.5 SDK, Release 2 +@jd:body + +

For more information on this SDK release, read the +Release Notes.

+ +

SDK Contents

+ +

Development tools

+ +

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 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. + +

Android Platforms

+ +

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.

+ + + + + + + + + + + + + + + + + + +
PlatformAPI LevelNotesDescription
Android 1.53Version NotesIncludes 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).
Android 1.12Version NotesIncludes 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).
+ +

SDK Add-Ons

+ +

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.

+ + + + + + + + + + + +
Add-OnAPI LevelNotesDescription
Google APIs3 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.
+ +

Sample Code and Applications

+ +

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.

+ +

Documentation

+ +

The SDK package includes a full set of local documentation. To view it, open the <sdk>/documentation.html 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.

+ +

The most current documentation is always available on the Android Developers site:

+ +

http://developer.android.com/

+ diff --git a/docs/html/sdk/1.5_r2/installing.jd b/docs/html/sdk/1.5_r2/installing.jd new file mode 100644 index 000000000000..69b2c1bef533 --- /dev/null +++ b/docs/html/sdk/1.5_r2/installing.jd @@ -0,0 +1,332 @@ +sdk.version=1.5 +sdk.rel.id=2 +sdk.date=April 2009 + +page.title=Installing the Android SDK +@jd:body + + +

This page describes how to install the Android SDK and set up your +development environment. If you haven't downloaded the SDK, you can +do so from the +Download page. Once you've downloaded +the SDK, return here.

+ +

If you encounter any problems during installation, see the +Installation Notes at the bottom of +this page.

+ +

Upgrading?

+

If you have already developed applications using an earlier version +of the SDK, please read +Upgrading the +SDK, instead. +

+ + +

Preparing for Installation

+ +

Before you begin, take a moment to confirm that your development machine meets the +System Requirements. +

+ +

If you will be developing on Eclipse with the Android Development +Tools (ADT) Plugin — the recommended path if you are new to +Android — make sure that you have a suitable version of Eclipse +installed on your computer (3.3 or newer). If you need to install Eclipse, you can +download it from this location:

+ +

http://www.eclipse.org/downloads/

+ +

A Java or RCP version of Eclipse is recommended.

+ +

Installing the SDK

+ +

After downloading the SDK, unpack the .zip archive to a suitable location on your machine. +By default, the SDK files are unpacked into a directory named +android_sdk_<platform>_<release>. +The directory contains a local copy of the documentation (accessible by opening +documentation.html in your browser) and the subdirectories +tools/, add-ons/, platforms/, and others. Inside +each subdirectory of platforms/ you'll find samples/, which includes +code samples that are specific to each version of the platform.

+ +

Make a note of the name and location of the unpacked SDK directory on your system — you +will need to refer to the SDK directory later, when setting up the Android plugin or when +using the SDK tools.

+ +

Optionally, you may want to add the location of the SDK's primary tools directory +to your system PATH. The primary tools/ directory is located at the root of the +SDK folder. Adding tools to your path lets you run Android Debug Bridge (adb) and +the other command line tools without +needing to supply the full path to the tools directory.

+ + +

Note that, if you update your SDK in the future, you +should remember to update your PATH settings to point to the new location, if different.

+ +

If you will be using the Eclipse IDE as your development environment, +the next section describes how to install the Android Development Tools plugin and set up Eclipse. +If you choose not to use Eclipse, you can +develop Android applications in an IDE of your choice and then compile, debug and deploy using +the tools included in the SDK (skip to Next Steps).

+ + +

Installing the ADT Plugin for Eclipse

+ +

Android offers a custom plugin for the Eclipse IDE, called Android +Development Tools (ADT), that is designed to give you a powerful, +integrated environment in which to build Android applications. It +extends the capabilites of Eclipse to let you quickly set up new Android +projects, create an application UI, add components based on the Android +Framework API, debug your applications using the Android SDK tools, and even export +signed (or unsigned) APKs in order to distribute your application.

+ +

In general, using Eclipse with ADT is a highly recommended +approach to Android development and is the fastest way to get started. +(If you prefer to work in an IDE other than Eclipse, +you do not need to install Eclipse or ADT, instead, you can directly +use the SDK tools to build and debug your application.)

+ +

Once you have Eclipse installed, as described in Preparing for +Installation, follow the steps below to +download the ADT plugin and install it in your respective Eclipse +environment.

+ + + + + + + +
Eclipse 3.3 (Europa)Eclipse 3.4 (Ganymede)
+ +
    +
  1. Start Eclipse, then select Help > Software Updates +> Find and Install....
    2. +
  2. In the dialog that appears, select Search for new features to install +and click Next.
    3. +
  3. Click New Remote Site.
    4. +
  4. In the resulting dialog box, enter a name for the remote site (e.g. "Android Plugin") and + enter the URL: + 
    https://dl-ssl.google.com/android/eclipse/
    +

    If you have trouble aqcuiring the plugin, try using "http" in the URL, + instead of "https" (https is preferred for security reasons).

    +

    Click OK.

    5. +
  5. You should now see the new site added to the search list (and checked). + Click Finish.
    6. +
  6. In the subsequent Search Results dialog box, select the checkbox for the + "Android Plugin". + This will select the nested tools: "Android DDMS" and "Android Development Tools". + Click Next.
    7. +
  7. Read and accept the license agreement, then click Next.
    8. +
  8. On the following Installation window, click Finish.
    9. +
  9. The ADT plugin is not digitally signed. Accept the installation anyway + by clicking Install All.
    10. +
  10. Restart Eclipse.
    11. +
+ +		 + + +
    +
  1. Start Eclipse, then select Help > Software Updates....
    2. +
  2. In the dialog that appears, click the Available Software tab.
    3. +
  3. Click Add Site...
    4. +
  4. Enter the Location: + 
    https://dl-ssl.google.com/android/eclipse/
    +

    If you have trouble aqcuiring the plugin, try using "http" in the Location URL, + instead of "https" (https is preferred for security reasons).

    +

    Click OK.

    5. +
  5. Back in the Available Software view, you should see the plugin listed by the URL, + with "Developer Tools" nested within it. Select the checkbox next to + Developer Tools and click Install...
    6. +
  6. On the subsequent Install window, "Android DDMS" and "Android Development Tools" + should both be checked. Click Next.
    7. +
  7. Read and accept the license agreement, then click Finish.
    8. +
  8. Restart Eclipse.
    9. +
+ +
+ +

Now modify your Eclipse preferences to point to the Android SDK directory:

+
    +
  1. Select Window > Preferences... to open the Preferences + panel (Mac: Eclipse > Preferences).
    2. +
  2. Select Android from the left panel.
    3. +
  3. For the SDK Location in the main panel, click Browse... and +locate your downloaded SDK directory.
    4. +
  4. Click Apply, then OK.
    5. +
+ +

Done! If you haven't encountered any problems, then you're ready to +begin developing Android applications. See the +Next Steps section for suggestions on how to start.

+ + +

Troubleshooting ADT Installation

+

+If you are having trouble downloading the ADT plugin after following the steps above, here are +some suggestions:

+ + +

+If you are still unable to use Eclipse to download the ADT plugin as a remote update site, you +can download the ADT zip file to your local machine and manually install the it: +

+
    +
  1. Download the ADT zip file (do not unpack it).
    2. +
  2. Follow steps 1 and 2 in the default install instructions (above).
    3. +
  3. In Eclipse 3.3, click New Archive Site....
    + In Eclipse 3.4, click Add Site..., then Archive...
    4. +
  4. Browse and select the downloaded zip file.
    5. +
  5. Follow the remaining procedures, above, starting from steps 5.
    6. +
+

To update your plugin once you've installed using the zip file, you will have to +follow these steps again instead of the default update instructions.

+ +

Other install errors

+ +

Note that there are features of ADT that require some optional +Eclipse components (for example, WST). If you encounter an error when +installing ADT, your Eclipse installion might not include these components. +For information about how to quickly add the necessary components to your +Eclipse installation, see the troubleshooting topic +ADT +Installation Error: "requires plug-in org.eclipse.wst.sse.ui".

+ +

For Linux users

+

If you encounter this error when installing the ADT Plugin for Eclipse: +

+An error occurred during provisioning.
+Cannot connect to keystore.
+JKS
+

+...then your development machine lacks a suitable Java VM. Installing Sun +Java 6 will resolve this issue and you can then reinstall the ADT +Plugin.

+ + +

Next Steps

+

Once you have completed installation, you are ready to +begin developing applications. Here are a few ways you can get started:

+ +

Learn about Android

+ + +

Explore the SDK

+ + +

Explore some code

+ + +

Visit the Android developer groups

+ + + +

Installation Notes

+ +

Ubuntu Linux Notes

+ + + +

Other Linux Notes

+ + + + + diff --git a/docs/html/sdk/1.5_r2/requirements.jd b/docs/html/sdk/1.5_r2/requirements.jd new file mode 100644 index 000000000000..4ed38a741261 --- /dev/null +++ b/docs/html/sdk/1.5_r2/requirements.jd @@ -0,0 +1,39 @@ +page.title=System Requirements +@jd:body + +

The sections below describe the system and software requirements for developing Android applications using the Android SDK tools included in Android SDK, Release .

+ +

Supported Operating Systems

+ + +

Supported Development Environments

+ + +

Note: If JDK is already installed on your development computer, please take a moment to make sure that it meets the version requirements listed above. In +particular, note that some Linux distributions may include JDK 1.4 or Gnu Compiler for Java, both of which are not supported for Android development.

\ No newline at end of file diff --git a/docs/html/sdk/1.5_r2/upgrading.jd b/docs/html/sdk/1.5_r2/upgrading.jd new file mode 100644 index 000000000000..bb5fc60e67f8 --- /dev/null +++ b/docs/html/sdk/1.5_r2/upgrading.jd @@ -0,0 +1,395 @@ +page.title=Upgrading the SDK +sdk.version=1.5_r2 +@jd:body + + +
+
+ +

Upgrading the SDK

+
    +
  • The Android 1.5 SDK uses a new project structure and a new ADT plugin (ADT 0.9).
    • +
  • To move existing projects into the SDK, you must make some minor changes in your + development environment.
    • +
  • The new ADT plugin (ADT 0.9) is not compatible with projects created in previous SDKs.
    • +
  • You need to uninstall your existing ADT plugin, before installing ADT 0.9.
    • +
+ +

In this document

+
    +
  1. Install the SDK
    2. +
  2. Update Your Eclipse ADT Plugin
    3. +
  3. Update Your Projects +
      +
    1. Eclipse Users
      2. +
    2. Ant Users
      3. +
    +
    4. +
  4. Migrate Your Applications +
    1. Future-proof your apps
    +
    5. +
+ +

Migrating references

+
    +
  1. Android 1.5 API Differences
    2. +
  2. Future-Proofing +Your Apps »
    3. +
  3. UI +framework changes in Android 1.5 »
    4. +
+ +
+
+ +

This document describes how to move your development environment and existing +Android applications from an Android 1.0 or 1.1 SDK to the Android 1.5 SDK. +If you are migrating applications from an SDK older than 1.0, please also read the upgrading +document available in the Android 1.0 SDK package.

+ +

There are several compelling reasons to upgrade, such as new SDK tools +that make developing more efficient and new APIs that allow you to expand the feature-set +of your applications. However, even if you or your applications don't require these enhancements, +it's important that you upgrade to ensure that your applications run properly on the +Android 1.5 platform.

+ +

The Android 1.5 platform will soon be deployable to devices around the world. +If you have already released Android applications to the public, you should +test the forward-compatibility of your applications on the latest version of the platform +as soon as possible. It's unlikely that you'll encounter breakage in your applications, but +in the interest of maintaining the best user experience, you should take no risks. +So, please install the new Android SDK and test your applications on Android 1.5.

+ +

For more information on new SDK features and system changes, +see the Android 1.5 Version Notes.

+ + +

Install the SDK

+ +

If you haven't yet downloaded the SDK, download from here +and unpack it into a safe location.

+ +

Before you begin: +If you had previously setup your PATH variable to point to the SDK tools directory, +then you need to update it to point to the new SDK. For example, for a +.bashrc or .bash_profile file:

+
export PATH=$PATH:<your_sdk_dir>/tools
+ +

If you don't use Eclipse for development, +skip to Update Your Projects.

+ + +

Update Your Eclipse ADT Plugin

+ +

If you installed ADT-0.9_pre with the early look 1.5 SDK, there have been +additional changes, so please continue with this guide and update to the final ADT 0.9.

+ +

A new ADT plugin (version 0.9) is required for the Android 1.5 SDK. +Because the component structure has been changed since Android 1.1, +the Android 1.5 SDK does not work with ADT 0.8 (or older) and previously installed SDKs will not +work with ADT 0.9. However, the Android 1.5 SDK includes an Android 1.1 SDK image that you +can build against while using ADT 0.9.

+ +

For information about using different system images (such as Android 1.1) +while running this SDK, see Developing +In Eclipse, with ADT or In +Other IDEs, as appropriate for your development environment.

+ +

In order to upgrade your Eclipse IDE to use the new 0.9 ADT, follow the steps below +for your respective version of Eclipse.

+ +

Uninstall your previous ADT plugin

+ +

You must uninstall your existing ADT plugin (0.8 or older). If you do not uninstall it, +you will get a conflict with the Android Editors when installing the new ADT. +(If you have already installed ADT-0.9_pre with the early look 1.5 SDK, you can skip this +uninstall procedure and continue to Install the 0.9 ADT plugin).

+ + + + + + + +
Eclipse 3.3 (Europa)Eclipse 3.4 (Ganymede)
+ +
    +
  1. Select Help > Software Updates > + Manage Configuration.
    2. +
  2. Expand the list in the left panel to reveal the installed tools.
    3. +
  3. Right-click "Android Editors" and click Uninstall. Click OK + to confirm.
    4. +
  4. Restart Eclipse. +

    (Do not uninstall "Android Development Tools".)

    5. +
+		 + +
    +
  1. Select Help > Software Updates.
    2. +
  2. Select the Installed Software tab.
    3. +
  3. Select "Android Editors". Click Uninstall.
    4. +
  4. In the next window, be sure "Android Editors" is checked, then click Finish + to uninstall.
    5. +
  5. Restart Eclipse. +

    (Do not uninstall "Android Development Tools".)

    6. +
+
+ + +

Install the 0.9 ADT plugin

+ +

Only install the new plugin once you've completed the procedure to +Uninstall your previous ADT plugin.

+ + + + + + + +
Eclipse 3.3 (Europa)Eclipse 3.4 (Ganymede)
+ +
    +
  1. Select Help > Software Updates > + Find and Install.
    2. +
  2. Select Search for new features to install.
    3. +
  3. Select the Android plugin entry by checking the box next to it, + then click Finish. +

    (Your original entry for the plugin should still be here. If not, see the guide + to Installing the ADT Plugin.) +

    4. +
  4. In the results, expand the entry for the Android plugin and + be sure that "Developer Tools" is checked, then click Next. + (This will install "Android DDMS" and "Android Development Tools".)
    5. +
  5. Read and accept the license agreement, then click Next. +
  6. In the next window, click Finish to start installation.
    7. +
  7. The ADT plugin is not digitally signed. Accept the installation anyway by clicking + Install All.
    8. +
  8. Restart Eclipse.
    9. +
+		 + +
    +
  1. Select Help > Software Updates.
    2. +
  2. Select the Available Software tab.
    3. +
  3. Expand the entry for the Andriod plugin (may be listed as the location URL) + and select "Developer Tools" by checking the box next to it, then click + Install.
    4. +
  4. On the next window, "Android DDMS" and "Android Development Tools" + should both be checked. Click Finish.
    5. +
  5. Restart Eclipse.
    6. +
+
+ +

If you encounter problems, ensure your ADT is fully uninstalled and then +follow the guide to +Installing the ADT Plugin +for Eclipse.

+ +

Update your Eclipse SDK Preferences

+ +

The last step is to update your Eclipse preferences to point to the new SDK directory:

+
    +
  1. Select Window > Preferences to open the Preferences + panel (Mac: Eclipse > Preferences).
    2. +
  2. Select Android from the left panel.
    3. +
  3. For the SDK Location in the main panel, click Browse + and locate your SDK directory.
    4. +
  4. Click Apply, then OK.
    5. +
+ + +

Update Your Projects

+ +

You will now need to update any and all Android projects that you have +developed using a previous version of the Android SDK.

+ + +

Eclipse users

+ +

If you use Eclipse to develop applications, use the following procedure to +update each project:

+ +
    +
  1. Right-click on the individual project (in the Package Explorer) + and select Properties.
    2. +
  2. In the properties, open the Android panel and select a "build target" to compile + against. This SDK offers the Android 1.1 and Android 1.5 platforms to choose from. When + you are initially updating your projects to the new SDK, we recommend that you select a build + target with the Android 1.1 platform. Click Apply, then + OK.
    3. +
+ +

The new plugin creates a gen/ folder in your project, in which it puts the +R.java file +and all automatically generated AIDL java files. If you get an error such as +The type R is already defined, +then you probably need to delete your old R.java or your old auto-generated +AIDL Java files in the src/ folder. +(This does not apply to your own hand-crafted parcelable AIDL java files.)

+ +

Note that, with the Android 1.5 SDK, there is a new process for running +applications in the Android Emulator. +Specifically, you must create an Android Virtual Device (AVD) before you can launch an instance +of the Emulator. Before attempting to run your applications with the new SDK, +please continue with the section below to +Migrate Your Applications.

+ + +

Ant users

+ +

If you build your projects using the Ant tool (rather than with Eclipse), note the +following changes with the new SDK tools.

+ +

build.xml has changed

+ +

You must re-create your build.xml file.

+ +

If you had customized your build.xml, first make a copy of it:

+ +
+$ cd my-project
+$ cp build.xml build.xml.old
+
+ +

Now use the new android tool (located in your_sdk/tools/) +to create a new build.xml that references +a specific platform target:

+ +
$ android update project --path /path/to/my-project --target 1
+ +

The "target" corresponds to an Android platform library (including any add-ons, such as +Google APIs) that you would like to build your project against. You can view a list of available +targets (and their corresponding integer ID) with the command, android list targets. +When you are initially updating your projects to the new SDK, we recommend that you select the +first target ("1"), which uses the Android 1.1 platform library.

+ +

A gen/ folder will be created the first time you build and your R.java and +your AIDL Java files will be generated in here. You must remove +the old R.java and old auto-generated AIDL java files from the +src/ folder. (This +does not apply to your own hand-crafted parcelabe AIDL java files.)

+ +

Note: The "activitycreator" tool has been replaced +by the new "android" tool. For information on creating new projects with the android tool, +see the documentation about Developing +In Other IDEs.

+ +

Note that, with the Android 1.5 SDK, there is a new process for running +applications in the Android Emulator. +Specifically, you must create an Android Virtual Device (AVD) before you can launch an instance +of the Emulator. Before attempting to run your applications with the new SDK, +please continue with the section below to +Migrate Your Applications.

+ + +

Migrate Your Applications

+ +

After you have completed the process above to Update Your +Projects, you are strongly encouraged to run each of your applications in an instance +of the emulator running the Android 1.5 system image. It's possible (however, unlikely) +that you'll encounter some breakage in your application when you run your applications on +the Android 1.5 system image. Whether you believe your application will be affected by +platform changes or not, it's very important that you test the application's +forward-compatibility on Android 1.5.

+ +

To test forward-compatibility, simply run your existing application (as-is) on an Android +Emulator that's running the Android 1.5 system image. The following procedure will guide +you through the process to running your existing applications on an emulator. Please read +the following guide completely before you begin.

+ +

To test your application on an emulator running Android 1.5:

+
    +
  1. Update Your Project (you should have done this + already, in the section above).
    2. +
  2. Run your existing project, as-is, on an emulator running the Android 1.5 system image. +

    As mentioned in the guide to Update Your Projects, + you should have selected a "build + target" of "1", which compiles your application against the Android 1.1 system image, so there + should be no new errors in your code.

    +

    Eclipse users: follow the + Eclipse guide to + Running Your Application.

    +

    Ant users: follow the + Ant guide to + Running Your Application +

    During the procedure to Running Your Application, select a "deployment target" + for the AVD that includes the Android 1.5 platform. + If your application utilizes the Google Maps APIs (i.e., + MapView), be certain to select a target that includes the Google APIs.

    +

    Once you complete the procedures to run your application in your respective environment, + linked above, return here.

    +
    3. +
  3. With your application running in the emulator, perform all regular testing on the application + to ensure that it functions normally (in both landscape and portrait orientations).
    4. +
+ +

Chances are, your application runs just fine on the Android 1.5 platform — +new devices will be able to safely install and run your application and +current users who update their devices will be able to continue using your application as usual. +However, if something doesn't work the way you expect, then you might need to revisit +your project and make any necessary changes to your code.

+ +

You can check for code breakages caused by API changes by opening your project +in Eclipse, changing the "build target" to one using the Android 1.5 platform, +and see where the ADT identifies errors in your code.

+ + +

Future-proof your apps

+ +

There have been several API additions made for this release, but there have been +very few actual API changes. Only a couple (relatively unused) elements +have been removed and a few have been deprecated, so your applications written with the +Android 1.1 system library should work just fine. However, +your application is more likely to encounter problems on Android 1.5 +if it performs any of the following:

+ + + +

Please read our blog post on Future-Proofing +Your Apps for more information on the issues mentioned above.

+ +

For information +about other changes made to Android 1.5, refer to the following documents:

+ + +

If you have additional trouble updating your code, visit the +Android Developers Group +to seek help from other Android developers.

diff --git a/docs/html/sdk/RELEASENOTES.jd b/docs/html/sdk/RELEASENOTES.jd index c44cef3a55fb..f3a1951f71fb 100644 --- a/docs/html/sdk/RELEASENOTES.jd +++ b/docs/html/sdk/RELEASENOTES.jd @@ -3,8 +3,16 @@ page.title=SDK Release Notes

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.

+page at http://developer.android.com/sdk/RELEASENOTES.html.

+ + +

Android 1.5 SDK, Release 2

+ +

This SDK release provides the same developer tools as the Android 1.5 SDK, +Release 1, but provides an updated Android 1.5 system image that includes a +security patch for the issue described in the oCert advisory below:

+ +

http://www.ocert.org/advisories/ocert-2009-006.html

Android 1.5 SDK, Release 1

diff --git a/docs/html/sdk/android-1.5-highlights.jd b/docs/html/sdk/android-1.5-highlights.jd index e6c4f88e4d32..ff64e8c28cf9 100644 --- a/docs/html/sdk/android-1.5-highlights.jd +++ b/docs/html/sdk/android-1.5-highlights.jd @@ -1,5 +1,4 @@ page.title=Android 1.5 Platform Highlights -sdk.version=1.5_r1 @jd:body

diff --git a/docs/html/sdk/older_releases.jd b/docs/html/sdk/older_releases.jd index ff57a36ec392..3c2bbd403129 100644 --- a/docs/html/sdk/older_releases.jd +++ b/docs/html/sdk/older_releases.jd @@ -1,37 +1,67 @@ -page.title=Older Releases +page.title=Other SDK Releases @jd:body -

- NOTICE: -

The SDKs listed on this page are "early-look" versions that were released in +

This page provides a full list of older, obsolete SDK releases, including +non-current versions of active releases and "early look" versions that were +released before Android 1.0. The list is provided for informational purposes +only.

+ +

If you are just getting started developing on Android, make sure that you +are using the most current SDK available, +to ensure that your applications will be compatible with the latest +Android-powered devices.

+ +

Obsolete Releases

+ +

The table below lists Android SDK releases that have been superceded by an +active release and that are now obsolete. If you are using one of these +releases, please upgrade to the current SDK +release.

+ + + + + + + + + + + + + + + + + +
Release + Platform(s)Date + Description +
Android 1.5 SDK, Release 1Android 1.5
Android 1.1		April 2009Replaced by Android 1.5 SDK, Release 2. Release notes
Android 1.0 SDK, Release 1Android 1.0September 2008Replaced by Android 1.0 SDK, Release 2. Release notes
+ +

Non-Compatible Releases

+ + +

The SDKs listed below are "early-look" versions that were released in the year preceding the full release of Android 1.0 in September 2008. Because these early-look SDKs were released before the Android 1.0 API specification was finalized, they do not provide a compliant Android execution environment. Consequently, applications that you develop in these SDKs will not be able to run on any Android-powered devices.

-

If you have an older application that you built in one of the early-look SDKs, - you must migrate it to the Android - 1.0 SDK (or later release) before you will be able to deploy it to - an Android-powered device. To help with this migration, each SDK package below - provides information about API changes from the previous version. You can find - the migration information in the documentation included in each SDK package.

- -

If you are just getting started developing on Android, do not use one of these early-look - SDKs. Instead, develop using the most current - SDK release available, to ensure that your applications will be compatible - with Android-powered devices.

-
- +

If you have an older application that you built in one of the early-look +SDKs, you must migrate it to the Android 1.0 SDK (or later release) before you +will be able to deploy it to an Android-powered device. To help with this +migration, each SDK package below provides information about API changes from +the previous version. You can find the migration information in the +documentation included in each SDK package.

+ - - -

Android 0.9 SDK beta

-

August 18, 2008 - Release Notes

+

Android SDK m5-rc15

+

August 18, 2008 - Release Notes

- - + @@ -58,15 +88,11 @@ page.title=Older Releases
PlatformPackagePackage Size MD5 Checksum
- - - -

Version m5-rc15

+

Version m5-rc15

March 3, 2008 - Release Notes

- - + @@ -93,15 +119,11 @@ page.title=Older Releases
PlatformPackagePackage Size MD5 Checksum
- - - -

Version m5-rc14

+

Version m5-rc14

February 12, 2008 - Release Notes

- - + @@ -131,12 +153,11 @@ page.title=Older Releases -

Version m3-rc37a

+

Version m3-rc37a

December 14, 2007 - Release Notes

PlatformPackagePackage Size MD5 Checksum
- - + @@ -166,12 +187,11 @@ page.title=Older Releases -

Version m3-rc22a

+

Version m3-rc22a

November 16, 2007 - Release Notes

PlatformPackagePackage Size MD5 Checksum
- - + @@ -201,12 +221,11 @@ page.title=Older Releases -

Version m3-rc20a

+

Version m3-rc20a

November 12, 2007 - Release Notes

PlatformPackagePackage Size MD5 Checksum
- - + diff --git a/docs/html/sdk/preview/features.html b/docs/html/sdk/preview/features.html index 392c0895ec25..a2f085cdce34 100644 --- a/docs/html/sdk/preview/features.html +++ b/docs/html/sdk/preview/features.html @@ -133,10 +133,10 @@

  • Current SDK Release

    @@ -185,16 +184,6 @@ - - - diff --git a/docs/html/sdk/sdk_toc.cs b/docs/html/sdk/sdk_toc.cs index 4b55b56177ce..2079dd8a62f3 100644 --- a/docs/html/sdk/sdk_toc.cs +++ b/docs/html/sdk/sdk_toc.cs @@ -26,19 +26,12 @@
  • Android 1.1 Version Notes
    • -
  • -

    Native Development Tools

    - -

  • Previous SDK Releases

    • -- cgit v1.2.3-59-g8ed1b From 522ab34d3821dc760e10f4bdf3fbdb558c6a1d01 Mon Sep 17 00:00:00 2001 From: Dirk Dougherty Date: Tue, 26 May 2009 15:46:56 -0700 Subject: AI 149272: Mark 1.5r1 as a "non-current" release, with pointer to 1.5r2. BUG=1790234 Automated import of CL 149272 --- docs/html/sdk/1.5_r1/index.jd | 1 + 1 file changed, 1 insertion(+) (limited to 'docs/html/sdk') diff --git a/docs/html/sdk/1.5_r1/index.jd b/docs/html/sdk/1.5_r1/index.jd index 438ee4bb80ce..405f56ce960a 100644 --- a/docs/html/sdk/1.5_r1/index.jd +++ b/docs/html/sdk/1.5_r1/index.jd @@ -1,6 +1,7 @@ sdk.version=1.5 sdk.rel.id=1 sdk.date=April 2009 +sdk.not_latest_version=true sdk.win_download=android-sdk-windows-1.5_r1.zip sdk.win_bytes=176263368 -- cgit v1.2.3-59-g8ed1b
    PlatformPackagePackage Size MD5 Checksum