Google launches Android Studio 3.2 with support for App Bundle, Energy Profiler and Emulator Snapshots


Join the leaders of online gaming at GamesBeat Summit Next on November 9-10. Learn more about what comes next.

Google today released Android Studio 3.2, the latest version of its Integrated Development Environment (IDE), with over 20 new features, including a few related to Android Pie and the new Android app set. You can now download the new version for Windows, Mac and Linux directly from If you are already using Android Studio, you can get the latest version from the navigation menu (Help => Check for updates on Windows / Linux and Android Studio => Check for updates on OS X).

Google released Android Studio 3.1 in March. The version number 3.2 suggests that it is not a significant version, but if you build for Android and go through the list, you may find the opposite.

Here’s the recap of what version 3.2 brings to the table:

  • Slice Support: There is a new built-in template for Slices, which displays app content in Google Search Suggestions and the Google Assistant, to help you extend your app with the vendor’s new APIs. slices as well as new lint checks to make sure you’re following best practices. To use it, right-click on a project folder and navigate to New → Other → Slice Provider.
  • Sample Data: This feature allows you to use placeholder data to aid in your application design, helping you visualize layouts that depend on runtime data. You can add built-in sample data to populate views such as RecyclerViews, ImageViews, and TextViews through a pop-up window in the layout editor.
  • Material Design Update: When you start to migrate from Android Design Support Library to the new MaterialComponents Theme and App Library, you will have access to new and updated widgets like BottomAppBar, Buttons, cards, text fields, new font styles and more.
  • CMakeList Edition Support – For those who use C / C ++ in their application, there is now better CMake support. Code completion and syntax highlighting also now work on common CMakeList build script commands.
  • What’s New Wizard – A new wizard panel now opens automatically after an update to let you know about the latest IDE changes. You can also open the panel by going to Help → What’s New in Android Studio.
  • AndroidX Refactoring Support – One of the components of Android Jetpack is the introduction of Android Extension Libraries (AndroidX) as a replacement for Android Support Libraries. To add AndroidX to a new project, you just need to add android.useAndroidX=true to your to file. Additionally, there is a new built-in refactoring action to help you migrate your project to the new namespace and new dependencies. Additionally, if you have any Maven dependencies that have not migrated to the AndroidX namespace, the build system will automatically convert those project dependencies as well.
  • IntelliJ Platform Update – IntelliJ Platform 2018.1.6 release adds many improvements to data flow analysis, debugging, new inspections, inline external annotations, Git commits partial, and much more.
  • Kotlin Update – Kotlin 1.2.61 supports Android 9 Pie SDK compatible with Kotlin.
  • Android App Bundle: The new app publishing format is designed to help you deliver smaller APK files to your users and reduce your app download size. Google Play’s new app delivery model, called Dynamic Delivery, processes your app set to generate and deliver APKs optimized for each user’s device configuration, so they only download the code and download them. resources they need to run your application. With Android Studio 3.2 or via the command line, you can easily create your code as an app bundle and benefit from smaller APKs based on language, screen density and ABIs without modifying your app code. .
  • D8 Desugaring – In some cases, new Java language features require new language bytecodes and APIs. However, older Android devices may not support these features. Desugaring allows you to use these features on older devices by replacing new bytecodes and language APIs with old ones during the build process. D8 sugar removal is enabled by default, and you can now use most of the latest language changes while targeting older devices.
  • R8 Optimizer – The transition to using R8 as a replacement for ProGuard, optimizing and reducing Java language bytecode, has started. R8 is still experimental, so Google does not recommend releasing your app using it again.
  • Emulator Snapshots – Create a snapshot of the current state of your emulator, boot and switch to any snapshot in under 2 seconds. Based on the Android Emulator Quickboot feature, Android Snapshots are even faster to save and load thanks to under-the-hood speed improvements. When testing and developing your app, Android Snapshots allow you to preconfigure an Android Virtual Device (AVD) snapshot with the presets, apps, data, and settings you want in place, and revert to repeatedly at the same snapshot.
  • Microsoft Hyper-V Support: You can now run the Android emulator on Windows 10 computers with Hyper-V enabled. Intel HAXM is still the default hypervisor for the fastest Android emulator experience. However, thanks to recent open source contributions from Microsoft and the addition of the new Windows Hypervisor Platform (WHPX) API, the Android emulator can coexist with other Hyper-V-based applications, such as local virtual machines, by using the new Hyper-V. Support.
  • Support for AMD processors – AMD processors are now supported by Android emulator on Windows 10. Previously, running Android emulator was limited to slow software emulation when running Windows, but developers who have an AMD processor can now enjoy accelerated hardware performance.
  • Screen recording in Android emulator – You can now record both screen and audio on any level of Android API with the new screen recording feature in Android emulator. Latest Android Emulator (v28.0. +) Is no longer limited to screen recording on physical Android device only on Android 4.4 KitKat (API 19) and above, no audio. As a bonus, there is a built-in conversion for output to GIF and WebM format. You can trigger the new screen recording feature through the Android emulator Extended Controls panel, the command line, and from within Android Studio.
  • Virtual Stage Camera for Android Emulator – New Android Emulator Virtual Stage Camera helps you develop for ARCore, Google’s platform for creating augmented reality experiences. The emulator is calibrated to work with ARCore APIs for AR applications and also allows you to inject virtual scene bitmaps. The virtual stage camera can also be used as a standard HAL3 compatible camera.
  • ADB Connection Wizard – Android Studio 3.2 has a new wizard system to help you troubleshoot your Android ADB device connection issues. The ADB Connection Wizard walks you through common troubleshooting steps to connect your Android device to your development machine. You can trigger the wizard from the Run dialog box or by going to Tools → Connection Wizard.
  • Energy Profiler – The new Energy Profiler in the Android Studio performance profile suite can help you understand the energy impact of your app on an Android device. You can now view the estimated power consumption of system components and inspect background events that may be contributing to battery drain. To use the energy profiler, make sure you are connected to an Android device or emulator running Android 8.0 Oreo (API 26) or later.
  • System Trace: This new CPU profiler feature allows you to inspect how your application interacts with system resources with fine granularity. Inspect the exact timings and durations of your thread states, see where your CPU bottlenecks are across all cores, and add custom trace events for analysis. To use system trace, start profiling your application, click CPU Profiler, and then choose the system trace logging configuration.
  • Profiler Sessions – We now automatically save Profiler data as “sessions” for later review and inspection while Android Studio is open. We’ve also added the ability to import and export your CPU records and heap dumps for further analysis or inspection with other tools.
  • Auto Processor Logging: You can now automatically log processor activity using the Debug API. After you deploy your app to a device, the profiler will automatically start recording CPU activity when your app calls. startMethodTracing(String tracePath), and stop recording when your application calls stopMethodTracing(). Likewise, you can now also automatically start recording processor activity on application startup by enabling the Start recording method trace on startup option in your runtime configuration.
  • JNI Reference Tracking – For those of you who have C / C ++ code in your Android app, you can now inspect the memory allocations of your JNI code in the memory profiler. As long as you deploy your app to a device running Android 8.0 Oreo (API 26) and later, you can explore the allocation call stack from your JNI baseline. To use the feature, start a memory profiler session and select the JNI heap from the Live Allocation drop-down menu.

This release includes many stability and performance fixes in addition to new features (full release notes). Google has not shared its plans for the next version.


VentureBeat’s mission is to be a digital public place for technical decision-makers to learn about transformative technology and conduct transactions. Our site provides essential information on data technologies and strategies to guide you in managing your organizations. We invite you to become a member of our community, to access:

  • up-to-date information on the topics that interest you
  • our newsletters
  • Closed thought leader content and discounted access to our popular events, such as Transform 2021: Learn more
  • networking features, and more

Become a member


Comments are closed.