[GSI][13] LineageOS 20 TrebleDroid-based

Search This thread
By:
Advanced…
AndyYan

AndyYan

Recognized Contributor
Jan 30, 2012
4,684
4,189
Beijing
640px-Lineage_OS_Logo.png

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.
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
 
Last edited:
  • Like
  • Love
Reactions: 1NSN, joaofl, jonpjingleheimler and 22 others
AndyYan

AndyYan

Recognized Contributor
Jan 30, 2012
4,684
4,189
Beijing
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.
 
Last edited:
  • Like
Reactions: Autodakt, Sage, sso003 and 3 others
ismail demirbaş

ismail demirbaş

Member
Jan 6, 2021
34
2
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
 
  • Like
Reactions: hacker812c
P

ped1609

Member
Jun 4, 2013
22
5
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.
 
  • Like
Reactions: hacker812c
AndyYan

AndyYan

Recognized Contributor
Jan 30, 2012
4,684
4,189
Beijing
@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...
 
  • Like
Reactions: hacker812c
P

ped1609

Member
Jun 4, 2013
22
5
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.
 
Last edited:
  • Like
Reactions: hacker812c
N

nisfta

Member
Oct 1, 2022
13
1
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.
 
Last edited:
  • Like
Reactions: hacker812c
michael_hamada

michael_hamada

Senior Member
Jun 14, 2011
464
189
TOKYO
Samsung Galaxy S III I9300
HTC Desire
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.0o_O)
Anyway, this is a great ROM so far!
THX so much!
 
  • Like
Reactions: hacker812c
Jimmy Glex

Jimmy Glex

Senior Member
Jul 17, 2022
77
12
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
 
  • Like
Reactions: hacker812c
T

ttritium

Member
Nov 1, 2020
26
15
Samsung Galaxy A Series 2017 A3, A5, A7
Samsung Galaxy A22 5G
  • Like
Reactions: Rusik77, Jimmy Glex and AndyYan
You must log in or register to reply here.

Similar threads

AndyYan
  • Poll
