yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] jerfsonpaiva:
That work. Thanks.
[Samsung Galaxy S 5 Unified Development] reyanshzuber:
May I request for the links of 16.1 and 17.1 for G900F please. Thanks
[Samsung Galaxy S 5 Unified Development] kurtn:
There no official archive. You maybe find something in

https://androidfilehost.com/?a=show&w=files&flid=52842 or

Lineage.microg.org
[Samsung Galaxy S 5 Unified Development] zimral.xda:
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.
[Samsung Galaxy S 5 Unified Development] wiwi11:
I am new and i am also interested for the lineage 17.1 version.

wiwi11
[Samsung Galaxy S 5 Unified Development] zimral.xda:
I had an unexpected reboot this morning. Phone was sitting it its stand doing nothing. Discarge is at 1,2% per hour currently/since yesterday. Battery level was at 28%. Hardware is in very good condition. Works perfectly with 17.1 and with 18.1 until i did update to 20210801 using the built in updater. I am currently unboxing one of my test klts's with a build as of 20210711 to see how both can be compared. Have new batterys in both devices and i am currently charge them to the same battery level.

Will keep you posted here.
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 Battery Usage @ Idle

Oh My Gosh you are doing something wrong!

GSam screenshots with 0%/hour discharge I made today on Galaxy S5 G900M LineageOS 18.1 klte build 2021-08-01.

Hint: it's your setup, not the ROM. ;)

Details on setup & test method explained in previous post: S5 klte LineageOS 18.1 Battery Usage @ Idle Test - Sleeps Like a Rock.

***
[Samsung Galaxy S 5 Unified Development] zimral.xda:
Ok, if its my setup:

Why do i have another phone with the same setup + Google api and a battery which is a little bit older, which has now 4% loss in ~4 hours (the one running 2021-07-11) and the first one with a litte newer battery no google stuff which has now a battery loss of 13% in four hours. All of my four phones in use have the same setup the two others are a pixel3 and a pixel2 running LOS18.1. you showed me just a different way to look at the problem (thats interesting thank) but i have alot of information now to show that using the same hardware even a better battery will not prevent you from this heavier battery drain. And my other phone has google services running which cost additional power. without google i had normally ~0.5 to 0.8% per hour. I dont want to blame someone, RESPECT for the work of all maintainers! but there are some facts i cannot ignore. I think we should keep an eye on this and do some more analysis and we will see how it will develop. Unfortunately i cannot revert my current prod klte back to an older build as i have to use an RSA key generator on it and with a reset of this app i have to deploy new keys on my other devices. I cant do this currently due to my jobs workload.

We will seee if there are other users reporting similar problems when the 20210801 build is more widely in use.

Thanks for your help and additional idea with the GSAM setup.
[Samsung Galaxy S 5 Unified Development] supachris:
I'm pretty sure it's the setup in combination with the rom. Something of the non ROM setup behaves different on 17.1 here. Maybe one app or service interacts in another way with the system on 18.1 and leads to more power consumption. My wife's klte has the same setup, apps and hardware, it needs 5% overnight in 17.1 but 40% in 18.1. Very strange. There seems to be no certain app eating the battery if believing in BBS.
[Samsung Galaxy S 5 Unified Development] zimral.xda:
I agree with you in that. Such a small phone is a full blown Linux computer these day including its complexity. We should not say "This cant be the case" thats too easy thats what old people have done decades ago , my dad included. There are alot of things between heaven and earth and one day we will track this down and help Mr. Haggertk to continue support of this old and lovely phone.
[Samsung Galaxy S 5 Unified Development] Chatbox:
Is anyone able to get a Fiio Q1Mk2 DAC working with the latest 18.1 build? My G900F was on 17.1, and the DAC was working then. However, ever since I moved to 18.1 a few months ago, the DAC is no longer functional with the phone. On the other hand, for reference, my i9505 (S4) on 18.1 is working with the same DAC.
[Samsung Galaxy S 5 Unified Development] vd6x:
My kltedi still can't charge 😀
[Samsung Galaxy S 5 Unified Development] lecorbusier:
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).
[Samsung Galaxy S 5 Unified Development] kurtn:
Looks like you are running heavy apps. Start from scratch and add one by one till you see the lagging.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: S5 kltekdi Charging Issues

