Emulator with API above API 30 not working in Intel 12th gen processor. [215231636]

Verified

Bug

Status Update

No update yet.

Description

ad...@gmail.com

created issue #1

Jan 19, 2022 05:38AM

Build: AI-203.7717.56.2031.7935034, 202111210535,

AI-203.7717.56.2031.7935034, JRE 11.0.10+0-b96-7249189x64 JetBrains s.r.o., OS Linux(amd64) v5.15.0-051500-generic, screens 1366.0x768.0

Emulator version:31.1.4
Android SDK platform tools version:31.0.3
Host cpu:12th Gen Intel(R) Core(TM) i5-12600K
Device name:Pixel 5

Emulator with system image android 11 is working properly but Android 12(31) and 12L(32) is not even loading in my PC.
It was working perfectly in my previous PC with Ryzen 3200G processor,So I believe that the issue is with intel 12th gen processor.FYI I'm not using any external GPU.running emulator in cpu.

idea.log

35 KB

View

Download

Comments

ku...@google.com <ku...@google.com> Jan 19, 2022 08:05PM

Assigned to an...@google.com.

bo...@google.com <bo...@google.com> #2Jan 19, 2022 11:24PM

Reassigned to wd...@google.com.

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

bo...@google.com <bo...@google.com> #3Jan 19, 2022 11:25PM

WARN - Emulator: Pixel 9 Pro XL API 35 - Vanguard anti-cheat software is detected on your system. It is known to have compatibility issues with Android emulator. It is recommended to uninstall or deactivate Vanguard anti-cheat software while running Android emulator.
2024-12-03 13:34:02,503 [ 53041] INFO - #com.android.adblib.impl.SessionDeviceTracker - trackDevices() failed, will retry in 2000 millis, connection id=32
java.lang.IllegalStateException: ADB location has not been initialized

ad...@gmail.com <ad...@gmail.com> #4Jan 20, 2022 05:56AM

Hi, I have installed the Vulkan SDK on my PC, and my GPU is an NVIDIA GeForce RTX 3060 Laptop GPU with driver version 30.0.15.1274. I also tried deactivating the Vanguard anti-cheat, but the AVD still terminated. I’ve attached the log file after deactivating Vanguard.

Regarding the ADB issue ("ADB location has not been initialized"), I ran the adb version command in Command Prompt and successfully retrieved the version. Could you help me check this again?

avd-log-without-modem.txt

219 KB

View

Download

tr...@gmail.com <tr...@gmail.com> #5Feb 12, 2022 04:22PM

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.

wd...@google.com <wd...@google.com> #6Mar 2, 2022 08:47PM

Hi this is the output txt flle

tr...@gmail.com <tr...@gmail.com> #7Mar 3, 2022 02:08PM

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

wd...@google.com <wd...@google.com> #8Mar 3, 2022 06:27PM

The attached TXT file contains the output after adding -gpu swangle. Following that, I manually updated the emulator from Android Emulator (35.2.10) Stable to Android Emulator (35.4.3) Canary. I also deleted the old AVD and created a new one, but it still terminated. I’ve attached the report generated after updating the emulator version.

Could you please check this for me?

Message last modified on Mar 3, 2022 06:28PM

bo...@google.com <bo...@google.com> #9Mar 3, 2022 06:53PM

DEBUG | emuglConfig_get_vulkan_hardware_gpu: Physical devices count is 0

Serdar, could you please take a look?

bo...@google.com <bo...@google.com> #10Mar 3, 2022 07:23PM

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

tr...@gmail.com <tr...@gmail.com> #11Mar 4, 2022 01:07AM

Hi this is the output crash id :

Microsoft Windows [Version 10.0.19045.5131]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>cd C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator

C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator>crashreport.exe -l
C:\Users\crazy\AppData\Local\Temp\\AndroidEmulator\emu-crash-35.4.3.db\reports\fa3cbbcf-3433-4a63-9c3a-f4d9f8ba847a.dmp

C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator>crashreport.exe -u
Report fa3cbbcf-3433-4a63-9c3a-f4d9f8ba847a is available remotely as: 9a9150ec7b65047e

C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator>

bo...@google.com <bo...@google.com> #12Mar 4, 2022 02:02AM

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.

ad...@gmail.com <ad...@gmail.com> #13Mar 19, 2022 04:25AM

Does this look related?

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

wd...@google.com <wd...@google.com> #14Mar 23, 2022 06:10PM

I’m not entirely sure if it’s directly related to the issue I’m facing. If it is, what solutions would you recommend to address this? So far, I’ve noticed that deviceCount is zero, and I suspect it could be related to the Vulkan loader not detecting any devices.

If you have any specific steps or fixes in mind, I’d appreciate your guidance. I can also run additional tests like vulkaninfo or check my Vulkan configuration if needed.

wd...@google.com <wd...@google.com> Jun 10, 2022 06:23PM

Status: Won't Fix (Obsolete)

jo...@gmail.com <jo...@gmail.com> #15Apr 23, 2023 07:20PM

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.

wd...@google.com <wd...@google.com> #16Apr 24, 2023 03:06PM

Status: Assigned (reopened)

Hi bro, the AVD is working now! After uninstalling the driver and reinstalling the latest version, the AVD opens successfully. Thank you so much for your help and for taking the time to assist me!

wd...@google.com <wd...@google.com> Apr 28, 2023 05:00PM

Accepted by wd...@google.com.

bo...@google.com <bo...@google.com> #17Apr 28, 2023 05:51PM

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.

wd...@google.com <wd...@google.com> #18May 2, 2023 10:48PM

Thank you for the update.

wd...@google.com <wd...@google.com> #19May 8, 2023 02:59PM

Marked as fixed.

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.

ra...@google.com <ra...@google.com> #20May 15, 2023 10:37PM

Verified by ra...@google.com.

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!