How to Get Pain Relieving CBD Delivered to You Today

Are you or a loved one suffering from chronic pain? According to healthcare providers, chronic pain is the most difficult condition to treat. This is because chronic pain is, by nature, a complicated…

Smartphone

独家优惠奖金 100% 高达 1 BTC + 180 免费旋转




Quick Boot for Android Emulator in Practice

Recently a game changer was announced in Android Developers Blog — super fast boot for Android emulator. Less than 6 seconds and it’s ready to go.

How cool is that!

This is how the first boot looks:

Cold Boot

“Saving state…” is happening on exit automatically:

Saving emulator state on exit to restore it next time in a few seconds

But… what to do if Android emulator stuck at some point and doesn’t react to any interactions? Close emulator and reopen it again? Not really. Only if you want to save a broken state…

Let’s find out how we can configure and smarter use Quick Boot feature with UI or the command line.

This functionality is included in the newest version of Android Studio and enabled by default for your existing virtual devices and for new ones.

Fortunately, there are some configuration options which we can manage.

Boot options for a specific virtual device
Quick Boot configuration options

With option “Ask” on exit it will look like this:

A confirmation to save or not a current emulator state on exit

Once I had a case when Android emulator got frozen. I just exited the emulator in order to reboot it. I forgot that Quick Boot exist and it saved that unwanted state of my virtual device. Who cares if it does respond in my case? At least the boot was super fast! I love this feature.

So I needed to reboot my emulator without using a previous state. “How can I “unstuck” my emulator? Hm, I will disable Quick Boot feature for a while: close the emulator without saving the current state and reopen it to have a fresh new start! It will just do a cold boot, right? Easy!” I thought. Nope!

The configuration didn’t work as I expected. Quick Boot feature is so smart that it keeps the latest saved state from #1 (cold boot) … to #n (your last exit if enabled). As I already had a saved state #n, and even if on exit I declined saving the current state (#n+1), it boots to a previous saved state #n again. And why did I think that I could get a new #1? Never mind.

Alright. We can always ignore a saved state and reboot an emulator in UI or in the command line. Fresh start for my emulator!

Cold Boot

Thanks for Quick Boot feature! I really love it. Android emulator boots MUCH faster now!

Thanks for reading! 👍

PS. Less time on boot, more time on exit ;)

Add a comment

Related posts:

Notes on tech and design

How I built this course site and the choices behind my course design. “Notes on tech and design” is published by Malik Singleton in Data Skills.

How the Best Sales and CS Teams are Finding Expansion Opportunities with Slack

The original version of this post can be found on the Correlated website. (How the Best Sales and CS Teams are Finding Expansion Opportunities with Slack) You can see which users or accounts are more…

Why Lifestyle Investment Strategies Should Constantly Evolve

Most people use a simple and straightforward approach to investing. They assume it’s simply a means to prepare for retirement. But really investing is a delicate balancing act that should change…