diff --git a/docs/html/distribute/googleplay/index.html b/docs/html/distribute/googleplay/index.html deleted file mode 100644 index 46a8ce2c3b676..0000000000000 --- a/docs/html/distribute/googleplay/index.html +++ /dev/null @@ -1,10 +0,0 @@ - - - -Redirecting... - - -

You should have been redirected. Please click here.

- - \ No newline at end of file diff --git a/docs/html/guide/practices/app-design/accessibility.html b/docs/html/guide/practices/app-design/accessibility.html deleted file mode 100644 index 0fa7b3213dd9b..0000000000000 --- a/docs/html/guide/practices/app-design/accessibility.html +++ /dev/null @@ -1,11 +0,0 @@ - - - -Redirecting... - - -

You should be redirected. Please click here.

- - \ No newline at end of file diff --git a/docs/html/guide/practices/ui_guidelines/icon_design_1.html b/docs/html/guide/practices/ui_guidelines/icon_design_1.html deleted file mode 100644 index 183facf18db81..0000000000000 --- a/docs/html/guide/practices/ui_guidelines/icon_design_1.html +++ /dev/null @@ -1,9 +0,0 @@ - - - -Redirecting... - - -click here if you are not redirected. - - diff --git a/docs/html/guide/topics/index.html b/docs/html/guide/topics/index.html deleted file mode 100644 index 4881acf44581b..0000000000000 --- a/docs/html/guide/topics/index.html +++ /dev/null @@ -1,8 +0,0 @@ - - - - - -click here if you are not redirected. - - \ No newline at end of file diff --git a/docs/html/guide/topics/ui/sharables/sample_images.zip b/docs/html/guide/topics/ui/sharables/sample_images.zip deleted file mode 100644 index 007a68aca79ec..0000000000000 Binary files a/docs/html/guide/topics/ui/sharables/sample_images.zip and /dev/null differ diff --git a/docs/html/sdk/1.0_r1/upgrading.jd b/docs/html/sdk/1.0_r1/upgrading.jd deleted file mode 100644 index d6a7ed5cdc606..0000000000000 --- a/docs/html/sdk/1.0_r1/upgrading.jd +++ /dev/null @@ -1,155 +0,0 @@ -page.title=Upgrading the SDK -sdk.version=1.0_r1 -excludeFromSuggestions=true -@jd:body - -

For the current SDK release, see the links under Current SDK Release in the side navigation.

- -

This guide will help you migrate your development environment and applications -to version 1.0, release 1, of the Android SDK. Use this guide if you've been developing applications -on a different version of the Android SDK.

- -

To ensure that your applications are compliant with the Android 1.0 system available -on mobile devices, you need to install the new SDK and port your existing Android -applications to the updated API. The sections below guide you through the process.

- -

Install the new SDK

- -

After unpacking the SDK, you should:

- - - -

Update your ADT Eclipse Plugin

- -

If you develop on Eclipse and are using the ADT plugin, follow these steps to install the -plugin that's required for this version of the SDK.

- - - - - - - -
Eclipse 3.3 (Europa)Eclipse 3.4 (Ganymede)
-
    -
  1. Download the ADT v0.8.0 zip - file (do not unpack it).
    2. -
  2. Start Eclipse, then select Help > Software Updates > Find - and Install....
    3. -
  3. In the dialog that appears, select Search for new features to install and click - Next.
    4. -
  4. Click New Archive Site...
    5. -
  5. Browse and select the downloaded the zip file.
    6. -
  6. You should now see the new site added to the search list (and checked). - Click Finish.
    7. -
  7. In the subsequent Search Results dialog box, select the checkbox for - Android Plugin > Developer Tools. - This will check both features: "Android Developer Tools", and "Android - Editors". The Android Editors feature is optional, but recommended. If - you choose to install it, you need the WST plugin mentioned earlier in this - page. Click Next.
    8. -
  8. Read the license agreement and then select Accept terms of the license agreement. - Click Next.
    9. -
  9. Click Finish.
    10. -
  10. The ADT plugin is not signed; you can accept the installation anyway - by clicking Install All.
    11. -
  11. Restart Eclipse.
    12. -
- -		 - -
    -
  1. Download the ADT v0.8.0 zip - file (do not unpack it).
    2. -
  2. Start Eclipse, then select Help > Software Updates....
    3. -
  3. In the dialog that appears, click the Available Software tab.
    4. -
  4. Click Add Site..., then Archive....
    5. -
  5. Browse and select the downloaded the zip file.
    6. -
  6. Back in the Available Software view, you should see the plugin. Select the checkbox next to - Developer Tools and click Install...
    7. -
  7. On the subsequent Install window, "Android Developer Tools", and "Android Editors" should both be checked. - The Android Editors feature is optional, but recommended. If - you choose to install it, you need the WST plugin mentioned earlier in this - page. Click Next.
    8. -
  8. Accept the license agreement and click Finish.
    9. -
  9. Restart Eclipse.
    10. -
- -
- -

After restart, update your Eclipse preferences to point to the SDK directory:

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

Set Up Application Signing

- -

All applications must now be signed before you can install them on the emulator. Both -the ADT plugin and the Ant-based build tools support this requirement by signing compiled -.apk files with a debug key. To do so, the build tools use the Keytool utility included -in the JDK to to create a keystore and a key with a known alias and password. For more -information, see "Signing and Publishing Your App" in the documentation included with the SDK. - -

To support signing, you should first make sure that Keytool is available to the SDK build -tools. In most cases, you can tell the SDK build tools how to find Keytool by making sure that -your JAVA_HOME environment variable is set and that it references a suitable JDK. Alternatively, -you can add the JDK version of Keytool to your PATH variable.

- -

If you are developing on a version of Linux that originally came with Gnu Compiler for Java, -make sure that the system is using the JDK version of Keytool, rather than the gcj version. -If keytool is already in your PATH, it might be pointing to a symlink at /usr/bin/keytool. -In this case, check the symlink target to make sure that it points to the keytool in the JDK.

- -

If you use Ant to build your .apk files (rather than ADT for Eclipse), you must regenerate -your build.xml file. To do that, follow these steps:

-
    -
  1. In your Android application project directory, locate and delete the current build.xml file.
    2. -
  2. Run activitycreator, directing output to the folder containing your application project. - -
    - exec activitycreator --out <project folder> your.activity.YourActivity
    - -
    3. -
- -

Run in this way, activitycreator will not erase or create new Java files (or manifest files), -provided the activity and package already exists. It is important that the package and the activity -are real. The tool creates a new build.xml file, as well as a new directory called "libs" in which -to place 3rd jar files, which are now automatically handled by the Ant script.

- -

Migrate your applications

- -

If (and only if) you have written apps in an SDK released previous to -the Android 1.0 SDK, you will need to migrate your applications. After -updating your SDK, you may encounter breakages in your code, due to -framework and API changes. You'll need to update your code to match -changes in the Android APIs.

- -

One way to start is to open your project in Eclipse and see where the ADT -identifies errors in your application. You can also look up -specific changes in the Android APIs in the Overview of Changes and -API Diffs Report, both available in the documentation included with the -Android 1.0 SDK package.

- -

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

- -

If you have modified one of the ApiDemos applications and would like to migrate it -to the new SDK, note that you will need to uninstall the version of ApiDemos that comes -preinstalled in the emulator.

diff --git a/docs/html/sdk/1.0_r2/upgrading.jd b/docs/html/sdk/1.0_r2/upgrading.jd deleted file mode 100644 index 243950d671d63..0000000000000 --- a/docs/html/sdk/1.0_r2/upgrading.jd +++ /dev/null @@ -1,155 +0,0 @@ -page.title=Upgrading the SDK -sdk.version=1.0_r2 -excludeFromSuggestions=true -@jd:body - -

For the current SDK release, see the links under Current SDK Release in the side navigation.

- -

This guide will help you migrate your development environment and applications -to version 1.0, release 2, of the Android SDK. Use this guide if you've been developing applications -on a different version of the Android SDK.

- -

To ensure that your applications are compliant with the Android 1.0 system available -on mobile devices, you need to install the new SDK and port your existing Android -applications to the updated API. The sections below guide you through the process.

- -

Install the new SDK

- -

After unpacking the SDK, you should:

- - - -

Update your ADT Eclipse Plugin

- -

If you develop on Eclipse and are using the ADT plugin, follow these steps to install the -plugin that's required for this version of the SDK.

- - - - - - - -
Eclipse 3.3 (Europa)Eclipse 3.4 (Ganymede)
-
    -
  1. Download the ADT v0.8.0 zip - file (do not unpack it).
    2. -
  2. Start Eclipse, then select Help > Software Updates > Find - and Install....
    3. -
  3. In the dialog that appears, select Search for new features to install and click - Next.
    4. -
  4. Click New Archive Site...
    5. -
  5. Browse and select the downloaded the zip file.
    6. -
  6. You should now see the new site added to the search list (and checked). - Click Finish.
    7. -
  7. In the subsequent Search Results dialog box, select the checkbox for - Android Plugin > Developer Tools. - This will check both features: "Android Developer Tools", and "Android - Editors". The Android Editors feature is optional, but recommended. If - you choose to install it, you need the WST plugin mentioned earlier in this - page. Click Next.
    8. -
  8. Read the license agreement and then select Accept terms of the license agreement. - Click Next.
    9. -
  9. Click Finish.
    10. -
  10. The ADT plugin is not signed; you can accept the installation anyway - by clicking Install All.
    11. -
  11. Restart Eclipse.
    12. -
