Android Studio Emulator Network [267647323]

Fixed

Bug

Status Update

No update yet.

Description

do...@gmail.com

created issue #1

Feb 3, 2023 11:38AM

Description has been deleted.

Comments

do...@gmail.com <do...@gmail.com> #2Feb 3, 2023 01:48PM

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

ml...@google.com <ml...@google.com> Feb 3, 2023 02:50PM

Assigned to an...@google.com.

bo...@google.com <bo...@google.com> Feb 8, 2023 07:22PM

Reassigned to wd...@google.com.

wd...@google.com <wd...@google.com> #3Feb 8, 2023 07:52PM

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

Message last modified on Feb 8, 2023 07:58PM

do...@gmail.com <do...@gmail.com> #4Feb 9, 2023 09:20AM

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?

pixel2_33.txt

22 KB

View

Download

wd...@google.com <wd...@google.com> #5Feb 9, 2023 03:51PM

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> #6Feb 9, 2023 04:07PM

Hi this is the output txt flle

ma...@google.com <ma...@google.com> #7Feb 9, 2023 04:33PM

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

Message last modified on Feb 9, 2023 04:35PM

ma...@google.com <ma...@google.com> #8Feb 9, 2023 04:36PM

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?

wd...@google.com <wd...@google.com> #9Feb 9, 2023 08:26PM

Accepted by wd...@google.com.

DEBUG | emuglConfig_get_vulkan_hardware_gpu: Physical devices count is 0

Serdar, could you please take a look?

Message last modified on Feb 9, 2023 08:26PM

wd...@google.com <wd...@google.com> #10Feb 10, 2023 12:16AM

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

do...@gmail.com <do...@gmail.com> #11Feb 10, 2023 10:45AM

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>

Message last modified on Feb 10, 2023 10:50AM

wd...@google.com <wd...@google.com> #12Feb 10, 2023 02:12PM

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.

wd...@google.com <wd...@google.com> #13Mar 13, 2023 09:48PM

Does this look related?

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

Message last modified on Mar 13, 2023 09:49PM

wd...@google.com <wd...@google.com> #14Mar 14, 2023 02:56PM

Marked as fixed.

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.

Message last modified on Mar 14, 2023 03:41PM

go...@gmail.com <go...@gmail.com> #15Jul 19, 2023 10:45AM

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> #16Aug 28, 2023 02:58PM

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!