This is similar to my wife´s klte. 3...5% per hour. BBS showed 97% deep sleep nevertheless. Rolled back to 17.1 with same app setup and opengapps pico and same sync settings, the battery consumtion is down to less than 1% per hour.Dont worry i'll watch it over the day. As mentioned it is not really productive currently. All tasks are killed except GSAM. No fingerprint or lock screen or screen saver. I am working over 40 years in software development, datacenter support/networks and application support. I've seen alot of impossible things in my IT- life..... ...and dont forget the users: "i did nothing...really, ..nothing..."
update: BTW it is now at 4,0% per hour....total of 88... very interesting. What about this old tale that sometimes a battery has itself to "arrange" with a ROM - is this a fairy tale ? Or are there "Gremlins at work" ?
Update 1500 CET: 3.1% per hour
You need to have a "user-acceptance-test device" I still have my other prod klte as a backup with 17.1. I run that from spring 2020 until spring 2021 when i installed 18.1 on the phone i used with 16.x . It has the same setup, a good battery. Each year i keep my current one and update the other (older) one to the new LOS version. Therefore its easy to compare them lying side by side and depending on that i can agree with your experience above.This is similar to my wife´s klte. 3...5% per hour. BBS showed 97% deep sleep nevertheless. Rolled back to 17.1 with same app setup and opengapps pico and same sync settings, the battery consumtion is down to less than 1% per hour.
Since she was complaining so much, I cannot experiment too much, unfortunately...
There no official archive. You maybe find something in
I am new and i am also interested for the lineage 17.1 version.the latest LOS17 version in my archive for the klte is the following:
lineage-17.1-20210411-nightly-klte-signed.zip plus the recovery.
In april i switched over to LOS18.1.
if you send me a link where i can upload it we can give that a try.
I dont have the checksum file but i only download from lineageos.org therefore i can state that this is the original file.
Looks like you are running heavy apps. Start from scratch and add one by one till you see the lagging.Someone with deeper insight than me may shed some light, but i think the S5 is hopelessly under-powered now. High cpu load and memory management working overtime due to insufficient ram(my Note 10.1 2014 with Snapdragon 800, 3GB RAM and Los17.1 performs considerably better, probably all for that one GB) cause high latencies and timeouts with and without error messages.
And extremely high battery usage and temps. Cpu cores only know two stages anymore(offline/idle and 2,45ghz), which denotes how puny the SD 801 has become.
I use Naptime to save battery in standby. Though this helps somehow, it also de-calibrates the battery monitor. I think you can also see it with Gsam & Co:
Battery consumption in standby may be low(1%/h), but once the device is out of standby, battery percentage will drop rapidly for a limited time and the end result is catastrophic. I'm (got another fresh battery one year ago) down to about 9-12h standby with at most 3 hours SOT, all the way down from more than 24 hours standby and more than 7 hours SOT in 2016/17 and up to stock 6.1.
And you are much less productive when just waiting for something for most of the time or having to repeat stuff or kill and re-run apps because of timeouts and non-responding/endless tasks(silent timeout).
I personally plan to start looking for LOS19.x (or whatever the name will be) in the LATE march/april timeframe.
|klte||SM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8|
|kltechnduo||SM-G9006W, SM-G9008W, SM-G9009W|
|kltekor||SM-G900K, SM-G900L, SM-G900S|
It's (likely) not. I've found an issue in the legacy paths of the recent sdfat (Samsung exfat driver) revision. I haven't been able to recreate the bug/assert after the fix. After getting a second confirmation I'll upload the merge the change.SDcard corruption may be caused by a recent Google security patch. I experienced this once with the "new" unofficial LOS17 for the Samsung P605, coming from unofficial 14.1,where this never happened before. But others started complaining about the same issue, after this antique rom got a recent security patch.