[DISCONTINUED][GSI][10] LineageOS 17.x GSI (all archs) - Treble-Enabled Device Development A/AB ROMS

[DISCONTINUED][GSI][10] LineageOS 17.x GSI (all archs) - Treble-Enabled Device Development A/AB ROMS

Reserved
Couple of things to note:
Even on a device that runs Pie GSIs nicely, it's still possible to get broken media, camera, RIL or even flat-out no-boot on Android 10 ones. You are strongly advised to try PHH's AOSP first and identify/report issues there, before moving onto other GSIs that are based on his work. Please report bugs here only if it's specific to this GSI.
LineageOS 17.x has lost some features in the process of transitioning to Android 10, e.g. Privacy Guard and built-in SU.
If using Magisk on an A-only device, a modified Magisk is required.
exfat SD cards still don't seem to work. Any help related to this would be appreciated.
The feature "Re-enabled lockscreen shortcuts by default" has been dropped - not that it can't be done, but Google again made ugly changes to the lockscreen, and with the shortcuts turned on it looks asymmetric and adds to the ugliness. Lockscreen shortcuts themselves might still come back with a future upstream update, just like how it did in 16.0.
In the 16.0 GSIs I've included changes that allow for automatic front camera actions for Xiaomi Redmi K20 Pro, but these have to be reworked for Android 10, and I'm not interested in doing so (in fact I prefer manual controls). Consider these changes abandoned for now.

Initial builds are based on PHH v204 and November security patches.
Building-related bits will be published when I have more time to clean them up.
EDIT: Due to some missing bits in LOS, the fix from v204 failed to apply. If you are having camera issue specific to this GSI, refer to this post for a temporary fix. Won't make a separate batch of builds just for this one issue.

Warm welcome. :fingers-crossed:

:good:

:good:

Redmi S2 YSL - 8.1 Oreo custom vendor Arm64
stock camera / open camera. /Gcam X
lock screen / FP X
viper4android. ✓

Thanks for this Rom
is it with or wirhout Gapps ?

Any mirrors?, sourceforge is a mess to download from.

Nice work ?

hasni2005 said:
Thanks for this Rom
is it with or wirhout Gapps ?
Click to expand...
Click to collapse
without
look, it have small size. with gapps rom around twice bigger

Hey OP, thanks for this. Just curious what devices you've tested this on?

MishaalRahman said:
Hey OP, thanks for this. Just curious what devices you've tested this on?
Click to expand...
Click to collapse
See my signature

Thanks great work i have at the moment bugs
The recents not working and the battery indicator and camera is not working
Galaxy J710FN

Using ZTE Axon 7.
None of the camera apps work and fingerprint doesnt work. Other than that seems pretty okay for now.

@AndyYan hello
i tried your fresh Los17 arm64ab build on the Mi A2 Lite
and faced with big issue - camera not works at all
and screen recorder, and torch
tried opencamera too
but it works in the AOSP v204 and Havoc 3.0 GSI

Congrads to OP, arm Aonly build working well in moto g6 xt1925-6. Used magisk phh 19.3 to root. Seems very smooth, no noticeable lag and ambient display is bright and easy to see when phone is picked up. Very nice. Cheers

eremitein said:
@AndyYan hello
i tried your fresh Los17 arm64ab build on the Mi A2 Lite
and faced with big issue - camera not works at all
and screen recorder, and torch
tried opencamera too
but it works in the AOSP v204 and Havoc 3.0 GSI
Click to expand...
Click to collapse
Seems the problem lies here:
Code:
02-04 19:00:13.397 827 827 E vndksupport: Could not load /vendor/lib/hw/camera.msm8953.so from default namespace: dlopen failed: library "libnativeloader.so" not found.
02-04 19:00:13.398 827 827 E HAL : load: module=/vendor/lib/hw/camera.msm8953.so
02-04 19:00:13.398 827 827 E HAL : unknown
02-04 19:00:13.398 827 827 E [email protected]: Could not load camera HAL module: -22 (Invalid argument)
However I'm pretty sure this has been fixed by v204 already, which I did include (it fixed FP on one of my devices). Are you really using the 1117 build? If yes I'll consult PHH about it.
(I reckon you're in the Telegram group as well?)

AndyYan said:
However I'm pretty sure this has been fixed by v204 already, which I did include (it fixed FP on one of my devices). Are you really using the 1117 build? If yes I'll consult PHH about it.
(I reckon you're in the Telegram group as well?)
Click to expand...
Click to collapse
yes, I'm sure it is 1117 build and I used same base for test. right now I'm on Havoc 3 by ExpressLuke and camera works fine
i like high speed of this los build, it's like a rocket:laugh:
please, fix this bug)) I'm in phh group too, and can test quick fixes if need (@eternityson)

