Главная » Android

Android studio sdk platforms

Содержание
  1. Installing the Android SDK
  2. Download
  3. Terms and Conditions
  4. 1. Introduction
  5. 2. Accepting this License Agreement
  6. 3. SDK License from Google
  7. 4. Use of the SDK by You
  8. 5. Your Developer Credentials
  9. 6. Privacy and Information
  10. 7. Third Party Applications
  11. 8. Using Android APIs
  12. 9. Terminating this License Agreement
  13. 10. DISCLAIMER OF WARRANTIES
  14. 11. LIMITATION OF LIABILITY
  15. 12. Indemnification
  16. 13. Changes to the License Agreement
  17. 14. General Legal Terms
  18. Android Studio
  19. Intelligent code editor
  20. Code templates and GitHub integration
  21. Multi-screen app development
  22. Virtual devices for all shapes and sizes
  23. Android builds evolved, with Gradle
  24. More about Android Studio
  25. System Requirements
  26. Windows
  27. Mac OS X
  28. Linux
  29. SDK Tools Release Notes
  30. Revisions

Installing the Android SDK

Android Studio provides everything you need to start developing apps for Android, including the Android Studio IDE and the Android SDK tools.

If you didn’t download Android Studio, go download Android Studio now, or switch to the stand-alone SDK Tools install instructions.

Before you set up Android Studio, be sure you have installed JDK 6 or higher (the JRE alone is not sufficient)—JDK 7 is required when developing for Android 5.0 and higher. To check if you have JDK installed (and which version), open a terminal and type javac -version . If the JDK is not available or the version is lower than 6, go download JDK.

To set up Android Studio on Windows:

  1. Launch the .exe file you just downloaded.
  2. Follow the setup wizard to install Android Studio and any necessary SDK tools.

On some Windows systems, the launcher script does not find where Java is installed. If you encounter this problem, you need to set an environment variable indicating the correct location.

Select Start menu > Computer > System Properties > Advanced System Properties. Then open Advanced tab > Environment Variables and add a new system variable JAVA_HOME that points to your JDK folder, for example C:\Program Files\Java\jdk1.7.0_21 .

The individual tools and other SDK packages are saved outside the Android Studio application directory. If you need to access the tools directly, use a terminal to navigate to the location where they are installed. For example:

To set up Android Studio on Mac OSX:

  1. Unzip the downloaded zip file, android-studio-ide- -mac.zip .
  2. Drag and drop Android Studio into the Applications folder.
  3. Open Android Studio and follow the setup wizard to install any necessary SDK tools.