- -		 - -
    -
  1. Download the ADT v0.8.0 zip - file (do not unpack it).
    2. -
  2. Start Eclipse, then select Help > Software Updates....
    3. -
  3. In the dialog that appears, click the Available Software tab.
    4. -
  4. Click Add Site..., then Archive....
    5. -
  5. Browse and select the downloaded the zip file.
    6. -
  6. Back in the Available Software view, you should see the plugin. Select the checkbox next to - Developer Tools and click Install...
    7. -
  7. On the subsequent Install window, "Android Developer Tools", and "Android Editors" should both be checked. - The Android Editors feature is optional, but recommended. If - you choose to install it, you need the WST plugin mentioned earlier in this - page. Click Next.
    8. -
  8. Accept the license agreement and click Finish.
    9. -
  9. Restart Eclipse.
    10. -
- -
- -

After restart, update your Eclipse preferences to point to the SDK directory:

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

Set Up Application Signing

- -

All applications must now be signed before you can install them on the emulator. Both -the ADT plugin and the Ant-based build tools support this requirement by signing compiled -.apk files with a debug key. To do so, the build tools use the Keytool utility included -in the JDK to to create a keystore and a key with a known alias and password. For more -information, see "Signing and Publishing Your App" in the documentation included with the SDK. - -

To support signing, you should first make sure that Keytool is available to the SDK build -tools. In most cases, you can tell the SDK build tools how to find Keytool by making sure that -your JAVA_HOME environment variable is set and that it references a suitable JDK. Alternatively, -you can add the JDK version of Keytool to your PATH variable.

- -

If you are developing on a version of Linux that originally came with Gnu Compiler for Java, -make sure that the system is using the JDK version of Keytool, rather than the gcj version. -If keytool is already in your PATH, it might be pointing to a symlink at /usr/bin/keytool. -In this case, check the symlink target to make sure that it points to the keytool in the JDK.

- -

If you use Ant to build your .apk files (rather than ADT for Eclipse), you must regenerate -your build.xml file. To do that, follow these steps:

-
    -
  1. In your Android application project directory, locate and delete the current build.xml file.
    2. -
  2. Run activitycreator, directing output to the folder containing your application project. - -
    - exec activitycreator --out <project folder> your.activity.YourActivity
    - -
    3. -
- -

Run in this way, activitycreator will not erase or create new Java files (or manifest files), -provided the activity and package already exists. It is important that the package and the activity -are real. The tool creates a new build.xml file, as well as a new directory called "libs" in which -to place 3rd jar files, which are now automatically handled by the Ant script.

- -

Migrate your applications

- -

If (and only if) you have written apps in an SDK released previous to -the Android 1.0 SDK, you will need to migrate your applications. After -updating your SDK, you may encounter breakages in your code, due to -framework and API changes. You'll need to update your code to match -changes in the Android APIs.

- -

One way to start is to open your project in Eclipse and see where the ADT -identifies errors in your application. You can also look up -specific changes in the Android APIs in the Overview of Changes and -API Diffs Report, both available in the documentation included with the -Android 1.0 SDK package.

- -

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

- -

If you have modified one of the ApiDemos applications and would like to migrate it -to the new SDK, note that you will need to uninstall the version of ApiDemos that comes -preinstalled in the emulator.

diff --git a/docs/html/sdk/1.1_r1/upgrading.jd b/docs/html/sdk/1.1_r1/upgrading.jd deleted file mode 100644 index 840ae6b748588..0000000000000 --- a/docs/html/sdk/1.1_r1/upgrading.jd +++ /dev/null @@ -1,151 +0,0 @@ -page.title=Upgrading the SDK -sdk.version=1.1_r1 -excludeFromSuggestions=true -@jd:body - - - -

This document describes how to move your development environment and existing -Android applications from an Android 1.0 SDK to the Android 1.1, Release 1 SDK. -If you are migrating applications from an earlier SDK, please read the upgrading -document available in the Android 1.0 SDK package. -

- -

To ensure that your applications are compliant with the Android 1.1 system available -on mobile devices, you need to install the Android 1.1 SDK and port your existing Android -applications to it. The sections below will guide you through the process.

- -

Installing the Latest SDK

- -

Download the SDK and unpack it into a safe location.

- -

After unpacking the new SDK and saving it an appropriate location, you should:

- - - - -

Update your ADT Eclipse Plugin

- -

If you develop on Eclipse and are migrating from an Android 1.0 -SDK, no update of the ADT plugin is needed — skip to Update your Eclipse SDK Preferences.

- -

If you are migrating from an earlier version of the SDK, you will -need to update the ADT plugin.

You may also want to upgrade your -ADT plugin when a new version becomes available for your existing version -of the SDK.

- -

The steps below describe how to update the ADT plugin to the latest -version available.

- - - - - - - -
Eclipse 3.3 (Europa)Eclipse 3.4 (Ganymede)
-
    -
  1. Select Help > Software Updates > Find and Install....
    2. -
  2. Select Search for updates of the currently installed features and click Finish.
    3. -
  3. If any update for ADT is available, select and install.
    4. -
  4. Restart Eclipse.
    5. -
-

Alternatively,

-
    -
  1. Select Help > Software Updates > Manage Configuration.
    2. - -
  2. Navigate down the tree and select Android Development Tools <version>
    3. -
  3. Select Scan for Updates under Available Tasks.
    4. -
-		 -
    -
  1. Select Help > Software Updates...
    2. -
  2. Select the Installed Software tab.
    3. -
  3. Click Update...
    4. -
  4. If an update for ADT is available, select it and click Finish.
    5. -
  5. Restart Eclipse.
    6. -
-
- -

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 OSX: Eclipse > Preferences)
    2. -
  2. Select Android from the left panel.
    3. -
  3. For the SDK Location in the main panel, click Browse... and locate the SDK directory.
    4. -
  4. Click Apply, then OK.
    5. -
- -

Migrate Your Applications, if Necessary

- -

If (and only if) you have written apps in an SDK released previous to -the Android 1.0 SDK, you will need to migrate your applications. After -installing the new SDK and updating the ADT Plugin (if applicable), you -may encounter breakages in your application code, due to -framework and API changes. You'll need to update your code to match the -latest APIs.

- -

One way to start is to open your project in Eclipse and see where the ADT -identifies errors in your application. You can also look up -specific changes in the Android APIs in the -Android 1.1 Version -Notes document.

- - -

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

- -

If you have modified one of the ApiDemos applications and would like to migrate it -to the new SDK, note that you will need to uninstall the version of ApiDemos that comes -preinstalled in the emulator. For more information, or if you encounter an "reinstallation" -error when running or installing ApiDemos, see the troubleshooting topic -I can't install ApiDemos -apps in my IDE because of a signing error for information about how to solve the problem.

- diff --git a/docs/html/sdk/1.5_r1/upgrading.jd b/docs/html/sdk/1.5_r1/upgrading.jd deleted file mode 100644 index 03770698997fe..0000000000000 --- a/docs/html/sdk/1.5_r1/upgrading.jd +++ /dev/null @@ -1,396 +0,0 @@ -page.title=Upgrading the SDK -sdk.version=1.5_r1 -excludeFromSuggestions=true -@jd:body - - -
-
- -

Upgrading quickview

- - -

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/1.5_r2/upgrading.jd b/docs/html/sdk/1.5_r2/upgrading.jd deleted file mode 100644 index 31b23582cbec7..0000000000000 --- a/docs/html/sdk/1.5_r2/upgrading.jd +++ /dev/null @@ -1,396 +0,0 @@ -page.title=Upgrading the SDK -sdk.version=1.5_r2 -excludeFromSuggestions=true -@jd:body - - -
-
- -

Upgrading the SDK

- - -

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/1.5_r3/upgrading.jd b/docs/html/sdk/1.5_r3/upgrading.jd deleted file mode 100644 index 62b9a787bcddb..0000000000000 --- a/docs/html/sdk/1.5_r3/upgrading.jd +++ /dev/null @@ -1,398 +0,0 @@ -page.title=Upgrading the SDK -sdk.version=1.5 -sdk.rel.id=3 -excludeFromSuggestions=true - -@jd:body - - -
-
- -

Upgrading the SDK

- - -

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 Android 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 parcelable 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/1.6_r1/upgrading.jd b/docs/html/sdk/1.6_r1/upgrading.jd deleted file mode 100644 index e6dded0f420a2..0000000000000 --- a/docs/html/sdk/1.6_r1/upgrading.jd +++ /dev/null @@ -1,386 +0,0 @@ -page.title=Upgrading the SDK -sdk.version=1.6 -excludeFromSuggestions=true -@jd:body - - -
-
- -

Upgrading the SDK

- - -

In this document

-
    -
  1. Install the SDK
    2. -
  2. Update Your Eclipse ADT Plugin
    3. -
  3. Run Your Applications
    4. -
  4. Migrate Your Applications
    5. -
- -

Migrating information