I guess you mean kltekdi.

Which model number do you have exactly and what is the build date of the LineageOS package that you installed?

See this post: Re: S5 kltekdi Charging Issues.

I did not get any reply from the kltekdi user @Hamza Shahbaz or haggertk. ¯\_(ツ)_/¯

***
[Samsung Galaxy S 5 Unified Development] vd6x:
Oh yeah kltekdi, sorry typo.

I'm sure Hamza Shahbaz still having the same problem as me
[Samsung Galaxy S 5 Unified Development] curiousrom:
Read the post again, especially haggert's quote.

***
[Samsung Galaxy S 5 Unified Development] x2k13:
No build today:
[Samsung Galaxy S 5 Unified Development] EojjN:
Hi everyone,

I have a kltekdi running Android 5 which I'd like to update with this ROM.

What do I need to do to get to version 6 and have 18.1 working?
[Samsung Galaxy S 5 Unified Development] curiousrom:
How To Install LineageOS 18.1 on S5 kltekdi

Which model exactly?

Either flash Samsung stock OS 6.0.1 for your device that you can get on sammobile.com or updato.com (their download pages include instructions & link to Odin) or see S5 Odin Flashable Modem & Bootloader .

Then either follow the official installation guide using Heimdall & the Lineage recovery: Galaxy S5 LTE (SC-04F/SCL23) (kltekdi) or I wrote this for Windows PC users & LineageOS 16.0 because Odin is so much easier to use compared to Heimdall to flash TWRP but the same steps works for 18.1 & I prefer TWRP on my S5 G900M: S5 super clean install.

Caveat: you may have to boot in recovery to charge your S5 kltekdi. 🤪

See this post: Re: S5 kltekdi Charging Issues.

I did not get any reply from the kltekdi user @Hamza Shahbaz nor @haggertk. ¯\_(ツ)_/¯

@vd6x also reported a S5 kltekdi not charging issue here but he did not reply to my question about the exact model. SC-04F or SCL23?

***

See other posts about installing Magisk on S5, screen lock, etc that I linked to here

***
[Samsung Galaxy S 5 Unified Development] EojjN:
I have the SCL23. The not charging issue sounds like a big problem. I would probably want to wait for that to be resolved before flashing. Thanks so much for your detailed information.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: S5 kltekdi Charging Issues

The problem is that @haggertk does not have that model so he cannot test the custom bootimage he made to fix the issue.

You could contribute by testing it & reporting back.

Let's see if haggertk replies. Or maybe he's gone fishing to a remote location during his vacations. ¯\_(ツ)_/¯

***

BTW you are welcome.

***
[Samsung Galaxy S 5 Unified Development] EojjN:
I have the SCL23. The not charging issue sounds like a big problem. I would probably want to wait for that to be resolved before flashing. Thanks so much for your detailed information.

Yeah of course, as long as my device doesn't get bricked, I'm happy to help the development along!
[Samsung Galaxy S 5 Unified Development] Vini69:
Kernel build - Help needed to complete process

So, I have been trying to build my own kernel for LOS 18.1

Phone : S5 KLTEDUOS

System : Windows 10 + WSL2 + Ubuntu 20.04.2 LTS

Kernel source : https://github.com/LineageOS/android_device_samsung_msm8974-common

Toolchain : https://github.com/LineageOS/android_prebuilts_gcc_linux-x86_arm_arm-linux-androideabi-4.9

After studying the different config files, I choose : /arch/arm/configs/lineage_klteduos_defconfig

Build completes OK and I end up with an output directory with zImage and zImage-dbt

I understand I need to create a bootable image using mkbootimg :

1 : which image do I need to use : zImage or zImage-dbt

2 : it seems to require a ramdisk.gz - after a lot of research, I couldn't find where/how to get it...

3 : I tried a few iterations from mkbootimg, but none would produce a bootable kernel image

mkbootimg --cmdline 'console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3 zcache.enabled=1 zcache.compressor=lz4 buildvariant=userdebug' --kernel ./zImage --base 0x00000000 --pagesize 2048 --tags_offset 0x01E00000 --output ./boot.img

