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.

GREAT. Fixed! In version 32.1.1 on Fedora 36

Sorry everyone. I almost use Android Emulator for my development only. So now I really need a hot fix for this one. Anyone has solution or alternative Emulator that can be used for development and having same function of create custom location route?

Thanks for your reports. It seems there was a breaking change to the Google Maps javascript API. We are working with the Google maps team on a fix. Thanks for your patience and sorry for the inconvenience.

We have submitted a server-side change that should fix the problem. Could you please reboot emulator and see if it's fixed?

Sorry. The map can be loaded now. But I can not simulate the location. I try to set Location and then I use the Google and press Get current location, but it cannot get the location I just set. Anyone has solution for this?

Thanks your copration.

What is your emulator version? And could you also provide the emulator logs?

PSA (May 13, 2024)

In mid-May, Google maps in the Android Emulator Extended Controls will NO LONGER WORK in emulator versions before 34.2.13. Please update your emulator to avoid this issue.

For more into, see https://developer.android.com/studio/run/emulator-troubleshooting#google-maps-extended-controls