[OFFICIAL] LineageOS 17.1 for Galaxy S5 klte + Variants

[HippoMan]

I am running the January 3 version of 17.1 on my klte phone. I'm running Magisk 20.4 and Magisk Manager 8.0.4. My version of TWRP is old: 3.3.1-0. Everything is working fine.

I see that some people are running TWRP version 3.5.0, and I'm assuming that this means that it's safe for me to run that TWRP version. Can anyone think of any downside to my upgrading TWRP to version 3.5.0 on my device?

Thank you very much.

 

[Massedil]

Hello,

Just a feedback after using LineageOS 17.1.

1. Phone app : the page that displayed recent contacts disappeared replaced by a favourite contact page. Without favourite, it is useless compared to the recent calls page.

2. When manually locking the phone, notifications disappeared on the lock screen.

3. Wait for the screen to lock (don't force it with the menu because of last point). Notifications are here in portrait mode. When the lock screen is rotated to landscape, notifications disappears, and reappears again when in portrait again.

4. No more Android orthography corrector, even if it is activated in the parameters. EDIT 2021-01-18 : issue 2532 seems to solve this problem that disappeared with lineage-17.1-20210117-nightly-klte-signed.zip

5. Notification panel is sometimes laggy. Especially when using swiches.

6. More problems with Bluetooth disconnection than with 16.1. I have tried to change Bluetooth parameters in developers mode without success.

Can you reproduce? Do you have some workaround?

 

[synch]

First attempt: didn't change.
Second attempt: Unsuccesful flash
Third attempt: ... it shows up correctly now.

What the actual hell is going on here

Thanks for the tip! I'm feeling brave, 17.1 flash, here I come!

Edit: It actually booted into 17.1... and recognized the SIM.

I'm going to consider this a provisional victory.

Thanks a lot @wireroot and @curiousrom

Either way it's a step in the right direction!

So, it's been a few days and I've had zero random restarts, all boots were succesful and it's performing great. Made a few phonecalls, have received SMS and Signal messages and did some browsing.

No Gapps or anything fancy. Just a few fdroid apps.

Updating the baseband did the trick. What I don't get is why it was rebooting so inconsistently. You'd think that with a problem like that it would always reboot at the same time, and never manage to fully boot, instead of randomly restarting and occasionally working as intended.

Ah well, I hope this is of some use to anyone

 

[baldgyt]

Maybe you should disable smart cover in connected devices NFC ...

That's definitively the smart cover option. Turn it off or adjust behaviour in settings connected devices.

 

[kurtn]

...

No need to reply. A simple like tells me i was right and you appreciate

 

[curiousrom]

S5 LineageOS 17.1 klte & Variants Update 2021-01-10

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

There are 7 changes to the S5's 17.1 kernel (android_kernel_samsung_msm8974) all made by haggertk, some others are labeled android_hardware_motorola and do not concern the S5 klte family and two other minor ones a you can see in https://download.lineageos.org/klte/changes/ for example.

Or check on your device in the built-in Settings > System > Advanced > Updater > 3-dots > Changelog which will open in a mobile browser the same page as above.

Since that page changes all the time I attached a screenshot for posterity.

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.

The upcoming Android Bump Security String to 2021-01-05 is not included. Top left of that page you can see @ the present the label Active meaning still under review.

After it's marked Merged it should be included in the next update.

Thank you Mr. haggertk for supporting our S5's.
***

 

[Eadn33]

Ideas on why the Motoactions are showing up in the Klte updates?

 

[761gg1i3219]

I'm following the thread on 18.1 and sometimes I'm looking at the changes on Gerrit.
In the "Initial batch of 18.1 promotions/additions" there's a list of I guess the firsts devices that will update to 18.1 once it goes official but klte* are not in it so I have two questions (I'm not asking for ETA, just want to understand better how things work):

- When do LOS changes version? Again, I'm not asking for ETA but what has to happen before changing major version? Like they have a list of features that are to be implemented and when that is done the upgrade will be shipped or what else? Or they want to have a "test phase" for a fixed number of months and then release 18.1?
- Second question is related to klte*, since 18.1 is not yet official for any device, why are they not included in the "Initial batch of 18.1 promotions/additions"? Like is it a choice by haggertk to keep it unofficial till second batch because he prefers so or is there another reason, like for example the devices included in 1st batch are more "forward" in completing the tasks needed for 18.1 and klte* will be included in 1st batch if it meets some criteria before 18.1 going official?

