[GSI][13] LineageOS 20 TrebleDroid-based

Search This thread

atlantix1

Senior Member
Sep 27, 2011
117
33
This GSI works really well on my Galay S22 (SM-S901B)! Everything works flawlessly and runs smoothly! Big thanks to the developer! One thing, though: Whenever I try to register my fingerprint, systemui immediately crashes. Maybe the attached log helps to find the cause? Thanks!

Edit: The issue is fixed in latest Treble Droid release: https://github.com/TrebleDroid/plat...mmit/2f67d9f7b996f4143a1fcc7dc1a64819ab3b5429.

Sorry, should have posted bug there. ;)
 

Attachments

  • locat.txt
    33.4 KB · Views: 7
Last edited:
Have you tested with any other non-LOS gsis? If so, same issue? What about testing on stock firmware?
No, I'm honestly a bit afraid of damaging my system through the various tests and then not having a working smartphone anymore.
I am unfortunately very dependent on the device and a change to another device is not so easy because a lot runs on it.

But I did some research, and it seems that the bug is somewhere in LineageOS 20:
 

xavier.miller

Senior Member
Oct 2, 2014
56
20
www.xaviermiller.be
Thank you for your help.

Curiously, I tried sending an SMS to a new recipient over the weekend and it worked flawlessly.

With the messages that could not be sent, it can not actually be the receiver, because I could send SMS from the same cell with the same settings and the same SIM card from my other smartphone.

So SMS sending works, but only with certain recipients, while with other devices SMS sending works with all recipients.

I just can not figure it out.
Hi!

I have the same issue sending SMS.

I have found a workaround : if I go to plane mode then back, I can resend the blocked SMS.

HTH
 
I have found a workaround : if I go to plane mode then back, I can resend the blocked SMS.
I had already tried that without success.
I had also tested sending with disabled mobile data and only WLAN, or only 4G, or only 5G.

Also the tips linked in the link above with a prefix in front of the number, or the workaround to delete the contact and the conversation was not successful.

Resetting the APN settings did not work, nor did using a different messaging app.
 

AnonVendetta

Senior Member
Apr 29, 2016
1,484
531
I had already tried that without success.
I had also tested sending with disabled mobile data and only WLAN, or only 4G, or only 5G.

Also the tips linked in the link above with a prefix in front of the number, or the workaround to delete the contact and the conversation was not successful.

Resetting the APN settings did not work, nor did using a different messaging app.
Now that you've found a report from someone other than yourself, at least now you know it's probably a bug in LOS.

My suggestion would be to go back to stock, or try on another gsi that doesn't use LOS source code. Or you can stay on LOS and "deal with it" until a bugfix can be found. Even though you may not want to try other things to test further, it's not like you really have a lot of other good options. And besides, trying multiple approaches is the best way to solve problems. In all my years of dealing with various issues on a day to day basis, I've found that's really the only way to get solutions. Think outside the box, as the saying goes. A willingness to try different approaches is all part of the process.
 
  • Like
Reactions: psychofaktory

insestito

Senior Member
Jul 29, 2009
1,077
181
Xiaomi 12T Pro
This GSI works really well on my Galay S22 (SM-S901B)! Everything works flawlessly and runs smoothly! Big thanks to the developer! One thing, though: Whenever I try to register my fingerprint, systemui immediately crashes. Maybe the attached log helps to find the cause? Thanks!
Hi mate, do you finded any bug or somethhing on the S22 exynos?
How is the battery screen on time?
Thanks
 

atlantix1

Senior Member
Sep 27, 2011
117
33
Hi mate, do you finded any bug or somethhing on the S22 exynos?
How is the battery screen on time?
Thanks
Hi, so here are my impressions/advices:

* As far as battery life is concerned I am still in testing phase. But it seems already much better to me, standby drain is much better. But I cannot provide reliable statistics right now.

* I have rooted my device as I need some magisk fixes. So be sure to download a version of this rom which is not pre-rooted. I have patched the firmware file within magisk app and then transferred in the AP slot via odin before patching the recovery and finally flash the system image via fastboot. No problem here.

* Google wallet works with system spoofing enabled in Treble settings app and after flashing the latest safety net fix mod from displax im magisk. However, after flashing the module in magisk you have to clear data from google play services and goole play store. Device is certified here.

* There is a bug with audio recording within camera apps. I have found a magisk module to fix that in a telegram disussion group (s22-gsi-fixes.zip) tohether with some other small fixes. I do not know if I am allowed to post the link to the group here, but you will find the link to the group in the xda thread: https://forum.xda-developers.com/t/...oki-kernel-exynos2200-s22-plus-ultra.4468599/. You have to flash the module and enable "use alternative audio policy" in treble app. Unfortunately, the fix did not work for me. But I found the solution by make a small change in the file "audio_policy_configuration_base.xml" within the module by myself. I can provide further information on that if needed.

