[OFFICIAL] LineageOS 17.1 for Galaxy S5 klte + Variants

Search This thread

ludwig83

Member
May 9, 2018
17
10
Hello!
I own a G870F / klteactivexx and went from 16.1 and TWRP to 17.1 and LIneageos Recovery (clean flash). I would say 2 or 3 months ago...everything works fine except:
Whenever I lose GSM (in the garage or when im in the coutryside) it does not come back ...i get the message that Sim Card is missing?? After Power OFF/ON - everything works again...
Never had that problem with 16.1 / Baseband should be ok - G870FXXU1BQA1
Went for a new Sim Card 2 weeks ago...did not resolve the issue - its T-Mobile / Magenta
Someone out there with a good idea how to deal with?
Unfortunately there is no extra S5 Active Thread ....i hope its ok to post it here...THX
 
Last edited:
  • Like
Reactions: Andresine
S5 klte - Magisk 22.0 Not Surviving Update

Update 2021-03-14 uninstalls Magisk

Just flashed magisk 21.4 and reflashed klte 03-14 lineageOS with twrp 3.3.1-0; addon.d script worked as expected. What was your setup?

Magisk 21.4 stable survived updates & Magisk 22.0 stable does not on the S5 klte family.

I dirty flashed build 2021-03-14 over Galaxy S5 G900M LineageOS 17.1 klte build 2021-02-28 + Open GApps Pico + Magisk 22.0 + TWRP 3.5.0 recovery and as you can see in the attached TWRP screenshot, it reports successfully running the Magisk 22.0 addon.d survival script but after rebooting to system the Magisk app reports that Magisk is not installed & my modules were not applied.

I tried reinstalling the Magisk-v22.0.apk app & rebooting but still no Magisk enabled.

It was the same as posted previously in Magisk 22.0 Not Surviving OTA Update when OTA updating to 2021-02-28: I had to rename Magisk-v22.0.apk to Magisk-v22.0.zip & flash it with TWRP.
***
 

Attachments

  • TWRP_Magisk_22-0_addon.d_S5_17-1_curiousrom.png
    TWRP_Magisk_22-0_addon.d_S5_17-1_curiousrom.png
    228.2 KB · Views: 17
Last edited:

Zytrel

Senior Member
Jun 17, 2012
116
87
Just a heads up for anyone having trouble with Wear OS being stuck at the splash screen. It turns out that this semms to be related to the version of OpenGapps installed. I tried upgrading to the latest Lineage (17.1-20210314) using the current latest Version of OpenGapps (arm-10.0-nano-20210314), and I encounted the above mentioned problem with Wear OS. Reinstalling the very same version of Lineage, but instead using OpenGapps arm-10.0-nano-20210206 fixed the issue and Wear OS starts normally again.

Regards,
Zy.
 

Andresine

Senior Member
Mar 2, 2017
71
18
And where is the problem in reinstalling magisk after updating the rom? It takes a minute. Obviously it is a magisk 22 problem not from the rom.
 
Re: S5 klte - Magisk 22.0 Not Surviving Update

And where is the problem in reinstalling magisk after updating the rom?...

It's easy to workaround & manually reflash Magisk but it's still an issue as it's supposed to be automatic.

Obviously it is a magisk 22 problem not from the rom.

Not so obvious because if it was an issue with Magisk 22.0 for all devices then there would be a ton of reports by all kind of users & devices in the Magisk General Support / Discussion thread.

And if in TWRP the Magisk 22.0 addon.d survival script is reported as successful then LineageOS maybe is breaking it when booting. And/or the log is wrong.

So there are 4 variables in this case & they interact & depend on each other.

Not so easy to troubleshoot.
***
 
  • Like
Reactions: dcarvil
Just a heads up for anyone having trouble with Wear OS being stuck at the splash screen. It turns out that this semms to be related to the version of OpenGapps installed. I tried upgrading to the latest Lineage (17.1-20210314) using the current latest Version of OpenGapps (arm-10.0-nano-20210314), and I encounted the above mentioned problem with Wear OS. Reinstalling the very same version of Lineage, but instead using OpenGapps arm-10.0-nano-20210206 fixed the issue and Wear OS starts normally again.

Regards,
Zy.

Thanks for the heads up. 👍

Maybe you could report that here so an Open GApps dev may see it:

 

gretchen.m

New member
Sep 16, 2020
3
1
My new SD card arrived shortly and it's the same issue with the new one. Phone keeps crashing when I'm doing intensive writing to the SD card, like making backups with Titanium or Signal.

When I insert the SD card into a card reader and repair the broken card under Win10 and put it back in the phone, I can use it without formatting it with Android and almost all files are present.



Well, that confirms my experience. This also means, not using a SD card at all will prevent crashes like this?
Is there an issue on Github or elsewhere about this? Can we contribute somehow?

Let's say I go the same way and flash the kernel you mentioned, will the next LOS update be a compatibility problem or will the update just overwrite the other kernel and everything is back to completly LOS? (I haven't flashed a kernel yet, just complete ROMs.)
I'm experiencing the same SD card issue (S5 Duos, Lineage OS build from 13/03/21): The issue already happened 2 times - 1st time when running Titanium backup, 2nd time when running OAndBackup.

Luckily the workaround with "repair SD card" under windows worked for me as well -- the first time I used windows in private life after several years of abstinence.

If there is any place where I can help (report the bug, test fixes, ...), please let me know. Installing a ROM different from the official lineageos one unfortunately is not an option for me.
 
  • Like
Reactions: Eadn33

chillipig

Member
Jun 22, 2015
21
1
Having done a clean install on my S5 DUOS (most up to date stock ROM+TWRP+Magisk+gapps nano) I have found 17.1 sometimes reboots after a few seconds of pressing power then boots OK, only for it to happen again a few boots later, the phone is not encryped and it didnt happen on 16.0 (which instead used to crash every other time I shut down.)
As I couldnt find a mention elsewhere I assumed it might be a hardware problem and such being my desire for a dual SIM phone with a removable battery (of which I have a collection) I got another one off ebay and flashed that one only to see the same problem.
The new one was the Arabic revision whereas the first was Russian although that probably doesnt matter. I can live with some of the known issues (not sure about bluetooth) but I kind of foresee that one off bootloop becomeing a reocurring bootloop just at the wrong moment.
Has anyone else seen this or resolved it?

Thanks.
 
Unwanted Reboot - Power Button

...clean install on my S5 DUOS (most up to date stock ROM+TWRP+Magisk+gapps nano) I have found 17.1 sometimes reboots after a few seconds of pressing power then boots OK, only for it to happen again a few boots later, the phone is not encryped...

I'm not sure I understand: are you saying that if you use the Power button to turn off the screen for example then your S5 reboots by itself? What else are you doing with that button exactly?

To try to find the reason why you have this issue connect your device to a computer and try capturing a continuous logcat that will be saved in the folder where you are running adb when the device turns off or reboots or until you stop it with ctrl+c:

adb devices

adb logcat > logcat_Unwanted_Reboot.txt

Then open the logcat in Notepad++, WordPad or similar & search it with reboot or chatty or crash or Beginning of crash or killing for example, etc.

Or use an app on the phone like MatLog (also available on F-Droid - attached a screenshot) or Logcat Extreme to record the crash & reboot.

MatLog requires root permission or if you don't have root, connect to a computer & copy/paste this in adb to grant the required permission:

adb shell pm grant com.pluscubed.matlog android.permission.READ_LOGS

Reboot to make the logcat shorter & more relevant, MatLog > 3-dots > File > Record then reproduce the problem & after the device reboots > internal sdcard > matlog > saved_logs.

Or press on the MatLog icon to create a Record shortcut.

You could zip the logcat & attach it to a reply & maybe I could find some clues in it.
***
 

chillipig

