I’m trying to run waydroid on my Pinephone Pro. I installed waydroid and waydroid-image, enabled the container and ran the setup as root, then rebooted. After boot, I started the session in a terminal, which told me: [gbinder] Service manager /dev/binder has appeared
Since then I’m trying to see which apps are installed using: $ waydroid app list
But all I see is: [22:21:48] Failed to get service waydroidplatform, trying again...
One line each second.
When I click the waydroid icon in the starter, I get a splash screen that just sits there indefinitely. Meanwhile, I can ping the container and two processes called bootanimation and surfaceflinger are constantly taking ~20% CPU, so I’m guessing it’s doing something, but I don’t get to use it.
Can someone tell me what I’m missing here, or how I could find out?
Yeah, Waydroid is kinda messy :S
When i tried it out, i had this issue many times, using these commands usually solved it to me, but sometimes doesn’t. When it didn’t, i simply restarted my whole system and tried to start it again with:
When look at dmesg while the "Failed to get service … " lines fill my screen, I saw this, repeated just as often:
[ 9585.182805] init: Received control message 'interface_start' for 'android.hardware.sensors@1.0::ISensors/default' from pid: 15 (/system/bin/hwservicemanager)
[ 9585.182884] init: Could not find 'android.hardware.sensors@1.0::ISensors/default' for ctl.interface_start
What sensors is it missing, and is there a way to solve this?
The problem was caused by two ^@ characters in /var/lib/waydroid/waydroid_base.prop, so that the rest of the file /var/lib/waydroid/waydroid_base.prop, generated after starting the session, could not be generated entirely.