-
Install anbox-modules-dkms
sudo pacman -S anbox-modules-dkms
-
Reboot
-
Setting up Kernel Modules:
i) To enable module loading at boot, create a file inside /etc/modules-load.d/, which contains the lines:
(sudo nano /etc/modules-load.d/anbox.conf)
/etc/modules-load.d/anbox.conf
ashmem_linux
binder_linux
(Save and exit)
ii) Load Modules: sudo modprobe -a binder-linux ashmem-linux
iii) To enable creating mount point of binderfs at boot, create a file in /etc/tmpfiles.d/ with the content:
(sudo nano /etc/tmpfiles.d/anbox.conf)
/etc/tmpfiles.d/anbox.conf
d! /dev/binderfs 0755 root root
(Save and exit)
iv) Mount binderfs:
sudo mkdir -p /dev/binderfssudo mount -t binder none /dev/binderfs
v) To enable mounting binderfs at boot, add a line in the fstab. The option nofail here will not greet you with a recovery shell when booting a kernel without binderfs support (such as the standard kernel).:
(sudo nano /etc/fstab)
/etc/fstab
none /dev/binderfs binder nofail 0 0
- Setting up Anbox:
i) Install Anbox:
You can install it from Garuda Gamer -> Emulators. It will install Anbox with all necessary dependencies and even Google PlayStore
ii) Configure Networking:
sudo systemctl enable --now systemd-networkd
iii) Enable the Container Manager Service:
sudo systemctl enable --now anbox-container-manager.service
iv) Enable the Session Manager Service:
systemctl --user enable --now anbox-session-manager.service
v) If you want to use adb to debug, install android-tools:
sudo pacman -S android-tools
-
To check modules status
sudo ls -1 /dev/{ashmem,binderfs}
It should give somewhat similar output:
❯ sudo ls -1 /dev/{ashmem,binderfs}
/dev/ashmem
/dev/binderfs:
anbox-binder
anbox-hwbinder
anbox-vndbinder
binder
binder-control
features
hwbinder
vndbinder
[For more details, refer to: Anbox - ArchWiki]
This post is a simplified version of this one: https://forum.garudalinux.org/t/a-little-help-with-anbox/
There you are, enjoy Android Apps in Garuda Linux!
and at this moment I didn't have time to "study" on it a bit ...