Could anyone use waydroid with linux-cachyos
kernel?
Search Criteria
Package Details: waydroid 1.4.2-1
Package Actions
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: | 102 |
Popularity: | 6.95 |
First Submitted: | 2021-09-12 03:33 (UTC) |
Last Updated: | 2023-11-06 19:55 (UTC) |
Dependencies (9)
- dbus-python
- dnsmasq (dnsmasq-gitAUR, pi-hole-ftlAUR)
- gtk3 (gtk3-ubuntuAUR, gtk3-no_deadkeys_underlineAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classic-xfceAUR, gtk3-classicAUR)
- lxc (lxc-selinuxAUR, lxc-gitAUR)
- nftables (nftables-gitAUR, nftables-fullconeAUR)
- python-gbinderAUR
- python-gobject (python-gobject-gitAUR)
- git (git-gitAUR) (make)
- python-pyclipAUR (optional) – share clipboard with container
Required by (8)
Sources (1)
Aftermath commented on 2023-05-08 15:22 (UTC)
yuhldr commented on 2023-05-04 04:04 (UTC)
linux-headers
or linux-lts-headers
maybe necessary
austinrojers commented on 2023-04-17 07:16 (UTC)
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
austinrojers commented on 2023-04-16 13:10 (UTC)
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
neuronestanco commented on 2023-04-13 19:44 (UTC)
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
dcryptr commented on 2023-02-27 02:54 (UTC)
@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.
dangerdev commented on 2023-02-26 17:19 (UTC)
@dcryptr try the solution in this thread.
dcryptr commented on 2023-02-26 13:09 (UTC) (edited on 2023-02-26 15:16 (UTC) by dcryptr)
@dangerdev well, i've tried linux-zen. same error messages.
my network is rather down, will edit this comment after trying uninstall / install waydroid.
edit:
nope, nothing works anymore.
reinstall waydroid, changing kernel, reinstall anbox-modules / binder_linux ...
before update, it runs well with linux-lts version 5.* and linux version 6.1.12
but, now the container not even starting properly with this error with dmesg,
[45115.884915] init: SetupMountNamespaces failed: Read-only file system
and this error with waydroid log,
lxc-start: waydroid: ../src/lxc/conf.c: run_buffer: 322 Script exited with status 126
lxc-start: waydroid: ../src/lxc/start.c: lxc_end: 985 Failed to run lxc.hook.post-stop for container "waydroid"
could someone tell me how to get more info / logs ?
dangerdev commented on 2023-02-26 06:00 (UTC) (edited on 2023-02-26 06:05 (UTC) by dangerdev)
@dcryptr Have you tried using the linux-zen kernel ? In archwiki I found this:
Using Linux-Zen
The linux-zen 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.
dcryptr commented on 2023-02-26 01:42 (UTC) (edited on 2023-02-26 02:28 (UTC) by dcryptr)
@C_Schmidpeter it is indeed strange, and after i check dmesg this is the (partial) message with error;
...
[45115.883487] init: Running restorecon...
[45115.883645] init: Created socket '/dev/socket/property_service', mode 666, user 0, group 0
[45115.884915] init: SetupMountNamespaces failed: Read-only file system
[45115.885404] init: InitFatalReboot: signal 6
[45115.890082] init: #00 pc 00000000000e40bd /system/bin/init (android::init::InitFatalReboot(int)+205)
[45115.890090] init: #01 pc 000000000006b4b0 /system/bin/init (android::init::InitAborter(char const*)+32)
[45115.890097] init: #02 pc 0000000000019cfc /system/lib64/libbase.so (android::base::SetAborter(std::__1::function<void (char
const*)>&&)::$_3::__invoke(char const*)+60)
[45115.890103] init: #03 pc 00000000000192a0 /system/lib64/libbase.so (android::base::LogMessage::~LogMessage()+368)
[45115.890108] init: #04 pc 00000000000aed25 /system/bin/init (android::init::SecondStageMain(int, char**)+13653)
[45115.890113] init: #05 pc 000000000003798c /system/bin/init (main+300)
[45115.890117] init: #06 pc 0000000000093bc8 /system/lib64/bootstrap/libc.so (__libc_init+104)
[45115.890121] init: Reboot ending, jumping to kernel
...
things i've tried before: 1. full upgrade system 2. change from anbox-modules-dkms to binder_linux 3. change from linux-lts to linux
well, when i try to change back to anbox-modules-dkms i get fatal error while build. for now i'm using linux-6.1.2 and binder_linux-dkms.
where i can get more debug info so i can get to know what is causing the error?
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
andwaydroid-image
, run this command to initialize the container:Then the container can be started via
waydroid-container.service
. The official project group/channel can be found on: