Status Update
Comments
ya...@google.com <ya...@google.com>
bo...@google.com <bo...@google.com>
ke...@netflix.com <ke...@netflix.com> #2
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> #3
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
zh...@google.com <zh...@google.com> #4
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?
sy...@syntezzz.ru <sy...@syntezzz.ru> #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.
bo...@google.com <bo...@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:
ja...@google.com <ja...@google.com> #8
ki...@gmail.com <ki...@gmail.com> #9
DEBUG | emuglConfig_get_vulkan_hardware_gpu: Physical devices count is 0
Serdar, could you please take a look?
ki...@gmail.com <ki...@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
wh...@gmail.com <wh...@gmail.com> #11
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>
ch...@gmail.com <ch...@gmail.com> #12
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.
Maybe we should return false
if deviceCount
is zero.
ch...@gmail.com <ch...@gmail.com> #14
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.
ch...@gmail.com <ch...@gmail.com> #15
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.
Description
Android Studio Version: Giraffe | 2022.3.1
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 32.1.14-10330179
HAXM / KVM Version: HVF 13.5.0
Android SDK Tools: 26.1.1
Host Operating System: macOS 13.5
CPU Manufacturer: Other CPU:
64-bit CPU
RAM: 16384 MB
GPU:
Build Fingerprint:
AVD Details: Name: Pixel_C_Tablet_API_33
CPU/ABI: arm64
Path: /Users/tomas/.android/avd/Pixel_C_API_33.avd
Target: google_apis [Google APIs] (API level 33)
Skin: 2560x1800
SD Card: 512 MB
AvdId: Pixel_C_Tablet_API_33
PlayStore.enabled: false
avd.ini.displayname: Pixel C Tablet API 33
avd.ini.encoding: UTF-8
disk.dataPartition.size: 6G
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:b6f369a5174fab4bbf46015b0d842ec6
hw.device.manufacturer: Google
hw.gps: no
hw.gpu.enabled: yes
hw.gpu.mode: auto
hw.initialOrientation: landscape
hw.keyboard: yes
hw.lcd.density: 320
hw.lcd.height: 1800
hw.lcd.width: 2560
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-33/google_apis/arm64-v8a/
runtime.network.latency: none
runtime.network.speed: full
showDeviceFrame: no
skin.dynamic: yes
skin.path.backup: /Users/tomas/Library/Android/sdk/skins/pixel_c
tag.display: Google APIs
vm.heapSize: 192
Steps to Reproduce Bug:Call PackageManager.hasSystemFeature(PackageManager.FEATURE_SENSOR_HINGE_ANGLE) and this method returns true on Pixel C tablet.
Expected Behavior:
Returns false on Pixel C tablet.
Observed Behavior: