Fixed
Status Update
Comments
me...@gmail.com <me...@gmail.com>
lf...@google.com <lf...@google.com>
lf...@google.com <lf...@google.com> #2
Hi, thanks for the report. Can you do "adb logcat" right when you start the emulator, so we can collect gpu info in SurfaceFlinger logs?
What is your CPU/GPU setup btw?
Also, consider trying -gpu angle_indirect and comparing with -gpu host for lagginess.
Finally, API 27 rendering lags a lot for me too, but API 25/26 are much smoother. Can you also give these API levels a try and report how laggy they are?
What is your CPU/GPU setup btw?
Also, consider trying -gpu angle_indirect and comparing with -gpu host for lagginess.
Finally, API 27 rendering lags a lot for me too, but API 25/26 are much smoother. Can you also give these API levels a try and report how laggy they are?
me...@gmail.com <me...@gmail.com> #3
Hi thanks for the reply,
I took logcat of device both at startup and at shutdown. but the one thing that got me to thinking was that this time the emulator worked fine and ran smooth. appears that the lag of emulator is quite random. Please check the attachments of the logcat.
Also my H/W setup is as follows:
Intel Core i7-4790k.
Nvidia GTX 960 2GB.
8GB 1600 MHz RAM.
API 25/26 works fine on my system.. Also there's one more issue i have renderer for emulator as gfx card but whenever the emulator launches it initializes opengl to 1.4 instead of 2.0 or 3.0. can you please look into that as well because my graphic card supports open gl 4.5
I took logcat of device both at startup and at shutdown. but the one thing that got me to thinking was that this time the emulator worked fine and ran smooth. appears that the lag of emulator is quite random. Please check the attachments of the logcat.
Also my H/W setup is as follows:
Intel Core i7-4790k.
Nvidia GTX 960 2GB.
8GB 1600 MHz RAM.
API 25/26 works fine on my system.. Also there's one more issue i have renderer for emulator as gfx card but whenever the emulator launches it initializes opengl to 1.4 instead of 2.0 or 3.0. can you please look into that as well because my graphic card supports open gl 4.5
lf...@google.com <lf...@google.com> #4
Thanks very much for the logcats!
In reference to opengl 1.4; I believe that emulator is already using OpenGL ES 2.0:
12-29 04:38:24.382 1430 1430 I SurfaceFlinger: OpenGL ES informations:
12-29 04:38:24.382 1430 1430 I SurfaceFlinger: vendor : Google (NVIDIA Corporation)
12-29 04:38:24.382 1430 1430 I SurfaceFlinger: renderer : Android Emulator OpenGL ES Translator (GeForce GTX 960/PCIe/SSE2)
12-29 04:38:24.382 1430 1430 I SurfaceFlinger: version : OpenGL ES 2.0 (4.5.0 NVIDIA 388.71)
You should also be able to run the emulator with OpenGL ES 3.0/3.1 by `echo "GLESDynamicVersion = on" >> ~/.android/advancedFeatures.ini" or launching with flag -feature GLESDynamicVersion (or going to extended settings page > Advanced > OpenGL ES API level > Renderer maximum) and selecting a API 24/25/26/27 x86 Google APIs / Play Store image.
Is the 1.4 you're talking about the EGL version?
12-29 04:38:24.211 1430 1430 I SurfaceFlinger: vendor : Android
12-29 04:38:24.211 1430 1430 I SurfaceFlinger: version : 1.4 Android META-EGL
That is expected; EGL is a separate API and 1.4 is one of the newer versions of it.
On the sudden lack of lag; We have some Windows 10 users who have had luck restarting their computers / turning off virus scanners.
In reference to opengl 1.4; I believe that emulator is already using OpenGL ES 2.0:
12-29 04:38:24.382 1430 1430 I SurfaceFlinger: OpenGL ES informations:
12-29 04:38:24.382 1430 1430 I SurfaceFlinger: vendor : Google (NVIDIA Corporation)
12-29 04:38:24.382 1430 1430 I SurfaceFlinger: renderer : Android Emulator OpenGL ES Translator (GeForce GTX 960/PCIe/SSE2)
12-29 04:38:24.382 1430 1430 I SurfaceFlinger: version : OpenGL ES 2.0 (4.5.0 NVIDIA 388.71)
You should also be able to run the emulator with OpenGL ES 3.0/3.1 by `echo "GLESDynamicVersion = on" >> ~/.android/advancedFeatures.ini" or launching with flag -feature GLESDynamicVersion (or going to extended settings page > Advanced > OpenGL ES API level > Renderer maximum) and selecting a API 24/25/26/27 x86 Google APIs / Play Store image.
Is the 1.4 you're talking about the EGL version?
12-29 04:38:24.211 1430 1430 I SurfaceFlinger: vendor : Android
12-29 04:38:24.211 1430 1430 I SurfaceFlinger: version : 1.4 Android META-EGL
That is expected; EGL is a separate API and 1.4 is one of the newer versions of it.
On the sudden lack of lag; We have some Windows 10 users who have had luck restarting their computers / turning off virus scanners.
lf...@google.com <lf...@google.com> #5
Also: "OpenGL ES 2.0 (4.5.0 NVIDIA 388.71)" above means that we indeed detect OpenGL 4.5 on your system and are using it, and that your current NVIDIA driver version is 388.71 (the latest I think).
In fact that GPU should be capable of OpenGL 4.6 (since 388.1x), it's just that we use 4.5 max currently because that's what we have tested the most so far.
In fact that GPU should be capable of OpenGL 4.6 (since 388.1x), it's just that we use 4.5 max currently because that's what we have tested the most so far.
me...@gmail.com <me...@gmail.com> #6
Alright! Thank you for the information. now i understood. but what was happening earlier was i was developing an android app that used google maps api v2. but when run the app in emulator the map didnt load stating android emulator requires opengl 2.0 and it reported that my emulator only had opengl 1.4..
lf...@google.com <lf...@google.com> #7
In that case, it could be because you are doing this on API 27, where our system image has a very unfortunate bug in it where ro.opengles.version is not written by the guest system, even though it is clearly using OpenGL ES 2+.
for google maps apis, for now, I would recommend using instead a system image such as api 25/26 where that problem does not occur. We will fix this in the next API 27 though. Very sorry for the inconvenience.
for google maps apis, for now, I would recommend using instead a system image such as api 25/26 where that problem does not occur. We will fix this in the next API 27 though. Very sorry for the inconvenience.
me...@gmail.com <me...@gmail.com> #8
Thank you for the info. I thought the issue was with my system hw/sw. thanks for clarifying this. I'll then work on lower Api's.
lf...@google.com <lf...@google.com> #9
Np, thanks for working with us to try things out!
Description
Android Studio Version:
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 27.0.2-4498654
HAXM / KVM Version: HAXM 6.2.1
Android SDK Tools: 26.1.1
Host Operating System: Windows 10 Enterprise Insider Preview
CPU Manufacturer: Intel CPU
Virtualization is supported
64-bit CPU
Steps to Reproduce Bug:
when shutting down the android in emulator i get the error:
Emulator: qemu-system-i386.exe: Unable to open C:\Users\Nihal\.android\avd\Nexus_5X_API_27_x86.avd\data\misc\pstore\pstore.bin: Permission denied
in event log.. also even after having high end graphics card the emulator lags a lot which didnt use to happen earlier...
Expected Behavior:
Observed Behavior: errors in event log and lag in emulator