Download‎ > ‎

ADT 17 Preview

Note: SDK Tools r17 and ADT 17 have been released 03/21/2012.

March 8, 2012:
Preview 4 released. This contains bug fixes (primarily in the build system) based on bugs reported in preview 1, 2 and 3. (There are download links below the New Features section.)

March 5, 2012: Preview 3 released. This contains bug fixes based on bugs reported in preview 1 and preview 2. (There are download links below the New Features section.)
February 27, 2012: Preview 2 released. This contains a number of bug fixes based on bugs reported in preview 1.
February 23, 2012: We have just released a preview build of ADT 17 and of the SDK Tools, r17. Follow the installation instructions below.

New Features

  • DDMS can now show the live detailed network usage of an app (More Info)
  • ProGuard
    • Bundled ProGuard updated to version 4.7. In addition to many new features, this will fix the "Conversion to Dalvik format failed with error 1" error some users have experienced.
    • The default proguard.cfg file has been updated with better default flags for Android.
    • The ProGuard configuration file has been split in half, with project specific flags kept in project and the generic Android flags distributed (and updated) with the tools themselves.
    • More info
  • Lint
    • Lint now checks Java code, and checks which previously performed pattern based searches in the Java code (such as the unused resource check) have been rewritten to use the more accurate Java parse trees.
    • Lint supports library projects, so for example the unused resource check will properly handle resources declared in a library project and referenced in a downstream project.
    • Lint warnings can be suppressed 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:
      • Find Android API calls that require a version of Android higher than the minimum supported version. You can use the new @TargetApi annotation to specify local overrides for conditionally loaded code. (More Info)
      • Performance rules
      • About 30 other new rules
    • Revamped Eclipse Lint UI.
      • New "Run Lint" toolbar action with a dropdown menu for selecting specific (or all) projects, clearing results, etc.
      • The results window is now organized as a tree rather than a flat list. Each issue type has a single top level item, which makes it easier to quickly scan through the reported issues and narrow down to issues you are most interested in.
      • The results window contains many new toolbar actions, including expand/collapse, ignore in file, ignore in project, ignore everywhere, show options, and configure columns.
      • There are new columns available, such as category, priority, project, file and line. The column selection (as well as the column sizes) are persisted. You can click on columns to sort by that column.
      • The Lint Options dialog has Enable All and Disable All buttons, and a search filter textbox to filter by issue id, summary and severity.
  • New Quick Outline for XML editors (Ctrl-O, Command-O). This shows the structure of the current file including icons and ids, and lets you filter and quickly jump to specific ids.
  • The resource chooser now shows the resolved value for resources (e.g. when selecting @string/hello it displays that the resolved value is "Hello World"). It also allows editing the chosen value directly.
  • The layout editor no longer assigns default ids to layouts, includes and merge tags. This tended to pollute the namespace with a lot of unused resources since layouts aren't usually manipulated via code, or referenced from XML. (The RelativeLayout editor automatically assigns ids to views without ids when pointing to them.)
  • Export Screenshot from the Layout Editor
  • Layout editor fix for SlidingDrawer which on some platforms could not be dragged into the layout. Also fix preview rendering for SlidingDrawer and TabHost (issue 23022).
  • New default application icons, including an xhdpi version.
  • Important bug fixes:
    • Fixed issues that could prevent layout rendering due to unresolvable resources (issues 21046 and 21051)
    • Fix bug in resource chooser which made some types of framework resources impossible to select (issue 20589)
    • Fix a bug in the formatter where a certain whitespace pattern could result in a non-space character getting deleted (issue 23940)
    • Fix locale bug affecting Turkish locales in particular (issue 23747)


NOTE: ADT 17 requires Java 1.6 or higher (and Eclipse 3.6.2 or higher.).
NOTE: Eclipse 4.x has some known issues with the Android support; we recommend 3.6.2 or 3.7.1 for now.

ADT 17 depends on changes in the tools and platform-tools components as well, so to use the preview you will need to update all 3 (tools, platform-tools and the ADT plugin).


and one of the following depending on whether you are developing on Windows, Linux or Mac OSX:
and one of the following depending on whether you are developing on Windows, Linux or Mac OSX:
If you have already installed preview1, preview2 or preview3, you do not need to update platform-tools again; they are unchanged from preview1 to preview4.

The source code is available in the Android Git repository, using SDK changeset 05a9e90a0e6dfd20e58c493165f94cba8beb4359).

Updating the SDK

ADT 17 relies on some changes to the SDK command line tools, so first you'll need to update your SDK with the new binaries which are not yet available via the SDK Manager.

Go to your Android SDK root directory (where you have existing tools/ and platform-tools/ folders), and copy or move the existing directories out of the way. (Don't just delete them. This is a preview release, so it's possible for the new versions to have bugs and you may want to be able to go back).

Then unzip both your and files into the SDK directory.

On Windows and Mac OSX, you can extract and copy the files using the Windows Explorer or the Mac Finder.  On Linux, you can use something like the following (which just unzips the contents of the preview file directly on top of the SDK directory, with the -d flag pointing to the destination SDK directory:

$ unzip -d /your/sdk/dir ~/Downloads/

Installing the ADT plugins

Download and unzip the file somewhere and then start Eclipse and install the plugin in the normal way described here: For Eclipse 3.7 this means opening the "Install New Software..." dialog from the Help menu, then pointing to the directory where you unzipped and following the on-screen instructions.

As always, please provide feedback and bug reports (using one of the feedback channels).