Waydroid not working correctly

zany130 · 17 July 2023 00:39

So I am having trouble setting up waydroid with magisk. I followed this guide Ultimate Guide to install Waydroid in any Arch-based distro(especially Garuda)
If I use zen, tkg or any kernel that is not linux-cachyos
I get this when trying to run waydroid

[20:29:51] Starting waydroid session
[gbinder] WARNING: Service manager /dev/binder has died

and this is the status of the systemd service

systemctl status waydroid-container.service
● waydroid-container.service - Waydroid Container
     Loaded: loaded (/usr/lib/systemd/system/waydroid-container.service; enabled; preset: disabled)
     Active: active (running) since Sun 2023-07-16 20:29:02 EDT; 5min ago
   Main PID: 769 (python3)
      Tasks: 6 (limit: 38370)
     Memory: 21.7M
        CPU: 204ms
     CGroup: /system.slice/waydroid-container.service
             ├─  769 python3 /usr/bin/waydroid -w container start
             └─22318 dnsmasq --conf-file=/dev/null -u dnsmasq --strict-order --bind-interfaces --pid-file=/run/waydroid-lxc/dnsmasq.pid --listen-address 192.168.240.1 --dhcp-range 192.168.240.2,192.168.240.254 -->

Jul 16 20:29:02 Garuda-Linux systemd[1]: Started Waydroid Container.
Jul 16 20:29:51 Garuda-Linux dnsmasq[22318]: started, version 2.89 cachesize 150
Jul 16 20:29:51 Garuda-Linux dnsmasq[22318]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset nftset auth cryptohash DNSSEC loop-detect inotify dumpfile
Jul 16 20:29:51 Garuda-Linux dnsmasq-dhcp[22318]: DHCP, IP range 192.168.240.2 -- 192.168.240.254, lease time 1h
Jul 16 20:29:51 Garuda-Linux dnsmasq-dhcp[22318]: DHCP, sockets bound exclusively to interface waydroid0
Jul 16 20:29:51 Garuda-Linux dnsmasq[22318]: reading /etc/resolv.conf
Jul 16 20:29:51 Garuda-Linux dnsmasq[22318]: using nameserver 192.168.2.1#53
Jul 16 20:29:51 Garuda-Linux dnsmasq[22318]: using nameserver 2600:1700:5230:84d0::41#53
Jul 16 20:29:51 Garuda-Linux dnsmasq[22318]: read /etc/hosts - 12 names
Jul 16 20:29:51 Garuda-Linux waydroid[769]: [20:29:51] waiting 10 seconds for container to start...

on catchy I can run waydroid fine, but I can't install Magisk due to this issue
which says to try a different kernel, but no other kernel allows me to boot way droid (including linux-xanmod-anbox)

garuda-inxi
System:
  Kernel: 6.4.3-273-tkg-bmq arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
    parameters: intel_pstate=passive split_lock_detect=off amd_pstate=active
    BOOT_IMAGE=/@/boot/vmlinuz-linux-linux-tkg-bmq-generic_v3
    root=UUID=53e270ad-dfd5-4874-a125-69d21ada6b8d rw rootflags=subvol=@
    rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
    sysrq_always_enabled=1 amdgpu.ppfeaturemask=0xffffffff nowatchdog
    nmi_watchdog=0 psi=1 drm.edid_firmware=HDMI-A-1:edid/LG-C2.bin
    initrd=@\boot\initramfs-linux-tkg-bmq-generic_v3.img
  Desktop: KDE Plasma v: 5.27.6 tk: Qt v: 5.15.10 wm: kwin_wayland vt: 1
    dm: N/A Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: ASRock model: X470 Taichi serial: <superuser required>
    UEFI: American Megatrends v: P5.10 date: 10/20/2022
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master 3
    serial: <filter> charge: 100% (should be ignored) rechargeable: yes
    status: discharging
