• 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
EFS Partition & Restoring a TWRP Backup

I only had the Nandroid backup in TWRP, and it didn't allow a restore. Wouldn't the efs partition be included in that backup? If so, then I do not understand bersems advice above for restoring the old backup on another phone (I have already bought one, waiting for it to arrive shortly): "Dont restore your EFS backup if u have made it on your old phone." How could I avoid doing that if they're part of the Nandroid backup of the old phone? (So much for my understanding of these matters!)

See the text + attachments in S5 - EFS Partition Backup - No Service, No IMEI & No SIM Card Fix].

In TWRP you need to restore only System, Data & Boot partitions. Boot is in fact the kernel on the S5.

The EFS Partition Backup created on a specific S5 device can be restored on that device only if for example it lost it's IMEI or has no service even with a known good SIM card & proper network provider's APN settings.
***
 

Attachments

  • TWRP_Full_Backup_LineageOS_18-1_S5_curiousrom.png
    TWRP_Full_Backup_LineageOS_18-1_S5_curiousrom.png
    161.3 KB · Views: 26
  • TWRP_Restore_Boot_System_Data_LineageOS_18.1_S5_curiousrom.png
    TWRP_Restore_Boot_System_Data_LineageOS_18.1_S5_curiousrom.png
    160.7 KB · Views: 26
Last edited:
  • Like
Reactions: mangokm40

jenssa

Member
Dec 8, 2018
44
13
64
Oslo
EFS Partition



See the text + attachments in S5 - EFS Partition Backup - No Service, No IMEI & No SIM Card Fix].

In TWRP you need to restore only System, Data & Boot partitions. Boot is in fact the kernel on the S5.

The EFS Partition Backup created on a specific S5 device can be restored on that device only if for example it lost it's IMEI or has no service even with a known good SIM card & proper network provider's APN settings.
***
Thanks, I will remember to backup the efs partition when I get the other phone. (I have tried in vain to flash the files you list up as the content in the efs folder (efs.ext4.win, efs.ext4.win.sha2, efs.info & recovery.log files) after first converting them into .tar-files by 7-zip. Odin says Fail! any way I try to flash them. I thought this might revive my soft bricked phone.)

Edit 16/9: Before I transfer Nandroid from the old phone, is there any way to salvage more of the original User Interface and apps? I must confess that the firmware runs a lot more smoothly than the lineageos + gapps, so it would have been great to be able to rip off some of the Samsung Telenor set up and transfer it to the new build. The internet app, for instance, has both a return and a forward button, the camera is better, indeed the whole set up runs a lot smoother. Yet, I need to upgrade from Marshmallow to use certain apps.

Edit 26/9: I finally decided to test restoring the NANDROID backup of the old (soft bricked) S5 on my "new" S5. It worked, though I experienced a freeze that I think was to to finger print scanner problems. I completely wiped and restored once more, and the phone seems to work. (For some reason I was not able to restore the NANDROID that I made of the new phone, though, so there was no way going back). Now I have even installed today's update of Lineageos 18.1, and it seems to be working fine. (Had to sideload magisk in TWRP, though, but that doesn't have any connection with the restoring of the old phone upon the new.) I'll come back with a report if I experience problems. But at least for now it think I can conclude that it is possible to transfer one NANDROID backup from one phone to another of the exact same make. Thanks for all the good help!
 
Last edited:

bersem

Senior Member
Jan 19, 2014
354
159
hi there,