I'm sorry for the chaotic questions but I really I have no idea about all of this works and wanted to learn. If anyone could help me understand that'd be great. Thanks in advance. and thank you again haggertk for your amazing work on this device, you're truly a hero.

 

[KrautHolg]

Just to let people know how it turned out in the end. Maybe someone has similar problems.

Tried lineage-17.1-20201011-nightly-klte to no avail. Bluetooth still didn't work. Completely useless that way.

Then I tried out lineage-14.1-20200614-UNOFFICIAL-klte on 10/30 and Bluetooth hasn't crashed once since. I guess I'll stay with this build until the Bluetooth issue is resolved.

I decided to give it another shot with the latest lineage-17.1-20210110-nightly-klte-signed

Unfortunately the Bluetooth problem is still there for me. I couldn't do a logcat last time, as I had already switched to another ROM and I needed the phone on an everyday basis. Also, I am not familiar with Android Studio, although I have just installed it.

Here is my question: Is there a *simple* and *easy* way to do a logcat for the Bluetooth issue, either via ADB or directly on the phone? I will provide it as soon as I can.

Cheers!

KrautHolg

 

[kurtn]

I decided to give it another shot with the latest lineage-17.1-20210110-nightly-klte-signed

Unfortunately the Bluetooth problem is still there for me. I couldn't do a logcat last time, as I had already switched to another ROM and I needed the phone on an everyday basis. Also, I am not familiar with Android Studio, although I have just installed it.

Here is my question: Is there a *simple* and *easy* way to do a logcat for the Bluetooth issue, either via ADB or directly on the phone? I will provide it as soon as I can.

Cheers!

KrautHolg

If you have a PC with adb ist easy. Type adb logcat in terminal.

 

[curiousrom]

I'm following the thread on 18.1 and sometimes I'm looking at the changes on Gerrit.
In the "Initial batch of 18.1 promotions/additions" there's a list of I guess the firsts devices that will update to 18.1 once it goes official but klte* are not in it...

I think your post is in the wrong thread since this one is about official 17.1.

Maybe you could copy/paste it in [ROM][UNOFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*) & delete this one or link to your new post?

For those wondering he is referring to this in the Lineage Gerrit Code Review which is not Merged yet: hudson: Initial batch of 18.1 promotions and expand lineage-build-targets.

I'm pretty sure that when haggertk thinks that the klte family is official 18.1 ready, he will add it to it or push them later.
***

 

[curiousrom]

...Is there a *simple* and *easy* way to do a logcat for the Bluetooth issue, either via ADB or directly on the phone?

From the post #1: 6- Bluetooth Crashing ... 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?

Check this XDA portal article: What is ADB? How to Install ADB, Common Uses, and Advanced Tutorials (for Windows, macOS or Linux)

...I am not familiar with Android Studio, although I have just installed it.

It's not necessary to install that but there are plenty of tutorials about how to use it.
***

 

[4Privacy]

From my earlier post (updated):

LineageOS 17.1 klte Upgrade experiences
[...]

I clean installed 17.1 and noticed a few things compared to LOS 16.0 (which I run before and which also worked without any bugs worth mentioning):

1. UI is sometimes laggy (as already mentioned) - will continue to test in latest build 20201122 - can confirm that reboot often solves these problems - did not recognize this anymore since a few OTA updates

2. As opposed to the official LOS blog post (Changelog 24) where it says: "Wi-Fi display is available once again." a connection to wifi display devices is not possible (same as in LOS16.0). Is there a dependency to Google/Gapps/proprietary compoenents?!

3. I cannot configure "quick shortcuts" anymore (as before in LOS16.0) for being able to launch camera (or other apps) directly from lock screen.

4. UI changes in LOS17.1 do not allow to quickly open battery preferences page anymore by pulling statusbar down and tapping on battery percents in right top edge.

