Android Studio release notes

Android Studio is the official IDE for Android development, and includes everything you need to build Android apps.

To get the latest version, click Help > Check for updates (on Mac, Android Studio > Check for updates).

You can also download Android Studio here.

If you encounter problems in Android Studio, check the Known issues or Troubleshoot page.

For the latest news on releases, including a list of notable fixes in each preview release, see the release updates.

For information on what’s new in the Android Plugin for Gradle, see its release notes.

3.2 (September 2018)

Android Studio 3.2 is a major release that includes a variety of new features and improvements.

3.2.1 (October 2018)

This update to Android Studio 3.2 includes the following changes and fixes:

  • The bundled Kotlin version is now 1.2.71.
  • The default build tools version is now 28.0.3.
  • In the Navigation library, argument types have been renamed from type to argType.
  • The following bugs have been fixed:
    • When using the Data Binding library, variable names with underscores were causing compilation errors.
    • CMake was causing IntelliSense and other CLion features to fail.
    • Adding a SliceProvider was causing compilation errors in projects that did not use androidx.* libraries.
    • Some Kotlin unit tests were not being run.
    • An issue with data binding was causing a PsiInvalidElementAccessException.
    • <merge> elements were sometimes causing the Layout Editor to crash.

3.2.0 known issues

Note: These issues have been resolved in Android Studio 3.2.1

  • We strongly recommend against using Kotlin version 1.2.70.

    Kotlin version 1.2.61 fixes a bug that can cause Android Studio to hang, but Kotlin 1.2.70 does not include this fix.

    Kotlin versions 1.2.71 and later, however, do include this fix.

  • Although you typically don't need to specify the build tools version, when using Android Gradle plugin 3.2.0 with renderscriptSupportModeEnabled set to true, you need to include the following in each module's build.gradle file:

    android.buildToolsVersion "28.0.3"

What's New Assistant

A new assistant informs you about the latest changes in Android Studio.

The assistant opens when you start Android Studio after a fresh installation or update if it detects that there is new information to show. You can also open the assistant by choosing Help > What's new in Android Studio.

Android Jetpack

Android Jetpack helps to accelerate Android development with components, tools, and guidance that eliminate repetitive tasks and enable you to more quickly and easily build high-quality, testable apps. Android Studio includes the following updates to support Jetpack. For more information, see the Jetpack documentation.

The new Navigation Editor integrates with the navigation components of Android Jetpack to provide a graphical view for creating the navigation structure of your app. The Navigation Editor simplifies the design and implementation of navigation between in-app destinations.

In Android Studio 3.2, the Navigation Editor is an experimental feature. To enable the Navigation Editor, click File > Settings (Android Studio > Preferences on Mac), select the Experimental category in the left pane, check the box next to Enable Navigation Editor, and restart Android Studio.

To learn more, read the Navigation Editor documentation.

AndroidX migration

As part of Jetpack, we are migrating the Android Support Libraries to a new Android extension library using the androidx namespace. For more information, see the AndroidX overview.

Android Studio 3.2 helps you through this process with a new migration feature.

To migrate an existing project to AndroidX, choose Refactor > Migrate to AndroidX. If you have any Maven dependencies that have not migrated to the AndroidX namespace, the Android Studio build system also automatically converts those project dependencies.

The Android Gradle plugin provides the following global flags that you can set in your file:

  • android.useAndroidX: When set to true, this flag indicates that you want to start using AndroidX from now on. If the flag is absent, Android Studio behaves as if the flag were set to false.
  • android.enableJetifier: When set to true, this flag indicates that you want to have tool support (from the Android Gradle plugin) to automatically convert existing third-party libraries as if they were written for AndroidX. If the flag is absent, Android Studio behaves as if the flag were set to false.

Both flags are set to true when you use the Migrate to AndroidX command.

If you want to start using AndroidX libraries immediately and don't need to convert existing third-party libraries, you can set the android.useAndroidX flag to true and the android.enableJetifier flag to false.

Android App Bundle

Android App Bundle is a new upload format that includes all of your app’s compiled code and resources, but defers APK generation and signing to the Google Play Store.

Google Play’s new app serving model, called Dynamic Delivery, then uses your app bundle to generate and serve optimized APKs for each user’s device configuration, so each user downloads only the code and resources they need to run your app. You no longer need to build, sign, and manage multiple APKs, and users get smaller, more optimized downloads.

Additionally, you can add dynamic feature modules to your app project and include them in your app bundle. Through Dynamic Delivery, your users can then download and install your app’s dynamic features on demand.

To build a bundle, choose Build > Build Bundle(s) / APK(s) > Build Bundle(s).

For more information, including instructions for building and analyzing an Android App Bundle, see Android App Bundle.

Sample data in Layout Editor

Many Android layouts have runtime data that can make it difficult to visualize the look and feel of a layout during the design stage of app development. You can now easily see a preview of your view in the Layout Editor filled with sample data. When you add a view, a button appears below the view in the Design window. Click this button to set the design-time view attributes. You can choose from a variety of sample data templates and specify the number of sample items with which to populate the view.

To try using sample data, add a RecyclerView to a new layout, click the design-time attributes button below the view, and choose a selection from the carousel of sample data templates.


Slices provide a new way to embed portions of your app's functionality in other user interface surfaces on Android. For example, Slices make it possible to show app functionality and content in Google Search suggestions.

Android Studio 3.2 has a built-in template to help you to extend your app with the new Slice Provider APIs, as well as new lint checks to ensure that you're following best practices when constructing the Slices.

To get started right-click a project folder and choose New > Other > Slice Provider.

To learn more, including how to test your Slice interactions, read the Slices getting started guide.

Kotlin 1.2.61

Android Studio 3.2 bundles Kotlin 1.2.61, and the new Android SDK integrates better with Kotlin. For more information, see the Android Developers blog.

IntelliJ IDEA 2018.1.6

The core Android Studio IDE has been updated with improvements from IntelliJ IDEA through the 2018.1.6 release.

Android profilers

Try the following new Android Profiler features in Android Studio 3.2.


You can now save Profiler data as sessions to revisit and inspect later. The profiler keeps your session data until you restart the IDE.

