yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 Getting Hot?

When doing something or @ idle?

How old is your battery? The older, the more heat it produces because of increased internal resistance.

Check > Settings > System > Developer options > Running services > and also it's 3-dots > Show cached processes.

Also in Developer options > Memory > Memory used by apps.

Try booting in Safe Mode.

In the Power menu long press either Power off or Restart & select Safe Mode.

Safe Mode besides temporarily disabling all user installed third-party apps will also, if rooted with Magisk, disable all Magisk modules and MagiskHide if you use those.

If the overheating problem is solved then the issue is caused by something you installed.

After testing reboot to get back to normal System & reactivate your apps.

Note that Magisk modules and MagiskHide must be re-enabled in the Magisk app.
[Samsung Galaxy S 5 Unified Development] brt4722:
Battery is 2 months old. I will look at it
[Samsung Galaxy S 5 Unified Development] curiousrom:
See Fake vs OEM S5 Samsung Battery

***
[Samsung Galaxy S 5 Unified Development] brt4722:
Battery is real one.
[Samsung Galaxy S 5 Unified Development] brt4722:
Videochat works but gives beeping sound.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Are you aware that this is a clickbait site monetizing the work of the LineageOS volunteers?

***
[Samsung Galaxy S 5 Unified Development] kurtn:
I would be glad to have a better source for deprecated lineageOS versions.
[Samsung Galaxy S 5 Unified Development] wuko:
Hallo,

sometimes I can't flash a new system OTA.

I can only download the zip file.

How to flash it with TWRP (3.6.2) ??

Thanks
[Samsung Galaxy S 5 Unified Development] kurtn:
Try lineage recovery
[Samsung Galaxy S 5 Unified Development] DeoHeo:
Hello all,

I hope I'm in the right place here, if not then a hint would be helpful as to where best to contact.

I am following the following guide:

Install LineageOS on klteactivexx | LineageOS Wiki

wiki.lineageos.org

I get in the chapter "Installing a custom recovery using Odin" to the point "Click "Start". A blue transfer bar will appear on the device showing the recovery image being flashed." After that Odin crashes without showing me an error message.

I have already tried the following:

- different USB cable

- other USB port

- tried Odin version 1.86 and 3.14.4 additionally (it crashes here too)

- searched the internet and tried the solutions, for example run as admin, ...

I use Windows 10.

Gladly I can still what to work, if something is still unclear.

Thanks for all the work on the LineageOS project.

Greetings
[Samsung Galaxy S 5 Unified Development] kurtn:
Hard to diagnose from the distance. Instead of Odin you can try heimdall on a Linux machine. There are guides on twrp.me
[Samsung Galaxy S 5 Unified Development] bmwdroid:
Which Odin used? For that old device I'd use version 3.0.9.

What lineage recovery file (full name please) did you try it with and where was it from? (and it was changed to ....tar before?)

Btw I'd never used lineage recovery and never read a recommendation for it.

Does the same happen when you try to flash TWRP...tar?
[Samsung Galaxy S 5 Unified Development] JWS5:
Can't switch between calls on Galaxy S5 G900F​

A really annoying 'feature' of Lineage OS 18.1 (I assume it doesn't happen on other OS's) is that if I am on a call or leaving a voice message and someone calls me, either the person I am leaving a voice message for because they didn't answer in time, or someone else, the phone throws up an error message (see screenshot attached), saying that I cannot switch between calls. I have to hang up from leaving a voicemail, or hang up from the previous call and then answer the incoming call when my phone is in the no-active call state, but usually by the time I have got it back to that state the person has rung-off, so I have to call them back.

Does anyone know of a fix for this, that would allow switching between calls?

I am on the most up to date version (02-10-2022), but it has been like this ever since installing Lineage OS 18.1.

Thanks, John
[Samsung Galaxy S 5 Unified Development] Louham:
Hello,

just upgraded to lineageos 18.1 20221002 nightly build using (as usual) embedded Update Manager on S5 klte, and having troubles:

some applications (photo included) crash at startup, then phone is getting warm, seems crashed apps still running in background: phone is getting cooler after reboot.

Very annoying to wait for next update, any idea of workarounds to try ?

Thank you developpers for great job made in keeping good old phones alive ;)
[Samsung Galaxy S 5 Unified Development] Louham:
Problem finally solved:

issue was with the SD Card hosting some of the faulty apps.

Transfered them to internal memory, then ejected SD Card and remount it as external storage: everything is fine but lost photos...
[Samsung Galaxy S 5 Unified Development] PhilEsk:
I have an SM-900a which is AT&T but unlocked. I believe this is also called kiteatt. It is not on your supported list. Is that similar enpough to one of the other models you have tested? These are pretty readily available on the use market for $US 50-60.
[Samsung Galaxy S 5 Unified Development] Skulldron:
Hey guys! I've got a problem. Gonna cut right to the chase.

Kltekdi (SC-04F) is my device.

Charging doesn't work on operating system. It only works in twrp recovery. Any ideas on how to fix this?
[Samsung Galaxy S 5 Unified Development] curiousrom:
AT&T's S5 SM-G900A is Not Supported

SIM network unlocked is not the same as bootloader unlocked.

AT&T's S5 SM-G900A has an impossible to unlock bootloader because that's what they requested from Samsung.

An unlocked bootloader is required to be able to install a custom recovery which in turn is required to be able to install a custom ROM like LineageOS.

Say thank you AT&T!

***
[Samsung Galaxy S 5 Unified Development] Skulldron:
Hi, by any chance do you know why kltekdi, charging does not function?
[Samsung Galaxy S 5 Unified Development] curiousrom:
Search this thread: https://xdaforums.com/search/50059485/?q=kltekdi&t=post&c[thread]=4267517&o=date

***
[Samsung Galaxy S 5 Unified Development] Skulldron:
I believe I have an idea with why the s5 kltekdi doesn't charge. The ROM is detecting the wrong charging port. I recall someone saying that once they used the docomo charging dock that came with these Japanese s5's, charging worked completely normally. So i believe something has been flipped in the driver for the charging chip, and its using the wrong detection.

If anyone wants me to test any fixes for this device, just let me know, i am 100% ready to!
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: S5 5 kltekdi Charging Issue

Maybe you missed this one by @haggertk the S5 klte* maintainer in the kltekdi thread search results:

***
[Samsung Galaxy S 5 Unified Development] Skulldron:
Hi. No no, I didnt miss it but not to worry. The s5 I'm using isn't my daily, its purely for fun, hence why if it is needed, I don't mind testing. Just lmk if anything is needed for klte-kdi
[Samsung Galaxy S 5 Unified Development] uglylove:
Hey guys. Do you know anyone when will be published android12 official Lineageos devolopment for our legendary S5?
[Samsung Galaxy S 5 Unified Development] curiousrom:
Probably never.

See Bad News: No Official LineageOS 19 for the S5 klte* Family.

***
[Samsung Galaxy S 5 Unified Development] uglylove:
Thanks for the info.

I thought with this commit backport issue solved. Really bad news for S5 lovers like me. Hope with this commit we can move forward on official.

Thanks again for Khalvat and Haggertk.
[Samsung Galaxy S 5 Unified Development] kurtn:
Looks like some 18.1 devices will survive 20.0 rollout

https://review.lineageos.org/c/LineageOS/hudson/+/341860
[Samsung Galaxy S 5 Unified Development] curiousrom:
That's if a maintainer wants to continue the support for a given 18.1 device after the LOS 20 launch then it will be kept on the build roster.

Thanks for the pointer. 👍

***
[Samsung Galaxy S 5 Unified Development] JWS5:
Surely I can't be the only person who is experiencing this issue with the Galaxy S5 on Lineage OS 18.1!

Really considering changing operating systems, as it is so annoying.

Any help would be much appreciated.
[Samsung Galaxy S 5 Unified Development] Massedil:
Not sure at all, but for me it is an option of your network provider. In France, some low cost contracts do not include this option, so you can't switch between calls and be warn if someone call you when you are already online. For information , I do not encounter your problem with my phone on the latest LineageOS version.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Official LineageOS 18.1 Updates Now Monthly!

Bad news & good news. LineageOS in the recent past supported only 2 Android versions @ the same time because of infrastructure, LineageOS automated builder, servers & volunteer staff limitations and with the current testing and eventual launch of LOS 20.0 (no ETA questions please), all 18.1 supported devices should be on the chopping block.

But this time the devs made an exception. This LineageOS Gerrit Code Review change removed 89 devices from the weekly build roster Drop 18.1 devices:

And this change added 57 LineageOS 18.1 devices to the new monthly build roster: "I am alive, but very badly burned". Note that the S5 klte* family is on that lineage-build-targets list! :cool: 👍

