Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

RK3576 nanopi M5 cannot start Waydrod

Featured Replies

RK3576 nanopi M5 cannot start Waydrod
I am trying to use Waydrod on the nanopi M5, and I am starting it up
CONFIG_ANDROID_BINDER_IPC=y
CONFIG_ANDROID_BINDERFS=y
CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder"
However, during the actual startup of Waydrod, there was a continuous black screen crash and restart.
The following is the error log:
nano@nanopi-m5:$ waydroid show-full-ui
[13:55:56] Introspect error on :1.103:/ContainerManager: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[13:56:21] Failed to unfreeze container. Trying to launch anyways...
[13:57:06] Failed to get service waydroidplatform, trying again...
[13:57:07] Failed to get service waydroidplatform, trying again...
[13:57:08] Failed to get service waydroidplatform, trying again...
[13:57:09] Failed to get service waydroidplatform, trying again...
[13:57:10] Failed to get service waydroidplatform, trying again...
[13:57:11] Failed to get service waydroidplatform, trying again...
[13:57:12] Failed to get service waydroidplatform, trying again...
[13:57:13] Failed to get service waydroidplatform, trying again...
[13:57:14] Failed to get service waydroidplatform, trying again...
[13:57:15] Failed to get service waydroidplatform, trying again...
[13:57:16] Failed to get service waydroidplatform, trying again...nano@nanopi-m5:$ waydroid log
(009909) [13:52:01] % lxc-info --version
5.0.3
(009909) [13:52:01] % mkdir -p /var/lib/waydroid/lxc/waydroid
(009909) [13:52:01] % 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"
(009909) [13:52:01] % sed -i s/LXCARCH/aarch64/ /var/lib/waydroid/lxc/waydroid/config
(009909) [13:52:01] % cp -fpr /usr/lib/waydroid/data/configs/waydroid.seccomp /var/lib/waydroid/lxc/waydroid/waydroid.seccomp
(009909) [13:52:01] % systemctl is-active -q apparmor
(009909) [13:52:01] % mv /var/lib/waydroid/config_nodes /var/lib/waydroid/lxc/waydroid
(006325) [13:52:01] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH
STOPPED
(006325) [13:52:01] % modprobe -q ashmem_linux
(006325) [13:52:01] % chmod 666 -R /dev/binder
(006325) [13:52:01] % chmod 666 -R /dev/vndbinder
(006325) [13:52:01] % chmod 666 -R /dev/hwbinder
(010960) [13:53:11] Starting waydroid session
(006325) [13:53:11] % /usr/lib/waydroid/data/scripts/waydroid-net.sh start
vnic is waydroid0
(006325) [13:53:11] % systemctl is-active -q nfcd
(006325) [13:53:11] % chmod 777 -R /dev/sw_sync
(006325) [13:53:11] % chmod 777 -R /sys/kernel/debug/sync/sw_sync
(006325) [13:53:11] % chmod 777 -R /dev/dri/renderD130
(006325) [13:53:11] % chmod 777 -R /dev/dri/renderD129
(006325) [13:53:11] % chmod 777 -R /dev/dri/renderD128
(006325) [13:53:11] % chmod 777 -R /dev/fb0
(006325) [13:53:11] % chmod 777 -R /dev/dma_heap/reserved
(006325) [13:53:11] % chmod 777 -R /dev/dma_heap/system-uncached
(006325) [13:53:11] % chmod 777 -R /dev/dma_heap/system
(006325) [13:53:11] % mv /var/lib/waydroid/config_session /var/lib/waydroid/lxc/waydroid
(006325) [13:53:11] % mount -o ro /var/lib/waydroid/images/system.img /var/lib/waydroid/rootfs
(006325) [13:53:11] % mkdir -p /var/lib/waydroid/overlay_work/system
(006325) [13:53:11] % mount -t overlay -o ro,lowerdir=/var/lib/waydroid/overlay:/var/lib/waydroid/rootfs,upperdir=/var/lib/waydroid/overlay_rw/system,workdir=/var/lib/waydroid/overlay_work/system,xino=off overlay /var/lib/waydroid/rootfs
(006325) [13:53:11] % mount -o ro /var/lib/waydroid/images/vendor.img /var/lib/waydroid/rootfs/vendor
(006325) [13:53:11] % mkdir -p /var/lib/waydroid/overlay_work/vendor
(006325) [13:53:11] % mount -t overlay -o ro,lowerdir=/var/lib/waydroid/overlay/vendor:/var/lib/waydroid/rootfs/vendor,upperdir=/var/lib/waydroid/overlay_rw/vendor,workdir=/var/lib/waydroid/overlay_work/vendor,xino=off overlay /var/lib/waydroid/rootfs/vendor
(006325) [13:53:11] % mount -o bind /var/lib/waydroid/waydroid.prop /var/lib/waydroid/rootfs/vendor/waydroid.prop
(006325) [13:53:11] Save config: /var/lib/waydroid/waydroid.cfg
(006325) [13:53:11] % lxc-start -P /var/lib/waydroid/lxc -F -n waydroid -- /init
(006325) [13:53:11] New background process: pid=11037, output=background
(006325) [13:53:11] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH
RUNNING
(010960) [13:53:11] Skipping clipboard manager service because of missing pyclip package
(011121) [13:55:27] Session is already running
(011139) [13:55:56] Introspect error on :1.103:/ContainerManager: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(011139) [13:55:56] Executing introspect queue due to error
(011139) [13:56:21] Failed to unfreeze container. Trying to launch anyways...
(011139) [13:57:06] Failed to get service waydroidplatform, trying again...
(006325) [13:57:06] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH
RUNNING
(011139) [13:57:07] Failed to get service waydroidplatform, trying again...
(011139) [13:57:08] Failed to get service waydroidplatform, trying again...
(011139) [13:57:09] Failed to get service waydroidplatform, trying again...
(011139) [13:57:10] Failed to get service waydroidplatform, trying again...
(011139) [13:57:11] Failed to get service waydroidplatform, trying again...
(011139) [13:57:12] Failed to get service waydroidplatform, trying again...
(011139) [13:57:13] Failed to get service waydroidplatform, trying again...
(011139) [13:57:14] Failed to get service waydroidplatform, trying again...
(011139) [13:57:15] Failed to get service waydroidplatform, trying again...
(011139) [13:57:16] Failed to get service waydroidplatform, trying again...
(012115) [13:57:27] % tail -n 60 -F /var/lib/waydroid/waydroid.log
(012115) [13:57:27] *** output passed to waydroid stdout, not to this log ***
nano@nanopi-m5:~sudo systemctl status waydroid-containerer
● waydroid-container.service - Waydroid Container
Loaded: loaded (/usr/lib/systemd/system/waydroid-container.service; enabled; preset: enabled)
Active: active (running) since Sun 2025-09-21 13:17:05 CST; 41min ago
Main PID: 6325 (waydroid)
Tasks: 6 (limit: 9464)
Memory: 21.4M (peak: 92.5M)
CPU: 4min 20.835s
CGroup: /system.slice/waydroid-container.service
├─ 6325 /usr/bin/python3 /usr/bin/waydroid -w container start
└─11005 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 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=waydroid0 ->