[DISCONTINUED][GSI][10] LineageOS 17.x GSI (all archs)
Replies
1K
Views
323K
S
simbiyot
EnesSastim
[9.0][GSI] PixelExperience P - UNOFFICIAL
Replies
2K
Views
474K
元
元老鼠-鼠王
erfanoabdi
[Q][GSI][A/AB][arm64] Android Q Developer Preview
Replies
2K
Views
514K
Benyonq
Benyonq
sixohtew
[ROM][GSI] BlissRoms [11.8] 9.0 [Stable][arm64 a/ab][gapps optional] Official
Replies
435
Views
530K
R
rajesh vijay
phhusson
[AOSP 8.1] [2019-03-06] Phh-Treble
Replies
3K
Views
780K
Eric_Mello
Eric_Mello

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 4
    AndyYan
    AndyYan
    Updated all variants with May security patches and in sync with TD 20230429. [Insert obligatory backup-and-test warning here]
    View
    3
    AndyYan
    AndyYan
    conduisant said:
    Hello i run LOS 20-20230507-UNOFFICIAL-arm64_bvS on a xiaomi redmi note 11, and i can't send any SMS or MMS in 4G, only 3G mode (By changing prefered network) works well...any idea ?
    Click to expand...
    Click to collapse
    Set up IMS/VoLTE properly in Treble settings.
    mouseracer said:
    It was at this point the phone display started stuttering whenever I'd touch the screen (and sometimes would do so without). The setup process was stuttering throughout the entire process.

    At the end of the setup, after I pressed on the final button at the end of the Lineage Setup, the screen finally went black and the only sort of response I could do was to hold the power button, which showed me a minimal power menu.
    Click to expand...
    Click to collapse
    This sounds like something crashing hard in the background repeatedly - a logcat would perhaps be useful.
    lemon07r said:
    Also is the TD based rom, or the light rom expected to have better compatibility with phones like the Legion Y70 (ignoring the call bug)?
    Click to expand...
    Click to collapse
    Neither - right now it's a known issue that Moto/Lenovo QCOM S vendor devices have spotty or no SMS reception, and this can easily break daily driving. I've even bought a device just to look into this, but so far I don't know how to solve it within a GSI environment (device-specific ROMs have more room to work with).
    jukatkatze said:
    "Disclaimer:
    No flashing instructions will be offered. If you're here in this forum, you should know what you're doing."

    Keep jealously guarding your secrets and let the rest of the world die stupid, you lousy rats!
    Click to expand...
    Click to collapse
    Just because this is a generic image doesn't mean there's a generic enough way of flashing it everywhere. I've handled dozens of devices for GSI purposes so far, and many have curious traits that one would never know until a hands-on. You can blame me for being lazy and not summarizing findings on my devices on PHH's wiki, but I won't take blame for not offering an all-encompassing guide that "just works".
    View
    3
    A
    AnonVendetta
    syneoa said:
    Lecture you? Dude, by installing just one Google app after your MicroG exhbition all that you said above failed down deep in the water so better revise your thinking from ground up :D
    Click to expand...
    Click to collapse
    Unfortunately, Play Store is a necessary addition to MicroG. And it's otherwise the only not open source Google app i include. It's pretty much the only way to buy apps or make in-app purchases. And some apps check their licenses to make sure they're not pirated. Without PS, this isn't possible, not without resorting to other apps/methods that coincidentally are forbidden for discussion by XDA rules.

    If "revise your thinking" means "switch back to GApps" or "buy an iPhone"....no thanks. If I'm just going to play by the accepted rules that Google and the manufacturers push, then this means that I should only run stock ROMs, always keep bootloader locked, etc. No to that too.

    On this, we can agree to disagree, and that's the end of this line of conversation, I'm drawing the line by deciding it's not worth discussing with you anymore. It all started because you asked "Why not just flash G variant than?" I interpreted this as you not being aware of MicroG, or why some would choose it over GApps.
    View
    2
    A
    AnonVendetta
    syneoa said:
    It's strange really, flashed week ago or so and still no stats. We'll keep on looking but at least I know it's me and not for rest of you guys, ✌️
    Oh, gotta say I debloated a ton of apps from it so I may exaggerated a bit lol
    Click to expand...
    Click to collapse
    You probably debloated too much. There's not much of a point in doing so, LOS is very clean, even the GApps builds. If you want a gsi that doesn't need debloating, go for Phh's AOSP vanilla builds. No fluff, just raw Android. And its' bugs will be 99% the same as this LOS. For GApps, use vndklite and flash MindTheGApps on top, if you have TWRP.
    View
    2
    A
    AnonVendetta
    @syneoa: I suggest reflashing the gsi, then using this to debloat:

    Magisk Module Systemless Debloater

    Magisk Module Systemless Debloater Download...
    forum.xda-developers.com forum.xda-developers.com

    It doesn't really delete anything, so if you debloat too much, just edit your config file and reflash the mod zip. Anything you've "deleted" will be back.

    You can also do real deletion without a module, but then it will be harder to put something back if you make a mistake.

    For deleting mobile data stuff, I guess you missed the "remove telephony subsystem" option in Phh Treble Settings, Misc menu.
    View
  • 25
    AndyYan
    AndyYan
    640px-Lineage_OS_Logo.png

    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.
    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
    View
    7
    AndyYan
    AndyYan
    Updated all variants with April security patches and in sync with TD 20230417. [Insert obligatory backup-and-test warning here]

    All modern Xiaomi/Redmi devices should be able to see high refresh rates now (if supported), without having to spoof properties globally.
    View
    6
    AndyYan
    AndyYan
    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.
    View
    6
    AndyYan
    AndyYan
    Updated all variants with Android 13 QPR2 and March security patches. [Insert obligatory backup-and-test warning here]

    As usual with "feature drops", things can change or break majorly.

    Fixed in-call audio on Snapdragon 8 Gen 2 (SM8550), tested on OnePlus 11, should pave the way for future QCOM SoCs as well. Users of other SM8550 devices like Xiaomi 13 and RedMagic 8 Pro/+ might want to try this out too. Also pushed to TD upstream, so in case you don't like LOS, it's still coming to your favorite TD/-based GSI later.

    Imported some SN fixes from HentaiOS - GAPPS users should now get CTS profile match as well.

    Fixed videos sometimes getting stuck after pausing and resuming, thanks @Cozzmy13 for working it.

    Fixed two-pane layout in Settings for tablets - set an appropriate density then force stop Settings for it to take effect.

    And finally for builders, starting this month LOS has moved to Git LFS for hosting their Chromium webviews. Please re-init the repo with "--git-lfs" flag BEFORE syncing again or you will hit errors. If you already have a bad sync, clear the residue and re-init:
    Code: 
    rm -rf external/chromium-webview/prebuilt/*
rm -rf .repo/projects/external/chromium-webview/prebuilt/*
rm -rf .repo/project-objects/LineageOS/android_external_chromium-webview_prebuilt_*
    View
    5
    AndyYan
    AndyYan
    Updated all variants with January security patches and in sync with TD 20230104. [Insert obligatory backup-and-test warning here]

    During my CoV downtime, A13 QPR1 happened and TD-based had a lot of changes as well, which accumulated to this month and I had to update more patches than expected (way more than "Light" - lower maintenance is why I made that in the first place). I might've made oopsies along the way, so I don't feel quite confident about this batch, and you should exercise extra caution.

    Some users have reported that securize bootloops their device, and the current "integrally securize" approach means they can't boot up even once. This month I've changed it yet again to "securize on-demand", which is similar to how you securize on PHH/TD-based (a toggle in Treble Settings), but reversible and doesn't require SU.
    For new users who are unsure about whether securize might bootloop your device, please turn on USB Debugging and Rooted Debugging below it, and if/when you do hit a bootloop on the next boot, you'll have a rooted ADB shell available to you, from where you can toggle off manually:
    Code: 
    adb root
adb shell setprop persist.sys.phh.securize false
adb reboot
    For users who are already on a gN build, be sure to toggle it on and reboot right after you update!

    Properly fixed exfat for Samsung/Sony, tested on the one Sammy I still own.
    View

New posts