(Solved) New UT on Pixel 3a user.

globetrotterdk · 17 Feb 2024, 08:11

(After complete uninstall and app data wipe with Waydroid Helper)
OK, I have gotten smart this time and run the commands through adb shell to see what is going on - much easier:

$ adb shell
phablet@ubuntu-phablet:~$ sudo waydroid init -s GAPPS
[sudo] password for phablet: 
[09:02:25] Downloading https://sourceforge.net/projects/waydroid/files/images/system/lineage/waydroid_arm64/lineage-18.1-20240217-GAPPS-waydroid_arm64-system.zip/download
[Downloading] 863.96 MB/864.2 MB    23383.79 kbps(approx.)[09:03:14] Validating system image
[09:03:15] Extracting to /var/lib/waydroid/images
[09:03:53] Downloading https://sourceforge.net/projects/waydroid/files/images/vendor/waydroid_arm64/lineage-16.0-20240217-HALIUM_9-waydroid_arm64-vendor.zip/download
[Downloading] 6.95 MB/7.09 MB    25762.95 kbps(approx.)[09:03:54] Validating vendor image
[09:03:54] Extracting to /var/lib/waydroid/images

$ sudo waydroid container start
ERROR: WayDroid container service is already running
phablet@ubuntu-phablet:~$ sudo waydroid shell
[09:05:41] WayDroid container is STOPPED
$ sudo waydroid container start
ERROR: WayDroid container service is already running

So is the container running or stopped? The system appears to be confused...

saveurlinux · 18 Feb 2024, 13:49

@globetrotterdk did you try reboot ?

globetrotterdk · 18 Feb 2024, 14:33

@saveurlinux Yes, a number of times. After the latest try, I get the following:

$ adb shell
phablet@ubuntu-phablet:~$ sudo waydroid session start
[sudo] password for phablet: 
[15:30:05] ERROR: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
[15:30:05] See also: <https://github.com/waydroid>
Run 'waydroid log' for details.