Several of those legacy devices like the klte* cannot be promoted to official 19.1 or 20 as explained in LineageOS Changelog 26 - Tailored Twelve, Audacious Automotive, Neat Networking, Devoted Developers > Let’s talk about legacy devices chapter.

You can see the current LineageOS build roster in the hudson/lineage-build-targets on GitHub. At the present there are 105 devices supported with LineageOS 19.1 weekly builds & + the 57 LineageOS 18.1 devices.

An amazing achievement for a volunteer-based organization. ↑ (ツ)

I'm grateful for those LineageOS 18.1 devices that will get about 1 years' worth of monthly Android security bumps & some other changes. ٩(- ̮̮̃-̃)۶

***
[Samsung Galaxy S 5 Unified Development] antistress:
Hi, I've changed my LineageOS 17.1 for the 18.1 version on Aug 20th, 2022 (clean install) and everything was ok :)

But this week I've did my first 18.1 upgrade to the latest 18.1 (Oct 23rd, 2022) and since I've trouble taking pictures (OpenCamera), screenshots, opening PDF files (default file manager+MuPDF mini).

For instance :

taking a picture : "impossible d'enregistrer la photo"

taking a screenshot : "impossible d'enregistrer la capture d'écran. Les captures d'écran ne sont pas autorisées par l'application ni par votre organisation"

opening a pdf file : "only owner is able to interact with pending item content://media/external/downloads/2735. No document to open". BUT if i choose within the file manager "SD card", then "Download" I can access files that are store there.

can't rename a file store on my SD Card nor on my phone etc.

I've read that using TWRP "Fix Contexts" Function could solve the problem but I don't have this function in my Recovery (

https://www.reddit.com/r/LineageOS/comments/7k1thi
)

Thanks !
[Samsung Galaxy S 5 Unified Development] uglylove:
Probably, you have file_contexts file issue after upgrade ROM. file_contexts are saved in root on our devices.

I assume you have file_contexts.bak too on your root. If it's, remove file_contexts and change name of file_contexts.bak to file_contexts.

Best solution for me compare with those files manually and edit file_contexts header of external storage with file_contexts.bak on your root.
[Samsung Galaxy S 5 Unified Development] antistress:
Thanks

But how can I access that file ? If I plug my phone via USB I can only see my SD card, and the same If I use default file manager (com.android.documentsui)...
[Samsung Galaxy S 5 Unified Development] Boatshow:
Been using my S5 as a spare alarm clock. Anyone else having problems with the alarm not firing? I think it's affected by deep sleep/doze. When literally nothing else is running in the background I noticed the alarm can fire extremely late or it only fires whenever I wake the phone.

A few months ago I upgraded to a T-Mo Pixel 4A 5G with <30 charge cycles for $175. Just had to coax T-Mo to unlock the phone, took about a week. I installed LOS + Advanced Charge Control to cap the battery to 75%. It has backwards design features associated with newer phones but I've been happy. If you're in the market for an affordable plastic phone with 3.5mm, VOLTE and long support cycles I bet most people here won't hate it.

You need root privileges to do this inside Android. If you're not sure, just boot into TWRP and the file manager should have root. If that doesn't work you can also open a terminal in TWRP.
[Samsung Galaxy S 5 Unified Development] Lederhose:
Edit: Just read that updates are now monthly.
[Samsung Galaxy S 5 Unified Development] nilpernil:
I came here to ask for the updated, I tought the s5 will be discontinued, but I'm happy this is not the case!!

I use my S5 to watch youtube vanced from the bed and as my alarm clock, i love it, it has the perfect size for that, I can hide behind the blanket like if I was 9 and start watching youtube till falling asleep ☺️☺️

Thanks to the dev's for maintaining the s5 and thanks lineage os too ❤️❤️❤️
[Samsung Galaxy S 5 Unified Development] kurtn:
Updated klte to November security patch release. Monthly 18.1 builds seem to run stable
[Samsung Galaxy S 5 Unified Development] antistress:
Thank you uglylove & Boatshow : I'll kept your tips for the next time, it will be useful for me. As for now, monthly update solves the problem without further intervention ! :)

