[OFFICIAL] LineageOS 17.1 for Galaxy S5 klte + Variants

Search This thread
By:
Advanced…
curiousrom

curiousrom

Recognized Contributor
Jun 4, 2011
2,172
4,101
Costa Rica
www.reddit.com
Samsung Galaxy S III I9300
Samsung Galaxy Tab 2
Ambient Display - Screen on Notification - Custom LED Color

g.k.h.n said:
...I dirty upgraded from LineageOS 16.1 official to 17.1 official and i can't see the "ambient display" page in display settings.
Click to expand...
Click to collapse
Garry58 said:
... It's under Display - Advanced - Lock screen Display for me (not just Display). There's also shortcut tile for the notification panel (you can edit it by tapping on the pencil in left-bottom corner, if you can't see it).
Click to expand...
Click to collapse
g.k.h.n said:
Tried both but i haven't that setting
Click to expand...
Click to collapse

I also "dirty upgraded from LineageOS 16.1 official to 17.1 official". BTW it's 16.0. ;)

As you can see in the attachments there is a Ambient display quick tile as @Garry58 said. I don't use a screen lock most of the time so that's the only way to access that setting for me.

If you can't see it edit the quick tiles with the pencil as he said. Maybe it's lower and you have to drag it up.

That's on my Galaxy S5 G900M LineageOS 17.1 klte build 2021-02-28.

I could not take a screenshot of when the screen turns on to show the SMS notification so I used the built-in Recorder app, started a screen recording, turned off the screen, sent an SMS to the S5, stopped the recording and took a screenshot of the screen recording.

Garry58 said:
...I don't find Ambient screen that useful on S5 tbh, since it has notification light, which has similar purpose (the color of which picked automatically based on app icons and can even be set by app manually. I didn't expect such customization on modern OS, as they're not typically installed on the newer devices).
Click to expand...
Click to collapse

I agree with that. It's really cool to be able to chose a custom notification LED color for each app. You can then decide to check the notification or not depending on the app & it's LED notification color and it's blinking speed if you wish.

Search Settings with Notification light, enable Use custom values in that panel, then with the + add the apps. Long press on them & choose the color & you can also customize the Pulse length & speed. (screenshot)
***
 

Attachments

  • Ambient_display_Quick_Tile_LineageOS_17-1_S5_curiousrom.png
    Ambient_display_Quick_Tile_LineageOS_17-1_S5_curiousrom.png
    229.1 KB · Views: 39
  • Ambient_display_Notification_LineageOS_17-1_S5_curiousrom.png
    Ambient_display_Notification_LineageOS_17-1_S5_curiousrom.png
    129.8 KB · Views: 41
  • Notification_Light_Custom_Values_S5_LineageOS_17-1_curiousrom.png
    Notification_Light_Custom_Values_S5_LineageOS_17-1_curiousrom.png
    357.3 KB · Views: 44
Last edited:
  • Like
Reactions: dcarvil and pmduper
G

g.k.h.n

Member
Jan 1, 2020
8
1
curiousrom said:
Ambient Display - Screen on Notification - Custom LED Color





I also "dirty upgraded from LineageOS 16.1 official to 17.1 official". BTW it's 16.0. ;)

As you can see in the attachments there is a Ambient display quick tile as @Garry58 said. I don't use a screen lock most of the time so that's the only way to access that setting for me.

If you can't see it edit the quick tiles with the pencil as he said. Maybe it's lower and you have to drag it up.

That's on my Galaxy S5 G900M LineageOS 17.1 klte build 2021-02-28.

I could not take a screenshot of when the screen turns on to show the SMS notification so I used the built-in Recorder app, started a screen recording, turned off the screen, sent an SMS to the S5, stopped the recording and took a screenshot of the screen recording.



I agree with that. It's really cool to be able to chose a custom notification LED color for each app. You can then decide to check the notification or not depending on the app & it's LED notification color and it's blinking speed if you wish.

Search Settings with Notification light, enable Use custom values in that panel, then with the + add the apps. Long press on them & choose the color & you can also customize the Pulse length & speed. (screenshot)
***
Click to expand...
Click to collapse

Thank you both, i saw it in the quick tiles. I'm already using the different led colors and you're right, it's very useful.

I actually want to see the digital watch without unlock the screen but i didn't see it anywhere. Is there always on display feature on 17.1? I think i saw that in other roms but not in LineageOS on klte. Thanks again.
 
  • Like
Reactions: curiousrom
Lee245

Lee245

Member
Jul 3, 2010
5
1
Many thanks to the developers for maintaining the LineageOS roms on the S5! I've been using the 16.0 version for a quite a while now and I'm not sure what to expect when moving to 17.1. Are there any (major) issues apart from the ones mentioned in the topic start? Can I upgrade to 17.1 for use as a daily driver?
 
corrdude

corrdude

New member
Mar 4, 2021
4
0
Brothers and Sisters,

I share the pain with you of losing my connection between headphone and smartphone for media play. music, video, calls, alert chimes, all do not work because bluetooth behaves as if it is connected on the phone but it actually is not connected and won't connect until a restart.

So, after reading the above about a bug report protocol. I'm attempting to follow the protocol by creating and transmitting the .zip consisting of the lgocat.log and other logs. They were taken the moment after the crash of bluetooth so developers can easily resolve it.


--------- beginning of crash
03-03 14:26:41.785 F/libc (11349): Fatal signal 31 (SIGSYS), code 1 (SYS_SECCOMP) in tid 11349 (dmesg), pid 11349 (dmesg)
03-03 14:26:41.841 I/crash_dump32(11352): obtaining output fd from tombstoned, type: kDebuggerdTombstone
03-03 14:26:41.850 I/crash_dump32(11352): performing dump of process 11349 (target tid = 11349)
03-03 14:26:41.852 F/DEBUG (11352): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-03 14:26:41.853 F/DEBUG (11352): LineageOS Version: '17.1-20201115-NIGHTLY-klte'
03-03 14:26:41.853 F/DEBUG (11352): Build fingerprint: 'samsung/kltexx/klte:6.0.1/MMB29M/G900FXXU1CRH1:user/release-keys'
03-03 14:26:41.853 F/DEBUG (11352): Revision: '14'
03-03 14:26:41.853 F/DEBUG (11352): ABI: 'arm'
03-03 14:26:41.855 F/DEBUG (11352): Timestamp: 2021-03-03 14:26:41-0800
03-03 14:26:41.855 F/DEBUG (11352): pid: 11349, tid: 11349, name: dmesg >>> dmesg <<<
03-03 14:26:41.855 F/DEBUG (11352): uid: 10131
03-03 14:26:41.855 F/DEBUG (11352): signal 31 (SIGSYS), code 1 (SYS_SECCOMP), fault addr --------
03-03 14:26:41.855 F/DEBUG (11352): Cause: seccomp prevented call to disallowed arm system call 103
 

Attachments

  • 2021-03-03_14.27-event.zip
    3.1 KB · Views: 5
x2k13

x2k13

Senior Member
Nov 2, 2015
614
560
Somewhere in the vicinity of Betelgeuse
Samsung Galaxy S4
Samsung Galaxy S5
corrdude said:
Brothers and Sisters,

I share the pain with you of losing my connection between headphone and smartphone for media play. music, video, calls, alert chimes, all do not work because bluetooth behaves as if it is connected on the phone but it actually is not connected and won't connect until a restart.

So, after reading the above about a bug report protocol. I'm attempting to follow the protocol by creating and transmitting the .zip consisting of the lgocat.log and other logs. They were taken the moment after the crash of bluetooth so developers can easily resolve it.


--------- beginning of crash
03-03 14:26:41.785 F/libc (11349): Fatal signal 31 (SIGSYS), code 1 (SYS_SECCOMP) in tid 11349 (dmesg), pid 11349 (dmesg)
03-03 14:26:41.841 I/crash_dump32(11352): obtaining output fd from tombstoned, type: kDebuggerdTombstone
03-03 14:26:41.850 I/crash_dump32(11352): performing dump of process 11349 (target tid = 11349)
03-03 14:26:41.852 F/DEBUG (11352): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-03 14:26:41.853 F/DEBUG (11352): LineageOS Version: '17.1-20201115-NIGHTLY-klte'
03-03 14:26:41.853 F/DEBUG (11352): Build fingerprint: 'samsung/kltexx/klte:6.0.1/MMB29M/G900FXXU1CRH1:user/release-keys'
03-03 14:26:41.853 F/DEBUG (11352): Revision: '14'
03-03 14:26:41.853 F/DEBUG (11352): ABI: 'arm'
03-03 14:26:41.855 F/DEBUG (11352): Timestamp: 2021-03-03 14:26:41-0800
03-03 14:26:41.855 F/DEBUG (11352): pid: 11349, tid: 11349, name: dmesg >>> dmesg <<<
03-03 14:26:41.855 F/DEBUG (11352): uid: 10131
03-03 14:26:41.855 F/DEBUG (11352): signal 31 (SIGSYS), code 1 (SYS_SECCOMP), fault addr --------
03-03 14:26:41.855 F/DEBUG (11352): Cause: seccomp prevented call to disallowed arm system call 103
Click to expand...
Click to collapse
You are running a ROM version from November 11, 2020. You might want to update the ROM to the latest version, which is 20210228, then try again.
 
  • Like
Reactions: curiousrom
J

jmh2002

Senior Member
Jun 1, 2016
151
83
NZL, POL, UKR
haggertk said:
Your note about adoptable storage is also something that should not have happened for consistency of experience. And the stance is internally consistent:
- If sdcard -> you have adoptable storage
- If physical buttons -> you don't get navbar

Edit: but 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.
Click to expand...
Click to collapse

Given the above opinion of the developer of these builds, as well as some consideration to whatever the situation will be 18.0, what is the current suggested 'Best Practice' as far as SD Cards are concerned?

IE: Use Adoptable Storage, or Not?

And the pluses and minuses?

THANKS :)
 
