Android Emulator Stability and Efficiency Updates

Android Emulator Stability and Efficiency Updates



Posted by Neville Sicard-Gregory – Senior Product Supervisor, Android Studio

On the lookout for a extra secure, dependable, and performant Emulator? Obtain the newest model of Android Studio or guarantee your Emulator is updated within the SDK Supervisor.

A split screen shows Kotlin code on the left and the corresponding Android app display on the right in Android Studio. The app displays the Google Play Store, Photos, YouTube, Gmail, and Chrome icons.

We all know how essential the steadiness, reliability, and efficiency of the Android Emulator is to your on a regular basis work as an Android developer. After listening to worthwhile suggestions about stability, reliability, and efficiency, the Android Studio workforce took a step again from giant characteristic work on the Android Emulator for six months and began an initiative referred to as Undertaking Quartz. This initiative was made up of a number of workstreams geared toward decreasing crashes, dashing up startup time, closing out bugs, and organising higher methods to detect and stop points sooner or later.

Improved stability and reliability

A key aim of Undertaking Quartz aimed to scale back Emulator crashes, which might frustrate and block builders, reducing their productiveness. We centered on fixing points inflicting backend and UI crashes and freezes, up to date the UI framework, up to date our hypervisor framework, and our graphics libraries, and eradicated tech debt. This included:

    • Transferring to a more recent model of Qt, the cross-platform framework for constructing the graphical consumer interfaces of the Android Emulator, and making it secure on all platforms (as of model 34.2.13/ This was additionally a required change to make sure issues like Google Maps and the placement settings UI continued to work within the Android Emulator.
    • Updating gfxstream, the graphics rendering system used within the Android Emulator, to enhance our graphics layer.
    • Including greater than 600 end-to-end checks to the present pytests take a look at suite.

In consequence, now we have seen 30% fewer crashes within the newest secure model of Android Studio, as reported by builders who’ve opted-in to sharing crash particulars with us. Together with further end-to-end testing, this implies a extra secure, dependable, and better high quality expertise with fewer interruptions whereas utilizing the Android Emulator to check your apps.

A horizontal bar graph showing performance times of different versions of the Android emulator in milliseconds

This chart illustrates the discount in reported crashes by secure variations of the Android Emulator (newer variations are on the prime and shorter is healthier).

We have now additionally enhanced our opt-in telemetry and logging to higher perceive and determine the foundation causes of crashes, and added extra testing to our pre-launch launch course of to enhance our skill to detect potential points previous to launch.

Improved launch high quality

We additionally applied a number of measures to enhance launch high quality, together with rising the quantity and frequency of end-to-end, automated, and integration checks on macOS, Microsoft Home windows, and Linux. Now, greater than 1,100 end-to-end checks are ran in postsubmit, up from 500 checks prior to now implementation, on all supported working system platforms . These checks cowl varied eventualities, together with (amongst different options) totally different Android Emulator snapshot configurations, various graphics card issues , networking and Bluetooth performance, and efficiency benchmarks between Android Emulator system picture variations.

This complete testing ensures these essential parts perform accurately and interprets to a extra dependable testing surroundings for builders. In consequence, Android app builders can precisely assess their app’s conduct in a wider vary of eventualities.

Lowered open points and bugs

It was additionally vital for us to scale back the variety of open points and bugs logged for the Android Emulator by addressing their root trigger and making certain we cowl extra of the use instances you run into in manufacturing. Throughout Undertaking Quartz, we diminished our open points by 43.5% from 4,605 to 2,605. 17% of those have been actively fastened throughout Quartz and the remaining have been closed as both obsoleted or beforehand fastened (e.g. in an earlier model of the Android Emulator) or duplicates of different points.

Subsequent Steps

Whereas these enhancements are thrilling, it is not the top. We are going to proceed to construct on the standard enhancements from Undertaking Quartz to additional improve the Android Emulator expertise for Android app builders.

As at all times, your suggestions has and continues to be invaluable in serving to us make the Android Emulator and Android Studio extra sturdy and efficient in your growth wants. Sharing your metrics and crashdumps is essential in serving to us perceive what particularly causes your crashes so we are able to prioritize fixes.

You may opt-in by going to Settings, then Look and Habits, then System Settings, then Information Sharing, and choosing the checkbox marked ‘Ship utilization statistics to Google.’

The Android Studio settings menu displays the Data Sharing settings page, where 'Send usage statistics to Google' option is selected.

You should definitely obtain the newest model of the Android Emulator alongside Android Studio to expertise these enhancements.

As at all times, your suggestions is vital to us – examine recognized points, report bugs, recommend enhancements, and be a part of our vibrant group on LinkedIn, Medium, YouTube, or X. Collectively, we are able to create unimaginable Android experiences for customers worldwide!



author avatar
roosho Senior Engineer (Technical Services)
I am Rakib Raihan RooSho, Jack of all IT Trades. You got it right. Good for nothing. I try a lot of things and fail more than that. That's how I learn. Whenever I succeed, I note that in my cookbook. Eventually, that became my blog. 
rooshohttps://www.roosho.com
I am Rakib Raihan RooSho, Jack of all IT Trades. You got it right. Good for nothing. I try a lot of things and fail more than that. That's how I learn. Whenever I succeed, I note that in my cookbook. Eventually, that became my blog. 

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here


Latest Articles

author avatar
roosho Senior Engineer (Technical Services)
I am Rakib Raihan RooSho, Jack of all IT Trades. You got it right. Good for nothing. I try a lot of things and fail more than that. That's how I learn. Whenever I succeed, I note that in my cookbook. Eventually, that became my blog.