yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] curiousrom:
LineageOS 16.0 Update 2020-08-09 - Security Bump

FYI the monthly Android security patch Bump Security String to 2020-08-05 is included in LineageOS 16.0 for the S5 klte + variants build 2020-08-09 or newer as well as 28 other changes mostly related to security including a bunch to the S5's LineageOS kernel (android_kernel_samsung_msm8974) as you can see in your model's changelog. For example: https://download.lineageos.org/klte/changes/

Because that Changes page is updated all the time I attached some screenshots for posterity.

See Android Security Bulletin—August 2020 for details about the security fixes.

I updated to LineageOS 2020-08-09 via the built-in LineageOS OTA Updater a Galaxy S5 G900M LineageOS 16.0 klte running build 2020-07-19 + Open GApps Pico + LineageOS AddonSU, no custom kernel or system mods of any kind & everything went smoothly as usual.

Of note from the moment I clicked OK to install to full boot to system after the automated flashing in TWRP it took 8 minutes instead of the usual +- 5 minutes. That may vary depending on your setup.

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

View attachment 5076381

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.

Thank you to the Lineage Team & Mr. haggertk (who made that bump security patch) for keeping our old S5 up to date. :good::cool:

***
[Samsung Galaxy S 5 Unified Development] Tombab:
So if custom kernel is flashed it overwrites stock kernel and it's security improvements?
[Samsung Galaxy S 5 Unified Development] curiousrom:
Custom Kernel & Security Bump

Yes unless the maker of that kernel is using the LineageOS repo & updates often.

As you can see here the S5's LineageOS maintainer haggertk works on it quite often: https://review.lineageos.org/q/project:LineageOS%2Fandroid_kernel_samsung_msm8974

I never saw any benchmarks proving that custom kernel x is any better than stock so I stick to it because my S5 feels snappy & with excellent battery life.

Instead of changing the kernel this is what I do for optimization: S5 Remove Animations UI Speedup Test - Taming Google & Apps and also Galaxy S5 LineageOS 16.0 Battery Usage @ Idle for screenshots.

***
[Samsung Galaxy S 5 Unified Development] Tombab:
Well for me Intelli-kernel seem to bring better battery life and phone doesn't heat up as much as with stock kernel but sadly it isn't updated that often. I'm using Gsam battery monitor and average screen-on-time starts to go down whenever I use stock kernel for a while after LOS flash so it's not just placebo.
[Samsung Galaxy S 5 Unified Development] ArvixxBesin:
Found Bug KLTEKDI

One thing I noticed was when someone calls , they didnt hear me and I also dont hear them. Is there any fix ?

edit: my front speakers and Microphones are working.

KLTEKDI (G900J)

Smart Communications. (PH)
[Samsung Galaxy S 5 Unified Development] idtheftvictim:
Trying to install the new nightly on a virgin G900T kltetmo, used odin to flash twrp, and then tried to install it, and I get error 7 this package is for device blah blah blah, and this device is UNKNOWN. Once I was in twrp I wiped System, Data, Cache. rebooted into twrp and tried to flash. Not sure what the problem is. Now I have no OS on my device, downloading the original firmware (6.01) i believe to get it booting again.

Any help would be appreciated.
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 G900T Wrong ROM Version?

Error 7 is a TWRP generic message & the exact error message in the lines just above it is important for troubleshooting.

Maybe you are trying to install the wrong LineageOS ROM on your S5.

The only way to know the truth about what is the exact S5 model is to turn off the phone & boot in Odin Mode (aka Download mode): press and hold Home + Power + Volume Down buttons and confirm with Volume up to Continue.

The PRODUCT NAME that you can see after you accept the disclaimer is the real model number. (screenshot)

I saw several cases on XDA of S5 users scammed with a S5 made for the Chinese market labeled SM-G900F which is for the European market.

What is the exact full name of the file you are trying to flash? For example: lineage-16.0-20200809-nightly-klte-signed.zip.

Did you flash anything besides LineageOS?

Try a S5 LineageOS Super Clean Install including Format Data (not wipe) + wiping System, Dalvik / Art cache & Cache.

***
[Samsung Galaxy S 5 Unified Development] mpower25:
Hello. I've flashed the ROM with Magisk. Magisk Manager tells it's working fine, including Superuser. However, I can't get any app to alter build.prop file.

Root Explorer tells the file is read only, and never requests SU privileges. ES File Explorer requests it when root explorer is enabled, appears in Superuser list, but when I browse root folder, it says it's empty.

