在更新到Android Studio 2后，当我试图运行我的应用程序并选择一个模拟器时，我等待模拟器启动，它突然被杀死。我可以看到模拟器进程几分钟，但从来没有GUI。在Android studio中，我得到了错误
android studio Error while waiting for the device: The emulator process for AVD was killed
即使我在Android Studio之外运行模拟器也会发生这种情况。我试用了Android 6和基于Android 4.4的模拟器。 在Windows 7 x64 PC上运行。类似于另一个StackOverflow帖子被关闭。我尝试了各种ram、VM堆和分辨率设置。
当前回答
总结一下:
Install and reinstall HAXM 7.5.6 (only available version) under 'Android SDK' settings. Try downloading it manually, even other versions (they don't work with Android SDK), installing it from the Android/Sdk folder, etc. sc query intelhaxm in cmd should show if it is running correctly. Virtualization is enabled in your BIOS and has been tested Made sure the PATH variables are correct (ANDROID_HOME / ANDROID_SDK_ROOT) but NOT (ANDROID_SDK_HOME) to the folder in your settings per Here. Otherwise, you will see EVENTS on the Android Studio splash screen. Try unchecking / rechecking Launch in a tool window in Emulator settings (and even Enable Device Frame in AVD settings) Try rebuilding in several different combinations of android, different phones, etc (but with same levels and packages ... 30 for example) Try Rebooting in several different configurations Make sure all SDK Tools are up-to-date, and even try a fresh install of Android Studio. However, tried removing all of them, and adding them back. Check your space, try to have 25GB maybe or more free Check for Virtual Box, Antivirus Software, etc. Open Android Studio with Administrator privileges
运行在双显示器/坞站上?
A)在不插任何插头的情况下运行模拟器，然后插回显示器!(我知道很奇怪)……或者更好的是…… B)创建一个新的硬件配置文件，它将使您能够将图形:自动更改为软件。
其他回答
如果你使用的是苹果硅(M1)芯片，请确保你使用的是基于arm64的模拟器:
如果不是，创建一个新的Virtual Device，并使用Other映像中的arm64-v8a映像。
这招对我很管用:
工具-> SDK管理器-> SDK工具(选项卡)->取消选择“Android模拟器”-> OK
现在，当你试图运行你的应用程序，或从AVD管理器启动设备时，它会给出“安装模拟器”错误->单击确定。 这将自动下载正确的版本。
转到设置avd，将“图形”从“快速启动”改为“冷启动”。
检查模拟器安装驱动器的剩余空间是否大于5gb
I have been struggling with the The emulator process for AVD Pixel_2_API_30 was killed for a while now. I was trying to launch a Pixel 2 API 30 running android 11.0, I tried all the possible solutions but nothing seemed to work. I decided t use a different setup e.g. Pixel 2 API 28 running android 9.0, and it worked perfectly. I am not sure what causes the bug in the higher-level API or android version though... So my suggestion is to change the API and android version IF all of the other solutions didn't work.
