The changes outside of /rw (/home/user and /usr/local) are not persistent in the AppVM. If you need to install something system-wide then do this in template.
Or you can use bind-dirs:
Ć waydroid-firewall.service
Loaded: loaded (/etc/systemd/system/waydroid-firewall.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Mon 2024-03-18 10:24:45 CET; 46s ago
Process: 476 ExecStart=/usr/sbin/iptables -I INPUT -i waydroid0 -p tcp -m multiport --dports 53,67 -j ACCEPT (code=exited, status=0/SUCCESS)
Process: 551 ExecStart=/usr/sbin/iptables -I INPUT -i waydroid0 -p udp -m multiport --dports 53,67 -j ACCEPT (code=exited, status=0/SUCCESS)
Process: 552 ExecStart=/usr/sbin/iptables -I FORWARD 2 -o eth0 -i waydroid0 -j ACCEPT (code=exited, status=1/FAILURE)
Main PID: 552 (code=exited, status=1/FAILURE)
CPU: 16ms
Mar 18 10:24:44 android systemd[1]: Starting waydroid-firewall.serviceā¦
Mar 18 10:24:45 android iptables[552]: iptables: Index of insertion too big.
Mar 18 10:24:45 android systemd[1]: waydroid-firewall.service: Main process exited, code=exited, status=1/FAILURE
Mar 18 10:24:45 android systemd[1]: waydroid-firewall.service: Failed with result āexit-codeā.
Mar 18 10:24:45 android systemd[1]: Failed to start waydroid-firewall.service.
Mar 18 10:25:32 android systemd[1]: /etc/systemd/system/waydroid-firewall.service:1: Unknown section āUNITā. Ignoring.
~
Did you change the default Qubes OS iptables rules?
Whatās the output of this command?
iptables -nvL
Seems like the iptables FORWARD chain is empty:
Process: 552 ExecStart=/usr/sbin/iptables -I FORWARD 2 -o eth0 -i waydroid0 -j ACCEPT (code=exited, status=1/FAILURE)
Mar 18 10:24:45 android iptables[552]: iptables: Index of insertion too big.
Can anyone tell me why I have to set up the firewall and if this effects any other qubes. Because today I have seen that there are other network issues which may be caused by the waydroid experiments
Thatās because itās required for waydroid to work:
No, it shouldnāt have any effect on other qubes.
I did this the other day, 0 issues when following Appās instructions.
It works almost flawlessly.
Only issue is with GAPPS not working, but thatās to do with the image and such, not these instructions.
There is a separate image that has GAPPS:
Or are GAPPS not working in the GAPPS Waydroid image?
Iāve tested the GAPPS Waydroid image some time ago and GAPPS worked there.
I have 2 virtuals, one that uses GAPPS, and one that is VANILLA.
I really needed the GAPPS one to work as I was relying on that to get some things done.
The older versions may work, but the latest one isnāt.
On Q4.1 at the moment I canāt even get Android to install properly, vanilla or not, it just wonāt boot afterwards. Thatās why I was trying WayDroid since I found your guide which works absolutely perfectly.
The issue with the GAPPS WayDroid version is the fact that you canāt use Google Play Store, Google Applications, Google Services, and canāt log in to Google with an Account either.
It keeps saying that the hardware wonāt support the Play Protect and stuff. And that just causes everything every few seconds after installation to just go crazy to the point where I canāt even use it.
I still have my Android 2, 4.1, 8 & 9 that work though. But I want Lineage.
Not even BlissOS will install correctly and then boot. Every time it just says there is no boot device.
Using your methodology, I could probably insert Bliss or similar instead of their image, that wouldnāt be hard now I have it all installed properly.
If you have any thoughts, would love to discuss things about it. If itās WayDroid, here, if not, then maybe in DM.
You have to self certify the Waydroid:
Related issue:
So this is an issue with Waydroid?
Never had to register a device that was running LineageOS beforeā¦
Guess this is just an issue with WayDroidā¦
I donāt know how Play Protect works, maybe itās checking the hardware device fingerprint or/and the ROM to be supported.
I have used LineageOS on identical hardware, same PC, same version of Qubes, everythingā¦ With GApps and all. Never had the issue, never had to register my hardware with a marketing company.
I donāt know how it works so I can only assume that LinageOS is certifying their ROM builds with Google but the Waydroid is not. The Waydroid is based on LineageOS with some patches but itās not using the LineageOS ROM builds and build the images by themself and donāt certify them with Google.
Waydroid uses LineageOS. Their ROMs are LineageOS.
There is nothing to certifyā¦
They have not registered my hardware with googleā¦ Nor has Waydroids copy. So there should be no issueā¦ as I sayā¦ SHOULDā¦
So I donāt get itā¦
But since this is just running Android under a virtual, it would be easier for me to just run Lineage under XEN instead of XEN and a virtual.
If they fix their build then it may be worth coming back for a look.
Well, got LineageOS running and no issue.So there must be something in WayDroid that has an issue with identical hardware to what Iām using for LineageOS. Meaning that there should really be no issueā¦ Or is it the fact that itās running under Sway?
Itās better to ask this from Waydroid devs in their matrix/telegram channel or in the linked github issue.
I donāt think the Sway is the problem here.
Iāll run some tests. Iāll load the same image into sway and see what happens. Just have to wait for a new drive to arrive. Need an m.2 as Iām currently running dual SATA, but I need more speed as everything running so damn slow since the update issue with qubes that has not been resolved. So I have to install 4.1 again.
Hoping by the end of the week to check all of the details and will post the results here.
Iāve updated the guide with this info:
Add Waydroid App menu shortcut to the newly created qubes by default
To add the Waydroid App menu shortcut to the newly created qubes you need to set default-menu-items feature for Waydroid template.
Open dom0 terminal and run this command to set the default App menu items for qubes based on this template:
qvm-features d12m-waydroid default-menu-items "Waydroid-Sway.desktop debian-xterm.desktop"
Hey, Iām running Qubes r4.2.1 I successfully got everything up and running. However, Waydroid does not have internet. I verified that I ran the commands for 4.2.1 and that the changes took. The Qube itself has internet and completed a ping to google.com.
Whatās the output of this command in Waydroid qube (run as root)?
nft list ruleset
How did you check that you donāt have internet there?