Current section in the page:

CONFIG_ASHMEM=m
CONFIG_ANDROID=y
CONFIG_ANDROID_BINDER_IPC=m
CONFIG_ANDROID_BINDERFS=n
CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder"

CONFIG_ANDROID_BINDER_IPC is a bool value in the kconfig of android. It can only take y/n. Maybe should be y here? https://github.com/torvalds/linux/blob/master/drivers/android/Kconfig

Same question for CONFIG_ASHMEM.
—This unsigned comment is by User:Pbeliveau (talk) 03:30, 15 April 2022 (UTC). Please sign your posts with ~~~~!

while Apparmor is enabled, this configuration in /etc/apparmor.d/usr.sbin.dnsmasq is needed otherwise LXC(also waydroid) will fail

@{run}/waydroid-lxc/ r, 
@{run}/waydroid-lxc/* rw, 

--Alfzki (talk) 13:04, 28 April 2022 (UTC)

The Wiki page states that WayDroid does not run on NVIDIA GPUs, unless software rendering is used. It seems that fact has changed at some point, as I was able to boot up WayDroid with no modifications, running the GAPPS image managed by WayDroid (not from AUR). Managed to install LibHoudini via https://github.com/casualsnek/waydroid_script . Installed Arknights from the Play Store, and after fixing a permissions issue in the image via shell (second-last message in issue #45 in the above repository) it actually seems to run surprisingly well (I'd say about on par with Microsoft's WSA).

System information: AMD Ryzen 3950x NVIDIA Geforce GTX 1660 Super / nvidia-dkms driver Running on Kernel: linux-zen DE: KDE Wayland

MaxDev 404 (talk) 00:36, 7 January 2023 (UTC)

Waydroid automatically defaults to software rendering on nvidia now. See https://github.com/waydroid/waydroid/pull/449

Quackdoc (talk) 14:06, 8 January 2023 (UTC)

It seems like waydroid, with (almost?) all of it's dependencies has been uploaded to official packages: https://archlinux.org/packages/extra/any/waydroid/ Wilsontulus (talk) 01:07, 2 November 2025 (UTC)

If Docker is installed on the host, it changes the default iptables FORWARD policy to DROP to isolate containers. This silently drops Waydroid traffic because the kernel treats it as routed traffic rather than outbound traffic.

The standard instruction to append rules (-A) often fails in this scenario because the rules are added after Docker's block rules. Users with Docker need to insert the rules at the top of the chain using -I:

# iptables -I FORWARD 1 -i waydroid0 -j ACCEPT
# iptables -I FORWARD 1 -o waydroid0 -j ACCEPT

--Foothill5285 (talk) 00:57, 19 January 2026 (UTC)

When using Waydroid on desktop environments the Meta key (Super/Windows key) often triggers the Android Google Assistant or Search function within the container, even if the user intended to open the host's application menu. To prevent Waydroid from intercepting the Meta key for the assistant, you can disable the default assistant app within the Android container:

• Settings > Apps > Default apps > Digital assistant app
• by setting the default digital assistant app to None.

This ensures that the Meta key is either ignored by Waydroid or can be handled exclusively by the host's window manager/compositor shortcuts.

--NicerSlicer (talk) 14:56, 10 February 2026 (UTC)