First of all this is my laptop; MSI GL63 8RC, core i5 8th gen with upgraded RAM to 24 GB.
Installing android.iso in a standalone HVM does pass the moment when it says “OK. There is no hard drive to edit partitions.” But if I simply run android.iso in live mode, without actually installing, it works. I get no problems at all. No mouse problems as mentioned in various topics across the internet. But only issue I was getting is that everytime I poweroff my machine, I have to reboot android.iso in live mode which means I have to reinstall all the apps and sign in… etc. Which is obviously a frustrating. So, I passed the usb controller to HVM. Connected a 16 gig USB drive and booted from android.iso. This time I installed the android on a usb drive and obviously it worked. No errors like “OK. There is no hard drive to edit partitions.” Now if I need to use my android HVM, I simply pass the usb controller to the HVM, connect the USB drive and it boots fine, works great. Don’t have to reinstall apps every time I reboot.
But now the problem is that my laptop has only one USB controller which controls 3 USB type A and 1 USB type C port. So, if I pass that controller to the android HVM, I cannot any other usb devices in other app VMs, including my wireless mouse. Although,my touchpad works, but I don’t like using touchpad a lot.
My devices that I can pass to HVM;
I have explained my situation. So is there anyway possible that I can either install the android.iso on qubes HVM’s virtual drive? Or could I use my USB wireless mouse across the entire qubes OS even if I pass the usb controller to HVM where I am booting it from usb-drive-android?