yes, sorry, I’m sleeping… 
Thanks!
Thank you all, especially @rinigus , to remind me of this being unsolved on my phone. I rarely need Android software, but I had similar problems with generating and attaching to a session as @jsingla and this always frustrated me. Using waydroid-runner as nemo or defaultuser is so much nicer!
Hello, I’m trying to get waydroid run on Xiaomi Redmi 5 Plus with 4.4.0.68 (32bit) but waydroid log gives me this
(006868) [11:08:15] UserMonitor service is not even started
(006868) [11:08:15] Clipboard service is not even started
(006868) [11:08:15] ERROR: [Errno 13] Permission denied: ‘/var/lib/waydroid/session.cfg’
(006868) [11:08:15] See also: https://github.com/waydroid
(006868) [11:08:15] Traceback (most recent call last):
File “/opt/waydroid/tools/init.py”, line 62, in main
actions.session_manager.stop(args)
File “/opt/waydroid/tools/actions/session_manager.py”, line 59, in stop
os.remove(config_path)
PermissionError: [Errno 13] Permission denied: ‘/var/lib/waydroid/session.cfg’
and waydroid-runner running from terminal as nemo
[D] unknown:0 - Using Wayland-EGL
library “libgui.so” wasn’t loaded and RTLD_NOLOAD prevented it
Wayland socket: …/…/display/wayland-1
[W] unknown:0 - Failed to query EGL extensions
[D] onCompleted:580 - Warning: specifying an object instance fo
r initialPage is sub-optimal - prefer to use a Component
[D] expression for onStatusChanged:110 - Status: -2 Android se
ssion started already. Stop that session and restart this appli
cation.
Unfortunately, my xz2c already has waydroid installed and I cannot test from “zero”. However, after uninstall and reinstall I managed to get into the same state where Waydroid doesn’t start. Hard to say why. I will update your issue at SFOS/Waydroid and let’s see if @piggz has any ideas.
2 Likes
Thanks rinigus,
One question, there is some way to install an old version?
Thanks!
You mean of the old Android image? Probably there is, but you have to look it up yourself. Some images are at WayDroid - Browse /images at SourceForge.net . Not sure what they really use these days
I was thinking on an old package of waydroid, not the image, but if you think the problem is the image, that should be easy, righ?
I would suspect the image. But it is my guess…
hello,
I tried to download an old image, 20210928, HALIUM (and also the vendor from the same date) to check. After reboot I’ve got this error:
(007875) [20:51:20] % umount -l /sys/fs/cgroup/schedtune
[waydroid-sensors-daemon] Got new plugin for pressuresensor with pid 7885 and session 21
[waydroid-sensors-daemon] Got plugin_string pressuresensor
[waydroid-sensors-daemon] Got plugin_interface local.PressureSensor
[waydroid-sensors-daemon] Got plugin_path /SensorManager/pressuresensor
umount: /sys/fs/cgroup/schedtune: no mount point specified.
(007875) [20:51:20] % chmod 777 -R /dev/ashmem
(007875) [20:51:20] % chmod 777 -R /sys/kernel/debug/sync/sw_sync
[waydroid-sensors-daemon] Got new plugin for proximitysensor with pid 7885 and session 22
[waydroid-sensors-daemon] Got plugin_string proximitysensor
[waydroid-sensors-daemon] Got plugin_interface local.ProximitySensor
[waydroid-sensors-daemon] Got plugin_path /SensorManager/proximitysensor
(007875) [20:51:20] % chmod 777 -R /dev/dri
[waydroid-sensors-daemon] Got new plugin for stepcountersensor with pid 7885 and session 23
[waydroid-sensors-daemon] Got plugin_string stepcountersensor
[waydroid-sensors-daemon] Got plugin_interface local.StepCounterSensor
[waydroid-sensors-daemon] Got plugin_path /SensorManager/stepcountersensor
(007875) [20:51:20] % chmod 777 -R /dev/ion
(007875) [20:51:20] % chmod 777 -R /dev/video
(007875) [20:51:20] % chmod 777 -R /dev/video2
(007875) [20:51:20] % chmod 777 -R /dev/video1
(007875) [20:51:20] % chmod 777 -R /dev/video33
[waydroid-sensors-daemon] Failed to create SensorfwTemperatureSensor: Could not create sensorfw backend
(007875) [20:51:20] % chmod 777 -R /dev/video32
(007875) [20:51:20] % chmod 777 -R /dev/video0
(007875) [20:51:20] % lxc-start -P /var/lib/waydroid/lxc -F -n waydroid -- /init
(007875) [20:51:20] New background process: pid=7939, output=background
lxc-start: waydroid: utils.c: lxc_can_use_pidfd: 1772 Kernel does not support pidfds
lxc-start: waydroid: utils.c: safe_mount: 1198 Not a directory - Failed to mount "/dev/video" onto "/usr/lib64/lxc/rootfs/dev/video"
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!
lxc-start: waydroid: conf.c: mount_entry: 2248 No such file or directory - Failed to mount "tmpfs" on "/usr/lib64/lxc/rootfs/tmp"
lxc-start: waydroid: conf.c: lxc_setup: 4104 Failed to setup mount entries
lxc-start: waydroid: start.c: do_start: 1291 Failed to setup container "waydroid"
lxc-start: waydroid: sync.c: sync_wait: 36 An error occurred in another process (expected sequence number 3)
lxc-start: waydroid: start.c: __lxc_start: 2053 Failed to spawn container "waydroid"
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"
lxc-start: waydroid: tools/lxc_start.c: main: 308 The container failed to start
lxc-start: waydroid: tools/lxc_start.c: main: 314 Additional information can be obtained by setting the --logfile and --logpriority options
(007875) [20:51:20] waiting 10 seconds for container to start...
(007875) [20:51:21] waiting 9 seconds for container to start...
(007875) [20:51:22] waiting 8 seconds for container to start...
(007875) [20:51:23] waiting 7 seconds for container to start...
(007875) [20:51:24] waiting 6 seconds for container to start...
(007875) [20:51:25] waiting 5 seconds for container to start...
(007875) [20:51:26] waiting 4 seconds for container to start...
(007875) [20:51:27] waiting 3 seconds for container to start...
(007875) [20:51:28] waiting 2 seconds for container to start...
(007875) [20:51:29] waiting 1 seconds for container to start...
(007875) [20:51:30] ERROR: container failed to start
(007875) [20:51:30] See also: <https://github.com/waydroid>
(007875) [20:51:30] Traceback (most recent call last):
File "/opt/waydroid/tools/__init__.py", line 69, in main
actions.container_manager.start(args)
File "/opt/waydroid/tools/actions/container_manager.py", line 163, in start
raise OSError("container failed to start")
OSError: container failed to start
(008289) [20:51:38] % tail -n 60 -F /var/lib/waydroid/waydroid.log
(008289) [20:51:38] *** output passed to waydroid stdout, not to this log ***
Thanks!
After some tinkering and looking at error messages from waydroid, I suspect my gemini is lacking ashmem and binder from the kernel.
I don’t have any experience with compiling kernel modules (I am not even sure if it is a possible alternative to get some kind of patch?)
does anyone know of a good beginner friendly explanation, to get something this moving in the right direction ?
thanks!
2 Likes
in github repo, they commented they are using some old version of binder, I think.
1 Like
Since Waydroid’s last online update (I downloaded and installed right now), Waydroid doesn’t start any more. It hangs on ‘Starting Android session’ and shows eternally spinning circle. Did a few reboots and tried again after, but still hanging. Volla/ GS290, SFOS 4.4.0.72. What can I do? Any ideas?
I installed it recently for first time, did the init stuff, but never get past the spinning spinner of spininess either.
Just a guess: dnsmasq
1 Like
Thank you all for helping, but I reflashed the Volla with Ubuntu touch and there will never again come SFOS onto the Volla. I really have to quit this for my emotional stability and this time it is consequently.