Download tools android sdk


Installing Android SDK Tools | CodePath Android Cliffnotes

The Android software development kit (SDK) includes different components, including SDK Tools, Build Tools, and Platform Tools. The SDK Tools primarily includes the stock Android emulator, hierarchy viewer, SDK manager, and ProGuard. The Build Tools primarily include aapt (Android packaging tool to create .APK), dx (Android tool that converts .java files to .dex files). Platform Tools include the Android debug shell, sqlite3 and Systrace.

The Android SDK can be installed automatically using the latest version of Gradle or downloading the Android SDK manually in several different ways. Below is an overview of all different approaches.

Installing the Android SDK (Automated Way)

Gradle 2.2.0 now supports downloading automatically dependencies. Make sure to upgrade to the latest Gradle version. The Gradle plugin to manage dependencies is now deprecated.

Installing for Ubuntu Linux

If you are using Ubuntu 15.04 or 15.10, make sure to install the following packages. Otherwise, you may notice No such file or directory when running trying to execute the aapt program that is part of the Android SDK toolset:

sudo apt-get install libc6-dev-i386 lib32z1 default-jdk

Installing the Android SDK (via Homebrew)

Assuming you have OS X running, you can use Homebrew to install the Android SDK.

  1. Install Homebrew - package manager for OSX
  2. run brew tap caskroom/cask brew cask install android-sdk

This will install the Android SDK tools in /usr/local/Cellar/android-sdk/<version number>

Installing the Android SDK (Manual Way)

You will need to download the Android SDK without Android Studio bundled. Go to Android SDK and navigate to the SDK Tools Only section. Copy the URL for the download that's appropriate for your build machine OS.

Use wget with the correct SDK URL:

$ wget https://dl.google.com/android/repository/tools_r25.2.3-macosx.zip

Unzip and place the contents within your home directory. The directory names can be anything you like, but save the files in somewhere easy to find (i.e. ~/android-sdk).

Run the sdkmanager tool:

$ tools/bin/sdkmanager --update $ tools/bin/sdkmanager "platforms;android-25" "build-tools;25.0.2" "extras;google;m2repository" "extras;android;m2repository" $ tools/bin/sdkmanager --licenses

Now it's time to set your build environment's PATH variable and other variables that will be use to locate Android.

Edit your .bash_profile file. If you're not using bash, edit the right config file for your environment.

# Android export ANDROID_HOME=/Users/ciandroid/android-sdk-macosx export PATH=$PATH:$ANDROID_HOME/tools

Save and quit. Reload .bash_profile:

$ source ~/.bash_profile

Installing via the GUI

At the prompt, type android and hit Enter to launch the Android SDK Manager in a window. If this doesn't work, your PATH variable has not been set up with the Android SDK location.

You will want to install the same Android SDK packages on your build machine as you did to get Gradle running locally. Before you begin, take a look at the build.gradle file in your project.

Packages to install

Here are the SDK package names you'll definitely wish to select:

  • Tools > Android SDK Tools
  • Tools > Android SDK Platform-tools
  • Tools > Android SDK Build-tools
  • One version of the Android Platform. E.g., Android 5.1.1 (API 22). It should be the one you named in the android: compileSdkVersion section of your build.gradle file.

You will also want to download the extras:

  • Android Support Repository
  • Android Support Library

Note: Choose the Android SDK Build-tools for the version of Android that you listed in the build.gradle file as the android: buildToolsVersion target. If your build.gradle says

android { buildToolsVersion '21' ... }

then make sure to download that API version in the Android SDK Manager.

Installing via the Command Line

You can also download the SDK packages using the command line with the --no-ui parameter.

android update sdk --no-ui --all

If you want to be selective about installing, you can use android list to view all the packages and apply the --filter option for selective installs:

sudo android update sdk --no-ui --filter platform-tools,tools

If you decide to be selective about which packages to be installed, make sure to include the extra Android Maven repository. Otherwise, you may not be able to use the latest support design library.

android update sdk --no-ui --all --filter extra-android-m2repository

There is currently no filter to install the build tools directly. See this ticket for more information.

guides.codepath.com

SDK Tools | Android Developers

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