G

Garry58

Member
Nov 13, 2020
34
27
Samsung Galaxy S5
SD Cards are much slower than internal memory. Adoptable storage will try to merge two together without giving you the choice what to store on which storage device. The performance may drop significantly for some apps in the process.

I'd really suggest against using it. SD cards are good to store some data like music files or pictures or whatever that is, it's really not great to store system/app files.

p.s. also, format your Data partition to F2FS, if you can (you will lose all your data, make a backup).
 
x2k13

x2k13

Senior Member
Nov 2, 2015
614
560
Somewhere in the vicinity of Betelgeuse
Samsung Galaxy S4
Samsung Galaxy S5
jmh2002 said:
Given the above opinion of the developer of these builds, as well as some consideration to whatever the situation will be 18.0, what is the current suggested 'Best Practice' as far as SD Cards are concerned?

IE: Use Adoptable Storage, or Not?

And the pluses and minuses?

THANKS :)
Click to expand...
Click to collapse
Upside: Way more internal (Apps) memory
Downside: Less speed*

*depending on which SD-Card you are using

It's really up to you and what you prefer.

You need a lot of Apps without having to worry about space?
Go for adoptable storage.

You want all the I/O speed you can possibly get?
Don't use adoptable storage.

I'm using a pretty fast (write speed) and large SD-Card and can confirm the phone being a tad slower than without, but I can live with that when in turn I don't have to worry about space for Apps.