-
    -
  1. Android 1.6 API -Differences
    2. -
- -
-
- -

This document describes how to move your development environment and existing -Android applications from an Android 1.5 SDK to the Android 1.6 SDK. If you are -migrating applications from an SDK older than 1.5, please also read the -upgrading document available in the Android 1.5 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 upcoming Android platform.

- -

The Android 1.6 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 problems 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 the new platform.

- - -

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

- - -

Install the SDK

- -

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

- -

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

Update Your Eclipse ADT Plugin

- -

If you don't use the Eclipse IDE for development, -skip to Run Your Applications.

- -

A new version of the ADT Plugin, ADT 0.9.3, is available in conjunction with -this SDK release. To use the SDK, you must upgrade your ADT Plugin to version -0.9.3. With ADT 0.9.3, you can still compile your existing applications against -multiple platform versions, such as Android 1.5, Android 1.1, and so on. However, -ADT 0.9.3 is not compatible with previous versions of the SDK and its tools, so -make sure that you upgrade both your SDK and the ADT Plugin.

- -The upgrade steps for ADT are described below. For information about new features in ADT, see the Release Notes document.

- -

If you're currently using a version of ADT older than version 0.9, -then you must uninstall ADT before you proceed (read how to Uninstall your previous -ADT plugin). If you currently have version 0.9 or 0.9.1, then you don't need -to uninstall and can continue with the procedure below.

- - - - - - - -
Eclipse 3.4 (Ganymede)Eclipse 3.5 (Galileo)
- -
    -
  1. Select Help > Software Updates.
    2. -
  2. Select the Available Software tab.
    3. -
  3. Select the checkboxes next to Android DDMS and Android Developer Tools, - then click Update.
    4. -
  4. In the resulting Available Updates dialog, ensure that both Android DDMS - and Android Development Tools are selected, then click - Next.
    5. -
  5. Read and accept the license agreement and then click Finish. - This will download and install the latest version of Android DDMS and - Android Development Tools.
    6. -
  6. Restart Eclipse.
    7. -
-		 - -
    -
  1. Select Help > Check for Updates.
    2. -
  2. In the resulting Available Updates dialog, locate the Android DDMS and - Android Development Tools features in the list and ensure that the checkboxes - next to them are selected. Click Next. -

    If the Available Updates dialog does not list Android DDMS and Android - Development tools, make sure that you have set up a remote update site - for them, as described in - Installing the ADT Plugin. -

    3. -
  3. In the Update Details dialog, click Next.
    4. -
  4. Read and accept the license agreement and then click Finish. - This will download and install the latest version of Android DDMS and - Android Development Tools.
    5. -
  5. Restart Eclipse.
    6. -
-
- -

If you encounter problems with this update procedure, try performing a fresh -installation. Fully remove your existing ADT Plugin as described in Uninstall your previous -ADT plugin 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, click Browse - and locate your SDK directory.
    4. -
  4. Click Apply, then OK.
    5. -
- - -

Run Your Applications to Test Forward Compatibility

- -

Now that you have installed the Android 1.6 SDK, we encourage you run each of -your existing applications on the Android 1.6 system image that is included in -the SDK, to ensure that it functions properly on the new platform. -Testing forward-compatibility in this way is especially important for -applications that you may have already published and that may be installed on -devices that will upgrade to the new platform.

- -

In most cases, your applications will function properly when run on the new -version of the platform. However, it is possible that you will encounter -unexpected behavior, because of changes in the API or underlying platform. If -you do find problems, you can use the SDK tools to compile and publish an update -to the applications, which users can then download. - -

To test forward-compatibility, simply run your application, as-is, on an -instance of the Android Emulator that uses an AVD targeted to the "Android 1.6" -system image. Here are the steps:

- -
    -
  1. Make no changes to your application code.
    2. -
  2. Create a new AVD that runs the new "Android 1.6" platform.
    3. -
  3. Launch your application in an emulator running the new AVD.
    4. -
  4. Perform normal testing on your application to ensure everything works as - expected.
    5. -
- -

Note that, for the purposes of forward-compatibility testing, you should not -change how your application is compiled. That is, you should continue to compile -the application against the same version of the Android library as before. The -only change needed is to the AVD, which controls the version of the Android -system image (run-time environment) on which the application is run. - -

For more information on creating an AVD and launching your application, see -Running Your -Applications (Eclipse) or Running -Your Applications (other IDEs), depending on your development -environment.

- -

Android 1.6 Forward-Compatibility Tips

- -

The new version of the Android platform includes several new APIs, but -very few actual changes to existing APIs. This means that, in most -cases, your applications written with earlier versions of the Android library -should run properly on the Android 1.6 platform.

- -

However, here are some areas to pay attention to as you test forward-compatibility:

- - - -

Migrate Your Applications

- -

If you want to use any of the new Android 1.6 APIs in your existing -applications, you must first migrate the applications to the new Android -platform version. Generally, migrating an application includes:

- - - -

Additionally, to run your application in the emulator, you need to -create an AVD that uses the Android 1.6 system image.

- -

Note: You only need migrate your application as -described in this section if the application will actually use APIs -introduced in the Android 1.6 platform (which are not available on -devices running older versions of the Android platform). If your application -does not use any new APIs, you can compile and run it without modification and -not migration is necessary.

- -

Reference the Proper API Level

- -

If your application is using APIs introduced in Android 1.6, you must -reference that dependency in the application's manifest file so that it can be -deployed to devices running the Android 1.6 platform.

- -

Open the manifest file and locate the minSdkVersion attribute -in the <uses-sdk> manifest element. Set the value of -minSdkVersion to "4" (the API Level -identifier corresponding to Android 1.6). Here's an example:

- -
-<manifest>
-  ...
-  <uses-sdk android:minSdkVersion="4" />
-  ...
-</manifest>
-
- -

Compile Against the Proper Build Target

- -

Once you've changed the minSdkVersion value in your -application's manifest, you need to set the application's project properties so -that the application will be compiled against the Android 1.6 library. To do so, -follow the steps below for your respective development environment.

- -

Eclipse Users

- -
    -
  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 new Project Build Target. - Select "Android 1.6" to target the new platform (or "Google APIs" with the "4" - API Level, if your application uses the Google Maps APIs).
    3. -
  3. Click Apply, then OK.
    4. -
- -

Ant Users

- -

Use the android tool (located in -your_sdk/tools/) to create a new build.xml -that references the new platform target. To see a list of available targets, -execute:

- -
android list targets
- -

Select the target id that corresponds to the "Android 1.6" platform -and pass it with the --target parameter when updating your project. -For example:

- -
android update project --path /path/to/my-project --target 2
- -

If your application uses the Google Maps APIs (i.e., MapView), be certain to -select a Google APIs target.

- -

Create an AVD that Uses the Android 1.6 Platform

- -

Finally, you need to set up a new AVD that uses the Android 1.6 platform, so that -you can run your application in the emulator. - -

To set up the new AVD, use the android tool, available in the -tools/ directory of the SDK. You can run the AVD manager by simply -changing to the tools/ directory and entering android -at the command line. Click "New" to create the AVD and set its properties.

- -

When creating the AVD, make sure to select a target of "Android 1.6 - API -Level 4". If your application uses the Google Maps APIs (MapView), select the -target "Google APIs (Google Inc.) - API Level 4".

- -

For more information about running your application in an AVD, see Running Your -Application (Eclipse) or Running Your -Application (other IDEs).

- -

For general information about AVDs, see the Android Virtual -Devices document.

- - - -
-

If you have trouble migrating to the new version of the SDK, 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 cbcbb1299c6a0..d69697ab46ac6 100644 --- a/docs/html/sdk/RELEASENOTES.jd +++ b/docs/html/sdk/RELEASENOTES.jd @@ -731,11 +731,11 @@ to this release.

ADT Plugin Compatibility

-

For this version of the SDK — Android 1.0 SDK, Release 1 — the compatible version of the Android Development Tools (ADT) Plugin for Eclipse is 0.8.0. If you are using a previous version of ADT, you should update to the latest version for use with this SDK. For information about how to update your ADT plugin, see Upgrading the SDK.

+

For this version of the SDK — Android 1.0 SDK, Release 1 — the compatible version of the Android Development Tools (ADT) Plugin for Eclipse is 0.8.0. If you are using a previous version of ADT, you should update to the latest version for use with this SDK.

Installation and Upgrade Notes

-

If you've been developing an application using a previous SDK version and you want the application to run on Android-powered mobile devices, you must port the application to the Android 1.0 SDK. Please see Upgrading the SDK for detailed instructions on how to make the transition to this release. Be sure to wipe application user data (emulator option -wipe-data) when running your application on the Android 1.0 SDK emulator.

+

If you've been developing an application using a previous SDK version and you want the application to run on Android-powered mobile devices, you must port the application to the Android 1.0 SDK. Be sure to wipe application user data (emulator option -wipe-data) when running your application on the Android 1.0 SDK emulator.

Other Notes

