If you run echo $XDG_SESSION_TYPE and echo $XDG_SESSION_DESKTOP in the cmdline, what is the output?
Same error after today waydroid update
If you could do this, I maybe can help you working around this issue.
After running in terminal devel-su waydroid upgrade
It is working again
Thanks, but anothe problem appeared - it outputs “Run waydroid log for details” even if running waydroid log, lol.
Hey,
I am trying to get Waydroid working on Volla 22 (latest SFOS) and I am stuck where other are stuck to.
(003653) [16:46:20] % mount -o bind /vendor/lib/egl /var/lib/waydroid/rootfs/vendor/lib/egl
(003653) [16:46:20] % mount -o bind /vendor/lib64/egl /var/lib/waydroid/rootfs/vendor/lib64/egl
(003653) [16:46:20] % mount -o bind /vendor/odm /var/lib/waydroid/rootfs/odm_extra
(003653) [16:46:20] % mount -o bind /var/lib/waydroid/waydroid.prop /var/lib/waydroid/rootfs/vendor/waydroid.prop
(003653) [16:46:20] Save config: /var/lib/waydroid/waydroid.cfg
(003653) [16:46:20] % mount -o bind /home/defaultuser/.local/share/waydroid/data /var/lib/waydroid/data
(003653) [16:46:20] % chmod 777 -R /dev/ashmem
(003653) [16:46:20] % chmod 777 -R /dev/MTK_SMI
(003653) [16:46:20] % chmod 777 -R /dev/mdp_sync
(003653) [16:46:20] % chmod 777 -R /dev/mtk_cmdq
(003653) [16:46:20] % chmod 777 -R /dev/graphics
(003653) [16:46:20] % chmod 777 -R /dev/ion
(003653) [16:46:20] % chmod 777 -R /dev/fb0
(003653) [16:46:20] % chmod 777 -R /dev/video1
(003653) [16:46:20] % chmod 777 -R /dev/video0
(003653) [16:46:20] % lxc-start -P /var/lib/waydroid/lxc -F -n waydroid – /init
(003653) [16:46:20] New background process: pid=7226, output=background
lxc-start: waydroid: utils.c: lxc_can_use_pidfd: 1772 Kernel does not support pidfds
lxc-start: waydroid: utils.c: open_without_symlink: 1062 Too many levels of symbolic links - vibrator in /usr/lib64/lxc/rootfs/sys/class/leds/vibrator was a symbolic link!
(003653) [16:46:20] Save session config: /var/lib/waydroid/session.cfg
(003653) [16:46:21] Failed to add service waydroidhardware: -2147483647
(003653) [16:46:21] Failed to add service waydroidhardware: -2147483647
(007138) [16:46:21] Failed to start Clipboard manager service, check logs
(007454) [16:46:22] Failed to get service waydroidplatform, trying again…
(007454) [16:46:23] Failed to get service waydroidplatform, trying again…
(007454) [16:46:24] Failed to get service waydroidplatform, trying again…
(007454) [16:46:25] Failed to get service waydroidplatform, trying again…
(007454) [16:46:26] Failed to get service waydroidplatform, trying again…
(007454) [16:46:27] Failed to get service waydroidplatform, trying again…
(007454) [16:46:28] Failed to get service waydroidplatform, trying again…
(007585) [16:46:29] UserMonitor service is not even started
(007585) [16:46:29] Clipboard service is not even started
(003653) [16:46:29] session manager stopped, stopping container and waiting…
(003653) [16:46:29] % lxc-stop -P /var/lib/waydroid/lxc -n waydroid -k
(007454) [16:46:29] Failed to get service waydroidplatform, trying again…
lxc-start: waydroid: conf.c: run_buffer: 323 Script exited with status 126
lxc-start: waydroid: start.c: lxc_end: 996 Failed to run lxc.hook.post-stop for container “waydroid”
(003653) [16:46:30] % /opt/waydroid/data/scripts/waydroid-net.sh stop
vnic is waydroid0
(003653) [16:46:30] % pidof waydroid-sensord
7174
(003653) [16:46:30] % kill -9 7174
(003653) [16:46:30] % umount /home/waydroid/rootfs/vendor/waydroid.prop
(003653) [16:46:30] % umount /home/waydroid/rootfs/vendor/lib64/egl
(003653) [16:46:30] % umount /home/waydroid/rootfs/vendor/lib/egl
(003653) [16:46:30] % umount /home/waydroid/rootfs/vendor
(003653) [16:46:30] % umount /home/waydroid/rootfs/odm_extra
(003653) [16:46:30] % umount /home/waydroid/rootfs
(003653) [16:46:30] % umount /home/waydroid/data
(003653) [16:46:30] % chmod 666 -R /dev/anbox-binder
(003653) [16:46:30] % chmod 666 -R /dev/anbox-vndbinder
(003653) [16:46:30] % chmod 666 -R /dev/anbox-hwbinder
(003653) [16:46:30] Container manager is waiting for session to load
(007138) [16:46:30] UserMonitor service is not even started
(007138) [16:46:30] Clipboard service is not even started
(007454) [16:46:30] Failed to get service waydroidplatform, trying again…
(007454) [16:46:31] Failed to get service waydroidplatform, trying again…
(007454) [16:46:32] Failed to get service waydroidplatform, trying again…
(007676) [16:47:38] % tail -n 60 -F /var/lib/waydroid/waydroid.log
(007676) [16:47:38] *** output passed to waydroid stdout, not to this log ***
The variables are empty:
[defaultuser@Phone22 ~]$ echo $XDG_SESSION_TYPE
[defaultuser@Phone22 ~]$ echo $XDG_SESSION_DESKTOP
Maybe someone has a clever hint?
That did the trick:
The /etc/gbinder.d/anbox-hybris.conf file was incorrect, more things had to be changed.
Did anybody answer this question? I tried to install waydroid on my XA2 Ultra along with App support, but it doesn’t start but gives Error code 2, whatever that means.
Should I expect it to work or are there obvious reasons that stop this show?
Have a look here:
but alongside App Support I have no idea.
I have tried with a certain patience, insistence and kind answers and help from members but probably I was missing skills to make WD work on my XA2 (earlier posts in this thread).
Problem is that probably few people have tried, as App Support is available on the XA2.
I just tried on freshly-flashed XA2 with Sailfish OS 4.5.0.21.
I did everything what I do to make Waydroid working on F(x)tec Pro1 (Sailfish 4.5.0.19). But it doesn’t work in XA2 case.
On Pro1 I install Waydroid, Settings, Sensors and Gbinder Hybris. I change aidl2 to aidl3 in config, waydroid init, enable container service, disable dnsmasq, enable starting session at boot and run Waydroid. Works on Pro1. Doesn’t work on XA2.
Journalctl / systemctl status doesn’t show any errors in terms of container service. So I guess problem is in session?
I will keep trying.
This may rely to old hardware, SFOS on XA2 runs in 32 bit mode. I guess it’s possible that Waydroid only runs on 64 bit systems.
Waydroid used to work for me in 32bit (Xperia X) with vibration sensor disabled but now it doesn’t work anymore.
Wait you ran Waydroid on Xperia X?
I’m thinking about switching to a Volla (the new x23 precisely), giving all the positive feedback here in the forum. However, I’m unsure about replacing the Android support with waydroid regarding usability. I see that you can run waydroid in the background (as Android support does) to speed up the starting time of apps. As I’m mainly use communication apps, this would be my use case. I presume that with this setting, there is little difference to the Android support, right?
One thing I’m wondering is the app permission thing. Does waydroid offer the possibility to control them (e.g. giving one app access to the contacts of SFOS while block another one / give it an empty contact list)? How about network access, can I restrict internet access for an app?
Does somebody know and can answer my questions? Thanks already.
Well, Waydroid <-> Sailfish integration is very small. Internet control? I think it’d be on Android side, as Waydroid is just full Lineage 18.1 running on Sailfish OS. There is a script adding Magisk = root access, but I’m not sure if it works on Sailfish’s Waydroid (it’s designed for normal Waydroid on Linux). A small integration with Sailfish can be achieved using Sailfish Connect and KDE Connect, but Android notifications won’t show on Sailfish (yet).
You are right, it is not possible at all. It was X10II.
It works but the mount point is different i.e.:
mount --bind /home/defaultuser/Downloads /home/waydroid/data/media/0/Download
2 Likes
You just have to imagine it to be like you have the entire android OS (as Lineage in this instance) as an app. When you open the app, you see the boot image and then Lineage starts. You download and control apps exactly like you do on Android (within the app). You can import contacts, and likely control what apps have what permissions.
To get notifications you need to leave the app (Waydroid) running in the background so you can hear the notifications come through. They don’t show up in Sailfish
I’m unsure about root access, I haven’t delved too deep into it.
One thing to note is that you likely can’t have many apps operating within Waydroid without slowing the phone down. I run outlook and chrome in there for work, but not at the same time. I really like how you can run apps in Waydroid in real time and monitor then from the Sailfish running/minimised apps screen.
I used to use an Android browser when running Alien Dalvik on an Xperia 10 as it operated better than the stock browser, but now I find myself only using either the stock browser or Angelfish.
I’m now using an XZ2 and am looking to get rid of the supported Xperia 10 device with how well the XZ2 runs Sailfish.
All the best with your decision.
3 Likes
This is what worked for me, thanks to @Seven.of.nine funnily enough:
ln -s /home/waydroid/data/media/0/ /home/defaultuser/Android-Data
1 Like