Member
Jun 22, 2015
21
1
Unwanted Reboot - Power Button



I'm not sure I understand: are you saying that if you use the Power button to turn off the screen for example then your S5 reboots by itself? What else are you doing with that button exactly?

To try to find the reason why you have this issue connect your device to a computer and try capturing a continuous logcat that will be saved in the folder where you are running adb when the device turns off or reboots or until you stop it with ctrl+c:

adb devices

adb logcat > logcat_Unwanted_Reboot.txt

Then open the logcat in Notepad++, WordPad or similar & search it with reboot or chatty or crash or Beginning of crash or killing for example, etc.

Or use an app on the phone like MatLog (also available on F-Droid - attached a screenshot) or Logcat Extreme to record the crash & reboot.

MatLog requires root permission or if you don't have root, connect to a computer & copy/paste this in adb to grant the required permission:

adb shell pm grant com.pluscubed.matlog android.permission.READ_LOGS

Reboot to make the logcat shorter & more relevant, MatLog > 3-dots > File > Record then reproduce the problem & after the device reboots > internal sdcard > matlog > saved_logs.

Or press on the MatLog icon to create a Record shortcut.

You could zip the logcat & attach it to a reply & maybe I could find some clues in it.
***
Hi. Thanks for your reply
From an off state I press power to turn it on and within a second or two of seeing the lineage loading logo it reboots then loads up OK, the next couple of times I reboot it may not do it, then it will happen again. This is a clean install with absolutely nothing else present and no settings changed just TWRP/GAPPS nano and Magisk.
I suppose I was half expecting someone to say it was known about but not a major bug as it doesnt result in a continuous bootloop.
Will give logcat a go.
 
  • Like
Reactions: curiousrom
Re: Unwanted Reboot - Power Button

Hi. Thanks for your reply
From an off state I press power to turn it on and within a second or two of seeing the lineage loading logo it reboots then loads up OK, the next couple of times I reboot it may not do it, then it will happen again. This is a clean install with absolutely nothing else present and no settings changed just TWRP/GAPPS nano and Magisk.
I suppose I was half expecting someone to say it was known about but not a major bug as it doesnt result in a continuous bootloop.
Will give logcat a go.

You are welcome.

Thanks for the additional troubleshooting info. :cool: 👍

Since you have Magisk, to capture a logcat of a failed boot see https://www.didgeridoohan.com/magisk/MagiskHideHelp > "Logcat boot script. This is useful if your device won't boot for some reason, or if you're experiencing other boot related issues...".

That script works on my S5 and it creates a bootlog.log in the /cache folder.
***

Rule of thumb: the larger the GApps package the more chance of errors @ boot.

I prefer the smaller Pico package & just add the extra apps I need from Play Store and https://f-droid.org/

See Open GApps Package Comparison.

You can dirty flash Pico to downgrade without losing your apps & settings.
***
 
  • Like
Reactions: g000n and dcarvil
Last edited:

761gg1i3219

Member
Apr 11, 2020
37
1
Hey guys, since last month I am getting a lot of random reboots, the type that freeze the phone then the lineage logo flashes for a few times and then the phone restarts.

Yesterday night it happened again but the phone seemed stuck at the Samsung Galaxy S5 powered by android screen so I took the battery out ( I know, I am stupid). Now the phone is stuck in a bootloop. I can access Recovery just fine but cannot access System boot.
I read how to get a logcat but if the phone doesn't start adb won't see it and adb logcat while in recovery doesn't work.

Do I have to clean install everything or is there something else I can try?
 

kurtn

Senior Member
Jan 28, 2017
3,929
1,690
Small town in Bavaria
Hey guys, since last month I am getting a lot of random reboots, the type that freeze the phone then the lineage logo flashes for a few times and then the phone restarts.

Yesterday night it happened again but the phone seemed stuck at the Samsung Galaxy S5 powered by android screen so I took the battery out ( I know, I am stupid). Now the phone is stuck in a bootloop. I can access Recovery just fine but cannot access System boot.
I read how to get a logcat but if the phone doesn't start adb won't see it and adb logcat while in recovery doesn't work.

