-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Use more recent LineageOS versions #16
Comments
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. |
Source: 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 Output:
repo sync build/make Output:
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
apply-waydroid-patches
matrix-commander '`apply-waydroid-patches` finished!' Have to execute again sudo apt install -y python-is-python3
lunch lineage_waydroid_x86_64-userdebug Output:
|
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
simg2img $OUT/system.img ~/system.img
ls -l ~/system.img
file $OUT/system.img ~/system.img Output:
sha512sum ~/system.img
|
See the end of the comment for download.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
Could try to simg2img $OUT/vendor.img ~/vendor.img
ls -l ~/vendor.img
file $OUT/vendor.img ~/vendor.img Output:
sha512sum ~/vendor.img
Working LineageOS 20 (Android 13) Waydroid image:Archive with both 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 Output:
Could try sudo waydroid init does not produce any output. waydroid show-full-ui Output:
Before applying https://docs.waydro.id/faq/get-waydroid-to-work-through-a-vm. After get:
Running on a host seems to make sense. On Pegasus Debian 12 GNOME get:
Should investigate |
Could compile for 18.1 to check if it works fine. |
Searching the Internet for Failed to add service waydroidusermonitor.
setenforce Output:
|
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. |
|
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 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 Output:
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:
|
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 Output:
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
apply-waydroid-patches
matrix-commander '`apply-waydroid-patches` finished!' With
|
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 Output:
|
@Benjamin-Loison, can you please also build images for arm? |
I've never run Waydroid or build Waydroid images for ARM but I'll investigate that. |
thank you a lot! |
Related to gmankab/waydroid/issues/1. |
Personal notes: https://www.ovhcloud.com/en/bare-metal/prices/ only mentions Intel and AMD, hence not ARM as far as I know DuckDuckGo and Google OVH ARM. Related to ovh/public-cloud-roadmap/issues/343#issue-1533554528. https://community.ovh.com/en/t/so-you-start-arm-storage-servers/1452/2 Always free Oracle VPS is limited to 200 GB of storage which might not be enough according to recommendations of LineageOS, so should look for an alternative, notably as 4 OCPUs and 24 GB of RAM may not be enough. https://docs.waydro.id/usage/install-on-desktops#ubuntu-debian-and-derivatives sudo apt install curl ca-certificates -y Output:
curl -s https://repo.waydro.id | sudo bash Output:
sudo apt install -y waydroid Output:
https://docs.waydro.id/faq/get-waydroid-to-work-through-a-vm may be necessary. waydroid show-full-ui
waydroid init OUtput:
sudo waydroid init Output:
DuckDuckGo https://forum.manjaro.org/t/how-do-i-install-the-binder-linux-module/41931/2 The OS is 24.04 and packages are up-to-date according to APT. uname -r
Maybe using Debian solves the issue. I checked and I do not have a Debian already installed on ARM. Let us create one with account:
No matter the availability domain and Fault domain in Frankfurt have this issue. https://docs.oracle.com/en-us/iaas/Content/FreeTier/freetier_topic-Always_Free_Resources.htm#compute it seems that having 4 OCPUs, 24 GB RAM, ARM instance with 100 GB and 2 instances of AMD with 50 GB of disk each seems free. https://discord.com/channels/@me/1094061921684164608/1296824728794697748 So in theory for an arbitrarily small period of time can have an arbitrarily good configuration? Could ask confirmation to Oracle first. At least with current AMD instance in parallel the maximum number of OCPUs is 41 and amount of RAM GB is 277. Same limits for an account with no instance:
So for OCPUs it is limited freely to 73.17 hours. Would be nice to notice on web interface something like current total number of OCPUs or RAM consumption. https://docs.oracle.com/iaas/Content/Quotas/Concepts/resourcequotas.htm
Source: https://cloud.oracle.com/compute/instances?region=eu-marseille-1 seems to indicate that I can't have more even temporarily. sudo apt install -y binder_linux Output:
Same for waydroid init Output:
Even after waydroid show-full-ui Output:
waydroid log Output:
waydroid/waydroid/issues/1195#issuecomment-1858959470 solves this issue. |
sudo apt install -y weston
weston From terminal in waydroid show-full-ui Output:
|
waydroid log Output:
waydroid logcat
waydroid/waydroid/issues/1576#issuecomment-{2379535684,2399851229} lead to: waydroid show-full-ui Output:
but after a few minutes no window shows up. Maybe running as Same issue when waydroid log Output:
|
@gmankab Can you elaborate on why you are interested in Waydroid for ARM? Are you able to show Waydroid window on Oracle always free ARM VPS (note that as far as I know only Marseille Home region at account creation gives always free ARM CPU architecture VPS)? As described above, I quickly tried on Ubuntu and Debian without luck. |
i posted android 13 guide in my telegram channel, and one of my friends asked about arm - https://t.me/gmankachat/1303710 there are some people using postmarket os on phones in our telegram chat also i plan to buy xiaomi pad 5 and install postmarket os on it about oracle, i have oracle arm server, but i never tried to run waydroid on it if you need people to test some scripts or anything on arm hardware with postmarket os, feel free to ask |
how to use libhoudini on android13 |
@gmankab Can you try running Waydroid on Oracle ARM server? |
@solitudealma waydroid_script does not work? |
only libndk |
i want to run a game, which cant run with libndk |
What is the game @solitudealma? I can't help you further yet but who knows maybe someone will step in or later on I'll have more skills concerning this topic. |
http://a.9game.cn/sdxl |
yes, if you explain how to do it and provide bash commands |
My point is that, as described from #issuecomment-2422208834 to #issuecomment-2423360068, I was not able to run Waydroid on Oracle ARM server. If you are able on your own to make it run, then I can investigate how to build Waydroid LineageOS 20 (Android 13) on ARM. |
i don't really know how to do it |
Then I can't really help much more because it would mean that I'm unable to even test my ARM build. |
@gmankab I contacted on Telegram the person you mentioned in #16 (comment) for further investigation of what this person is able to concerning Waydroid and ARM.
Personal notes: I do not have ARM hardware so I use Oracle Always Free ARM VPS. Are you able to run Waydroid on such VPS? |
@Benjamin-Loison thanks for the Android 13 image, I'm able to use it on SteamOS / Steam Deck by making minor modifications from this repo - https://github.com/ryanrudolfoba/SteamOS-Waydroid-Installer @gmankab thanks for the guide also on how to use the custom image i've used it as a guide in making minor modifications to my script. I've used casualsnek waydroid_script to add libndk, playstore and widevine and it seems to have installed fine - Playstore is working too I'm able to login and download games from the Playstore - However launching games that are ARM fails. In theory it should work since the LIBNDK translation layer is installed but ARM apps close - LIBNDK ARM translation layer works fine on Android 11 as we've been using it for several months now. It seems its only broken when on Android 13. LIBNDK translation layer will be really useful as majority of the apps in the Playstore are ARM based. I'll poke around and between Android 11 and Android 13 and compare if the files needed are getting copied to the right location. If you guys have any other ideas how to troubleshoot this that will be awesome. |
Thanks for the feedback @ryanrudolfoba. I am not comfortable on how libndk works, so won't be able to help you much. Your best luck is to understand how libndk is installed on Android 11 and try to adapt it to Android 13. |
I removed |
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.
+46
Describe the solution you'd like.
Not read.
Describe alternatives you've considered.
Not read.
Additional context
No response
The text was updated successfully, but these errors were encountered: