Emulator screen is flickering. [268498686]

Duplicate

of 290658423

Bug

Status Update

No update yet.

Description

cl...@gmail.com

created issue #1

Feb 10, 2023 02:41AM

Please Read:

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

Android Studio Version: Unknown

Emulator Version (Emulator--> Extended Controls--> Emulator Version): 32.1.11-9536276
HAXM / KVM Version: WHPX 10.0.22623

Android SDK Tools: 26.1.1

Host Operating System: Windows 10 Home Single Language

CPU Manufacturer: AMD CPU
Inside a VM
64-bit CPU

RAM: 7599 MB

GPU: GPU #1
Make: 10de
Model: NVIDIA GeForce GTX 1650
Device ID: 1f99

Build Fingerprint:

AVD Details: Name: google_service
CPU/ABI: x86_64
Path: C:\Users\Aryan Bisht\.android\avd\google_service.avd
Target: google_apis_playstore [Google Play] (API level 30)
Skin: pixel_4
SD Card: 512M
AvdId: google_service
PlayStore.enabled: true
avd.ini.displayname: google service
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:6b5943207fe196d842659d2e43022e20
hw.device.manufacturer: Google

hw.device.name: pixel_4
hw.gps: yes
hw.gpu.enabled: yes
hw.gpu.mode: auto
hw.initialOrientation: Portrait
hw.keyboard: yes
hw.lcd.density: 440
hw.lcd.height: 2280
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_playstore\x86_64\
runtime.network.latency: none
runtime.network.speed: full
showDeviceFrame: yes
skin.dynamic: yes
tag.display: Google Play

tag.id: google_apis_playstore
vm.heapSize: 228

Steps to Reproduce Bug:Screen is flickering.
Expected Behavior:

Observed Behavior:

Comments

ak...@google.com <ak...@google.com> Feb 10, 2023 03:42AM

Assigned to an...@google.com.

bo...@google.com <bo...@google.com> #2Feb 15, 2023 07:48PM

Reassigned to ya...@google.com.

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

ya...@google.com <ya...@google.com> #3Feb 15, 2023 09:28PM

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

cl...@gmail.com <cl...@gmail.com> #4Feb 16, 2023 01:51AM

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?

ya...@google.com <ya...@google.com> #5Feb 16, 2023 06:22PM

Reassigned to ca...@google.com.

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.

ma...@trimble.com <ma...@trimble.com> #6Feb 20, 2023 06:46PM

Hi this is the output txt flle

Message last modified on Feb 20, 2023 06:48PM

ya...@google.com <ya...@google.com> #7Feb 21, 2023 07:31PM

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

ca...@google.com <ca...@google.com> #8Feb 21, 2023 08:37PM

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?

Nvidia pc.mp4

14 MB

Download

ya...@google.com <ya...@google.com> #9Feb 22, 2023 11:56PM

DEBUG | emuglConfig_get_vulkan_hardware_gpu: Physical devices count is 0

Serdar, could you please take a look?

ca...@google.com <ca...@google.com> #10Feb 24, 2023 09:09PM

Reassigned to ya...@google.com.

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

ToT.mp4

10 MB

Download

32.1.11.mp4

5.5 MB

Download

ya...@google.com <ya...@google.com> #11Feb 27, 2023 10:57PM

Reassigned to de...@google.com.

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>

de...@google.com <de...@google.com> Mar 15, 2023 07:57PM

Accepted by de...@google.com.

de...@google.com <de...@google.com> #12Mar 17, 2023 05:22PM

Assigned to ra...@google.com.

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.

sa...@outlook.com <sa...@outlook.com> #13Apr 22, 2023 10:43PM

Does this look related?

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

li...@gmail.com <li...@gmail.com> #14May 13, 2023 06:59PM

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.

bugreport.zip

4.2 MB

Download

ra...@google.com <ra...@google.com> Oct 21, 2023 12:28AM

Reassigned to de...@google.com.

ya...@google.com <ya...@google.com> Oct 24, 2023 08:29PM

Status: Duplicate of

290658423

Issue 268498686

Description

Issue summary

Comments

ak...@google.com <ak...@google.com> Feb 10, 2023 03:42AM

bo...@google.com <bo...@google.com> #2Feb 15, 2023 07:48PM

ya...@google.com <ya...@google.com> #3Feb 15, 2023 09:28PM

cl...@gmail.com <cl...@gmail.com> #4Feb 16, 2023 01:51AM

ya...@google.com <ya...@google.com> #5Feb 16, 2023 06:22PM

ma...@trimble.com <ma...@trimble.com> #6Feb 20, 2023 06:46PM

ya...@google.com <ya...@google.com> #7Feb 21, 2023 07:31PM

ca...@google.com <ca...@google.com> #8Feb 21, 2023 08:37PM

ya...@google.com <ya...@google.com> #9Feb 22, 2023 11:56PM

ca...@google.com <ca...@google.com> #10Feb 24, 2023 09:09PM

ya...@google.com <ya...@google.com> #11Feb 27, 2023 10:57PM

de...@google.com <de...@google.com> Mar 15, 2023 07:57PM

de...@google.com <de...@google.com> #12Mar 17, 2023 05:22PM

sa...@outlook.com <sa...@outlook.com> #13Apr 22, 2023 10:43PM

li...@gmail.com <li...@gmail.com> #14May 13, 2023 06:59PM

ra...@google.com <ra...@google.com> Oct 21, 2023 12:28AM

ya...@google.com <ya...@google.com> Oct 24, 2023 08:29PM

Add comment

Issue metadata