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.

To reproduce the issue. Open a fragment for example then request permission. send the app to background, open it again from recent apps. it will crash with the above exception.

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

IMPORTANT: Please try https://developer.android.com/studio/run/device#resolve-usb-issues first. Supply all required information if it is not a USB connection issue, e.g. idea.log (Select Help > Show Log in Finder/Files)

Studio Build: OS: Android Device model number & build number: Android SDK Platform Tools version: Attach the idea.log file via Help > Show Log in Finder.

Steps to Reproduce: 1. 2. 3.

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

This has been fixed already in aosp/1359642 and will be available in Activity 1.2.0-alpha07.

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

Reassigned to ca...@google.com.

Carlos,

would you help to see if you could repro this issue? Please try to use an nVidia GeForce graphics card if possible.

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

We have had this issue too. Appears on NVIDIA graphics, various different computers. Does not happen with the prior emulator version 31.x, occurs using system image 30 as above. We are using the emulator standalone.

Found it occurs mostly when there is another OpenGL/3D app (Unity) running on the computer at the same time.

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

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

Thank you for your report. That would help us isolating the issue.

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

I can't reproduce this on our corp machine that uses an Nvidia Quadro P1000 on 511.09 drivers but on my personal machine running an RTX 2080 Super on 512.15 drivers, I'm experiencing some graphical artifacts as shown in the attached video. Is this similar to what everyone is experiencing?

Nvidia pc.mp4

14 MB

Download

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

Hi Carlos,

would you help to test if this build fixes the issue?

https://android-build.googleplex.com/builds/pending/P50592976/emulator-windows_x64/latest/sdk-repo-windows-emulator-P50592976.zip

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

Reassigned to ya...@google.com.

I have tried that Build and the Emulator version that had the issue but can no longer reproduce them. I have also tried running Unity programs as suggest by

comment #6

but It seems it is an issue that is not as easily reproducible.

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 Devki,

Would you help to cp the following to the next stable and canary? Thanks!

https://android-review.git.corp.google.com/q/topic:%22no-window%22

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.

Ranjit, can you please help verify this in 32.1.12 stable and 33.1.3 canary?

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

Hi

I was also experiencing this issue on my Nvidia 1660 Super Graphics card, on the latest 32.1.12 stable.

I can confirm that using the 33.1.2 canary (I wasn't able to find the 33.1.3 canary publicly) appears to have fixed the issue.

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

Same issue with flickering.

I am using Pixel_7_API_33 with AS Hedgehog Canary 3. 1650 discrete graphics with latest 531.79 drivers. The emulator version is 33.1.10-10078095.

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