eremitein said:
yes, I'm sure it is 1117 build and I used same base for test. right now I'm on Havoc 3 by ExpressLuke and camera works fine
i like high speed of this los build, it's like a rocket:laugh:
please, fix this bug)) I'm in phh group too, and can test quick fixes if need (@eternityson)
Click to expand...
Click to collapse
You're likely right - I just checked the only Oreo vendor device I own and I'm seeing libnativeloader-related errors in log as well. Camera doesn't work on this device even on AOSP v204 so I assumed they were bugging out for the same reason; looks like that's not the case. Good thing I still have at least this Oreo vendor device on hand - this libnativeloader problem (and the corresponding fix in v204) was said to only target Oreo vendors.
I'll do some tests and/or consult PHH - the fix might not be immediate so if you need your phone don't hesitate to switch to other ROMs.

Related

[ROM][UNOFFICIAL][dumpling] LineageOS 15.1 [AOSP][8.1][16 FEB]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's special about my build:
Sometimes I pick a few patches from the Lineage Gerrit before they are approved and merged into our trees.
The kernel is based on Lineage's one, but I have upstreamed with the latest patches from linux-stable, added a few things such as performance and battery tweaks, security and stability fixes, SafetyNet spoofing, additional kernel controls.... This kind of things
The device trees will also be improved overtime with various improvements from mixed sources (for example better presets, different HAL solutions and so on).
All the rest is kept as recommended in the maintainer's manifest (including the optional patches).
What's working:
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
NFC
Camera
Video Playback
Audio (Record and Playback)
Fingerprint (with gestures)
Sensors
Flash
Notification LED
SELinux
SafetyNet
What's not working:
VoLTE calls are currently not working
With February security patches, TWRP is unable to decrypt data. The only way to be able to access it is removing any lockscreen PIN or password before entering recovery. This will be addressed by the TWRP guys soon.
Instructions:
Before instaling, make sure you are running the latest Open Beta 3 firmware.
If you are unencrypted take a full backup of all your data, because this ROM enforces encryption and so you will have to format your phone.
If you are encrypted and running an AOSP ROM (8.0 or newer) you're fine. If you come from OOS (both Nougat and Oreo) take a full backup of all your data as there's currently not way to change masterkey without formatting, sorry you should be able to go ahead and flash without formatting the internal storage, just make sure to remove any screen lock before switching ROM.
Download the latest build and GApps (both links are below).
Reboot to a custom recovery (latest unified codeworkx's build works perfectly and supports masterkey3 encryption).
If you are coming from any other ROM (even LineageOS 15.0 or 15.1) wiping /data is strongly recommended
Flash the latest build and GApps.
If you want root, flash it afterwards. If you plan to use Magisk, let the first boot happen and flash it later!
Reboot and enjoy :good:
Downloads:
ROM: lineage-15.1-20180216-UNOFFICIAL-kylothow-dumpling.zip
Google Apps: OpenGapps 8.1 (UNOFFICIAL)
Reporting bugs:
Grab a logcat right after the problem has occurred (please include at least a few pages of the log, not just the last few lines, unless you know what you're doing).
If it is a random reboot, grab /proc/last_kmsg (do not bother getting a logcat unless you can get it just before the reboot, a logcat after a reboot is useless).
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log (only applies to SELinux enforcing builds).
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Credits:
This is a very important note: I am NOT the original developer of the device trees I'm using. Despite I do my best to fix bugs, improve security, stabilty and the performance of the ROM, it's not thanks to me that this is up and running now.
Please, be sure to thank and donate to the developers behind the device trees.
Huge thanks and credits to the NastyAndroidDevs team (https://github.com/NastyAndroidDevs).
@amartinz: https://github.com/amartinz
@codeworkx: https://github.com/codeworkx
@jrizzoli: https://github.com/jrizzoli
@jumoog: https://github.com/jumoog
Sources:
Device Trees (Reference): LineageOS
Kernel Tree (Reference): LineageOS
Manifest (Reference): NastyAndroidDevs
Device Trees (Custom): EvilDumplings
Kernel Tree (Custom): EvilDumplings
Manifest (Custom): EvilDumplings

Announcements/News:
20 December 2017:
The official LineageOS 15.1 dumpling and cheeseburger device trees are being uploaded on LineageOS' official GitHub account.
31 December 2017:
The fist working unofficial LineageOS 15.1 builds are going live
I made all my changes to NastyAndroidDevs' sources public. See the "Sources" section in the OP.

Thanks

kylothow said:
mine
Click to expand...
Click to collapse
Thnks for your hardwork and time. ?

Thanks:good:
downloading

Will you become the official maintainer for lineage OS for the oneplus 5t in the future?

Colday96 said:
Will you become the official maintainer for lineage OS for the oneplus 5t in the future?
Click to expand...
Click to collapse
As I said in the OP, I'm not the developer behind the device trees, it's all thanks to the NastyAndroidDevs (with pretty known names, if you know CyanogenMod/Lineage) who are unifying the OnePlus 5 and 5T sources (with a common tree with most stuff); it's likely one or more of them will maintain the device.

good morning first of all thanks for putting the ROM looks very good pinta.queria know if facial recognition works to unlock with the face. Thanks and greetings
Enviado desde mi ONEPLUS A5010 mediante Tapatalk

Great! It's finally coming to op5t

This is great news. Will we get a LOS 14.1 build then too? LOS 15 is still missing a lot of features unfortunately. It would be nice to have LOS 14.1 until things like the privacy manager and such get incorporated into LOS 15.

Nice to see this here, even if some basic features are still missing.

YAAAAASSS

CommanderROR said:
Nice to see this here, even if some basic features are still missing.
Click to expand...
Click to collapse
The biggest one is camera.

I think I should be able to fix Camera and NFC soon...

Great!
Thanks for your hard work on this.
I'd love an aosp rom on the BEA5T!!

I have a problem, when i flash the rom on twrp ive got error 7: "Rom is for dumpling, your device is: OnePlus 5T".
WTF?!

Kookitza said:
I have a problem, when i flash the rom on twrp ive got error 7: "Rom is for dumpling, your device is: OnePlus 5T".
WTF?!
Click to expand...
Click to collapse
That's because in device tree, ro.product.device property has been set as "dumpling", @kylothow , perhaps, it should be set to "OnePlus5T", the value that TWRP reads from device when the assert is checked while flashing.
EDIT:
In device tree, file BoardConfig.mk:
Code:
TARGET_OTA_ASSERT_DEVICE := [B]dumpling[/B]
...I get a little annoyed because not unified criteria about naming OP5T.

BitOBSessiOn said:
That's because in device tree, ro.product.device property has been set as "dumpling", perhaps, it should set to "OnePlus5T", the value that TWRP reads from device when the assert is checked while flashing.
Click to expand...
Click to collapse
This is something that we can change on build.prop or we should wait for the dev?

Kookitza said:
This is something that we can change on build.prop or we should wait for the dev?
Click to expand...
Click to collapse
You can unzip (or use something like mc...), edit the flashing script (META-INF/com/google/android/updater-script) delete the first two lines (assert...), repack/save zip, and try again...

BitOBSessiOn said:
You can unzip (or use something like mc...), edit the flashing script (META-INF/com/google/android/updater-script) delete the first two lines (assert...), repack/save zip, and try again...
Click to expand...
Click to collapse
Can you upload the right file (Updater-script), cause i think i messed it :/

[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)

Reserved
Couple of things to note:
I now have a rather taxing day job, and can't devote nearly as much time/effort into this as I did as a student.
As always, you are strongly advised to try PHH's AOSP first and identify/report issues there, before moving onto other GSIs that are based on his work. Please report bugs here only if it's specific to this GSI.
Thanks to patches from @eremitein , Magisk compatibility is partially restored. For devices that still don't play well with it (e.g. kernel restrictions implemented by OEM), use PHH-SU instead. Install the app and you'll get root for apps.
A-only and VNDKLite targets are now generated from AB images instead of built from source, see sas-creator. Kinda hacky and might be buggy. Move on to an AB device if you can.
To mount /system RW on AB devices, refer to this.
exfat SD cards still don't seem to work. Any help related to this would be appreciated.

Initial builds are based on PHH v300.j and December security patches.
Building-related bits have been published, but only for AB targets - I'm not sure if I want to integrate sas-creator yet.

Dear AndyYan. Thank you very much for all your work on these Roms. Do you think that I can flash the latest BitGapps R19 which was available a few weeks ago on the BitGapps website ?

Great job dude! I ammire you

Relesse 18 thank You my friend

Arm64 avS can't flash the beta versions of GApps and NikGApps, otherwise, constantly restart to TWRP.
Test again, it should be GApps problem, SD821 vndk27 Aonly everything is fine. Thank you.

The ROM bootlooped on Moto E6, though this is a very new ROM so I think I'll revert back to your LOS 17.1 ROM until things are a bit more ironed out.
I think this is the only Android 11 GSI so we all greatly appreciate your work. We're rooting for you

koyo said:
I think this is the only Android 11 GSI so we all greatly appreciate your work. We're rooting for you
Click to expand...
Click to collapse
Hey hey, it's still based on PHH's AOSP R, which has been out there for quite a while, just without an XDA thread. Let's all thank him first

Booted up just fine but no mobile data for me even after trying the IMS settings. Great work and thank you for the release!

Works perfectly on xt1962-1 or moto g7 river using LOS17.1 base

'just a report, tried it on oldies J730G booted fine wifi works, sim works, unable to play medias, reboots by itself about every 10mins or so, very snappy though. Thanks. Off to flashing another one, I'm developing a bad habit, just because I can doesn't mean I should

Edited:
Thanks to Phh for fixing ussd on v300L

Successfully installed the a/b-GSI from 2020-12-19 on Xiaomi MI 10T lite (gauguin) via fastbootd (necessary to handle dynamic partitions!).
Camera quality is awefull (;-) ) but the rest i tested so far looks promissing (WiFi works, Fingerprint works ... well see what make problems ;-) ).
Well done guys!!!
Cheers Kurt

Installed it successfuly on my Honor 9 (A/B). Almost everything works. Except:
- SD-Card don't work (as mentioned)
- Can't flash gapps, because of missing twrp for my device

Saftpresse99 said:
Installed it successfuly on my Honor 9 (A/B). Almost everything works. Except:
- SD-Card don't work (as mentioned)
- Can't flash gapps, because of missing twrp for my device
Click to expand...
Click to collapse
For my gauguin, i used root and Franko-Kernel-Manager to flash NikGapps ... had to mount /system rw manually, but at least it worked.
Cheers
Kurt

Kurt Krummbein said:
For my gauguin, i used root and Franko-Kernel-Manager to flash NikGapps ... had to mount /system rw manually, but at least it worked.
Cheers
Kurt
Click to expand...
Click to collapse
Thanks. I now using phhusson gsi. With gapps.
Perhaps it is easier to mount r/w with a vndklite Version.
Does anybody know, if it possible to switch between this rom and phhusson rom, without loose data?

Saftpresse99 said:
Thanks. I now using phhusson gsi. With gapps.
Perhaps it is easier to mount r/w with a vndklite Version.
Does anybody know, if it possible to switch between this rom and phhusson rom, without loose data?
Click to expand...
Click to collapse
Already tested between caosR and los18, just wipe system, cache and dalvik/art via twrp , flash new system img (+gapps if existed before), and reboot.

AndyYan said:
Background:
This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019.
Disclaimer:
This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
No flashing 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.
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
Revived navbar layout tuning via sysui_nav_bar tunable
Disabled "vendor mismatch" warning on boot
Signature spoofing support from MicroG
Default stretch-to-fullscreen (force apps to render in longer than 16:9)
Stuff on GitHub (builders-only):
Since builders' stuff aren't really interesting to end users, I decided not to separately document the modifications needed in this post; instead just check out the scripts/patches, where most things should be self-explanatory: treble_build_los, treble_patches (PHH's treble_patches adjusted for LOS). Not the cleanest code, but should help if you need some clues.
Donate?
https://paypal.me/AndyCGYan
Click to expand...
Click to collapse
AndyYan said:
Background:
This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019.
Disclaimer:
This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
No flashing 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.
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
Revived navbar layout tuning via sysui_nav_bar tunable
Disabled "vendor mismatch" warning on boot
Signature spoofing support from MicroG
Default stretch-to-fullscreen (force apps to render in longer than 16:9)
Stuff on GitHub (builders-only):
Since builders' stuff aren't really interesting to end users, I decided not to separately document the modifications needed in this post; instead just check out the scripts/patches, where most things should be self-explanatory: treble_build_los, treble_patches (PHH's treble_patches adjusted for LOS). Not the cleanest code, but should help if you need some clues.
Donate?
https://paypal.me/AndyCGYan
Click to expand...
Click to collapse
Thanks for your work . Your system working very fast , I share your system https://forum.xda-developers.com/t/gsi-11-lineageos-18-x-gsi-all-archs.4211857/ . Thanks for this system.

Sir ur BvS builds never pass safety net for me not even on A10 ur BvN were flawless....can u help please how to pass...I tried phh/secuize, magisk hide, changing fingerprint to various pixel devices, adding secure file but nothing works
I am on 18.1 rn and using Nokia 8.1 sdm 710
Or can u please just switch back to BvN

[GSI][UNOFFICIAL][12] Pixel Experience

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pixel Experience for GSI
What is this?
Pixel Experience is an AOSP based ROM with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Their mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12
What is working?
Almost everything
These are beta builds so expect some bugs
Known issues
Same issues of phh's AOSP
Download
Github
Telegram
Pixel Experience GSI
Translation
Help with project translation
Blog
Pixel Experience
Donate
jhenrique09
phhusson
AndyYan
eremitein
kdrag0n
ponces
Build author: ponces
Source code: PixelExperience
Device source code: device_phh_treble
ROM developer: jhenrique09
Contributors: Pixel Experience Team, phhusson, AndyYan, eremitein and kdrag0n - all credits should go to them

Pixel Experience 12.0 v400.a released!
Changelog:
Initial build
Sync with phh's AOSP 12.0 v400.a

Notes:
Don't ask for PE+ builds as they will come later in time. In the past, PE team took nearly four months to release the first builds of PE+ after releasing regular PE builds. Based on PE's team predictions, it should arrive in a month or so!
Use the slim variant if you have a small system partition (without Drive, Gmail, Maps, Photos, Recorder, Wallpapers and Google app)
Finally, take in consideration phh's notes that should also apply here:
This is a pre-release. This is not considered daily-drivable, though your mileage may vary.
As you'll notice, there is no A-only variant at the moment. It is still undecided whether A-only variants will later appear.
If you want unshared_blocks/read-write system, use vndklite variants. Non-vndklite devices are capable of running vndklite variants.
Click to expand...
Click to collapse

This release can be flashed in device with vendor for Android 10?

shjeanpy said:
This release can be flashed in device with vendor for Android 10?
Click to expand...
Click to collapse
Yes

stuck at android logo on Pixel XL. Any suggestions?

Hello I'm facing major issue in this GSI. Can't pull status bar quick toggles, developer options disabled showing "developer options not available for this user", gesture navigation buttons not working, recent apps always showing empty. Needed to know if this is known issue. I guess this happening because after fresh installation this didn't show setup wizard similar issue to this article.

it works fine for me, only a few minor graphical glitches. hope the next version will be better

I have tested in my xperia lena 10 III , stability is same as stock rom here + I have certified play stores
good job

This GSI is running fine on my a71 but when I try to get into recovery, it just gets stuck on the logo screen and reboots and boots into twrp again but still stuck on the logo screen. This happens until I hard reset device. After I hard reset I boot fine into the gsi

Is this rom has material you monet themeing

This is outstanding ... Went from stock Android 10 somewhere last week, to your Pixel+ GSI to now a Pixel 12 GSI on my Galaxy Note 9 (Exynos) with what i can see so far is 0 issues (auto brightness excepted ( i need to help fix that with an overlay i suspect )). Great work and many thanks to you and @phhusson for keeping this old fella up to date !! Android has been fun again the past week
Im not seeing the GPU glitches either mentioned on phh's github for Samsung unless the workaround is already applied..
Thanks !!!!

Cass67 said:
This is outstanding ... Went from stock Android 10 somewhere last week, to your Pixel+ GSI to now a Pixel 12 GSI on my Galaxy Note 9 (Exynos) with what i can see so far is 0 issues (auto brightness excepted ( i need to help fix that with an overlay i suspect )). Great work and many thanks to you and @phhusson for keeping this old fella up to date !! Android has been fun again the past week
Im not seeing the GPU glitches either mentioned on phh's github for Samsung unless the workaround is already applied..
Thanks !!!!
Click to expand...
Click to collapse
How did you applied that glitch work around I can't find that lines in build props not even on terminal I am. Using galaxy tab 10.1.
Also one question this rom. Has monet wallaper based themeing or not

pankspoo said:
How did you applied that glitch work around I can't find that lines in build props not even on terminal I am. Using galaxy tab 10.1.
Also one question this rom. Has monet wallaper based themeing or not
Click to expand...
Click to collapse
I have not applied any workaround. I just don't see any glitches. I also guess monet theming is in place as its a part of A12.. you can change stuff relating colors in the settings, not paid much attention to that though.

Cass67 said:
This is outstanding ... Went from stock Android 10 somewhere last week, to your Pixel+ GSI to now a Pixel 12 GSI on my Galaxy Note 9 (Exynos) with what i can see so far is 0 issues (auto brightness excepted ( i need to help fix that with an overlay i suspect )). Great work and many thanks to you and @phhusson for keeping this old fella up to date !! Android has been fun again the past week
Im not seeing the GPU glitches either mentioned on phh's github for Samsung unless the workaround is already applied..
Thanks !!!!
Click to expand...
Click to collapse
Yeah can someone help with auto brightness on Samsung devices ? Also root a S10 is kind of a pain, even going in recovery take few tries with buttons combinations. Boring stuff

Works well on moto g 5g plus!
Thank you for your work
I think the old version of TWRP published on XDA for nairo does't work on android 12 anymore because it bootloops.
EDIT: Also the aux isn't working, I've tried using the patches in settings for huawei devices and also connecting a usb-c dongle to aux but it's not working either.
I hope there will be a patch together with huawei for motorola phones but i guess they have less development going on.
There might be both overlays for nairo and audio drivers(i think) on the omnirom project.
EDIT2: SOLVED both problems, i created a guide to fix both here

I`m new to GSI, more like used to old school ROM installing and crap. I wonder if after installing this ROM on my treble-compatible device (which has worked perfectly fine for other people on YouTube):
1. Any new updates from this alpha stage will be rolled out automatically over the air or do I have to update manually reflashing, etc? How would that happen?
2. Google`s security updates, like the one released today will be installed over this build or that is part of another process?
Thank you!

lcmazza said:
1. Any new updates from this alpha stage will be rolled out automatically over the air or do I have to update manually reflashing, etc? How would that happen?
2. Google`s security updates, like the one released today will be installed over this build or that is part of another process?
Click to expand...
Click to collapse
1. No GSIs have user-facing OTA yet. Flash manually all the time.
2. As part of flashing/updating the GSI itself.

Hello, i just flashed this gsi (arm64 ab).
But, when booted, it just blank. But it have sounds using power button (Like sound while locking and opening). And i can't mount system in recovery. Using a10 vendor
Is this vendor issue?

where do i grab the pixel experience gsi for flashing to moto g7 power .

[GSI][12] LineageOS 19.x GSI (A64B/64B)

Reserved
Notes:
I now have a rather taxing day job, and can't devote nearly as much time/effort into this as I did as a student.
GAPPS builds are offered as-is without guarantees. Read #10 for more.
/system is RO on regular builds and RW on VNDKLite builds. VNDKLite builds can be used on most non-VNDKLite devices as well.
ADB is intentionally insecure, even on first boot (turned on by default and no authentication needed). GSIs are more fragile compared to device-specific custom ROMs, both on first boot (no-boot issues) and on subsequent boots (after tuning certain Treble settings), and I insist that no-auth ADB is a must-have for debugging and general fail-safe.
Signature spoofing (MicroG) is supported, but only for priv-apps. This is a security consideration from PHH.
Magisk support should be on par with A11 (thanks @eremitein). The "abnormal state / unsupported SU" warning can be ignored. For devices that still don't play well with Magisk (e.g. kernel restrictions implemented by OEM), use PHH-SU instead. Install the app and you'll get root for apps.

Initial builds are based on PHH v400.c and November security patches.
Sigh, I don't really want to make a thread this early...
BTW, 32-bit and A-only users, you should really move on.

Big work thank You

Hey How to flash this Gsi Guys can someone answer me????

Thank you so much. Are gapps included ?

walid77dz said:
Thank you so much. Are gapps included ?
Click to expand...
Click to collapse
From an earlier post...
AndyYan said:
32*/A32* users, I'm not stopping your monthly builds just yet, but 32-bit is getting phased out, and you should upgrade soon. Similar goes for A-only. Ideally in the future we'll only have 64B, making room for other much needed variants such as GAPPS.
Click to expand...
Click to collapse
Their deprecation does seem likely now, so I'll try a GAPPS build or two when I have time.

Do you consider this alpha usable as daily driver?
And, does it require clean installation from LOS 18 GSI?

Avraham Tsaban said:
Do you consider this alpha usable as daily driver?
And, does it require clean installation from LOS 18 GSI?
Click to expand...
Click to collapse
I am using it as my daily driver - I enabled Gallery and LiveDisplay for just that purpose.
Out of curiosity I did try a dirty install from 18.1. It booted and most apps work, to my surprise, but Messaging won't allow me to select contacts properly no matter what, and that was a blocker, so don't.

People who love LOS, insist on using GAPPS with it, and had been asking me for such builds all this time - I now have a lil something for you, a test LOS19 build with GAPPS built-in. It's intentionally in the "personal" flavor to discourage use as your daily driver, but also shared-blocks (unlike previous "personal" builds) to save some space.
It was more trivial to build than I thought, but that doesn't mean I'll build it alongside vanilla yet...
Every variant takes disk space and build time
The image itself is huge and won't fit in even slightly older devices
Too many archs/variants confuse users
I cannot make any guarantees about it
I've seldom mentioned the last point, yet it's critical - I'm in China and I don't use GAPPS at all, so I have little idea about what counts as "properly working" for GAPPS and how to troubleshoot them. Even if I do eventually build with GAPPS, I can only provide builds as-is, and you'll have to help each other out on GAPPS-related/-induced issues. At the end of the day, I still recommend using other ROMs that are built around GAPPS, e.g. @ponces ' PE, for a more cohesive experience and better support.
For now, all I know is this test build logs in (after registering the device here), can open Play Store and download apps, nothing beyond that.

Huawei P20L mobile data doesn't work

confirmed working on huawei mediapad m5 (cmr-w09 model name)
thx so much AndyYan
first degoogled android 12
su working via phh su app - magisk wasn't working proper

I do the installation through fastboot, because I don't have twrp, The installation is successful, but when I start to start the installation it gives an error: Invalid sparse file format at header magic, and after that it installs normally, but when I start the system, it gets stuck in the logo of the manufacturer of my device, Any solution?

Flashed this ROM on my Oneplus 9 Pro and was surprised how great and smooth it is.
I read on a thread how to fix fingerprint issue on GSI ROM by editing /vendor/build.prop, tried it and ended up in bootloop and I have to start all over.
What's the right way to do this?
Thanks in advance.

Geoz said:
fix fingerprint issue on GSI ROM
Click to expand...
Click to collapse
You don't - no A12 GSIs support UDFPS yet.

AndyYan said:
You don't - no A12 GSIs support UDFPS yet.
Click to expand...
Click to collapse
Good to know. I appreciate you taking the time to explain this.
Thanks.

Geoz said:
Good to know. I appreciate you taking the time to explain this.
Thanks.
Click to expand...
Click to collapse
BTW, I believe most OPlus devices have read-only vendor, so even in the future you probably shouldn't head down that road.

AndyYan said:
BTW, I believe most OPlus devices have read-only vendor, so even in the future you probably shouldn't head down that road.
Click to expand...
Click to collapse
What of if I use Lineage OS as the base?
Thanks again.

Geoz said:
What of if I use Lineage OS as the base?
Thanks again.
Click to expand...
Click to collapse
That depends on your maintainer (LuK), and also PHH only deals with issues with stock vendors.
Speaking of which, looks like someone else also can't wait for LuK's 19.0, hehe...

AndyYan said:
That depends on your maintainer (LuK), and also PHH only deals with issues with stock vendors.
Speaking of which, looks like someone else also can't wait for LuK's 19.0, hehe...
Click to expand...
Click to collapse
First time on GSI ROM but I'm really impressed. I've learned a lot from you in a very short time. All information I read on the internet is not valid rather from a developer like you.
I appreciate you.

[GSI][13] LineageOS 20 "Light"

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
Click to expand...
Click to collapse
MUST-READ BACKGROUND - Android 13 and the two approaches:
As some of you already know, due to various reasons, @phhusson , who kickstarted the GSI trend and committed to it over the years, is backing out from future development - there won't be any AOSP 13+ builds or patches directly from him. He did most of the heavylifting for fixing bugs and implementing features, and selflessly supported more than his AOSP GSIs and more than devices he own. For the situation of GSIs today, we owe him a big thank-you.
Since PHH made up his mind, a number of existing builders incl. myself have formed the TrebleDroid organization, with PHH himself helping us in technical issues. TD will forward-port PHH's final patches (v415) onto Android 13 and attempt to fix new issues. This is still a new and ongoing process, but if done right, will have compatibility and feature-completion on par with past PHH-based GSIs.
Meanwhile, I'm aware that at least I myself am not as capable as PHH, and won't be able to look after the myriad of patches and devices, esp. legacy ones (pre-A10). Therefore, inspired by @PeterCxy , I'm taking a different approach - start over from AOSP's generic gsi_* target, add in the minimum amount of fixes needed for my own devices, shaking off much of the legacy burden in the process and making it easier for myself to follow/maintain. This is a radical, selfish approach that by definition won't work for legacy devices anymore, and won't work as well as PHH-based GSIs that you've come to love either. However, I've fixed it up to my own daily-driver standards, and I figured it should still be of use to many. For now, I call this the "light" approach.
Disclaimer:
No flashing 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.
The selfish nature of this approach means I can and will ignore certain bugs as I see fit. Deal with it or kindly go try something else.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Scroll down for the naming rules of variants.
Compressed as .xz archives - extract first.
Stuff on GitHub (builders-only):
Most things should be self-explanatory. Not the cleanest code, but should help if you need some clues.
lineage_build_unified - my unified script for building
lineage_patches_unified - my unified patches for building
device_lineage_gsi - my device tree that extends native generic targets
Thanks to:
The LineageOS team - helping me out even when they don't offer GSIs themselves
@phhusson - shaped the treble community, and even the "light" approach uses his fixes/infra extensively
@PeterCxy - inspired me with his personal-use GSI, and coded critical fixes such as sysbta
...and more
Donate?
https://paypal.me/AndyCGYan

This post documents my progress on top of the native generic targets.
Already implemented/fixed:
Built-in root (PHH-SU)
Device overlays
Screen resolution & refresh rate - improved upon PHH's implementation
Alternative audio policy (Qualcomm)
Disable soundvolume effect (Qualcomm)
Alternative backlight scale (MediaTek)
resetprop/copyprop tool
In-call audio
BT audio
VoLTE on Qualcomm/MediaTek pre-S vendors
VoLTE on Qualcomm/MediaTek S vendors - new, backported to PHH-based
GAPPS - using MindTheGapps for now
Securized - "on-demand" reversible toggle
Disable A2DP offload
Alternative audio jack detection
Signature spoofing - limited to priv-app for the same security reason as in PHH/TD-based
Optional FP lockout (set persist.sys.fp.lockouts.disable to true to disable timeout on failed FP attempts)
Built-in PHH-SU app for *S variant
Override minimum brightness
Override navbar availability
Exfat
In-call audio on Snapdragon 8 Gen 2 (SM8550) and newer Qualcomm devices
To be implemented/fixed at a later time:
VoLTE on Motorola Qualcomm S vendors - situation did not improve with stock T, lowering priority
Known but will not implement/fix:
Compatibility with legacy (pre-A10) devices, A-only, VNDKLite
FOD/UDFPS (commonly known as in-display fingerprint) - not skilled enough for it and not interested either
MediaTek kernel BPF bug (#9)
VoLTE on non-Qualcomm/MediaTek vendors
Samsung/Huawei oddities

Notes:
I now have a rather taxing day job, and can't devote nearly as much time/effort into this as I did as a student, or even a year ago.
No A-only or VNDKLite builds. These are concepts that don't exist natively.
GAPPS builds are offered as-is without guarantees. As a Chinese I can't/won't help with GAPPS/SN issues - please help each other out.
ADB is intentionally insecure, even on first boot (turned on by default and no authentication needed). GSIs are more fragile compared to device-specific custom ROMs, both on first boot (no-boot issues) and on subsequent boots (after tuning certain Treble settings), and I insist that no-auth ADB is a must-have for debugging and general fail-safe.
Signature spoofing (MicroG) is supported, but only for priv-apps. This is a security consideration from PHH.
Refer to #9 for explanation/workaround of an MediaTek-specific kernel bug that causes no internet.

TD-based LOS20 will be offered as well, but at a later date - I've only made a first test build of it today. At its current state though, it doesn't work as well as PHH-based A12 either, so don't get your hopes up too high.

Good job!

Yay!!!

yay!!!! thank you!!!!

Thank you very much for your great work. I've been waiting for this for a long time.
I ran into a very, very strange bug.
I have a Qin F21PRO (MT6761).
This model has two sub-models:
4GB RAM + 64GB storage
3GB RAM + 32GB storage.
My device is
4GB RAM + 64GB storage
But after flashing this GSI, it is shown that there is only 32GB storage.
edit: after factory reset via twrp, i getting 64GB storage

There's a known kernel bug in some recent MTK devices that breaks BPF badly, resulting in broken networking features since Android 13, and no-boot since r11 (Google decided to tighten the check). I've reverted the no-boot, but the actual bug can't be fixed from platform-side.
This affects LOS in that it has Restricted Networking Mode turned on by default, and with the bug in place, apps cannot be added to the allow list, resulting in no internet in even system apps.
If you own an MTK device and notice such a thing, as a temporary workaround, you can turn the feature off manually with:
Code:
adb shell settings put global restricted_networking_mode 0
If you're on the gN variant, SetupWizard would also have no internet, so just skip the setup entirely, turn on USB Debugging once you're in the OS, run the above, then re-initiate the setup from the status bar.
As for a more persistent fix - thanks to @Rortiz2 , there's now a way to manually patch the kernel binary, however I no longer have an affected device for testing this. Feel free to try out the patcher here.
There might be other broken networking features that I'm unaware of. In the long term, the one true solution is to upgrade to a newer vendor base, hoping that the OEM has merged the kernel-side fix.

AndyYan said:
TD-based LOS20 will be offered as well, but at a later date - I've only made a first test build of it today. At its current state though, it doesn't work as well as PHH-based A12 either, so don't get your hopes up too high.
Click to expand...
Click to collapse
There is no Navigation key or gesture options, How to do it?, I can install it on my Samsung device but without navigation, no home/back key

redymedan said:
There is no Navigation key or gesture options, How to do it?, I can install it on my Samsung device but without navigation, no home/back key
Click to expand...
Click to collapse
Ugh, a Samsung oddity. I didn't implement the force overide switch - if a non-Samsung hits this as well, I might.
If you know how to, try adding "qemu.hw.mainkeys=0" to /system/build.prop. These images are EXT4 unshared blocks, so as long you have verity disabled and root, you should be able to edit/save it.

redymedan said:
There is no Navigation key or gesture options, How to do it?, I can install it on my Samsung device but without navigation, no home/back key
Click to expand...
Click to collapse
AndyYan said:
Ugh, a Samsung oddity. I didn't implement the force overide switch - if a non-Samsung hits this as well, I might.
If you know how to, try adding "qemu.hw.mainkeys=0" to /system/build.prop. These images are EXT4 unshared blocks, so as long you have verity disabled and root, you should be able to edit/save it.
Click to expand...
Click to collapse
Same problem with Redmi Note 10 (mojito)

@redymedan @spider1163 Can you give me the full result of "getprop" from shell? Paste it to e.g. Pastebin.

D
AndyYan said:
Ugh, a Samsung oddity. I didn't implement the force overide switch - if a non-Samsung hits this as well, I might.
If you know how to, try adding "qemu.hw.mainkeys=0" to /system/build.prop. These images are EXT4 unshared blocks, so as long you have verity disabled and root, you should be able to edit/save it.
Click to expand...
Click to collapse
Done! I just added "qemu.hw.mainkeys=0" to /system/build.prop and the navigation keys enabled. also in Gesture menu "System navigation" option appeared. It works now on my Galaxy A50, Thanks
Other problem: Google Play Protect certified "This device isn't Play Protect certified"

amazing! waiting for gapps variant now.

redymedan said:
Done! I just added "qemu.hw.mainkeys=0" to /system/build.prop and the navigation keys enabled.
Click to expand...
Click to collapse
Thanks for confirming it's that simple! Given that "light" won't look back on legacy devices, I think I'll just enable this prop globally in the next releases.

This is exactly what I was waiting for, it will be fun to test on my old Huawei P smart 2019 with Android 9 vendor so let's see what happens. Any result of this experiment will be shared here.

THX for your great work.
But how can I install gapps?
I've tried to install BitGApps with Magisk as a Magisk module, but it says 'insufficient partition size'.
There's no working TWRP for my device

michael_hamada said:
THX for your great work.
But how can I install gapps?
I've tried to install BitGApps with Magisk as a Magisk module, but it says 'insufficient partition size'.
There's no working TWRP for my device
Click to expand...
Click to collapse
you wait... ..

THX for your great work. but auto brightness not working Is this expected behavior？

Better Mobile App

welcome