Package Details: qemu-android-x86 9.0.r2-2

Git Clone URL: (read-only, click to copy)
Package Base: qemu-android-x86
Description: Android-x86 environment via QEMU and VirGL
Upstream URL:
Licenses: GPL2, Apache, custom:Creative Commons 3.0 Attribution Unported
Submitter: Refutationalist
Maintainer: Refutationalist
Last Packager: Refutationalist
Votes: 5
Popularity: 0.007579
First Submitted: 2019-04-26 23:52
Last Updated: 2020-05-18 18:26

Latest Comments

1 2 Next › Last »

Janhouse commented on 2020-12-18 23:57

Could you please add option to remove ",format=raw,readonly" from system image line? It is handy to convert the image to qcow2 format and make it writable if necessary.

cosarara97 commented on 2020-12-09 20:22

How does one cleanly shut down the emulator? That is, is there any way to simulate the power button long press and access the shutdown menu?

Zeioth commented on 2020-09-05 01:29

It's been so easy to configure! Thank you for making this package!!

archmanjaro commented on 2020-09-03 17:36

I have installed the package in "Manjaro-KDE", everything is working fine but the audio/sound is crackling. It is horrible! please help me!

candybar commented on 2020-09-03 00:44

Is there a way to use a different resolution? If it's not 1280x720x32 then all I get is a black screen. I don't see anything useful from console :( Thanks. Version : 9.0.r2-2 Update/Edit: I am able to get normal display using VIDEO="768x1280". The mouse/cursor is offset incorrectly, however full screening the window fixes the mouse.

Popolon commented on 2020-05-17 15:43

inkscape 1.0 doesn't support -z anymore, I don't know what this option was for. -e is replaced by -o to export file name, so the line to build the icons in PKGBUILD, should be now : inkscape -o $pkgdir/usr/share/icons/hicolor/${size}x${size}/apps/qemu-android.png -w $size -h $size $srcdir/Android_robot.svg

romjan1412 commented on 2020-05-04 13:27

I'm having a problem with playing games. When I entered the game my keyboard and mouse don't work. It's workes fine when I'm not in any application. I'm confused. Do I need to set manually a hardware-keyboard to play games? if so, how do I do that? or any help would be appreciated.

Refutationalist commented on 2020-04-01 21:13

@greyltc I figured I might need to do this at some point. What you'd need to do is break /usr/share/android-x86/system.sfs out of it's SquashFS filesystem, and set SYSTEMIMG to the new filesystem you created in the config file.

It might also require some changes to the initrd, but if I recall it already had hooks for a rw root in it. Next chance I'll have to take a real crack at it is next week, I'll give it a shot if I don't hear anything.

greyltc commented on 2020-04-01 14:32

Hey, thanks very much for putting this together! Generally it's working great, but I'm having some trouble with input and I think I can solve it by editing some input device configuration files1 that I see in the image in /system/usr/idc/

Do you know how I can run this with /system mounted as writeable?

Or maybe you can directly help solve my input problem: Some apps do not seem to be coded to respond to mouse clicks and only respond to screen taps. They are unusable here (they're actually even unusable on my pixel 2 phone with a mouse connected via USB OTG). For example, from the app store "Tap Titans 2". For testing, you can deliver the app a tap at x=50, y=50 by running input tap 50 50 in the andorid root shell and the app registers that. Any help would be appreciated!

Refutationalist commented on 2020-03-23 11:55

I tried 9.0-r1 and it works, let me know if you find anything.