Finalize custom Android 13 image setup #67
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JamiKettunen
force-pushed
the
custom-api33-final
branch
from
af93200 to
9d7bb5c
Compare
JamiKettunen
changed the title
JamiKettunen
force-pushed
the
custom-api33-final
branch
from
9d7bb5c to
db6b4fc
Compare
JamiKettunen
changed the title
Since waydroid/waydroid@6a0d190 one no longer needs the hacky wrapper script to properly launch it on Halium 12/13 devices; also drop it if found from a previous run.
Since there's still no OTA yet re-use most of the previous custom image setup bits but instead wire them up to download VANILLA/GAPPS lineage-20 images from the official SourceForge for now.
JamiKettunen
force-pushed
the
custom-api33-final
branch
from
4a9ad86 to
c68f0ff
Compare
Now they should no longer stop working on channel switch or OTAs in general, improves perceived stability of Waydroid on Halium 12/13 reducing the need to re-run install action from Waydroid Helper just to previously setup the bind-mount again without even downloading anything :)
JamiKettunen
force-pushed
the
custom-api33-final
branch
from
c68f0ff to
3ff723a
Compare
maciek134
approved these changes
Jun 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since Waydroid 1.5.0 (waydroid/waydroid@6a0d190) one no longer needs the hacky wrapper script to properly launch it on Halium 12/13 devices; drop it starting with 20.04 OTA-9 which also introduces proper A13 support in the form of https://gitlab.com/ubports/development/core/packaging/waydroid/-/merge_requests/22 which should improve stability and fixes various things depending on the service manager binder being functional.
I'm still having to sometimesthis was fixed by https://gitlab.com/ubports/development/core/packaging/waydroid/-/merge_requests/23sudo systemctl restart waydroid-containerto get it starting again which is rather strange..I've since originally creating the PR also switched
waydroid-custom-initover to using the officiallineage-20VANILLA/GAPPS system andHALIUM_13vendor zips from https://sourceforge.net/projects/waydroid/files/images/ that further fix some known unstabilities with the previous now GAPPS-only images as well as reduce the required download size back to normal.Last but not least finally move the custom image location over from
/etc/waydroid-extra/imagesto just the usual/var/lib/waydroid/imageswith some config trickery; while the old images could be preserved (moved over) I hardly think it's worth it as per the above considering there's no proper way to do this update either then without manually doing an uninstall + install again.