Setup (and usage) is non-trivial under Halium 12+
Volla Phone X23 for example comes with Android 12 (and thus the port is based on Halium 12) so the current officially available Android 11 images from https://sourceforge.net/projects/waydroid/files/images/ as a default simply can't work as you cannot use vendor libraries/binaries for a newer Android version on an older Android version.
On the other hand with the images from https://sourceforge.net/projects/aleasto-lineageos/files/LineageOS%2020/waydroid_arm64/ and a bit of messing around on command line it can actually launch:
NOTE: These image come without Google apps, so you'd have to use alternate means to run apps dependent on Google Play services if that's what you're after.
Now to actually set it up:
sudo su
mount -o remount,rw /
mkdir -p {/userdata/system-data,}/etc/waydroid-extra
mount -o bind /userdata/system-data/etc/waydroid-extra /etc/waydroid-extra
mkdir -p /etc/waydroid-extra/images
echo '/etc/waydroid-extra auto persistent none none' >> /etc/system-image/writable-paths
images_url=https://sourceforge.net/projects/aleasto-lineageos/files/LineageOS%2020/waydroid_arm64
wget $images_url/system.img/download -O /etc/waydroid-extra/images/system.img
wget $images_url/vendor.img/download -O /etc/waydroid-extra/images/vendor.img
waydroid init -f
exit # from the root shell as you can't run e.g. "waydroid show-full-ui" as root
You may have to repeat the whole first section (mkdir, mount, writable-paths) of steps after updates. Even after that and tapping on the Waydroid
launcher the graphical interface will not show up and you additionally have to also run waydroid show-full-ui
in the Terminal app (or even twice on adb shell
/ terminal app if more convenient, the important part is it has to be invoked twice); the first boot also can take multiple minutes so be patient.
Sometimes the UI also simply won't work with the following seen in sudo waydroid logcat
:
F DEBUG : Abort message: 'no suitable EGLConfig found, giving up'
In this case sudo waydroid init -f
and retrying to launch should help.