If you are new to the Android SDK, the SDK starter package installs the latest 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 version of the SDK Tools, use the Android SDK Manager to get the update, rather than downloading a new SDK starter package. For more information about how to update, see Exploring the SDK.

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 21.1.0 (February 2013)

Dependencies:
  • 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.
General Notes:
  • 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)

Dependencies:
  • 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.
General Notes:
  • 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: renderscript.target = 17 Previously, the Renderscript compilation target was tied to the android:minSdkVersion setting in the manifest. (Issue 40487)
Bug fixes:
  • 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 and layout_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.
  • 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)

Dependencies:
  • 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.
General Notes:
  • 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: set dex.force.jumbo=true
    • 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.
  • Lint
    • Added over 25 new lint rules for resources, locale settings, layout files, incorrect use of SparseArray and PowerManager.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.
  • 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.
Bug fixes:
  • Fixed manifest merger to properly adapt library classes in the merged manifest.

SDK Tools, Revision 20.0.3 (August 2012)

Dependencies:
  • 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.
Bug fixes:
  • Fixed problem with cached download lists in SDK Manager.

SDK Tools, Revision 20.0.1 (July 2012)

Dependencies:
  • 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.
Bug fixes:
  • Fixed wrong check on build state that forced repetitive Java code recompilation.
  • Fixed problems with running more than one emulator and running multiple emulators with GPU acceleration.
  • Improved resize algorithm for better rendering on scaled emulator windows.
  • Fixed a bug in the lint check for unprotected broadcast receivers to ignore unprotected receivers for default Android actions.
  • Fixed build issue for projects using Renderscript.
  • Fixed memory leak in the emulator.

SDK Tools, Revision 20 (June 2012)

Dependencies:
  • 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.
General notes:
  • Added new Device Monitor application, grouping Android debugging tools into a single 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 you to capture a slice of system activity, plus additional information tagged from the Settings > Developer Options > Monitoring: Enable traces or with specific calls added to your application code.
  • Build System
    • Added automatic merging of library project manifest files into the including project's manifest. Enable this feature with the manifestmerger.enabled property.
    • Added automatic ProGuard support for the aapt -G flag. This change causes the build system to generate a temporary ProGuard keep-rules file containing classes that are referenced from XML files (such as custom views) and pass this to ProGuard at shrink time. This can 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 the default ProGuard configuration file have also been removed.
    • Added two ProGuard configuration files for use in projects: proguard-android-optimize.txt which enables optimizations and proguard-android.txt which disables them.
  • 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).
Bug fixes:
  • Build
    • Fixed problem where test projects did not have access to the full classpath of tested projects, including Library Projects and third-party jars.
    • Fixed deployment logic so that applications with embedded tests can now be deployed and 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 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 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.
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 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.
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 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.
General notes:
  • Emulator
  • 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 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.
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:

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

Dependencies:

If you are developing in Eclipse with ADT, note that the SDK Tools r13 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)

Dependencies:

If you are developing in Eclipse with ADT, note that the SDK Tools r12 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)

Dependencies:

If you are developing in Eclipse with ADT, note that the SDK Tools r11 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)

Dependencies:

If you are developing in Eclipse with ADT, note that the SDK Tools r10 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)

Dependencies:

If you are developing in Eclipse with ADT, note that the SDK Tools r9 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 <SDK>/tools/adb to <SDK>/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:
  • 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)

Dependencies:

If you are developing in Eclipse with ADT, note that SDK Tools r8 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 <SDK>/tools/adb to <SDK>/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:
  • 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 add the attribute automatically. In Eclipse/ADT, all incremental builds are assumed to be debug builds, so the tools insert android:debuggable="true". When exporting a signed release build, the tools do not add the attribute. In Ant, a ant debug command automatically inserts the android:debuggable="true" attribute, while ant release does not. If android:debuggable="true" is manually set, then ant release will actually do a debug build, rather than a release build.
  • Automatic ProGuard support in release builds. Developers generate a ProGuard configuration file using the android tool — the build tools then automatically run ProGuard against the project sources during the build. For more information, see the ProGuard documentation.
  • New overridable Ant javac properties: java.encoding, java.source, and java.target (default values are "ascii", "1.5", and "1.5", respectively).
  • New UI for the HierarchyViewer tool.

SDK Tools, Revision 7 (September 2010)