And more. On developer options, I can't get the option that enables root for apps. The only options are Disabled and ADB only.

What am I doing wrong?

[EDIT] solved problem by using QuickEdit app to directly open and edit the file. It worked flawlessly with Magisk root.
[Samsung Galaxy S 5 Unified Development] idtheftvictim:
I have tried with super clean install. Haven't I stalled ANYTHING else. Attaching pic of error when trying to install. This phone came straight from T-Mobile so, it's not a fake.
[Samsung Galaxy S 5 Unified Development] kurtn:
Root settings in developer settings is only for addonsu from download/ extras.

For root check, I enable local terminal and type SU in terminal.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: S5 G900T Wrong ROM Version?

Thanks :good: for the photo of TWRP showing the error. I used an OCR app to get the text of the important part which will help this post come up in search engines:

"...E3004: This package is for device: klte,klteacg,

klteatt , kltecan , kltelra , kltetmo , klteub , klteusc ,

kltevzw, kltexx; this device is .

E:unknown command [log]

Updater process ended with ERROR: 7

Error installing zip file '/sdcard/lineage-16.O-

20200809-nightly-klte-signed. zip ' "

There is a foolproof script in the LineageOS package to prevent bricking the phone if the user is trying to install a ROM not made for that device.

And that error says it's not compatible.

The first troubleshooting step is to check the device model and as described in my post above the best method is to check the chip hard-coded PRODUCT NAME which is visible in Odin mode (a.k.a. Download mode).

Second best: turn off your S5 and look at the sticker under the battery. It should be something like SM-...

But stickers can be removed or replaced hence the Odin method recommendation.

Third but this also can be modified: look in Settings > About phone if you can boot in System.

LineageOS 16.0 klte for Galaxy S5 is a unified OS & supports all those models: SM-G900AZ, SM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8, SM-S902L but the other S5 klte variants require their own specific ROM.

There are other S5 models who are not in the klte + variants family as seen in https://wiki.lineageos.org/devices/

***

Edit: [MENTION=3388189]idtheftvictim[/MENTION]:

1- In TWRP did you reboot to Recovery before installing the LineageOS ROM as recommended in S5 LineageOS Super Clean Install after format data & wiping System?

Some S5 users reported failed to install when using twrp-3.4.0-0-klte & their workaround was doing that. Sadly they did not report the exact error message in TWRP.

2- You could try with twrp-3.3.1-0-klte instead. See How To Update TWRP 3.3.1-0 Using TWRP Itself.

Still waiting for your exact device model check. ;)

***

FYI if you Sideload or flash manually you can check the TWRP log for errors: after flashing in TWRP & before rebooting: go to > Backup > Select Storage to external Micro SD card then > Home > Advanced > Copy Log to external SD card then you can connect to a computer to copy it as MTP is enabled by default in TWRP.

***
[Samsung Galaxy S 5 Unified Development] daaaquan:
haha yes this happens to me too very annoying. Are you using a different kernal? Try this

https://xdaforums.com/galaxy-s5/general/mic-volume-gain-mod-s5-t3491483

