When I start the 'android studio' program, displayed a window of 'downloading components' which says:
'Android SDK was installed to: C: / Users / user / AppData / Local / android / SDK2
SDK tools directory is missing '
I can not fix and I need help!!

“Android SDK was installed to: C: / Users / user / AppData / Local / android / SDK2 SDK tools directory is missing ”
It means the Android SDK requires a folder “tools”, where this SDK was installed. But that “Tools” folder did not get installed. Probably due to low storage.

Android SDK Tools 30.0.4 is available to all software users as a free download for Windows 10 PCs but also without a hitch on Windows 7 and Windows 8. Compatibility with this software may vary, but will generally run fine under Microsoft Windows 10, Windows 8, Windows 8.1, Windows 7, Windows Vista and Windows XP on either a 32-bit or 64-bit setup. Rm -rf /.android-sdk-macosx/ Download the Mac SDK Tools from the Android developer site under 'Get just the command line tools'. Make sure you save them to your Downloads folder. Go to your Downloads folder. Cd /Downloads/ Unzip the tools you downloaded. Unzip toolsr.-macosx.zip Move them somewhere you won't accidentally delete them.

[SOLUTION] : Uninstall the Android SDK and install it again. This time just make sure that you have ATLEAST 5GB (though 3.2gb would be enough) free space where ever you are going to install this SDK.
Once the installation is complete, just check whether “tools” folder is there or not (At the location where you are installing the SDK)

Just do the following and it will work fine.

1. When the error appears instead of clicking on ‘finish’ , click on ‘x’.It will ask to to re initialize. Take the recommended option.
2. After it reconfiguration it will take back to the main screen. Just go to
   Configure -> Project Defaults -> Project Structure
   and copy paste or browse (appData folder may be hidden) to location
   C: / Users / user / AppData / Local / android / SDK.
3. Finish and try creating project again. Will work like charm !! 😉

This was an issue for me because I already had the SDK installed under a different directory. In order to tell Android Studio to where the SDK is you need to get to the settings, but the “SDK tools directory is missing” dialog always exits the whole program when you click “Finish”. Here’s how I “solved” it:

1. Delete your ~/.Android* folders (losing all of your settings :/).
2. Run Android Studio. It will show you a welcome wizard where it tries to download the SDK again (and fails due to my rubbish internet).
3. Click the X on the wizard window. That will enable you to get to the normal welcome dialog.
4. Go to Settings->Project Defaults->Project Structure and change the Android SDK location to the correct one.

Deleting the .Android Studio folders may be unnecessary – I never tried pressing the X on the original error dialog – I only tried “Finish” which exits Android Studio. It is possible if you click the X you can get to settings but unfortunately I can’t go back and check now.

If your SDK tools directory is missing, maybe you deleted it by accident and there is a easy way to download it and guide android studio to it.

First go to android developer site (https://developer.android.com/studio/index.html), scroll to the bottom of the page and chose your download according to system you have(but don’t download installer version for windows) you need a zip file which contains SDK.

After you download just put it in my documents (MAC or WINDOWS) and then when you open android studio screen will popup for installing SDK (like the time that you got error), don’t click next, go to browse, find that file and press ok. After that go next and it will work like a charm.

That’s it.

I had this problem on a Mac due to a corporate proxy blocking the installer’s call to the internet. The phase in which the Android Studio installer is supposed to install the SDK did not happen and the install process just went straight to the “SDK tools directory is missing” message. Sadly, there was no message stating that a connection could not be made.

To fix the problem, it was required that I list the path to my corporate PAC file by using Configure -> “Appearance and Behavior” -> System Settings -> HTTP Proxy. I selected “Automatic proxy configuration url:” and entered the correct URL for the PAC file.

I had this issue when I was trying to reinstall Android Studio through its wizard. I already had a “tools” folder though.

In my case, while the “tools” directory already existed, it will deliver the “sdk tools directory is missing” error for its subfolders also. Somehow my sdk folder only had a libs subdirectory.

When I pasted in sdk/ant, sdk/apps, sdk/proguard, sdk/qemu, sdk/support, and sdk/templates the wizard was finally happy with this configuration and went to download some more files.

I also faced the same problem, problem with me was on my first run I wasn’t connected to Internet properly. After connecting to internet it required some updates to download, and then it ran without any problem

I googled this error and tried all suggestions but nothing to work. My problem is a little bit different. I’m using Ubuntu 16.04 64bit. I was set mount /tmp folder as tmpfs for increasing the performance of applications. My fstab entry was:

This is setting /tmp file space to 1G and this is bottleneck for android studio becouse it needs more space in /tmp folder for download SDK files. Now I removed this line and rebooted my computer and everything is working now.

I spend 3 hours for this. I hope help to others.

Try installing it somewhere else, maybe that would solve the problem.
Also, you could try installing it on a USB flash drive.

Change the SDK directory to C:UsersusernameAppDataLocalAndroidSdk

If you are using the latest android studio you can configure this using
Configure -> Project Defaults -> Project Structure

In my case it was installing into an already existing directory. When you choose a directory for the installation. The programm won’t allow you to type in a non-existing directory. So choose the path, get back to the main window and type the new folder name where you want install the SDK, probably feature.

I experienced this error when I was installing Android Studio with too little memory to install everything needed. It didn’t help freeing up memory or installing Android SDK my self. Re-installing Android studio with sufficient memory, made the download start when I first opened up Android Studio.

Android Sdk And Tools

when first installing android studio and everything, install sdk to a new file like C:Androidsdk and make sure all the next setup sdk items point to the folder you installed sdk to. It will work fine now… it must have something to do with permissions in the appdata folder is what my guess is

your folder AppData is hidden, you should open it

Tags: android

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 the android: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 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)

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

• 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 ProGuard keep-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 and proguard-android.txt whichdisables 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).

• 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.
• Build
  • Added a feature that allows you to run some code only in debug mode. Builds nowgenerate a class called BuildConfig containing a DEBUG 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.
• 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.

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 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 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 thegen directory) and bytecode (in the res/raw directory) from your native .rs files

SDK Tools, Revision 9(January 2011)

If you are developing in Eclipse with ADT, note that 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
• 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 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 and ddms to support the new location of adb.
• 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)

Android Studio Sdk Tools Download

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 theSDK

If 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. 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 theandroid: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 insert android:debuggable='true'.When exporting a signed release build, the tools do not add the attribute. InAnt, a ant debug command automatically inserts theandroid:debuggable='true' attribute, while ant releasedoes not. If android: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, 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)

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

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.

• .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 and android 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.

Android Sdk Tools Download Manually

• 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 Tools Download

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.