Thanks again
[Samsung Galaxy S 5 Unified Development] jian1:
So can I safely jump into this LineageOS thingy for S5 now? I don't want a buggy android experience and that was the main reason why I haven't flashed S5 for LineageOS....
[Samsung Galaxy S 5 Unified Development] kurtn:
It's not buggy. Maybe you get a small degradation in camera quality. And some very security sensitive apps will not run. Like video streaming or banking
[Samsung Galaxy S 5 Unified Development] x2k13:
As long as it's an official ROM and you're not messing around with Magisk this shouldn't happen.
[Samsung Galaxy S 5 Unified Development] Not-Aus:
Camera quality has nothing to do with Magisk and not running apps can be made to run with Magisk.
[Samsung Galaxy S 5 Unified Development] x2k13:
You misunderstood. I was referring to banking apps. Magisk can be detected, Zygisk or not. Don't use Magisk if you need banking apps, it just causes a lot of additional issues and a version later the apps devs found out how to detect rooted devices again. But okay, if you still want to live dangerously and have a potentially insecure and defunct device, go ahead.
[Samsung Galaxy S 5 Unified Development] x2k13:
@haggertk Cell Brodcast national disaster warnings don't work on LineageOS 18.1 (at least on the S5) in Germany (they had a nationwide CB test earlier). This needs to be fixed soon, since that is a vital function for peoples safety.
[Samsung Galaxy S 5 Unified Development] vanMacG:
Worked on two S5 without a problem for me.
[Samsung Galaxy S 5 Unified Development] x2k13:
Then you are lucky. I've heard from several people using the S5 with 18.1 who had no alert. Since I retired that phone in favor of Vayu, it's not my problem anymore. But it's the problem of all other users where that won't work. Just saying.
[Samsung Galaxy S 5 Unified Development] wuko:
Hallo.

S5,klte: no problems

suggestion: for nationwide alerts by CB

there should be the same notifications like normal SMS (tone,led,vibration) not only vibration.
[Samsung Galaxy S 5 Unified Development] vanMacG:
I just wanted to mention that it worked for me with 18.1, so it's not a problem in general.

I had a different sound than normal SMS + vibration. I think this behviour is intended, it should alarm you, not sound like a normal SMS...
[Samsung Galaxy S 5 Unified Development] zimral.xda:
As far as i can see, this german "cell broadcast national disaster warning day" was a total DISASTER! There were mixed results from region to region, provider to provider and phone to phone. I have a total of five phones two actual Pixel5, one P4a, all have either Stock A13 or A13 based CalxyOS, and one 2016 iphoneSE with IOS 15.7. All had these alerts enabled but only an old (2017) Huawei P10 with a vodafone sim card received the alert. As far as i have infos out of the neighbourhood, mostly german Telekom (T-mobile) was not able to transmit this alert.

The CB "technology is at least 20 yeras old. It is unbelieveable, germany becomes a third world country more and more each day.
[Samsung Galaxy S 5 Unified Development] jenssa:
Thanks a lot for this! I really appreciate it. I realized just now that Google pay again detects root even if my phone passes the Magisnk SafetyNet test, and I have enabled MagiskHide (as well as hiding the Magisk app itself and hiding Googe pay by the shield). Strangly, Google pay worked fine when the phone failed Magisk SafetyNet test. I should have mentioned above that I was unable to reinstall the BITGapps (for some reason the app package did not show up even if flashing seemed to run to completion in both sideload Los-intallation as well as twrp-installation from internal storage in a second (or third) try), and instad I flashed the MindTheGapps-11.0.0-arm-20210220_134931.zip, which works fine (although I liked the BITGapps package, which seems lighter? At least now the phone seems a bit slower). I will test out your proposals another day that I have more time.
[Samsung Galaxy S 5 Unified Development] Nobby1960:
I installed LOS 18.1 (20210502-nightly-klte) so far - complete clean flash with the current TWRP. The ROM makes a good and fast impression. I haven't gotten to installing all of my daily used apps yet. Root access with Magisk worked immediately.

But I have problems with the microphone gain in Telegram and WhatsApp - voice messages are too low. The voice recorder is also too low. Is there any solution to fix it?
[Samsung Galaxy S 5 Unified Development] ludwig83:
https://xdaforums.com/t/rom-unoffic...-samsung-galaxy-s5-klte.4209545/post-84661995
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 Mic Boost Magisk Module - Stereo Recordings

If your device is rooted with Magisk, thanks to a post by @dcarvil in the old 16.x thread here for inspiration, I created a module for myself for a S5 G900M klte to boost the mic via the mixer_paths.xml because my WhatsApp's sound messages were too low.

