Waydroid

The requirements depend on the CPU architecture. You can check table for more information.

You can check if you have the required CPU instructions with cat /proc/cpuinfo.

Waydroid currently works best with Intel GPUs. They should work out of the box.

AMD GPUs appear to have mixed results (in particular, the RX 6800 does not work using official images as of 2022-09-29); if Waydroid does not work you might also want to try to build a new Waydroid image (which works for Radeon 680M), or try the NVIDIA instructions below.

NVIDIA GPUs do not work currently, but there are 2 workarounds:

• Switch to integrated graphic card if possible;
• Use software rendering:
  • Make sure that you have already run waydroid init (see #Installation section)
  • Edit /var/lib/waydroid/waydroid_base.prop and set:

    ro.hardware.gralloc=default
    ro.hardware.egl=swiftshader

  • Restart the waydroid-container.service.

Waydroid only works in a Wayland session manager, so make sure you are in a Wayland session.

Note that even if you are in X11, many Wayland session managers support nested session (so you can run it inside your X11 session), the simplest example is weston.

You need to run a kernel which comes with the binder modules and optionally the ashmem one. They are not part of Arch Linux's default kernel (), thus you need to install a kernel which ships these modules.

You might also need to configure your bootloader to use a different kernel. Please refer to the wiki page of your bootloader how to boot with the new kernel. Booting into another kernel (version) is one of the few occasions when you have to reboot a Linux system. You should boot into the kernel with these modules before starting Waydroid.

To get a compatible kernel, you have multiple options:

The kernel includes the necessary modules. This might be the most comfortable way, as you do not have to compile the kernel (which takes a long time) and will receive updated versions regularly.

You can install and load kernel modules with:

# modprobe ashmem_linux
# modprobe binder_linux

Alternatively, if your kernel is 5.18 or newer, install binder_linux-dkms^AUR, which provides just binder_linux.

Alternatively, you can recompile the kernel — or other kernel packages (>=5.7) — with the necessary options. Also see Kernel#Compilation.

When setting compilation options, you have 2 options available; binder and binderfs. Instructions for both are provided below.

The modules can either be compiled into the kernel (), into modules (), or not at all (). Also, not all combinations in the configuration are possible, and some options will require other options.

The configuration options below will compile binder as a module, while the last option specifies that there will be three devices created in the directory, when the binder module is loaded.

When building a kernel from the AUR, one can update the configuration with the following steps:

1. run , which will download the sources, verify and extract them and run the function.
2. edit the file (with the dot in the filename), which is located at the base of the kernel directory.
3. at the end of the function was probably a command which regenerates the makefiles with information from the configuration, possibly . Move that to the build() function, or execute it yourself.
4. run makepkg --noextract, which will continue from the place where stopped.

The binder kernel module is known to cause some issues to several users. To address these issues, binderfs was created. One has to choose between the old and the new way when compiling the kernel. With the options below, one will use binderfs instead.

With the kernel sources comes also a simple script to set configuration options. It will not do dependency checks, just like when editing the configuration by hand. When being in the same directory where the file lies, one can execute the following commands:

When building a kernel from the AUR, it is enough to insert these lines at the right place in the PKGBUILD, usually in .

Make sure you have the latest version of Waydroid package, and Waydroid will take automatically care of this.

Waydroid is in rapid developement so if you face issues, here is a good list of steps to do first:

1. Make sure your Waydroid package is up to date;
2. Make sure you have the latest Waydroid image by running
3. Reset Waydroid: stop the waydroid-container.service, run

   # waydroid init -f

   and start the service again.
4. You may also want to do little cleanup, run

See https://github.com/waydroid/waydroid/issues/70

Click F11 to switch the current app to windowed mode.

Install

Press Left Alt key.

On Arch based distributions there's a "bug" that may appear while working with lxc-attach that may cause this issue with commands inside like or settings. A possible workaround for this would be replace the command with

See https://github.com/waydroid/waydroid/issues/136

You should enable PSI. Add to the kernel command line.