NOTE: This is a wiki, edit any mistakes you see

First, BlissOS as a template with qubes integration would be great, but to the best of my knowledge, no one has done that.

Also, note there is more then one "android on PC" type distribution. I know of: * Android-x86 * BlissOS (aparently a derivative of Android-x86) * Waydroid

Also note that waydroid has a "Waydroid template" guide at: https://forum.qubes-os.org/t/waydroid-template/23356/59

However, there can still be reasons to use BlissOS over waydroid, like for example that BlissOS supposedly supports bluetooth, while waydroid does not.

This article is intended to collect information into one spot, instead of in multiple posts.

BlissOS install: (This mostly comes from the steps @Cubadicto followed to install BlissOS in a qube with internet working (https://forum.qubes-os.org/t/bliss-os-no-internet-connection/23154/6))

  1. First choose a BlissOS version from: https://blissos.org/index.html#download
  2. Choose a Bliss OS .iso.
  3. Download Bliss OS and its sha256 file and check both checksums are equal, just to avoid possible strange errors.
  4. Provision the Bliss OS qube,
  5. very important! Do not move on until you can see all the following info in the qube settings under the "net qube" section:
  6. Install Bliss OS via qube settings -> Advanced -> boot qube from CD-ROM. I recommend you to prepare partition for OTA updates. I have no idea if necessary, but worked in my case. I also recommend installing grub2 initializer. Also i recommend creating partition with dos tag instead of gtp tag if asked (when creating the partition)
  7. Next follow this steps to boot Bliss OS in a qube (maybe u know but just to write down all steps): https://www.youtube.com/watch?v=piYcKnwpKPE

  8. When booted, try to open Smart Dock and give requested permissions. Is not mandatory, but will make things easier

  9. Next open apps menu and find one called “Bliss Ethernet Manager”. That’s why i told u to check checksums, if checksums are correct, this app might be installed, which is the key here. Open the app

  10. Change the IP Assignment to “Static”, change IP address to the same qube IP assigned address that you saw before with the netmask (e.g: ip: 10.0.0.4, mask: 255.255.255.255. Then you write IP Address: 10.0.0.4/32), change Gateway address to the one assigned to the qube (e.g: 10.0.0.1), and add both DNS Addresses separated with a comma (e.g: 10.0.0.2,10.0.0.3). Finally press “Interface Down” button (if nothing happens, try the “Interface Up”, but should be “Interface Down” correct). Bliss OS should be restart, and you might see in notification area that no WiFi option is available but Internet instead. Try to open any page in the browser, it might work!!

I hope this thread is not much Bliss OS specific, the key is simply using the Bliss OS ethernet app and assign the same qubes addresses

It's possible for "bliss ethernet manager" to set the ip address, but not set up the route. If this happpens, you can manually add the routes with: 1. Go go to apps list and run “KernelSU” 2. Give termux su permissions 3. go back to termux and do “su” again (it should work) 4. run “ip route add {gateway address} dev eth0 scope link" 5. run “ip route add 0.0.0.0/0 via {gateway address}”

However, while the routes are now there, pings still dont get through at this point in bliss 15.9.1 .

Alternate option for #10: If there is no “Bliss Ethernet Manager” app, then you probably should have downloaded version 15.9. Or if the Bliss Ethernet Manager is there but does not work for you, you can still get partial networking going anyway by: (this worked with version 14.10, but is not working with version 15.9) 1. Go go to apps list and run “KernelSU” 2. Give termux su permissions 3. go back to termux and do “su” again (it should work) 4. run “ifconfig” (you should see “eth0” in the list) 6. run “ifconfig eth0 {the IP address you just found} netmask 255.255.255.255 up” (note: for some reason doing /32 after the address does not work) 7. run “ip route add 0.0.0.0/0 via {gateway address}” internet (but not DNS) should now be working

(Not sure how to do DNS, since /etc/resolv.conf seems to be missing)