Depending on your security settings, when you attempt to open Android Studio, you might see a warning that says the package is damaged and should be moved to the trash. If this happens, go to System Preferences > Security & Privacy and under Allow applications downloaded from, select Anywhere. Then open Android Studio again.

  • Follow the links to install the SDK outside of the Android Studio directories.

    • The individual tools and other SDK packages are saved outside the Android Studio application directory. If you need access the tools directly, use a terminal to navigate into the location where they are installed. For example:

    To set up Android Studio on Linux:

    1. Unpack the downloaded Tar file, android-studio-ide- -linux.zip , into an appropriate location for your applications.
    2. To launch Android Studio, navigate to the android-studio/bin/ directory in a terminal and execute studio.sh .

    You may want to add android-studio/bin/ to your PATH environmental variable so that you can start Android Studio from any directory.

    If the SDK is not already installed, follow the setup wizard to install the SDK and any necessary SDK tools.

    Note: You may also need to install the ia32-libs, lib32ncurses5-dev, and lib32stdc++6 packages. These packages are required to support 32-bit apps on a 64-bit machine.

    Android Studio is now ready and loaded with the Android developer tools, but there are still a couple packages you should add to make your Android SDK complete.

    The stand-alone SDK Tools package does not include a complete Android development environment. It includes only the core SDK tools, which you can access from a command line or with a plugin for your favorite IDE (if available).

    If you didn’t download the SDK tools, go download the SDK now, or switch to the Android Studio install instructions.

    To get started on Windows:

    Your download package is an executable file that starts an installer. The installer checks your machine for required tools, such as the proper Java SE Development Kit (JDK) and installs it if necessary. The installer then saves the Android SDK Tools to a specified the location outside of the Android Studio directories.

    1. Double-click the executable ( .exe file) to start the install.
    2. Make a note of the name and location where you save the SDK on your system—you will need to refer to the SDK directory later when using the SDK tools from the command line.
    3. Once the installation completes, the installer starts the Android SDK Manager.

    To get started on Mac OSX:

    Unpack the ZIP file you’ve downloaded. By default, it’s unpacked into a directory named android-sdk-mac_x86 . Move it to an appropriate location on your machine, such as a «Development» directory in your home directory.

    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 using the SDK tools from the command line.

    To get started on Linux:

    Unpack the .zip file you’ve downloaded. The SDK files are download separately to a user-specified directory.

    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 using the SDK tools from the command line.

    Troubleshooting Ubuntu
    • If you need help installing and configuring Java on your development machine, you might find these resources helpful:
      • https://help.ubuntu.com/community/Java
      • https://help.ubuntu.com/community/JavaInstallation
    • Here are the steps to install Java:

      1. If you are running a 64-bit distribution on your development machine, you need to install additional packages first. For Ubuntu 13.10 (Saucy Salamander) and above, install the libncurses5:i386 , libstdc++6:i386 , and zlib1g:i386 packages using apt-get :

        For earlier versions of Ubuntu, install the ia32-libs package using apt-get :

        The Android SDK tools are now ready to begin developing apps, but there are still a couple packages you should add to make your Android SDK complete.

        Then, select which SDK bundle you want to install:

        Источник

        Download

        Before installing Android Studio or the standalone SDK tools, you must agree to the following terms and conditions.

        Terms and Conditions

        1. Introduction

        2. Accepting this License Agreement

        3. SDK License from Google

        4. Use of the SDK by You

        5. Your Developer Credentials

        6. Privacy and Information

        7. Third Party Applications

        8. Using Android APIs

        9. Terminating this License Agreement

        10. DISCLAIMER OF WARRANTIES

        11. LIMITATION OF LIABILITY

        12. Indemnification

        13. Changes to the License Agreement

        You’re just a few steps away from building apps for Android!

        In a moment, you’ll be redirected to Installing the Android SDK.

        I have read and agree with the above terms and conditions

        Android Studio

        The official Android IDE

        • Android Studio IDE
        • Android SDK tools
        • Android 5.0 (Lollipop) Platform
        • Android 5.0 emulator system image with Google APIs

        Download Android Studio

        To get Android Studio or stand-alone SDK tools, visit developer.android.com/sdk/

        Intelligent code editor

        At the core of Android Studio is an intelligent code editor capable of advanced code completion, refactoring, and code analysis.

        The powerful code editor helps you be a more productive Android app developer.

        Code templates and GitHub integration

        New project wizards make it easier than ever to start a new project.

        Start projects using template code for patterns such as navigation drawer and view pagers, and even import Google code samples from GitHub.

        Multi-screen app development

        Build apps for Android phones, tablets, Android Wear, Android TV, Android Auto and Google Glass.

        With the new Android Project View and module support in Android Studio, it’s easier to manage app projects and resources.

        Virtual devices for all shapes and sizes

        Android Studio comes pre-configured with an optimized emulator image.

        The updated and streamlined Virtual Device Manager provides pre-defined device profiles for common Android devices.

        Android builds evolved, with Gradle

        Create multiple APKs for your Android app with different features using the same project.

        Manage app dependencies with Maven.

        Build APKs from Android Studio or the command line.

        More about Android Studio

        For more details about features available in Android Studio, read the overview at Android Studio.

        If you have been using Eclipse with ADT, be aware that Android Studio is now the official IDE for Android, so you should migrate to Android Studio to receive all the latest IDE updates. For help moving projects, see Migrating to Android Studio.

        System Requirements

        Windows

        • Microsoft® Windows® 8/7/Vista/2003 (32 or 64-bit)
        • 2 GB RAM minimum, 4 GB RAM recommended
        • 400 MB hard disk space
        • At least 1 GB for Android SDK, emulator system images, and caches
        • 1280 x 800 minimum screen resolution
        • Java Development Kit (JDK) 7
        • Optional for accelerated emulator: Intel® processor with support for Intel® VT-x, Intel® EM64T (Intel® 64), and Execute Disable (XD) Bit functionality

        Mac OS X

        • Mac® OS X® 10.8.5 or higher, up to 10.9 (Mavericks)
        • 2 GB RAM minimum, 4 GB RAM recommended
        • 400 MB hard disk space
        • At least 1 GB for Android SDK, emulator system images, and caches
        • 1280 x 800 minimum screen resolution
        • Java Runtime Environment (JRE) 6
        • Java Development Kit (JDK) 7
        • Optional for accelerated emulator: Intel® processor with support for Intel® VT-x, Intel® EM64T (Intel® 64), and Execute Disable (XD) Bit functionality

        On Mac OS, run Android Studio with Java Runtime Environment (JRE) 6 for optimized font rendering. You can then configure your project to use Java Development Kit (JDK) 6 or JDK 7.

        Linux

        • GNOME or KDE desktop
        • GNU C Library (glibc) 2.15 or later
        • 2 GB RAM minimum, 4 GB RAM recommended
        • 400 MB hard disk space
        • At least 1 GB for Android SDK, emulator system images, and caches
        • 1280 x 800 minimum screen resolution
        • Oracle® Java Development Kit (JDK) 7

        Tested on Ubuntu® 14.04, Trusty Tahr (64-bit distribution capable of running 32-bit applications).

        Источник

        SDK Tools Release Notes

        SDK Tools is a downloadable component for the Android SDK. It includes the complete set of development and debugging tools for the Android SDK. It is included with Android Studio.

        If you are already using the SDK and you want to update to the latest version of the SDK Tools, use the SDK Manager to get the update.

        Revisions

        The sections below provide notes about successive releases of the SDK Tools, as denoted by revision number. To determine what revision of the SDK Tools you are using, refer to the «Installed Packages» listing in the Android SDK Manager.

        For a summary of all known issues in SDK Tools, see http://tools.android.com/knownissues.

        SDK Tools, Revision 24.3.3 (June 2015)

        SDK Tools, Revision 24.3.2 (June 2015)

        SDK Tools, Revision 24.3.1 (June 2015)

        Caution: This release is known to contain issues which prevent builds from completing. We strongly recommend that you update to SDK Tools 24.3.2 as soon as possible.

        SDK Tools, Revision 24.3.0 (June 2015)

        Caution: This release is known to contain issues which prevent builds from completing. We strongly recommend that you update to SDK Tools 24.3.2 as soon as possible.

        SDK Tools, Revision 24.2.0 (May 2015)

        SDK Tools, Revision 24.1.2 (February 2015)

        SDK Tools, Revision 24.0.2 (December 2014)

        SDK Tools, Revision 24.0.1 (December 2014)

        SDK Tools, Revision 24.0.0 (December 2014)

        SDK Tools, Revision 23.0.5 (October 2014)

        SDK Tools, Revision 23.0.4 (October 2014)

        SDK Tools, Revision 23.0.2 (July 2014)

        SDK Tools, Revision 23.0.0 (June 2014)

        SDK Tools, Revision 22.6.4 (June 2014)

        SDK Tools, Revision 22.6.3 (April 2014)

        When you create an Android Wear virtual device in the AVD manager, a target API Level lower than 19 may be selected by default. Make sure you select the target API Level 19 when creating Android Wear virtual devices.

        SDK Tools, Revision 22.6.2 (March 2014)

        SDK Tools, Revision 22.6.1 (March 2014)

        Fixed a problem with virtual devices created using ADT 22.3 or earlier.

        If you created an Android Virtual Device using ADT 22.3 or earlier, the AVD may be listed as broken in the AVD Manager in 22.6.1. To fix this problem, select the virtual device on the AVD Manager and click Repair.

      2. Fixed a problem with the command line tools when creating virtual devices. (Issue 66740)
      3. Fixed a problem with the command line lint script.

    Known Issues:

    When you create an Android virtual device using the Nexus 5 device definition, you must enable the Use Host GPU option, otherwise the virtual device will not start.

    SDK Tools, Revision 22.6 (March 2014)

    The command line lint script ( tools\lint.bat on Windows platforms, tools/lint on other platforms) and the lint target on ant builds fail with the following error:

    Exception in thread «main» java.lang.NoClassDefFoundError: lombok/ast/AstVisitor

    As a temporary workaround, rename the file tools\lib\lombok-ast-0.2.2.jar to tools\lib\lombok-ast.jar . We will release an updated version of the tools with a fix for this issue as soon as possible.

  • Added support for Java 7 language features like multi-catch, try-with-resources, and the diamond operator. These features require version 19 or higher of the Build Tools. Try-with-resources requires minSdkVersion 19; the rest of the new language features require minSdkVersion 8 or higher.
  • Added new lint checks:
    • Security:
      • Look for code potentially affected by a SecureRandom vulnerability.
      • Check that calls to checkPermission use the return value.
    • Check that production builds do not use mock location providers.
    • Look for manifest values that are overwritten by values from Gradle build scripts.
  • Fixed a number of minor issues in the SDK and build system.
  • Emulator:
    • Fixed a problem with the emulator shutting down immediately for Android 1.5 on the Nexus One and Nexus S devices. (Issue 64945)
    • Fixed a problem with port numbers longer than four digits. (Issue 60024)
    • Fixed battery errors for the Nexus One and Nexus S devices. (Issue 39959)
    • Fixed a problem with paths or arguments that contain spaces on Windows platforms. (Issue 18317)
    • Fixed a problem with long path values on Windows platforms. (Issue 33336)
    • Fixed a problem with the -snapshot-list command line option on 64-bit systems. (Issue 34233)
  • Fixed an issue with RenderScript support. Using RenderScript support mode now requires version 19.0.3 of the Build Tools.

    • SDK Tools, Revision 22.3 (October 2013)

    SDK Tools, Revision 22.2.1 (September 2013)

    SDK Tools, Revision 22.2 (September 2013)

    directory.

  • Modified Tracer for OpenGL ES to support OpenGL ES 3.0.
  • Lint
    • Fixed problem with lint not detecting custom namespaces. (Issue 55673)
    • Fixed problem with the XML report including invalid characters. (Issue 56205)
    • Fixed command-line execution of lint to work in headless mode to support execution by build servers. (Issue 55820)
  • Improved support for path names with spaces in the Windows command-line tools.

    • SDK Tools, Revision 22.0.5 (July 2013)

    SDK Tools, Revision 22.0.4 (July 2013)

    SDK Tools, Revision 22.0.1 (May 2013)

    SDK Tools, Revision 22 (May 2013)

    SDK Tools, Revision 21.1 (February 2013)

    SDK Tools, Revision 21.0.1 (December 2012)

    SDK Tools, Revision 21 (November 2012)

    SDK Tools, Revision 20.0.3 (August 2012)

    SDK Tools, Revision 20.0.1 (July 2012)

    SDK Tools, Revision 20 (June 2012)

    SDK Tools, Revision 19 (April 2012)

    Note: This update of SDK Tools is only available through the Android SDK Manager. Use this tool to download and install this update.

    Dependencies:

    • Android SDK Platform-tools revision 9 or later.
    • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 18.0.0 and later. If you haven’t already, we highly recommend updating your ADT Plugin to 18.0.0.
    • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.

    Bug fixes:

    • Fixed an issue that prevented some developers from running the emulator with GPU acceleration.

    SDK Tools, Revision 18 (April 2012)

    Important: To download the new Android 4.0 system components from the Android SDK Manager, you must first update the SDK tools to revision 14 or later and restart the Android SDK Manager. If you do not, the Android 4.0 system components will not be available for download.

    Dependencies:

    • Android SDK Platform-tools revision 9 or later.
    • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 18.0.0 and later. If you haven’t already, we highly recommend updating your ADT Plugin to 18.0.0.
    • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.

    General notes:

    • Updated the SdkController app to encapsulate both sensor and multitouch emulation functionality.

    Bug fixes:

    • Fixed Ant issues where some jar libraries in the libs/ folder are not picked up in some cases.

    SDK Tools, Revision 17 (March 2012)

    Important: To download the new Android 4.0 system components from the Android SDK Manager, you must first update the SDK tools to revision 14 or later and restart the Android SDK Manager. If you do not, the Android 4.0 system components will not be available for download.

    Dependencies:

    • Android SDK Platform-tools revision 9 or later.
    • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 17.0.0 and later. If you haven’t already, we highly recommend updating your ADT Plugin to 17.0.0.
    • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.

    General notes:

    • Emulator
      • Added support for hardware accelerated graphics rendering. This feature requires an API Level 15, Revision 3 or later system image. (more info)
      • Added support for running Android x86 system images in virtualization mode on Windows and Mac OS X. (more info)

        Note: Use the Android SDK Manager to download and install x86 system images. Android x86 system images are not available for all API levels.

      • Added experimental support for multi-touch input by enabing the emulator to receive touch input from a USB-tethered physical Android device. (more info)
    • Added viewing of live detailed network usage of an app in DDMS. (more info)
    • ProGuard
      • Updated the bundled ProGuard tool to version 4.7. In addition to many new features, this update fixes the Conversion to Dalvik format failed with error 1 error some users have experienced.
      • Updated the default proguard.cfg file with better default flags for Android.
      • Split the ProGuard configuration file has been in half, with project specific flags kept in project and the generic Android flags distributed (and updated) with the tools themselves.
    • Build
      • Added a feature that allows you to run some code only in debug mode. Builds now generate a class called BuildConfig containing a DEBUG constant that is automatically set according to your build type. You can check the ( BuildConfig.DEBUG ) constant in your code to run debug-only functions.
      • Fixed issue when a project and its libraries include the same jar file in their libs folder. (more info)
      • Added support for custom views with custom attributes in libraries. Layouts using custom attributes must use the namespace URI http://schemas.android.com/apk/res-auto instead of the URI that includes the app package name. This URI is replaced with the app specific one at build time.
    • Lint
      • Updated Lint to check Android application code. Lint rules which previously performed pattern based searches in the application code (such as the unused resource check) have been rewritten to use the more accurate Java-style parse trees.
      • Added support for checking library projects. This change means that rules such as the unused resource check properly handle resources declared in a library project and referenced in a downstream project.
      • Added ability to suppress Lint warnings in Java code with the new @SuppressLint annotation, and in XML files with the new tools: namespace and ignore attribute. (more info)
      • New Lint checks:
        • Added check for Android API calls that require a version of Android higher than the minimum supported version. You can use the new @TargetApi annotation to suppress warnings when the code is wrapped in a system version condition. (more info)
        • Added over 20 new Lint rules, including checks for performance, XML layouts, manifest and file handling.

    SDK Tools, Revision 16 (December 2011)

    Important: To download the new Android 4.0 system components from the Android SDK Manager, you must first update the SDK tools to revision 14 or later and restart the Android SDK Manager. If you do not, the Android 4.0 system components will not be available for download.

    Dependencies:

    • Android SDK Platform-tools revision 9 or later.
    • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 16.0.0 and later. If you haven’t already, we highly recommend updating your ADT Plugin to 16.0.0.
    • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.

    General notes:

    • Added Lint tools to detect common errors in Android projects. (more info)
    • Added sensor emulation support, which allows the emulator to read sensor data from a physical Android device. (more info)
    • Added support for using a webcam to emulate a camera on Mac OS X.

    Bug fixes:

    • Snapshots now work for Android 4.0 system images.
    • Fixed several small issues for the build file. (Issue 21023, Issue 21267, Issue 21465, Issue 21525).

    SDK Tools, Revision 15 (October 2011)

    Important: To download the new Android 4.0 system components from the Android SDK Manager, you must first update the SDK tools to revision 14 or later and restart the Android SDK Manager. If you do not, the Android 4.0 system components will not be available for download.

    Dependencies:

    • Android SDK Platform-tools revision 9 or later.
    • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 15.0.0 and later. If you haven’t already, we highly recommend updating your ADT Plugin to 15.0.0.
    • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.

    Bug fixes:

    • Fixed emulator crash on Linux due to improper webcam detection (Issue 20952).
    • Fixed emulator issue when using the -wipe-data argument.
    • Fixed build issue when using RenderScript in projects that target API levels 11-13 (Issue 21006).
    • Fixed issue when creating an AVD using the GoogleTV addon (Issue 20963).
    • Fixed ant test (Issue 20979).
    • Fixed android update project (Issue 20535).
    • Fixed scrolling issue in the new Logcat panel of DDMS.
    • Fixed issue with MonkeyRunner (Issue 20964).
    • Fixed issues in the SDK Manager (Issue 20939, Issue 20607).

    SDK Tools, Revision 14 (October 2011)

    Important: To download the new Android 4.0 system components from the Android SDK Manager, you must first update the SDK tools to revision 14 and restart the Android SDK Manager. If you do not, the Android 4.0 system components will not be available for download.

    Dependencies:

    • Android SDK Platform-tools revision 8 or later.
    • If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 14.0.0 and later. If you haven’t already, we highly recommend updating your ADT Plugin to 14.0.0.
    • If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.

    General notes:

    • Added webcam support to Android 4.0 or later platforms to emulate rear-facing cameras when one webcam is present, and to emulate both rear-facing and front-facing cameras when two webcams are present. Webcam support is for Windows and Linux only. Mac support will come in a later release.
    • Changed default.properties to project.properties and build.properties to ant.properties . Any existing projects that you build with Ant must be updated with the android update project command.
    • Changed Ant build.xml file to support improvements to the build system and added and modified Ant commands to support these changes. For a list of Ant commands, see the Ant Command Reference.
    • Changed how library projects are built.
    • Improved incremental builds, so that resource compilation runs less frequently. Builds no longer run when you edit strings or layouts (unless you add a new id ) and no longer run once for each library project.
    • Introduced a «PNG crunch cache» that only runs on modified PNG files, instead of crunching all existing PNG files, all the time.
    • Revamped the SDK Manager UI (more info).

    For a complete overview of the build system changes and what you need to do to support them, see the Android Tools Project site.

    SDK Tools, Revision 13 (September 2011)

    If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 12.0.0 and later. If you haven’t already, we highly recommend updating your ADT Plugin to 12.0.0.

    If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.

    General notes:

    • Fix compilation issue in Ant ( dex step) when paths have spaces.
    • Fix issue in emulator installation when paths have spaces.
    • Fix issue when AVD paths have spaces.
    • Fix rendering issue when using emulator scaling (see more).

    SDK Tools, Revision 12 (July 2011)

    If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 12.0.0 and later. If you haven’t already, we highly recommend updating your ADT Plugin to 12.0.0.

    If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.

    General notes:

    • The AVD manager and emulator can now use system images compiled for ARM v7 and x86 CPUs.

    SDK Tools, Revision 11 (May 2011)

    If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 10.0.1 and later. If you haven’t already, we highly recommend updating your ADT Plugin to 10.0.1.

    If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.

    General notes:

    • Miscellaneous emulator changes to support Android 3.1.

    SDK Tools, Revision 10 (February 2011)

    If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 10.0.0 and later. After installing SDK Tools r10, we highly recommend updating your ADT Plugin to 10.0.0.

    If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.

    General notes:

    • The tools now automatically generate Java Programming Language source files (in the gen directory) and bytecode (in the res/raw directory) from your native .rs files

    SDK Tools, Revision 9 (January 2011)

    If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 9.0.0 and later. After installing SDK Tools r9, we highly recommend updating your ADT Plugin to 9.0.0.

    If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.

    Upgrading to SDK Tools r9:

    If you are upgrading to SDK Tools r9 from SDK Tools r7 or earlier, the default installed location for the adb tool has changed from /tools/adb to /platform-tools/adb . This means that you should add the new location to your PATH and modify any custom build scripts to reference the new location. Copying the adb executable from the new location to the old is not recommended, since subsequent updates to the SDK Tools will delete the file.

    General notes:

    • The default ProGuard configuration, proguard.cfg , now ignores the following classes:
      • classes that extend Preference
      • classes that extend BackupAgentHelper
    • Ant lib rules now allow you to override java.encoding , java.source , and java.target properties.
    • The default encoding for the javac Ant task is now UTF-8.
    • The LogCat view in DDMS now properly displays UTF-8 characters.
    • The SDK Manager is more reliable on Windows. For details on the improvements, see the Android Tools Project Site.
    • Early look at the new snapshot feature: To improve startup time for the emulator, you can enable snapshots for the system state. The emulator will then restore to the state when it last closed almost instantly. Note: The snapshot feature is still under active development and might not always perform as expected.
    • Fixed the missing JAR file error that prevented draw9patch from running.
    • Fixed the Windows launch scripts hierarchyviewer and ddms to support the new location of adb .
    • Known issues with emulator performance: Because the Android emulator must simulate the ARM instruction set architecture on your computer, emulator performance is slow. We’re working hard to resolve the performance issues and it will improve in future releases.

    SDK Tools, Revision 8 (December 2010)

    If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 8.0.0 and later. After installing SDK Tools r8, we highly recommend updating your ADT Plugin to 8.0.0.

    If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.

    Also note that SDK Tools r8 requires a new SDK component called Platform-tools. The new Platform-tools component lets all SDK platforms (Android 2.1, Android 2.2, and so on) use the same (latest) version of build tools such as adb , aapt , aidl , and dx . To download the Platform-tools component, use the Android SDK Manager, as described in Exploring the SDK

    Upgrading from SDK Tools r7:

    If you are upgrading to SDK Tools r8 from an earlier version, note that the the default installed location for the adb tool has changed from /tools/adb to /platform-tools/adb . This means that you should add the new location to your PATH and modify any custom build scripts to reference the new location. Copying the adb executable from the new location to the old is not recommended, since subsequent updates to the SDK Tools will delete the file.

    SDK Tools, Revision 7 (September 2010)

    If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 0.9.8 and later. After installing SDK Tools r7, we highly recommend updating your ADT Plugin to 0.9.8.

    General notes:

    • Added support for library projects that depend on other library projects.
    • Adds support for aidl files in library projects.
    • Adds support for extension targets in Ant build to perform tasks between the normal tasks: -pre-build , -pre-compile , and -post-compile .
    • Adds support for «headless» SDK update. See android -h update sdk for more information.
    • Fixes location control in DDMS to work in any locale not using ‘.’ as a decimal point.

    SDK Tools, Revision 6 (May 2010)

    If you are developing in Eclipse with ADT, note that this version of SDK Tools is designed for use with ADT 0.9.7 and later. After installing SDK Tools r6, we highly recommend updating your ADT Plugin to 0.9.7.

    The SDK Tools now support the use of library projects during development, a capability that lets you store shared Android application code and resources in a separate development project. You can then reference the library project from other Android projects and, at build time, the tools compile the shared code and resources as part of the dependent applications. More information about this feature is available in the Creating and Managing Projects document.

    If you are developing in Eclipse, ADT provides the equivalent library project support.

    SDK Tools, Revision 5 (March 2010)

    SDK Tools, Revision 4 (December 2009)

    This version of SDK Tools is compatible with ADT 0.9.5 and later, but not compatible with earlier versions. If you are developing in Eclipse with ADT, you must update your ADT plugin to version 0.9.5 or higher if you install SDK Tools r4 in your SDK.

    General notes:

    • Launcher script now forces GDK_NATIVE_WINDOW=true (linux only), to fix a compatibility issue between GTK and SWT.

    Android SDK and AVD Manager:

    • AVD Launch dialog now shows scale value.
    • Fixes potential NPE in SDK Manager on AVD launch, for older AVD with no skin name specified.
    • Fixes XML validation issue in on older Java versions.
    • No longer forces the use of Java 1.5 on Mac OS X.

    Emulator:

    • No longer limits the size of the system partition.

    Ant build tools:

    • .apk packaging now properly ignores vi swap files as well as hidden files.

    SDK Tools, Revision 3 (October 2009)

    This version of SDK Tools is compatible with ADT 0.9.4 and later, but not compatible with earlier versions. If you are developing in Eclipse with ADT, you must update your ADT plugin to version 0.9.4 or higher if you install SDK Tools r3 in your SDK.

    Android tool:

    • Adds new android create test-project and android update test-project commands to allow for greater flexibility in the location of the main and test projects.

    DDMS:

    • Adds a button to dump HPROF file for running applications (app must be able to write to the sdcard).
    • Button to start/stop profiling of a running application (app must be able to write to the sdcard). Upon stop, Traceview will automatically be launched to display the trace.
    • Fixed DDMS, Traceview, and the AVD Mananger/SDK Updater to run on Mac OS X 10.6.
    • Fixed screenshot support for devices running 32-bit framebuffer.

    Android SDK and AVD Manager:

    • Provides a new UI that lets you set options for controlling the emulator skin, screen size/density, and scale factor used when launching an AVD.
    • Provides improved AVD creation UI, which lets you customize the hardware properties of your AVDs.
    • Now enforces dependencies between platforms and tools components, and between SDK add-ons and platforms.

    Layoutopt, a new tool for optimizing layouts:

    The SDK Tools r3 package includes layoutopt , a new command-line tool that helps you optimize your layout hierarchies. When run against your layout files, the tool analyzes their hierarchies and notifies you of inefficiencies and other potential issues. The tool also provides simple solutions for the issues it finds. For usage, see layoutopt.

    Источник

    Читайте также:  Nokia android one recovery
    Оцените статью
    © 2024 Ваши гэджеты