When running aosp build for aosp_x86-eng combo in emulator via android studio on windows it just stuck with black screen. How to debug this?

148 views
Skip to first unread message

Agry Gami

unread,
May 28, 2020, 7:16:45 PM5/28/20
to Android Building
I run following sequence of commands to build android image on my remote ubuntu machine:

> repo init -u https://android.googlesource.com/platform/manifest -b android-10.0.0_r33
...
> repo sync
...
> . build/envsetup.sh
> lunch
... selected "aosp_x86-eng" which was 23
> make -j4
... build succeed

Then I moved all image files from out directory to my windows machine and replace those that are in android sdk under `sdk\system-images\android-29\default\x86\`, there are two system.img and system-qemy.img files produced from build and system-qemu.img has same size as system.img in sdk directory, so I assume I need to use this, though I've tried all combinations (replacing all img file, only system.img) - nothing worked.

To run this image in emulator via android studio I've created new virtual device for Android 10 (i.e. without google-apis) and when started - it stuck in black screen. When I use original image from sdk - everything works. From build.prop files that lay around in sdk directory I see that it was built using "userdebug" mode, but there is no such combo option, only "-eng" is available.

How can I understand why this image doesn't work? It looks totally fine from all perspectives (except userdebug vs eng maybe). Or how can I build "userdebug" version of "aosp_x86" combo?


Reply all
Reply to author
Forward
0 new messages