Fixed
Status Update
No update yet.
Comments
il...@google.com
I grabbed a logcat from API 31 and another logcat from API 33 (first boot, Pixel 5 rather than Pixel 4a), in case they prove helpful. The failures seem the same, surfaceflinger crashing over and over again.
I noticed some older images had been re-published as arm64-v8a since I got the M1 and had to leave behind older images. I setup an AVD with API 23, and it booted up fine.
I noticed some older images had been re-published as arm64-v8a since I got the M1 and had to leave behind older images. I setup an AVD with API 23, and it booted up fine.
ou...@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.
il...@google.com
ap...@google.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 :)
il...@google.com
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.
sp...@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.
Description
Version used: android.arch.navigation:navigation-ui:1.0.0-alpha05
Devices/Android versions reproduced on: any
I suppose it's no a bug, but just a wrong behavior.
If i have i custom scheme, like "com.example://" - this could not be used and inside framework http(s) will be appended.
NavDeeplink states that there is a scheme pattern, that should detect if there is any scheme before ":", but it fails if there is any dot in scheme. So any scheme that contains dots will fail. Only schemes with "-" are supported by now.
private static final Pattern SCHEME_PATTERN = Pattern.compile("^(\\w+-)*\\w+:");