CPU:
  Info: model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 2 microcode: 0xA20120A
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
    L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 3939 high: 4573 min/max: 550/4651 scaling:
    driver: amd-pstate-epp governor: performance cores: 1: 3620 2: 4255 3: 4063
    4: 4525 5: 3609 6: 3618 7: 3618 8: 4004 9: 4164 10: 4573 11: 3639 12: 3591
    bogomips: 88896
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
    vendor: Gigabyte driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
    process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
    lanes: 16 ports: active: DP-1,HDMI-A-1,HDMI-A-2 empty: DP-2
    bus-ID: 10:00.0 chip-ID: 1002:73df class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.1.2
    compositor: kwin_wayland driver: N/A d-rect: 5120x2592 display-ID: 0
  Monitor-1: DP-1 pos: bottom-r res: 2048x864 size: N/A modes: N/A
  Monitor-2: HDMI-A-1 pos: primary,top-left res: 1536x864 size: N/A
    modes: N/A
  Monitor-3: HDMI-A-2 pos: middle-c res: 1536x864 size: N/A modes: N/A
  API: OpenGL v: 4.6 Mesa 23.1.3 renderer: AMD Radeon RX 6700 XT (navi22
    LLVM 15.0.7 DRM 3.52 6.4.3-273-tkg-bmq) direct-render: Yes
Audio:
  Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 10:00.1 chip-ID: 1002:ab28
    class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASRock
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 12:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Sony INZONE H9 / H7
    driver: cdc_acm,hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-6:3 chip-ID: 054c:0e53
    class-ID: 0a00
  API: ALSA v: k6.4.3-273-tkg-bmq status: kernel-api with: aoss
    type: oss-emulator tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 0.3.74 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 08:00.0
    chip-ID: 8086:24fb class-ID: 0280
  IF: wlp8s0 state: down mac: <filter>
  Device-2: Intel I211 Gigabit Network vendor: ASRock driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 0a:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp10s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
  IF-ID-2: waydroid0 state: down mac: <filter>