diff --git a/docs/html/sitemap.txt b/docs/html/sitemap.txt index 105f60d805215..46164c170b79a 100644 --- a/docs/html/sitemap.txt +++ b/docs/html/sitemap.txt @@ -4214,7 +4214,6 @@ http://developer.android.com/reference/org/w3c/dom/Text.html http://developer.android.com/reference/org/w3c/dom/TypeInfo.html http://developer.android.com/reference/org/w3c/dom/UserDataHandler.html http://developer.android.com/reference/android/support/v4/content/pm/ActivityInfoCompat.html -http://developer.android.com/guide/developing/debug-tasks.html http://developer.android.com/reference/renderscript/rs__math_8rsh.html http://developer.android.com/reference/renderscript/structrs__matrix4x4.html http://developer.android.com/reference/renderscript/rs__cl_8rsh.html @@ -6473,7 +6472,6 @@ http://developer.android.com/sdk/api_diff/10/changes/packages_index_changes.html http://developer.android.com/sdk/api_diff/3/changes/constructors_index_removals.html http://developer.android.com/sdk/api_diff/3/changes/constructors_index_additions.html http://developer.android.com/sdk/api_diff/3/changes/constructors_index_changes.html -http://developer.android.com/tools/debug-tasks.html http://developer.android.com/sdk/api_diff/5/changes/classes_index_additions.html http://developer.android.com/sdk/api_diff/5/changes/classes_index_changes.html http://developer.android.com/sdk/api_diff/16/changes/classes_index_additions.html diff --git a/docs/html/tools/avd.html b/docs/html/tools/avd.html deleted file mode 100644 index 1d314a10c7149..0000000000000 --- a/docs/html/tools/avd.html +++ /dev/null @@ -1,10 +0,0 @@ - - - -Redirecting... - - -

You should be redirected. Please click here.

- - \ No newline at end of file diff --git a/docs/html/tools/debug-tasks.html b/docs/html/tools/debug-tasks.html deleted file mode 100644 index 2a5bc511242e3..0000000000000 --- a/docs/html/tools/debug-tasks.html +++ /dev/null @@ -1,10 +0,0 @@ - - - -Redirecting... - - -

You should be redirected. Please click here.

- - \ No newline at end of file diff --git a/docs/html/tools/eclipse-adt.html b/docs/html/tools/eclipse-adt.html deleted file mode 100644 index 0d59d49897350..0000000000000 --- a/docs/html/tools/eclipse-adt.html +++ /dev/null @@ -1,10 +0,0 @@ - - - -Redirecting... - - -

You should be redirected. Please click here.

- - \ No newline at end of file diff --git a/docs/html/tools/help/aapt.html b/docs/html/tools/help/aapt.html deleted file mode 100644 index ebd375d312f0c..0000000000000 --- a/docs/html/tools/help/aapt.html +++ /dev/null @@ -1,10 +0,0 @@ - - - -Redirecting... - - -

You should be redirected. Please click here.

- - \ No newline at end of file diff --git a/docs/html/tools/other-ide.html b/docs/html/tools/other-ide.html deleted file mode 100644 index 2bfe876570a2b..0000000000000 --- a/docs/html/tools/other-ide.html +++ /dev/null @@ -1,10 +0,0 @@ - - - -Redirecting... - - -

You should be redirected. Please click here.

- - \ No newline at end of file diff --git a/docs/html/tools/othertools.html b/docs/html/tools/othertools.html deleted file mode 100644 index ed45ccdf8103a..0000000000000 --- a/docs/html/tools/othertools.html +++ /dev/null @@ -1,10 +0,0 @@ - - - -Redirecting... - - -

You should be redirected. Please click here.

- - \ No newline at end of file diff --git a/docs/html/tools/sdk/OLD_RELEASENOTES.jd b/docs/html/tools/sdk/OLD_RELEASENOTES.jd deleted file mode 100644 index b7fd12f7cc5b5..0000000000000 --- a/docs/html/tools/sdk/OLD_RELEASENOTES.jd +++ /dev/null @@ -1,528 +0,0 @@ -page.title=Release Notes for Older SDK Versions -excludeFromSuggestions=true -@jd:body - -
-

Note: These are the release notes for the "early-look" SDK versions, released - before the full Android 1.0 release in September 2008. - Release notes for the Android 1.0 and later SDK versions are provided in the main - Release Notes document.

-
- - - - -

Android 0.9 SDK Beta (r1)

- -

This beta SDK release contains a large number of bug fixes and improvements from the early-look SDKs.  -The sections below describe the highlights of the release. - -

New Features and Notable Changes

- -

Behavior and System Changes

- -

- - Significant API Changes -

- -

- - Maps & Location -

- -

- ADT Plugin for Eclipse

-

The ADT Plugin that accompanies this SDK includes a preview of the Graphical Layout Editor. Files located in <project>/res/layout[-qualifiers]/ will be opened with the new layout editor. This is very much a work in progress, and provided here for preview purpose. The editor feature is subject to change. -

- - -

Known issues/limitations for Graphical Layout Editor include:

- - - - -

Other ADT features/notes include:

- - -

Ant Build Tools

- - - -

Emulator

- - - -

- Other Development Tools -

- -

The SDK includes several new development tools, such as

- -

- Application Signing -

- -

- Sample Code -

- -

- - Removed Functionality -

- -

- - Miscellaneous -

- - -

- Resolved Issues -

-

- The list below is not comprehensive, but instead highlights the most interesting fixes since the last SDK release. -

- - -

- Known Issues -

- - - - - - -

Version m5-rc15

- -

New Features

-

m5-rc15 does not introduce any new features.

- -

Resolved Issues

- - -

Known Issues

-

Unless otherwise noted, Known Issues from m5-rc14 also apply to m5-rc15.

- - - - - -

Version m5-rc14

- -

New Features

- -

In addition to changes in the Android APIs, m5-rc14 also introduces changes to the Android Developer Tools:

- -

emulator

- - -

DDMS

- - -

ADT

- - -

AIDL

- - -

traceview

- - -

Resolved Issues

- -

The following Known Issues from m3-rc20 have been resolved:

- - -

Known Issues

- -

The following are known issues in m5-rc14:

- - - -

Unless otherwise noted, Known Issues from m3-rc20a also apply to m5-rc14.

- - - - - -

Version m3-rc37a

- -

Version m3-rc37a and ADT 0.3.3 were released on December 14, 2007.

- -

New Features

- -

Android Debug Bridge (ADB)

- - -

ADT Plugin for Eclipse

- - -

Emulator Console

- - -

Emulator

- - -

Resolved Issues

- -

907947

-

adb -version now returns a version number.

- -

917462

-

Audio on Windows is fixed and is no longer 'choppy'.

- -

Removed Manifest File Locking on Mac OS X

- -

ADT plugin now uses a custom java editor for R.java/Manifest.java, to make those files non-editable. This is to replace the current locking mechanism which causes issues on Mac OS (preventing projects from being deleted). Note that your project must recompile at least once for the lock to be removed from the files.

- -

The following known issues noted in m3-rc20 are now fixed:

-

-

-

- -

Known Issues

- -

Unless otherwise noted, Known Issues from m3-rc22a also apply to m3-rc37a.

- - - - - -

Version m3-rc22a

- -

Version m3-rc22a and ADT 0.3.1 were released on November 16, 2007.

- -

Resolved Issues

- -

920067

-

The New Android Project wizard provided by ADT 0.3.1 now properly displays error messages when used with Eclipse 3.2 on Windows.

- -

920045

-

The AndroidManifest.xml files generated by ADT 0.3.1 now include the XML element required for displaying the associated app in the "Applications" menu. If you have applications created with ADT 0.3.0, simply ensure that your AndroidManifest.xml file contains the following highlighted line:

-
-...
-    <intent-filter>
-        <action android:value="android.intent.action.MAIN" />
-        <category android:value="android.intent.category.LAUNCHER" />
-    </intent-filter>
-...
-
- -

920098

-

ADT 0.3.1 is now compatible with Eclipse 3.4.

- -

920282

-

Fixes a NullPointerException that is thrown in certain situations with the DDMS perspective in Eclipse.

- -

918637

-

Address a keyboard lock-up issue when using adb on Mac OS X 10.4 and 10.5.

- -

Known Issues

- -

Unless otherwise noted, known issues from m3-rc20a also apply to m3-rc22a.

- - - -

Version m3-rc20a

-

Known Issues

- -

The following are known issues in m3-rc20a:

- -

778432 - Resolved in m5

-

In certain circumstances, icons for newly installed applications do not display as expected.

- -

890937 - Resolved in m3-rc37a

-

The emulator currently does not support non-QWERTY keyboards.

- -

894618 - Resolved in m3-rc37a

-

The adb shell command may fail to connect when used for the first time.

- -

896274 - Resolved in m5

-

On Windows, the emulator screen will sometimes show up off-screen when it is started. The workaround for this is to right-click on the emulator taskbar entry, select Move, and move the window using keyboard arrow keys

- -

899949 - Resolved in m3-rc37a

-

The emulator may fail to start when using the -useaudio in some environments

- -

901122 - Resolved in m5

-

The focus ring shown in the browser may sometimes not properly wrap links.

- -

905242 - Resolved in m5

-

On Mac OS X 10.5, the Eclipse plugin's Run Dialog may sometimes fail to show the option to select the Android Launcher.

- -

905852 - Resolved in m5

-

On Mac OS X 10.5, adb will emit warnings about deprecated API use when first used.

- -

912168 - Resolved in m5