Would someone (@haggertk) be kind enough to guide me through the final steps to produce a bootable kernel ?

Thanks in advance.
[Samsung Galaxy S 5 Unified Development] linrax:
This is amazing, thx so much for maintaining this device. I made a clean install with the los recovery (finally without twrp ;) without gaps and it works like charm. In comparison to my redmi note 7 it is just a bit slower, but I will use the S5 instaed from now on.
[Samsung Galaxy S 5 Unified Development] Boatshow:
@Vini69 You use zImage.

This is probably not the right way to do stuff but it works for my builds here. First you need to open your device's LOS 18.1 zip and grab the boot.img. I use a script called "AIK-Linux" to chop up the parts. There's also probably a Windows version but I'll assume it's not much different.

1. Put your donor boot.img in the AIK-Linux folder

2. Run unpackimg.sh to unpack it. A folder called split_img should appear.

3. Go into split_img and delete "boot.img-kernel"

4. Get the zimage you just built and rename it to "boot.img-kernel"

5. Put the new "boot.img-kernel" inside the split_img folder

6. Run repack.sh

7. You should get a image-new.img. Rename it to boot.img to help you remember. You can put this on your phone and flash it to the boot partition in recovery to install just the kernel. Or you can replace the boot.img in the LOS 18.1 zip.

8. Get rid of the .imgs and run cleanup.sh when you're done

9. Boot and confirm the new kernel was successful installed by running "uname -r" and "cat /proc/version" with root. You should be able to tell with the timestamps.

https://xdaforums.com/attachments/kernel_adiutor-png.5302705/
[Samsung Galaxy S 5 Unified Development] Nico059:
I would like to thank all the folks that maintain our good old Samsung S5 uptodate with this ROM and specifically @haggertk ! Thanks thnaks thanks !

FYI, I successfully flash lineage-18.1-20210718-nightly-klte-signed.zip + MindTheGapps-11.0.0-arm-20210412_124103.zip with TWRP 3.2.3-0 on 2 devices (SM-G900F = klte). Everything work fluently, I don't have battery drain at all (lost only 4% on the night only, and the batteries are original-7 years old).

Regards !
[Samsung Galaxy S 5 Unified Development] curiousrom:
Old TWRP

Thanks for the report. :cool: 👍

That TWRP 3.2.3-0 version is too old (2018-07-30) and OTA updates via the built-in Updater may fail because of it. Ref. Settings > System > Advanced > Updater.

See How To Update TWRP Using TWRP Itself.

FWIW my Galaxy S5 G900M LineageOS 18.1 klte build 2021-08-01 @ the present + MindTheGapps + Magisk 23.0 + TWRP 3.5.2_9-0 (2021-04-06) works fine and was OTA updated dozens of times.
[Samsung Galaxy S 5 Unified Development] lecorbusier:
@kurtn:

The heavy apps are e. g. Firefox running a single tab with a fancy scripted page with lots of ads.

Same for news apps (w/o subscription & overloaded with ads). Adblocking helps somewhat and is already taken into account(DNS66).

Then there's weather apps with fancy layouts & effects.

The xda app is sort of medium heavy-weight.

Tapatalk not at all.

Same goes for email apps and even Youtube.

Of course not satnav stuff, or Google Earth, swipe a bit on the map and it crashes.

Another "heavy app" would be the Amazon app or any other shopping app. Online shopping should be one of the most basic tasks, with emails becoming as oldskool as SMS or wired calls & stuff i grew up with....
[Samsung Galaxy S 5 Unified Development] Nico059:
Thanks @curiousrom for the link to update TWRP ! yes my TWRP is a old .... l will give it a try. OTA is a real bonus to have, and if you confirm it works ! It's always stressfull to update a phone (as I don't do that regularly) so I try to minimize the manipulation.

My next step is to install Magisk too (I need to understand how it works ... I used addon su previously...), do you have a link with a comprehensive explaination about Magisk ?
[Samsung Galaxy S 5 Unified Development] curiousrom:
Galaxy S5 LineageOS 18.1 - Magisk Installation and Magisk and MagiskHide Installation and Troubleshooting guide.

If you need help: XDA Magisk support thread where you can find several helpful local experts.

After updating TWRP create a full backup except the cache before updating.

***
[Samsung Galaxy S 5 Unified Development] zimral.xda:
Start at 1300 CET: 4.5% per hour

Update 1500 CET: 3.1% per hour

Update 1700 CET: 2.8% per hour - ~17% in 6.5 hours

Update 2355 CET: 1.6% per hour - Strange

Update 2021-08-03 1100 CET: 1.2% per hour

Just want you keep you updated here.......

Its currently (2021-08-11 0800 CET) running at 0,6% per hour since 4,5 days nearly doing nothing.

Nothing has been changed, no apps running except GSAM and a few times a day a RSA Token app.

This is weird.

will re-charge now.

Maybe i change the half year old battery against an older one and see if there is a difference. But i guess no.

The older battery runs fine in another klte with 18.1 build as of 2021-07-11 and (for test purposes) an actual gapps "pico".

Have the "Gremlins" been disappeared?
[Samsung Galaxy S 5 Unified Development] lecorbusier:
I never had exceptional wear on a battery. A max of 5% capacity loss per year is normal and that was which i gained back with each new battery in any device, so it makes certainly sense if the S5 still has its original battery. Mine the third or forth one, and i bought one of the last g900fs, when the S6 was out.

One year ago i exchanged the dual cell 8000mAh battery of my P605 tablet. Battery had about 60% capacity left after 7years, but most of the decline happened when the battery began to bulge to at least double thickness some months ago, deforming the whole tablet.

After long phases of standby, check for rapid batter decline(about 1%/min after wakeup). This will ruin the show. I just got 1 day of operation with about 2h 10min SOT, doing stuff as mentioned in my recent post, all from home via wifi and with low brightness, fitting for interior use.
[Samsung Galaxy S 5 Unified Development] x2k13:
If I were you I would hurry up to get rid of that thing. It's a timebomb, literally.
[Samsung Galaxy S 5 Unified Development] zimral.xda:
i am keeping an eye on my batterys. its important that you charge them completely when they are new, they need to have a dozen cycles or so. after that do not discharge to a very low level and do not overcharge (leave them connected to the power supply for hours/over whole night). A Li-Ion has a limited amount of possible "cycles", this is between 500 and 1500 depending on the manufacturers quality. I dont expect, that the usual phone battery for a handful of $/EUR's from Amazon or AliExpress is a rocket-science approved "Hi-Tech/high-Quality-product" :)

I have some they are more than 6 years old and they are still working. I replaced one in a Huawei Mate 20L some weeks ago and this seems to have only 60% of its design capacity, i assume its a very poor quality. I am still trying to push this to a higher value, will see if it works.
[Samsung Galaxy S 5 Unified Development] Andresine:
Is it possible to add a numeric row on the keyboard in the next builds, like on the samsung keyboard with towchwiz? Thanks in advance
[Samsung Galaxy S 5 Unified Development] Garry58:
You can always install a different keyboard. I'm using Gboard, which has numeric row option (even though I don't use it).
[Samsung Galaxy S 5 Unified Development] x2k13:
That's a myth from the early days of li-ion battery technology. Back then, the charger circuits weren't smart compared to what's in our phones today. All modern charger circuits measure the voltage continiously and as soon as the battery is fully charged, leaving the cord plugged in doesn't damage the battery.
[Samsung Galaxy S 5 Unified Development] zimral.xda:
Yes this should be the case. But it depends on the charger. I can confirm that the Pixels chargers i have in use (Pixel2, 3 and 5 - seems to be all the same) have this feature. I am not sure about the old S5 chargers. Therefore i use a charger with the "minimum level" as of QC2/3. Huawei chargers which come with the Mate20 and the p10 have that feature either. Be careful if you use those extra cheap chargers.
[Samsung Galaxy S 5 Unified Development] Terry Barnaby:
Is anyone else having an issue where a long press on any of the pull down quick buttons (such as Wifi) crashes the UI ?