9月 21 13:17:05 nanopi-m5 systemd[1]: Started waydroid-container.service - Waydroid Container.
9月 21 13:17:52 nanopi-m5 waydroid[6552]: [13:17:52] Downloading https://sourceforge.net/projects/waydroid/files/images/system/lineage/waydroid_arm64/lineage-20.0-20250809-VANILLA-waydroid_arm64-system.zip/download
9月 21 13:34:17 nanopi-m5 waydroid[6552]: [13:34:17] Validating system image
9月 21 13:53:11 nanopi-m5 dnsmasq[11005]: started, version 2.90 cachesize 150
9月 21 13:53:11 nanopi-m5 dnsmasq[11005]: 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
9月 21 13:53:11 nanopi-m5 dnsmasq-dhcp[11005]: DHCP, IP range 192.168.240.2 -- 192.168.240.254, lease time 1h
9月 21 13:53:11 nanopi-m5 dnsmasq-dhcp[11005]: DHCP, sockets bound exclusively to interface waydroid0
9月 21 13:53:11 nanopi-m5 dnsmasq[11005]: reading /etc/resolv.conf
9月 21 13:53:11 nanopi-m5 dnsmasq[11005]: using nameserver 127.0.0.53#53
9月 21 13:53:11 nanopi-m5 dnsmasq[11005]: read /etc/hosts - 10 names

