![mac android emulator doesn mac android emulator doesn](https://i.stack.imgur.com/AwI79.png)
- MAC ANDROID EMULATOR DOESN'T BOOT PATCH
- MAC ANDROID EMULATOR DOESN'T BOOT SOFTWARE
- MAC ANDROID EMULATOR DOESN'T BOOT OFFLINE
- MAC ANDROID EMULATOR DOESN'T BOOT MAC
MAC ANDROID EMULATOR DOESN'T BOOT SOFTWARE
Here's the log of the latest M1 build using aosp_tv_arm64-eng:Įmulator: Android emulator version 30.3.5.0 (build_id 7036990) (CL:N/A)Įmulator: Found ANDROID_PRODUCT_OUT: /Volumes/android/out/target/product/generic_arm64Įmulator: Found build target architecture: arm64Įmulator: argv: '/Users/builduser/Downloads/Android Emulator.app/Contents/MacOS/emulator/emulator' program directory: '/Users/builduser/Downloads/Android Emulator.app/Contents/MacOS/emulator'Įmulator: emuDirName: '/Users/builduser/Downloads/Android Emulator.app/Contents/MacOS/emulator'Įmulator: try dir /Users/builduser/Downloads/Android Emulator.app/Contents/MacOS/emulatorĮmulator: Trying emulator path '/Users/builduser/Downloads/Android Emulator.app/Contents/MacOS/emulator/qemu/darwin-aarch64/qemu-system-aarch64'Įmulator: Found target-specific 64-bit emulator binary: /Users/builduser/Downloads/Android Emulator.app/Contents/MacOS/emulator/qemu/darwin-aarch64/qemu-system-aarch64Įmulator: Adding library search path: '/Users/builduser/Downloads/Android Emulator.app/Contents/MacOS/emulator/lib64'Įmulator: Adding library search path: '/Users/builduser/Downloads/Android Emulator.app/Contents/MacOS/emulator/lib64/gles_angle'Įmulator: Adding library search path: '/Users/builduser/Downloads/Android Emulator.app/Contents/MacOS/emulator/lib64/gles_angle9'Įmulator: Adding library search path: '/Users/builduser/Downloads/Android Emulator.app/Contents/MacOS/emulator/lib64/gles_angle11'Įmulator: Adding library search path: '/Users/builduser/Downloads/Android Emulator.app/Contents/MacOS/emulator/lib64/gles_swiftshader'Įmulator: Adding library search path for Qt: '/Users/builduser/Downloads/Android Emulator.app/Contents/MacOS/emulator/lib64/qt/lib'Įmulator: Silencing all qWarning() use qCWarning(.) instead: QT_LOGGING_RULES=default.warning=falseĮmulator: Setting Qt plugin search path: QT_QPA_PLATFORM_PLUGIN_PATH=/Users/builduser/Downloads/Android Emulator.app/Contents/MacOS/emulator/lib64/qt/pluginsĮmulator: Setting Qt to use software OpenGL: QT_OPENGL=softwareĮmulator: Setting QML to use software QtQuick2D: QMLSCENE_DEVICE=softwarecontextĮmulator: Overriding pre-existing bad Qt high dpi settings.Įmulator: Running :/Users/builduser/Downloads/Android Emulator.app/Contents/MacOS/emulator/qemu/darwin-aarch64/qemu-system-aarch64Įmulator: qemu backend: argv = "/Users/builduser/Downloads/Android Emulator.app/Contents/MacOS/emulator/qemu/darwin-aarch64/qemu-system-aarch64"Įmulator: qemu backend: argv = "-noaudio"Įmulator: qemu backend: argv = "-verbose"Įmulator: Concatenated backend parameters: All the image files are there, as far as I can tell There's some hiccups with CoreAudio not initializing on the M1 Mac, but disabling audio ( -noaudio) gets around this.Īs far as I can tell nothing is wrong from using -debug-init and -verbose emulator flags. I have also tried various GPU options when launching the emulator in case of graphical rendering issues.
MAC ANDROID EMULATOR DOESN'T BOOT PATCH
I was able to patch the build in necessary places to build to completion - this is all in build/soong so it's not the actual AOSP code needing a change.
MAC ANDROID EMULATOR DOESN'T BOOT OFFLINE
ADB show the emulator as offline once launched so it doesn't seem to be specific to a graphical issue more likely a boot.īuilding AOSP is not a problem, except when it comes to the M1 and needing the 11.x MacOSSDK.
![mac android emulator doesn mac android emulator doesn](https://docs.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/device-manager-images/win/01-devices-dialog.png)
MAC ANDROID EMULATOR DOESN'T BOOT MAC
I mainly use a M1 mac (aarm64), but have also tried on an Intel (x86_64), tried multiple image builds on each, but same result - black screen on boot. Any insights/gotchas would be super helpful. I'm newer to AOSP building, but now have successfully built various AOSP build configurations, but never been able to boot a built image.