Do I have to clean install everything or is there something else I can try?
Worst case your s5 is dying from a hardware defect. Storage or so. But you can start in small steps. With twrp you can wipe dalvic and cache and reboot. Next escalation: wipe system and flash lineageOS and the GApps you has before.
 

761gg1i3219

Member
Apr 11, 2020
37
1
I'm starting to believe it's an hardware problem: I wiped System and while I was flashing the lineageos zip it rebooted starting again the bootloop. Now I'm not able to access Recovery, it reboots itself before launching TWRP.
I'm still able to access Download mode though, what do you guys think? Should I reflash TWRP and hope this fixes it?
 
S5 Cannot Boot in Recovery. - Frozen or Bootloop Reset

...the phone seemed stuck at the Samsung Galaxy S5 powered by android screen so I took the battery out ( I know, I am stupid). Now the phone is stuck in a bootloop. I can access Recovery just fine but cannot access System boot...

Removing the battery is like turning off the engine in a car going at 100 km/h without using the clutch. I have read user's reports about having corrupted files after doing that.

On the S5 you can safely simulate a battery removal if you press Volume down + Power button for 10-20 seconds while frozen, in bootloop or Download Mode: the S5 goes black & turns off.

If you keep on pressing the buttons until the Samsung bootloader splash screen appears & release them then S5 should reboot in System.

Worst case your s5 is dying from a hardware defect. Storage or so. But you can start in small steps. With twrp you can wipe dalvic and cache and reboot. Next escalation: wipe system and flash lineageOS and the GApps you has before.

Good steps.

I'm starting to believe it's an hardware problem: I wiped System and while I was flashing the lineageos zip it rebooted starting again the bootloop. Now I'm not able to access Recovery, it reboots itself before launching TWRP.
I'm still able to access Download mode though, what do you guys think? Should I reflash TWRP and hope this fixes it?

Try that & while in TWRP connect to computer to backup your internal sdcard.

The best troubleshooting step to confirm or rule out a hardware problem is to flash the most recent stock manufacturer's OS for your device & test thoroughly before installing LineageOS. That will also update the vendor's firmware if you did not do that already.

After installing the most recent TWRP, backup the important EFS partition before flashing LineageOS. (screenshot)

What is your exact S5 model?
***
 