nano@nanopi-m5:~$ systemctl status dbus
● dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: active (running) since Sat 2025-09-20 21:30:20 CST; 16h ago
TriggeredBy: ● dbus.socket
Docs: man:dbus-daemon(1)
Main PID: 1455 (dbus-daemon)
Tasks: 1 (limit: 9464)
Memory: 3.5M (peak: 3.8M)
CPU: 2.817s
CGroup: /system.slice/dbus.service
└─1455 @dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

9月 21 13:16:57 nanopi-m5 dbus-daemon[1455]: [system] Reloaded configuration
9月 21 13:17:02 nanopi-m5 dbus-daemon[1455]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=1527 comm="/usr/sbin/NetworkManager --no-daemon")
9月 21 13:17:02 nanopi-m5 dbus-daemon[1455]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
9月 21 13:17:11 nanopi-m5 dbus-daemon[1455]: Unknown username "gnome-remote-desktop" in message bus configuration file
9月 21 13:17:11 nanopi-m5 dbus-daemon[1455]: Unknown username "whoopsie" in message bus configuration file
9月 21 13:17:11 nanopi-m5 dbus-daemon[1455]: [system] Reloaded configuration
9月 21 13:23:17 nanopi-m5 dbus-daemon[1455]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.94' (uid=1000 pid=4015 comm="/usr/bin/gnome-control-center network")
9月 21 13:23:17 nanopi-m5 dbus-daemon[1455]: [system] Successfully activated service 'org.freedesktop.hostname1'
9月 21 13:53:11 nanopi-m5 dbus-daemon[1455]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=1527 comm="/usr/sbin/NetworkManager --no-daemon")
9月 21 13:53:11 nanopi-m5 dbus-daemon[1455]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
nano@nanopi-m5:$ nano@nanopi-m5:$ sudo lxc-attach -n waydroid -- systemctl status dbus
lxc-attach: waydroid: ../src/lxc/attach.c: get_attach_context: 406 Connection refused - Failed to get init pid
lxc-attach: waydroid: ../src/lxc/attach.c: lxc_attach: 1470 Connection refused - Failed to get attach context
nano@nanopi-m5:$ nano@nanopi-m5:$ ls -l /var/lib/waydroid/
ls -l /var/lib/waydroid/lxc/waydroid/
total 52
drwxr-xr-x 2 root root 4096 9月 21 13:52 cache_http
drwxr-xr-x 2 root root 4096 9月 21 13:52 host-permissions
drwxr-xr-x 2 root root 4096 9月 21 13:51 images
drwxr-xr-x 3 root root 4096 9月 21 13:52 lxc
drwxr-xr-x 3 root root 4096 9月 21 13:52 overlay
drwxr-xr-x 4 root root 4096 9月 21 13:52 overlay_rw
drwxr-xr-x 4 root root 4096 9月 21 13:53 overlay_work
drwxr-xr-x 1 root root 4096 9月 21 13:52 rootfs
-rw-r--r-- 1 root root 472 9月 21 13:52 waydroid_base.prop
-rw-r--r-- 1 root root 486 9月 21 13:53 waydroid.cfg
-rw-rw-rw- 1 root root 6558 9月 21 13:57 waydroid.log
-rw-r--r-- 1 root root 776 9月 21 13:53 waydroid.prop
total 16
-rw-r--r-- 1 root root 989 9月 21 13:52 config
-rw-r--r-- 1 root root 1860 9月 21 13:52 config_nodes
-rw-r--r-- 1 root root 311 9月 21 13:53 config_session
-rw-r--r-- 1 root root 346 6月 24 17:18 waydroid.seccomp
nano@nanopi-m5:~$

How to reproduce?

At present, RK3576 cannot use Waydrod when opening IPC and Android binder.
Perhaps it is due to the absence of VNet ANDROID_SHMEM.

On which OS are you observing this problem? (for easier diagnosis please provide logs with armbianmonitor -u)

Armbian Ubuntu 24.04 Noble

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.