IssueTracker

Hi, some users reported that installing "Vulkan SDK" helps with this issue. What is your GPU and its driver versions?

Could you please try stating the Emulator from the command line this way

cd C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator
emulator.exe -avd Pixel_9_Pro_XL_API_33 -wipe-data -no-snapshot -verbose -feature -Vulkan

and attach its output? If you notice any popups about missing dlls please include them here.

Thank you, please try adding -gpu swangle (this is a software GPU, it will be slow), I think for whatever reason we can't talk to your GPU.

Please consider trying the latest version we have here:

https://developer.android.com/studio/emulator_archive

DEBUG | emuglConfig_get_vulkan_hardware_gpu: Physical devices count is 0

Serdar, could you please take a look?

Please check if you have crashreports and if you do consider uploading them (please attach crash ids here):

cd C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator
crashreport.exe -l
crashreport.exe -u

Thank you a lot! We got the crash. I think we can't handle zero of VK devices well :) Serdar should know more why we get zero VK devices.

https://android.googlesource.com/platform/external/qemu/+/refs/heads/emu-master-dev/android/android-ui/modules/aemu-gl-init/src/android/opengl/emugl_config.cpp#525

Maybe we should return false if deviceCount is zero.

Does this look related?

https://github.com/KhronosGroup/Vulkan-Loader/issues/552

As I understand, Vulkan-Loader/issues/552 is talking about the case when there are two GPUs: an integrated AMD and a separate NVIDIA and somehow the AMD side prevents returning anything. If this is your case, I think the solution is to update the AMD GPU drivers.

Thank you for confirming this. We will fix the crash, but all we can do is to say "Your system has no Vulkan devices, update drivers or something" and exit.

Thanks for reporting this, a change is submitted (aosp/3393546) and will be available in the next canary builds of the emulator to correctly give an error for zero device cases. I'll close this one now as the booting issue is resolved with a driver update.

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

• Android Emulator 35.3.11 Stable

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

Further fixes for this issue are now available in:

• Android Emulator 35.4.5 Canary

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

RE#21 Another question, are you using the emulator in a tool window? I think it might be the specific scenario which still has bug.

I'm launching the emulator in a standalone window.

RE#24 Ok, I tried it myself and I could not reproduce unfortunately. With have you tried to move the emulator window? I think the time should be updated when you starting using the emulator. being said, would it be possible for you to try it again?

Sure, will try

Unfortunately, it happened again. Moving a window did not help.

Some additional info:

• I use a pair of external displays connected via Type-C, Bluetooth keyboard and mouse.
• Power adapter is plugged in. This way I can safely close a macbook lid and continue using it with the external displays. When macbook is sleeping I can wake it up by pressing a key on a keyboard or by clicking a mouse button.
• Today I left my workplace for 40-50 minutes. When I came back, external displays were in standby mode. After waking the macbook up, I've reproduced the issue.

RE#28 I realized what went wrong. My fix didn't merge into the 32 release. It's only available in the 31 release and the dev branch. Let me resolve that issue real quick and release a new version. Thanks for your input!

Thank you!

New CL merged. Will release a new version ASAP.

The fix is available in the next canary and stable release in June.

RE#36 To clarify, the bug is still reproducible for API 29 and API 30. Other APIs are working fine. We have an internal bug for tracking the API specific time update issue.

The new fix is merged

sivhuop@ Hi, the fix is not merge in (33.1.4-9936625). Would it be possible for you to upgrade your emulator the latest canary version or at least 33.3.14? Here is the link to the archived emualtor downloads.

RE#42 Thanks for the feedback on the emulator. To help us troubleshoot this issue further, we will need more information. Please share detailed reproduction steps as much as possible of the following information:

1, Run the emulator from command line with “$ANDROID_SDK_ROOT/emulator/emulator -avd <NameOfAVD> -verbose -wipe-data” and send the logs from terminal

2, Run adb bugreport and send the zip file.

I confirm 34.1.9 has no this issue anymore

https://developer.android.com/studio/releases/emulator#32-1-14