Attachments

  • TWRP_EFS_Backup_Only_LineageOS_16-0_S5_curiousrom.png
    TWRP_EFS_Backup_Only_LineageOS_16-0_S5_curiousrom.png
    151.4 KB · Views: 13
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 9
    S5 LineageOS 17.1 klte & Variants Update 2021-04-11 - Magisk 22.1 Survives!

    FYI I OTA updated my Galaxy S5 G900M LineageOS 17.1 klte build 2021-04-04 + Open GApps Pico + Magisk 22.1 + TWRP 3.5.2_9-0 recovery to build 2021-04-11 & everything went smoothly including Magisk 22.1 surviving the update.

    There is no changes compared to build 2021-04-04 as you can see in https://download.lineageos.org/klte/changes/ but I wanted to test the TWRP & Magisk updates vs. OTA.

    Before the OTA update made a full TWRP backup then I used TWRP 3.5.1_9-0 to update to TWRP 3.5.2_9-0 as described in How To Update TWRP Using TWRP Itself then rebooted to recovery to check the version and finally to System. (screenshots). Changelog https://twrp.me/

    I used the installed Magisk 22.0 app to update it to Magisk 22.1 app, then Direct install method to update Magisk itself to 22.1. (screenshots) Changelog: https://github.com/topjohnwu/Magisk/releases.

    Of note in that Magisk page it says this but it was not my case: "RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN!".
    ***

    I was hoping for an upgrade to official LineageOS 18.1 or a security bump on 17.1 but that will have to wait for the next update I guess.

    Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 up to date. :cool: 👍
    ***
    7
    Official LineageOS 18.1 for the Galaxy S5 klte family Launched!

    FYI these haggertk's commits are now marked as Merged so it should be available in the next update if all goes well with the Lineage automated builder:
    And it's confirmed in the LineageOS build target list and the wiki pages https://wiki.lineageos.org/devices/ also.

    The respective wiki pages include an upgrade guide.

    Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 up to date. :cool: 👍
    ***
    6
    S5 LineageOS 17.1 klte & Variants Update 2021-04-18 - Bump Security

    I OTA updated my Galaxy S5 G900M LineageOS 17.1 klte build 2021-04-11 + Open GApps Pico + Magisk 22.1 + TWRP 3.5.2_9-0 recovery to build 2021-04-18 & everything went smoothly including Magisk 22.1 surviving the update.

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

    The Vendor security patch level 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.

    There are a bunch of changes in this update as you can see in https://download.lineageos.org/klte/changes/ but the ones with the word "intel" do not concern the S5.

    The klteduos 20210418 build failed as you can see in the LineageOS automated builder here so better luck next week.

    No official LineageOS 18.1 yet for the klte family until these haggertk's commits are marked as Merged top left instead of Active so patience is required:
    Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 up to date. :cool: 👍
    ***
    4
    Hello friends,
    I am using the tuned kernel for screen flickering problem. Will it work if I upgrade from 17.1 to 18.1
    18.1 will most likely overwrite tuned kernel when you upgrade. @fbs will prolly update to support android R when LOS 18.1 klte officially comes out.
    3
    Why o why has my screen have to break now?

    Btw the last links with
    Yet another ...
    And where the ...
    I don't get it. What are these links and things I can see there?
    Gerrit is the code review System used by lineageOS. Each change in source code has to be approved in that system, before changes get merged to official source code. The linked changes are not for lineageOS source code, but for the build servers. Hudson/build targets tells the build server, what device and version to build.
  • 9
    S5 LineageOS 17.1 klte & Variants Update 2021-04-11 - Magisk 22.1 Survives!

    FYI I OTA updated my Galaxy S5 G900M LineageOS 17.1 klte build 2021-04-04 + Open GApps Pico + Magisk 22.1 + TWRP 3.5.2_9-0 recovery to build 2021-04-11 & everything went smoothly including Magisk 22.1 surviving the update.

    There is no changes compared to build 2021-04-04 as you can see in https://download.lineageos.org/klte/changes/ but I wanted to test the TWRP & Magisk updates vs. OTA.

    Before the OTA update made a full TWRP backup then I used TWRP 3.5.1_9-0 to update to TWRP 3.5.2_9-0 as described in How To Update TWRP Using TWRP Itself then rebooted to recovery to check the version and finally to System. (screenshots). Changelog https://twrp.me/

    I used the installed Magisk 22.0 app to update it to Magisk 22.1 app, then Direct install method to update Magisk itself to 22.1. (screenshots) Changelog: https://github.com/topjohnwu/Magisk/releases.

    Of note in that Magisk page it says this but it was not my case: "RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN!".
    ***

    I was hoping for an upgrade to official LineageOS 18.1 or a security bump on 17.1 but that will have to wait for the next update I guess.

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

    Edit: FYI the LineageOS S5 klte family maintainer created a new thread here:

    [ROM][OFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)
    ***
    Code:
    #include "std_disclaimer.h"
    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    */

    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.

    All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit the Wiki.

    Important Info
    WARNING: the official 17.1 build 20201101 is defective, causing a bootloop & got removed from the Lineage servers. The ROMs affected are klte, klteduos & kltedv.

    If you updated to 20201101 and are caught in a bootloop as reported by several S5 users in the pages #3 of this thread and the following pages: flash an older version like 20201025 without wiping anything (a.k.a. dirty flash) and you will not lose your aps & settings:

    1- On the S5 you can simulate a battery removal if you press Volume down + Power button for 10-20 seconds while frozen, in bootloop or Download Mode: the S5 goes black & turns off.

    If you keep on pressing the buttons until the Samsung bootloader splash screen appears & release them then S5 should reboot in System.

    Or remove the battery to turn it off.

    2- With the S5 turned off hold Volume Up + Home + Power to boot in recovery and either sideload the older version or copy to the S5 the older build as MTP is enabled by default in TWRP and flash it from there.
    ***

    To flash this rom you need TWRP version 3.3.1-0 or newer or the Lineage Recovery specific to your device model.

    Some TWRP 3.4.0 users reported fail to install LineageOS after a wipe. Rebooting to TWRP recovery after the wipe solves this issue.

    The adb command adb reboot sideload does not work in TWRP for the S5 as if you sideload a file afterwards it will fail as I tested myself with this error message: " command is: 'sideload' and there is no value". You must manually select in TWRP > Advanced > ADB Sideload > swipe to begin sideload then you can sideload your file. You must do the same for each files if you sideload more than one.

    The S5 maintainer haggertk recommends not choosing Internal storage for the Micro SD card (adoptable storage) when formatting the card in the device and posted about it here: "...my opinion is no one should use adoptable storage. It's a fragile mess and always has been since Google explicitly does not care about sdcards.".

    Some S5 17.1 users reported being stuck in an endless boot animation after restoring a 17.1 TWRP backup. A workaround tested by @wireroot & posted here is to flash the original LineageOS ROM that you were running when you made that backup right after the restore operation. This was confirmed by @jdrch in his post here.

    An other possible workaround is to flash "fix_rootfs_label.zip" that you can find here right after restoring the TWRP backup. Note: this was NOT confirmed yet by S5 users in this thread.

    EFS Partition Restore - @Eadn33 reported here in the old 16.0 thread that he could not restore the EFS partition with TWRP 3.4.0 but could with TWRP 3.3.1-0 on his S5 G900V. Other models may have that problem also but no other reports so far. See EFS Partition Backup - No Service, No IMEI & No SIM Card Fix for explantions.

    Warning: do NOT select install TWRP app in TWRP as it will cause a bootloop.


    Download Links
    The Galaxy S5 klte variants currently supported by LineageOS are:

    klte - SM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8
    klteactivexx - SM-G870A, SM-G870F
    kltechn - SM-G9006V, SM-G9008V
    kltechnduo - SM-G9006W, SM-G9008W
    klteduos - SM-G900FD, SM-G900MD
    kltedv - SM-G900I, SM-G900P
    kltekdi - SCL-23, SC-04F
    kltekor - SM-G900K, SM-G900L, SM-G900S

    Each respective download pages include a link to the official clean installation instructions and a link to Device info which includes a link about how to upgrade to a higher version. For example from official 16.0 to official 17.1 without losing your settings & apps.

    The wiki mentions only the Lineage recovery but several S5 users reported successful clean install or 16.0 > 17.1 upgrading while using TWRP instead.

    TWRP: https://twrp.me/samsung/samsunggalaxys5qualcomm.html

    Google apps (Optional. The S5 requires the ARM for Android 10 version because LineageOS 17.1 is based on Android 10 & the S5's ARM architecture.): https://wiki.lineageos.org/gapps.html

    As a rule of thumb the larger the Open GApps package, the more chance of a problem on first boot with the ever changing privapp-permissions.

    I prefer the smaller Pico package & just add the extra apps I need from Play Store and https://f-droid.org/ See Open GApps Package Comparison

    Some users prefer not installing any Gapps packages & use the Aurora Store v3 - a FOSS Google Play client to download apps from Play Store. Note that some apps may require the Google Play Services & librairies which are included in the Gapps packages & may not work properly or will not get timely notifications because of it.

    Root (Optional): The LineageOS AddonSU and Privacy Guard are deprecated in 17.1. :(

    Magisk which is the only root solution for 17.1 @ the present is not supported by LineageOS. See Magisk download & Installation instructions by the Magisk dev & also the excellent Magisk and MagiskHide Installation and Troubleshooting guide by @Didgeridoohan. Thread on XDA: Magisk General Support / Discussion.

    Magisk can be installed later at anytime so it's not necessary to install it during the initial installation of LineageOS.

    Bug Reporting
    If a bug is discovered, confirm it with other users in this thread & include your device model & build date (for ex. lineage-17.1-20201025-nightly-klte), then report it following the LineageOS wiki here: https://wiki.lineageos.org/bugreport-howto.html

    Known Bugs - Known Issues
    1- On an encrypted S5 17.1 + Gapps if Secure Startup is enabled it may fail to reboot or take a very long time to boot. See bug report here.

    From haggert's post here:

    ...there is some kind of timeout that hits ALL legacy devices - addition of gapps is seemingly enough to push it over the edge. Aside from first boot or upgrade, sometimes you'll be able to get in and sometimes not. I bet if you are able to decrypt in twrp and delete dalvik cache you'll get fully booted again.

    Bottom line, if you are encrypted, make sure to disable secure startup (go change the pin/pattern/password, even to the same thing, and say that you do not want to have to answer for the device to start). {bold by me}

    2- Not a bug really but some S5 users reported fail to boot on 17.1 or no SIM card recognized because they had an older baseband/modem. See S5 Odin Flashable Modem & Bootloader.

    Haggertk posted here about 17.1: "...I'm willing to bet that you have some L or earlier baseband. Except for the activexx build, you have to be running M baseband now." {bolding by him}.

    3- Google Backup cannot be restored if you use a 4x4, 5x5 or 6x6 lock screen pattern in LineageOS instead of the Android default 3x3 pattern. See the bug report here.

    4- Display accepts touch input while off due to proximity and screen does not turn back on after call bug report by @Eadn33. The bug was fixed with klte family builds 2020-11-13 or newer. Thank you Mr. haggertk.

    5- SMS reception notification delay depends on doze / unlock state by @wireroot. He posted about it in this thread here.

    6- Bluetooth Crashing - Some users reported having issues with Bluetooth in this thread: @KrautHolg here, @liquidraver here and here, @pmduper here, @navcar here and included a logcat, @badesh here and here, @mrmarioman who posted here.

    @KrautHolg created a report in the LineageOS bug tracker with a logcat here: Bluetooth repeatedly crashes with multiple devices for the S5 klte LineageOS 17.1.

    OTOH @Eadn33 reported here that he does not have any problems "with a soundbar, music and hands free in car , or scan tool for car". I tested for 2 hours listening to music with Bluetooth headphones, received a call & also had no problems on my S5 G900M klte.

    So far nobody created a Bluetooth bug report with an attached logcat in the LineageOS bug tracker for the S5 running LineageOS 17.1. See this post about how to create one: S5 Bluetooth Crashing Bug Report?

    7- Fingerprint Scanner: Some S5 users reported not being able to register their fingerprints in > Settings > Security > Fingerprint. Contrary to the Lineage instructions the finger must be swiped down & not just "Touch the sensor". See the screenshot & the linked trick if you still can't register the fingerprint in S5 G900F Fingerprint Issue.

    Not a bug but some users reported the scanner not working on older basebands but working after updating it like @jackass5 in his post here. See S5 Odin Flashable Modem & Bootloader.

    Several users, including me, reported a higher battery usage after registering some fingerprints. See S5 Screen Lock Fingerprint Battery Tests @ Idle - BetterBatteryStat

    8- Camera (Snap) > Settings > Storage > if you select SD Card the photos are saved to /external sdcard I.D./Android/Data/org.lineageos.snap/Files/ but taping on the thumbnail of the photo you just took mistakenly opens /storage/emulated/0/DCIM/Camera/. Additionally, Gallery does not see that Files folder but a third-party app like Simple Gallery Pro that does show the Files album.

    In LineageOS 17.1 build 2020-11-23 or newer the SD Card option was deleted instead of fixing the bug. See LineageOS 17.1 - In Camera the Option Save to SD Card has Been Removed in this thread.

    9- Call Forwarding Not Working - In both the stock Phone app or when dialing a code it's broken. See this post that includes a link to a bug report: S5 klte LineageOS 17.1 Call Forwarding Error. Thanks to @uyguremre for reporting the issue here.
    ***

    S5 U.I. Speed-Up Tip: Try those as fast as you can before the tweak: expand/close notification curtain, app drawer & scroll, recent apps & scroll, horizontal scroll fast between hope pages if you have a few, open Settings & scroll, etc.

    Then: Settings > Accessibility > enable Remove animations.

    Test again as you did before. Profit!

    LineageOS FAQ
    https://wiki.lineageos.org/faq.html

    LineageOS Stats
    https://stats.lineageos.org/

    Credits
    The S5 klte + variants LineageOS maintainer is @haggertk who valiantly supported the S5 klte family through LineageOS 14.1, 15.1, 16.0 & now 17.1. Big thanks for his perseverance & dedication. :cool:👍

    He is also one of the 9 LineageOS directors and maintains other devices as well as you can see in https://wiki.lineageos.org/contributors.html

    Many thanks also to the LineageOS team and all the contributors out there in the community that made the Lineage project possible. You can see their names or nicknames in the zoomable & searchable > Settings > About phone > Contributors.

    Haggertk seemed uninterested in creating an S5 17.1 tread on XDA or he is too busy maybe so I went ahead and created one using part of the OP of his old S5 LineageOS 15.x thread. If he wants a transfer of this thread's ownership I will gladly do it.


    Kernel Source Code:
    Kernel tree: https://github.com/LineageOS/android_kernel_samsung_msm8974/tree/lineage-17.1

    LineageOS Gerrit code review: https://review.lineageos.org

    Android version: 10

    Note: this post as well as posts #2 & 3 will be updated soon.
    ***
    7
    Official LineageOS 18.1 for the Galaxy S5 klte family Launched!

    FYI these haggertk's commits are now marked as Merged so it should be available in the next update if all goes well with the Lineage automated builder:
    And it's confirmed in the LineageOS build target list and the wiki pages https://wiki.lineageos.org/devices/ also.

    The respective wiki pages include an upgrade guide.

    Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 up to date. :cool: 👍
    ***
    7
    S5 LineageOS 17.1 klte & Variants Update 2021-01-24

    I updated my Galaxy S5 G900M LineageOS 17.1 klte build 2021-01-17 + Open GApps Pico + Magisk 21.4 Stable + Magisk Manager 8.0.7 & TWRP 3.5.0 to build 2021-01-24 via the built-in OTA Updater: everything went smoothly as usual & Magisk survived the update.

    Some of the changes that you can see in https://download.lineageos.org/klte/changes/ do not concern the S5 klte family (Motoactions, fastcharge & nvidia) and the others like the ones concerning android_packages_apps_ThemePicker (Settings > Display > Styles & wallpapers) are not dramatic but I updated anyway to be able to post in this thread.

    Thank you Mr. haggertk & to the entire LineageOS Team for supporting our S5's. :cool: 👍
    ***
    6
    S5 LineageOS 17.1 klte & Variants Update 2021-02-14

    I updated my Galaxy S5 G900M LineageOS 17.1 klte build 2021-02-07 + Open GApps Pico + Magisk 21.4 Stable + Magisk Manager 8.0.7 & TWRP 3.5.0 to build 2021-02-14 via the built-in OTA Updater: everything went smoothly as usual & Magisk survived the update.

    There are no important changes except maybe some time zone stuff for certain regions as you can see in https://download.lineageos.org/klte/changes/ but I updated anyway so I could post about it here.

    Thank you Mr. haggertk & to the entire LineageOS Team for supporting our S5's. :cool: 👍
    ***
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone