maximilionus/android-qemu-launcher

Utility and docs to run hardware-accelerated Android images on Linux QEMU KVM

android-qemu-launcher's Issues

Drive mounting docs/script

About

The issue with qcow2 disk image format is that you can not mount it as a simple image with mount tool. You have to load the kernel NBD module first, then connect to the drive with qemu-nbd and only then you can mount it.

Solution

As this is not a trivial task, it should be documented somewhere in this repo or even integrated into the main launcher as a special subset of CLI commands.

Extra

This feature was already implemented in the legacy versions of this launcher. The latest available versions of these scripts are located in the 5f0e39e commit tree:

• drive-mount.sh
• drive-unmount.sh

Display tweaking

Add instructions for VM display params tweaking to README.md.

Tweaks to document:

• Change screen resolution with Grub kernel entry
• Configure aspect ratio lock (Is it even possible?)

Mostly broken on Wayland + NVIDIA

About

Wayland is not working fine with every input and output device for this emulator. Yes, you can launch this VM in Wayland, but the performance and usability will be very poor.

Issues

Note
Most of the issues will be solved as qemu official Wayland support will roll out. XWayland is cursed without any workaround.

• Laggy input from mouse and keyboard.
• Virtual keyboard key sticking.
• Virtual mouse (tablet) invalid cursor offset.
• NVidia GPU poor performance.
• Full input lock on VM window on any action.

Solution

The solution is very simple and straightforward. Use Xorg, don't use Wayland. For now. Or swap this crappy GPU with AMD.

Make ADB feature switchable

That's probably a good idea to make adb switchable within the configuration file, so user can disable all the port forwarding to host, if adb access is not required at all. This switch is also probably should be turned off by default, to minimize the possibility of some weird random issues.