$ waydroid log
(003442) [09:03:55] Save config: /var/lib/waydroid/waydroid.cfg
(003442) [09:03:55] % lxc-info --version
4.0.12
(003442) [09:03:55] % mkdir -p /var/lib/waydroid/lxc/waydroid
(003442) [09:03:55] % sh -c cat "/usr/lib/waydroid/data/configs/config_base" "/usr/lib/waydroid/data/configs/config_3" "/usr/lib/waydroid/data/configs/config_4" > "/var/lib/waydroid/lxc/waydroid/config"
(003442) [09:03:55] % sed -i s/LXCARCH/aarch64/ /var/lib/waydroid/lxc/waydroid/config
(003442) [09:03:55] % cp -fpr /usr/lib/waydroid/data/configs/waydroid.seccomp /var/lib/waydroid/lxc/waydroid/waydroid.seccomp
(003442) [09:03:55] % aa-enabled --quiet
(003442) [09:03:55] % mv /var/lib/waydroid/config_nodes /var/lib/waydroid/lxc/waydroid
(001917) [09:03:56] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH
STOPPED
(001917) [09:03:56] % chmod 666 -R /dev/anbox-binder
(001917) [09:03:56] % chmod 666 -R /dev/anbox-vndbinder
(001917) [09:03:56] % chmod 666 -R /dev/anbox-hwbinder
(003498) [09:05:41] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH
STOPPED
(003498) [09:05:41] WayDroid container is STOPPED
(001917) [09:12:41] Hardware service is not even started
(001917) [09:12:41] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH
STOPPED
(001917) [09:12:41] % /usr/lib/waydroid/data/scripts/waydroid-net.sh stop
vnic is waydroid0
waydroid-net isn't running
(001917) [09:12:41] % systemctl is-enabled -q nfcd
(001917) [09:12:41] % systemctl start nfcd
Failed to start nfcd.service: Transaction for nfcd.service/start is destructive (mount-android-partitions.service has 'stop' job queued, but 'start' is included in transaction).
See system logs and 'systemctl status nfcd.service' for details.
(001917) [09:12:41] % pidof waydroid-sensord
(001272) [15:27:56] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH
STOPPED
(001272) [15:27:56] % lxc-info --version
4.0.12
(001272) [15:27:56] % mkdir -p /var/lib/waydroid/lxc/waydroid
(001272) [15:27:56] % sh -c cat "/usr/lib/waydroid/data/configs/config_base" "/usr/lib/waydroid/data/configs/config_3" "/usr/lib/waydroid/data/configs/config_4" > "/var/lib/waydroid/lxc/waydroid/config"
(001272) [15:27:56] % sed -i s/LXCARCH/aarch64/ /var/lib/waydroid/lxc/waydroid/config
(001272) [15:27:56] % cp -fpr /usr/lib/waydroid/data/configs/waydroid.seccomp /var/lib/waydroid/lxc/waydroid/waydroid.seccomp
(001272) [15:27:56] % aa-enabled --quiet
(001272) [15:27:56] % mv /var/lib/waydroid/config_nodes /var/lib/waydroid/lxc/waydroid
(001972) [15:27:57] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH
STOPPED
(001972) [15:27:57] % chmod 666 -R /dev/anbox-binder
(001972) [15:27:57] % chmod 666 -R /dev/anbox-vndbinder
(001972) [15:27:57] % chmod 666 -R /dev/anbox-hwbinder
(003528) [15:30:05] ERROR: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
(003528) [15:30:05] See also: <https://github.com/waydroid>
(003528) [15:30:05] Traceback (most recent call last):
  File "/usr/lib/waydroid/tools/__init__.py", line 70, in main
    actions.session_manager.start(args)
  File "/usr/lib/waydroid/tools/actions/session_manager.py", line 35, in start
    name = dbus.service.BusName("id.waydro.Session", dbus.SessionBus(), do_not_queue=True)
  File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 212, in __new__
    return Bus.__new__(cls, Bus.TYPE_SESSION, private=private,
  File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 102, in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 124, in __new__
    bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

(003537) [15:33:04] % tail -n 60 -F /var/lib/waydroid/waydroid.log
(003537) [15:33:04] *** output passed to waydroid stdout, not to this log ***

saveurlinux · 18 Feb 2024, 17:11

@globetrotterdk I have same phone as you and waydroid install throw WayDroid Helper. It works fine on my phone, except banking apps.
Trying to launch throw the command line

sudo waydroid session start

raise the same error as you,
but launching it throw the WayDroid Helper works

saveurlinux · 18 Feb 2024, 17:24

@saveurlinux I think, you should try to launch it with sudo but as:

waydroid session start

and in an other tab launch

waydroid show-full-ui

other command line are available look at

waydroid help

globetrotterdk · 18 Feb 2024, 20:17

@saveurlinux
1st. shell:

$ adb shell
phablet@ubuntu-phablet:~$ sudo waydroid session start
[sudo] password for phablet: 
[21:11:07] ERROR: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
[21:11:07] See also: <https://github.com/waydroid>
Run 'waydroid log' for details.

2nd. shell:

$ adb shell
phablet@ubuntu-phablet:~$ sudo waydroid show-full-ui
[sudo] password for phablet: 
[21:12:19] Starting waydroid session
[21:12:19] ERROR: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
[21:12:19] See also: <https://github.com/waydroid>
Run 'waydroid log' for details.

Looks to me like a DBus issue, but I will take a look at waydroid help tomorrow and see if I can get something out of that. At this point, not holding out much hope however, as my experience is that when you cut out the gui and just using the cli, there is a better chance of understanding what is going on. While the errors are fairly verbose, the result isn't ringing any bells.

saveurlinux · 18 Feb 2024, 21:14

@globetrotterdk have you tried without sudo ?

globetrotterdk · 18 Feb 2024, 22:15

@saveurlinux The Waydroid icon appears, but no active window, and when I try to swipe from the right, the system tells me that there are no apps running.

Here is the cli output from the same session:

$ adb shell
phablet@ubuntu-phablet:~$ waydroid session start
[23:10:10] WAYLAND_DISPLAY is not set, defaulting to "wayland-0"
[23:10:11] Failed to start Clipboard manager service, check logs
[gbinder] Service manager /dev/anbox-binder has appeared
[23:10:36] Android with user 0 is ready
Traceback (most recent call last):
  File "gbinder.pyx", line 499, in gbinder.LocalObject.callback
  File "/usr/lib/waydroid/tools/interfaces/IUserMonitor.py", line 33, in response_handler
    packageStateChanged(arg1, arg2, arg3)
  File "/usr/lib/waydroid/tools/services/user_manager.py", line 87, in packageStateChanged
    makeDesktopFile(appInfo)
  File "/usr/lib/waydroid/tools/services/user_manager.py", line 35, in makeDesktopFile
    for cat in appInfo["categories"]:
TypeError: 'NoneType' object is not subscriptable
Exception ignored in: 'gbinder.local_transact_callback'
Traceback (most recent call last):
  File "gbinder.pyx", line 499, in gbinder.LocalObject.callback
  File "/usr/lib/waydroid/tools/interfaces/IUserMonitor.py", line 33, in response_handler
    packageStateChanged(arg1, arg2, arg3)
  File "/usr/lib/waydroid/tools/services/user_manager.py", line 87, in packageStateChanged
    makeDesktopFile(appInfo)
  File "/usr/lib/waydroid/tools/services/user_manager.py", line 35, in makeDesktopFile
    for cat in appInfo["categories"]:
TypeError: 'NoneType' object is not subscriptable
^C
phablet@ubuntu-phablet:~$

saveurlinux · 18 Feb 2024, 22:28

@globetrotterdk maybe that's because you are doing it from adb and WAYLAND_DISPLAY is not available ? Try to do it from the phone terminal

When the command

waydroid session start

succeed , you can open a new tab into the terminal phone app and then do this next one:

waydroid show-full-ui

globetrotterdk · 19 Feb 2024, 06:57

@saveurlinux Unfortunately, no such luck. I get a few of the same lines and then the process refuses to go any further:

$ waydroid session start
[07:49:53] Failed to start Clipboard manager service, check logs
[gbinder] Service manager /dev/anbox-binder has appeared
[07:50:19] Android with user 0 is ready
^C

arubislander · 19 Feb 2024, 09:50

@globetrotterdk The last line says it is ready, maybe it doesn't go any further until you follow with what @saveurlinux suggests?

globetrotterdk · 19 Feb 2024, 10:59

@arubislander Cool. That works. I was able to go in and get the Waydroid instance certified (through the adb shell) by following the Waydroid instructions and getting the android id.

Unfortunately, after using Wayroid stop and rebooting the phone, the system freezes at the Google splash screen.

A restart is possible, and I am able to get into Waydroid again by using the app tray.

globetrotterdk · 19 Feb 2024, 19:54

Thanks to everyone for all of the help and feedback!