Open clbr opened 5 years ago
The same happens when I add "vga=791 nomodeset" to the boot arguments. On 32-bit, adding these improves the display, but they weren't required.
The same happens with android-x86_64-8.1-r2-k49.iso.
VMware 15.5 does the same (underscore) with r2 x86, x86_64 and x86_64_k49.
x86 debug jams to random: [10.326] input, [59.106] random: crng init done, [59.106] random: 7 urandom warnings missed due to ratelimiting
also r1 x86_64_k49 ends up in command line, debug mode jams at same place [208.074] crng, urandom warnings
one question: why doesn't android run natively on x86 hardware, even if the image was for x86?
Have you tried to boot a GSI "open sourced" 'GSIs are for app developers to perform application validation and development purposes. They aren't to be redistributed by you or used in any way except as specifically set forth in the license terms enclosed in each individual download.' android 10 images?
https://developer.android.com/topic/generic-system-image/releases
the file system on the image should be ext4, but ubuntu 18.04.3 cannot recognize the boot partition after it has written it with Disk Image Writer.
qemu -m 3072 -cdrom android-x86_64-8.1-r2.iso The boot ends with a blinking underscore. The 32-bit version boots to GUI, but that has issue #56, google play services has stopped working.
When booting in debug mode, I see avc denied messages for surfaceflinger, same as here: https://superuser.com/questions/1344954/android-x86-8-1-installed-from-linux-rpm-not-fully-booting-looping-log-entrie/1396775
avc: denied { open } for pid=8599 comm="surfaceflinger" path="/dev/tty0" dev="tmpfs" ino=7383 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:tty_device:s0 tclass=chr_file permissive=1