Android Studio 的客人已经7秒钟没有上线了

当我第一次在 Android Studio 中启动模拟器时,我得到一条信息消息,

客人7秒内没有上线,重试

我很好奇如何停止它,因为它在我的屏幕上大约40秒,我不能在模拟器中做任何事情。

42413 次浏览

maybe it's bug from intel haxm 6.2.1, because after i update i got same problem.

I solved by recreate emulator and testing again

Actually 'Cold Boot Now' may work in this situation avd manager with emulator action menu showing Cold Boot Now option

In "Your Virual Device" - Click on Duplicate OR Duplicate your Device. It will work like Charm.

  1. I specified AVD memory 2048 Mbyte instead of 1536 Mbyte. Things started to work again. (I'm developing on macbook.)
  2. I tried "Kuldeep Chandel" solution which is to duplicate AVD and my app runs again too. Because of that I specified RAM again as 1536 Mbyte. Guess what... It worked...

I think AVD confuses to handle things and we need to duplicate the current AVD, and use it instead of the problematic one.

tools->Android->AVD Manager

Choose the device then Cold Boot Now

I had the same problem. Selecting Cold Boot Now in AVD manager solves the problem.

But I have to open AVD manager each time when I want to launch Emulator and I just want to click on Run app button and select device, without opening AVD manager.

To solve this: open AVD manager -> Edit device -> Show Advanced Settings -> Boot option -> select Cold Boot instead of Quick boot.

I faced this issue on using Android API 28 emulator with Android Studio 3.0.1. Android API 28 requires Studio 3.1 and above. Once I updated Studio to 3.1.4 and Android Emulator to the latest version, it worked.

I managed to solve this issue by updating the .ini file manually. (I was not able to find a corresponding setting in the GUI.)

The location of the .ini file, relative to your home directory, is:

~/.android/avd/MyDevice.avd/config.ini

where MyDevice refers to the configured device name.

Depending on your operating system, you may find your home directory according https://en.wikipedia.org/wiki/Home_directory.

Change the entry within config.ini from no to yes:

fastboot.forceColdBoot=yes

Seting default settings for problem device from Android Device Manager resolved issue for me.