Status Update
Comments
jo...@google.com <jo...@google.com>
li...@tomtom.com <li...@tomtom.com> #2
jo...@google.com <jo...@google.com> #3
As a workaround, I was able to successfully downgrade android emulator to 28.
See:
I downloaded 28.0.25.0 (build_id 5395263) from here:
I deleted everything EXCEPT package.xml from
$HOME/Library/Android/sdk/emulator/
and replaced them with the contents of the extracted zip file.
Finally, make sure your AVD system image is NOT running api 30.
sdkmanager "system-images;android-27;google_apis_playstore;x86"
System images higher than api 29 are using a kernel format that the older emulator cannot understand.
Here's a workaround script you can try:
cd ~
mkdir emulator_downgrade
cd emulator_downgrade
wget https://dl.google.com/android/repository/emulator-darwin-5395263.zip
unzip emulator-darwin-5395263.zip
mv ~/Library/Android/sdk/emulator ~/Library/Android/sdk/previous-emulator
mv emulator ~/Library/Android/sdk/emulator
cp ~/Library/Android/sdk/previous-emulator/package.xml
~/Library/Android/sdk/emulator/package.xml
cd ~
~/Library/Android/sdk/emulator/emulator -version
~/Library/Android/sdk/emulator/emulator -list-avds
li...@tomtom.com <li...@tomtom.com> #4
li...@tomtom.com <li...@tomtom.com> #5
jo...@google.com <jo...@google.com> #6
Can't run emulator after upgrading to version 30.5.3.
My macOS is 10.12.6
li...@google.com <li...@google.com> #7
li...@tomtom.com <li...@tomtom.com> #8
For 30.2.6 the build number is 6962233 and that one still works for me on Sierra. Hope this gets fixed/backported. I'm waiting for new MbPros to be released (hopefully without touchbar). Don't want to upgrade my old one to >= Catalina.
li...@google.com <li...@google.com>
li...@tomtom.com <li...@tomtom.com> #9
li...@google.com <li...@google.com>
li...@google.com <li...@google.com> #10
30.2.6 (build 6962233) in Mojave works for me
li...@tomtom.com <li...@tomtom.com> #12
I can confirm that 7229563 works for me
li...@tomtom.com <li...@tomtom.com> #13
Hi, thanks for the report. Can you try the emulator from
https://ci.android.com/builds/submitted/7229563/sdk_tools_mac/latest/sdk-repo-darwin-emulator-7229563.zip ?
Another mojave user here with the problem. After replacing the emulator folder with the contents of the zip I can run the emulator again. Thanks.
li...@google.com <li...@google.com> #14
It works-ish, but I still get some library failures on launch...
handleCpuAcceleration: feature check for hvf
cannot add library /Volumes/Jeff/Library/Android/sdk/emulator/qemu/darwin-x86_64/lib64/vulkan/libvulkan.dylib: failed
added library /Volumes/Jeff/Library/Android/sdk/emulator/lib64/vulkan/libvulkan.dylib
cannot add library /Volumes/Jeff/Library/Android/sdk/emulator/qemu/darwin-x86_64/lib64/vulkan/libMoltenVK.dylib: failed
added library /Volumes/Jeff/Library/Android/sdk/emulator/lib64/vulkan/libMoltenVK.dylib
emulator: INFO: GrpcServices.cpp:301: Started GRPC server at 127.0.0.1:8554, security: Local
emulator: emulator window was out of view and was recentered
emulator: INFO: QtLogger.cpp:68: Warning: Failed to get QCocoaScreen for NSObject(0x0) ((null):0, (null))
li...@google.com <li...@google.com>
ap...@google.com <ap...@google.com> #15
I remember seeing these warning messages on previous emulator binaries as well. But they seem harmless.
Description
1.0.0-beta.1
Devices/Android versions reproduced on:
- Samsung Galaxy. Pixel 3. A wide range of devices. with Android 9, Android 10 and Android 11.
Android Auto version reproduced on:
- 5.9.604633-release
If this is a bug in the library, we would appreciate if you could attach, if possible:
- Sample project to trigger the issue.
In the code, getTemplate() could return null sometimes. It is not clear in the documentation if we could return null for this function.
- A screen record or screenshots showing the issue (if UI related).
- A bug report. See attached log.txt.