But again, you'll need an SD-Card with high write speed.

The limiting factor is the built in card reader, generally speaking.
 
J

jmh2002

Senior Member
Jun 1, 2016
151
83
NZL, POL, UKR
Thanks for the comments regarding Adoptable Storage. Most of those normal things I understood but after making some tests It seems that I misunderstood one point:

- when using Adoptable Storage the SD Card still shows separately and it's then possible to move selected apps to the SD Card just like it was before Adoptable Storage

For some reason I assumed that this would not be possible with Adoptable Storage, since I thought the SD Card would be 'adopted' and combined as part of the total storage and that would be that.

What I also noticed is that if I use the 'Migrate' function I don't have any control over what is moved.

So given that an SD Card could still become corrupted it seems a better idea to just move the non essential apps there manually, and not use 'Migrate' at all? That's what I done for the moment anyway.

The one down side to this seems to be the following:

* Using Migrate - the SD Card is Available File Browser apps

* NOT using Migrate, but moving apps manually - the SD Card is Unavailable in File Browser apps

That's not helpful for some large apps which I would like to have on the SD Card but would still like to have file access too, via my laptop, etc.

Is there any fix or work around for that? Or some more general thoughts on the situation?

Or simply go back to using the SD Card in Portable / External mode?

THANKS :)
 
Last edited:
curiousrom

curiousrom

Recognized Contributor
Jun 4, 2011
2,172
4,101
Costa Rica
www.reddit.com
Samsung Galaxy S III I9300
Samsung Galaxy Tab 2
S5 klte Update 2021-03-07 - Skip It!

If you already have build 2021-02-14 or more recent installed on your S5 there is no reason to update to 2021-03-07 because there are no changes as you can see in https://download.lineageos.org/klte/changes/ (or in the first attached screenshot).

As you can see in the second screenshot or in that page the Bump Security String to 2021-03-05 will be included in the next build so it should be in next week's update if all goes well with the LineageOS automated builder.
***
 

