Android Sdk Starter Package Download

Posted on |



The Android SDK Manager, manages various Android SDK versions, tools and various other useful packages that you can select and download, to keep your development environment up-to-date. Generally when you launch the Android Studio for the first time, it will open the Android SDK Manager window, to prompt you to install the required packages for. The sdkmanager tool is provided in the Android SDK Tools package (25.2.3 and higher) and is located in androidsdk/tools. System-images; Extras; Home. Name API Rev Downloads; Android SDK Platform 10: 10: 2: 81.51 MB: Download: Android SDK Platform 11: 11: 2: 99.67 MB: Download: Android SDK Platform 12: 12: 3. Adding Platforms and Packages; Exploring the SDK; Download the NDK; Workflow. Setting Up Virtual Devices. With AVD Manager; From the Command Line; Using the Android Emulator; Using Hardware Devices; Setting Up Projects. From Eclipse with ADT; From the Command Line. Downloading the SDK Starter Package; 3. Installing the ADT Plugin for Eclipse.

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 Updating SDKComponents.

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.

Starter 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:
  • Snapshots now work for Android 4.0 system images.
  • Fixed several small issues for the build file. (Issue 21023, Issue 21267, Issue 21465, Issue 21525).
SDK Tools, Revision 15(October 2011)

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

Dependencies:
  • Android SDK Platform-tools revision 9 or later.
  • If you are developing in Eclipse with ADT, note that 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 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)
Dependencies:

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.

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

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

General notes:
  • Miscellaneous emulator changes to support Android 3.1.
SDK Tools, Revision 10Android sdk starter package download windows 10(February 2011)
Dependencies:

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.

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

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.

Upgrading to SDK Tools r9:

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.

General notes:
  • The default ProGuard configuration, proguard.cfg, now ignores the following classes:
    • classes that extend Preference
    • classes that extend BackupAgentHelper
  • Ant lib rules now allow you to override java.encoding, java.source, and java.target properties.
  • The default encoding for the javac Ant task is now UTF-8.
  • The LogCat view in DDMS now properly displays UTF-8 characters.
  • The SDK Manager is more reliable on Windows. For details on the improvements, see the Android Tools Project Site.
  • Early look at the new snapshot feature: To improve startup time for the emulator, you 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)
Dependencies:

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 Adding SDKComponents

Upgrading from SDK Tools r7:

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.

General notes:
  • 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 7Starter(September 2010)
Dependencies:

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.

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 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)
Dependencies:

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.

Library projects:

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

Package
General notes:
  • Launcher script now forces GDK_NATIVE_WINDOW=true (linux only), to fix acompatibility 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 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.
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 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.

Android tool:
  • Adds new android create test-project and android updatetest-project commands to allow for greater flexibility in the location of themain and test projects.
DDMS:
  • 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 and AVD Manager:
  • 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 Starter Package Download

Android Sdk Starter Package Download

Layoutopt, a new tool for optimizing layouts:

Android Sdk Starter Package Download Free

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.