Sdk platform tools release notes android studio

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

     14. General Legal Terms

     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 Platforms Release Notes

     See Also

     This document provides release information about the SDK Platform packages required for app development. If you want details about the features and APIs added in each Android version, instead read the highlights in the About section.

     In order to compile your application against a particular version of Android, you must use the SDK Manager to download and install the SDK Platform for that release. If you want to test your application on an emulator, you must also download at least one System Image for that Android version.

     Each platform release includes system images that support a specific processor architecture, such as ARM EABI, Intel x86 or MIPS. Platform releases also include a system image that contains Google APIs. The SDK Manager lists available platform system images under each platform version header, for example:

     • ARM EABI v7a System Image
     • Intel x86 Atom System Image
     • MIPS System Image
     • Google APIs

     To determine what revisions of an Android platform you have installed, refer to the Packages listing in the Android SDK Manager.

     Important: To download the most recent Android system components from the Android SDK Manager, you must first update the SDK Tools to the most recent release and restart the SDK Manager. If you do not, the latest Android system packages may not be available for download.

     Android 5.1

     Revision 1 (March 2015)

     Initial release for Android 5.1 (API level 22).

     • Android SDK Platform-tools r22 or higher is required.
     • Android SDK Tools 23.0.5 or higher is required.

     Android 5.0

     Revision 2 (December 2014)

     Updated layouts in the Support Library and fixed various issues.

     • Android SDK Platform-tools r21 or higher is required.
     • Android SDK Tools 23.0.5 or higher is required.

     Revision 1 (October 2014)

     Initial release for Android 5.0 (API level 21).

     • Android SDK Platform-tools r21 or higher is required.
     • Android SDK Tools 23.0.5 or higher is required.

     Device Definitions

     The platform includes the following new device definitions for use in creating Android Virtual Devices in the AVD Manager:

     • Nexus 6 (5.96″, 1440 x 2560, Normal 560dpi screen)
     • Nexus 9 (8.9″, 2048 x 1536, X-Large xhdpi screen)

     Android 4.4W

     Revision 2 (October 2014)

     Updated the rendering library.

     • Android SDK Platform-tools r20 or higher is required.
     • Android SDK Tools 23.0 or higher is required.

     Revision 1 (June 2014)

     Initial release for Android Wear.

     • Android SDK Platform-tools r20 or higher is required.
     • Android SDK Tools 23.0 or higher is required.

     Device Definitions

     The platform includes the following device definitions for use in creating Android Virtual Devices in the AVD Manager:

     • Android Wear Round (320 x 320, hdpi)
     • Android Wear Square (320 x 320, hdpi)

     Android 4.4

     Revision 2 (December 2013)

     Maintenance release. The system version is 4.4.2.

     Dependencies: Android SDK Platform-tools r19 or higher is required. Android SDK Tools 22.3 or higher is recommended.

     Revision 1 (October 2013)

     Initial release. The system version is 4.4.

     Dependencies: Android SDK Platform-tools r19 or higher is required. Android SDK Tools 22.3 or higher is recommended.

     Google APIs System Image

     Revision 4 (March 2014)

     This release includes Google Play services version 4.3, allowing you to test your application in an emulator using the latest Google Play services.

     Revision 3 (February 2014)

     This release includes Google Play services version 4.2.42, allowing you to test your application in an emulator using the latest Google Play services.

     Revision 2 (December 2013)

     This release includes Google Play services version 4.0.33.

     Revision 1 (October 2013)

     Initial release. This release includes Google Play services version 4.0.30.

     Android 4.3

     Revision 2 (August 2013)

     Maintenance update. The system version is 4.3.

     Dependencies: Android SDK Platform-tools r18 or higher is required. Android SDK Tools 22.0.4 or higher is recommended.

     Revision 1 (July 2013)

     Initial release. The system version is 4.3.

     Dependencies: Android SDK Platform-tools r18 or higher is required. Android SDK Tools 22.0.4 or higher is recommended.

     Google APIs System Image

     Revision 3 (September 2013)

     Maintenance update. This release includes Google Play services version 3.2.65.

     Revision 2 (August 2013)

     Maintenance update. This release includes Google Play services version 3.2.25.

     Revision 1 (July 2013)

     Initial release. This release includes Google Play services version 3.1.58.

     Android 4.2

     Revision 2 (February 2013)

     Maintenance update. The system version is 4.2.2.

     Dependencies: SDK Tools r21 or higher is required.

     Revision 1 (November 2012)

     Initial release. The system version is 4.2.

     Dependencies: SDK Tools r20 or higher is required.

     Device Definitions

     The platform includes the following device definitions for use in creating Android Virtual Devices in the AVD Manager:

     • Nexus 7 (7.3″, 800 x 1280, Large tvdpi screen)
     • Galaxy Nexus (4.7″, 720 x 1280, Normal xhdpi screen)
     • Nexus S (4.0″, 480 x 800, Normal hdpi screen)
     • Nexus One (3.7″, 480 x 720, Normal hdpi screen)
     • 10.1″ WXGA Tablet (1280 x 800, X-Large mdpi screen)
     • 7.0″ WSVGA Tablet (1024 x 600, Large mdpi screen)
     • 5.4″ FWVGA (480 x 854, Large mdpi screen)
     • 5.1″ WVGA (480 x 800, Large mdpi screen)
     • 4.7″ WXGA (1280 x 720, Normal xhdpi screen)
     • 4.65″ 720p (720 x 1280, Normal xhdpi screen)
     • 4.0″ WVGA (480 x 800, Normal hdpi screen)
     • 3.7″ WVGA (480 x 800, Normal hdpi screen)
     • 3.7″ FWVGA slider (480 x 854, Normal hdpi screen)
     • 3.4″ WQVGA (240 x 432, Normal ldpi screen)
     • 3.3″ WQVGA (240 x 400, Normal ldpi screen)
     • 3.2″ QVGA ADP2 (320 x 480, Normal mdpi screen)
     • 3.2″ HVGA slider ADP1 (320 x 480, Normal mdpi screen)
     • 2.7″ QVGA slider (240 x 320, Small ldpi screen)
     • 2.7″ QVGA (240 x 320, Small ldpi screen)

     Android 4.1

     Revision 3 (October 2012)

     Maintenance update. The system version is 4.1.2.

     Dependencies: SDK Tools r20 or higher is required.

     Revision 2 (July 2012)

     Maintenance update. The system version is 4.1.1.

     Dependencies: SDK Tools r20 or higher is required.

     Revision 1 (June 2012)

     Initial release. The system version is 4.1.0.

     Dependencies: SDK Tools r20 or higher is required.

     Emulator Skins

     The downloadable platform includes the following emulator skins:

     • QVGA (240×320, low density, small screen)
     • WQVGA400 (240×400, low density, normal screen)
     • WQVGA432 (240×432, low density, normal screen)
     • HVGA (320×480, medium density, normal screen)
     • WVGA800 (480×800, high density, normal screen)
     • WVGA854 (480×854 high density, normal screen)
     • WXGA720 (1280×720, extra-high density, normal screen)
     • WSVGA (1024×600, medium density, large screen)
     • WXGA800-7in (1280×800, high density, large screen) new
     • WXGA800 (1280×800, medium density, xlarge screen)

     To test your application on an emulator that represents the Nexus 7 tablet device, you can create an AVD with the new WXGA800-7in skin. For best performance, make sure to enable graphics acceleration in the emulator configuration.

     Android 4.0.3

     Revision 3 (March 2012)

     Maintenance update. The system version is 4.0.4.

     Note: This system image includes support for emulator hardware graphics acceleration when used with SDK Tools r17 or higher. (more info)

     Dependencies: SDK Tools r17 or higher is required.

     Revision 2 (January 2012)

     Maintenance update. The system version is 4.0.3.

     Dependencies: SDK Tools r14 or higher is required.

     Revision 1 (December 2011)

     Initial release. The system version is 4.0.3.

     Dependencies: SDK Tools r14 or higher is required.

     Emulator Skins

     The downloadable platform includes the following emulator skins:

     • QVGA (240×320, low density, small screen)
     • WQVGA400 (240×400, low density, normal screen)
     • WQVGA432 (240×432, low density, normal screen)
     • HVGA (320×480, medium density, normal screen)
     • WVGA800 (480×800, high density, normal screen)
     • WVGA854 (480×854 high density, normal screen)
     • WXGA720 (1280×720, extra-high density, normal screen)
     • WSVGA (1024×600, medium density, large screen)
     • WXGA (1280×800, medium density, xlarge screen)

     Android 4.0

     Android 4.0, Revision 2 (December 2011)

     Maintenance update. The system version is 4.0.2.

     Dependencies: SDK Tools r14 or higher is required.

     Android 4.0, Revision 1 (October 2011)

     Initial release. The system version is 4.0.1.

     Dependencies: SDK Tools r14 or higher is required.

     Emulator Skins

     The downloadable platform includes the following emulator skins:

     • QVGA (240×320, low density, small screen)
     • WQVGA400 (240×400, low density, normal screen)
     • WQVGA432 (240×432, low density, normal screen)
     • HVGA (320×480, medium density, normal screen)
     • WVGA800 (480×800, high density, normal screen)
     • WVGA854 (480×854 high density, normal screen)
     • WXGA720 (1280×720, extra-high density, normal screen) new
     • WSVGA (1024×600, medium density, large screen) new
     • WXGA (1280×800, medium density, xlarge screen)

     To test your application on an emulator that represents the latest Android device, you can create an AVD with the new WXGA720 skin (it’s an xhdpi, normal screen device). Note that the emulator currently doesn’t support the new on-screen navigation bar for devices without hardware navigation buttons, so when using this skin, you must use keyboard keys Home for the Home button, ESC for the Back button, and F2 or Page-up for the Menu button.

     However, due to performance issues in the emulator when running high-resolution screens such as the one for the WXGA720 skin, we recommend that you primarily use the traditional WVGA800 skin (hdpi, normal screen) to test your application.

     Android 3.2

     Android 3.2, Revision 1 (July 2011)

     Emulator Skins

     The downloadable platform includes the following emulator skin:

     • WXGA (1280×800, medium density, xlarge screen)

     For more information about how to develop an application that displays and functions properly on all Android-powered devices, see Supporting Multiple Screens.

     Android 3.1

     Android 3.1, Revision 3 (July 2011)

     Requires SDK Tools r12 or higher.

     Improvements to the platform’s rendering library to support the visual layout editor in the ADT Eclipse plugin. This revision allows for more drawing features in ADT and fixes several bugs in the previous rendering library. It also unlocks several editor features that were added in ADT 12.

     Android 3.1, Revision 2 (May 2011)

     Requires SDK Tools r11 or higher.

     Fixes an issue with the visual layout editor rendering library that prevented Android 3.1 from running in ADT.

     Android 3.1, Revision 1 (May 2011)

     Requires SDK Tools r11 or higher.

     Emulator Skins

     The downloadable platform includes the following emulator skin:

     • WXGA (1280×800, medium density, xlarge screen)

     For more information about how to develop an application that displays and functions properly on all Android-powered devices, see Supporting Multiple Screens.

     Android 3.0

     Android 3.0, Revision 2 (July 2011)

     Requires SDK Tools r12 or higher.

     Improvements to the platform’s rendering library to support the visual layout editor in the ADT Eclipse plugin. This revision allows for more drawing features in ADT and fixes several bugs in the previous rendering library. It also unlocks several editor features that were added in ADT 12.

     Android 3.0, Revision 1 (February 2011)

     Requires SDK Tools r10 or higher.

     Emulator Skins

     The downloadable platform includes the following emulator skin:

     • WXGA (1280×800, medium density, xlarge screen)

     Android 2.3.4

     Android 2.3.4, Revision 1 (May 2011)

     Requires SDK Tools r11 or higher.

     Emulator Skins

     The downloadable platform includes a set of emulator skins that you can use for modeling your application in different screen sizes and resolutions. The emulator skins are:

     • QVGA (240×320, low density, small screen)
     • WQVGA400 (240×400, low density, normal screen)
     • WQVGA432 (240×432, low density, normal screen)
     • HVGA (320×480, medium density, normal screen)
     • WVGA800 (480×800, high density, normal screen)
     • WVGA854 (480×854 high density, normal screen)

     Android 2.3.3

     Android 2.3.3, Revision 2 (July 2011)

     Requires SDK Tools r12 or higher.

     Improvements to the platform’s rendering library to support the visual layout editor in the ADT Eclipse plugin. This revision allows for more drawing features in ADT and fixes several bugs in the previous rendering library. It also unlocks several editor features that were added in ADT 12.

     Android 2.3.3, Revision 1 (February 2011)

     Requires SDK Tools r9 or higher.

     Emulator Skins

     The downloadable platform includes a set of emulator skins that you can use for modeling your application in different screen sizes and resolutions. The emulator skins are:

     • QVGA (240×320, low density, small screen)
     • WQVGA400 (240×400, low density, normal screen)
     • WQVGA432 (240×432, low density, normal screen)
     • HVGA (320×480, medium density, normal screen)
     • WVGA800 (480×800, high density, normal screen)
     • WVGA854 (480×854 high density, normal screen)

     Android 2.3

     Android 2.3, Revision 1 (December 2010)

     Requires SDK Tools r8 or higher.

     Emulator Skins

     The downloadable platform includes a set of emulator skins that you can use for modeling your application in different screen sizes and resolutions. The emulator skins are:

     • QVGA (240×320, low density, small screen)
     • WQVGA400 (240×400, low density, normal screen)
     • WQVGA432 (240×432, low density, normal screen)
     • HVGA (320×480, medium density, normal screen)
     • WVGA800 (480×800, high density, normal screen)
     • WVGA854 (480×854 high density, normal screen)

     Android 2.2

     Android , Revision 3 (July 2011)

     Requires SDK Tools r12 or higher.

     Improvements to the platform’s rendering library to support the visual layout editor in the ADT Eclipse plugin. This revision allows for more drawing features in ADT and fixes several bugs in the previous rendering library. It also unlocks several editor features that were added in ADT 12.

     Android , Revision 2 (July 2010)

     Requires SDK Tools r6 or higher.

     System Image:

     • Adds default Search Widget.
     • Includes proper provisioning for the platform’s Backup Manager. For more information about how to use the Backup Manager, see Data Backup.
     • Updates the Android 2.2 system image to FRF91.

     Android , Revision 1 (May 2010)

     Requires SDK Tools r6 or higher.

     Adds support for building with Android library projects. See SDK Tools, r6 for information.

     Emulator Skins

     The downloadable platform includes a set of emulator skins that you can use for modeling your application in different screen sizes and resolutions. The emulator skins are:

     • QVGA (240×320, low density, small screen)
     • WQVGA (240×400, low density, normal screen)
     • FWQVGA (240×432, low density, normal screen)
     • HVGA (320×480, medium density, normal screen)
     • WVGA800 (480×800, high density, normal screen)
     • WVGA854 (480×854 high density, normal screen)

     Источник

     Читайте также:  Беспроводные наушники beats для андроид