Attachments

  • Updater_Changelog_2021-03-07_S5_LineageOS_17-1_S5_curiousrom.png
    Updater_Changelog_2021-03-07_S5_LineageOS_17-1_S5_curiousrom.png
    353.5 KB · Views: 22
  • Updater_Changelog_2021-03-07_Security_Bump_Next_Update_S5_LineageOS_17-1_S5_curiousrom.png
    Updater_Changelog_2021-03-07_Security_Bump_Next_Update_S5_LineageOS_17-1_S5_curiousrom.png
    225.7 KB · Views: 23
  • Like
Reactions: BlueCyclone and dcarvil
H

haggertk

Senior Member
Jun 26, 2010
1,114
5,518
Denver, CO
Samsung Galaxy Note 3
Samsung Galaxy S5
curiousrom said:
S5 klte Update 2021-03-07 - Skip It!

If you already have build 2021-02-14 or more recent installed on your S5 there is no reason to update to 2021-03-07 because there are no changes as you can see in https://download.lineageos.org/klte/changes/ (or in the first attached screenshot).

As you can see in the second screenshot or in that page the Bump Security String to 2021-03-05 will be included in the next build so it should be in next week's update if all goes well with the LineageOS automated builder.
***
Click to expand...
Click to collapse

Or you go download it and get ro.build.version.security_patch=2021-03-05 instead of waiting a week.
 
  • Like
Reactions: dcarvil
curiousrom

curiousrom

Recognized Contributor
Jun 4, 2011
2,172
4,101
Costa Rica
www.reddit.com
Samsung Galaxy S III I9300
Samsung Galaxy Tab 2
haggertk said:
Or you go download it and get ro.build.version.security_patch=2021-03-05 instead of waiting a week.
Click to expand...
Click to collapse

Hello stranger.

Are you saying that the klte changelog is not accurate @ the present (as seen in the screenshot above) & that Bump Security String to 2021-03-05 is included already in lineage-17.1-20210307-nightly-klte-signed.zip?
***
 
Last edited:
B

blikkk

Senior Member
Jul 28, 2018
78
33
n0me said:
Hello there,

I've been using 17.1 for a few days now as my daily driver and I run into the folowing problem every now and then: starting random apps (TitaniumBackup x2, Magic Earth x4, DiskUsage x2) results in a crash/reboot of the phone. After booting up, the external SD is not readable anymore and Android asks to reformat, losing all my stored data in the process. Everything else (encrypted system, internal SD) works fine after the reboot. I can still access the SD card from TWRP and read/copy the content. Only the TitaniumBackup folder seemed unreadable the last time the crash happend while doing a backup with Titanium. I used all the above apps and the SD card in combination before without any problems on LOS 16.0. I don't really know what is causing the problem (broken SD card? Android 10? Encryption?) and where to start looking for a fix.

Has anyone of you experienced the same problem and what was the reason for it (if you solved it)?

Thank you!

My S5: LOS mG 17.1 (20210202), encrypted, 128 GB SanDisk external SD card (not adopted), Magisk 22.0
Click to expand...
Click to collapse

Same problem. I thought the Drivedroid app was causing the reboot. I was wrong. Intensive SD card usage is the problem. I wrote incorrectly that it has been corrected. This is a kernel bug. I'm using the Luis rom kernel, it solved the problem.

https://xdaforums.com/t/rom-klte-10-luisrom-android-10-based-on-crdroid-v6-x.4050529/
Download rom, extract zip, copy boot.img to phone, flash with twrp.

My phone: klte duos, 128Gb Transcend SD card, EXFat
Fine working (2 sim, mobile data, etc). Not rebooting, not freezeing.

I am confident that the official kernel will be fixed soon.
 
  • Like
Reactions: n0me
curiousrom

curiousrom

Recognized Contributor
Jun 4, 2011
2,172
4,101
Costa Rica
www.reddit.com
Samsung Galaxy S III I9300
Samsung Galaxy Tab 2
S5 klte Update 2021-03-07 - OTA Update Fail

haggertk said:
Or you go download it and get ro.build.version.security_patch=2021-03-05 instead of waiting a week.
Click to expand...
Click to collapse

@haggertk - I just tried to OTA update to lineage-17.1-20210307-nightly-klte-signed.zip via the built-in Updater app and for the first time since November 2020 the OTA update failed.

It stalled in TWRP recovery so before rebooting I went to Home > Backup > Select Storage to external Micro SD card then > Home > Advanced > Copy Log to external SD card.

I attached the recovery.log to this message. From it:

Code: 
I:operation_start: 'OpenRecoveryScript'
Running Recovery Commands
I:command is: 'install'
I:value is: '@/cache/recovery/block.map'
I:Unable to install via mapped zip '/cache/recovery/block.map'
Error installing zip file '@/cache/recovery/block.map'
Done processing script file
I:Set page: 'action_complete'
I:operation_end - status=1

