Ultimate Guide to install Waydroid in any Arch-based distro(especially Garuda)

[NaN]

Yeah it is fine.

[alex5402]

so why my waydroid is not working says binder is died

like
this

[NaN]

@alex5402

so why my waydroid is not working says binder is died

like
this

Have you used these two commands first before going for

waydroid show-full-ui

@Austin

i. Start the container first:

sudo waydroid container start

ii. And in a new terminal tab, start the waydroid session (without sudo):

waydroid session start

Does enabling the container service make any difference?

@Austin

6.1 Enable and start the waydroid-container service:

sudo systemctl enable --now waydroid-container

Then launch Waydroid from the applications menu.

[alex5402]

@Austin

sudo waydroid container start

ya already did sir

[Austin]

@NaN

Does enabling the container service make any difference?

It probably starts the container at boot, so you wouldn’t have to do it on every boot.

[Austin]

Currently, linux-xanmod has binder drivers as kernel modules, unlike linux-zen or linux-cachyos with binder inbuilt.

So you need to do some additional steps:

i) You need to enable automatic loading of the modules on boot:

echo binder_linux | sudo tee /etc/modules-load.d/binder.conf

ii) Enable PSI by default:
Add the psi=1 boot parameter to the kernel command line of your boot loader.
(edit /etc/default/grub and add psi=1 to the end of GRUB_CMDLINE_LINUX_DEFAULT, within “” and before any # symbols)

Waydroid works for me with linux-xanmod,

---

Magisk in Waydroid, weirdly/interestingly, works only with linux-xanmod.

As you can see in the screenshot below, Magisk is installed when using linux-xanmod.
You just have to install Magisk Delta through waydroid-extras, and everything is automatically configured (only with linux-xanmod).

You will get all these options in the Magisk Delta app.

You can refer to this for more info/details:

GitHub - nitanmarcel/waydroid-magisk: Magisk Delta manager for Waydroid.

[Austin]

@alex5402 wants to install Magisk, so he is trying to run Waydroid with linux-xanmod.

Alex, did you add psi=1 to the kernel boot parameters, run sudo update-grub and then reboot?

[alex5402]

you can use this GitHub - ALEX5402/libndk_translation_Module: Installs SUPPORT ARM APPS functions into your AVD

this is works well also

[alex5402]

Now i can finally run waydroid properly also i have root access now thanks to Austin

Some extra info you need to know

• If you want to run pubg mobile then you need to install libjni only
• if you want root access on waydroid then don't install binder module
• you need to add psi=1 to your kernel parm from grub
• just install xanmod kernel and do this

• and reboot with xanmod and done

[Austin]

@alex5402

If you want to run pubg mobile then you need to install libndk and libjni both of them

I don’t think that works. This is what I observed
You could confirm it though.

@Austin

If you install both libndk & libhoudini, apps will use the ARM-translation library you last installed(the last one you installed overwrites the previous one), so it is of no use. (That’s what I saw when I tested)

[alex5402]

ya from the prop

[Austin]

New updates and tips:

i)

@Austin

9. To fix unusable rotated apps:

Run this in your normal terminal while Waydroid is running:

sudo waydroid shell wm set-fix-to-user-rotation enabled

ii) I checked out Roblox, and it runs perfectly fine. Even the keyboard works out of the box.

iii) If you can’t find some of your apps in the Play Store, you can probably find them in the Aurora Store.

[Austin]

Hey @dr460nf1r3, could you please compile the linux-xanmod kernel for the chaotic-aur with

CONFIG_ANDROID_BINDER_IPC=y
CONFIG_ANDROID_BINDERFS=y

Instead of this (which it should be right now)

CONFIG_ANDROID_BINDER_IPC=m
CONFIG_ANDROID_BINDERFS=m

Outdated Binder module · Issue #386 · xanmod/linux · GitHub

When binder_linux is compiled with (=y), it becomes a kernel component and will always be loaded in memory every boot. If it is compiled with (=m), it(binder_linux) will become a .ko module object in /lib/modules/.../, which will be loaded only when requested.`

[dr460nf1r3]

@Austin

When binder_linux is compiled with (=y), it becomes a kernel component and will always be loaded in memory every boot. If it is compiled with (=m), it(binder_linux) will become a .ko module object in /lib/modules/.../, which will be loaded only when requested.`

I don’t think this is the behavior we want for binder_linux what prevents us from using the module?

[Austin]

@Austin

So you need to do some additional steps:

i) You need to enable automatic loading of the modules on boot:

echo binder_linux | sudo tee /etc/modules-load.d/binder.conf

ii) Enable PSI by default:
Add the psi=1 boot parameter to the kernel command line of your boot loader.
(edit /etc/default/grub and add psi=1 to the end of GRUB_CMDLINE_LINUX_DEFAULT, within “” and before any # symbols)

Many users are not able to follow these instructions.

Making binder inbuilt like in Cachyos, just makes it seamless.

Let me know any concerns you have.

[dr460nf1r3]

I guess we can try it.

[Austin]

Update:

@Austin

(II) If you are not able to run waydroid(i.e. getting errors) when switching to another linux kernel that has the binder drivers, reinitialize Waydroid:

sudo waydroid init -f
or
sudo waydroid init -s GAPPS -f (If you have a GAPPS image)

The waydroid init -f command initializes Waydroid.
( The -f flag tells Waydroid to force a reset.)

This downloads the latest Android image (if there is an update), sets up the Waydroid configuration file and starts the Waydroid container.

---

@dr460nf1r3

I guess we can try it.

We don’t need it anymore!

It seems that if you first initialize and run Waydroid with a kernel and then later switch to another kernel, you will have to reinitialize Waydroid to work with the later kernel.

@Austin

Currently, linux-xanmod has binder drivers as kernel modules, unlike linux-cachyos with binder inbuilt.

So you need to do some additional steps:

i) You need to enable automatic loading of the modules on boot:

echo binder_linux | sudo tee /etc/modules-load.d/binder.conf

You also don’t have to do this any more.

[dr460nf1r3]

@Austin

It seems that if you first initialize and run Waydroid with a kernel and then later switch to another kernel, you will have to reinitialize Waydroid to work with the later kernel.

Did I understand correctly, waydroid init -f does it for us?

[Austin]

Yup, it points Waydroid towards the loaded binder drivers.

[zany130]

found a workaround for lack of root in kernels other than xanmod (root works fine there as previously mentioned)

you can use shizuku which is replacing su on android

Shizuku

while it is not full root it does give you the adb permissions which on android is more than enough to do 99% of the things you would normaly use root for.

only problem is that normaly you would have to connect through adb and run the start script everytime android boots, but on waydroid you can simpially do this from the terminal

sudo waydroid shell sh /storage/emulated/0/Android/data/moe.shizuku.privileged.api/start.sh

Trying to find a way to automate this so everytime waydroid starts up it automatically runs this