someone noticed low microphone volume on third party apps like messenger, whatsapp ( calls ) ( doesn't hear me well ) ?

@haggertk possible to increase this volumes in the future ( next nightly ? ) or stock values will continue to be used to avoid damages and not to degrade the sound quality ?

@curiousrom cleaned already the mic hole and dont want to tweak mixer file.. :D

Regards !
 
  • Haha
Reactions: curiousrom
S5 Low Mic in Third-party Apps Workaround

...someone noticed low microphone volume on third party apps like messenger, whatsapp ( calls ) ( doesn't hear me well ) ?

@haggertk possible to increase this volumes in the future ( next nightly ? ) or stock values will continue to be used to avoid damages and not to degrade the sound quality ?...

Good luck getting haggertk to modify that mixer_paths.xml system file as that low mic issue was reported by S5 users way back in LineageOS 15.1, 16.0, 17.1 & now 18.1 threads.

Meanwhile this works in LineageOS 18.1 for klte* & survives updates: S5 Mic Boost Magisk Module - Stereo Recordings
***
 
  • Haha
Reactions: bersem

bersem

Senior Member
Jan 19, 2014
354
159

x2k13

Senior Member
hi there,

someone noticed low microphone volume on third party apps like messenger, whatsapp ( calls ) ( doesn't hear me well ) ?

@haggertk possible to increase this volumes in the future ( next nightly ? ) or stock values will continue to be used to avoid damages and not to degrade the sound quality ?

@curiousrom cleaned already the mic hole and dont want to tweak mixer file.. :D

Regards !
Try this:
Works on 18.1 as well, tested by me on my G900F. No Magisk needed. You might want to delete the addon.d survival script 60-mixer.sh in /system (mount the partition first, of course) before you flash the lineage update, because it somehow seems to be faulty (at least on my phone) leading your klte to have no sound at all if you didn't delete it beforehand.

Long story short
1. Delete 60-mixer.sh
2. Flash lineage update .zip
3. Flash micgain .zip
4. Flash whatever additional.zip you need
5. Reboot, have boosted mic and speaker
6. Enjoy
 
  • Like
Reactions: pmduper and bersem

x2k13

Senior Member
That zip file modifies many things without any explanation nor justification.

It's like using a shotgun to kill a fly if one only needs to modify 2 values in mixer_paths.xml to fix the low mic issue.
***
I tried the "2 values" method myself, ended up with no sound at all.
What is it exactly you're critizising?
 
Last edited:
I tried the "2 values" method myself, ended up with no sound at all.

You did not say how you did it exactly so difficult to troubleshoot.

Maybe because not giving permissions rw- r-- r-- 644 to the modified mixer_paths.xml after putting it in /system/vendor/etc/.

Anyway if rooted with Magisk the module is much easier & carefree.
***
 

Attachments

  • MiXplorer_mixer_paths_xml_18.1_S5_curiousrom.png
    MiXplorer_mixer_paths_xml_18.1_S5_curiousrom.png
    191.5 KB · Views: 25

x2k13

Senior Member
You did not say how you did it exactly so difficult to troubleshoot.

Maybe because not giving permissions rw- r-- r-- 644 to the modified mixer_paths.xml after putting it in /system/vendor/etc/.

Anyway if rooted with Magisk the module is much easier & carefree.
***
Not everyone wants their phone to be rooted. You still didn't say what you critizise exactly. What does the .zip alter that you doubt is necessary and why?
 
Not everyone wants their phone to be rooted...

Without being rooted with Magisk one can use TWRP > Advanced > File manager or adb pull to get the file, modify it then put it back in with TWRP or adb push.

What does the .zip alter that you doubt is necessary and why?

About two years ago I downloaded that micgain .zip, uzipped and compared the files in it to the stock files with DiffMerge and found zero justifications for all the mods it makes in the OP of that thread.

It's a vodoo zip mod for believers. :)

Anyway everything sound related on my S5 works fine so I don't see any reasons to modify anything except for slightly higher mic values for recording without distortions.

I am attaching a bird recording I made with the S5 just in front of my house @ 4h am.
***
 

Attachments

  • Bird Chiricoca - Gray-necked Wood-rail.zip
    917.1 KB · Views: 12

bersem

Senior Member
Jan 19, 2014
354
159
Could you check this mixer file @curiousrom :D :D :D ? Modified from mixer_paths_File_Diffs_TheFixItMan_vs_Brunowp8.txt.

Used the @Brunowp8 values !

I was able to copy the mixer file from /system/vendor/ etc with Total Comander & non Rooted )

Boot into TWRP
Mount System
Delete the old mixer file in /system/vendor/etc ( make / made Backup before )
Copy the edited mixer file to /system/vendor/etc
Set permissions to 0644 (mixer file )

Reboot

There is another vendor folder on the root directory ? Im confused now :O
 

Attachments

  • mixer_paths.xml
    44.4 KB · Views: 8
  • Screenshot_20210918-153921_Total_Commander.png
    Screenshot_20210918-153921_Total_Commander.png
    101.5 KB · Views: 25
  • Screenshot_20210918-153947_Total_Commander.png
    Screenshot_20210918-153947_Total_Commander.png
    173.8 KB · Views: 23
  • Screenshot_20210918-153913_Total_Commander.png
    Screenshot_20210918-153913_Total_Commander.png
    101.9 KB · Views: 20
  • Screenshot_20210918-154340_Total_Commander.png
    Screenshot_20210918-154340_Total_Commander.png
    181.5 KB · Views: 20
  • Screenshot_20210918-154309_Total_Commander.png
    Screenshot_20210918-154309_Total_Commander.png
    177 KB · Views: 24
S5 LineageOS 18.1 Update 2021-09-19 - Android Security Bump & Call Forwarding Fix

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

There are quite a few changes as you can see in https://download.lineageos.org/klte/changes/ some do not concern the S5 klte* family but most importantly it includes the monthly Android security bump: Merge tag 'android-11.0.0_r43' into staging/lineage-18.1_merge-android-11.0.0_r43.

After the automatic reboot as seen in the screenshot > Settings > About phone > press on Android version > Android security update: September 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—September 2021 for details about the security fixes.
***

S5 LineageOS 18.1 Call Forwarding Fix!

Thanks to haggertk's commits msm8974-common: libril: initialise RIL_CallForwardInfo to 0 when requesting status and also klte-common: libril: avoid SEGV when requesting call forwarding info in the LineageOS stock Phone app > 3-dots > Settings > Calls > GSM call settings > Call forwarding > Always forward > select contact to forward to > turn on works! :)

Of note as seen in the screenshots with call forwarding active, clicking on the Call Forwarding notification & turning it off a returns a Call settings error - Unexpected response from network but forwarding is disabled anyway and I could receive a call. 🤷‍♂️

That may depend on my specific network provider's response.
***

Contrary to update 2021-06-13 as I posted here and other updates, shortcuts on Home created with the LineageOS Settings widget, a third-party app & to web pages with the stock Browser, Chrome & Edge survived. 🤷‍♂️

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

Attachments

  • Updater_2021-09-19_LineageOS_18-1_S5_curiousrom.png
    Updater_2021-09-19_LineageOS_18-1_S5_curiousrom.png
    324.9 KB · Views: 29
  • Call_Forwarding_Turn_Off_2021-09-19_LineageOS_18-1_S5_curiousrom.png
    Call_Forwarding_Turn_Off_2021-09-19_LineageOS_18-1_S5_curiousrom.png
    252.1 KB · Views: 27
Last edited:

rgrapow

Member
Feb 28, 2018
43
21
S5 LineageOS 18.1 Update 2021-09-19 - Android Security Bump & Call Forwarding Fix
Hi, just to write about my experience:

in my case Ii wasn't like that, I did an OTA update over 2021-08-15 and I had a boot stuck and/or boot loop (obviously magisk had to do) so I had to flash this by the following (steps), but before that, I did a restore from a TWRP backup:

1.- ROM (2021-09-19)
2.- Gapps (latest version of that moment)
3.- Magisk
4.- Clean Dalvik/cache

All went ok.

Thank you for your guidance, it helped me a lot.
 
  • Like
Reactions: curiousrom

zimral.xda

Senior Member
Apr 5, 2021
99
56
Samsung Galaxy S5
Google Pixel 2
Hi, i updated my dev phone to build 2021-09-19 coming from 2021-09-12. Config is SM-G900F german/european version, no vendor brand, TWRP 3.5.2_9-0, open gapps "pico", no magisk, etc. All good, no problem occurs.
Hi there , just did my productive device, going to 2021-09-19 coming from 2021-09-12. 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.
 

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
    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"
    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...
    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.
    ***