Verified
Status Update
No update yet.
Comments
a1...@gmail.com
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.room:room-compiler:2.7.0-alpha07
ml...@google.com
a1...@gmail.com
I was excited to see "[Bug Fix] Error with launching API 33 AVD on Mac M1" in the Emulator release notes (https://developer.android.com/studio/releases/emulator ) but alas, there is no change. Surfaceflinger still crashes repeatedly in the API 31 and API 33 images.
I was just prompted to upgrade my Emulator to 31.3.12 but there aren't release notes for it yet. I did not help with this issue, surfaceflinger still crashes repeatedly in the API 31 and API 33 images.
I was just prompted to upgrade my Emulator to 31.3.12 but there aren't release notes for it yet. I did not help with this issue, surfaceflinger still crashes repeatedly in the API 31 and API 33 images.
a1...@gmail.com
I did some more googling and went from https://stackoverflow.com/questions/45244891/android-emulator-inside-docker-container-surfaceflinger-crashing-endldess-boot-l to https://www.jc-tech.info/2018/04/10/android-emulator-crashing-due-to-access-violation/ , which suggested changing the Emulator to use SwiftShader.
Changing the Emulator to use SwiftShader instead of Desktop native OpenGL allowed the Emulator to run from Terminal. At least for API 31 and 33, but not for API 30. Also, nothing was working when embedded into Android Studio...
I'm not sure why my Emulator wasn't set to auto (may literally have been for ancient Android 2.3 images?), but I set it to auto (see screenshot) and now everything works!
I was able to launch all of these from within Android Studio and deploy apps to them: API 23, 28, 30, 31, 32 and 33.
I guess that means you can close this :)
Changing the Emulator to use SwiftShader instead of Desktop native OpenGL allowed the Emulator to run from Terminal. At least for API 31 and 33, but not for API 30. Also, nothing was working when embedded into Android Studio...
I'm not sure why my Emulator wasn't set to auto (may literally have been for ancient Android 2.3 images?), but I set it to auto (see screenshot) and now everything works!
I was able to launch all of these from within Android Studio and deploy apps to them: API 23, 28, 30, 31, 32 and 33.
I guess that means you can close this :)
co...@sim.org
Thank you for the above, this fixed a long-standing problem for me!
For those coming after, you get to this setting when you start up the emulator, even though it's not starting up normally, click on the three dots on the toolbar to the side of the emulator window, click Settings, then on the right side you'll see Advanced at the top. That's where to choose autoselect as in above screenshot.
For those coming after, you get to this setting when you start up the emulator, even though it's not starting up normally, click on the three dots on the toolbar to the side of the emulator window, click Settings, then on the right side you'll see Advanced at the top. That's where to choose autoselect as in above screenshot.
bo...@google.com
ya...@google.com
Checked with the latest Android Studio, gpu auto should be the default option.
Also, cannot repro the issue with any gpu settings. If anyone could repro it, please run the emulator from command line:
/path/to/emulator -avd [your_avd_name] -feature GLESDynamicVersion -verbose
and upload the logs here. I will close the issue for now, and will reopen if there would be more reports or logs.
Also, cannot repro the issue with any gpu settings. If anyone could repro it, please run the emulator from command line:
/path/to/emulator -avd [your_avd_name] -feature GLESDynamicVersion -verbose
and upload the logs here. I will close the issue for now, and will reopen if there would be more reports or logs.
a1...@gmail.com
I just updated to the current emulator release. The issue still reproduces for me if I set the renderer to "Desktop native OpenGL" and API level to "Compatibility" (but not if I leave both on auto).
I have attached the output from ~/Files/Android/sdk/emulator/emulator -avd Pixel_4a_API_33 -feature GLESDynamicVersion -verbose 2>&1
I have attached the output from ~/Files/Android/sdk/emulator/emulator -avd Pixel_4a_API_33 -feature GLESDynamicVersion -verbose 2>&1
mr...@gmail.com
ya...@google.com
Hi,
please try to update to the latest emulator (33.1.6+), thanks!
a1...@gmail.com
Tested just now using Android emulator version 32.1.12.0 (build_id 9751036) on a MacBook Pro 14" with M1 Pro CPU.
Launching a Pixel 4a AVD using API 33.
surfaceflinger (inside the AVD) still crashes if I set the renderer to "Desktop native OpenGL" and API level to "Compatibility".
Everything still works just fine if I set both settings to auto.
So, no change from 2 Feb, when I last reported that setting both things to auto fixed this.
Launching a Pixel 4a AVD using API 33.
surfaceflinger (inside the AVD) still crashes if I set the renderer to "Desktop native OpenGL" and API level to "Compatibility".
Everything still works just fine if I set both settings to auto.
So, no change from 2 Feb, when I last reported that setting both things to auto fixed this.
ap...@rtwsa.com
For me, using emulator 32.1.13, API 33 is starting OK with auto OpenGL ES Renderer. But on any API < 32, I have to select SwiftShader, or I only get a black screen.
ya...@google.com
ya...@google.com
Hi,
If you got the chance, would you help to run the emulator again with -feature GLESDynamicVersion -verbose, then send us both the emulator console output and logcat?
We are looking for the OpenGL ES version there, we want them to have GLES version number >=3.0 (Mac OpenGL core profile 4.1).
The logs in #7 and #2 have different version numbers. So we want to check if logcat gets the right version after using -feature GLESDynamicVersion.
a1...@gmail.com
I have tested just now using Android emulator version 32.1.13.0 (build_id 10086546) on a MacBook Pro 14" with M1 Pro CPU.
Launching a Pixel 4a AVD using API 33 (revision 12).
I tried all combinations of Desktop/Swiftshader + Compatibility/Max. Only Desktop + Compatibility results in surfaceflinger crashing. I included the other logs as well in case they prove useful.
I noticed on the crashing one that surface flinger crashed just after the line "SurfaceFlinger: Enter boot animation" in logcat so I trimmed the other logcats shortly after that line (since they were otherwise over 2.5M).
Hopefully something in there helps...
Launching a Pixel 4a AVD using API 33 (revision 12).
I tried all combinations of Desktop/Swiftshader + Compatibility/Max. Only Desktop + Compatibility results in surfaceflinger crashing. I included the other logs as well in case they prove useful.
I noticed on the crashing one that surface flinger crashed just after the line "SurfaceFlinger: Enter boot animation" in logcat so I trimmed the other logcats shortly after that line (since they were otherwise over 2.5M).
Hopefully something in there helps...
ya...@google.com
Thank you for your logs. That is extremely helpful. The logs showed that we sent a wrong GLES version number to the guest. I can narrow down the root cause now.
ya...@google.com
Hi Devki,
please help to cp aosp/2620446 to next stable. Thanks!
de...@google.com
vk...@google.com
This issue not reproducing in Emulator version: 32.1.14-10330179
de...@google.com
um...@gmail.com
Android Emulator / Virtual Device not working on M1 - 8GB(Unfortunately, your computer does not support hardware accelerated virtualization). Is the issue resolved to run android virtual device on M1 Mac- Ventura-V-13.2
ya...@google.com
Re #16,
it looks like a different bug. Would you file a new issue with all the emulator console output attached? Thanks
it looks like a different bug. Would you file a new issue with all the emulator console output attached? Thanks
Description
STEPS TO REPRODUCE:
1. Setup an AVD with API >30, arm64-v8a (Google APIs). In my case, I used Pixel 4a as the device (since that's what I have).
2. Start the emulator
API 30 works.
API 28 also works.
I assumed this was a temporary issue with API 31... but the issue persists with API 32 which makes testing things difficult without using my actual phone.
ATTACH SCREENSHOTS/RECORDINGS OF THE ISSUE
There's nothing to see, just the "Google" splash screen.
ATTACH LOG FILES (Select Help > Show Log in Files, or Show Log in Finder on a Mac)
Emulator bug report thing doesn't work (because the system hasn't come up?), but I captured a logcat showing something crashing over and over again.
Android Studio Chipmunk | 2021.2.1 Patch 2
Build #AI-212.5712.43.2112.8815526, built on July 11, 2022
Runtime version: 11.0.12+0-b1504.28-7817840 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 12.5.1
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 8
Registry: external.system.auto.import.disabled=true
Non-Bundled Plugins: org.jetbrains.kotlin (212-1.7.10-release-333-AS5457.46)
Android Emulator 31.3.10 (installed by Android Studio)
MacBook Pro (14-inch, 2021)
macOS Monterey 12.5.1
M1 Pro CPU
16GB RAM