Fixed
Status Update
Comments
lf...@google.com <lf...@google.com>
lf...@google.com <lf...@google.com> #2
Update: Can you try the latest emulator canary release (27.1.2)? We found that for some users at least, macOS can end up switching to the "Apple Software Renderer" on opengl core profile. We've since tried to fix it.
Also, are other API levels (such as 24, 25, 26) faster for you?
Also, are other API levels (such as 24, 25, 26) faster for you?
lf...@google.com <lf...@google.com> #3
Ah, sorry, misread your comment there.
Something to keep in mind is that API 27 uses a newer version of Android UI and might have performance problems :(
Something to keep in mind is that API 27 uses a newer version of Android UI and might have performance problems :(
lf...@google.com <lf...@google.com> #4
Especially the app drawer slide; we're not yet sure what is causing the problem, but when we find something we'll let you know.
an...@gmail.com <an...@gmail.com> #5
I tried 27.1.2. Nothing changed. Some animations are smooth: opening and closing activity, startup logo animation, Switch animation. It seems like only scrollable widgets (RecyclerView, ListView, ViewPager) are causing problems. Also, the less content scrollable widget has, more smooth animations I see. Maybe is hard to notice in the video, but transition between Home and Games are better than between Movies and Music. Scrolling the lines of content is lagging as well.
Maybe, is there anything I could help you with it?
Maybe, is there anything I could help you with it?
lf...@google.com <lf...@google.com> #6
Got it, so you're probably not on a software renderer then. Is it just isolated to the scrolling on API 27?
To diagnose steady rate of draw calls versus all the things going on in the Android UI when scrolling, can you try the GPU emulation stress test APK and compare between smoother API levels versus API 27?
https://github.com/google/gpu-emulation-stress-test/releases
If there is not much difference, then it's definitely specific to the UI rendering in API 27. It's strange that it went that slow though as in the video :/
What are your hardware specs?
To diagnose steady rate of draw calls versus all the things going on in the Android UI when scrolling, can you try the GPU emulation stress test APK and compare between smoother API levels versus API 27?
If there is not much difference, then it's definitely specific to the UI rendering in API 27. It's strange that it went that slow though as in the video :/
What are your hardware specs?
an...@gmail.com <an...@gmail.com> #7
> Is it just isolated to the scrolling on API 27?
No. It isn't, but it most noticeable on the scrolling.
I tried the stress test (1000 objects). First thing I noticed, API 27 doesn't support openGL3. I tested both of them against openGL2. The result is pretty the same:
API 27: 41 FPS
API 26: 44 FPS (ant 38 FPS on openGL3)
> What are your hardware specs?
mac book pro, 16 GB RAM, i7-4770HQ with Intel Iris Pro. No dedicated GPU.
Need to mention, my environment suffers from high memory pressure and I am always on 2-3 external displays.
No. It isn't, but it most noticeable on the scrolling.
I tried the stress test (1000 objects). First thing I noticed, API 27 doesn't support openGL3. I tested both of them against openGL2. The result is pretty the same:
API 27: 41 FPS
API 26: 44 FPS (ant 38 FPS on openGL3)
> What are your hardware specs?
mac book pro, 16 GB RAM, i7-4770HQ with Intel Iris Pro. No dedicated GPU.
Need to mention, my environment suffers from high memory pressure and I am always on 2-3 external displays.
ra...@gmail.com <ra...@gmail.com> #8
I have the same issue. I've checked it on MacBook and three Windows PCs.
Moreover, what is really strange, on API 27 Nexus 5x emulator I see this in the logcat:
E/Google Maps Android API: Google Maps Android API v2 only supports devices with OpenGL ES 2.0 and above
but on the API 27 Nexus 5 emulator Google Maps Android API v2 works ok.
Moreover, what is really strange, on API 27 Nexus 5x emulator I see this in the logcat:
E/Google Maps Android API: Google Maps Android API v2 only supports devices with OpenGL ES 2.0 and above
but on the API 27 Nexus 5 emulator Google Maps Android API v2 works ok.
lf...@google.com <lf...@google.com> #9
Hi, thanks for the extra feedback. That Maps API problem will need a system image revision to fix. The problem is that ro.opengles.version was not set in the emulator image. You'll need to use API 26 or lower for now.
I've found a workaround for the lagginess issue:
You can switch to the experimental Skia OpenGL renderer:
adb shell
su
stop
setprop debug.hwui.renderer skiagl
start
I've found a workaround for the lagginess issue:
You can switch to the experimental Skia OpenGL renderer:
adb shell
su
stop
setprop debug.hwui.renderer skiagl
start
lf...@google.com <lf...@google.com> #10
Also try those together:
Mac emulator, experimental:https://drive.google.com/open?id=1j5qTgJwZRVUO5mU3aMbDWzYniCIPbBxG
New API 27 image, experimental:https://drive.google.com/open?id=1DCTcHySNPS1mMs6wOkx7m_TqbWG2WyJU
To install the experimental API 27 image, replace the contents of the $ANDROID_SDK_ROOT/system-images/android-27/google_apis/x86/ folder with the contents of the google drive link.
Launch the Mac emulator on your current API 27 AVD with -feature IgnoreHostOpenGLErrors
How does it compare?
Mac emulator, experimental:
New API 27 image, experimental:
To install the experimental API 27 image, replace the contents of the $ANDROID_SDK_ROOT/system-images/android-27/google_apis/x86/ folder with the contents of the google drive link.
Launch the Mac emulator on your current API 27 AVD with -feature IgnoreHostOpenGLErrors
How does it compare?
an...@gmail.com <an...@gmail.com> #12
On the mac, it works smooth and nice. Can't wait to be released with Google Play store image
lf...@google.com <lf...@google.com> #13
Thanks for trying it out! Glad that is working better for you. We should have a new version out (that may also be play store approved) in the next month or so.
lf...@google.com <lf...@google.com> #14
We should have a version of API 27 out soon that has this feature flag (which should work with emulator canary 27.1.5 or later).
ra...@gmail.com <ra...@gmail.com> #15
Hello, it is still laggy using Android Emulator 27.1.6, any updates when you will release fixes?
lf...@google.com <lf...@google.com> #16
#15: 27.1.6 only changes the host side emulation engine, while the needed fixes are in the system image, which will be released later in February.
Description
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 27.0.2-4498654
HAXM / KVM Version: HVF 10.13.0
Android SDK Tools: 26.1.1
Host Operating System: Mac OS X 10.13.2
CPU Manufacturer: Intel CPU
Virtualization is supported
64-bit CPU
Info:
The interface is laggy. I tried various GPU and OpenGL settings in the previous emulator version, nothing helped. Seems like rendering is working in software mode. Older API (<=26) is working smooth.
Steps to Reproduce Bug:
Slide something. For example, slide down notification bar.
Expected Behavior:
Smooth sliding
Observed Behavior:
Sliding is very laggy. I see about 1-2FPS during sliding