-

extremely rapid or prolonged scrolling in the Maps application or in a MapView will result in application errors.

- -

912619 - Resolved in m3-rc37a

-

The emulator console listens for connections on ports 5554-5587. Future versions will only accept connections from localhost. It is recommend that you use a firewall to block external connections to those ports on your development machine.

- -

912849

-

On Mac OS X 10.4, the emulator may hang if started in the background (i.e. ./emulator &).

- -

914692

-

On Mac OS X 10.5, the emulator will emit warnings about deprecated API use when started from the command line.

- -

917247 - Resolved in m5

-

The dmtracedump and traceview tools are not available in the SDK.

- -

917399 - Resolved in m3-rc37a

-

On Windows, running multiple emulator consoles can result in unexpected behavior when simulating incoming telephone calls.

- -

917465 - Resolved in m5

-

Unanswered incoming calls placed from the emulator console, will result in an unfinished call UI if you press the call back button.

- -

917572 - Resolved in m5

-

Using activityCreator with the --ide intellij option creates IntelliJ scripts with incorrect documentation location specified. To correct, change value for the <JAVADOC> element in the generated .ipr file from file://.../docs/framework to file://.../docs/reference.

- -

917579

-

On Ubuntu 7.10 (Gusty), the Eclipse package installed by the apt-get install eclipse command uses java-gcj by default. This configuration is not compatible with the Android Eclipse plugin (ADT) and will result in "Class not found" errors whenever you access an ADT feature.

-

The resolution for this issue is to install a Sun JDK

- 
sudo update-java-alternatives --jre java-1.5.0-sun
-

and then configure Eclipse to use it by exporting the following environment variable:

- 
export JAVA_HOME=/usr/lib/jvm/java-1.5.0-sun
-

or by adding following to your .eclipse/eclipserc file:

- 
JAVA_HOME=/usr/lib/jvm/java-1.5.0-sun
- diff --git a/docs/html/tools/sdk/RELEASENOTES.jd b/docs/html/tools/sdk/RELEASENOTES.jd deleted file mode 100644 index cbcbb1299c6a0..0000000000000 --- a/docs/html/tools/sdk/RELEASENOTES.jd +++ /dev/null @@ -1,804 +0,0 @@ -page.title=SDK Release Notes -excludeFromSuggestions=true -@jd:body - -

This document provides version-specific information about Android SDK -releases.

- -

Android SDK

- -

The Android SDK has changed! If you've worked with the Android SDK before, -you will notice several important differences:

- - - -

Note that if you are currently using the Android 1.6 SDK, you do not -necessarily need to install the new SDK, since your existing SDK already -includes the Android SDK and AVD Manager tool. To develop against Android 2.0.1, -for example, you could just download the Android 2.0.1 platform into your existing -SDK.

- -

Release notes for Android platforms and other SDK components are -now available from the "SDK" tab, under "Downloadable SDK Components."

- - - -

To get started with the SDK, review the Quick Start summary on the Android SDK download page or read Installing the SDK for detailed -installation instructions.

- - -

Android 1.6 SDK, Release 1

- -

This SDK provides updates to the development tools and Android system that -you use to create applications for compliant Android-powered devices.

- -

Release Overview

- -

This SDK release includes several 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 Android 1.6 version notes.

- -

Installation and Upgrade Notes

- -

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.

- -

ADT Plugin for Eclipse

- -

An updated version of the ADT Plugin for Eclipse is available with the -Android 1.6 SDK. The new version, ADT 0.9.3, provides several new -features, including integrated support for the Android SDK and AVD Manager -and zipalign tool. In addition, the New Project Wizard now -lets you create a test package containing tests for your application. These -features are described in the sections below.

- -

If you are developing in Eclipse with ADT and want to get started with the -Android 1.6 SDK, you should download and install a compatible version of the ADT -Plugin (0.9.3 or higher).

- -

The new version of ADT is downloadable from the usual remote update site or -is separately downloadable as a .zip archive. For instructions on how to -download the plugin, please see ADT Plugin for Eclipse.

- -

Android SDK and AVD Manager

- -

The SDK offers a new tool called Android SDK and AVD Manager that lets you -manage your SDK and AVD environments more efficiently.

- -

Using the tool, you can quickly check what Android platforms, add-ons, -extras, and documentation packages are available in your SDK environment, what -their versions are, and whether updated versions are available. You can then -download one or more items from remote repositories and install them directly in -your SDK environment. For example, the tool lets you obtain updates to SDK tools -incrementally, as they are made available, without having to wait for the next -SDK release. You can also download Android platform versions into your -environment that were not included in the SDK package.

- -

The tool also lets you quickly create new AVDs, manage -their properties, and run a target AVD from a single window.

- -

If you are developing in Eclipse with ADT, you can access the Android SDK -and AVD Manager from the Window menu.

- -

If you are developing in another IDE, you can access the Android SDK and -AVD Manager through the android command-line tool, located in the -<sdk>/tools directory. You can launch the tool with a graphical UI by -using the android command without specifying any options. You can -also simply double-click the android.bat (Windows) or android (OS X/Linux) file. -You can still use android commands to create and manage AVDs, -including AVDs with custom hardware configurations.

- -

Integration with zipalign

- -

The Android system offers a performance optimization for installed -application packages whose contained uncompressed files are all aligned on -4-byte boundaries. For these .apks, the system can read the files by mmap'ing -the zip file, rather than by copying all the data out of them. This reduces -the amount of memory used by the application at run time. The SDK includes -a tool called zipalign that you can run against your .apks, to -align them properly and enable them to benefit from this optimization.

- -

The ADT Plugin and the Ant build tools both provide integrated support for -aligning your application packages. After you build an .apk, the SDK tools can -sign and then run zipalign against it. The SDK includes the -standalone version of the zipalign tool, so you can run also run it -manually from the command line if you choose.

- - - -

In general, note that you must zipalign an application only -after it has been signed, as signing will disrupt the package -alignment.

- -

Support for Test Packages in New Project Wizard

- -

The New Project Wizard available in the ADT 0.9.3 now lets you add a test -package containing Instrumentation or other classes of tests while you are -creating or importing a new Android application project.

- -

New USB Driver 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. - -

The Windows version of the Android 1.6 SDK includes a new, WinUSB-based -driver that you can install. The driver is compatible with both 32- and 64-bit -versions of Windows XP and Vista. The driver represents an upgrade from the USB -driver included in previous Android SDKs, although installing the new driver is -not required.

- -

If you installed the USB driver from a previous SDK release and it is working -properly, you do not need to upgrade to the new driver. However, we recommend -upgrading if you have had any problems with the older driver or simply want -to upgrade to the latest version.

- -

For driver installation or -upgrade instructions, see USB Driver for Windows.

-

- -

Emulator Skins, Android 1.6 Platform

- -

The Android 1.6 platform included in the SDK provides a new set of emulator -skins, including:

- - - -

Besides these defaults, You can also create an AVD that overrides the default -density for each skin, to create any combination of resolution/density (WVGA -with medium density, for instance). To do so, use the android tool -command line to create a new AVD that uses a custom hardware configuration. See -Creating an -AVD for more information.

- -

Other Notes and Resolved Issues

- - - - -

Android 1.5 SDK, Release 3

- -

Provides an updated Android 1.5 system image that includes permissions -fixes, as described below, and a new application — an IME for Japanese -text input. Also provides the same set of developer tools included in the -previous SDK, but with bug fixes and several new features.

- -

Permissions Fixes

- -

The latest version of the Android platform, deployable to -Android-powered devices, includes fixes to the permissions-checking -in certain areas of the framework. Specifically, the Android system -now properly checks and enforces several existing permissions where it -did not do so in the previous release. Because of these changes in -enforcement, you are strongly encouraged to test your application -against the new Android 1.5 system image included in this SDK, to ensure -that it functions normally.

- -

In particular, if your application uses any of the system areas listed below, -you should add the required permissions to the application's manifest and then -test the areas of your code that depend on the permission-protected services. -Even if you believe your application does not use the permissions-protected -services, you should compile and test your application under the latest platform -version to ensure that users will not encounter problems when using your -application.

- -

The changes to permissions are as follows:

- - - -

For more information, see the issue described in the oCert advisory -below:

- -

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

- -

Resolved Issues, Changes

- - - -

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

- -

This SDK provides updates to the development tools and Android system that -you use to create applications for compliant Android-powered devices.

- -

Release Overview

- -

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 Android 1.5 version notes.

- -

Installation and Upgrade Notes

- -

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.

- -

SDK Add-Ons

- -

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.

- -

Android Virtual Devices (AVDs)

- -

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 Creating and Managing Virtual Devices - -

Other Notes

- -

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:

- - - -

For driver installation or -upgrade instructions, see USB Driver for Windows.

-

- -

Resolved Issues, Changes

- -

Media

- - -

Known Issues

- -

Sensor problems in Emulator

- - - -

Other

- - - - -

Android 1.1 SDK, Release 1

- -

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.

- -

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.

- -

App Versioning for Android 1.1

- -

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:

- -
<manifest>
-  ...
-  <uses-sdk android:minSdkVersion="2" />
-  ...
-</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.

- -

If your application uses APIs introduced in Android 1.1 but does not declare -<uses-sdk android: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 android: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.

