Waydroid error: not using Wayland. But I am!

[quixote]

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 . I'll try getting waydroid running again when I have a minute and report back.