In this document
- Android Sdk Manager Download Mac Installer
- Android Sdk Manager Download Mac High Sierra
- Android Sdk Manager Download Zip
- 4. Adding Platforms and Other Components
8/10 - Download Android SDK Mac gratis. Crea applicazioni per dispositivi Android, scarica Android SDK gratis per Mac, il kit di strumenti di sviluppo con tante librerie API utili a programmare. Setup Android SDK on a Mac. GitHub Gist: instantly share code, notes, and snippets. Use Command line tools or SDK Manager. Download and Install.
See also
This page describes how to install the Android SDKand set up your development environment for the first time.
If you encounter any problems during installation, see theTroubleshooting section at the bottom ofthis page.
Updating?
If you already have an Android SDK, use the Android SDK and AVD Manager tool to installupdated tools and new Android platforms into your existing environment. For information about how todo that, see Adding SDK Components.
Step 1. Preparing Your Development Computer
Before getting started with the Android SDK, take a moment to confirm thatyour development computer meets the SystemRequirements. 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 DevelopmentTools (ADT) Plugin—the recommended path if you are new toAndroid—make sure that you have a suitable version of Eclipseinstalled on your computer as described in theSystem Requirements document.If you need to install Eclipse, you can download it from this location:
The 'Eclipse Classic' version is recommended. Otherwise, a Java orRCP version of Eclipse is recommended.
Step 2. Downloading the SDK Starter Package
The SDK starter package is not a fulldevelopment environment—it includes only the core SDK Tools, which you canuse to download the rest of the SDK components (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
.zip
or .tgz
package (instead of the SDK installer), unpackit to a safe location on your machine. By default, the SDK files are unpackedinto a directory named android-sdk-<machine-platform>
.If you downloaded the Windows installer (
.exe
file), run it now and it will checkwhether the proper Java SE Development Kit (JDK) is installed (installing it, if necessary), theninstall 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 torefer to the SDK directory later, when setting up the ADT plugin and when usingthe SDK tools from the command line.
Step 3. Installing the ADT Plugin for Eclipse
Android offers a custom plugin for the Eclipse IDE, called AndroidDevelopment Tools (ADT), that is designed to give you a powerful, integratedenvironment in which to build Android applications. It extends the capabilitesof Eclipse to let you quickly set up new Android projects, create an applicationUI, debug your applicationsusing the Android SDK tools, and even export signed (or unsigned) APKs in orderto distribute your application. In general, developing in Eclipse with ADT is ahighly 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 forstep-by-step installation instructions, then return here to continue thelast step in setting up your Android SDK.
If you prefer to work in a different IDE, you do not need toinstall Eclipse or ADT. Instead, you can directly use the SDK tools to build anddebug your application. The Introductionto Android application development outlines the major steps that you need to complete whendeveloping in Eclipse or other IDEs.
Step 4. Adding Platforms and Other Components
The last step in setting up your SDK is using the Android SDK and AVD Manager (atool included in the SDK starter package) to download essential SDK components into your developmentenvironment.
The SDK uses a modular structure that separates the major parts of the SDK—Android platformversions, add-ons, tools, samples, and documentation—into a set of separately installablecomponents. The SDK starter package, which you've already downloaded, includes only a singlecomponent: the latest version of the SDK Tools. To develop an Android application, you also need todownload at least one Android platform and the associated platform tools. You can add othercomponents and platforms as well, which is highly recommended.
If you used the Windows installer, when you complete the installation wizard, it will launch theAndroid SDK and AVD Manager with a default set of platforms and other components selectedfor you to install. Simply click Install to accept the recommended set ofcomponents and install them. You can then skip to Step 5, but werecommend you first read the section about the Available Components tobetter understand the components available from the Android SDK and AVD Manager.
You can launch the Android SDK and AVD Manager in one of the following ways:
- From within Eclipse, select Window > Android SDK and AVD Manager.
- On Windows, double-click the
SDK Manager.exe
file at the root of the AndroidSDK directory. - On Mac or Linux, open a terminal and navigate to the
tools/
directory in theAndroid SDK, then execute:
To download components, use the graphical UI of the Android SDK and AVDManager to browse the SDK repository and select new or updatedcomponents (see figure 1). The Android SDK and AVD Manager installs the selected components inyour SDK environment. For information about which components you should download, see Recommended Components.
Figure 1. The Android SDK and AVD Manager'sAvailable Packages panel, which shows the SDK components that areavailable for you to download into your environment.
Available Components
By default, there are two repositories of components for your SDK: AndroidRepository and Third party Add-ons.
The Android Repository offers these types of components:
- SDK Tools — Contains tools for debugging and testing your applicationand other utility tools. These tools are installed with the Android SDK starter package and receiveperiodic updates. You can access these tools in the
<sdk>/tools/
directory ofyour SDK. To learn more aboutthem, see SDK Tools in thedeveloper guide. - SDK Platform-tools — Contains platform-dependent tools for developingand debugging your application. These tools support the latest features of the Android platform andare typically updated only when a new platform becomes available. You can access these tools in the
<sdk>/platform-tools/
directory. To learn more about them, see Platform Tools in thedeveloper guide. - Android platforms — An SDK platform isavailable for every production Android platform deployable to Android-powered devices. EachSDK platform component includes a fully compliant Android library, system image, sample code,and emulator skins. To learn more about a specific platform, see the list of platforms that appearsunder the section 'Downloadable SDK Components' on the left part of this page.
- USB Driver for Windows (Windows only) — Contains driver filesthat you can install on your Windows computer, so that you can run and debugyour applications on an actual device. You do not need the USB driver unlessyou plan to debug your application on an actual Android-powered device. If youdevelop on Mac OS X or Linux, you do not need a special driver to debugyour application on an Android-powered device. See Using Hardware Devices for more informationabout developing on a real device.
- Samples — Contains the sample code and apps availablefor each Android development platform. If you are just getting started withAndroid development, make sure to download the samples to your SDK.
- Documentation — Contains a local copy of the latestmultiversion documentation for the Android framework API.
![Android Sdk Manager Download Mac Android Sdk Manager Download Mac](/uploads/1/1/7/8/117837212/780280237.jpg)
The Third party Add-ons provide components that allow you to create a developmentenvironment using a specific Android external library (such as the Google Maps library) or acustomized (but fully compliant) Android system image. You can add additional Add-on repositories byclicking Add Add-on Site.
Recommended Components
The SDK repository contains a range of components that you can download.Use the table below to determine which components you need, based on whether youwant to set up a basic, recommended, or full development environment:
Environment | SDK Component | Comments |
---|---|---|
Basic | SDK Tools | If you've just installedthe SDK starter package, then you already have the latest version of this component. TheSDK Tools component is required to develop an Android application. Make sure you keep this up todate. |
SDK Platform-tools | This includes more tools that are requiredfor application development. These tools are platform-dependent and typically update only whena new SDK platform is made available, in order to support new features in the platform. Thesetools are always backward compatible with older platforms, but you must be sure that you havethe latest version of these tools when you install a new SDK platform. | |
SDK platform | You need to download | |
+ | ||
Recommended (plus Basic) | Documentation | The Documentation component is useful because it lets you work offline andalso look up API reference information from inside Eclipse. |
Samples | The Samples components give you source code that you can use to learn aboutAndroid, load as a project and run, or reuse in your own app. Note that multiplesamples components are available — one for each Android platform version. Whenyou are choosing a samples component to download, select the one whose API Levelmatches the API Level of the Android platform that you plan to use. | |
Usb Driver | The Usb Driver component is needed only if you are developing on Windows andhave an Android-powered device on which you want to install your application fordebugging and testing. For Mac OS X and Linux platforms, nospecial driver is needed. | |
+ | ||
Full (plus Recommended) | Google APIs | The Google APIs add-on gives your application access to the Maps externallibrary, which makes it easy to display and manipulate Maps data in yourapplication. |
Additional SDK Platforms | If you plan to publish your application, you will want to downloadadditional platforms corresponding to the Android platform versions on which youwant the application to run. The recommended approach is to compile yourapplication against the lowest version you want to support, but test it againsthigher versions that you intend the application to run on. You can test yourapplications 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 components, you're ready to startdeveloping Android apps. The next section describes the contents of the Android SDK to familiarizeyou with the components you've just installed.
For more information about using the Android SDK and AVD Manager, see the Adding SDK Components 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'sinside.
The table below describes the full SDK directory contents, with componentsinstalled.
Name | Description | ||
---|---|---|---|
add-ons/ | Contains add-ons to the Android SDK developmentenvironment, which let you develop against external libraries that are available on somedevices. | ||
docs/ | A full set of documentation in HTML format, including the Developer's Guide,API Reference, and other information. To read the documentation, load thefile offline.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 (adb ) as well as other tools that youdon't typically use directly. These tools are separate from the development tools in the tools/ directory because these tools may be updated in order to support newfeatures in the latest Android platform. | ||
platforms/ | Contains a set of Android platform versions that you can developapplications against, each in a separate directory. | ||
<platform>/ | Platform version directory, for example 'android-11'. All platform version directories containa similar set of files and subdirectory structure. Each platform directory also includes theAndroid library (android.jar ) that is used to compile applications against theplatform 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, suchas the emulator, the Android SDK and AVD Manager, ddms , hierarchyviewer and more. The tools in this directory may be updated at any time using the Android SDK and AVDManager and are independent of platform releases. | ||
SDK Readme.txt | A file that explains how to perform the initial setup of your SDK,including how to launch the Android SDK and AVD Manager tool on allplatforms. | ||
SDK Manager.exe | Windows SDK only. A shortcut that launches the Android SDK and AVDManager tool, which you use to add components to your SDK. |
Optionally, you might want to add the location of the SDK's
How to update your PATHtools/
andplatform-tools
to your PATH
environment variable, to provide easyaccess to the tools.Adding both
tools/
and platform-tools/
to your PATH lets you runcommand line tools without needing tosupply the full path to the tool directories. Depending on your operating system, you caninclude these directories in your PATH in the following way:- On Windows, right-click on My Computer, and select Properties. Under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path (under System Variables). Add the full path to the
tools/
andplatform-tools/
directories to the path. - On Linux, edit your
~/.bash_profile
or~/.bashrc
file. Look for a line that sets the PATH environment variable and add the full path to thetools/
andplatform-tools/
directories to it. If you don't see a line setting the path, you can add one: - On a Mac OS X, look in your home directory for
.bash_profile
and proceed as for Linux. You can create the.bash_profile
if you don't already have one.
Next Steps
Once you have completed installation, you are ready tobegin developing applications. Here are a few ways you can get started:
Set up the Hello World application
- If you have just installed the SDK for the first time, go to the Hello World tutorial. The tutorial takes you step-by-step through the process of setting up your first Android project, including setting up an Android Virtual Device (AVD) on which to run the application.
Following the Hello World tutorial is an essentialfirst step in getting started with Android development.
Learn about Android
- Take a look at the Dev Guide and the types of information it provides.
- Read an introduction to Android as a platform in What is Android?
- Learn about the Android framework and how applications run on it in Application Fundamentals.
- Take a look at the Android framework API specification in the Reference tab.
Explore the development tools
- Get an overview of the development tools that are available to you.
- Read the Introduction to Androidapplication development.
- Read Using Hardware Devices to learnhow to set up an Android-powered device so you can run and test your application.
Follow the Notepad tutorial
- The Notepad Tutorial shows you how to build a full Android application and provides helpful commentary on the Android system and API. The Notepad tutorial helps you bring together the important design and architectural concepts in a moderately complex application.
Following the Notepad tutorial is an excellentsecond step in getting started with Android development.
Explore some code
- The Android SDK includes sample code and applications for each platformversion. You can browse the samples in the Resources tab or download theminto your SDK using the Android SDK and AVD Manager. Once you've downloaded thesamples, you'll find them in
<sdk>/samples/<platform>/
.
Visit the Android developer groups
- Take a look at the Community pages to see a list of Android developers groups. In particular, you might want to look at the Android Developers group to get a sense for what the Android developer community is like.
Troubleshooting
Ubuntu Linux Notes
- If you need help installing and configuring Java on your development machine, you might find these resources helpful:
- Here are the steps to install Java and Eclipse, prior to installing the Android SDK and ADT Plugin.
- If you are running a 64-bit distribution on your development machine, you need to install the
ia32-libs
package usingapt-get:
: - Next, install Java:
- The Ubuntu package manager does not currently offer an Eclipse 3.3 version for download, so we recommend that you download Eclipse from eclipse.org (http://www.eclipse.org/ downloads/). A Java or RCP version of Eclipse is recommended.
- Follow the steps given in previous sections to install the SDK and the ADT plugin.
- If you are running a 64-bit distribution on your development machine, you need to install the
Other Linux Notes
- If JDK is already installed on your development computer, please take a moment to make sure that it meets the version requirements listed in the System Requirements. In particular, note that some Linux distributions may include JDK 1.4 or Gnu Compiler for Java, both of which are not supported for Android development.
SDK Tools is a downloadable component for the Android SDK. It includes thecomplete set of development and debugging tools for the Android SDK.
If you are new to the Android SDK, the SDK starter package installs thelatest revision of the SDK Tools in the
<sdk>/tools
directory.If you are already using the SDK and you want to update to the latest versionof the SDK Tools, use the Android SDK Manager to get theupdate, rather than downloading a new SDK starter package. For more informationabout how to update, see Exploring the SDK.
Revisions
The sections below provide notes about successive releases ofthe SDK Tools, as denoted by revision number. To determine what revision of the SDKTools 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 21.1.0(February 2013)
- Android SDK Platform-tools revision 16 or later.
- If you are developing in Eclipse with ADT, note that the SDK Tools r21.1.0 is designed for use with ADT 21.1.0 and later. If you haven't already, update your ADT Plugin to 21.1.0.
- If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
- Improved error reporting in
dx
when dex merging fails in the build system. - Added more than 15 new Lint checks, including checks for overriding older APIs, XML resource problems, graphic asset issues and manifest tags.
- Added new aapt feature to compile resources.
SDK Tools, Revision 21.0.1(December 2012)
- Android SDK Platform-tools revision 16 or later.
- If you are developing in Eclipse with ADT, note that the SDK Tools r21.0.1 is designed for use with ADT 21.0.1 and later. If you haven't already, update your ADT Plugin to 21.0.1.
- If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
- Build
- Updated build to detect and handle package name conflicts between an application and the libraries it depends on. Libraries cannot share package names unless all of them share the same package name. (Issue 40152, Issue 40273)
- Added a flag to disable dex merging to deal with cases where merging could generate a broken dex file. If this happens to your project, add the following setting to your
project.properties
file:dex.disable.merger=true
This setting causes the build system to revert to the older, slower dex processing that does not pre-dex libraries.
- Renderscript
- Added support for Filterscript compilation.
- Added new project setting to control the Renderscript compilation target separately from an Android project. Adding the following line to a
project.properties
file causes Renderscript code to be compiled for Android API Level 17, while the containing application can target a different (lower) API level: Previously, the Renderscript compilation target was tied to theandroid:minSdkVersion
setting in the manifest. (Issue 40487)
- Lint
- Corrected check for
0px
values in style XML elements. (Issue 39601) - Fixed incorrect flagging of formatting strings. (Issue 39758)
- Fixed problem where
tools:ignore
directive in the manifest file was ignored by the Lint tool. (Issue 40136) - Fixed problem with flagging a wakelock release inside a conditional. (Issue 40424)
- Fixed incorrect reporting of missing
layout_width
andlayout_height
XML fields. (Issue 38958) - Fixed handling of custom namespace attributes.
- Added fixes for filtering out library project warnings.
- Removed warnings about missing classes before a build.
- Corrected check for
- Fixed problem with UI Automator Viewer execution script where Android tools directory is not set.
- Fixed problem with the SDK Manager so that it auto-selects the most recently released platform on startup.
- Fixed Java finding script to look for the currently supported version of Java (1.6 or higher).
- Fixed the SDK Manager launcher in the ADT bundle so that it can properly launch the SDK Manager program when it is placed at the root of the bundle.
SDK Tools, Revision 21(November 2012)
- Android SDK Platform-tools revision 16 or later.
- If you are developing in Eclipse with ADT, note that the SDK Tools r21 is designed for use with ADT 21.0.0 and later. If you haven't already, update your ADT Plugin to 21.0.0.
- If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
- Build System
- Added a flag that sets jumbo mode for DEX files, which allows a larger number of strings in the DEX files. Enable this mode by adding the following line to the
project.properties
file of your project: - Improved the build time by pre-dexing libraries (both JAR files and library projects).
- Updated the build to generate
R
resource classes for library projects with only the IDs needed by the libraries, reducing the risk of hitting DEX file limits for fields and methods. - Improved the build so that several editing features (code completion, resource chooser, go to declaration) properly handle library project resources.
- Added a flag that sets jumbo mode for DEX files, which allows a larger number of strings in the DEX files. Enable this mode by adding the following line to the
- Lint
- Added over 25 new lint rules for resources, locale settings, layout files, incorrect use of
SparseArray
andPowerManager.WakeLock
and manifest issues. - Updated reporting to include errors in library projects if the library project is in the list of projects to be checked.
- Added a new
lint
target to the Ant build system for easier integration with continuous build systems. - Added new
--sources
and--classpath
arguments to point to sources with different directory structures. - Improved the XML export function to support the Jenkins Lint plugin.
- Added support for class file flow analysis.
- Added over 25 new lint rules for resources, locale settings, layout files, incorrect use of
- Android Virtual Devices (AVD)
- Added new Device Definitions tab in the AVD Manager for configuring standard size and Nexus virtual devices.
- Improved emulators so that they launch with a skin that is dynamically generated and reflects the actual hardware configured in the AVD Manager.
- Improved support for developing Android apps on MIPS-based devices with new MIPS System Images for Android Virtual Devices.
- Added
jobb
tool for creating and encrypting APK Expansion Files. (more info) - Improved the Android JUnit test runner to allow a test to be run on all connected devices simultaneously.
- Fixed manifest merger to properly adapt library classes in the merged manifest.
SDK Tools, Revision 20.0.3(August 2012)
- Android SDK Platform-tools revision 12 or later.
- If you are developing in Eclipse with ADT, note that the SDK Tools r20.0.3 is designed for use with ADT 20.0.3 and later. If you haven't already, update your ADT Plugin to 20.0.3.
- If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
- Fixed problem with cached download lists in SDK Manager.
SDK Tools, Revision 20.0.1(July 2012)
- Android SDK Platform-tools revision 12 or later.
- If you are developing in Eclipse with ADT, note that the SDK Tools r20.0.1 is designed for use with ADT 20.0.1 and later. If you haven't already, update your ADT Plugin to 20.0.1.
- If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
- Fixed wrong check on build state that forced repetitive Java code recompilation.
- Fixed problems with running more than one emulator and running multiple emulatorswith GPU acceleration.
- Improved resize algorithm for better rendering on scaled emulator windows.
- Fixed a bug in the
lint
check for unprotected broadcast receivers to ignoreunprotected receivers for default Android actions. - Fixed build issue for projects using Renderscript.
- Fixed memory leak in the emulator.
SDK Tools, Revision 20(June 2012)
- Android SDK Platform-tools revision 12 or later.
- If you are developing in Eclipse with ADT, note that the SDK Tools r20 is designed for use with ADT 20.0.0 and later. If you haven't already, we highly recommend updating your ADT Plugin to 20.0.0.
- If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.
- Added new Device Monitor application, grouping Android debugging tools into asingle application, including ddms, traceview, hierarchyviewer and Tracer for GLES. (more info)
- Added new System Trace new tool for tracing Android system activity. This tool allow youto capture a slice of system activity, plus additional information tagged from the Settings> Developer Options > Monitoring: Enable traces or with specific calls added to yourapplication code.
- Build System
- Added automatic merging of library project manifest files into the includingproject's manifest. Enable this feature with the
manifestmerger.enabled
property. - Added automatic ProGuard support for the
aapt -G
flag. This change causesthe build system to generate a temporary ProGuardkeep-rules
file containing classes thatare referenced from XML files (such as custom views) and pass this to ProGuard at shrink time. Thiscan make the resulting APK much smaller when using just a small portion of a large library project(such as the Android Support library), since the catch-all rules to keep all custom views from thedefault ProGuard configuration file have also been removed. - Added two ProGuard configuration files for use in projects:
proguard-android-optimize.txt
which enables optimizations andproguard-android.txt
whichdisables them.
- Added automatic merging of library project manifest files into the includingproject's manifest. Enable this feature with the
- SDK Manager
- Improved caching to reduce downloading of repository definitions.
- Added Tools > Manage Add-on Sites option to improve performance by allowing temporary deactivation of third-party sites if they are loading slowly.
- Added settings for the SDK Manager download cache (SDK Manager > Tools >Options).
- Build
- Fixed problem where test projects did not have access to the full classpath of testedprojects, including Library Projects and third-party jars.
- Fixed deployment logic so that applications with embedded tests can now be deployedand tested like test applications, including code coverage information.
- Fixed Ant support for testing projects with libraries.
SDK Tools, Revision 19(April 2012)
Note: This update of SDK Tools is only available throughthe Android SDK Manager. Use this tool todownload and install this update.
- Android SDK Platform-tools revision 9 or later.
- If you are developing in Eclipse with ADT, note that the SDK Tools r19 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.
- Fixed an issue that prevented some developers from running the emulator with GPUacceleration.
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.
- Android SDK Platform-tools revision 9 or later.
- If you are developing in Eclipse with ADT, note that the SDK Tools r18 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.
- Updated the SdkController app to encapsulate both sensor and multitouch emulation functionality.
- Fixed Ant issues where some jar libraries in the
libs/
folder are not picked upin 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.
- Android SDK Platform-tools revision 9 or later.
- If you are developing in Eclipse with ADT, note that the SDK Tools r17 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.
- Emulator
- Added support for hardware accelerated graphics rendering. This feature requires anAPI Level 15, Revision 3 or later system image.(more info)
- Added support for running Android x86 system images in virtualization mode onWindows and Mac OS X.(more info) Note: Use the Android SDK Manager to download andinstall 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 haveexperienced. - Updated the default
proguard.cfg
file with better default flags for Android. - Split the ProGuard configuration file has been in half, with project specific flagskept in project and the generic Android flags distributed (and updated) with the toolsthemselves.
- Updated the bundled ProGuard tool to version 4.7. In addition to many new features,this update fixes the
- Build
- Added a feature that allows you to run some code only in debug mode. Builds nowgenerate a class called
BuildConfig
containing aDEBUG
constant that isautomatically 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 usingcustom attributes must use the namespace URI
http://schemas.android.com/apk/res-auto
insteadof the URI that includes the app package name. This URI is replaced with the app specific one atbuild time.
- Added a feature that allows you to run some code only in debug mode. Builds nowgenerate a class called
- Lint
- Updated Lint to check Android application code. Lint rules which previouslyperformed pattern based searches in the application code (such as the unused resource check) havebeen rewritten to use the more accurate Java-style parse trees.
- Added support for checking library projects. This change means that rules such asthe unused resource check properly handle resources declared in a library project and referenced ina 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 andignore 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.
- Added check for Android API calls that require a version of Android higher than the minimum supported version. You can use the new
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.
- Android SDK Platform-tools revision 9 or later.
- If you are developing in Eclipse with ADT, note that the SDK Tools r16 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.
- 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.
- 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.
- Android SDK Platform-tools revision 9 or later.
- If you are developing in Eclipse with ADT, note that the SDK Tools r15 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.
- 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.
- Android SDK Platform-tools revision 8 or later.
- If you are developing in Eclipse with ADT, note that the SDK Tools r14 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.
- 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
toproject.properties
andbuild.properties
toant.properties
. Any existing projects that you build with Ant must be updated with theandroid 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 Antcommands, see theAnt CommandReference. - 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 (moreinfo).
For a complete overview of the build system changes and what you need to do to support them,see the Android Tools Projectsite.
SDK Tools, Revision 13(September 2011)
If you are developing in Eclipse with ADT, note that the SDK Tools r13 is designed for use withADT 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 ApacheAnt 1.8 or later.
- 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 the SDK Tools r12 is designed for use withADT 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 ApacheAnt 1.8 or later.
- 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 the SDK Tools r11 is designed for use withADT 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 ApacheAnt 1.8 or later.
- Miscellaneous emulator changes to support Android 3.1.
SDK Tools, Revision 10(February 2011)
If you are developing in Eclipse with ADT, note that the SDK Tools r10 isdesigned for use with ADT 10.0.0 and later. After installing SDK Tools r10, wehighly recommend updating your ADT Plugin to 10.0.0.
If you are developing outside Eclipse, you must have ApacheAnt 1.8 or later.
- The tools now automatically generate Java Programming Language source files (in the
gen
directory) and bytecode (in theres/raw
directory) from your native.rs
files
SDK Tools, Revision 9(January 2011)
If you are developing in Eclipse with ADT, note that the SDK Tools r9 isdesigned for use with ADT 9.0.0 and later. After installing SDK Tools r9, wehighly recommend updating your ADT Plugin to 9.0.0.
If you are developing outside Eclipse, you must have ApacheAnt 1.8 or later.
If you are upgrading to SDK Tools r9 from SDK Tools r7 or earlier, the default installed locationfor the
adb
tool has changed from <SDK>/tools/adb
to<SDK>/platform-tools/adb
. This means that you shouldadd the new location to your PATH and modify any custom build scripts toreference the new location. Copying the adb
executable from the newlocation to the old is not recommended, since subsequent updates to the SDKTools will delete the file.- The default ProGuard configuration,
proguard.cfg
, now ignores the following classes:- classes that extend
Preference
- classes that extend
BackupAgentHelper
- classes that extend
- Ant lib rules now allow you to override
java.encoding
,java.source
, andjava.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 canenable snapshots for the system state. The emulator will then restore to the state when it lastclosed almost instantly. Note: The snapshot feature is still under activedevelopment and might not always perform as expected.
- Fixed the missing JAR file error that prevented
draw9patch
from running. - Fixed the Windows launch scripts
hierarchyviewer
andddms
to support the new location ofadb
. - Known issues with emulator performance: Because the Android emulator must simulate the ARMinstruction set architecture on your computer, emulator performance is slow. We're working hard toresolve 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 SDK Tools r8 isdesigned for use with ADT 8.0.0 and later. After installing SDK Tools r8, wehighly recommend updating your ADT Plugin to 8.0.0.
If you are developing outside Eclipse, you must have ApacheAnt 1.8 or later.
Also note that SDK Tools r8 requires a new SDK component calledPlatform-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 buildtools such as
adb
, aapt
, aidl
, anddx
. To download the Platform-tools component, use the Android SDKManager, as described in Exploring theSDKIf you are upgrading to SDK Tools r8 from an earlier version, note that thethe default installed location for the
adb
tool has changed from<SDK>/tools/adb
to<SDK>/platform-tools/adb
. Full free minecraft download mac os. This means that you shouldadd the new location to your PATH and modify any custom build scripts toreference the new location. Copying the adb
executable from the newlocation to the old is not recommended, since subsequent updates to the SDKTools will delete the file.- All SDK platforms now support Library Projects.
- Support for a true debug build. Developers no longer need to add the
android:debuggable
attribute to the<application>
tag in the manifest — the build tools addthe attribute automatically. In Eclipse/ADT, all incremental builds are assumedto be debug builds, so the tools insertandroid:debuggable='true'
.When exporting a signed release build, the tools do not add the attribute. InAnt, aant debug
command automatically inserts theandroid:debuggable='true'
attribute, whileant release
does not. Ifandroid:debuggable='true'
is manually set, thenant release
will actually do a debug build, rather than a releasebuild. - Automatic ProGuard support in release builds. Developers generate a ProGuardconfiguration file using the
android
tool — the build toolsthen automatically run ProGuard against the project sources during the build.For more information, see the ProGuarddocumentation. - New overridable Ant javac properties:
java.encoding
,java.source
, andjava.target
(default values are'ascii', '1.5', and '1.5', respectively). - New UI for the HierarchyViewer tool.
SDK Tools, Revision 7(September 2010)
If you are developing in Eclipse with ADT, note that SDK Tools r7 isdesigned for use with ADT 0.9.8 and later. After installing SDK Tools r7, wehighly recommend updating your ADT Plugin to 0.9.8.
- 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 thenormal 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 adecimal point.
SDK Tools, Revision 6(May 2010)
If you are developing in Eclipse with ADT, note that SDK Tools r6 isdesigned for use with ADT 0.9.7 and later. After installing SDK Tools r6, wehighly recommend updating your ADT Plugin to 0.9.7.
Android Sdk Manager Download Mac Installer
The SDK Tools now support the use of library projects duringdevelopment, a capability that lets you store shared Android applicationcode and resources in a separate development project. You can then reference thelibrary project from other Android projects and, at build time, the toolscompile 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, ADTprovides the equivalent library project support.
SDK Tools, Revision 5(March 2010)
- If you are developing in Eclipse with ADT, note that SDK Tools r5 isdesigned for use with ADT 0.9.6 and later. After installing SDK Tools r5, wehighly recommend updating your ADT Plugin to 0.9.6.
- For Mac OS platforms, OS X 10.4.x (Tiger) is no longerofficially supported.
- Fixes SSL download for the standalone version of the SDK Updater.
- Fixes issue with 64-bit JVM on Windows.
- Adds support for platform samples components.
- Improves support for dependency between components.
- AVDs now sorted by API level.
- The AVD creation dialog now enforces a minimum SD card size of 9MB.
- Prevents deletion of running AVDs.
- Settings are now automatically saved, no need to click 'Apply'.
- Emulator now requires SD card to be 9MB or more.
- Fixes
layoutopt.bat
to execute correctly on Windows.
SDK Tools, Revision 4(December 2009)
SDK Tools r4 is compatible with ADT 0.9.5 and later, but notcompatible with earlier versions. If you are developing in Eclipse with ADT, youmust update your ADT plugin to version 0.9.5 or higher if youinstall SDK Tools r4 in your SDK.
- Launcher script now forces GDK_NATIVE_WINDOW=true (linux only), to fix acompatibility issue between GTK and SWT.
- AVD Launch dialog now shows scale value.
- Fixes potential NPE in SDK Manager on AVD launch, for older AVD with noskin name specified.
- Fixes XML validation issue in on older Java versions.
- No longer forces the use of Java 1.5 on Mac OS X.
- No longer limits the size of the system partition.
Android Sdk Manager Download Mac High Sierra
- .apk packaging now properly ignores vi swap files as well as hidden files.
SDK Tools, Revision 3(October 2009)
SDK Tools r3 is compatible with ADT 0.9.4 and later, but notcompatible with earlier versions. If you are developing in Eclipse with ADT, youmust update your ADT plugin to version 0.9.4 or higher if youinstall SDK Tools r3 in your SDK.
- Adds new
android create test-project
andandroid updatetest-project
commands to allow for greater flexibility in the location of themain and test projects.
- Adds a button to dump HPROF file for running applications (app must be ableto write to the sdcard).
- Button to start/stop profiling of a running application (app must be able towrite to the sdcard). Upon stop, Traceview will automatically be launched todisplay the trace.
- Fixed DDMS, Traceview, and the AVD Mananger/SDK Updater to run on Mac OS X10.6.
- Fixed screenshot support for devices running 32-bit framebuffer.
- Provides a new UI that lets you set options for controllingthe emulator skin, screen size/density, and scale factor used when launchingan AVD.
- Provides improved AVD creation UI, which lets you customize the hardwareproperties of your AVDs.
- Now enforces dependencies between platforms and tools components, andbetween SDK add-ons and platforms.
Android Sdk Manager Download Zip
The SDK Tools r3 package includes
layoutopt
, a new command-linetool that helps you optimize your layout hierarchies. When run against yourlayout files, the tool analyzes their hierarchies and notifies you ofinefficiencies and other potential issues. The tool also provides simplesolutions for the issues it finds. For usage, see layoutopt.