- - -

ADT Plugin Compatibility

- -

For this version of the SDK — Android 1.1 SDK, Release 1 -— the compatible version of the Android Development Tools (ADT) -Plugin for Eclipse is 0.8.0. If you are using a -previous version of ADT, you should update to the latest version for use -with this SDK. For information about how to update your ADT plugin, see -ADT Plugin for Eclipse.

- -

Installation and Upgrade Notes

- -

If you've been developing an application using an Android 1.0 SDK no -changes to your application are needed. You may want to wipe application -user data (emulator option -wipe-data) when running your -application on the Android 1.1 emulator for the first time.

- -

Other Notes

- -

MapView API Key

- -

com.google.android.maps.MapView is a class that lets you -easily integrate Google Maps into your application. Before you can -access the maps data, you will need to register with the Google Maps -service and receive a Maps API Key, which you then add to your MapView -for authentication to the server.

- -

Developers should note that the registration service for MapView is now -active and Google Maps is actively enforcing the Maps API Key requirement. -For information about how to register for a Maps API Key, see - -Obtaining a Maps API Key.

- -

USB Drivers for Windows

- -

If you 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 Connecting Hardware Devices.

-

- -

Resolved Issues, Changes

- -

Emulator

- - -

Known Issues

- -

JUnit and Eclipse/ADT

- - -

Other

- - - - -

Android 1.0 SDK, Release 2

- -

This SDK release includes the Android 1.0 platform and application API. -Applications developed on this SDK will be compatible with mobile devices -running the Android 1.0 platform.

- -

This release includes mainly bug fixes, although some smaller features were -added.

- -

ADT Plugin Compatibility

- -

For this release of the SDK, the compatible version of the Android -Development Tools (ADT) Plugin for Eclipse is 0.8.0. If you are -using a previous version of ADT, you should update to the latest version for use -with this SDK. For information about how to update your ADT plugin, see ADT Plugin for Eclipse.

- -

Other Notes

- -

T-Mobile G1 Compatibility

- -

This version of the SDK has been tested for compatibility with the first -Android-powered mobile device, the T-Mobile -G1.

- -

MapView API Key

- -

MapView is a class that lets you easily integrate Google Maps into your -application. Before you can access the maps data, you will need to register with -the Google Maps service and receive a Maps API Key, which you then add to your -MapView for authentication to the server.

- -

Developers should note that the registration service for MapView is now -active and Google Maps is actively enforcing the Maps API Key requirement. For -information about how to register for a Maps API Key, see http://code.google.com/android/add-ons/google-apis/mapkey.html. -

- -

USB Driver for Windows

-

If you 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 a -USB driver that you can install, to let you develop on the device. The USB -driver files are located in the <SDK>/usb_driver directory. - -

- -

Resolved Issues, Changes

- - -

Unless otherwise noted, Known Issues from the previous SDK release also apply -to this release.

- - - - - - -

Android 1.0 SDK, Release 1

- -

This SDK release is the first to include the Android 1.0 platform and application API. Applications developed on this SDK will be compatible with mobile devices running the Android 1.0 platform, when such devices are available.

- -

This release includes mainly bug fixes, although some smaller features were added. The Android 1.0 also includes several API changes from the 0.9 version. For those porting from the M5 release, the SDK also includes the legacy changes overview and API Differences Reports. See the current Overview of Changes for more information.

- -

ADT Plugin Compatibility

- -

For this version of the SDK — Android 1.0 SDK, Release 1 — the compatible version of the Android Development Tools (ADT) Plugin for Eclipse is 0.8.0. If you are using a previous version of ADT, you should update to the latest version for use with this SDK. For information about how to update your ADT plugin, see Upgrading the SDK.

- -

Installation and Upgrade Notes

- -

If you've been developing an application using a previous SDK version and you want the application to run on Android-powered mobile devices, you must port the application to the Android 1.0 SDK. Please see Upgrading the SDK for detailed instructions on how to make the transition to this release. Be sure to wipe application user data (emulator option -wipe-data) when running your application on the Android 1.0 SDK emulator.

- -

Other Notes

- -

MapView API Key

- -

MapView is a class that lets you easily integrate Google Maps into your application. Before you can access the maps data, you will need to register with the Google Maps service and receive a Maps API Key, which you then add to your MapView for authentication to the server.

- -

Currently, the registration service for MapView is not yet active and Google Maps is not yet enforcing the Maps API Key requirement. However, note that the registration service will be activated soon, so that MapViews in any application deployed to a mobile device will require registration and a valid Maps API Key.

- -

As soon as the registration service becomes available, we will update the page at http://code.google.com/android/add-ons/google-apis/mapkey.html with details about how and where to register. Please check that page periodically for registration information, if you are using a MapView.

- - -

Resolved Issues, Changes

- -

Emulator

- - -

SQLite

- - -

Other

- - - diff --git a/docs/html/tools/sdk/installing.jd b/docs/html/tools/sdk/installing.jd deleted file mode 100644 index 19e89902432e7..0000000000000 --- a/docs/html/tools/sdk/installing.jd +++ /dev/null @@ -1,591 +0,0 @@ -page.title=Installing the SDK -excludeFromSuggestions=true - -@jd:body - - - - - -
-
- -

In this document

-
    -
  1. 1. Preparing Your Development Computer
    2. -
  2. 2. Downloading the SDK Starter Package
    3. -
  3. 3. Installing the ADT Plugin for Eclipse
    4. -
  4. 4. Adding Platforms and Other Packages -
      -
    1. Available Packages
      2. -
    2. Recommended Packages
      3. -
    5. -
  5. 5. Exploring the SDK (Optional)
    6. -
  6. Next Steps
    7. -
  7. Troubleshooting
    8. -
- -

See also

-
    -
  1. ADT Plugin for Eclipse
    2. -
  2. Exploring the SDK
    3. -
- -
-
- -

This page describes how to install the Android SDK -and set up your development environment for the first time.

- -

If you encounter any problems during installation, see the -Troubleshooting section at the bottom of -this page.

- -

Updating?

- -

If you already have an Android SDK, use the Android SDK Manager tool to install -updated tools and new Android platforms into your existing environment. For information about how to -do that, see Exploring the SDK.

- - -

Step 1. Preparing Your Development Computer

- -

Before getting started with the Android SDK, take a moment to confirm that -your development computer meets the System -Requirements. In particular, you might need to install the JDK, if you don't have it already.

- -

If you will be developing in 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 as described in the -System Requirements document. -If you need to install Eclipse, you can download it from this location:

- -

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

- -

The "Eclipse Classic" version is recommended. Otherwise, a Java or -RCP version of Eclipse is recommended.

- - -

Step 2. Downloading the SDK Starter Package

- -

The SDK starter package is not a full -development environment—it includes only the core SDK Tools, which you can -use to download the rest of the SDK packages (such as the latest Android platform).

- -

If you haven't already, get the latest version of the SDK starter package from the SDK download page.

- -

If you downloaded a {@code .zip} or {@code .tgz} package (instead of the SDK installer), unpack -it to a safe location on your machine. By default, the SDK files are unpacked -into a directory named android-sdk-<machine-platform>.

- -

If you downloaded the Windows installer ({@code .exe} file), run it now and it will check -whether the proper Java SE Development Kit (JDK) is installed (installing it, if necessary), then -install the SDK Tools into a default location (which you can modify).

- -

Make a note of the name and location of the SDK directory on your system—you will need to -refer to the SDK directory later, when setting up the ADT plugin and when using -the SDK tools from the command line.

- - -

Step 3. 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, debug your applications -using the Android SDK tools, and even export signed (or unsigned) APKs in order -to distribute your application. In general, developing in Eclipse with ADT is a -highly recommended approach and is the fastest way to get started with Android. -

- -

If you'd like to use ADT for developing Android applications, install it now. -Read Installing the ADT Plugin for -step-by-step installation instructions, then return here to continue the -last step in setting up your Android SDK.

- -

If you prefer to work in a different IDE, you do not need to -install Eclipse or ADT. Instead, you can directly use the SDK tools to build and -debug your application. The Introduction -to Android application development outlines the major steps that you need to complete when -developing in Eclipse or other IDEs.

- - - -

Step 4. Adding Platforms and Other Packages

- -

The last step in setting up your SDK is using the Android SDK Manager (a -tool included in the SDK starter package) to download essential SDK packages into your development -environment.

- -

The SDK uses a modular structure that separates the major parts of the SDK—Android platform -versions, add-ons, tools, samples, and documentation—into a set of separately installable -packages. The SDK starter package, which you've already downloaded, includes only a single -package: the latest version of the SDK Tools. To develop an Android application, you also need to -download at least one Android platform and the associated platform tools. You can add other -packages and platforms as well, which is highly recommended.

- -

If you used the Windows installer, when you complete the installation wizard, it will launch the -Android SDK Manager with a default set of platforms and other packages selected -for you to install. Simply click Install to accept the recommended set of -packages and install them. You can then skip to Step 5, but we -recommend you first read the section about the Available Packages to -better understand the packages available from the Android SDK Manager.

- -

You can launch the Android SDK Manager in one of the following ways:

- - -

