[GSI][13] LineageOS 20 TrebleDroid-based

Search This thread
By:
Advanced…
A

atlantix1

Senior Member
Sep 27, 2011
117
34
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: 9
Last edited:
P

psychofaktory

Senior Member
Aug 22, 2018
116
18
Samsung Galaxy S III I9300
Sony Xperia XA2
AnonVendetta said:
Have you tested with any other non-LOS gsis? If so, same issue? What about testing on stock firmware?
Click to expand...
Click to collapse
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:
gitlab.com

Cannot send texts after upgrade to lineageOS 20 from 19, Moto X4 (payton) (#5391) · Issues · LineageOS / issues / android · GitLab

Expected Behavior After upgrading payton from lineageOS 19 -> lineageOS 20 I should be able to send texts. ...
gitlab.com gitlab.com
 
xavier.miller

xavier.miller

Senior Member
Oct 2, 2014
56
25
www.xaviermiller.be
psychofaktory said:
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.
Click to expand...
Click to collapse
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
 
P

psychofaktory

Senior Member
Aug 22, 2018
116
18
Samsung Galaxy S III I9300
Sony Xperia XA2
xavier.miller said:
I have found a workaround : if I go to plane mode then back, I can resend the blocked SMS.
Click to expand...
Click to collapse
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.
 
A

AnonVendetta

Senior Member
Apr 29, 2016
1,565
563
psychofaktory said:
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.
Click to expand...
Click to collapse
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
I

insestito

Senior Member
Jul 29, 2009
1,083
181
Xiaomi 12T Pro
atlantix1 said:
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!
Click to expand...
Click to collapse
Hi mate, do you finded any bug or somethhing on the S22 exynos?
How is the battery screen on time?
Thanks
 
A

atlantix1

Senior Member
Sep 27, 2011
117
34
insestito said:
Hi mate, do you finded any bug or somethhing on the S22 exynos?
How is the battery screen on time?
Thanks
Click to expand...
Click to collapse
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: joaofl and insestito
I

insestito

Senior Member
Jul 29, 2009
1,083
181
Xiaomi 12T Pro
atlantix1 said:
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!
Click to expand...
Click to collapse
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
A

atlantix1

Senior Member
Sep 27, 2011
117
34
insestito said:
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 ...
Click to expand...
Click to collapse
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

noahhhh

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

ildar_prophet

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

m0byn

Senior Member
Feb 13, 2023
73
13
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!
 
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
475K
元
元老鼠-鼠王
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