Fixed
Status Update
Comments
yb...@google.com <yb...@google.com> #2
does 31.1.x have this flicking problem ?
an...@gmail.com <an...@gmail.com> #3
Hi, are you using emulator in a tool window or the standalone emulator?
an...@gmail.com <an...@gmail.com> #4
using emulator in tool window.
an...@gmail.com <an...@gmail.com> #5
Carlos,
would you help to see if you could repro this issue? Please try to use an nVidia GeForce graphics card if possible.
would you help to see if you could repro this issue? Please try to use an nVidia GeForce graphics card if possible.
an...@gmail.com <an...@gmail.com> #6
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.
Found it occurs mostly when there is another OpenGL/3D app (Unity) running on the computer at the same time.
an...@gmail.com <an...@gmail.com> #7
Thank you for your report. That would help us isolating the issue.
da...@google.com <da...@google.com> #8
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?
an...@gmail.com <an...@gmail.com> #10
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.
ap...@google.com <ap...@google.com> #11
da...@google.com <da...@google.com> #12
Ranjit, can you please help verify this in 32.1.12 stable and 33.1.3 canary?
an...@gmail.com <an...@gmail.com> #13
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.
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.
Description
Version used: 1.1.1
Devices/Android versions reproduced on: Latest android emulator on Mac OS running Oreo image, Lenovo K6 Power
Also tried with Android studio 3.2 stable and Android 3.3 Preview version as well.
Building my project takes 15 min. If I comment out below line
annotationProcessor "android.arch.persistence.room:compiler:$ROOM_VERSION"
from my app's build.gradle, it takes only a minute to build the project. It's not a very big project (entity count wise) and I did not try reproducing the issue in a sample project. However, I can reproduce the
I have tried:
1. Cleaning. Rebuilding...
2. Invalidate caches/Restart.
3. Even tried migration to using all the androidx artifacts.
It seems like a bug in Room's annotationProcessor but I don't have a sample project to share.