To download packages, use the graphical UI of the Android SDK -Manager to browse the SDK repository and select new or updated -packages (see figure 1). The Android SDK Manager installs the selected packages in -your SDK environment. For information about which packages you should download, see Recommended Packages.

- - -

Figure 1. The Android SDK Manager's -Available Packages panel, which shows the SDK packages that are -available for you to download into your environment.

- - -

Available Packages

- -

By default, there are two repositories of packages for your SDK: Android -Repository and Third party Add-ons.

- -

The Android Repository offers these types of packages:

- - - -

The Third party Add-ons provide packages that allow you to create a development -environment using a specific Android external library (such as the Google Maps library) or a -customized (but fully compliant) Android system image. You can add additional Add-on repositories by -clicking Add Add-on Site.

- - -

Recommended Packages

- -

The SDK repository contains a range of packages that you can download. -Use the table below to determine which packages you need, based on whether you -want to set up a basic, recommended, or full development environment: -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
EnvironmentSDK PackageComments
BasicSDK ToolsIf you've just installed -the SDK starter package, then you already have the latest version of this package. The -SDK Tools package is required to develop an Android application. Make sure you keep this up to -date.
SDK Platform-toolsThis includes more tools that are required -for application development. These tools are platform-dependent and typically update only when -a new SDK platform is made available, in order to support new features in the platform. These -tools are always backward compatible with older platforms, but you must be sure that you have -the latest version of these tools when you install a new SDK platform.
SDK platformYou need to download at least one platform into your environment, so that -you will be able to compile your application and set up an Android Virtual -Device (AVD) to run it on (in the emulator). To start with, just download the -latest version of the platform. Later, if you plan to publish your application, -you will want to download other platforms as well, so that you can test your -application on the full range of Android platform versions that your application supports.
+
Recommended
(plus Basic)		DocumentationThe Documentation package is useful because it lets you work offline and -also look up API reference information from inside Eclipse.
SamplesThe Samples packages give you source code that you can use to learn about -Android, load as a project and run, or reuse in your own app. Note that multiple -samples packages are available — one for each Android platform version. When -you are choosing a samples package to download, select the one whose API Level -matches the API Level of the Android platform that you plan to use.
Usb DriverThe Usb Driver package is needed only if you are developing on Windows and -have an Android-powered device on which you want to install your application for -debugging and testing. For Mac OS X and Linux platforms, no -special driver is needed.
+
Full
(plus Recommended)		Google APIsThe Google APIs add-on gives your application access to the Maps external -library, which makes it easy to display and manipulate Maps data in your -application.
Additional SDK PlatformsIf you plan to publish your application, you will want to download -additional platforms corresponding to the Android platform versions on which you -want the application to run. The recommended approach is to compile your -application against the lowest version you want to support, but test it against -higher versions that you intend the application to run on. You can test your -applications on different platforms by running in an Android Virtual Device -(AVD) on the Android emulator.
- -

Once you've installed at least the basic configuration of SDK packages, you're ready to start -developing Android apps. The next section describes the contents of the Android SDK to familiarize -you with the packages you've just installed.

- -

For more information about using the Android SDK Manager, see the Exploring the SDK document.

- - -

Step 5. Exploring the SDK (Optional)

- -

Once you've installed the SDK and downloaded the platforms, documentation, -and add-ons that you need, we suggest that you open the SDK directory and take a look at what's -inside.

- -

The table below describes the full SDK directory contents, with packages -installed.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
add-ons/Contains add-ons to the Android SDK development -environment, which let you develop against external libraries that are available on some -devices.
docs/A full set of documentation in HTML format, including the Developer's Guide, -API Reference, and other information. To read the documentation, load the -file index.html in a web browser.
platform-tools/Contains platform-dependent development tools that may be updated with each platform release. -The platform tools include the Android Debug Bridge ({@code adb}) as well as other tools that you -don't typically use directly. These tools are separate from the development tools in the {@code -tools/} directory because these tools may be updated in order to support new -features in the latest Android platform.
platforms/Contains a set of Android platform versions that you can develop -applications against, each in a separate directory.
<platform>/Platform version directory, for example "android-11". All platform version directories contain -a similar set of files and subdirectory structure. Each platform directory also includes the -Android library (android.jar) that is used to compile applications against the -platform version.
samples/Sample code and apps that are specific to platform version.
tools/Contains the set of development and profiling tools that are platform-independent, such -as the emulator, the Android SDK Manager, the AVD Manager, ddms, -hierarchyviewer -and more. The tools in this directory may be updated at any time using the Android SDK -Manager and are independent of platform releases.
SDK Readme.txtA file that explains how to perform the initial setup of your SDK, -including how to launch the Android SDK Manager tool on all -platforms.
SDK Manager.exeWindows SDK only. A shortcut that launches the Android SDK -Manager tool, which you use to add packages to your SDK.
- - -

Optionally, you might want to add the location of the SDK's tools/ and -platform-tools to your PATH environment variable, to provide easy -access to the tools.

- - -
- - - How to update your PATH -
- -

Adding both tools/ and platform-tools/ to your PATH lets you run -command line tools without needing to -supply the full path to the tool directories. Depending on your operating system, you can -include these directories in your PATH in the following way:

- - - -
-
- - -

Next Steps

-

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

- -

Set up the Hello World application

- - -

Following the Hello World tutorial is an essential -first step in getting started with Android development.

- -

Learn about Android

- - -

Explore the development tools

- - -

Follow the Notepad tutorial

- - -

Following the Notepad tutorial is an excellent -second step in getting started with Android development.

- -

Explore some code

- - - -

Visit the Android developer groups

- - -

Troubleshooting

- -

Ubuntu Linux Notes

- - - -

Other Linux Notes

- - diff --git a/docs/html/tools/sdk/older_releases.jd b/docs/html/tools/sdk/older_releases.jd deleted file mode 100644 index 94baa92e4e4ed..0000000000000 --- a/docs/html/tools/sdk/older_releases.jd +++ /dev/null @@ -1,614 +0,0 @@ -page.title=SDK Archives -excludeFromSuggestions=true -@jd:body - -

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

- -
-

If you are just starting to develop applications for Android, please -download the current Android -SDK. With the current Android SDK, you can add any current and previous -version of the Android platform as a component and use it for -development and testing.

-

If you already have an Android SDK for platform version 1.6 or newer, then -you do not need to install a new SDK—especially not one from this page. -You should install older platforms as components of your existing SDK. -See Exploring the SDK.

-
- - -

Archived SDKs

- -

The tables below provides Android SDKs that are current in terms of their -platform version, but do not provide the latest Android development -environment and tools. Instead of downloading one of these, as a separate -SDK for each version of the platform, you should instead use the new -version-neutral Android SDK to download each version of -the Android platfrom as an individual component.

- -

Please download the current Android SDK.

- - -

Release 1.6 r1

-

September 2009 - Release -Notes

- - - - - - - - - - - - - - - - - - - - - - - - - - - -
PlatformPackageSizeMD5 Checksum
Windows - android-sdk- -windows-1 .6_r1.zip - 260529085 bytes2bcbacbc7af0363058ca1cac6abad848
Mac OS X (intel) - android-sdk- -mac_x86-1 .6_r1.zip - 247412515 byteseb13cc79602d492e89103efcf48ac1f6
Linux (i386) - android- -sdk- linux_x86-1.6_r1.tgz - 238224860 bytesb4bf0e610ff6db2fb6fb09c49cba1e79
- - -

Release 1.5 r3

-

July 2009 - Release -Notes

- - - - - - - - - - - - - - - - - - - - - - - - - - - -
PlatformPackageSizeMD5 Checksum
Windows - android-sdk- -windows-1 .5_r3.zip - 191477853 bytes1725fd6963ce69102ba7192568dfc711
Mac OS X (intel) - android-sdk- -mac_x86-1 .5_r3.zip - 183024673 bytesb1bafdaefdcec89a14b604b504e7daec
Linux (i386) - android- -sdk- linux_x86-1.5_r3.zip - 178117561 bytes350d0211678ced38da926b8c9ffa4fac
- - -

Release 1.1 r1

-

February 2009 - Release -Notes

- - - - - - - - - - - - - - - - - - - - - - - - - - - -
PlatformPackageSizeMD5 Checksum
Windows - android-sdk- -windows-1 -.1_r1.zip - 86038515 bytes8c4b9080b430025370689e03d20842f3
Mac OS X (intel) - android-sdk- -mac_x86-1 -.1_r1.zip - 79046151 bytesbecf0f1763d61eedce15d2a903d6c1dd
Linux (i386) - android- -sdk- -linux_x86-1.1_r1.zip - 79345522 bytesebcb16b0cd4aef198b4dd9a1418efbf1
- - -

Release 1.0 r2

-

November 2008 - Release -Notes

- - - - - - - - - - - - - - - - - - - - - - - - - - - -
PlatformPackageSizeMD5 Checksum
Windows - android-sdk- -windows-1 -.0_r2.zip - 98360564 bytesa5e1af8ac145946b4a9627516ad4a711
Mac OS X (intel) - android-sdk- -mac_x86-1 -.0_r2.zip - 93771410 bytes87b99d5e9f59b78363a63200c11498e8
Linux (i386) - android- -sdk- -linux_x86-1.0_r2.zip - 94186463 bytesa1f3b6d854596f850f5008856d0f380e
- - - - -

