PINE64
Waydroid error: not using Wayland. But I am! - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: PinePhone (https://forum.pine64.org/forumdisplay.php?fid=120)
+--- Forum: PinePhone Software (https://forum.pine64.org/forumdisplay.php?fid=121)
+---- Forum: Mobian on PinePhone (https://forum.pine64.org/forumdisplay.php?fid=139)
+---- Thread: Waydroid error: not using Wayland. But I am! (/showthread.php?tid=15341)

Waydroid error: not using Wayland. But I am! - quixote - 11-15-2021

I'm stuck. I hope someone here can come up with a workaround! I'm using bookworm and Phosh, all up to date, on a Braveheart 1.1 phone. I installed by following the step-by-step on the Waydroid Site (https://waydro.id/ at bottom of page). There are no errors until I get to the second steps under "Running Waydroid."

Code:
sudo container waydroid start
errors:

Code:
[16:06:43] NOTE: The failed command's output is above the ^^^ line in the log file: /var/lib/waydroid/waydroid.log
[16:06:43] ERROR: Command failed: % mount /var/lib/waydroid/images/system.img /var/lib/waydroid/rootfs
[16:06:43] See also: <https://github.com/waydroid>
Run 'waydroid log' for details.


and
Code:
waydroid session start
tells me the XDG session is not Wayland. But both
Code:
$ echo $XDG_SESSION_TYPE
and
Code:
$ loginctl show-session 1 -p Type
returns "wayland" (I did check to make sure I had the right session)

Anyone have any idea what's going on? Or, even better, how to make it go away? Huh

(also posted this just now to Waydroid issues tab on github)

RE: Waydroid error: not using Wayland. But I am! - wibble - 11-19-2021

You need to fix the error starting the container before you can run the session. Check the log file as it suggests, as it might give a bit more detail as to what went wrong when trying to mount the android system.img - alternatively you can try mounting it manually.

RE: Waydroid error: not using Wayland. But I am! - quixote - 11-19-2021

Hmm. You mean given that all else has failed, read the instructions? Big Grin  Yes, you're right. I'll give it a closer look.

If I want to start it manually, what's the command?

sudo mount -t [what is the fstype??]  [what's the waydroid device name?] [where would it expect to be mounted?]

Or is there some other mount command for virtual machines?

Thanks!

RE: Waydroid error: not using Wayland. But I am! - wibble - 11-22-2021

I've not tried Waydroid yet so can't give too many specifics, but the error you quoted included the mount command you're asking about. It says it tried to mount /var/lib/waydroid/images/system.img at /var/lib/waydroid/rootfs. Specifying the fstype may not be strictly necessary - for files it can usually be autodetected. First check that /var/lib/waydroid/images/system.img actually exists, and is a sensible size for a filesystem image. Next run 'file -L /var/lib/waydroid/images/system.img' which should show you the fstype - the '-L' is in case it's a symlink. If the system.img exists and detects as a filesystem (not still zipped, corrupt etc.) and the mount point exists you can try mounting it manually and check for errors.

RE: Waydroid error: not using Wayland. But I am! - quixote - 11-23-2021

Yes system.img is there, 1.4GB. the "file -L" command says it's ext2, so that's useful.

I checked the log on a fresh try and this was the result for the current attempt:
Code:
(000453) [21:05:36] % mkdir -p /dev/binderfs
(000453) [21:05:36] % mount -t binder binder /dev/binderfs
(000453) [21:05:36] % ln -s /dev/binderfs/anbox-hwbinder /dev/binderfs/anbox-vndbinder /dev/binderfs/anbox-binder /dev/binderfs/vndbinder /dev/binderfs/hwbinder /dev/binderfs/binder /dev/binderfs/binder-control /dev/
(000453) [21:05:36] % chmod 666 -R /dev/binder
(000453) [21:05:36] % chmod 666 -R /dev/vndbinder
(000453) [21:05:36] % chmod 666 -R /dev/hwbinder
(000453) [21:05:36] Container manager is waiting for session to load

No errors that I can see. (The ones that made my eyes glaze over, such as "UserMonitor service is not even started Clipboard service is not even started", were from earlier attempts with a previous install and I didn't realize it till I looked more carefully.)

It looks like the session is not loading because of some kind of wayland issue? Like the error msg says. One thing I noticed when I updated this morning was that "xwayland" was among the updates. Who knows? All my problems may be solved Big Grin . I'll try getting waydroid running again when I have a minute and report back.

RE: Waydroid error: not using Wayland. But I am! - quixote - 12-03-2021

I seem to be getting different error messages. Progress? All the messages from my most recent attempt:

Code:
(004592) [18:20:38] Container manager is waiting for session to load
(004629) [18:21:37] Save session config: /var/lib/waydroid/session.cfg
(004629) [18:21:37] UserMonitor service is not even started
(004629) [18:21:37] Clipboard service is not even started
(000544) [18:21:38] % /usr/lib/waydroid/data/scripts/waydroid-net.sh start
(004592) [18:21:38] % /usr/lib/waydroid/data/scripts/waydroid-net.sh start
RTNETLINK answers: File exists
Failed to setup waydroid-net.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.

dnsmasq: failed to create listening socket for 192.168.250.1: Cannot assign requested address
Failed to setup waydroid-net.
Failed to setup waydroid-net.
(004592) [18:21:38] % mount /var/lib/waydroid/images/system.img /var/lib/waydroid/rootfs
(000544) [18:21:38] % mount /var/lib/waydroid/images/system.img /var/lib/waydroid/rootfs
(000544) [18:21:38] % mount -o remount,ro /var/lib/waydroid/images/system.img /var/lib/waydroid/rootfs
(004592) [18:21:38] % mount -o remount,ro /var/lib/waydroid/images/system.img /var/lib/waydroid/rootfs
(000544) [18:21:38] % mount /var/lib/waydroid/images/vendor.img /var/lib/waydroid/rootfs/vendor
(004592) [18:21:39] % mount /var/lib/waydroid/images/vendor.img /var/lib/waydroid/rootfs/vendor
mount: /var/lib/waydroid/rootfs/vendor: /dev/loop2 already mounted or mount point busy.
(000544) [18:21:39] % mount -o remount,ro /var/lib/waydroid/images/vendor.img /var/lib/waydroid/rootfs/vendor
(004592) [18:21:39] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(004592) [18:21:39] NOTE: The failed command's output is above the ^^^ line in the log file: /var/lib/waydroid/waydroid.log
(004592) [18:21:39] ERROR: Command failed: % mount /var/lib/waydroid/images/vendor.img /var/lib/waydroid/rootfs/vendor
So, if I understand it right, it didn't mount successfully. But it seems like it also had all sorts of other issues, like being unable to set up its network.

Not complaining about wayland anymore, but now what? Huh

RE: Waydroid error: not using Wayland. But I am! - wibble - 12-07-2021

Perhaps try asking on their telegram or matrix channels?

RE: Waydroid error: not using Wayland. But I am! - jsch - 01-09-2022

I was able to have waydroid running, had challenge with the network as well.
Not sure if this make as difference, but installed the software from branch bookworm (using upsream repo), besides that everything as described on https://wiki.mobian-project.org/doku.php?id=waydroid
Since I have nftables installed, I had to tweak https://wiki.mobian-project.org/doku.php?id=waydroid (see https://github.com/waydroid/waydroid/issues/105#issuecomment-934012156) as well as the nft script (see https://github.com/waydroid/waydroid/issues/105#issuecomment-950577505).
Now I'm struggling with missing support of the cameras.