I rebooted & tried again to apply the update but this time it did not even try to reboot in recovery. I captured a logcat & attached it also.

That's on a Galaxy S5 G900M LineageOS 17.1 klte build 2021-02-28 + Open GApps Pico + Magisk 22 + TWRP 3.5.0 recovery.
 

Attachments

  • TWRP_2021-03-07-09_OTA_Update_Fail.png
    TWRP_2021-03-07-09_OTA_Update_Fail.png
    112 KB · Views: 22
  • recovery__2021-03-07_OTA_Update_Fail_S5_curiousrom.zip
    5.3 KB · Views: 5
  • logcat_2021-03-07_OTA_Update_Fail_S5_curiousrom.zip
    490.3 KB · Views: 4
  • Screenshot_20210307-092933_Trebuchet.png
    Screenshot_20210307-092933_Trebuchet.png
    467.4 KB · Views: 19
Last edited:
  • Like
Reactions: dcarvil
M

Martin-By

Member
May 1, 2020
32
11
65
Hello, my KLTE update to 2021-03-07 were done as expected, without any problems!

All is working smooth and fast.


But I have a question about S5 builtin sensors! My problem is one special APP that needs the motion sensor.

I do not find any option to control any of the sensors. Are these sensors avaiable within this realease?
 
curiousrom

curiousrom

Recognized Contributor
Jun 4, 2011
2,172
4,101
Costa Rica
www.reddit.com
Samsung Galaxy S III I9300
Samsung Galaxy Tab 2
Last edited:
B

blikkk

Senior Member
Jul 28, 2018
78
33
curiousrom said:
Could you give more details about your device model & setup like I did above please?



Try with a sensor test app like Sensors Sandbox on F-Droid or DevCheck in Play Store. Both work on my S5 G900M.
***
Click to expand...
Click to collapse


G900FD, Magisk 22, OpenGapps, TWRP 3.5
OTA, download and install: Phone reboot, rom not install, not error.
Select install, browse /data/lineageos_updates/lineage-17.1-20210307-nightly-klteduos-signed.zip, flash.
Rom installed, phone reboot, working.
 
  • Like
Reactions: curiousrom
curiousrom

curiousrom

Recognized Contributor
Jun 4, 2011
2,172
4,101
Costa Rica
www.reddit.com
Samsung Galaxy S III I9300
Samsung Galaxy Tab 2
Re: S5 klte Update 2021-03-07 - OTA Update Fail

blikkk said:
G900FD, Magisk 22, OpenGapps, TWRP 3.5
OTA, download and install: Phone reboot, rom not install, not error.
Select install, browse /data/lineageos_updates/lineage-17.1-20210307-nightly-klteduos-signed.zip, flash.
Rom installed, phone reboot, working.
Click to expand...
Click to collapse

Thanks for the troublehooting info. :cool: 👍

So the OTA update via the Updater app failed for you too but worked when flashing manually in TWRP, right?

You did not get a notification of a failed update like the screenshot I posted above?
***
 
You must log in or register to reply here.

Similar threads

H
[ROM] [OFFICIAL] LineageOS 14.X for Galaxy S5 | Android 7.X Nougat
Replies
11K
Views
1M
pmduper
pmduper
kornfed
  • Poll
[ROM] [Official & Nightlies] [BlissPop 6.01] 6/8 - [KLTE-SPR-DV-USC]
Replies
9K
Views
1M
E
erkanakarcay
S
[ROM][7.1.2_r36][DEC-31]Resurrection Remix N KLTE[5.8.5][klte+variants]
Replies
6K
Views
815K
Y
yeahman45
afaneh92
[ROM][8.1.0][UNOFFICIAL] LineageOS 15.1 for klte
Replies
3K
Views
643K
L
lecorbusier
fumes007
[ROM][6.0.1_r74][klte+variants][NOV-21]RESURRECTION REMIX MM V5.7.4
Replies
6K
Views
798K
M
Mcha01

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 10
    curiousrom
    curiousrom
    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}
    Click to expand...
    Click to collapse

    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.

    haggertk said:
    Device source code:
    Click to expand...
    Click to collapse

    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.
    ***
    View
    9
    curiousrom
    curiousrom
    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: 👍
    ***
    View
    7
    curiousrom
    curiousrom
    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: 👍
    ***
    View
    7
    curiousrom
    curiousrom
    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: 👍
    ***
    View
    6
    curiousrom
    curiousrom
    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: 👍
    ***
    View

New posts