I did not create a module installer for it yet but you can download the attached Module_mixer_paths_mic_Boost_curiousrom.zip, unpack it and copy the mixer_paths folder to /data/adb/modules & reboot.

After that in the Magisk app > Modules: enable mic_boost_118 as seen in the screenshot & reboot.

I boosted the value for both mics near the USB port and the one on the top of the S5 next to the IR blaster from 95 to 118. If you change it to a higher value expect some distortions in some apps:

<!-- Recording Scenario -->
<path name="rec-main-mic">
<path name="main-mic" />
<ctl name="DEC2 Volume" value="118" />
</path>

<path name="rec-sub-mic">
<path name="sub-mic" />
<ctl name="DEC4 Volume" value="118" />
</path>

I use a vacuum cleaner once in a while to clean the USB port, the mic hole next to it & also the top mic hole next to the IR blaster which is used when you have stereo recording enabled in some third-party recording apps like Easy Voice Recorder for example. (screenshots)

You can modify the mixer_paths/system/vendor/etc/mixer_paths.xml file in that module folder if you want to change the values of other stuff & reboot to apply.

***

If not rooted using adb root or File Manager in TWRP you can pull the /system/vendor/etc/mixer_paths.xml file, modify it & push it back to the device but that will not survive an update & you will have to redo it afterwards. :-/

Maybe @haggertk could apply this mic boost mod to the official LineageOS 18.1 for the S5 klte family as it is a common issue reported by several users? :unsure:

***

Note: thanks @ludwig83 for your post above linking to my post in the abandoned unofficial S5 18.1 thread. Might as well re-post it here, add a note for non-rooted devices and pinging haggertk about it.

***
[Samsung Galaxy S 5 Unified Development] curiousrom:
LineageOS Snap Camera U.I. the Fix is in the Tubes!

Good news, following a conversation with a dev here in the Lineage subreddit this commit was merged & will be included in next build: Snap: use translucent control background on 16:9.
[Samsung Galaxy S 5 Unified Development] x2k13:
One thing I noticed, after reboot, when entering SIM PIN, it takes a long time before the lock screen appears. Doing the same on jfltexx on 18.1 doesn't lag like this.
[Samsung Galaxy S 5 Unified Development] Boatshow:
Dirty flashed device SM-G900T from 16.x and ran into the lockscreen problem here. Performing the fix worked. I think it happened because I was using a passphrase for encryption but a pin for screen unlock. After resetting the screen PIN I was able to change my encryption passphrase back by following these instructions:

Fire up the terminal and do this:

su
vdc cryptfs changepw TYPEOFNEWPASSWORD OLDPASSWORD NEWPASSWORD

where TYPEOFNEWPASSWORD can be any of password, pin, pattern (if you use a pattern, match the position of the dots with corresponding numbers on keypad to obtain a numeric string)

SD card was still recognized but I couldn't play any of the music on it. Had to back up the files, format it as portable again and copy the files back.

fbs' tuned kernel is too old for Android 11. Would love to undervolt the CPU on 18.1. if there's a way to do this on the stock kernel please tell me.

The developer option to hold "back" to force close an app is gone but it seems like it will come back.

Some minor changes in Android 11 that I don't enjoy.

Bluetooth seems more stable than usual. Fingers crossed.

Just some nitpicks. The OS seems pretty stable so far. Great work!

Anyone not using most of gapps but need the swipe keyboard? I have a Magisk module for you. I downloaded the arm32 Android 10 blob from OpenGapps and put it in this magisk module that originally had the arm64 blob. Zip included at end of post.

Edit: Moved the keyboard Magisk module to this thread:

https://xdaforums.com/t/magisk-10-11-swipe-to-type-swype-glide-for-gappless-phones.4292395/
[Samsung Galaxy S 5 Unified Development] x2k13:
I'm not sure if you're referring to my post above yours, but I can use the lock screen with my PIN and get to home screen, it just takes at least 30 sec. to unlock the SIM. This is not the case on jfltexx, wich instantly unlocks the SIM.
[Samsung Galaxy S 5 Unified Development] grabelbaum:
For anyone also experiencing the issue where the navigation buttons are not working and mobile data not working: You have to run the setup wizard; not the one from google but the one from lineageOS:

adb shell am start org.lineageos.setupwizard/org.lineageos.setupwizard.SetupWizardTestActivity

Source: https://github.com/LineageOS/androi...ard/blob/lineage-18.1/start_lineage_wizard.sh