Release updates archive



Android Studio 3.2 Canary 13 is now available in the Canary and Dev channels.

For details of what's new in this canary release, see these sections of the release notes ...

Emulator 27.2.7 is now available in the Canary channel. It contains the following changes:

  • Fixed issues with some parts of the emulator UI being unresponsive if the Extended controls window was not opened at least once.
  • To address concerns of excessive memory usage, loading and saving of AVD snapshots has been optimized to only use RAM that is currently in the guest working set. This applies to Quick Boot snapshots saved automatically and to snapshots saved and loaded using the Save now and Load now buttons in the Settings panel of the Extended controls window.
  • On Windows with HAXM 7.2.0, AVD snapshot loads are optimized to load memory on demand, greatly decreasing snapshot load times. (HAXM 7.2.0 is not yet publicly released.)
  • Improved performance with Skia: For Android 8.1 (API 27) and Android P images, Android Emulator can render the Android UI with Skia. With Skia, UI rendering is smoother and uses fewer resources.
    • Currently, to use Skia, you need to manually enable it with the following commands in an adb shell:
      • su
      • setprop debug.hwui.renderer skiagl
      • stop
      • start
    • In upcoming Android P images and later, Skia will become the default renderer. Skia uses more OpenGL features than the current solution, so it’s important for us to get thorough test coverage across real-world scenarios. We would like to get feedback on this change as early as possible. Please file an issue if you experience problems with it.



Android Studio 3.2 Canary 12 is now available in the Canary and Dev channels.

For details of what's new in this canary release, see these sections of the release notes ...

The Android Studio 3.1.2 bug-fix update is available in the stable release channel.

This update fixes several bugs and improves the speed of lint checking in some scenarios. For a list of fixes in this update, see the ...


Android Studio 3.2 Canary 11 is now available in the Canary and Dev channels.

Emulator 27.2.5 is now available in the Canary channel. It contains the following changes:
  • Fixed a crash in Swiftshader when saving snapshots while video is playing.
  • Fixed concurrency issues when using Swiftshader for multi-threaded rendering.
  • Fixed a crash in Swiftshader when drawing with no program bound.
  • Fixed use-after-free / concurrency issues in screen recording.
  • Fixed "Recorder not initialized" error when issuing screen recording commands from the telnet console.
  • Fixed an issue where resizing the data partition through Android Studio did not work. https://issuetracker.google.com/issues/75259650
  • Snapshot save operations have been further optimized to consume less RAM. This should reduce the time to save snapshots in memory-constrained situations.
  • Snapshot load operations on Mac and Linux have been optimized to reduce latency shortly after snapshot load.

We are very happy to announce the release of ConstraintLayout 1.1.0. It’s available from the google maven repository:

dependencies {
implementation 'com.android.support.constraint:constraint-layout:1.1.0'
}

This stable release fixes various issues in the 1.0 release, as well as introducing a new Optimizer to increase layout performances. The main additions from 1.0 are new helper objects (notably barriers), complex chain support, dimension constraints and circular constraints.


Android Studio 3.2 Canary 10 is now available in the Canary and Dev channels.

Emulator 27.2.4 is now available in the Canary channel. It contains the following changes:
  • Fixed an issue that caused the rotate buttons to not work unless the Extended controls window was open. https://issuetracker.google.com/issues/77258337
  • Some changes have been made to improve the speed of saving an AVD snapshot. If you still experience unusually long saves, please file an issue in Issuetracker, providing details of your CPU, RAM, and settings of any antivirus / firewall / security software that is running.






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.