or just bring a headset with you everywhere. People don't seem to complain if I have a mic plugged in
[Samsung Galaxy S 5 Unified Development] ArvixxBesin:
im using stock kernel from L16 package. and even wired earphone doesnt fix the problem :(

---------- Post added at 02:24 PM ---------- Previous post was at 02:20 PM ----------

I did format data and id tried super clean install but fingerprint scanner is really not working (SCL23KDUI1BNG3 4.4)

but,

when i upgraded to 6.0 (PH3) , and installed L16, its now working.
[Samsung Galaxy S 5 Unified Development] MapisM:
I've been running Lineage 16 on my daily driver GS5 for a lot of time, and it's still performing well enough to not make me wish to look for a replacement.

So, many thanks again for the fantastic job to all those who contributed.

There is just a minor annoying bit, for which maybe someone could point me in the right direction.

Sorry if it was discussed at some stage in the past, I did try some searches but no luck.

I am using Nova as my launcher, but even if it's set as default, occasionally I get a message asking me to chose between Nova and Trebuchet.

A few times, Trebuchet also managed to take over (sort of), apparently setting itself as default.

It's no big deal of course, but I am wondering if there is any way to remove Trebuchet, or if I'm missing some parameters to tell the device to ignore it completely.

Thanks in advance for your thoughts!
[Samsung Galaxy S 5 Unified Development] DragonQ:
Hmm I never had that issue, but I do remember trying to remove Trebuchet once using System App Uninstaller and it caused a continual crash loop, requiring an OS reinstall. So I doubt you can remove it. You can have a look in Development Settings to see if the Trebuchet service is running though, and maybe kill it from there.
[Samsung Galaxy S 5 Unified Development] Zytrel:
I disabled (not uninstalled) Trebuchet with Titanium Backup, if I remember correctly. Absolutely no issues running only Nova.

But be sure to do a complete TWRP Backup before you try, as disabled apps stay disabled even after a system reinstall.

Regards,

zy.
[Samsung Galaxy S 5 Unified Development] MapisM:
Can anyone suggest how to access development settings?

I have developer options already enable (if that's relevant), but I can't find development settings... :o

Ref. disabling Trebuchet with Titanium, am I right in guessing that the device should be rooted?

At some stage in the past, I reinstalled the ROM with no addonsu due to some conflict with GooglePay, and I wouldn't fancy rooting it again.
[Samsung Galaxy S 5 Unified Development] dcarvil:
Titanium Backup requires root. I use Magisk for root, and have had no problems using Magisk Hide to hide root from Google Pay.

I don't know what you mean by development settings.
[Samsung Galaxy S 5 Unified Development] MapisM:
Interesting. Is there any thread with the instructions for installing Magisk on this ROM?

I 'm also unsure of what development settings are - I only asked because DragonQ in his post #3055 suggested to check that out...
[Samsung Galaxy S 5 Unified Development] jachikez:
I was able to fix the network problem that comes before a booloop on Samsung S5 kccat

A couple of days back I was able to install the lineage os16 on my Samsung S5 kccat6 .. the ROM was running pretty well untill I started using the internet. 30 mins into heavy usage LTE signal disappeared.. I tried changing network mode but wasn't working . I restarted the device.

Booting up it restarted back to recovery.. and then I tried again..still not completing boot so I reflashed the ROM.. and started afresh.

Same thing happened each and Everytime I tried using internet especially on LTE..

So I started learning the device.. I noticed the network gives up whenever I used it.

So the Fix.......

1. Never reboot your device ...instead shut it down and power it back on.

2. Try to manage 3G ... LTE still works but get ready to pause your download to shutdown..I notice I had no problems with 3G.

3. Dial this code to change network. Works better than the phones settings network mode Changer... *#*#4636#*#*

4. Never flash any zip file after flashing the ROM.. it's better to flasheverything at ones..

I am not a developer and these fix I have provided is coming from discoveries..

?????? Annoy your ROM in peace
[Samsung Galaxy S 5 Unified Development] kurtn:
I think, you should post there: https://xdaforums.com/galaxy-s5/development/rom-lineage-os-samsung-galaxy-s5-lte-t3534283
[Samsung Galaxy S 5 Unified Development] dcarvil:
I'm not aware of any thread for installing Magisk on the S5. It's been a while since I've done it, but I believe it was just a matter of flashing the magisk zip in TWRP, clearing cache and dalvik, and rebooting. You will be prompted to approve SU requests when Titanium runs.

TWRP is at https://twrp.me/Devices/Samsung/ There are several S5 variants, so make sure you get the correct variant. I'm still using version 3.3.1, but 3.4.0 has been released. The page with the download links also has installation instructions.

Magisk is at https://github.com/topjohnwu/Magisk There is a Useful Links section that contains URLs to install instructions and other very helpful information.

If you run into Magisk problems the General Support thread is at https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/ It is huge, but the most useful current info would be in the last 10 pages or so. Also check https://www.didgeridoohan.com/magisk/HomePage if you have problems.
[Samsung Galaxy S 5 Unified Development] androiddude7899:
Lineage os 16 and 17.1 have the same network issue

RR android Q fixes it aswell as havoc os
[Samsung Galaxy S 5 Unified Development] curiousrom:
[MENTION=9662490]jachikez[/MENTION] posted about the Samsung S5 Plus G901F kccat6 which is not the topic of this thread as you can see in post #1.

This is the correct thread for S5 Plus as [MENTION=8031265]kurtn[/MENTION] linked to above: LineageOS for Samsung Galaxy S5 LTE+ (G901F) / LTE-A (G906S/K/L).

Also the LineageOS maintainers for the S5 Plus are not the same as for the S5 klte + variants.

***

That's false for official LineageOS 16.0 unless you post some proofs including the exact model, network provider & curent baseband (a.k.a. modem or radio).

***
[Samsung Galaxy S 5 Unified Development] curiousrom:
Official LineageOS 17.1 For S5 klte + Variants in the Tubes?

This post is pure speculation & teasing but the S5 klte + variants maintainer & one of the 9 LineageOS directors [MENTION=2693412]haggertk[/MENTION] published several klte + variants (samsung_msm8974) 17.1 commits in the LineageOS Gerrit Code Review recently as you can see in https://review.lineageos.org/q/owner:haggertk%40lineageos.org+branch:lineage-17.1+-hlte

Some are already Merged & some under review & marked as Active @ the present.

One commit is quite intriguing Revert "klte-common: Add support for TWRP": "Kind of don't care about it anymore. We have Lineage Recovery...". :eek:

We don't know yet when an official build will be released if ever or if he will first release unofficial haggertk builds for testing like he did for LineageOS 16.0 before it became official. :confused:

Please don't ask for an ETA (Estimated Time of Arrival) as the classic it will be ready when it will be ready still applies. :cool:

***
[Samsung Galaxy S 5 Unified Development] odoll:
Is it really intriguing? Frankly I'm not too sure: I still run a couple devices which don't get any official LOS any longer, but still unofficial LOS versions. So far I at least can still live with the fact, that most of them have the same "official" TWRP release version. But when the support for TWRP is dropped out of LOS, would that mean the gap in the "two-class society" between these devices will even increase?
[Samsung Galaxy S 5 Unified Development] FiestaLake:
He released unofficial builds: https://androidfilehost.com/?w=files&flid=316966
[Samsung Galaxy S 5 Unified Development] darkherman:
you can't publish the build links unless the developer allows it voluntarily, which I know.

hopes that [MENTION=2693412]haggertk[/MENTION] will publish it in a new post or make it official
[Samsung Galaxy S 5 Unified Development] haggertk:
That "rule" is something pulled out of thin air. If I didn't want the builds found and shared then I would have set appropriate visibility permissions.
[Samsung Galaxy S 5 Unified Development] darkherman:
ok sorry:)
[Samsung Galaxy S 5 Unified Development] snsnse:
Just installed/dirty flashed lineage-17.1-20200907-UNOFFICIAL-klte.zip using the provided recovery. Is this thread the proper place to report potential bugs (and/or post questions about the recovery and its features)?

Thanks much
[Samsung Galaxy S 5 Unified Development] FiestaLake:
I think you can post them here. But don't post regrading that too much :D
[Samsung Galaxy S 5 Unified Development] Rahbar11:
Clean flashed unofficial lineage 17.1, my battery life is better again and the device is really smooth but I noticed some bugs and I can't find a better place than this to post them, so the bugs are:

1. First unlock takes 15-20 seconds. (Not a big deal)

2. System UI becames laggy after using the device for a while and I need to restart the device to get the smooth performance again.

That's all...? Hoping to see official lineage 17.1 soon.
[Samsung Galaxy S 5 Unified Development] tomm1e:
Tested clean install of lineage-17.1-20200907-UNOFFICIAL-kltedv by [MENTION=2693412]haggertk[/MENTION]

Notes:

- Mobile network only works when the first network it connects to during boot is LTE. In this situation fallback to CDMA networks works properly.

- When CDMA is the first network at boot, something breaks, there is no mobile icon and no calls can be made, then it will even fail to connect to LTE after that. There are no segfaults or crashes in the logs.

- Signal strength displays a max integer on CDMA networks. (About phone -> SIM status)

That's all for now. Got logs if they are needed.

Have a great one!!
[Samsung Galaxy S 5 Unified Development] Eadn33:
Lineage in USA

Lineage 16 has been great for me on my 900V and would love to eventually try 17 but after reading several things on carrier switch to VoLTE is it the case that Lineage in general will no longer be an option in USA for most or even all carriers? This would be very sad.

I can’t quite tell for sure from google search results, but my understanding is VoLtE is something that can’t be added to Lineage because controlled by carriers?
[Samsung Galaxy S 5 Unified Development] xyz_969:
Your understanding is correct, and once carriers will start requiring VoLTE on their networks, the S5 with LineageOS will cease to work, unless you switch back to the latest official Samsung firmware which DID support VoLTE. Adding that to LOS appears to be a no-go, probably due to similar reasons why Wi-Fi calling also doesn't work in LOS or other custom firmwares.
[Samsung Galaxy S 5 Unified Development] Eadn33:
Thanks for the reply. I’m happy with my S5, but can’t see going back to Marshmallow without security updates. Is this same thing occurring in other countries?
[Samsung Galaxy S 5 Unified Development] kurtn:
In Germany we are not that fast. And the VoLTE issue us worst for Samsung. Motorola devices have no problem with it.
[Samsung Galaxy S 5 Unified Development] xyz_969:
I can't see myself doing that either, especially not with the god-awful TouchWiz crap.

It is sad that we will be forced away from using the S5 in the USA.
[Samsung Galaxy S 5 Unified Development] Vinczz:
No sound in calls with klteduos (lineages 16)

For more than one year, new releases of lineageos 16 for klteduos contain a bug preventing to have sound in calls.

I finally found the reason in another thread:

https://xdaforums.com/lineage/help/galaxy-s5-duos-sm-g900fd-call-sound-t4072019

The reason is that the property ro.multisim.audio_follow_default_sim should be set to true in the build.prop file.

I think I will have to modify this property at each upgrade unless if corrected in nightly files.
[Samsung Galaxy S 5 Unified Development] guest4711:
You may set it using a MagiskModule.

Simply add a file named system.prop in the modules folder. This file should contain something like

# This file will be read by resetprop
ro.multisim.audio_follow_default_sim=true
[Samsung Galaxy S 5 Unified Development] Sobhan Mazaheri:
Lineages 17.1 haggertk klteduos

lineage-17.1-20200907-UNOFFICIAL-klteduos by [MENTION=2693412]haggertk[/MENTION] bug:

1- Random restart (when entering Telegram)

2- Lagging while working

3- Sometimes the *RIL* disappears

4- The colors are merged between SIM cards 1 and 2 and the operator font is not read

5- The alarm has a problem *(missed alarm)*

Thanks to Mr [MENTION=2693412]haggertk[/MENTION] for their hard work and support of this device
[Samsung Galaxy S 5 Unified Development] snsnse:
I'm running lineage-17.1-20200907-UNOFFICIAL on a klte with opengapps pico.

The only issues I came across so far is that during ongoing phone calls the proximity sensor causes the screen to blank/lock, but it still receives touch events, potentially resulting in various unintended actions.

I might be one of the few people still holding their phones to their heads, but if this could be resolved the 17.1 ROM in it's current state would work as a daily driver for me.

Cheers
[Samsung Galaxy S 5 Unified Development] yoomefoo:
Lineage 16.x missing SD card message

Hello

i have klte and get SD Card missing/ insert device again message at startup.

i cannot see the SD card in "files app"

any quick fix for this?

Thanks For The Romzzzzz

NVM i reformatted it as portable and things are working better...

But now the clock widget is not loading...
[Samsung Galaxy S 5 Unified Development] gretchen.m:
Hi, I am the proud owner of two S5 Duos devices (SM-G900FD) and I've been running lineage OS on them for several years now.

There seems to be 2 issue which I first thought are a device hardware issue (which is why I bought the second phone) - but which now appear on the new one as well.

Note 1: I'm currently running LineageOS 16.1 (build 16.0 from 06/09/2020):

Note 2: In our family, we also have 4 S5 (non-Duos) devices running LineageOS. With neither of them we ever experienced the issues described, o it seems to be an issue related to the dual sim functionality.

Issue 1:

From time to time, it's not possible to receive text messages (SMS): Sometimes it takes hours until delayed messages arrive, sometimes even days (which can be super annoying as SMS transfer is not reliable). The issue does not affect network connection, phone calls or even sending SMS (this works without any problem). Reboot / replacing the battery does not help: The issue remains. It's hard to reproduce the issue as I haven't figured out, yet what triggers it (some days, I can receive SMS without any problem). This is quite annoying as you don't notice that the bug has kicked in again (and people can't reach you via SMS).

Issue 2 (does not happen on clean installs of LineageOS, but only after a while (several days/weeks)):

The phone does not want to connect to fast mobile networks anymore but only connects to EDGE

I don't know whether the two issues are related or independent of each other.

*** Has anybody experienced something similar or are the issues even known already?

*** I'm happy to support with testing (Duos & non-Duos) - particularly because I now own 2 devices so I can test without breaking the one I actually use every day.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Messaging Notification Delay?

If you are using the LineageOS stock Messaging app try Messaging Notification Delay - Fix

Did you try any third-party messaging app alternative?

***