However, there are and will be some issues:

* As you probably expect, VoLTE and WoWIFI won't work. Samsung's fault. There is nothing to do about that.

* The camera quality is worse than samsung's stock. But no big problem as I use this gcam go from shamim: https://www.celsoazevedo.com/files/android/google-camera/dev-shamim/f/dl16/. Works really decently, all three lenses, night mode and front facing camera. Not quite as good as the original google camera app and no 60 fps video recording, but hey - the image quality is really fine to me.

* The fingerprint reader does not work as for now on my device. But this issue was fixed with the latest release of TrebleDroid: https://github.com/TrebleDroid/treble_experimentations/releases. I hope for an update for this GSI as TrebleDroid ist too barebones (no Gapps, no spoofing of system status etc.). Until then I use xposed and the face unlock mod you find here on xda. Works fast an reliably.

Everything else seems to work fine, e.g. automatic brightness (a littlebit wanky), hotspot etc. But I have not tested everything as for now. And probably I have forgotten many things here... ;)

I won't go back to OneUI...

Hope that helps!
 
Last edited:
  • Like
Reactions: insestito

insestito

Senior Member
Jul 29, 2009
1,077
181
Xiaomi 12T Pro
Hi, so here are my impressions/advices:

* As far as battery life is concerned I am still in testing phase. But it seems already much better to me, standby drain is much better. But I cannot provide reliable statistics right now.

* I have rooted my device as I need some magisk fixes. So be sure to download a version of this rom which is not pre-rooted. I have patched the firmware file within magisk app and then transferred in the AP slot via odin before patching the recovery and finally flash the system image via fastboot. No problem here.

* Google wallet works with system spoofing enabled in Treble settings app and after flashing the latest safety net fix mod from displax im magisk. However, after flashing the module in magisk you have to clear data from google play services and goole play store. Device is certified here.

* There is a bug with audio recording within camera apps. I have found a magisk module to fix that in a telegram disussion group (s22-gsi-fixes.zip) tohether with some other small fixes. I do not know if I am allowed to post the link to the group here, but you will find the link to the group in the xda thread: https://forum.xda-developers.com/t/...oki-kernel-exynos2200-s22-plus-ultra.4468599/. You have to flash the module and enable "use alternative audio policy" in treble app. Unfortunately, the fix did not work for me. But I found the solution by editing a file called audio_policy_configuration_base.xml within the module by myself. I can provide further information on that if needed.

However, there are and will be some issues:

* As you probably expect, VoLTE and WoWIFI won't work. Samsung's fault. There is nothing to do about that.

* The camera quality is worse than samsung's stock. But no big problem as I use this gcam go from shamim: https://www.celsoazevedo.com/files/android/google-camera/dev-shamim/f/dl16/. Works really decently, even all three lenses, night mode and front facing camera. Not quite as good as the original google camera app and no 60 fps video recording, but hey - the image quality is really fine to me.

* The fingerprint reader does not work as for now on my device Samsung S22. But this issue was fixed with the last release of TrebleDroid: https://github.com/TrebleDroid/treble_experimentations/releases. I hope for an update for this GSI as TrebleDroid ist too barebones for me (no Gapps, no spoofing of system status etc.). Until then I use xposed and the face unlock mod you find here on xda. Works fast an reliably.

Everything else seems to work fine, e.g. automatic brightness (a littlebit wanky), hotspot etc. But I have not tested everything as for now. And probably I have forgotten some things here... ;)

I won't go back to OneUI...

Hope that helps!
I totally agree, in the end I installed Project Elixir, and it works perfect.
Install this camera (bottom of the web) :https://github.com/phhusson/treble_experimentations/wiki/Samsung-Galaxy-S22-(Exynos)
The camera for me... I think it's better than Samsung's
The bbattery is very better than ONE UI, i make about 1-1,5h more screen on time easy, and on IDLE is awesome compared with ONE UI.

Fingerprint not work and face unlock not work also.

What boot.img do you modified with magisk? i can't find it inside the Elixir rom img ...
 
  • Like
Reactions: atlantix1

atlantix1

Senior Member
Sep 27, 2011
117
33
I totally agree, in the end I installed Project Elixir, and it works perfect.
Install this camera (bottom of the web) :https://github.com/phhusson/treble_experimentations/wiki/Samsung-Galaxy-S22-(Exynos)
The camera for me... I think it's better than Samsung's
The bbattery is very better than ONE UI, i make about 1-1,5h more screen on time easy, and on IDLE is awesome compared with ONE UI.

