OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
apps-services high occasional DISPUTE

Get Waydroid running when the linux-omarchy kernel has no binder driver

omarchylinux-omarchywaydroidandroidliminekerneldesktoplaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Cause confirmed on this machine: /proc/config.gz on 7.2.5-3-omarchy has both ANDROID_BINDER options unset, while /usr/lib/modules/7.2.3-arch1-3/build/.config has CONFIG_ANDROID_BINDER_IPC_RUST=y. The stable mirrors were read today: pkgs.omarchy.org/stable still lists linux-omarchy-7.2.5-3, and stable-mirror.omarchy.org core.db still lists linux-7.2.3.arch1-3 and linux-lts-6.18.49-3. #12149 supplies the symptom text and suppressed-message counts, #13695 the binder_linux not found message, #12454 the 7.2.5-4 report. /etc/default/limine is sourced last by limine-common-functions and the migration writes BOOT_ORDER there, limine-update calls limine-mkinitcpio. The fix omitted the one workaround that works today on linux-omarchy for CPUs without IBT: AUR binder_linux-dkms, which the Arch wiki documents. This workstation (i9-9900K, no ibt flag) runs it on 7.2.5-3-omarchy, dkms status shows binder installed for both kernels and /proc/filesystems lists binder. The #12454 reporter (Ryzen 5 5600) also runs Waydroid that way. That matters because the stock-kernel route the fix offers lands on the broken 7.2.3.arch1-3 build. Added it as a labelled branch with the #13032 freeze report as its caveat. Waydroid itself was not started here.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.
RISK

Changing BOOT_ORDER changes which kernel boots by default. Both kernels stay installed, so the other one is always one menu entry away. binder_linux-dkms is an out-of-tree AUR module that taints the kernel, and one user on an Ivy Bridge CPU reported hard desktop freezes with it (omacom/omarchy#13032). On a CPU with IBT it oopses the kernel on every Waydroid start.

Symptom

After updating to Omarchy 4.0.4, Waydroid no longer starts. waydroid status stays at:


Session:	RUNNING
Container:	STOPPED
IP address:	UNKNOWN

The journal floods with [gbinder] ERROR: Can't open /dev/anbox-binder: No such file or directory, journald reports Suppressed 219321 messages from waydroid-container.service, and two CPU cores sit at 100%. On a fresh install sudo waydroid init fails with ERROR: Binder node "binder" for waydroid not found or FATAL: Module binder_linux not found. grep binder /proc/filesystems prints nothing.

Cause

linux-omarchy 7.2.5-3, which Omarchy 4.0.4's migration 1789325478.sh installs and makes the first Limine boot entry, is built with both binder drivers off: # CONFIG_ANDROID_BINDER_IPC is not set and # CONFIG_ANDROID_BINDER_IPC_RUST is not set (confirmed in /usr/lib/modules/7.2.5-3-omarchy/build/.config). With no binder there is no binderfs, so Waydroid has nothing to open, and an enabled waydroid-container.service retries in a tight loop. Stock Arch linux and linux-lts build the Rust binder driver in (CONFIG_ANDROID_BINDER_IPC_RUST=y, CONFIG_ANDROID_BINDER_DEVICES=""). Omarchy's kernel maintainer has published test kernels with binder enabled, and a report in omacom/omarchy#12454 says a 7.2.5-4 build has it, but as of 2026-10-04 the stable repository at pkgs.omarchy.org/stable still serves linux-omarchy-7.2.5-3.

Fix

**1. Stop the retry loop:**


waydroid session stop
sudo systemctl disable --now waydroid-container.service

**2. Confirm it is the kernel, and check your CPU:**


uname -r
zgrep ANDROID_BINDER /proc/config.gz
grep binder /proc/filesystems
pacman -Q linux linux-lts 2>/dev/null
grep -ow ibt /proc/cpuinfo | head -1     # prints 'ibt' if the CPU has Indirect Branch Tracking

**3a. CPU without ibt (all AMD, and Intel before 11th gen): add the binder module to linux-omarchy.** This is the Arch wiki's DKMS route and it keeps the Omarchy kernel. linux-omarchy-headers is already installed by the 4.0.4 migration.


yay -S binder_linux-dkms
dkms status                      # binder installed for 7.2.5-3-omarchy
sudo modprobe binder_linux devices=binder,hwbinder,vndbinder
echo binder_linux | sudo tee /etc/modules-load.d/binder_linux.conf
echo 'options binder_linux devices=binder,hwbinder,vndbinder' | sudo tee /etc/modprobe.d/binder_linux.conf

Do not use this on a CPU that prints ibt. It oopses the kernel on every Waydroid start there. See binder-linux-dkms-oops-missing-endbr-ibt.

**3b. Any CPU: boot a kernel that has binder built in.** The migration left the stock linux installed. Put it first in the boot order. /etc/default/limine overrides every drop-in, which is where the migration wrote its line:


sudoedit /etc/default/limine

BOOT_ORDER="linux, linux-omarchy, linux-omarchy-*, *, *fallback, Snapshots"

sudo limine-update

Or pick the linux entry in the Limine menu for each boot. **Check the version first:** Omarchy's stable mirror still carries linux 7.2.3.arch1-3 and linux-lts 6.18.49-3, which are broken in a different way. See waydroid-rust-binder-no-such-process-bad-bindgen-build before rebooting.

**4. Or wait for a fixed linux-omarchy.** After each omarchy update, check pacman -Q linux-omarchy and zgrep ANDROID_BINDER /proc/config.gz on that kernel. Once it has binder, remove binder_linux-dkms and the two conf files from step 3a.

**5. Re-enable Waydroid** once grep binder /proc/filesystems prints nodev binder:


sudo systemctl enable --now waydroid-container.service
waydroid session start

Verify

grep binder /proc/filesystems prints nodev binder, and waydroid status shows Container: RUNNING. journalctl -u waydroid-container -b has no Can't open /dev/anbox-binder flood.

Sources

waydroid-no-binder-on-linux-omarchy-kernel