Verified
Status Update
Comments
rk...@google.com <rk...@google.com>
rk...@google.com <rk...@google.com> #2
Hi, some users reported that installing "Vulkan SDK" helps with this issue. What is your GPU and its driver versions?
rk...@google.com <rk...@google.com>
ra...@google.com <ra...@google.com> #3
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
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
cm...@gmail.com <cm...@gmail.com> #4
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?
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?
rk...@google.com <rk...@google.com> #5
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.
cm...@gmail.com <cm...@gmail.com> #6
Hi this is the output txt flle
rk...@google.com <rk...@google.com> #7
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:
cm...@gmail.com <cm...@gmail.com> #8
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?
Could you please check this for me?
rk...@google.com <rk...@google.com> #9
DEBUG | emuglConfig_get_vulkan_hardware_gpu: Physical devices count is 0
Serdar, could you please take a look?
cm...@gmail.com <cm...@gmail.com> #10
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
rk...@google.com <rk...@google.com> #11
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>
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>
Description