Dependencies:

If you are developing in Eclipse with ADT, note that SDK Tools r7 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)

Dependencies:

If you are developing in Eclipse with ADT, note that SDK Tools r6 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.

Library projects:

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)

Dependencies:
  • If you are developing in Eclipse with ADT, note that SDK Tools r5 is designed for use with ADT 0.9.6 and later. After installing SDK Tools r5, we highly recommend updating your ADT Plugin to 0.9.6.
  • For Mac OS platforms, OS X 10.4.x (Tiger) is no longer officially supported.
SDK and AVD Manager:
  • 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:
  • Emulator now requires SD card to be 9MB or more.
Layoutopt:
  • Fixes layoutopt.bat to execute correctly on Windows.

SDK Tools, Revision 4 (December 2009)

Dependencies:

SDK Tools r4 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)

Dependencies:

SDK Tools r3 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.

stuff.mit.edu

Download Android SDK / Command Line Tools [Windows, Mac, Linux]

Full Android Studio installation is always recommended but there are scenarios where people especially developers are interested in using only certain packages such as Android SDK and Command Line tools. Well, for them, Google offers separate packages that can be downloaded and implemented manually. The benefit of command line is the familiarity and more control. Further, if you look at the download size, these tools occupy quite less space compared with the full installation of Android Studio. We have linked the latest Android SDK tools / Command Line tools ahead which you can download and implement.

The Command Line tools exist for users who are quite familiar with the commands and don’t want to familiarize themselves with evolving GUIs. As mentioned, the greater control entices but command line experience also allows you to modify tasks to the very low-level with tags and sorts which are otherwise hidden in the GUI. Lastly, the space savings are also there. Not only does these tools require less offline storage but you don’t need high bandwidth to download them in the first place. Read more to find out download links for Android SDK tools / Command line tools.

Download Android SDK Tools / Command Line Tools

As the Android SDK is present on all major Desktop Operating Systems (Windows, Mac and Linux), we have provided links for downloading Android SDK Tools / Command Line tools on all of these.

If you are looking to only install Android Platform Tools (ADB and Fastboot), read: Download ADB, Fastboot Android SDK Platform Tools

To read more about Android Studio 3.0 and Android O, read: Download Android Studio 3.0 Canary Preview 2

SDK Tools Changelog

Following is the descriptive changelog for SDK Tools.

SDK Tools, Revision 26.0.2 (April 2017)

  • Changes:When creating an AVD with avdmanager, it is no longer necessary to specify –tag if the package specified by –package only contains a single image (as is the case for all images currently distributed by Google).

SDK Tools, Revision 26.0.1 (March 2017)

  • Changes:Hierarchy Viewer and Pixel Perfect tools returned to Android Device Monitor (the command-line versions are still removed, as of revision 25.3.0)

SDK Tools, Revision 26.0.0 (March 2017)

  • Dependencies:Android SDK Platform-Tools revision 24 or later.
  • Changes:tools/android now attempts to reproduce the functionality of android in tools prior to version 25.3.0 by invoking the new tools.All avd, target, and device commands should work as before.sdk commands will be translated to similar commands using tools/bin/sdkmanager on a best-effort basis.tools/bin/avdmanager now supports the list target command.

SDK Tools, Revision 25.3.0 (March 2017)

  • Dependencies:Android SDK Platform-Tools revision 24 or later.
  • Changes:Android Emulator is removed from this package and moved to a different SDK directory.android avd command-line functionality replaced with new avdmanager tool.Obsolete/deprecated tools have been removed:androidddmsdraw9patchhierarchyviewertraceviewant scriptsProject and activity templatesExecutables have been moved to bin/:jobblintmonkeyrunnerscreenshot2UiautomatorviewerEnhanced sdkmanager:View and accept all licenses from the command lineImproved verbose-mode package list

SDK Tools, Revision 25.2.5 (January 2017)

  • Dependencies:Android SDK Platform-Tools revision 24 or later.Android Emulator bug fixes:Fixed a crash on async socket reconnect.Fixed a crash on Mac when glDeleteTextures() is called after the corresponding context was destroyed.

www.teamandroid.com

Download ADB, Fastboot - Android SDK Platform Tools

