• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][OFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)

Search This thread

haggertk

Senior Member
2okPze5.png



LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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. You will need to provide your own Google Applications package (gapps) . LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

Device source code:
Kernel source code:

Build Compatibility:
The noted models are the only ones supported. If you have a model that isn't listed and ask politely then I might work to add compatibility.
BuildModel
klteSM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8
klteactivexxSM-G870F
klteaioSM-G900AZ, SM-S902L
kltechnSM-G9006V, SM-G9008V
kltechnduoSM-G9006W, SM-G9008W, SM-G9009W
klteduosSM-G900FD, SM-G900MD
kltedvSM-G900I, SM-G900P
kltekdiSC-04F, SCL23
kltekorSM-G900K, SM-G900L, SM-G900S

Downloads:
Installation Instructions:
Reporting Bugs:
Compatibility Notes:
  • Bootloader version doesn't matter. Anyone who tells you so doesn't know what they are taking about. My Developer Edition G900V is still running the original 4.4.2 KK aboot. My G900W8 is running the latest 6.0.1.
  • All builds except for klteactivexx and klteaio MUST be running a marshmallow (6.0.1) radio for RIL to work. If you are about to report that RIL/radio isn't working then I pretty much guarantee this is your issue.
  • You MUST be running a marshmallow (6.0.1) NON-HLOS for the fingerprint reader to work. If you are about to report a fingerprint reader problem then you either have old firmware (update it), your /data was previously encrypted and you performed a "clean" flash without FORMATTING /data (start over and FORMAT /data), or your reader is just broken.
  • External SD cards don't support POSIX (ext*, f2fs) or NTFS filesystems anymore. If this affects you then just bite the bullet, copy any data off you really want to save, and reformat as exfat.
  • The latest TWRP seems like it works, but if someone has issues then perhaps try using the actual supported recovery.
Donations:
  • I absolutely don't personally accept them. If you really feel that this work deserves it, then find a local food bank or animal shelter/rescue and throw some money their way. You can also throw some the way of LineageOS, but we're actually doing pretty well right now.
 
Last edited:

Massedil

Senior Member
Dec 7, 2016
60
18
Paris
Hi,

Thanks for maintaining our phone !

I just upgraded to LineageOS 18.1 as I explained in this post and got stuck in the lock screen :

Do you know how can I solve this ?

Logcat :
https://paste.chapril.org/?86ff7c1c0ddf2642#5BDBqxDBmYJKjheUpjDSvhBvDL3EGv4ALYQaECGPwkNq
 

haggertk

Senior Member
Hi,

Thanks for maintaining our phone !

I just upgraded to LineageOS 18.1 as I explained in this post and got stuck in the lock screen :

Do you know how can I solve this ?

Logcat :
https://paste.chapril.org/?86ff7c1c0ddf2642#5BDBqxDBmYJKjheUpjDSvhBvDL3EGv4ALYQaECGPwkNq
Weird that you are getting caught by that, I explicitly tested the upgrade path. Try deleting the lockscreen files from recovery (/data/system/gatekeeper.*.key, /data/system/locksettings.db*). If that doesn't work, wipe data.
 
  • Sad
Reactions: curiousrom

Massedil

Senior Member
Dec 7, 2016
60
18
Paris
Weird that you are getting caught by that, I explicitly tested the upgrade path. Try deleting the lockscreen files from recovery (/data/system/gatekeeper.*.key, /data/system/locksettings.db*). If that doesn't work, wipe data.

I don't have any .key file, maybe it is the problem ?

Code:
/data/system # find /data/system -name '*key*'
/data/system/sensor_service/hmac_key
/data/system/dropbox/[email protected]
/data/system/dropbox/[email protected]
/data/system/dropbox/[email protected]
/data/system/dropbox/[email protected]
/data/system/dropbox/[email protected]
/data/system/dropbox/[email protected]
/data/system/recoverablekeystore.db

If it can helps :

