Open Benjamin-Loison opened 8 months ago
Concerning the comment about explaining how to try on our own a more recent LineageOS version, see waydroid/issues/1337#issuecomment-2049517200, it is unclear what wiki the person is referring to, as the repository does not have a wiki which would otherwise be at waydroid/wiki.
https://waydro.id seems to mostly redirect to https://docs.waydro.id/, see https://waydro.id/#docs.
The Android runtime environment ships with a minimal customized Android system image based on the LineageOS. The used image is currently based on Android 11.
Source: https://docs.waydro.id
May help:
https://docs.waydro.id/faq/using-custom-waydroid-images:
as Waydroid does not seem to propose alternative newer LineageOS images, have to investigate the following link:
https://docs.waydro.id/development/compile-waydroid-lineage-os-based-images
lineage_waydroid_x86_64-userdebug
seems to be the Waydroid AOSP Lunch Option we are interested in, see https://docs.waydro.id/development/compile-waydroid-lineage-os-based-images#waydroid-aosp-lunch-optionshttps://docs.waydro.id/development/compile-waydroid-using-android-generic-project: https://sourceforge.net/projects/waydroid/files/images/ only lists LineageOS images, right? So we are obliged to compile just to test? Let us keep focusing on LineageOS for the moment as it meets quite much my needs.
Virtual machine, see https://docs.waydro.id/faq/get-waydroid-to-work-through-a-vm.
Otherwise there does not seem to be any interesting resource on https://docs.waydro.id.
Related to #38.
I guess that the downloaded LineageOS update is not somehow partially executed without Waydroid start but maybe not updating it except if I use the outdated LineageOS Waydroid makes sense.
Only using Waydroid in a virtual machine may make sense.
Related to Benjamin-Loison/android/issues/62.
Once solved, consider Umay (I delete old snapshots).
# Source: https://narkive.com/QFd5Huo9.2
git config --global color.ui true
repo init -u https://github.com/LineageOS/android.git -b lineage-20.0 --git-lfs
repo sync build/make
wget -O - https://github.com/waydroid/android_vendor_waydroid/raw/lineage-20/manifest_scripts/generate-manifest.sh | bash
https://wiki.lineageos.org/devices/FP4/build/#download-the-source-code
time repo sync -j $(nproc --all)
matrix-commander '`repo sync` finished!'
Related to Benjamin_Loison/openssh/issues/6.
. build/envsetup.sh
including vendor/extra/vendorsetup.sh
apply-waydroid-patches
matrix-commander '`apply-waydroid-patches` finished!'
Have to execute again . build/envsetup.sh
?? See https://docs.waydro.id/development/compile-waydroid-lineage-os-based-images#waydroid-build-commands and https://matrix.to/#/!rLTECBThFGLDQRuPIg:connolly.tech/$81Twx5vP3n2CKCrvrTHWYjulMn14qxEUbc74tWG0h8k.
sudo apt install -y python-is-python3
lunch lineage_waydroid_x86_64-userdebug
Could investigate https://wiki.lineageos.org/devices/FP4/build/#turn-on-caching-to-speed-up-build.
sudo apt install -y libncurses5 zip
make systemimage -j$(nproc --all)
matrix-commander 'Make finished!'
Git LFS is necessary.
ls -l $OUT/system.img
-rw-r--r-- 1 debian debian 754659500 Jul 12 19:01 /home/debian/out/target/product/waydroid_x86_64/system.img
simg2img $OUT/system.img ~/system.img
ls -l ~/system.img
-rw-r--r-- 1 debian debian 754659328 Jul 12 19:09 /home/debian/system.img
file $OUT/system.img ~/system.img
sha512sum ~/system.img
d6f5f104b8718112422a8d1faaacfd5b9746324875c536b10f70e4d2b68701b0cf5ae78750659f5e135cd8fa138377611d07fa452c8339c9e7a374c22d9762d1 /home/debian/system.img
sudo apt install -y meson glslang-tools pkg-config python3-mako byacc flex
make vendorimage -j$(nproc --all)
matrix-commander 'Make finished!'
ls -l $OUT/vendor.img
-rw-r--r-- 1 debian debian 159273024 Jul 12 19:42 /home/debian/out/target/product/waydroid_x86_64/vendor.img
Could try to waydroid show-full-ui
or sudo waydroid init
if necessary, see below, despite not running simg2img
.
simg2img $OUT/vendor.img ~/vendor.img
ls -l ~/vendor.img
-rw-r--r-- 1 debian debian 159272960 Jul 12 19:45 /home/debian/vendor.img
file $OUT/vendor.img ~/vendor.img
sha512sum ~/vendor.img
8a762bef4919333229df47ae16677619b49e154ed52f5ecfe0d06ec429bceb9353cee142d47ccdc4085122d6e3166bb493567ef137737da95f50a73734e90e86 vendor.img
Archive with both .img
s.
https://www.mediafire.com/file/ogg607lky6say0h/archive.7z/file
Password: i4yUhPaS4dSy3tb4h42T7Lcy7gdxzwDEamyyP3
Build mentioned publicly at https://matrix.to/#/!rLTECBThFGLDQRuPIg:connolly.tech/$Eu9p_h-Ev9n7enq6Sa7qjPFrwnGtTy3hXFEgB8IFnb4.
On Debian 12 GNOME VirtualBox virtual machine:
sudo mkdir -p /etc/waydroid-extra/images/
sudo mv {system,vendor}.img /etc/waydroid-extra/images/
waydroid init -h
Could try waydroid show-full-ui
at this stage.
sudo waydroid init
does not produce any output.
waydroid show-full-ui
Before applying https://docs.waydro.id/faq/get-waydroid-to-work-through-a-vm.
Running on a host seems to make sense.
Should investigate waydroid log
.
Could compile for 18.1 to check if it works fine.
Searching the Internet for Failed to add service waydroidusermonitor.
/etc/gbinder.d/
setenforce
Look at waydroid/issues/new?assignees=&labels=&projects=&template=bug_report.yml&title=%5BBUG%5D to see what debugging is recommended.
Thanks to Benjamin-Loison/waydroid/issues/19 testing on my Linux Mint 21.3 Cinnamon Framework 13 could make sense. However, should make sure not to lose data/setup.
/var/lib/waydroid/waydroid.log
:(321564) [01:12:59] Starting waydroid session (321564) [01:12:59] WAYLAND_DISPLAY is not set, defaulting to "wayland-0" (319625) [01:12:59] % /usr/lib/waydroid/data/scripts/waydroid-net.sh start vnic is waydroid0 (319625) [01:12:59] % systemctl is-active -q nfcd (319625) [01:12:59] % chmod 777 -R /dev/dri (319625) [01:12:59] % mv /var/lib/waydroid/config_session /var/lib/waydroid/lxc/waydroid (319625) [01:12:59] % mount -o ro /etc/waydroid-extra/images/system.img /var/lib/waydroid/rootfs (319625) [01:12:59] % mount -t overlay -o ro,lowerdir=/var/lib/waydroid/overlay:/var/lib/waydroid/rootfs,upperdir=/var/lib/waydroid/overlay_rw/system,workdir=/var/lib/waydroid/overlay_work/system,xino=off overlay /var/lib/waydroid/rootfs (319625) [01:12:59] % mount -o ro /etc/waydroid-extra/images/vendor.img /var/lib/waydroid/rootfs/vendor (319625) [01:12:59] % mount -t overlay -o ro,lowerdir=/var/lib/waydroid/overlay/vendor:/var/lib/waydroid/rootfs/vendor,upperdir=/var/lib/waydroid/overlay_rw/vendor,workdir=/var/lib/waydroid/overlay_work/vendor,xino=off overlay /var/lib/waydroid/rootfs/vendor (319625) [01:12:59] % mount -o bind /var/lib/waydroid/waydroid.prop /var/lib/waydroid/rootfs/vendor/waydroid.prop (319625) [01:12:59] Save config: /var/lib/waydroid/waydroid.cfg (319625) [01:12:59] % lxc-start -P /var/lib/waydroid/lxc -F -n waydroid -- /init (319625) [01:12:59] New background process: pid=321637, output=background (319625) [01:12:59] % lxc-info -P /var/lib/waydroid/lxc -n waydroid -sH RUNNING (321564) [01:12:59] Skipping clipboard manager service because of missing pyclip package (319625) [01:12:59] Failed to add service waydroidhardware: -2147483647 (319625) [01:12:59] Failed to add service waydroidhardware: -2147483647 (321564) [01:12:59] Failed to add service waydroidusermonitor: -2147483647 (321564) [01:12:59] Failed to add service waydroidusermonitor: -2147483647```
sudo waydroid shell -- logcat -h
Should search error in compilation logs and pay attention to have complete ones.
waydroid_script mentions Android 13.
Source: waydroid/issues/563
waydroid_script: 1.5k stars waydroid: 7.3k stars
git clone --depth 1 https://github.com/casualsnek/waydroid_script
cd waydroid_script/
sudo apt install -y python3.11-venv
python3 -m venv venv
venv/bin/pip install -r requirements.txt
sudo venv/bin/python3 main.py
So it is assuming that we achieved to install somehow Android 13?
Searching Android 13 in opened and closed issues leads to the more or less interesting:
Just testing official images:
https://freefr.dl.sourceforge.net/project/waydroid/images/system/lineage/waydroid_x86_64/lineage-18.1-20240706-VANILLA-waydroid_x86_64-system.zip https://altushost-swe.dl.sourceforge.net/project/waydroid/images/vendor/waydroid_x86_64/lineage-18.1-20240709-MAINLINE-waydroid_x86_64-vendor.zip
work fine.
Trying to compile LineageOS 18.1:
Based on https://wiki.lineageos.org/devices/FP4/build/, no instruction differ in theory.
git config --global color.ui true
repo init -u https://github.com/LineageOS/android.git -b lineage-18.1 --git-lfs
repo sync build/make
wget -O - https://github.com/waydroid/android_vendor_waydroid/raw/lineage-18.1/manifest_scripts/generate-manifest.sh | bash
time repo sync -j$(nproc --all)
matrix-commander '`repo sync` finished!'
. build/envsetup.sh
including vendor/extra/vendorsetup.sh
apply-waydroid-patches
matrix-commander '`apply-waydroid-patches` finished!'
git-lfs
:Have to execute again . build/envsetup.sh
??
sudo apt install -y python-is-python3
lunch lineage_waydroid_x86_64-userdebug
sudo apt install -y libncurses5 zip
make systemimage -j$(nproc --all)
matrix-commander 'Make finished!'
Related to Improve_websites_thanks_to_open_source/issues/798.
ls -l $OUT/system.img
-rw-r--r-- 1 debian debian 1724445264 Jul 13 03:23 /home/debian/out/target/product/waydroid_x86_64/system.img
simg2img $OUT/system.img ~/system.img
ls -l ~/system.img
-rw-r--r-- 1 debian debian 3547480064 Jul 13 03:25 /home/debian/system.img
sha512sum ~/system.img
d17befbcad7b9230ee23f5846100196a0f2770206ca45f427365d17b86b80b656ff4bbc7c0917d1c3b28e2c8df951ff6faa7ebf16de012f0be19ad87cceb7ad4 /home/debian/system.img
sudo apt install -y meson glslang-tools pkg-config python3-mako byacc flex
make vendorimage -j$(nproc --all)
matrix-commander 'Make finished!'
sudo apt install -y meson
sudo apt install -y glslang-tools
sudo apt install -y pkg-config
sudo apt install -y python3-mako
sudo apt install -y byacc
sudo apt install -y flex
ls -l $OUT/vendor.img
-rw-r--r-- 1 debian debian 519426340 Jul 13 03:50 /home/debian/out/target/product/waydroid_x86_64/vendor.img
simg2img $OUT/vendor.img ~/vendor.img
ls -l ~/vendor.img
-rw-r--r-- 1 debian debian 1547481088 Jul 13 03:52 /home/debian/vendor.img
sha512sum ~/vendor.img
74bc9c79e0af436bb1dd4279dc1b994326fba3291e2574bc3df7cfa73f2890b2704f74e83385eb67c28deec4eb9be1ae3c93b1c510604ed68bcf2596ab0fbd0c /home/debian/vendor.img
sudo mv {system,vendor}.img /etc/waydroid-extra/images/
sudo waydroid init -f
waydroid show-full-ui
It works for LineageOS 18.1.
Maybe should retry from scratch to build LineageOS 20 or test on most recent Ubuntu LTS to oldest recommended one.
Archive with both .img
s.
https://www.mediafire.com/file/e2sgah5qlkj9lpg/archive.7z/file
Password: Lyf4xrEhNDQhRQZXAd3Mmrn5DkDxev9pcv7hs9
Still the same issue (nothing appears in Weston on Pegasus Debian 12 GNOME) from scratch after 1:37:13 on LineageOS 20:
waydroid show-full-ui
Could also test Mutter (https://docs.waydro.id/faq/color-correction-in-mutter).
sudo apt update
sudo apt upgrade -y
sudo apt autoremove -y
ip a
sudo apt install openssh-server
sudo service ssh start
echo 'ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEomyoGWAGCMrc3sb2Vie7lVkMy5NBWvfWxAH/bqGeSw benjamin@benjamin-loison-framework' >> ~/.ssh/authorized_keys
ssh-keygen -t ed25519 -lf <(ssh-keyscan -t ed25519 localhost 2>/dev/null)
curl https://repo.waydro.id | sudo bash
sudo apt install waydroid -y
sudo mkdir -p /etc/waydroid-extra/images/
sudo mv {system,vendor}.img /etc/waydroid-extra/images/
sudo waydroid init
waydroid show-full-ui
As root
:
waydroid init
/usr/lib/command-not-found --ignore-installed modprobe
bash: /usr/lib/command-not-found: No such file or directory
/usr/lib/command-not-found --ignore-installed modprobe
Could not find command-not-found database. Run 'sudo apt update' to populate it.
modprobe: command not found
/usr/lib/command-not-found --ignore-installed modprobe
sudo apt install -y kmod
Just not being root
but using sudo
solves the issue.
Should investigate adb logcat
and Waydroid logs.
Should monitor:
https://github.com/waydroid/android_hardware_waydroid/tree/lineage-20 https://github.com/waydroid/android_vendor_waydroid/tree/lineage-20 https://github.com/waydroid/android_device_waydroid_waydroid/tree/lineage-20
Last commits on those were at least 2 months ago, except if elsewhere but I believe the security patches version is hardcoded somewhere but where? Maybe first knowing where it is in LineageOS source code would make it clearer.
On my Fairphone 4 LineageOS System updates > Show changelog redirects to https://download.lineageos.org/devices/FP4/changes.
https://github.com/LineageOS/android_vendor_lineage/commits/lineage-21.0/vars/common lists previous security patches quite well. LineageOS team takes between 3 days to 20 days it seems.
Last one being:
from
https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/396644 using GitHub link
No vars/
folder in https://github.com/waydroid/android_vendor_waydroid/tree/lineage-20 contrarily to https://github.com/LineageOS/android_vendor_lineage/tree/lineage-21.0. Same for:
REPOS=(android_hardware_waydroid android_vendor_waydroid android_device_waydroid_waydroid)
for repo in "${REPOS[@]}"
do
git clone --depth 1 -b lineage-20 git@github.com:waydroid/$repo
done
find -name 'vars' -o -name 'common'
does not return anything.
Should consider recompiling if changed since last compilation or if there is new Android security patches.
Wikipedia: Android version history (1240587718) security occurrences only lead to the potentially relevant:
https://source.android.com/docs/security/bulletin
https://source.android.com/docs/security/bulletin/2024-08-01 https://source.android.com/docs/security/bulletin/2015-08-01
Currently https://source.android.com/docs/security/bulletin/2024-09-01 leads to Sorry, we couldn't find that page..
Force stop and:
waydroid session stop
sudo waydroid container stop
does not help.
Additional settings in the app crashes in a few seconds it seems:
Unrestricted does not seem to help.
Clear cache and Clear storage do not seem to help.
Get future Android security update date and potentially rebuild each month may make sense. Can leverage caching. Pay attention to bandwidth speed as it seems possibly quite limiting.
Could consider:
So still have to use outdated image for GAPPS, see #42.
Wikipedia: Version history (1239020550) does not mention any planned maintenance end for LineageOS 20. Should monitor when it is outdated. Same for Android 13 at Wikipedia: Android version history#Overview (1240587718).
Should test with GitHub Waydroid.
https://docs.waydro.id/usage/install-on-desktops#reinstalling-waydroid
sudo apt install -y git
git clone --depth 1 https://github.com/waydroid/waydroid
sudo ./waydroid.py init
sudo ./waydroid.py container start
Even above with just running waydroid show-full-ui
with APT package does not help.
Should try opening app manually.
https://docs.waydro.id/usage/install-and-run-android-applications
wget 'https://f-droid.org/F-Droid.apk'
waydroid app install F-Droid.apk
It seems sometimes to crash, but maybe it is only a feeling due to multiple windows, but I am able to update F-Droid from itself, install Aurora Store from F-Droid and install and run Element from Aurora Store with Anonymous authentication. Even if on another application, regularly have Trebuchet keeps stopping prompt.
Related to Benjamin_Loison/AuroraStore/issues/1.
Unable to run Waydroid LineageOS 20 on my Debian 12 GNOME Pegasus despite using:
weston --socket=wayland-0
waydroid show-full-ui
Should investigate what makes me move to X11 and how to revert.
What about Linux Mint 22 Cinnamon Framework 13 with Waydroid session?
On X11 I did:
https://docs.waydro.id/usage/install-on-desktops#reinstalling-waydroid
sudo apt install waydroid -y
sudo mkdir -p /etc/waydroid-extra/images/
sudo mv {system,vendor}.img /etc/waydroid-extra/images/
sudo waydroid init
On Waydroid session:
waydroid show-full-ui
works fine.
On X11 session:
weston --socket=waydroid_socket
WAYLAND_DISPLAY=waydroid_socket waydroid show-full-ui
also works fine.
So no Trebuchet issue in both cases.
In Linux Mint 22 Cinnamon Framework 13 VirtualBox virtual machine Linux Mint (trust):
Proceed to https://docs.waydro.id/faq/get-waydroid-to-work-through-a-vm between sudo waydroid init
and waydroid show-full-ui
.
Related to Benjamin-Loison/cinnamon/issues/74.
Does not show any window anyway.
Same issue for X11 with weston
.
Deepen Failed to add service waydroidusermonitor: -2147483647.
If change binder_protocol = aidl3
to binder_protocol = aidl4
and then waydroid show-full-ui
, then it reverts this change.
Probably AIDL refers to https://developer.android.com/develop/background-work/services/aidl.
Wikipedia: Interface description language#Examples (1232599078)
waydroid --version
1.4.2
Other branches do not look interesting, see branches/all.
The latest tag seems to be 1.4.2, see tags and releases/tag/1.4.2.
which waydroid
/usr/bin/waydroid
/usr/bin/waydroid
:This looks like blob/068a143be99bf57fe649395ad9d95ef966fc49d8/waydroid.py.
So just running the repository waydroid.py
instead of waydroid
may do the job.
https://docs.waydro.id/usage/install-on-desktops#reinstalling-waydroid
./waydroid.py init -f
sudo apt install python3-gbinder
./waydroid.py init -f
./waydroid.py init -h
sudo ./waydroid.py init -f
sudo apt install -y lxc
sudo ./waydroid.py init -f
seems to have completed silently.
./waydroid.py show-full-ui
https://docs.waydro.id/usage/install-on-desktops#manually-starting-waydroid
./waydroid.py container start
sudo ./waydroid.py container start
https://github.com/waydroid/waydroid/issues/854 https://github.com/waydroid/waydroid/issues/1281 https://github.com/waydroid/waydroid/issues/1046
do not help us much.
/etc/dbus-1/system.d/waydroid.conf
contain:Source: discussions/681#discussion-4736097
sudo ./waydroid.py container start
does not return.
./waydroid.py show-full-ui
Restarting does not help.
https://github.com/waydroid/waydroid/issues/854#issuecomment-1568921312 does not seem to help me.
Interestingly, the command sudo systemctl enable --now waydroid-container runs fine under X11, but not wayland.
Source: https://github.com/waydroid/waydroid/issues/854#issue-1672284502
On Pegasus Debian 12 GNOME host using X11, see Benjamin_Loison/Debian/issues/53:
./waydroid.py init -f
sudo apt install python3-dbus
sudo apt install libdbus-1-dev
pip install dbus-python
./waydroid.py init -f
sudo apt install python3-gbinder
Still facing No module named 'gbinder'.
sudo ./waydroid.py init -f
sudo apt install -y lxc
sudo ./waydroid.py container start
After modifying /etc/dbus-1/system.d/waydroid.conf
:
sudo ./waydroid.py container start
does not return.
./waydroid.py show-full-ui
apt show python3-gbinder
sudo ./waydroid.py show-full-ui
sudo weston
sudo weston --socket=wayland-0
pip install gbinder
https://pypi.org/search/?q=gbinder does not return any result.
Note that on Debian I use a default virtual environment, maybe not using it in this context may help.
pip -V
pip 24.1.2 from /home/benjamin_loison/venv/lib/python3.11/site-packages/pip (python 3.11)
deactivate
pip -V
pip 23.0.1 from /usr/lib/python3/dist-packages/pip (python 3.11)
./waydroid.py show-full-ui
sudo ./waydroid.py show-full-ui
So facing the same issues as before.
"org.freedesktop.DBus.Error.AccessDenied" "waydroid" does not return additional interesting results on DuckDuckGo and Google.
Searching 20 in opened and closed issues does not seem to help.
Should investigate:
.zip
sSo it does not even seem clear that I used HALIUM.
Could check that both .img
s are actually necessary.
Search and maybe ask on a Waydroid discussion room.
waydroid/blob/068a143be99bf57fe649395ad9d95ef966fc49d8/README.md?plain=1#L26-L29 https://waydro.id/#contact
Could investigate https://github.com/waydroid/waydroid/issues/922#issuecomment-1562801108 images.
https://matrix.to/#/!rLTECBThFGLDQRuPIg:connolly.tech/$CTyFNq2Jp5xU5bUB2mxSFoD6nEqyun56-bsflJFKdCo service
usage may be interesting.
Related to Benjamin_Loison/Telegram/issues/1.
Instead of host Debian 12 GNOME, could try with Ubuntu and Mint too.
Still on Pegasus Debian 12 GNOME Virtual Machine Manager Debian (trust) for https://t.me/WayDroid/143191 (note that this person sent a message a few minutes ago, see https://matrix.to/#/!rLTECBThFGLDQRuPIg:connolly.tech/$-Wu1O3VhTPFR1UqGnHOx3zrKKQPi0c9RPxO2kRnzvO4, so he's still around):
waydroid show-full-ui
Without any window while I verified that Wayland is supported and followed https://docs.waydro.id/faq/get-waydroid-to-work-through-a-vm.
I should try with a Debian 12 GNOME live USB on Pegasus and pay attention to verify that the live USB key has not been altered.
Should search waydroidusermonitor
in chat rooms and source code.
Maybe a bit blocking tracker/issues/46.
Could monitor https://sourceforge.net/projects/waydroid/files/images/system/lineage/waydroid_x86_64/ if a more recent LineageOS version is published.
I deployed on OverClock3000:
/home/benjamin/notifications/notifyOnRSSUpdate.py
:Alternatively could use {system,vendor}_ota
/var/lib/waydroid/waydroid.cfg
. However, current RSS approach seems to be more precise as it is necessary before those JSON updates.
If I remember correctly have to test on Debian 12 GNOME Pegasus (hence host) to have a Wayland not in a Virtual Machine Manager virtual machine possibly suffering some kind of https://docs.waydro.id/faq/get-waydroid-to-work-through-a-vm, see #issuecomment-2230872734.
Related to #47.
sudo waydroid upgrade
[19:57:43] Upgrade refused because Waydroid was configured to load pre-installed image from /etc/waydroid-extra/images.
ls /etc/waydroid-extra/images/
system.img vendor.img
sudo rm /etc/waydroid-extra/images/{system,vendor}.img
sudo waydroid init -f
Related to Benjamin_Loison/seedvault/issues/7.
Working LineageOS 20 (Android 13) Waydroid image at #issuecomment-2226210183
Is your feature request related to a problem? Please describe.
Notably to have accessibility menu to emulate power button, cf my Android Stack Exchange comment.
LineageOS 18.1 is no more supported since March 5, 2024, see Wikipedia: LineageOS#Version_history (1225763680). According to this source, LineageOS 18.1 is based on Android 11. According to Wikipedia: Android version history#Overview (1232781455), Android 11 is not supported since March 1, 2024. So what are the downloadable updates made of, only patches for Waydroid? I stopped reading recent closed issues at 23/05/23. Related to waydroid/issues/{922,456,563,390}
As a comparison I currently have on my Fairphone 4 Lineage OS 21 using Android 14.
Related to waydroid/issues/1337. I checked the title of all opened issues since LineageOS 18.1 is no more supported that is March 5, 2024, see Wikipedia: LineageOS#Version_history (1225763680) and it seems to be the only related issue.
+45
Describe the solution you'd like.
Not read.
Describe alternatives you've considered.
Not read.
Additional context
No response