Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
[Feature Request] Enable native BinderFS support in linux-omarchy for Waydroid
Reported by roubilibo · filed Sep 18, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
Feature request
Please enable native BinderFS support in the linux-omarchy kernel configuration for Waydroid users.
Current situation
On Omarchy 4.0.4-1 with linux-omarchy 7.2.5-3, the kernel does not provide the Android Binder/BinderFS configuration needed by Waydroid:
CONFIG_ANDROID=y
CONFIG_ANDROID_BINDER_IPC=y
CONFIG_ANDROID_BINDERFS=y
CONFIG_ANDROID_BINDER_DEVICES=""To run Waydroid, I currently need the out-of-tree binder_linux-dkms package. The module is loaded from:
/lib/modules/7.2.5-3-omarchy/updates/dkms/binder_linux.ko.zstThe kernel reports that this out-of-tree module taints the kernel.
Requested change
Please consider enabling BinderFS in the linux-omarchy kernel configuration, or documenting the intended supported approach for Waydroid users.
This would avoid requiring a DKMS module that must be rebuilt after kernel updates and would follow the BinderFS configuration recommended by the ArchWiki Waydroid documentation:
https://wiki.archlinux.org/title/Waydroid#Using_binderfs
Test system
- Omarchy: 4.0.4-1
- Kernel: 7.2.5-3-omarchy
- CPU: AMD Ryzen 5 5600
- GPU: AMD Radeon RX 6600
- Desktop: Hyprland
- Waydroid: 1.6.3
- Waydroid image: GAPPS with libndk ARM translation
The current DKMS workaround allows Waydroid to start, but native BinderFS support would be cleaner and easier to maintain.
Related discussion: https://github.com/omacom/omarchy/discussions/12453
View raw text
## Feature request Please enable native BinderFS support in the `linux-omarchy` kernel configuration for Waydroid users. ### Current situation On Omarchy 4.0.4-1 with `linux-omarchy 7.2.5-3`, the kernel does not provide the Android Binder/BinderFS configuration needed by Waydroid: ``` CONFIG_ANDROID=y CONFIG_ANDROID_BINDER_IPC=y CONFIG_ANDROID_BINDERFS=y CONFIG_ANDROID_BINDER_DEVICES="" ``` To run Waydroid, I currently need the out-of-tree `binder_linux-dkms` package. The module is loaded from: ``` /lib/modules/7.2.5-3-omarchy/updates/dkms/binder_linux.ko.zst ``` The kernel reports that this out-of-tree module taints the kernel. ### Requested change Please consider enabling BinderFS in the `linux-omarchy` kernel configuration, or documenting the intended supported approach for Waydroid users. This would avoid requiring a DKMS module that must be rebuilt after kernel updates and would follow the BinderFS configuration recommended by the ArchWiki Waydroid documentation: https://wiki.archlinux.org/title/Waydroid#Using_binderfs ### Test system - Omarchy: 4.0.4-1 - Kernel: 7.2.5-3-omarchy - CPU: AMD Ryzen 5 5600 - GPU: AMD Radeon RX 6600 - Desktop: Hyprland - Waydroid: 1.6.3 - Waydroid image: GAPPS with libndk ARM translation The current DKMS workaround allows Waydroid to start, but native BinderFS support would be cleaner and easier to maintain. Related discussion: https://github.com/omacom/omarchy/discussions/12453
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 15:42 UTC