Code:
sqlite3 locksettings.db
sqlite> SELECT * FROM locksettings ;
1|lockscreen.disabled|0|0
2|migrated|0|true
3|migrated_user_specific|0|true
4|lockscreen.password_type_alternate|0|0
5|migrated_biometric_weak|0|true
6|migrated_lockscreen_disabled|0|true
7|migrated_frp|0|1
8|lockscreen.enabledtrustagents|0|org.lineageos.profiles/.ProfilesTrustAgent
9|lockscreen.password_type|0|NNNNNN
11|sp-handle|0|NNNNNN
12|lockscreen.profilechallenge|0|1
13|lockscreen.passwordhistory|0|
14|lockscreen.istrustusuallymanaged|0|1
15|lockscreen.power_button_instantly_locks|0|0
22|lock_screen_owner_info_enabled|0|1
23|lock_screen_owner_info|0|XXXXXXXXXX
 

Massedil

Senior Member
Dec 7, 2016
60
18
Paris
Weird that you are getting caught by that, I explicitly tested the upgrade path. Try deleting the lockscreen files from recovery (/data/system/gatekeeper.*.key, /data/system/locksettings.db*). If that doesn't work, wipe data.
Thanks !

I just deleted /data/system/locksettings.db and I can now access the phone.

I have kept a copy of this database before removing, if you need it for investigation I can send it to you.

Thanks again !
 

ludwig83

Member
May 9, 2018
25
13
Hey guys! I'm now on 18.1 (of course a clean flash) ....great ROM so far but I have the same problem as on 17.1 ...whenever I lose GSM it does not come back ...I receive the message that SIM Card is missing - service not available (Keine SIM-Karte - Dienst nicht verfügbar) ...someone else with a klteactivexx here with the same experience? Never had a problem with Lineage 16.0 ...hope for someone who can confirm my problem...

 

zimral.xda

Senior Member
Apr 5, 2021
101
56
Samsung Galaxy S5
Google Pixel 2
2okPze5.png




Donations:
  • I absolutely don't personally accept them. If you really feel that this work deserves it, then find a local food bank or animal shelter/rescue and throw some money their way. You can also throw some the way of LineageOS, but we're actually doing pretty well right now.

Many THX for givin' the good old S5 a continued life again. Will look for food/money for the local animal shelter, our cat comes from there :)
 
  • Like
Reactions: jmh2002

haggertk

Senior Member
@haggertk thank you for your amazing work !! One question: Why arent navigation gestures enabled by default ?? Have to edit build.prop file to get it..

Regards !
The Galaxy S5 has physical keys, in particular, the home key. Since this key cannot be "hidden", our standards are that key disabler must not be able to be activated through normal user interaction.
 

Tenaya43

Member
Dec 20, 2012
15
8
First, I want to thank Haggertk and LineageOS for keeping the Galaxy S5 alive.

DISCLAIMER: I don’t know as much as I’d like about what’s behind the Android curtain. I’m especially ignorant about the Android file system, but I’m learning.

We’re in the process of switching from older Galaxy S2 Skyrockets (we keep our phones waaaaay too long) to SM‑G900Ts (newer, but still pretty old). For the past month or so, all three of our SM-G900Ts have been running unofficial 18.1 (20201225) with NikGapps Pico. This morning, I downloaded LineageOS 18.1-20210425-nightly-klte-signed and installed it on two of our SM-G900Ts via TWRP (which I had previously installed via ODIN).

We have two problems we didn’t have before:
  1. In 20210425, the 18.1 camera app doesn’t work. It tries to open (quick flash of a black background), then immediately stops. Trying the camera app a second time, it again tries to start, again immediately stops and then throws up a "camera keeps stopping" message. If I tap OK, the message closes and the phone continues to work normally. The camera app in unofficial 18.1 works fine (one of our three phones hasn’t been updated yet). The problem doesn’t seem to be hardware: Open Camera works fine on 20210425 after being side loaded.
  2. The Play Store app (installed by either Open Gapps or NikGapps) categorically refuses to install apps on 20210425, complaining there’s not enough space. The app offers to delete other apps to make space, but since there aren’t any (yet), it can’t. The problem doesn’t seem to be related to the size of the app: I tried to install a really small app (APK = 3.3KB) and that failed, too. The problem also doesn’t seem to be related to user partition space, I side loaded DiskInfo and it says Data/data/user/0 has 10.9GB free. Further, I can side load apps via APK: The not-small Open Camera, for example. The Play Store installs/installed apps just fine on 20201225.
Another quirk is that the phone s still running 20201225 refuses to run Google Maps (stops immediately after trying to start).

Yet another clue may be the fact that I haven’t been able to recreate whatever combination of OS version, GAPPS version and procedure I used to create the phone that’s still running 20210425. Perhaps I did something differently this time.