Fingerprint not work and face unlock not work also.

What boot.img do you modified with magisk? i can't find it inside the Elixir rom img ...
Regarding the linked camera: is the front facing camera working?

Because Elixir is also a GSI there is only the system image inside the compressed file you download. What I did to patch the samsung stock boot image and get root was simply to install magisk manager on the phone, extract the AP file from a recent Samsung firmware (you can e.g. download via samfirm reborn or use any of the common firmware sites) on your PC, transfer it to the phone, patch the file via magisk manager, copy it to your PC again, and then flash the patched AP file in the AP slot via ODIN. Then you have a magisk patched kernel plus patched vbmeta. From there you can flash any GSI system image via fastboot and always have root.
 
  • Like
Reactions: insestito

noahhhh

Member
Feb 9, 2017
43
1
Sony Xperia 1
Google Pixel 4 XL
Display settings. Display size & font size. Adjust to suite your preferences. Try different launchers.
nope, it does not work. Such as settings still won't get a split-views like this.
Screenshot_20221109-122731_Settings.png
 

ildar_prophet

Senior Member
Apr 20, 2011
297
45
johan-notes.blogspot.com

m0byn

Member
Feb 13, 2023
30
0
Hello all,
I am new to the custom ROM scene - so please be gentle. However, thanks to @AndyYan I was able to install Lineage OS 20 "light" on my Samsung Galaxy A50 and until now I am amazed by how smooth everything works! Thank you so much!
I do have one question, however, since I did not find any information about that. Does the built in encryption feature of Lineage OS 20 (note, not the "light"!) work on the Samsung Galaxy A50? Now, with the "light" version when clicking on "ecnrypt smartphone", then nothing happens. If it works with the TD-based version I would switch over!
I would be really thankful for any information on that!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    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_*
    3
    I use a similar approach as what @bpham1 outlined to upgrade the stock base of most of my devices, but please only ever think of attempting it if you're sure you can enter bootloader/recovery with key combo from a hot rebooting state. Even then there's still a minute but real possibility that hot rebooting after flashing stock is different from regular hot rebooting.
    For devices where I can't take such risks, I simply stick to a certain stock base until GSIs receive the next major Android update, by then I'd simply start over from a newer stock base.
    Also keep close attention on the flashing progress and reboot timing to interrupt it in time, otherwise stock ROM will try to boot and (even if it boots) ruin userdata.
    1
    Thanks for your assessment @AnonVendetta

    The thought came to me because I had read elsewhere some time ago that the vendor security patch level could only be raised by updating firmware/vendor and that this was probably possible.
    Unfortunately I could not find any info on how to proceed.


    Here it is also mentioned that it is possible. But also here is not mentioned how exactly to proceed:
    Unfortunately, the people who could provide answers in the subforum of the device no longer seem to be very active.


    Basically I share your opinion that it would make more sense to flash the latest Sony firmware clean and then flash the GSI together with the modded vbmeta afterwards.

    My inhibition at the moment is that I have no TWRP available and both FolderSync, as well as Swift Backup and Titanium Backup do not work. So I can't easily make a clean backup and then just restore it.
    Thus, it will be a significantly more complex endeavor....
    I plan to try this approach with a Sony Xperia 1iii. On paper it should work, but any missteps can lead to data loss. I'm more concerned about how long it would take me to restore my working apps. So, if this method works, then it would save me lots of time.

    1) Download stock firmware with XperiFirm

    2) Flash with Newflasher with option to keep userdata

    3) Immediately flash GSI
    1
    Hello bpham1,



    the downtime and duration for the recovery also scare me.

    I would be grateful for a report on your experience if you were able to perform the action successfully.
    The method works successfully on my Sony. I don't use encryption, so your mileage may vary. Just be sure you are familiar with the Newflasher walkthrough.

    I struggle with what combination to boot into fastboot. I keep forgetting not to connect the USB-C cable. Using the cable gets you into Flash mode, and without the cable gets you into Fastboot when you press and hold Volume Down button.

    Good luck!
    1
    Big thanks @AndyYan . I'm using this GSI as my daily driver on a Lenovo Legion Y70 and it works great. I truly appreciate your contribution to this community.
  • 17
    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.

    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
    5
    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_*
    5
    Updated all variants with February security patches and in sync with TD 20230131. [Insert obligatory backup-and-test warning here]
    5
    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.
    4
    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.