[GSI][13] LineageOS 20 TrebleDroid-based - Treble-Enabled Device Development A/AB ROMS

{
"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.
Earlier, inspired by @PeterCxy , I took the "light" approach, which starts over from AOSP's generic gsi_* target and adds the minimum amount of fixes needed for my own devices, intentionally leaving many legacy devices behind. For more details about it, visit its own thread.
Meanwhile, 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. This thread contains LOS builds based on TrebleDroid's collective work, which supposedly suits legacy devices, Samsung, etc. better than "light".
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.
MUST-READ - reporting bugs:
If you want to report a bug, then you MUST try reproducing on an AOSP reference build of around the same date from TrebleDroid, and ONLY proceed to report here when it's specific to this GSI. This filters out bugs common to all TD-based GSIs, which you should still let me know, but it might not be mine to fix. I might silently ignore your report if you skip this.
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
Thanks to:
The LineageOS team
@phhusson - shaped the treble community, and still takes care of TrebleDroid at a higher level
@PeterCxy - coded critical fixes such as sysbta
The TrebleDroid builders
...and more
Donate?
https://paypal.me/AndyCGYan

---

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.
I now daily-drive "light", so I can't test TD-based builds as extensively as before. For the same reason, I likely won't build/upload any TD-based "personal" build either.
While most >=A13 GSIs out there are going to be TD-based, some perform better than others - some devs have their own patches that haven't been merged into TD yet. I myself will stay close to TD's raw patchset as much as possible, without picking patches from others left and right. If you find another GSI working better, don't just complain - try to narrow down which ones, and the intersection of them might be an unmerged patch that, if approved, would be merged into TD and benefit all.
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.
On *S variants, install PHH-SU and you'll get basic root for apps, good for devices that don't play well with Magisk or when you don't need modules.
Refer to this post for explanation/workaround of an MediaTek-specific kernel bug that causes no internet.

---

Reserved

---

Initial builds are based on TD patches as of 20221111 and November security patches.

---

Treble Droid'e daha fazla dikkat edin çünkü bu tiz droid ışıktan daha iyi görünüyor ve neden 20 ota soyundan gelmiyor?
Pay more attention to Treble Droid I think because this treble droid looks better than light and why no lineageos 20 ota

---

Hello, the security patch is from November, it appears from 2021-

---

ismail demirbaş said:
why no lineageos 20 ota
Click to expand...
Click to collapse
PHH's OTA is incompatible with Magisk, so I chose to not configure it.
ped1609 said:
Hello, the security patch is from November, it appears from 2021-
Click to expand...
Click to collapse
One of the side effects of Securize - it copies your vendor security patch date.

---

AndyYan said:
La OTA de PHH es incompatible con Magisk, así que opté por no configurarla.
Uno de los efectos secundarios de Securize: c
Click to expand...
Click to collapse
AndyYan said:
La OTA de PHH es incompatible con Magisk, así que opté por no configurarla.
Uno de los efectos secundarios de Securize: copia la fecha del parche de seguridad de su proveedor .
Click to expand...
Click to collapse
Hola me encanta la rom de momento funciona bien. hare pruebas de llamadas ect,.Como hago para copiar la fecha del parche ,Gracias gran rom.

---

AndyYan said:
PHH's OTA is incompatible with Magisk, so I chose to not configure it.
One of the side effects of Securize - it copies your vendor security patch date.,Hello I love the rom at the moment it works well. I will test calls ect,. How do I copy the date of the patch, Thanks great rom
Click to expand...
Click to collapse

---

@ped1609 You can't correct it yourself.
I'll experiment with making Securize less intrusive, at this moment it impacts USB debugging, security patch date, model name, etc. Perhaps there's a lighter way out...

---

AndyYan said:
@ped1609 You can't correct it yourself.
I'll experiment with making Securize less intrusive, at this moment it impacts USB debugging, security patch date, model name, etc. Perhaps there's a lighter way out...
Click to expand...
Click to collapse
Hello, I'm in the rom but I don't know how to copy the provider, do I extract it from another rom with the correct date? can you edit build pro? I have a redmi note 11s, I use stock recovery.

---

Any screenshot for this build

---

everything looks great but , it connects to wifi ok , but not getting any internet from wifi , so cant use it

---

Jimmy Glex said:
everything looks great but , it connects to wifi ok , but not getting any internet from wifi , so cant use it
Click to expand...
Click to collapse
Can you all read notes?

---

Tested on Samsung galaxy tab A8 x-205 (arm64_bvN-secure). Camera and video playback don't work (reproducible on AOSP as well). When trying to launch a camera or play a video Lineage GUI freezes and then restarts. Everything else works and overall experience is smooth.

---

Does not boot for the samsung galaxy a12 nacho. (Edit: used ChonDoe Flasher and then it worked, so you need ChonDoe flasher for it to work)

---

Thanks for the great job.
Works very well on Samsung A22 5G (arm64_bvN-secure) after MediaTek internet bug solving.

---

Thanks for your great job.
Booted fine on my old Zenfone Max Pro M2.
I flashed it by OrangeFox recovery, and it booted fine once. But in the second boot, it fell to recovery and recovery caused boot loop.
More worse...Fastboot mode reject all fastboot command so I was lost several days.
Finally I managed to flash latest TWRP and everything went back to normal.
(Fastboot issue was caused by USB 3.0)
Anyway, this is a great ROM so far!
THX so much!

---

i downloaded as a gsi dsu sideload , and works , just wifi cant get internet even if it conects ,is there a work around to solve that? im in poco x3 gt

---

Jimmy Glex said:
i downloaded as a gsi dsu sideload , and works , just wifi cant get internet even if it conects ,is there a work around to solve that? im in poco x3 gt
Click to expand...
Click to collapse
AndyYan said:
Notes:
[...]
Refer to this post for explanation/workaround of an MediaTek-specific kernel bug that causes no internet.
Click to expand...
Click to collapse