Obsolete SDK Releases

- -

These tables provide Android SDK releases that have been superceded by -an active release (shown above) and that are now obsolete.

- - -

Release 1.5 r2

-

May 2009 - Release -Notes

- - - - - - - - - - - - - - - - - - - - - - - - - - - -
PlatformPackageSizeMD5 Checksum
Windows - android-sdk- -windows-1 .5_r2.zip - 178346828 bytesba54ac6bda45921d442b74b6de6ff6a9
Mac OS X (intel) - android-sdk- -mac_x86-1 .5_r2.zip - 169945128 bytesf4e06a5194410243f213d0177713d6c9
Linux (i386) - android- -sdk- linux_x86-1.5_r2.zip - 165035130 bytes1d3c3d099e95a31c43a7b3e6ae307ed3
- - -

Release 1.5 r1

-

April 2009 - Release -Notes

- - - - - - - - - - - - - - - - - - - - - - - - - - - -
PlatformPackageSizeMD5 Checksum
Windows - android-sdk- -windows-1 .5_r1.zip - 176263368 bytes42be980eb2d3efaced01ea6c32c0045f
Mac OS X (intel) - android-sdk- -mac_x86-1 .5_r1.zip - 167848675 bytes5b2a8d9f096032db4a75bfa0d689a51b
Linux (i386) - android- -sdk- linux_x86-1.5_r1.zip - 162938845 bytes2addfd315da0ad8b5bde6b09d5ff3b06
- - -

Release 1.0 r1

-

September 23, 2008 - Release -Notes

- - - - - - - - - - - - - - - - - - - - - - - - - - - -
PlatformPackageSizeMD5 Checksum
Windows - android-sdk- -windows-1 .0_r1.zip - 89.7 MB bytesd69f4ee93d4010f726c04302662fd999
Mac OS X (intel) - android-sdk- -mac_x86-1 .0_r1.zip - 87.5 MB bytes564876ada22872e50c2866806de9fc5c
Linux (i386) - android- -sdk- linux_x86-1.0_r1.zip - 87.8 MB bytes2660b4029039b7d714e59827e9a9a11d
- - - - -

Non-Compatible SDK 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.

- - -

Version 0.9 Beta

-

August 18, 2008 - Release Notes

- - - - - - - - - - - - - - - - - - - - - - - - -
PackageSizeMD5 Checksum
Windows - -android-sdk-windows-0.9_beta.zip93,126,573 bytes305031ad8335d1b6040bdd5a65349d6d
Mac OS X (intel) - -android-sdk-mac_x86-0.9_beta.zip91,374,464 bytes9a6969159091cede46302e11049fe3ca
Linux (i386) -android-sdk-linux_x86-0.9_beta.zip91,821,068 bytes077e5ef549dd9c5be54bd88e6a8e196c
- -

Version m5-rc15

-

March 3, 2008 - Release Notes

- - - - - - - - - - - - - - - - - - - - - - - - -
PackageSizeMD5 Checksum
Windows - -android-sdk_m5-rc15_windows.zip79 MBecce40bc50201886d95ba2690cdbc5ce
Mac OS X (intel) - -android-sdk_m5-rc15_mac-x86.zip76 MB45a6385bbc1b2cb295409cfc81fb04b4
Linux (i386) - -android-sdk_m5-rc15_linux-x86.zip76 MBe913f785afecdeed34c30639fd8c5862
- -

Version m5-rc14

-

February 12, 2008 - Release Notes

- - - - - - - - - - - - - - - - - - - - - - - - -
PackageSizeMD5 Checksum
Windows - -android-sdk_m5-rc14_windows.zip79 MBecc75c1e69588350634ca25867ce05a0
Mac OS X (intel) - -android-sdk_m5-rc14_mac-x86.zip76 MB844c80d0adb1a326f5a9fff262c61efc
Linux (i386) - -android-sdk_m5-rc14_linux-x86.zip76 MBf8b863c8a880afe9bb84124f5976aab1
- - - - -

Version m3-rc37a

-

December 14, 2007 - Release Notes

- - - - - - - - - - - - - - - - - - - - - - - - -
PackageSizeMD5 Checksum
Windows - -android_sdk_windows_m3-rc37a.zip58 MB5db5aea20a2c2f010baefc4b1091a575
Mac OS X (intel) - -android_sdk_darwin_m3-rc37a.zip54 MB0b22e73fbd07b4af4009387afce3a37f
Linux (i386) - -android_sdk_linux_m3-rc37a.zip54 MB41285beecc4f9926e6ecf5f12610b356
- - - - -

Version m3-rc22a

-

November 16, 2007 - Release Notes

- - - - - - - - - - - - - - - - - - - - - - - - -
PackageSizeMD5 Checksum
Windows - -android_sdk_windows_m3-rc22a.zip59 MBaa3dee05a9872752a3bc4efd0f93e98b
Mac OS X (intel) - -android_sdk_darwin_m3-rc22a.zip55 MB0547f45614ad94c3af22c3c0aa6f709f
Linux (i386) - -android_sdk_linux_m3-rc22a.zip55 MB84b3455de5cdfd841a172c13d24c382e
- - - - -

Version m3-rc20a

-

November 12, 2007 - Release Notes

- - - - - - - - - - - - - - - - - - - - - - - - -
PackageSizeMD5 Checksum
Windows - -android_sdk_windows_m3-rc20a.zip59 MBa404b875708df7339ba77bdf2e08dc06
Mac OS X (intel) - -android_sdk_darwin_m3-rc20a.zip55 MB8fc29aeaa45eda84bfac854ebd02a6da
Linux (i386) - -android_sdk_linux_m3-rc20a.zip55 MB9196759df9b69cd89a220b156f133364
diff --git a/docs/html/tools/sdk/win-usb.jd b/docs/html/tools/sdk/win-usb.jd deleted file mode 100644 index d322340028432..0000000000000 --- a/docs/html/tools/sdk/win-usb.jd +++ /dev/null @@ -1,172 +0,0 @@ -page.title=Google USB Driver -@jd:body - -
-
-

In this document

-
    -
  1. Revisions
    2. -
  2. Downloading the Google USB Driver
    3. -
-

See also

-
    -
  1. Installing a USB Driver
    2. -
  2. Using Hardware Devices
    3. -
  3. Exploring the SDK
    4. -
-
-
- -

The Google USB driver is a downloadable component for the Android SDK, available -from the SDK Manager. The driver is for Windows only and provides the necessary drivers for the -following devices:

- -

* Or similar hardware on other carriers

- -

All other devices require Windows drivers provided by the hardware manufacturer, as listed in -the OEM USB Drivers document. The Galaxy Nexus -driver is also distributed by Samsung -(listed as model SCH-I515).

- -

Note: -If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. To start -developing with your device, also read Using -Hardware Devices.

- -

The sections below provide instructions on how to download and install the Google USB Driver -for Windows.

- - - - -

Revisions

- -

The sections below provide notes about successive revisions of the USB Driver -for Windows, as denoted by revision number. To determine what revision of the -USB Driver for Windows you are using, refer to the "Installed Packages" listing -in the Android SDK Manager.

- - - - -
- - -USB Driver for Windows, Revision 4 (December 2010) -
- -
-

Adds support for the Nexus S.

-
-
-
- -
- - -USB Driver for Windows, Revision 3 (January 2010) -
- -
-

Adds support for the Nexus One.

-
-
-
- -
- - -USB Driver for Windows, Revision 2 (November 2009) -
- -
-

Adds support for the Verizon Droid (or similar hardware on -other carriers).

-
-
-
- -
- - -USB Driver for Windows, Revision 1 (October 2009) -
- -
-

Initial release of the WinUsb-based driver, with support -for the T-Mobile G1 and myTouch 3G (and similar devices).

-
-
-
- - -

Downloading the Google USB Driver

- -
- -

Figure 1. The SDK Manager - with the Google USB Driver selected.

-
- -

The USB Driver for Windows is available for download as an optional SDK -component. You need the driver only if you are developing on Windows and -want to connect an Android-powered device (ADP, Nexus One, or Nexus S) to your -development environment over USB.

- -

To download the driver, use the Android SDK Manager tool that is -included with the Android SDK:

-
    -
  1. Launch the Android SDK Manager by double-clicking SDK Manager.exe, - at the root of your SDK directory.
    2. -
  2. Expand Extras.
    3. -
  3. Check Google USB Driver package and click Install.
    4. -
  4. Proceed to install the package. When done, the driver files are -downloaded into the <sdk>\extras\google\usb_driver\ directory.
    5. -
- -

For installation information, read Installing a USB Driver.

diff --git a/docs/html/training/contacts-provider/ContactsList.zip b/docs/html/training/contacts-provider/ContactsList.zip deleted file mode 100644 index d2a5cfb5a196a..0000000000000 Binary files a/docs/html/training/contacts-provider/ContactsList.zip and /dev/null differ diff --git a/docs/html/training/multiple-threads/threadsample.zip b/docs/html/training/multiple-threads/threadsample.zip deleted file mode 100644 index bdc3ccfd7040a..0000000000000 Binary files a/docs/html/training/multiple-threads/threadsample.zip and /dev/null differ