After the emulator update, the network speed is slow [243053479]

Verified

Bug

Status Update

No update yet.

Description

a7...@gmail.com

created issue #1

Aug 19, 2022 02:56PM

Please Read:

https://developer.android.com/studio/report-bugs.html#emulator-bugs

Android Studio Version: Unknown

Emulator Version (Emulator--> Extended Controls--> Emulator Version): 31.3.10-8807927
HAXM / KVM Version: gvm 65544.0.0

Android SDK Tools: 26.1.1

Host Operating System: Windows 10 Enterprise LTSC 2021

CPU Manufacturer: AMD CPU
Virtualization is supported
64-bit CPU

RAM: 32692 MB

GPU: GPU #1
Make: 1002
Model: Radeon (TM) RX 480 Graphics
Device ID: 67df

Build Fingerprint:

AVD Details: Name: Pixel_5_API_30
CPU/ABI: x86
Path: C:\Users\Tom\.android\avd\Pixel_5_API_30.avd
Target: google_apis [Google APIs] (API level 30)
Skin: pixel_4
SD Card: 512M
AvdId: Pixel_5_API_30
PlayStore.enabled: false
avd.ini.displayname: Pixel 5 API 30
avd.ini.encoding: UTF-8
disk.dataPartition.size: 6442450944
fastboot.chosenSnapshotFile:
fastboot.forceChosenSnapshotBoot: no
fastboot.forceColdBoot: no
fastboot.forceFastBoot: yes
hw.accelerometer: yes
hw.arc: false
hw.audioInput: yes
hw.battery: yes
hw.camera.back: virtualscene
hw.camera.front: emulated
hw.cpu.ncore: 4
hw.dPad: no
hw.device.hash2: MD5:3274126e0242a0d86339850416b0ce34
hw.device.manufacturer: Google

hw.device.name: pixel_5
hw.gps: yes
hw.gpu.enabled: yes
hw.gpu.mode: auto
hw.initialOrientation: Portrait
hw.keyboard: yes
hw.lcd.density: 440
hw.lcd.height: 2340
hw.lcd.width: 1080
hw.mainKeys: no
hw.ramSize: 1536
hw.sdCard: yes
hw.sensors.orientation: yes
hw.sensors.proximity: yes
hw.trackBall: no
image.sysdir.1: system-images\android-30\google_apis\x86\
runtime.network.latency: none
runtime.network.speed: full
showDeviceFrame: yes
skin.dynamic: yes
tag.display: Google APIs

tag.id: google_apis
vm.heapSize: 256

Steps to Reproduce Bug:network speed is too slow
Expected Behavior:

Observed Behavior:

Comments

ya...@google.com <ya...@google.com> Aug 19, 2022 05:06PM

Assigned to an...@google.com.

bo...@google.com <bo...@google.com> Aug 19, 2022 05:07PM

Reassigned to wd...@google.com.

r....@gmail.com <r....@gmail.com> #2Aug 20, 2022 04:37PM

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

wd...@google.com <wd...@google.com> Aug 30, 2022 06:11PM

Accepted by wd...@google.com.

wd...@google.com <wd...@google.com> #3Aug 31, 2022 04:30PM

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 Aug 31, 2022 08:18PM

wd...@google.com <wd...@google.com> #4Aug 31, 2022 05:51PM

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?

Message last modified on Aug 31, 2022 06:06PM

wd...@google.com <wd...@google.com> #5Aug 31, 2022 06:21PM

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.

Message last modified on Aug 31, 2022 07:50PM

ra...@google.com <ra...@google.com> #6Aug 31, 2022 07:17PM

Hi this is the output txt flle

wd...@google.com <wd...@google.com> #7Aug 31, 2022 07:35PM

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> #8Aug 31, 2022 07:41PM

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> #9Aug 31, 2022 10:36PM

DEBUG | emuglConfig_get_vulkan_hardware_gpu: Physical devices count is 0

Serdar, could you please take a look?

Message last modified on Sep 1, 2022 02:28PM

wd...@google.com <wd...@google.com> #10Sep 6, 2022 03:17PM

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

wd...@google.com <wd...@google.com> Sep 9, 2022 08:17PM

Marked as fixed.

wd...@google.com <wd...@google.com> #11Sep 12, 2022 07:49PM

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 Sep 12, 2022 07:49PM

ra...@google.com <ra...@google.com> #12Sep 12, 2022 08:47PM

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.

ra...@google.com <ra...@google.com> #13Sep 13, 2022 09:51PM

Verified by ra...@google.com.

Does this look related?

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

jb...@gmail.com <jb...@gmail.com> #14Oct 15, 2022 01:45PM

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.