You can now download ADB and Fastboot (Android SDK Platform Tools) officially from Google. Android nerds like us have used ADB, Fastboot and other tools at some point in using Android devices. To install an OTA update, flash factory image or simply to unlock bootloader of our phone, these Android SDK platform tools have been an essential part. Normally, to use ADB or Fastboot you have to download Android SDK / Android Studio and set it up on your computer. This requires you to download the whole package which is about 1GB in size. That’s a lot if you only need the two most popular Android SDK platform tools: Fastboot and ADB.

Recently we covered the Minimal ADB and Fastboot toolkit by a developer, but it is always better to download these tools from the official source. The latest ADB, Fastboot can be downloaded for Windows, Mac and Linux. They are available in a ZIP package that you download and extract it anywhere in your computer where you want to use it. And the total size is just around 10MB. The smallest of these command line downloads are about 200MB in size. You do not need so much of it if you just want to perform various ABB and Fastboot related functions on your phone.

Third party releases of ADB and Fastboot can never be fully trusted or you never know if they are malicious in any way. These tools directly from Google mean you always have the most up-to-date Android SDK platform tools and should never have compatibility with any Android device.

As new Android versions release, ages old releases of ADB and Fastboot are no longer compatible with these phones. If you try to unlock a Pixel phone’s bootloader using the old Fastboot version, the process will fail and you may end up with a bricked phone. Similarly, you need to have an updated ADB tool. As platforms update and newer releases are available, Google makes sure they are fixed as soon as possible and newer version is out soon. You can see that below in the official changelog provided by Google.

If you are a developer, it is recommended to download ADB, Fastboot or update them directly from inside the SDK Manager. This ensures the tools are saved to the right place with the rest of your Android SDK tools and easily updated.

Download ADB and Fastboot for Windows, Mac, Linux

The latest releases of Android SDK Platform Tools are available below and you can download ADB and Fastboot for various platforms: Windows, Mac and Linux. This page will always have the latest ADB / Fastboot binaries that are also included with the latest release of Android Studio / SDK Manager.

Download SDK Platform-Tools for Windows: platform-tools-latest-windows.zip

Download SDK Platform-Tools for Mac: platform-tools-latest-darwin.zip

Download SDK Platform-Tools for Linux: platform-tools-latest-linux.zip

[UPDATED: June 2017]

Android SDK Platform Tools – Changelog

For all the past releases, this is the official changelog of these Android SDK Platform Tools by Google. You can see how often Google update the tools and make sure all bugs are fixed.

26.0.0 (June 2017)
  • Updated with the release of Android O final SDK (API level 26)
25.0.5 (April 24, 2017)
  • Fixed adb sideload of large updates on Windows, manifesting as “std::bad_alloc”.
  • Fixed adb problems with some Windows firewalls, manifesting as “cannot open transport registration socketpair”.
  • Both adb --version and fastboot --version now include the install path.
  • Changed adb to not resolve localhost to work around misconfigured VPN.
  • Changed adb to no longer reset USB devices on Linux, which could affect other attached USB devices.

Looking for SDK Platform-Tools 25.0.5? We have the older version of ADB, Fastboot available below:

25.0.4 (March 16, 2017)
  • Added experimental libusb support to Linux and Mac adb

To use the libusb backend, set the environment variable ADB_LIBUSB=true before launching a new adb server. The new adb host-features command will tell you whether or not you’re using libusb.

To restart adb with libusb and check that it worked, use adb kill-server; ADB_LIBUSB=1 adb start-server; adb host-features. The output should include “libusb”.

In this release, the old non-libusb implementation remains the default.

  • fastboot doesn’t hang 2016 MacBook Pros anymore
  • Fixed Systrace command line capture on Mac
25.0.3 (December 16, 2016)
  • Fixed fastboot bug causing Android Things devices to fail to flash
25.0.2 (December 12, 2016)
  • Updated with the Android N MR1 Stable release (API 25)
25.0.1 (November 22, 2016)
  • Updated with the release of Android N MR1 Developer Preview 2 release (API 25)
25.0.0 (October 19, 2016)
  • Updated with the release of Android N MR1 Developer Preview 1 release (API 25)
24.0.4 (October 14, 2016)
  • Updated to address issues in ADB and Mac OS Sierra

www.teamandroid.com


Смотрите также