When you record a method trace or capture a heap dump, the IDE adds that data (along with your app's network activity) as a separate entry to the current session, and you can easily switch back and forth between recordings to compare data.

System Trace

In the CPU Profiler, select the new System Trace configuration to inspect your device's system CPU and thread activity. This trace configuration is built on systrace and is useful for investigating system-level issues, such as UI jank.

While using this trace configuration, you can visually mark important code routines in the profiler timeline by instrumenting your C/C++ code with the native tracing API or your Java code with the Trace class.

Inspect JNI references in the Memory Profiler

If you deploy your app to a device running Android 8.0 (API level 26) or higher, you can now inspect memory allocations for your app’s JNI code using the Memory Profiler.

While your app is running, select a portion of the timeline that you want to inspect and select JNI heap from the drop-down menu above the class list, as shown below. You can then inspect objects in the heap as you normally would and double-click objects in the Allocation Call Stack tab to see where the JNI references are allocated and released in your code.

Import, export, and inspect memory heap dump files

You can now import, export, and inspect .hprof memory heap dump files created with the Memory Profiler.

Import your .hprof file by clicking Start new profiler session in the profiler’s Sessions pane and then selecting Load from file. You can then inspect its data in the Memory Profiler as you would any other heap dump.

To save heap dump data to review later, use the Export Heap Dump button at the right of the Heap Dump entry in the Sessions pane. In the Export As dialog that appears, save the file with the .hprof filename extension.

Record CPU activity during app startup

You can now record CPU activity during your app's startup, as follows:

  1. Select Run > Edit Configurations from the main menu.
  2. Under the Profiling tab of your desired run configuration, check the box next to Start recording a method trace on startup.
  3. Select a CPU recording configuration to use from the dropdown menu.
  4. Deploy your app to a device running Android 8.0 (API level 26) or higher by selecting Run > Profile.

Export CPU traces

After you record CPU activity with the CPU Profiler, you can export the data as a .trace file to share with others or inspect later.

To export a trace after you’ve recorded CPU activity, do the following:

  1. Right-click on the recording you want to export from the CPU timeline.
  2. Select Export trace from the dropdown menu.
  3. Navigate to where you want to save the file and click Save.

Import and inspect CPU trace files

You can now import and inspect .trace files created with the Debug API or CPU Profiler. (Currently, you can't import System Trace recordings.)

Import your trace file by clicking Start new profiler session in the profiler’s Sessions pane and then selecting Load from file. You can then inspect its data in the CPU Profiler similar to how you normally would, with the following exceptions:

  • CPU activity is not represented along the CPU timeline.
  • The thread activity timeline indicates only where trace data is available for each thread and not actual thread states (such as running, waiting, or sleeping).

Record CPU activity using the Debug API

You can now start and stop recording CPU activity in the CPU Profiler by instrumenting your app with the Debug API. After you deploy your app to a device, the profiler automatically starts recording CPU activity when your app calls startMethodTracing(String tracePath), and the profiler stops recording when your app calls stopMethodTracing(). While recording CPU activity that’s triggered using this API, the CPU Profiler shows Debug API as the selected CPU recording configuration.

Energy Profiler

The Energy Profiler displays a visualization of the estimated energy usage of your app, as well as system events that affect energy usage, such as wakelocks, alarms, and jobs.

The Energy Profiler appears as a new row at the bottom of the Profiler window when you run your app on a connected device or Android Emulator running Android 8.0 (API 26) or higher.

Click the Energy row to maximize the Energy Profiler view. Place your mouse pointer over a bar in the timeline to see a breakdown of energy use by CPU, network, and location (GPS) resources, as well as relevant system events.

System events that affect energy usage are indicated in the System timeline below the Energy timeline. Details of system events within the specified time range are shown in the event pane when you select a time range in the Energy timeline.

To see the call stack and other details for a system event, such as a wakelock, select it in the event pane. To go to the code responsible for a system event, double-click the entry in the call stack.

Lint checking

Android Studio 3.2 includes many new and improved features for lint checking.

The new lint checks help you to find and identify common code problems, ranging from warnings about potential usability issues to high-priority errors regarding potential security vulnerabilities.

Lint checks for Java/Kotlin interoperability

To make sure that your Java code interoperates well with your Kotlin code, new lint checks enforce the best practices described in the Kotlin Interop Guide. Examples of these checks include looking for the presence of Nullability annotations, use of Kotlin hard keywords, and placing lambda parameters last.

To enable these checks, click File > Settings (Android Studio > Preferences on Mac) to open the Settings dialog, navigate to the Editor > Inspections > Android > Lint > Interoperability > Kotlin Interoperability section, and select the rules that you want to enable.

To enable these checks for command-line builds, add the following to your build.gradle file:

android {
    lintOptions {
        check 'Interoperability'

Lint checks for Slices

New lint checks for Slices help to ensure that you are constructing Slices correctly. For example, lint checks warn you if you have not assigned a primary action to a Slice.

New Gradle target

Use the new lintFix Gradle task to apply all of the safe fixes suggested by the lint check directly to the source code. An example of a lint check that suggests a safe fix to apply is SyntheticAccessor.

Metadata updates

Various metadata, such as the service cast check, have been updated for lint checks to work with Android 9 (API level 28).

Warning if running lint on a new variant

Lint now records which variant and version a baseline is recorded with, and lint warns you if you run it on a different variant than the one with which the baseline was created.

Improvements to existing lint checks

Android Studio 3.2 includes many improvements to existing lint checks. For example, the resource cycle checks now apply to additional resource types, and the translation detector can find missing translations on the fly, in the editor.

Issue IDs more discoverable

Issue IDs are now shown in more places now, including in the Inspection Results window. This makes it easier for you to find the information that you need to enable or disable specific checks through lintOptions in build.gradle.

For more information, see Configure lint options with Gradle.

Data Binding V2

Data Binding V2 is now enabled by default and is compatible with V1. This means that, if you have library dependencies that you compiled with V1, you can use them with projects using Data Binding V2. However, note that projects using V1 cannot consume dependencies that were compiled with V2.

D8 desugaring

In Android Studio 3.1, we integrated the desugaring step into the D8 tool as an experimental feature, reducing overall build time. In Android Studio 3.2, desugaring with D8 is turned on by default.

New code shrinker

R8 is a new tool for code shrinking and obfuscation that replaces ProGuard. You can start using the preview version of R8 by including the following in your project’s file:

android.enableR8 = true

Changed default ABIs for multi-APKs

When building multiple APKs that each target a different ABI, the plugin no longer generates APKs for the following ABIs by default: mips, mips64, and armeabi.

If you want to build APKs that target these ABIs, you must use NDK r16b or lower and specify the ABIs in your build.gradle file, as shown below:

splits {
    abi {
        include 'armeabi', 'mips', 'mips64'

Improved editor features for CMake build files

If you use CMake to add C and C++ code to your project, Android Studio now includes improved editor features to help you to edit your CMake build scripts, such as the following:

  • Syntax highlighting and code completion: The IDE now highlights and suggests code completion for common CMake commands. Additionally, you can navigate to a file by clicking it while pressing the Control key (Command on Mac).
  • Code reformatting: You can now use IntelliJ’s code reformat option to apply code styles to your CMake build scripts.
  • Safe refactoring: The IDE’s built-in refactoring tools now also check if you are renaming or deleting files that you reference in your CMake build scripts.

When using the Project window in previous versions of Android Studio, you could navigate and inspect only the header files that belong to libraries you build from a local project. With this release, you can now also view and inspect header files included with external C/C++ library dependencies that you import into your app project.

If you already include C/C++ code and libraries in your project, open the Project window on the left side of the IDE by selecting View > Tool Windows > Project from the main menu and select Android from the drop-down menu. In the cpp directory, all headers that are within the scope of your app project are organized under the include node for each of your local C/C++ library dependencies, as shown below.

Native multidex enabled by default

Previous versions of Android Studio enabled native multidex when deploying the debug version of an app to a device running Android API level 21 or higher. Now, whether you’re deploying to a device or building an APK for release, the Android plugin for Gradle enables native multidex for all modules that set minSdkVersion=21 or higher.

AAPT2 moved to Google's Maven repository

Beginning with Android Studio 3.2, the source for AAPT2 (Android Asset Packaging Tool 2) is Google's Maven repository.

To use AAPT2, make sure that you have a google() dependency in your build.gradle file, as shown here:

  buildscript {
      repositories {
          google() // here
      dependencies {
          classpath ''
  } allprojects {
      repositories {
          google() // and here

The new version of AAPT2 fixes many issues, including improved handling of non-ASCII characters on Windows.

Removal of configuration on demand

The Configure on demand preference has been removed from Android Studio.

Android Studio no longer passes the --configure-on-demand argument to Gradle.

ADB Connection Assistant

The new ADB Connection Assistant provides step-by-step instructions to help you set up and use a device over the Android Debug Bridge (ADB) connection.

To start the assistant, choose Tools > Connection Assistant.

The ADB Connection Assistant provides instructions, in-context controls, and a list of connected devices in a series of pages in the Assistant panel.

Emulator improvements

You can now save and load snapshots of an AVD (Android virtual device) at any time in the Android Emulator, making it fast and easy to return an emulated device to a known state for testing. When you edit an AVD using the AVD Manager, you can specify which AVD snapshot to load when the AVD starts.

Controls for saving, loading, and managing AVD snapshots are now in the Snapshots tab in the emulator's Extended controls window.

For details, see Snapshots.

For additional information on what’s new and changed in the Emulator, see the Emulator release notes.

3.1 (March 2018)

Android Studio 3.1.0 is a major release that includes a variety of new features and improvements.

3.1.4 (August 2018)

This update to Android Studio 3.1 includes the following changes and fixes:

  • The bundled Kotlin is now version 1.2.50.
  • New projects are created with kotlin-stdlib-jdk* artifacts, rather than with kotlin-stdlib-jre* artifacts, which are deprecated.
  • R8 parsing of ProGuard rules has been improved.
  • The following bugs have been fixed:
    • Attempting to run the Kotlin Main class failed with an error: "Error: Could not find or load main class..."
    • R8 entered an infinite loop while performing certain optimizations.
    • Using the Rerun failed tests command in the Run window sometimes incorrectly returned the message "No tests were found".
    • D8 did not correctly handle invoke-virtual instances, causing a crash with a VerifyError: invoke-super/virtual can't be used on private method
    • The Data Binding compiler was depending on an old version of The compiler now uses tools annotations from the base project when available.
    • Android Studio crashed during fragment transitions when using profilers.
    • The debugger crashed when debugging a layout with a text box.
    • D8 failed to read some ZIP files with special characters.

3.1.3 (June 2018)

This update to Android Studio 3.1 includes fixes for the following bugs:

  • Memory leaks caused Android Studio to become slow and unresponsive after you had been using the Layout Editor. This update includes fixes for most of these issues. We intend to release another update soon to address additional memory leaks.
  • Some applications built with D8 crashed on some Verizon Ellipsis tablets.
  • Installation of applications built with D8 failed with an INSTALL_FAILED_DEXOPT error on devices running Android 5.0 or 5.1 (API level 21 or 22).
  • Some applications that used the OkHttp library and were built with D8 crashed on devices running Android 4.4 (API level 19).
  • Android Studio sometimes failed to start, with a ProcessCanceledException during class initialization for com.intellij.psi.jsp.JspElementType.

3.1.2 (April 2018)

This update to Android Studio 3.1 includes fixes for the following bugs:

  • In some cases, Android Studio hung indefinitely during exit.
  • Builds configured with source sets failed with the following message when Instant Run was enabled:

    "The SourceSet name is not recognized by the Android Gradle Plugin."

  • When Instant Run was enabled, builds of new Kotlin projects failed when triggered by the Run command.
  • During editing of the build.gradle file, there was sometimes a noticeable delay between typing a character and the character appearing on the screen.
  • Build failures occurred during dexing in some projects with large numbers of modules or external dependencies, with the following error message:

    "RejectedExecutionException: Thread limit exceeded replacing blocked worker"

  • The computation of the D8 main DEX list was not taking into account some reflective invocations.

This update also includes changes that make running lint checks from Gradle much faster in some scenarios.

3.1.1 (April 2018)

This update to Android Studio 3.1 includes fixes for the following bugs:

  • In some cases, when a project created in Android Studio 3.0 was opened for the first time in Android Studio 3.1, the Gradle-aware Make task was removed from the Before launch area in Run/Debug Configurations. The result was that projects did not build when the Run or Debug button was clicked, which in turn caused failures such as deployment of incorrect APKs and crashes when using Instant Run.

    To solve this problem, Android Studio 3.1.1 adds the Gradle-aware Make task to the run configuration for projects that are missing this entry. This modification occurs after the first Gradle sync when the project is loaded.

  • The debugger crashed when debugging a layout with a text box if advanced profiling was enabled.
  • Android Studio froze after you clicked Build Variants.
  • AAR (Android archive) files were extracted twice, once during the Gradle sync process and once during the Gradle build process.
  • Elements were missing from some vector drawables imported from SVG files.
  • The warning regarding the deprecation of the compile dependency configuration has been updated with better guidance regarding the implementation and api configurations. For details of migrating away from using the compile configuration, see the documentation for the new dependency configurations.


IntelliJ 2017.3.3

The core Android Studio IDE has been updated with improvements from IntelliJ IDEA through the 2017.3.3 release. Improvements include better control flow analysis for collections and strings, improved nullability inference, new quick fixes, and much more.

For details, see the JetBrains release notes for IntelliJ IDEA versions 2017.2 and 2017.3, as well as the JetBrains release notes for bug-fix updates.

SQL editing improvements with Room

When you use the Room database library, you can take advantage of several improvements to SQL editing:

  • Code completion within a Query understands SQL tables (entities), columns, query parameters, aliases, joins, subqueries, and WITH clauses.
  • SQL syntax highlighting now works.
  • You can right-click a table name in SQL and rename it, which also rewrites the corresponding Java or Kotlin code (including, for example, the return type of the query). Renaming works in the other direction, too, so renaming a Java class or field rewrites the corresponding SQL code.
  • SQL usages are shown when using Find usages (right-click and choose Find usages from the context menu).
  • To navigate to an SQL entity's declaration in Java or Kotlin code, you can hold Control (Command on Mac) while clicking the entity.

For information on using SQL with Room, see Save data in a local database using Room.

Updates to data binding

This update includes several improvements for data binding:

  • You can now use a LiveData object as an observable field in data binding expressions. The ViewDataBinding class now includes a new setLifecycle() method that you use to observe LiveData objects.

  • The ObservableField class can now accept other Observable objects in its constructor.

  • You can preview a new incremental compiler for your data binding classes. For details of this new compiler and instructions for enabling it, see Data Binding Compiler V2.

    Benefits of the new compiler include the following:

    • ViewBinding classes are generated by the Android Plugin for Gradle before the Java compiler.

    • Libraries keep their generated binding classes when the app is compiled, rather than being regenerated each time. This can greatly improve performance for multi-module projects.

Compiler and Gradle

D8 is the default DEX compiler

The D8 compiler is now used by default for generating DEX bytecode.

This new DEX compiler brings with it several benefits, including the following:

  • Faster dexing
  • Lower memory usage
  • Improved code generation (better register allocation, smarter string tables)
  • Better debugging experience when stepping through code

You don't need to make any changes to your code or your development workflow to get these benefits, unless you had previously manually disabled the D8 compiler. If you set android.enableD8 to false in your, either delete that flag or set it to true:


For details, see New DEX compiler.

Incremental desugaring

For projects that use Java 8 language features, incremental desugaring is enabled by default, which can improve build times.

Desugaring converts syntactic sugar into a form that the compiler can process more efficiently.

You can disable incremental desugaring by specifying the following in your project's file:


Simplified output window

The Gradle Console has been replaced with the Build window, which has Sync and Build tabs.

For details about how to use the new, simplified Build window, see Monitor the build process.

Batch updates and indexing concurrency

The Gradle sync and IDE indexing processes are now much more efficient, reducing time wasted on many redundant indexing operations.

C++ and LLDB

We have made many quality and performance improvements in the coding, syncing, building, and debugging phases of C++ development. Improvements include the following:

  • If you work with large C++ projects, you should notice a significant improvement in the reduction of time spent building symbols. Sync time is also greatly reduced for large projects.

  • Performance when building and syncing with CMake has been improved through more aggressive reuse of cached results.

  • The addition of formatters ("pretty printers") for more C++ data structures makes LLDB output easier to read.

  • LLDB now works with only Android 4.1 (API level 16) and higher.


Kotlin upgraded to version 1.2.30

Android Studio 3.1 includes Kotlin version 1.2.30.

Kotlin code now analyzed with command-line lint check

Running lint from the command line now analyzes your Kotlin classes.

For each project that you would like to run lint on, Google's Maven repository must be included in the top-level build.gradle file. The Maven repository is already included for projects created in Android Studio 3.0 and higher.

Performance tools

Sample native C++ processes with CPU Profiler

The CPU Profiler now includes a default configuration to record sampled traces of your app's native threads. You can use this configuration by deploying your app to a device running Android 8.0 (API level 26) or higher and then selecting Sampled (Native) from the CPU Profiler's recording configurations dropdown menu. After that, record and inspect a trace as you normally would.

You can change default settings, such as the sampling interval, by creating a recording configuration.

To switch back to tracing your Java threads, select either a Sampled (Java) or Instrumented (Java) configuration.

Filter CPU traces, memory allocation results, and heap dumps

The CPU Profiler and Memory Profiler include a search feature that allows you to filter results from recording a method trace, memory allocations, or heap dump.

To search, click Filter in the top-right corner of the pane, type your query, and press Enter.

Tip: You can also open the search field by pressing Control + F (Command + F on Mac).

In the CPU Profiler's Flame Chart tab, call stacks that include methods related to your search query are highlighted and moved to the left side of the chart.

For more information on filtering by method, class, or package name, see Record and inspect method traces.

Request tab in the Network Profiler

The Network Profiler now includes a Request tab that provides details about network requests during the selected timeline. In previous versions, the Network Profiler only provided information about network responses.

Thread View in the Network Profiler

After selecting a portion of the timeline in the Network Profiler, you can select one of the following tabs to see more detail about the network activity during that timeframe:

  • Connection View: Provides the same information as previous versions of Android Studio—it lists files that were sent or received during the selected portion of the timeline across all of your app's CPU threads. For each request, you can inspect the size, type, status, and transmission duration.
  • Thread View: Displays network activity of each of your app's CPU threads. This view allows you to inspect which of your app's threads are responsible for each network request.

Layout Inspector

The Layout Inspector gained new features, including some functionality previously provided by the deprecated Hierarchy Viewer and Pixel Perfect tools:

  • Zoom buttons and keyboard shortcuts for navigating and inspecting layouts
  • Reference grid overlay
  • Ability to load a reference image and use it as an overlay (useful for comparing your layout with a UI mockup)
  • Render subtree preview to isolate a view in a complex layout

Layout Editor

The Palette in the Layout Editor has received many improvements:

  • Reorganization of categories for views and layouts.
  • New Common category for views and layouts, which you can add to with a Favorite command.
  • Improved search for views and layouts.
  • New commands for opening documentation for a specific view or layout element.

You can use the new Convert view command in the Component tree or design editor to convert a view or layout to another type of view or layout.

You can now easily create constraints to items near the selected view using the new Create a connection buttons in the view inspector at the top of the Attributes window.

Run and Instant Run

The behavior of the Use same selection for future launches option in the Select deployment target dialog has been made more consistent. If the Use same selection option is enabled, then the Select deployment target dialog opens only the first time that you use the Run command until the selected device is no longer connected.

When targeting a device running Android 8.0 (API level 26) or higher, Instant Run can deploy changes to resources without causing an application restart. This is possible because the resources are contained in a split APK.


For details of what's new and changed in the emulator since Android Studio 3.0, see the Android Emulator release notes from version 27.0.2 through version 27.1.12.

Major improvements include the following:

  • Quick Boot snapshots for saving of emulator state and faster start, with the ability to use the Save now command to save a custom start state.
  • Windowless emulator screen.
  • System images for Android 8.0 (API level 26), Android 8.1 (API level 27), and Android P Developer Preview.

User interface and user experience improvements

More tooltips, keyboard shortcuts, and helpful messages

We have added tooltips and helpful message overlays in many places throughout Android Studio.

To see keyboard shortcuts for many commands, just hold the mouse pointer over a button until the tooltip appears.

Tools > Android menu removed

The Tools > Android menu has been removed. Commands that were previously under this menu have been moved.

  • Many commands moved to directly under the Tools menu.
  • The Sync project with gradle files command moved to the File menu.
  • The Device Monitor command has been removed, as described below.

Device Monitor available from the command line

In Android Studio 3.1, the Device Monitor serves less of a role than it previously did. In many cases, the functionality available through the Device Monitor is now provided by new and improved tools.

See the Device Monitor documentation for instructions for invoking the Device Monitor from the command line and for details of the tools available through the Device Monitor.

3.0 (October 2017)

Android Studio 3.0.0 is a major release that includes a variety of new features and improvements.

macOS users: If you are updating an older version of Android Studio, you may encounter an update error dialog that says "Some conflicts were found in the installation area". Simply ignore this error and click Cancel to resume the installation.

3.0.1 (November 2017)

This is a minor update to Android Studio 3.0 that includes general bug fixes and performance improvements.

Android Plugin for Gradle 3.0.0

The new Android plugin for Gradle includes a variety of improvements and new features, but it primarily improves build performance for projects that have a large number of modules. When using the new plugin with these large projects, you should experience the following:

  • Faster build configuration times due to new delayed dependency resolution.
  • Variant-aware dependency resolution for only the projects and variants you are building.
  • Faster incremental build times when applying simple changes to code or resources.

This version also includes the following:

For more information about what's changed, see the Android Plugin for Gradle release notes.

If you're ready to upgrade to the new plugin, see Migrate to Android Plugin for Gradle 3.0.0.

Kotlin support

As announced at Google I/O 2017, the Kotlin programming language is now officially supported on Android. So with this release, Android Studio includes Kotlin language support for Android development.

You can incorporate Kotlin into your project by converting a Java file to Kotlin (click Code > Convert Java File to Kotlin File) or by creating a new Kotlin- enabled project using the New Project wizard.

To get started, read how to add Kotlin to your project.

Java 8 language features support

You can now use certain Java 8 language features and consume libraries built with Java 8. Jack is no longer required, and you should first disable Jack to use the improved Java 8 support built into the default toolchain.

To update your project to support the new Java 8 language toolchain, update the Source Compatibility and Target Compatibility to 1.8 in the Project Structure dialog (click File > Project Structure). To learn more, read how to use Java 8 language features.

Android Profiler

The new Android Profiler replaces the Android Monitor tool and provides a new suite of tools to measure your app's CPU, memory, and network usage in realtime. You can perform sample-based method tracing to time your code execution, capture heap dumps, view memory allocations, and inspect the details of network-transmitted files.

To open, click View > Tool Windows > Android Profiler (or click Android Profiler in the toolbar).

The event timeline at the top of the window shows touch events, key presses, and activity changes so you have more context to understand other performance events in the timeline.

From the Android Profiler's overview timeline, click on the CPU, MEMORY, or NETWORK timelines to access the corresponding profiler tools.

CPU Profiler

The CPU Profiler helps you analyze the CPU thread usage of your app by triggering a sample or instrumented CPU trace. Then, you can troubleshoot CPU performance issues using a variety of data views and filters.

For more information, see the CPU Profiler guide.

Memory Profiler

The Memory Profiler helps you identify memory leaks and memory churn that can lead to stutter, freezes, and even app crashes. It shows a realtime graph of your app's memory use, lets you capture a heap dump, force garbage collections, and track memory allocations.

For more information, see the Memory Profiler guide.

Network Profiler

The Network Profiler allows you to monitor the network activity of your app, inspect the payload of each of your network requests, and link back to the code that generated the network request.

For more information, see the Network Profiler guide.

APK profiling and debugging

Android Studio now allows you to profile and debug any APK without having to build it from an Android Studio project—as long as the APK is built to enable debugging and you have access to the debug symbols and source files.

To get started, click Profile or debug APK from the Android Studio Welcome screen. Or, if you already have a project open, click File > Profile or debug APK from the menu bar. This displays the unpacked APK files, but it does not decompile the code. So, to properly add breakpoints and view stack traces, you need to attach Java source files and native debug symbols.

For more information, see Profile and Debug Pre-built APKs.

Device File Explorer

The new Device File Explorer allows you to inspect your connected device's filesystem, and transfer files between the device and your computer. This replaces the filesystem tool available in DDMS.

To open, click View > Tool Windows > Device File Explorer.

For more information, see the Device File Explorer guide.

Instant Apps support

New support for Android Instant Apps allows you to create Instant Apps in your project using two new module types: Instant App modules and Feature modules (these require that you install the Instant Apps Development SDK).

Android Studio also includes a new modularize refactoring action to help you add support for Instant Apps in an existing project. For example, if you want to refactor your project to place some classes in an Instant App feature module, select the classes in the Project window and click Refactor > Modularize. In the dialog that appears, select the module where the classes should go and click OK.

And when you're ready to test your Instant App, you can build and run your Instant App module on a connected device by specifying the Instant App's URL within the run configuration launch options: Select Run > Edit Configurations, select your Instant App module, and then set the URL under Launch Options.

For more information, see Android Instant Apps.

Android Things modules

New Android Things templates in the New Project and New Module wizards to help you start developing for Android-powered IOT devices.

For more information, see how to create an Android Things project.

Adaptive Icons wizard

Image Asset Studio now supports vector drawables and allows you to create adaptive launcher icons for Android 8.0 while simultaneously creating traditional icons ("Legacy" icons) for older devices.

To start, right-click on the res folder in your project, and then click New > Image Asset. In the Asset Studio window, select Launcher Icons (Adaptive and Legacy) as the icon type.

For more information, read about Adaptive Icons.

Support for font resources

To support the new font resources in Android 8.0, Android Studio includes a font resources selector to help bundle fonts into your app or configure your project to download the fonts on the device (when available). The layout editor can also preview the fonts in your layout.

To try downloadable fonts, ensure that your device or emulator is running Google Play Services v11.2.63 or higher. For more information, read about Downloadable Fonts.

Firebase App Indexing Assistant

The Firebase Assistant has been updated with a new tutorial to test App Indexing. To open the Assistant, select Tools > Firebase. Then select App Indexing > Test App Indexing.

The tutorial includes new buttons to test your public and personal content indexing:

  • In step 2, click Preview search results to verify that your URLs are showing up in Google Search results.
  • In step 3, click Check for errors to verify that the indexable objects in your app have been added to the personal content index.

The App Links Assistant has been updated with the following new capabilities:

  • Add URL tests for each URL mapping to be sure your intent filters handle real-world URLs.

    You can also define these URL tests by hand using the <tools:validation> tag described below.

  • Create a Digital Asset Links file with the appropriate object entry to support Google Smart Lock, and add the corresponding asset_statements <meta-data> tag to your manifest file.

URL intent-filter validator

Android Studio now supports a special tag in the manifest file that allows you to test your intent filter URLs. These are the same tags that the App Links Assistant can create for you.

To declare a test URL for an intent filter, add a <tools:validation> element alongside the corresponding <intent-filter> element. For example:

<activity ...>
    <tools:validation testUrl="" />

Be sure to also include xmlns:tools="" in the <manifest> tag.

If any one of the test URLs does not pass the intent filter definition, a lint error appears. Such an error still allows you to build debug variants, but it will break your release builds.

Layout Editor

The Layout Editor has been updated with a number of enhancements, including the following:

  • New toolbar layout and icons.
  • Updated layout in the component tree.
  • Improved drag-and-drop view insertions.
  • New error panel below the editor, showing all issues with suggestions to fix (if available).
  • Various UI enhancements for building with ConstraintLayout, including the following:
    • New support to create barriers.
    • New support to create groups: In the toolbar, select Guidelines > Add Group (requires ConstraintLayout 1.1.0 beta 2 or higher)
    • New UI to create chains: Select multiple views, and then right-click and select Chain.

Layout Inspector

The Layout Inspector includes enhancements to make it easier to debug issues with your app layouts, including grouping properties into common categories and new search functionality in both the View Tree and the Properties panes.

APK Analyzer

You can now use the APK Analyzer from the command line with the apkanalyzer tool.

The APK Analyzer has also been updated with the following improvements:

  • For APKs built with ProGuard, you can load ProGuard mapping files that add capabilities to the DEX viewer, including:
    • Bolded nodes to indicate that the nodes should not be removed when shrinking code.
    • A button to show nodes that were removed during the shrinking process.
    • A button that restores the original names of nodes in the tree view that were obfuscated by ProGuard.
  • The DEX Viewer now shows the estimated size impact of each package, class and method.
  • New filtering options at the top to show and hide fields and methods.
  • In the tree view, nodes that are references not defined in the DEX file appear in italics.

For more information, see Analyze Your Build with APK Analyzer.

Preview for D8 DEX compiler

Android Studio 3.0 includes an optional new DEX compiler called D8. It will eventually replace the DX compiler, but you can opt-in to use the new D8 compiler now.

DEX compilation directly impacts your app's build time, .dex file size, and runtime performance. And when comparing the new D8 compiler with the current DX compiler, D8 compiles faster and outputs smaller .dex files, while having the same or better app runtime performance.

To try it, set the following in your project's file:


For more information, see the blog post about the D8 compiler.

Google's Maven repository

Android Studio now uses Google’s Maven Repository by default instead of depending on the Android SDK Manager to get updates for Android Support Library, Google Play Services, Firebase, and other dependencies. This makes it easier to keep your libraries up to date, especially when using a continuous integration (CI) system.

All new projects now include the Google Maven repository by default. To update your existing project, add google() in the repositories block of the top-level build.gradle file:

allprojects {
    repositories {

Learn more about Google's Maven repository here.

Other changes

  • Native debugging with Android Studio no longer supports 32-bit Windows. We've chosen to focus on other platforms because very few developers are using this platform. If you are using 32-bit Windows and you plan to debug native code, you should keep using Android Studio 2.3.
  • Upgraded the base IDE to IntelliJ 2017.1.2, which adds a number of new features from 2016.3 and 2017.1, such as Java 8 language refactoring, parameter hints, semantic highlighting, draggable breakpoints, instant results in search, and much more.
  • Added many new lint checks.
  • Also see the latest Android Emulator updates.

2.3 (March 2017)

Android Studio 2.3.0 is primarily a bug fix and stability release, but it also includes a number of new features.

2.3.3 (June 2017)

This is a minor update to add support for Android O (API level 26).

2.3.2 (April 2017)

This is a minor update to Android Studio 2.3 for the following changes:

  • AVD Manager updates to support Google Play in system images.
  • Bug fixes for NDK builds when using R14+ of the NDK.

Also see corresponding updates for Android Emulator 26.0.3.

2.3.1 (April 2017)

This is a minor update to Android Studio 2.3 that fixes an issue where some physical Android devices did not work properly with Instant Run (see Issue #235879).


  • Android Studio can now convert PNG, BMP, JPG, and static GIF files to WebP format. WebP is an image file format from Google that provides lossy compression (like JPEG) as well as transparency (like PNG) but can provide better compression than either JPEG or PNG. For more information, see Convert images to WebP in Android Studio.
  • The new App Links Assistant simplifies the process of adding Android App Links to your app into a step-by-step wizard. Android App Links are HTTP URLs that bring users directly to specific content in your Android app.
  • The Layout Editor now includes support for two new ConstraintLayout features:
    • Define a view size based on an aspect ratio.
    • Create packed, spread, and weighted linear groups with constraint chains.
    For more information, see Build a Responsive UI with ConstraintLayout.
  • The Layout Editor also now lets you create a list of favorite attributes so you don't have to click View all attributes to access the attributes you use most.
  • When adding a material icon using the Vector Import Dialog (File > New > Vector Asset), you can now filter the list of available icons by category or by icon name. For more information, see Adding a material icon.
  • New and updated annotations. The new @RestrictTo annotation for methods, classes, and packages lets you restrict an API. The updated @VisibleForTesting annotation now has an optional otherwise argument that lets you designate what the visibility of a method should be if not for the need to make it visible for testing. Lint uses the otherwise option to enforce the intended visibility of the method.
  • New lint baseline support allows you to use a snapshot of your project's current set of warnings as a baseline for future inspection runs so only new issues are reported. The baseline snapshot lets you start using lint to fail the build for new issues without having to go back and address all existing issues first.
  • New lint checks, including the following:
    • Obsolete SDK_INT Checks: Android Studio removes obsolete code that checks for SDK versions.
    • Object Animator Validation: Lint analyzes your code to make sure that your ObjectAnimator calls reference valid methods with the right signatures and checks that those methods are annotated with @Keep to prevent ProGuard from renaming or removing them during release builds.
    • Unnecessary Item Decorator Copy: Older versions of the RecyclerView library did not include a divider decorator class, but one was provided as a sample in the support demos. Recent versions of the library have a divider decorator class. Lint looks for the old sample and suggests replacing it with the new one.
    • WifiManager Leak: Prior to Android 7.0 (API level 24), initializing the WifiManager with Context.getSystemService() can cause a memory leak if the context is not the application context. Lint looks for these initializations, and if it cannot determine that the context is the application context, it suggests you use Context.getApplicationContext() to get the proper context for the initialization.
    • Improved Resource Prefix: The existing resourcePrefix lint check had many limitations. You can now configure your project with a prefix, such as android { resourcePrefix 'my_lib' }, and lint makes sure that all of your resources are using this prefix. You can use variations of the name for styles and themes. For example for the my_lib prefix, you can have themes named MyLibTheme, myLibAttr, my_lib_layout, and so on.
    • Switch to WebP: This check identifies images in your project that can be converted to WebP format based on your project’s minSdkVersion setting. An associated quickfix can automatically convert the images, or you can convert images to WebP manually.
    • Unsafe WebP: If your project already includes WebP images, this check analyzes your project to ensure that your minSdkVersion setting is high enough to support the included images. For more information about WebP support in Android and Android Studio, see Which browsers natively support WebP? and Create WebP Images Using Android Studio.


  • A separate button to push changes with Instant Run: After deploying your app, you now click Apply Changes to quickly push incremental changes to your running app using Instant Run. The Run and Debug buttons are always available to you when you want to reliably push your changes and force an app restart.
    • Instant Run is supported only when deploying your app to a target device running Android 5.0 (API level 21) or higher.
    • Instant Run is no longer disabled for projects that link to external native projects using CMake or ndk-build. However, you can only use Instant Run to push incremental changes to your Java code, not your native code.
    • Cold swaps (which you can force for a running app by clicking Run ) are now more reliable. Forcing a cold swap also fixes the issue where changes to notification and widget UIs were not updated on the target device.
    • Includes optimizations that make app startup much faster. These optimizations may affect profiling, so you should temporarily disable Instant Run whenever profiling your app.
  • The AVD Manager and SDK Manager buttons are now included in the lean Navigation Bar as well as the full Toolbar. To use the lean Navigation Bar, click View to open the View menu, then ensure that Navigation Bar is selected and Toolbar is not selected.

  • The "Hybrid" debugger has been renamed to "Dual" debugger.
  • In the Run/Debug Configurations dialog, under Defaults in the left pane, the following run configuration names have changed with no behavior changes:
    • The JUnit name has changed to Android JUnit. If you have a project that uses JUnit run configurations, those configurations are transformed to Android JUnit run configurations the first time you open the project with Android Studio. A dialog appears to inform you of the name change.
    • The Android Tests name has changed to Android Instrumented Tests.
  • The GPU Debugger has been removed from Android Studio as of version 2.3. An open-source, standalone version of the tool is now available on GitHub.
  • The Run/Debug option is no longer available when you right-click a *.gradle build script.
  • All templates now use ConstraintLayout as the default layout.
  • The Widgets palette in the Layout Editor has been redesigned.

This release also includes a number of bug fixes. See all bug fixes in 2.3.0.

Known issue: Some device manufacturers block apps from automatically launching after being installed on the device. When deploying your app to a physical device using Android Studio 2.3, this restriction breaks the intended behavior of Instant Run and causes the following error output: Error: Not found; no service started. To avoid this issue, either use the emulator or enable automatic launching for your app in your device's settings. The proceedure for doing this is different for each device, so check the instructions provided by the manufacturer. For example, some affected Asus devices need to whitelist apps using the Auto-start Manager. To learn more about this issue, see Issue #235879.

2.2 (September 2016)

2.2.3 (December 2016)

This is a minor update to Android Studio 2.2. It includes a bug fixes focused around gradle, the core IDE, and lint.

Highlighted build changes:

  • ProGuard version rollback. Due to a correctness issue discovered in ProGuard 5.3.1, we have rolled back to ProGuard 5.2.1. We have worked with the ProGuard team on getting a fix quickly, and we expect to roll forward to ProGuard 5.3.2 in Android Studio 2.3 Canary 3.
  • Bug fix for aaptOptions IgnoreAssetsPattern not working properly (issue 224167)
  • Bug fix for Gradle autodownload for Constraint Layout library (issue 212128)
  • Bug fix for a JDK8/Kotlin compiler + dx issue (issue 227729)

See all bug fixes in 2.2.3.

2.2.2 (October 2016)

This is a minor update to Android Studio 2.2. It includes a number of small changes and bug fixes, including:

  • When reporting Instant Run issues through the IDE, the report now also includes logcat output for InstantRun events. To help us improve Instant Run, please enable extra logging and report any issues.
  • A number of small bug fixes for Gradle.
  • A fix for problems with generating multiple APKs.

2.2.1 (October 2016)

This is a minor update to Android Studio 2.2. It includes several bug fixes and a new feature to enable extra logging to help us troubleshoot Instant Run issues—to help us improve Instant Run, please enable extra logging and report any issues.


  • All new Layout Editor with tools custom-built to support ConstraintLayout.
  • New Layout Inspector lets you examine snapshots of your layout hierarchy while your app is running on the emulator or a device.
  • New Assistant window to help you integrate Firebase services into your app.
  • New APK Analyzer tool so you can inspect the contents of your packaged app.
  • New Espresso Test Recorder tool (currently in beta) to help you create UI tests by recording your own interactions.
  • New build cache (currently experimental) to speed up build performance.
  • New C/C++ build integration with CMake and ndk-build. Compile and build new or existing native code into libraries packaged into your APK, and debug using lldb. For new projects, Android Studio uses CMake by default, but also supports ndk-build for existing projects. To learn how to include native code in your Android application, read Add C and C++ Code to Your Project. To learn how to debug native code with lldb, see Debug Native Code.
  • New Samples Browser so you can easily look up Google Android sample code from within Android Studio to jump start app development.
  • New Merged Manifest Viewer to help you diagnose how your manifest file merges with your app dependencies across project build variants.
  • The Run window now contains log messages for the current running app. Note that you can configure the logcat Monitor display, but not the Run window.
  • New Android Emulator features:
    • Added new Virtual Sensors and Cellular > Signal Strength controls.
    • Added an LTE option to the Cellular > Network type control.
    • Added simulated vertical swipes for scrolling through vertical menus with a mouse wheel.
  • New Run/Debug Configuration features:
    • The Debugger tab of the Android App and Android Tests templates now contain several new options for debugging with LLDB.
    • The Profiling tab of the Android App and Android Tests templates now contain a Capture GPU Commands option for enabling GPU tracing. You can display GPU traces in the GPU Debugger (a beta feature).
    • The Android Tests template now has a Firebase Test Lab Device Matrix option for the Deployment Target.
    • The Native Application template has been deprecated. If you use this template in a project, Android Studio automatically converts it to the Android App template.
    • The Android Application template has been renamed to Android App.
  • Improved installation, configuration, performance, and UI features in the GPU Debugger (currently in beta).
  • Android Studio now comes bundled with OpenJDK 8. Existing projects still use the JDK specified in File > Project Structure > SDK Location. You can switch to use the new bundled JDK by clicking File > Project Structure > SDK Location and checking the Use embedded JDK checkbox.
  • Added new help menus and buttons in the UI so you can more easily find the online documentation.


  • Updated the IDE codebase from IntelliJ 15 to IntelliJ 2016.1
  • Instant Run now requires the platform SDK corresponding to the target device API level to be installed.
  • Instant Run will automatically disabled if user is running the app under a work profile or as a secondary user.
  • Fixed many reliability issues for Instant Run where changes were not getting deployed or the app would crash:
    • Some app assets were not deployed to your running app. ( Bug: #213454)
    • App crashes when user transitions between Instant Run and non Instant Run sessions where a Serializable class does not have serialVersionUID defined. (Bug: #209006)
    • Style changes aren’t reflected with Instant Run. (Bug: #210851)
    • Instant Run session is unreliable and causes FileNotFoundException. (Bug: #213083)
    • Changes to drawables not reflected until full rebuild is performed for KitKat. (Bug: #21530)
    • Resource changes aren’t reflected with Instant Run when custom sourceSets contain nested paths. (Bug: #219145)
    • Hot and warm swap don't work if changed class contains annotation with enum value. (Bug: #209047)
    • Changes to annotation data not reflected with Instant Run. (Bug: #210089)
    • Instant Run doesn't pick up code changes if you make changes outside the IDE. (Bug: #213205)
    • Instant Run session is unreliable due to mismatch security token. (Bug: #211989
    • Cold swap fails for devices that doesn’t properly support run-as. (Bug: #210875)
    • App crash after instant run restart. (Bug: #219744)
    • ClassNotFoundException observed when switching from Instant Run to Instant Debug. (Bug: #215805)
  • Improved performance for Gradle sync within the IDE, especially for large projects.
  • Improved build times for both full and incremental builds with new app packaging code.
  • Improved Jack compiler performance and features, including support for annotation processors and dexing in process. To learn more, read the Android plugin for Gradle 2.2.0 release notes.
  • Added an updated AccelerometerPlay sample so you can try out the emulator Accelerometer control. Select File > New > Import Sample to import the project.
  • Removed the Scale AVD property from the AVD Manager.
  • The Android Emulator -port and -ports command-line options now report which ports and serial number the emulator instance is using, and warn if there are any issues with the values you provided.
  • Improved the Create New Class dialog and the corresponding file templates. Note: If you've previously customized the AnnotationType, Class, Enum, Interface, or Singleton file templates, you need to modify your templates to comply with the new templates or you won’t be able to use the new fields in the Create New Class dialog.
  • Improved the Vector Asset Studio user interface and added support for Adobe Photoshop Document (PSD) files.
  • Improved the Image Asset Studio user interface.
  • Improved the Theme Editor's Resource Picker.
  • Fixed memory leaks and reduced overall memory usage in Android Studio.
  • Added a Background button in the SDK Manager so you can get back to work and install your packages in the background.
  • Improved Accessibility features, including support for screen readers and keyboard navigation.
  • Enhanced Code Analysis includes code quality checks for Java 8 language usage and more cross-file analysis.
  • Several toolbar icons have changed.

2.1 (April 2016)

The primary changes in this update provide support for development with the Android N Preview.

2.1.3 (August 2016)

This update adds compatibility with Gradle 2.14.1, which includes performance improvements, new features, and an important security fix. For more details, see the Gradle release notes.

By default, new projects in Android Studio 2.1.3 use Gradle 2.14.1. For existing projects, the IDE prompts you to upgrade to Gradle 2.14.1 and Android plugin for Gradle 2.1.3, which is required when using Gradle 2.14.1 and higher.

2.1.2 (June 2016)

This update includes a number of small changes and bug fixes:

  • Instant Run updates and bug fixes.
  • Improvements to LLDB performance and crash notifications.
  • Fixed a regression in the Android Studio 2.1.1 security update that caused git rebase to fail.

2.1.1 (May 2016)

Security release update.

The Android N platform adds support for Java 8 language features, which require a new experimental compiler called Jack. The latest version of Jack is currently supported only in Android Studio 2.1. So if you want to use Java 8 language features, you need to use Android Studio 2.1 to build your app.

Note: Instant Run is disabled when you enable the Jack compiler because they currently are not compatible.

Although Android Studio 2.1 is now stable, the Jack compiler is still experimental and you must enable it with the jackOptions property in your build.gradle file.

Other than the changes to support the N Preview, Android Studio 2.1 includes minor bug fixes and the following enhancements:

  • The Java-aware C++ debugger is now enabled by default when you're using an N device or emulator and select Native debugger mode (in the Debugger tab for your run/debug configuration).

For other build enhancements, including incremental Java compilation and dexing-in-process,update your Android plugin for Gradle to version 2.1.0.

2.0 (April 2016)

Note: If you are developing for the N Developer Preview, you should use Android Studio 2.1 Preview. Android Studio 2.0 does not support all the features required to target the N Preview. To learn more, read about how to properly set up your developer environment for the N Preview.

Instant Run:

  • Android Studio now deploys clean builds faster than ever before. Additionally, pushing incremental code changes to the emulator or a physical device is now almost instantaneous. Review your updates without redeploying a new debug build or, in many cases, without restarting the app.
  • Instant Run supports pushing the following changes to a running app:
    • Changes to the implementation of an existing instance method or static method
    • Changes to an existing app resource
    • Changes to structural code, such as a method signature or a static field (requires a target device running API level 21 or higher).
  • Read the documentation to learn more about Instant Run.

    Note: Instant Run is supported only when you deploy the debug build variant, use Android plugin for Gradle version 2.0.0 or higher, and configure your app's module-level build.gradle file for minSdkVersion 15 or higher. For the best performance, configure your app for minSdkVersion 21 or higher.

New additions to Lint:

  • Inspection of switch statements using @IntDef annotated integers to make sure all constants are handled. To quickly add any missing statements, use the intention action drop-down menu and select Add Missing @IntDef Constants.
  • Flags for incorrect attempts to use string interpolation to insert version numbers in the build.gradle file.
  • Flags for anonymous classes that extend the Fragment class.
  • Flags for native code in unsafe locations, such as the res/ and asset/ folders. This flag encourages storing native code in the libs/ folder, which is then securely packaged into the application’s data/app-lib/ folder at install time. AOSP: #169950
  • Flags for unsafe calls to Runtime.load() and System.load() calls. AOSP: #179980
  • Find and remove any unused resources by selecting Refactor > Remove Unused Resources from the menu bar. Unused resource detection now supports resources only referenced by unused resources, references in raw files such as .html image references, and tools:keep and tools:discard attributes used by the Gradle resource shrinker, while considering inactive source sets (such as resources used in other build flavors) and properly handling static field imports.
  • Checks that implicit API references are supported on all platforms targeted by minSdkVersion.
  • Flags improper usage of RecyclerView and Parcelable.
  • @IntDef, @IntRange, and @Size inspections are now also checked for int arrays and varargs.

Additional Improvements:

  • Optimized for Android Emulator 2.0, which is faster than ever before, supports a wider range of virtual devices, and features a drastically improved UI. To learn more about the new emulator, read the SDK Tools release notes.
  • Improvements to the Android Virtual Device Manager:
    • System images are now categorized under the following tabs: Recommended, x86, and Other.
    • Under advanced settings, you can enable multi-core support and specify the number of cores the emulator can use.
    • Under advanced settings, you can determine how graphics are rendered on the emulator by selecting one of the following options:
      • Hardware: use you computer's graphics card for faster rendering.
      • Software: use software-based rendering.
      • Auto: let the emulator decide the best option. This is the default setting.
  • Improved AAPT packaging times by specifying deploy target before the app is built. This allows Android Studio to efficiently package only the resources required by the specified device.
  • Added Cloud Test Lab integration to provide on-demand app testing with the convenience and scalability of a cloud service. Learn more about how you can use Cloud Test Lab with Android Studio.
  • Added a preview of the new GPU Debugger. For graphics intensive applications, you can now visually step through your OpenGL ES code to optimize your app or game.
  • Added Google App Indexing Test. Add support for URLs, app indexing, and search functionality to your apps to help drive more traffic to your app, discover which app content is used most, and attract new users. Test and validate URLs in your app all within Android Studio. See Supporting URLs and App Indexing in Android Studio.
  • Upgrades from the latest IntelliJ 15 release, including improved code analysis and performance. See What's New in IntelliJ for a complete description of the new features and enhancements.
  • XML editor auto-complete now adds quotations marks when completing attributes. To check if this option is enabled, open the Setting or Preferences dialogue, navigate to Editor > General > Smart Keys, and check the box next to Add quotes for attribute value on attribute completion. Issue: 195113
  • The XML editor now supports code completion for data binding expressions.

Older Releases