Bluetooth:
  Device-1: Edimax Bluetooth Adapter driver: btusb v: 0.8 type: USB rev: 1.1
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 5-2:2 chip-ID: 7392:c611
    class-ID: e001 serial: <filter>
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
  Local Storage: total: 2.96 TiB used: 4.11 TiB (139.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Samsung model: SSD 980 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 3B4QFXO7 temp: 40.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 2B2QEXE7 temp: 37.9 C
    scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000DX002-2DV164
    size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: CC41 scheme: GPT
Partition:
  ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 767.37 GiB (82.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:5
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 27.8 MiB (9.3%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:4
  ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 767.37 GiB (82.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:5
  ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 767.37 GiB (82.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:5
  ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 767.37 GiB (82.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:5
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 50 (default 100)
  ID-1: swap-1 type: zram size: 31.26 GiB used: 512 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 80.2 C mobo: 38.0 C gpu: amdgpu temp: 52.0 C
    mem: 54.0 C
  Fan Speeds (RPM): cpu: 0 fan-2: 2954 fan-3: 0 fan-4: 0 fan-5: 0
    gpu: amdgpu fan: 0
  Power: 12v: N/A 5v: N/A 3.3v: 3.14 vbat: 3.28 gpu: amdgpu watts: 27.00
Info:
  Processes: 640 Uptime: 2m wakeups: 7 Memory: total: 32 GiB
  available: 31.26 GiB used: 13.08 GiB (41.9%) Init: systemd v: 253
  default: graphical tool: systemctl Compilers: gcc: 13.1.1 clang: 15.0.7
  Packages: 2629 pm: pacman pkgs: 2600 libs: 589 tools: octopi,paru
  pm: appimage pkgs: 0 pm: flatpak pkgs: 29 Shell: fish v: 3.6.1 default: Bash
  v: 5.1.16 running-in: alacritty inxi: 3.3.28
Garuda (2.6.16-1):
  System install date:     2023-07-10
  Last full system update: 2023-07-16
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:            httpd.service systemd-networkd-wait-online.service

zany130 · 17 July 2023 02:54

Something else that i noticed isn't working (when waydroid is starting e.g on cachy linux kernel) are games like kingdom hearts dark road

trying to install the apk just fails ( copied the apk into the waydroid contanior cuz runing waydroid app install $path_to_apk just does nothing)

Austin · 17 July 2023 03:28

You would have got your answer if you had read this ,

Just yesterday only, I posted in the comments:

zany130 · 17 July 2023 21:22

I did do that

cat /etc/modules-load.d/binder.conf
File: /etc/modules-load.d/binder.conf
binder_linux

second to last option I am passing right before my custom edid

cat /boot/refind_linux.conf
File: /boot/refind_linux.conf
"Boot with standard options"  "amd_pstate=active BOOT_IMAGE=/@/boot/vmlinuz-linux-%v root=UUID=53e270ad-df
d5-4874-a125-69d21ada6b8d rw rootflags=subvol=@ rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel
=3 sysrq_always_enabled=1 amdgpu.ppfeaturemask=0xffffffff nowatchdog nmi_watchdog=0 psi=1 drm.edid_firmwar
e=HDMI-A-1:edid/LG-C2.bin"
"Boot to single-user mode"    "amd_pstate=active BOOT_IMAGE=/@/boot/vmlinuz-linux-%v root=UUID=53e270ad-df
d5-4874-a125-69d21ada6b8d rw rootflags=subvol=@ rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel
=3 sysrq_always_enabled=1 amdgpu.ppfeaturemask=0xffffffff nowatchdog nmi_watchdog=0 psi=1 single"
"Boot with minimal options"   "ro root=/dev/nvme0n1p2"

its also on my inxi here

Kernel: 6.4.3-273-tkg-bmq arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
    parameters: intel_pstate=passive split_lock_detect=off amd_pstate=active
    BOOT_IMAGE=/@/boot/vmlinuz-linux-linux-tkg-bmq-generic_v3
    root=UUID=53e270ad-dfd5-4874-a125-69d21ada6b8d rw rootflags=subvol=@
    rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
    sysrq_always_enabled=1 amdgpu.ppfeaturemask=0xffffffff nowatchdog
    nmi_watchdog=0 psi=1 drm.edid_firmware=HDMI-A-1:edid

The only kernel I can load Waydroid on is catchy (but then magisk doesn’t work correctly) anything else causes it to fail as I said in the OP

with

[20:29:51] Starting waydroid session
[gbinder] WARNING: Service manager /dev/binder has died

Austin · 18 July 2023 01:41

Can you run xanmod?
For Zen you will have to remove binder_linux from /etc/modules-load.d/binder.conf

zany130 · 18 July 2023 02:04

So I was using linux-xanmod-anbox and that didn't work tried linux-xanmod and that is indeed working actually and Magisk works as well.

I can't get Waydroid to launch on zen or tkg-bmq though tried removing /etc/modules-load.d/binder.conf and it gives me this now
when trying to run waydroid show-full-ui

[gbinder] ERROR: Can't open /dev/binder: No such file or directory
[21:55:51] Failed to add presence handler: None

tried removing psi from my kernel commands and made no difference

anyway solution is to use linux-xanmod for Waydroid with root and now that I re read the guide I do see it is actually mentioned must of missed it

oh and apps not installing was because the arm translation layer didn't get installed correctly I guess re ran the wayland-extras script and reinstalled the ndk one

Austin · 18 July 2023 02:43

So you are able to run linux-cachyos without any tweaks?
linux-zen should have worked without any tweaks, just like cachyos.

@NaN, could you confirm that Waydroid worked for you with linux_zen without any tweaks?

That’s great!

Actually, I added it to the guide only after your post.
Though I had already mentioned it in the thread comments, I was waiting for a reply from
‘Outdated Binder module · Issue #386 · xanmod/linux · GitHub’
to add it to the guide.

zany130 · 18 July 2023 02:48

Yeah its strange on cachy, waydroid works fine (with no magisk though) with psi=1 and echo binder_linux | sudo tee /etc/modules-load.d/binder.conf haven’t tried seeing if removing those 2 tweaks breaks waydroid, I thought they were needed for all kernel’s

on the zen kernel and the tkg-bmq (which I think also has binder) I can’t get it to work no matter what I try
it just refuses to load with either the no such file or directory error or service manager has died

Austin · 18 July 2023 02:52

These two tweaks are only supposed to be needed for kernels with binder drivers as kernel modules, not inbuilt.

NaN · 18 July 2023 04:35

Yup, no tweaks needed for me. I just had to follow the steps to load the binder modules at /dev/binder at startup and that was it.

Austin · 18 July 2023 06:26

This one?

NaN · 18 July 2023 06:32

Yeah that one.

Austin · 18 July 2023 16:15

If Zen kernel doesn’t work with these

Try doing step 4 of the guide:

zany130 · 18 July 2023 23:51

zen kernel still gives (after a reboot)

[gbinder] ERROR: Can't open /dev/binder: No such file or directory
[19:47:48] Failed to add presence handler: None

when following the guide

cat /etc/fstab
File: /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>                          <mount point>  <type>  <options>  <dump>  <pass>
UUID=4AC6-7B21                            /boot/efi      vfat    umask=0077 0 2
UUID=53e270ad-dfd5-4874-a125-69d21ada6b8d /              btrfs   subvol=/@,defaults,noatime,compress=zstd,
discard=async,ssd 0 0
UUID=53e270ad-dfd5-4874-a125-69d21ada6b8d /home          btrfs   subvol=/@home,defaults,noatime,compress=z
std,discard=async,ssd 0 0
UUID=53e270ad-dfd5-4874-a125-69d21ada6b8d /root          btrfs   subvol=/@root,defaults,noatime,compress=z
std,discard=async,ssd 0 0
UUID=53e270ad-dfd5-4874-a125-69d21ada6b8d /srv           btrfs   subvol=/@srv,defaults,noatime,compress=zs
td,discard=async,ssd 0 0
UUID=53e270ad-dfd5-4874-a125-69d21ada6b8d /var/cache     btrfs   subvol=/@cache,defaults,noatime,compress=
zstd,discard=async,ssd 0 0
UUID=53e270ad-dfd5-4874-a125-69d21ada6b8d /var/log       btrfs   subvol=/@log,defaults,noatime,compress=zs
td,discard=async,ssd 0 0
UUID=53e270ad-dfd5-4874-a125-69d21ada6b8d /var/tmp       btrfs   subvol=/@tmp,defaults,noatime,compress=zs
td,discard=async,ssd 0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0
UUID=d6a92575-7181-4506-80d1-84a9594f90e8 /mnt/GAMES     auto    nosuid,nodev,nofail,x-gvfs-show 0 0
none                         /dev/binderfs binder   nofail  0      0

 ╭─zany130@Garuda in ~ via  v3.11.3 took 7ms
 ╰─λ cat /etc/tmpfiles.d/waydroid.conf
File: /etc/tmpfiles.d/waydroid.conf
d! /dev/binderfs 0755 root root

 ╭─zany130@Garuda in ~ via  v3.11.3 took 6ms
 ╰─λ cat /etc/modules-load.d/waydroid.conf
File: /etc/modules-load.d/waydroid.conf
binder_linux

Austin · 19 July 2023 01:18

It should be binder.

Edit:
I too am not able to run Waydroid with Zen

@NaN, any hint?

NaN · 19 July 2023 11:01

Lemme check, I haven't used waydroid in a while. Currently I am traveling in a train so it would take a while for me to respond.

Austin · 19 July 2023 11:02

No worries, please you take your time.

NaN · 20 July 2023 18:57

@zany130 and @Austin I have just updated my system and also reinstalled waydroid. I am facing no issues using waydroid in linux-zen

╰─λ cat /etc/modules-load.d/waydroid.conf
File: /etc/modules-load.d/waydroid.conf
binder

╭─siddharth@siddharth in ~ took 29ms
󰂃66%
╰─λ cat /etc/tmpfiles.d/waydroid.conf
File: /etc/tmpfiles.d/waydroid.conf
d! /dev/binderfs 0755 root root

Redacted /etc/fstab

none    /dev/binderfs   binder  nofail  0   0

The only reason for the failure erroneous use of binder_linux in /etc/modules-load.d/waydroid.conf instead of binder.

Oh I also do not use the psi=1 kernel parameter

zany130 · 21 July 2023 00:12

for me it still gives this on zen

(didn't try a fresh install maybe that would work but then strange its working on cachy and xanmod)

[gbinder] ERROR: Can't open /dev/binder: No such file or directory
[20:06:57] Failed to add presence handler: None

File: /etc/tmpfiles.d/waydroid.conf
d! /dev/binderfs 0755 root root

File: /etc/modules-load.d/waydroid.conf
binder

and

File: /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>                          <mount point>  <type>  <options>  <dump>  <pass>
UUID=4AC6-7B21                            /boot/efi      vfat    umask=0077 0 2
UUID=53e270ad-dfd5-4874-a125-69d21ada6b8d /              btrfs   subvol=/@,defaults,noatime,compress=zstd,
discard=async,ssd 0 0
UUID=53e270ad-dfd5-4874-a125-69d21ada6b8d /home          btrfs   subvol=/@home,defaults,noatime,compress=z
std,discard=async,ssd 0 0
UUID=53e270ad-dfd5-4874-a125-69d21ada6b8d /root          btrfs   subvol=/@root,defaults,noatime,compress=z
std,discard=async,ssd 0 0
UUID=53e270ad-dfd5-4874-a125-69d21ada6b8d /srv           btrfs   subvol=/@srv,defaults,noatime,compress=zs
td,discard=async,ssd 0 0
UUID=53e270ad-dfd5-4874-a125-69d21ada6b8d /var/cache     btrfs   subvol=/@cache,defaults,noatime,compress=
zstd,discard=async,ssd 0 0
UUID=53e270ad-dfd5-4874-a125-69d21ada6b8d /var/log       btrfs   subvol=/@log,defaults,noatime,compress=zs
td,discard=async,ssd 0 0
UUID=53e270ad-dfd5-4874-a125-69d21ada6b8d /var/tmp       btrfs   subvol=/@tmp,defaults,noatime,compress=zs
td,discard=async,ssd 0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0
UUID=d6a92575-7181-4506-80d1-84a9594f90e8 /mnt/GAMES     auto    nosuid,nodev,nofail,x-gvfs-show 0 0
none                         /dev/binderfs binder   nofail  0      0

removed all other tweaks like psi=1

File: /boot/refind_linux.conf
"Boot with standard options"  "amd_pstate=active BOOT_IMAGE=/@/boot/vmlinuz-linux-%v root=UUID=53e270ad-df
d5-4874-a125-69d21ada6b8d rw rootflags=subvol=@ rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel
=3 sysrq_always_enabled=1 amdgpu.ppfeaturemask=0xffffffff nowatchdog nmi_watchdog=0 drm.edid_firmware=HDMI
-A-1:edid/LG-C2.bin"
"Boot to single-user mode"    "amd_pstate=active BOOT_IMAGE=/@/boot/vmlinuz-linux-%v root=UUID=53e270ad-df
d5-4874-a125-69d21ada6b8d rw rootflags=subvol=@ rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel
=3 sysrq_always_enabled=1 amdgpu.ppfeaturemask=0xffffffff nowatchdog nmi_watchdog=0 single"
"Boot with minimal options"   "ro root=/dev/nvme0n1p2"

Austin · 21 July 2023 04:00

I, too am having the same issue as @zany130.

Hmm. I tried reinstalling python-gbinder & libgbinder(followed by a reboot), still, the issue persists.
I don’t know if a Waydroid reinstall should work?
Let us know if someone has the same issue on a fresh Waydroid install.
I would not want to reinstall Waydroid cause I have setup many apps that I use.
But I will do it if nobody can.