Does anyone else have these problems? If so, are there fixes? Did I do something wrong? Is there something I need to do differently?

Thank you in advance,

Tenaya
 
  • Like
Reactions: Andresine
First, I want to thank Haggertk and LineageOS for keeping the Galaxy S5 alive.

DISCLAIMER: I don’t know as much as I’d like about what’s behind the Android curtain. I’m especially ignorant about the Android file system, but I’m learning.

We’re in the process of switching from older Galaxy S2 Skyrockets (we keep our phones waaaaay too long) to SM‑G900Ts (newer, but still pretty old). For the past month or so, all three of our SM-G900Ts have been running unofficial 18.1 (20201225) with NikGapps Pico. This morning, I downloaded LineageOS 18.1-20210425-nightly-klte-signed and installed it on two of our SM-G900Ts via TWRP (which I had previously installed via ODIN).

We have two problems we didn’t have before:
  1. In 20210425, the 18.1 camera app doesn’t work. It tries to open (quick flash of a black background), then immediately stops. Trying the camera app a second time, it again tries to start, again immediately stops and then throws up a "camera keeps stopping" message. If I tap OK, the message closes and the phone continues to work normally. The camera app in unofficial 18.1 works fine (one of our three phones hasn’t been updated yet). The problem doesn’t seem to be hardware: Open Camera works fine on 20210425 after being side loaded.
  2. The Play Store app (installed by either Open Gapps or NikGapps) categorically refuses to install apps on 20210425, complaining there’s not enough space. The app offers to delete other apps to make space, but since there aren’t any (yet), it can’t. The problem doesn’t seem to be related to the size of the app: I tried to install a really small app (APK = 3.3KB) and that failed, too. The problem also doesn’t seem to be related to user partition space, I side loaded DiskInfo and it says Data/data/user/0 has 10.9GB free. Further, I can side load apps via APK: The not-small Open Camera, for example. The Play Store installs/installed apps just fine on 20201225.
Another quirk is that the phone s still running 20201225 refuses to run Google Maps (stops immediately after trying to start).

Yet another clue may be the fact that I haven’t been able to recreate whatever combination of OS version, GAPPS version and procedure I used to create the phone that’s still running 20210425. Perhaps I did something differently this time.

Does anyone else have these problems? If so, are there fixes? Did I do something wrong? Is there something I need to do differently?

Thank you in advance,

Tenaya
you somehow have a media storage issue they changed the permission set with the way apks communicate with "sdcard" internal storage for less vulnerabilities at the user app level....and stopped external sd support....we had a legacy media patch for old devices....now heres the catch if you flashed with the external sdcard in with older TWRP it thinks that external is internal SD then when u boot internal is blank external don't work and the play store thinks you used up....also any music app doesn't see media... this happened to me... what i did was cracked back and format data and wiped all partitions took external out wiped everything in twrp...went to download mode in odin reflashed full four file G900TUVU1GQC2_G900TTMB1GQC2_G900TUVU1GQC2_HOME.tar.md5
somethimes its nice to boot Android 6.01 then look in the newer threads and see how people complain so much about this and that and remember The TOUCHWIZ days....lol....

Then flashed new 18.1 clean using the lineage recovery..... so that means I had to flash twrp once in odin to install the new recovery file to install the official build because I dont like hemidall
... with lineage gapps https://androidfilehost.com/?w=files&flid=322935
 
  • Like
