Arch Linux User Repository

Before install Waydroid, make sure that your kernel supports binder and ashmem module (currently only linux-zen does)

Keep in mind that Waydroid only works with Wayland compositors. It also does not work yet with proprietary NVIDIA driver.

After install waydroid and waydroid-image, run this command to initialize the container:

# waydroid init

Then the container can be started via waydroid-container.service. The official project group/channel can be found on:

• Matrix: https://matrix.to/#/#waydroid:connolly.tech
• Telegram: https://t.me/waydroid

python-gbinder 1.1.2 should now support building using cython3.

Does anyone have a "fix" for the python-gbinder dependency to work with the latest cython installed? Currently, python-gbinder has a hard dependency on cpython0, and cython0 conflicts with cython.

Edit: Answering myself, build it via makechrootpkg.

please add binder_linux-dkms as (optional?) dependency since it's required to download the OTA when you start waydroid for the first time.

@yuhldr, installing linux-headers didn't work?

Could anyone use waydroid with linux-cachyos kernel?

linux-headers or linux-lts-headers maybe necessary

I tried symlinking /dev/binder to /dev/binderfs/anbox-binder, but it gives an error:

[gbinder] ERROR: Can't open /dev/binder: Permission denied
[23:04:15] Failed to add presence handler: None

I even tried editing /usr/lib/waydroid/tools/helpers/lxc.py, but still no luck

Hi!

I use the linux-cachyos kernel, which has the binder modules. I installed Waydroid, and it is not starting

> sudo waydroid init 

[11:44:35] Already initialized

> ls /dev/
drwxr-xr-x       - root   16 Apr 17:00  binderfs
lrwxrwxrwx      22 root   16 Apr 17:00  features -> /dev/binderfs/features
lrwxrwxrwx      26 root   16 Apr 17:00  anbox-binder -> /dev/binderfs/anbox-binder
lrwxrwxrwx      28 root   16 Apr 17:00  anbox-hwbinder -> /dev/binderfs/anbox-hwbinder
lrwxrwxrwx      29 root   16 Apr 17:00  anbox-vndbinder -> /dev/binderfs/anbox-vndbinder
lrwxrwxrwx      28 root   16 Apr 17:00  binder-control -> /dev/binderfs/binder-control

> sudo ls -1 /dev/binderfs/
anbox-binder
anbox-hwbinder
anbox-vndbinder
binder-control
features

> sudo ls -1 /dev/binder
ls: cannot access '/dev/binder': No such file or directory

> sudo waydroid status
Session:    RUNNING
Container:  STOPPED
Vendor type:    MAINLINE
Session user:   austin(1000)
Wayland display:    wayland-0

> sudo systemctl enable --now waydroid-container

> waydroid session start

[11:36:52] Session is already running

> sudo waydroid container start
ERROR: WayDroid container service is already running

> waydroid show-full-ui
[gbinder] ERROR: Can't open /dev/binder: No such file or directory
[11:37:15] Waiting for binder Service Manager...
[11:38:15] Service Manager never appeared
[11:38:15] Failed to access IPlatform service

Thank you

I have a problem both with the integrated webcam of the laptop and with a webcamm connected to the usb port; the zoom video conferencing app does not detect the webcam, but neither do other programs that use the webcam; What do you think could be the problem? Thanks for your help

@dangerdev well, i have tried that before changing kernels and the like.

i don't have apparmor installed and PSI is default in kernel.

$ zcat /proc/config.gz | grep PSI
CONFIG_PSI=y
# CONFIG_PSI_DEFAULT_DISABLED is not set

for now i downgrade to 1.3.4, it's working again.

i don't know what's wrong because i don't have a way to get more detailed log info.

but, i think it is between waydroid and gbinder not working.