Since a month or two ago I have been having this issue on 4 different S5 klte phones, all Lineageos 18.1 + Gapps and very few other apps installed. See: https://gitlab.com/LineageOS/issues/android/-/issues/3715
[Samsung Galaxy S 5 Unified Development] Zytrel:
Erm, all the charging logic is in your phone, the charger acts merely as a power supply. I agree to avoid cheap ones due to general security reasons (overvoltage, explosion), but in terms of charging logic they're just completely irrelevant.

Regards,

Zy.
[Samsung Galaxy S 5 Unified Development] kurtn:
No problem here. Klte july 18
[Samsung Galaxy S 5 Unified Development] AloneDisaster:
But, it's better to use Battery Charge Limit to cut the power according to the battery percentage that is set as desired.
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 LineageOS 18.1 Update 2021-08-15 - Android Security Bump

Using the built-in Updater I OTA updated S5 G900M LineageOS 18.1 klte build 2021-08-01 + MindTheGapps + Magisk 23.0 + TWRP 3.5.2_9-0 to build 2021-08-15: everything went smoothly & GApps + Magisk survived the update.

There are a few changes as you can see in https://download.lineageos.org/klte/changes/ but most importantly it includes the monthly Android security bump: Merge tag 'android-11.0.0_r40' into staging/lineage-18.1_merge-android-11.0.0_r40: "Android 11.0.0 Release 40".

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

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

See Android Security Bulletin - August 2021 for details about the security fixes.

Contrary to update 2021-06-13 as I posted here and update 2021-08-01, shortcuts on Home created with the LineageOS Settings widget & a third-party app survived. 🤷‍♂️

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.

This issue as reported also by @Terry Barnaby here is still present for me with this update:

More details, tests & logcat in an other post.

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

***
[Samsung Galaxy S 5 Unified Development] Boatshow:
I noticed the firmware repository now has baseband G900TUVU1GRJ1 for the SM-G900T. It's actually pretty old but nobody could source it for a while, nice!

Anyone have any remarks about it before I flash it?
[Samsung Galaxy S 5 Unified Development] zimral.xda:
As far as i remember the S5/klte does not have any circuits/sensors to determine the charge/discharge per time to check for design/real capacity. This is the reason why the "AccyBattery" App is nearly useless on that phone. The developer of the "Chargie" (a battery charging control tool) answered my questions regarding his product that no actual smartphone is able to control (mean stop charging) at a given battery voltage which is used to determine the charging level. "Chargie" is doing that with an additional bluetooth connection acting as a control loop and then cutting the connection between the power supply and the phone. To be precise it is not possible that the charging circuits of a phone tell the power supply "Hey i am full now stop charging"! Decreasing the current level is done by the power supply by checking the battery's voltage level. Exacly the same thing as car battery chargers do and any other at least partial intelligent chargers. Sorry to say that but i think "Battery Charge Limit" is an app to collect some charging/discharging statistics but it is not able to completely control the charging process and stop it at a given level as this is in general not possible without additional hardware.
[Samsung Galaxy S 5 Unified Development] AloneDisaster:
You are right about data collection, and may for Battery Charge Limit using battery percentage data in notification to control charging stop and recharge according to the percentage we have set in the app, when the battery percentage has reached the limit we set, the application will make modifications to /sys/class/power_supply/batt_slate_mode (in my case. The control file can be different depending on the device) then changing the value to 1 or 0

"This is what the developer said :

It is 1 as default for me, when it is made 0, the phone doesn't charge even when connected to charger.

So, for me

1: Charging enabled

0: Charging disabled"

Src.

While for my kltekor

0 : charging enabled

1 : charging disabled.
[Samsung Galaxy S 5 Unified Development] g000n:
Not sure which update is making my phone boot into twrp and not the system, when I try to boot into system it just loads lineageos image and then takes me to twrp

Any help on how I can fix this?
[Samsung Galaxy S 5 Unified Development] kurtn:
Depends on what you have installed. But some basic steps are wiping caches, or reflashing lineageOS (and GApps)
[Samsung Galaxy S 5 Unified Development] g000n:
I went into TWRP and wiped cache, that didn't work

I reflashed the latest version of the rom + gapps and the same thing happened -> LOS boot screen -> phone restarts -> goes into twrp

Not sure what I can do to fix tis