Reactions: Andresine

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    S5 LineageOS 18.1 Update 2021-10-10 - Android Security Bump

    Using the built-in Updater I OTA updated S5 G900M LineageOS 18.1 klte build 2021-09-19 + MindTheGapps + Magisk 23.0 + TWRP 3.5.2_9-0 to build 2021-10-10: everything went smoothly & GApps + Magisk survived the update.

    There are quite a few changes listed in https://download.lineageos.org/klte/changes/ but most of them do not concern the S5 klte* family.

    Most importantly it includes the monthly Android security bump: Merge tag 'android-11.0.0_r46' into staging/lineage-18.1_merge-android-11.0.0_r463.

    After the automatic reboot as seen in the screenshot > Settings > About phone > press on Android version > Android security update: October 1, 2021.

    The Vendor security patch level just below it remains @ August 1, 2017 because the vendor is Samsung & it is not publishing security patches for it's S5 proprietary hardware related blobs anymore since August 2017.

    See Android Security Bulletin—October 2021 for details about the security fixes.

    Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 klte* up to date. :cool: 👍
    ***

    I found a weird workaround fix for my recurring Quick tiles & status bar curtain long press System UI crashing but that's for an other posts.
    ***
    4
    Good morning, yesterday evening i updated my productive device to nightly build 2021-09-26 coming from 2021-09-19. Config is SM-G900F german/european version, no vendor brand, LOS recovery, no gapps, no magisk, etc. All good, no problems so far.
    THX Mr. Haggertk.
    4
    A12 any expectations when a beta version is released for our S5 I would like to try it
    I personally plan to start looking for LOS19.x (or whatever the name will be) in the LATE march/april timeframe.
    If its there then, fine. If not, life will go on as usual, earth will continue to rotate and our sun will continue to burn many many tons of hydrogen per second and so on...
    4
    A12 any expectations when a beta version is released for our S5 I would like to try it
    when it's ready, obviously you don't know the golden rule "never ask an ETA"
    3
    On the subject of the Samsung Galaxy S5 only having 2GB of RAM and therefore a 'lack of resources' - I totally agree.

    Although I have found some work arounds that vastly improve the situation for me and my use.

    - Firstly as a general point I'm very strict about which apps are able to run in the background. In general this is the biggest problem. Although I do use the phone daily and normally and do still have quite a few background apps. In general I'm also not to agressive about how much multi tasking I try to do at once. I try to use an app, close it, and then open a different one.

    - I also try not to install apps that I don't use, or that I can maybe use via a browser instead. I'm also thorough about disabling apps that I can't uninstall but don't need, as well as killing apps that I only use periodically. I've also tried preventing some apps from starting at boot (by using something like SDMaid), but of course just running a 'kill apps' after boot solves that too.

    - For apps that I use regularly but which don't need to run in the background for any purpose (notifications, etc) I have set App Info > Advanced > Battery > Background Restriction > to Restricted.
    This enables the app to open much faster than if it were killed, but prevents it from using any resources if it's not open and in use.

    - Finally what has helped the most is a tweaking app available here on XDA called HEBF. I'm not an expert but I've used this to set several specific tweaks which have made an enormous difference, such as:

    - Low RAM Device Flag
    - Virtual Memory, increase Z-RAM
    (I didn't notice any battery hit from extra CPU use, but I did notice better memory management)
    - Low Memory Killer, change all parameters

    In the case of the Low Memory Killer I changed a lot of parameters through trial and error because I do have a few services that I wanted to always run in the background without fail and they would often get killed despite various measures to prevent this. I rarely if ever have that problem anymore with the tweaked settings.

    Anyway, just some info from my experience which might be useful to other users too.

    Thanks to everyone one who has helped me here on XDA including @haggertk for the continued support as well as a lot of other developers who have provided some great apps and other users for their experience and comments too.

    :)
  • 38
    2okPze5.png



    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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. You will need to provide your own Google Applications package (gapps) . LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

    Device source code:
    Kernel source code:

    Build Compatibility:
    The noted models are the only ones supported. If you have a model that isn't listed and ask politely then I might work to add compatibility.
    BuildModel
    klteSM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8
    klteactivexxSM-G870F
    klteaioSM-G900AZ, SM-S902L
    kltechnSM-G9006V, SM-G9008V
    kltechnduoSM-G9006W, SM-G9008W, SM-G9009W
    klteduosSM-G900FD, SM-G900MD
    kltedvSM-G900I, SM-G900P
    kltekdiSC-04F, SCL23
    kltekorSM-G900K, SM-G900L, SM-G900S

    Downloads:
    Installation Instructions:
    Reporting Bugs:
    Compatibility Notes:
    • Bootloader version doesn't matter. Anyone who tells you so doesn't know what they are taking about. My Developer Edition G900V is still running the original 4.4.2 KK aboot. My G900W8 is running the latest 6.0.1.
    • All builds except for klteactivexx and klteaio MUST be running a marshmallow (6.0.1) radio for RIL to work. If you are about to report that RIL/radio isn't working then I pretty much guarantee this is your issue.
    • You MUST be running a marshmallow (6.0.1) NON-HLOS for the fingerprint reader to work. If you are about to report a fingerprint reader problem then you either have old firmware (update it), your /data was previously encrypted and you performed a "clean" flash without FORMATTING /data (start over and FORMAT /data), or your reader is just broken.
    • External SD cards don't support POSIX (ext*, f2fs) or NTFS filesystems anymore. If this affects you then just bite the bullet, copy any data off you really want to save, and reformat as exfat.
    • The latest TWRP seems like it works, but if someone has issues then perhaps try using the actual supported recovery.
    Donations:
    • I absolutely don't personally accept them. If you really feel that this work deserves it, then find a local food bank or animal shelter/rescue and throw some money their way. You can also throw some the way of LineageOS, but we're actually doing pretty well right now.
    10
    SDcard corruption may be caused by a recent Google security patch. I experienced this once with the "new" unofficial LOS17 for the Samsung P605, coming from unofficial 14.1,where this never happened before. But others started complaining about the same issue, after this antique rom got a recent security patch.
    It's (likely) not. I've found an issue in the legacy paths of the recent sdfat (Samsung exfat driver) revision. I haven't been able to recreate the bug/assert after the fix. After getting a second confirmation I'll upload the merge the change.

    Every kernel < 4.8.y that had updated to sdfat 1.4.5 is affected.
    9
    S5 LineageOS 18.1 Update 2021-05-09 - Security Bump, Camera U.I. Fix & Kill App Option

    Using the built-in Updater I OTA updated S5 G900M LineageOS 18.1 klte build 2021-05-02 + MindTheGapps + Magisk 22.1 + TWRP 3.5.2_9-0 to build 2021-05-09: everything went smoothly & GApps + Magisk survived the update.

    There are a bunch of changes as you can see in https://download.lineageos.org/klte/changes/ but of note:

    After the automatic reboot as seen in the screenshot > Settings > About phone > press on Android version > Android security update: May 5, 2021.

    The Vendor security patch level just below it remains @ August 1, 2017 because the vendor is Samsung & it is not publishing security patches for it's S5 proprietary hardware related blobs anymore since August 2017.

    See Android Security Bulletin - May 2021 for details about the security fixes.

    With the change Snap: use translucent control background on 16:9 the stock camera is showing the full frame preview again (screenshot). There are other minor Camera changes.

    Interesting also there is a new Kill foreground app option in > Settings > System > Buttons > for Home, Back & Recents buttons which is useful when an app is frozen or you want to prevent it from using some RAM in the background (screenshot). Note that it may make it slower to open that killed app the next time you want to use it.

    BTW you can create a direct link to Updater & much more with the LineageOS Settings widget. I stacked a few of them on Home to create a LineageOS shortcut folder for quick access.

    Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 up to date. :cool: 👍
    ***
    8
    Galaxy S5 LineageOS 17.1 Upgrade to 18.1 + OTA Update Success Using TWRP

    I upgraded my S5 7 days ago and did not lose any apps & settings: Galaxy S5 G900M LineageOS 17.1 klte build 2021-04-18 + Open GApps Pico + TWRP 3.5.2_9-0 >>> LineageOS 18.1 klte build 2021-04-25 + MindTheGapps for Android 11 ARM + Magisk 22.1 which I just OTA updated to LineageOS 18.1 klte build 2021-05-02: everything went smoothly & GApps + Magisk survived the update.

    The only major issue is the unusable stock Camera as described here: LineageOS Snap Camera U.I. Not Showing the Full Image Preview. Edit: Good news, following a conversation with a dev this commit was merged & will be included in next build: Snap: use translucent control background on 16:9.

    Note: three S5 users so far AFAIK, including @Massedil in his post here, reported not being able to unlock their devices after upgrading to 18.1 from 17.1. I always disable screen & SIM locks before an update or upgrade just to remove variables that may go wrong.

    Old versions of TWRP may fail to apply OTA updates. See How To Update TWRP Using TWRP Itself.

    BTW don't install the TWRP app when offered in TWRP as it may causes bootloop because LineageOS is enforcing priv-app whitelisting rules.

    Several S5 klte variants users reported failed to boot on 17.1 with a modem older than Android 6.0.1. This may also cause No Network or No Service issues on 17.1 & 18.1. See S5 Odin Flashable Modem & Bootloader.

    Also before a major upgrade to a higher version but not before regular updates: Magisk > Uninstall > Restore images to preserve my Magisk settings & modules while disabling Magisk (screenshot).

    Re-flashed Magisk-22.1.zip after successful boot to System after the upgrade.

    MindTheGapps is similar to Open GApps Nano. See Open GApps Package Comparison.

    Searching apps with Google in /System:
    • Android Accessibility Suite
    • Android Auto
    • Android Setup
    • Data Transfer Tool
    • Exchange Services
    • Google (search app)
    • Google Calendar Sync
    • Google Contacts Sync
    • Google Partner Setup
    • Google Play services
    • Google Play Store
    • Google Services Framework
    • Google Text-to-speech Engine
    • Market Feedback Agent
    • Markup
    You can also download the MindTheGapps package, unzip & search it with apk.

    You can disable the Google's search app with it's optional personal data hungry Assistant in it's app info. Which I did because it has too many running services for my taste.

    AFAIK from the available Open GApps for Android 11 test builds 20210130 @ the present, only the Pico package was reported as issue free in the Open GApps support thread on XDA: GAPPS DAILY Open GApps for Android; All Android Versions & Devices.

    I have been an Open GApps Pico user for years on several devices but since there are no official releases for Android 11 @ the present, I decided to test MindTheGapps because that's what LineageOS links to @ the present in https://wiki.lineageos.org/gapps.html and wanted to post about it.

    See https://wiki.lineageos.org/devices/ > {device} > Upgrade to a higher version of LineageOS.

    After a full TWRP backup (including the important EFS partition but except the Cache) & triggering a fresh Google Backup* (Settings > System > Advanced > Backup in 17.1), I did the same steps as described in that upgrade guide except that I use TWRP 3.5.2_9-0 so sideload must be started manually on the S5 before sideloading from the computer: TWRP > Advanced > ADB Sideload > Swipe to Start Sideload.

    Or simply copy the files to the device & flash from there using TWRP.

    To make the TWRP backup smaller I use SD Maid > AppCleaner to clear the cache of all apps & make sure to delete all downloaded updates in Updater by long pressing them or if rooted move them from /data/lineageos_updates/ to external or internal SD Card.

    In case of failing to boot you can restore only the System, Data & Boot (boot.img is actually the kernel) partions from the full backup.

    Obviously there are other backup methods but that's the one I use since a couple of years & restored them both successfully.

    On some devices, some versions of TWRP do not work well with LineageOS 18.1 and the Lineage recovery is recommended in those cases but on my S5 klte, TWRP wins hands-down with it's backup/restore feature, File Manager, installing both manually or via sideload & applying successfully OTA updates so I don't see any reasons for switching to the Lineage recovery @ the present.

    Tip: to make the S5 18.1 U.I. faster & more fluid when opening the apps drawer, scrolling through home pages, opening Settings, etc: > Settings > Accessibility > toggle on Remove animations.

    Try it before & after as fast as you can to see the difference.

    *: Warning for people using a pattern lock screen see this bug report: Google cloud backup cannot be restored when using a 4x4, 5x5 or 6x6 lock screen pattern
    ***

    Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 up to date. :cool: 👍
    ***
    8
    S5 LineageOS 18.1 Update 2021-10-10 - Android Security Bump

    Using the built-in Updater I OTA updated S5 G900M LineageOS 18.1 klte build 2021-09-19 + MindTheGapps + Magisk 23.0 + TWRP 3.5.2_9-0 to build 2021-10-10: everything went smoothly & GApps + Magisk survived the update.

    There are quite a few changes listed in https://download.lineageos.org/klte/changes/ but most of them do not concern the S5 klte* family.

    Most importantly it includes the monthly Android security bump: Merge tag 'android-11.0.0_r46' into staging/lineage-18.1_merge-android-11.0.0_r463.

    After the automatic reboot as seen in the screenshot > Settings > About phone > press on Android version > Android security update: October 1, 2021.

    The Vendor security patch level just below it remains @ August 1, 2017 because the vendor is Samsung & it is not publishing security patches for it's S5 proprietary hardware related blobs anymore since August 2017.

    See Android Security Bulletin—October 2021 for details about the security fixes.

    Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 klte* up to date. :cool: 👍
    ***

    I found a weird workaround fix for my recurring Quick tiles & status bar curtain long press System UI crashing but that's for an other posts.
    ***