Package Details: waydroid 1.4.2-1

Git Clone URL: https://aur.archlinux.org/waydroid.git (read-only, click to copy)
Package Base: waydroid
Description: A container-based approach to boot a full Android system on a regular Linux system
Upstream URL: https://waydro.id/
Licenses: GPL
Submitter: Danct12
Maintainer: Danct12
Last Packager: Danct12
Votes: 103
Popularity: 6.43
First Submitted: 2021-09-12 03:33 (UTC)
Last Updated: 2023-11-06 19:55 (UTC)

Pinned Comments

Danct12 commented on 2021-09-21 06:23 (UTC) (edited on 2021-10-08 16:06 (UTC) by Danct12)

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:

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

Danct12 commented on 2021-09-30 14:12 (UTC)

@x1unix Clipboard manager isn't really required for Waydroid to start, so I added it to optdepends.

h3x4d3c1m4l commented on 2021-09-28 15:05 (UTC) (edited on 2021-09-28 21:36 (UTC) by h3x4d3c1m4l)

Any hints for internet connection inside the Android system?

I tried this from postmarketOS wiki: echo "/bin/ip route add default via 192.168.250.1" | sudo waydroid shell

But it says it can't find the route. I don't have any kind of firewall enabled at the moment.

EDIT: seems to be fixed after executing the steps from de Anbox wiki page: https://wiki.archlinux.org/title/Anbox#Via_NetworkManager (but substitute anbox by waydroid in both places of the command)

x1unix commented on 2021-09-27 18:45 (UTC)

@Danct12 please add pyclip as dependency (not available in AUR) to pass "Failed to start Clipboard manager service" issue.

jaro3 commented on 2021-09-24 10:34 (UTC)

It just doesn't start on latest Arch:

(014577) [19:31:22] Failed to start Clipboard manager service, check logs (014577) [19:31:27] Clipboard service is not even started (013106) [19:31:27] session manager stopped, stopping container and waiting...

Danct12 commented on 2021-09-24 05:37 (UTC) (edited on 2021-09-24 05:37 (UTC) by Danct12)

You can try to run this command to grep for kernel options required

zcat /proc/config.gz| grep 'ANDROID_BINDER_DEVICES\|ASHMEM'

If it return blank (or your kernel does not support one of the option) then your kernel doesn't work with Waydroid.

Anyway, core/linux (what you're using now) doesn't support Android options.

rado84 commented on 2021-09-23 12:39 (UTC)

How do I found out if the kernel supports binder? It's 5.14.6-arch1-1.

I did what robxu9 said about boot cmdline, rebooted but it keeps returning this eror: Module binder_linux not found I searched the repos for binder_linux but couldn't find any package with that specific name.

robxu9 commented on 2021-09-23 02:47 (UTC)

If you have binderfs (via linux-zen), it usually initialises empty. It looks like waydroid is currently not calling binder-control to automatically set up the devices, so if you're running into:

ERROR: Binder node "binder" for waydroid not found

Append the following to your boot cmdline and restart:

binder.devices=binder,hwbinder,vndbinder,anbox-binder,anbox-hwbinder,anbox-vndbinder

Danct12 commented on 2021-09-21 06:23 (UTC) (edited on 2021-10-08 16:06 (UTC) by Danct12)

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:

« First ‹ Previous 1 2 3 4 5 6 Next › Last »