[DISCONTINUED][GSI][9][Reference] LineageOS 16.0 GSI (all archs) and how to build them
- Thread starter AndyYan
- Start date
Voip calls don't work, the ther part can hear me but i can't hear them
(Whatsapp, Jami, Jitsi, Riot, Signal, Wire, anything)
Is this a general issue or is it just here?
(Whatsapp, Jami, Jitsi, Riot, Signal, Wire, anything)
Is this a general issue or is it just here?
G8231 & G8232 XZs crashes/freezes running a/b GSI Lineage & Havoc; freezes on lock screen after first shutdown and reboot, sporadic freezing thereafter. Anyone with tweaks or a fix with the same issue on other devices (tried the appops.xml delete, remanifests after the service is started upon reboot)? Was able to setenforce SELinux (1) to my surprise, nothing to do with the random crashes and freezes. Maybe it's the latest update/build?
LOS GSI builds are not for noobs ... sorry for you guys ! There are a lot of stuff that the end users must complete themselves for their specific vendors : fixing audio, bluetooth, fingerprint, additional permissions, battery offline charger, init, FM Radio, NXP NFC ... etc. You must refere to your stock ROM to achieve these things !
All GSI must be used as a "base" ROM ... and not as a "full" ROM ... That's why it is called "Treble Experimentation" !
Cheers
I just built a LOS 16.0 release with the July 2020 security patch and posted the images here: https://www.androidfilehost.com/?w=files&flid=306989
Nice, but ...
In services.jar (core)
Xiaomi FOD Interface (aka IXiaomiFingerprint) is missing from vendor
facola (FOD icon) is missing in com/android/server/fingerprint
You are using LOS FingerprintInscreen implementation, that had no system/vendor library or permission and no interface link in /bin/rw-system.sh, you should keep the one from AOSP used by phhusson !
Cheers
:good:
In services.jar (core)
Xiaomi FOD Interface (aka IXiaomiFingerprint) is missing from vendor
facola (FOD icon) is missing in com/android/server/fingerprint
You are using LOS FingerprintInscreen implementation, that had no system/vendor library or permission and no interface link in /bin/rw-system.sh, you should keep the one from AOSP used by phhusson !
Cheers
:good:
Magendanz, thank you for the practically up to date GSI of 16. Runs perfect on my Xperia with a few settings adjustments and boot tweaks. Keep up the good work.
Magendanz said:
Great! Thanks for the builds. Are you going to update regularly? Can you compress the files to save download bandwidth in future, please?
No, probably not. I'm dropping support for all my Android 9.0 custom ROMs, and it's not clear to me why anyone would be using LOS 16.0 GSIs at this point now that LOS 17.1 is so stable.
Magendanz said:
Yes, LOS 17.1 is indeed very stable, but on my low-end device it is rather laggy, consuming ~90% RAM just at idle. The difference in performance and responsiveness between 16.0 and 17.1 is substantial, so as much as I want to upgrade, I cannot if I want a usable device. Thanks for your reply, much appreciated, I shall continue to use your last LOS 16.0 build for the foreseeable future.
Wooooow thank you so much!
I'm just setting up a device (BV9100) with @eremitein 's LiR GSI and found it VERY laggy everywhere, a search brought me to your post and boom! Smooth as silk!
Someone outside of XDA informed me that the 16.0 build script is broken, so I hastily synced and fixed it, up to the point where it'll start building, but I didn't actually finish the build, so no image updates.
Man, time flies, the breakage happened early this year and it went unnoticed...
Man, time flies, the breakage happened early this year and it went unnoticed...
No the volte does not work but I am making a package for Huawei. On the other hand, we manage to compile again a Lineage 16
I have a OnePlus Nord N200, I wanna try a few GSIs but I have a question.
What's the difference between bvN and. bgN?
What's the difference between bvN and. bgN?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
83
Background:
We've been offered LOS 16 GSIs in the past (here, and here), but they haven't been updated in quite a while, so as a LineageOS lover, I decided to step up and do it myself. Turns out it wasn't so easy - there were a number of hurdles that prevented it from building properly, booting or being feature-complete. But here I am, having figured out most if not all what's needed, and verified booting on an arm64 ab device I own, I'm ready to share my findings as well as some builds with you.
Disclaimer:
This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
No instructions will be offered. If you're here in this forum, you should know what you're doing.
No guarantees that everything would work. This is a GSI, bugs are bound to happen.
Do not report hardware-related bugs in this thread. I am selfish and only care about getting it running on my device with whatever features I need working. Plus I'm not PHH and can't solve any either.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Compressed as .xz archives - extract first.
Vanilla except for these changes:
- Modifications needed to make it build/boot/feature-complete, see below
- Disabled "vendor mismatch" warning on boot
- Re-enabled lockscreen shortcuts
- Default stretch-to-fullscreen (force apps to render in 18:9)
Extra tip:
If you have a relatively low-end device and experience UI stutters, try this simple build.prop trick (technically a debug property, so use at your own risk). Thanks @SnapTheRipper for bringing it up!
Modifications needed (builders-only):
Now for the juicy part. On top of PHH's already fantastic build script, you'll need these:
device/phh/treble:
- Revert Update lineage.mk for LineageOS 16.0 - add back LOS sepolicy, so that LOS-specific features like Profiles, LiveDisplay, Styles, Trust would work
- Revert exfat fsck/mkfs selinux label - fix a conflict in doing so
- Revert Enable dyanmic image size for GSI - fix building
- Revert tinycompress: Use generated kernel headers - remove dependency on generated kernel headers
- Revert Initial support for in-display fingerprint sensors - use PHH's implementation
- Apply build/soong/Android.bp: Disable generated_kernel_* - disable generating kernel headers, since GSIs don't have a kernel
- Revert lineage: Enforce privapp-permissions whitelist, or change it to log
- Revert cryptfs_hw: Use generated kernel headers - remove dependency on generated kernel headers
- Apply [TEMP]: Header hack to compile for 8974 - fix a missing header
Stuff on GitHub (builders-only):
I've also collected necessary scripts/patches and uploaded them: treble_build_los, treble_patches (PHH's treble_patches adjusted for LOS). Not the cleanest code, but should help if you still need more clues.
Donate?
https://paypal.me/AndyCGYan
Thanks for reading - I hope this could be of use to fellow LineageOS lovers / home builders.24Things are really smooth and flawless! Tested since my latest comment on this thread and no regreats ever since ?
However, background imagens app crashes sometimes (not a big issue, but maybe check that out in the future).
NOTE: I found a really strong solution for the ones who suffer from UI/app stutters like me. It really brings the performance to stock-like level, which is great on a GSI. Kudos to Anton Paulic and Dinolek for this.
You have to paste the following code in your vendor build.prop (to prevent the lost of it during system flashes)
debug.sf.latch_unsignaled=114Updated all variants with September security patches and in sync with PHH v119. [Insert obligatory backup-and-test warning here]
- Now covering all device architectures, including arm-ab, arm_binder64-a, arm_binder64-ab - as shown by the survey, these have very few users and thus weren't thoroughly crowd-tested, but I believe I've done what I can here. I've worked around the privapp permissions so you won't need that whitelist xml from earlier.
- Using PHH's FOD implementation, as stated before
- Minor changes to building process will be synced to GitHub shortly, when I have time
Since I shelled out quite a bit for that SSD, here's a donation link if you like this stuff and want to help me a bit: https://paypal.me/AndyCGYan13A lil teaser - I managed to build and boot LOS 17 based on PHH v200.e. The building flow is largely unchanged, which is a relief. The image itself seems to function okay (I didn't test it in-depth), but LOS 17 upstream is still under development so certain features are missing, and the issues and non-booting samples people report about PHH v20x builds should also apply here.
I might upload a test build for one arch after I clean up the process, but actual release will follow PHH's.
Please keep in mind that PHH v20x is currently pre-release. The best thing to do right now is to try installing those AOSP test builds on your devices and report non-booting/bugs/instabilities to help PHH develop.