5. [Important in my eyes] The new dark mode feature (arriving with Android 10) comes with the LOS setting to apply the dark mode according to sunset/sunrise. For me this does not work. Again, is there a dependency to proprietary components/services regarding determination of location? What needs to be done in order to get this working? Thanks in advance. - for devices without Google Services -> install standalone MicroG UnifiedNlp Network Location Provider - thanks @curiousrom & @kurtn

6. Can someone explain to me why the page under System > Advanced > Backup is populated only when Google/Gapps etc. are installed?! (Like I said) I don't use Google at all (no Gapps, just clean LOS) and I am wondering why a backup function depends on Google and in particular leaving the backup page just blank...? Addition: There is no "Change backup provider" button @kurtn

7. [NEW]: The screen lock timeout is not being applied correctly. Instead the phone is getting locked immediately when display timeout is reached.

I think the points above may be helpful for some who started thinking about upgrading to LOS17.1 as well as the devs who look for bugs and respective solutions. Might be more helpful for some (who actually use their phone) instead of declaiming LOS18 in this thread.

 

[761gg1i3219]

I think your post is in the wrong thread since this one is about official 17.1.

Maybe you could copy/paste it in [ROM][UNOFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*) & delete this one or link to your new post?
***

Mind helping a brother out? I don't know how to delete the post.

I'm pretty sure that when haggertk thinks that the klte family is official 18.1 ready, he will add it to it or push them later.
***

I know but what are the differences in terms of "readiness" between haggertk's klte* builds and the ones already included in the "initial batch".

 

[KrautHolg]

From the post #1: 6- Bluetooth Crashing ... 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?

Check this XDA portal article: What is ADB? How to Install ADB, Common Uses, and Advanced Tutorials (for Windows, macOS or Linux)



It's not necessary to install that but there are plenty of tutorials about how to use it.
***

Thanks for all the answers. Unfortunately I have run into another snag. I will have to completely reinstall the phone and see where that gets me. I will probably do that tomorrow. As I need the phone, I will go back to an older ROM if I can't fix it any time soon. If all goes well, I will get the logcat.

Greetings from an extremely frustrated KrautHolg

 

[kurtn]

@4Privacy I see seedvault backup provider.

 

[x2k13]

S5 LineageOS 17.1 klte & Variants Update 2021-01-10

Funny thing I've noticed:
The LineageOS Version Tag under Settings > About Phone > Android Version still says "17.1-20201220-NIGHTLY-klte". So, apparently this hasn't changed since 2020-12-20 (although flashing the updates via TWRP without errors). Any idea why?
Sorry, my bad - I forgot the build.prop I modded keeps the version it came from (lol), all good.

But, still:
How do I get rid of the history list of updates in the updater?
With the build.prop coming from the latest update, the list got cleared automagically. Nevermind.

 

[KrautHolg]

From the post #1: 6- Bluetooth Crashing ... 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?

Check this XDA portal article: What is ADB? How to Install ADB, Common Uses, and Advanced Tutorials (for Windows, macOS or Linux)



It's not necessary to install that but there are plenty of tutorials about how to use it.
***

Would this be the right logcat?

Can I just upload the 2021-01-12_15.24.zip or does it have to be the unzipped logcat.log ?

Christ! Where did the attached file go now?

 

[KrautHolg]

Would this be the right logcat?

Can I just upload the 2021-01-12_15.24.zip or does it have to be the unzipped logcat.log ?

Christ! Where did the attached file go now?

I hope I did it right this time...

Bluetooth repeatedly crashes with multiple devices (#2944) · Issues · LineageOS / issues / android

Expected Behavior Bluetooth should remain active after connecting to a device. Current Behavior

gitlab.com

 

[Zytrel]

Tried dirty upgrading from latest 16.0 to lineage-17.1-20210110-nightly-klte (and virtually every version before) and Wear OS stopps working (being stuck at the loading screen). GApps-Nano, no Magisk. Anyone else experiencing this issue?

Also, any news on the issue with Encryption/Secure Boot and GApps as described here:
https://gitlab.com/LineageOS/issues/android/-/issues/2044
Just simply disabling Secure Boot is not really an option, as it's kinda the same as disabling encryption alltogether with an open bootloader.

Regards,
Zy.