yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] curiousrom:
No Sound During Calls - S5 G900FD (klteduos)

What happens if you use earbuds or speaker phone? Still no sounds during a call?

You said that you have a S5 LTE Duos G900FD (klteduos). Did you try turning off the device and switching the SIM to the other slot?

Did you try with an other SIM?

What does it say in > Settings > About phone > Android version > Baseband version?

What does it say in > Settings > About phone > SIM status > Mobile voice network type?

Check > Settings > Network & internet > Mobile network > Advanced > Access Point Names > APN > and make 100% sure that they are identical to your network provider's current recommended settings then turn off the device, wait a few seconds, turn back on, then send an SMS before receiving one.

***
[Samsung Galaxy S 5 Unified Development] Hasan1122behj:
I change from gsm to wcdma and sound like problem almost solved 😊😊

@Fandroid Tech
[Samsung Galaxy S 5 Unified Development] bersem:
Cant load YouTube. Message appears: App should be updated to newer version, but its already the latest from Playstoreo_O

It starts after clearing data of YouTube App... And the same message after second try

Someone else noticed the same issue ?

Regards !
[Samsung Galaxy S 5 Unified Development] curiousrom:
YouTube Asking for an Update But No Update in Play Store

This is a known YouTube/Play Store issue on the S5 since at least LineageOS 16.0.

See YouTube app is not getting update. in the LineageOS bug tacker.

Maybe it's Play Store that gives older YouTube version for older devices. ¯\_(ツ)_/¯

As a workaround I use NewPipe because it can download video & other stuff besides being much smaller.

Some users downloaded a more recent YouTube....apk from some mirror site, uninstalled the YouTube from Play Store & installed manually that apk as a workaround.

S5 Users with MindTheGApps like me & others with Open GApps reported the same issue.

***
[Samsung Galaxy S 5 Unified Development] bersem:
Im running LOS 18.1 on two other devices I9100 & jflte I9505. No issues with the same Open Gapps package.

Just checked the YT version on klte : 14.0.. on other devices i got YT update 16..

SOLVED: Copied the base apk file and three split files from jflte to KLTE and installed through Total Commander

Regards !
[Samsung Galaxy S 5 Unified Development] Tenaya43:
I'm not really sure where to ask this question, but here goes anyway.

I have LineageOS 18.1 KLTE installed on my SM-G900T and I'm fairly happy with it. That said, my carrier (AT&T through ConsumerCellular) has me worried that the looming network upgrades will not support my phone.

Does anyone know if this combination of hardware and OS will quote work unquote on my carrier (AT&T)?

I would especially be interested to hear what haggertk has to say on this.

​

Thanks,

Tenaya
[Samsung Galaxy S 5 Unified Development] dcarvil:
The phone will stop working once AT&T switches to VoLTE only. I don't know what the current date for that is. The stock Samsung ROM should support VoLTE, if you want to go back to the very old software.
[Samsung Galaxy S 5 Unified Development] Tenaya43:
So, even though the SM-G900T does suport VoLTE, LOS18.1 KLTE does NOT, right?

Will it ever?

OR, will LOS 19.x KLTE (Android 12) support VoLTE?

Tenaya
[Samsung Galaxy S 5 Unified Development] dcarvil:
Correct. Samsung never released source code for their proprietary implementation of VoLTE, so VoLTE is not supported by klte. I can't say what will happen with LOS 19, but since klte has never supported VoLTE, I would be very suprised if it was supported in the future.
[Samsung Galaxy S 5 Unified Development] Tenaya43:
Thanks for the explanation.

I guess I and everyone who has been hanging onto their S5s are all just SOL. That's too bad, I really like(d) the S5.

Now, I need to find a decent replacement, one that with a removable battery and that isn't as big as a tablet.

Tenaya
[Samsung Galaxy S 5 Unified Development] dcarvil:
If you find one with a removable battery, please let me know. I think the S5 was the last model with a removable battery.
[Samsung Galaxy S 5 Unified Development] Tenaya43:
The research I did before buying S5s (I actually have 4 of them) made me quite sure it was the last Samsung Galaxy S. There may be some other Samsung models that do, but it's more likely that I'll have to change manufacturers. Too bad, once I got the S5 to where I wanted it, I really like(d) it.
[Samsung Galaxy S 5 Unified Development] jmh2002:
I recently came across this issue, not because I fitted a Smart Cover, but because I fitted a Magnetic Charge Cable - and it tripped the sensor :oops:

So here's a couple of screenshots to add to the forum. I'm still on LOS 17.1, but I guess 18.1 is similar.

I just turned it Off in the settings there, and killed the FlipFlop app. Lineage didn't give me the option to disable it. If it wants to start at boot I'll turn that off with SD Maid (I checked, FlipFlop doesn't start at boot if it's turned Off and killed previously).
[Samsung Galaxy S 5 Unified Development] Hasan1122behj:
T

Thanks 🙂💮💮

It just soled with changing gsm to wcdma 🙂
[Samsung Galaxy S 5 Unified Development] Hasan1122behj:
Any solution for blinking and Flickering screen in low brightness 🤔
[Samsung Galaxy S 5 Unified Development] curiousrom:
You have a dying screen. Change screen or use higher brightness.

Try site:xdaforums.com s5 green flickering screen

Or if that device was repaired the screen ribbon may not be connected properly to the motherboard.

***
[Samsung Galaxy S 5 Unified Development] Nobby1960:
A known display defect. The greenish flickering occurs mainly in the cold. The smartphone can be heated with a hair dryer for the test.
[Samsung Galaxy S 5 Unified Development] tayfundokuyucu:
I use OLED Saver app.

OLED Saver - Apps on Google Play

This app solves the problem of flickering of AMOLED screen on low brightness

play.google.com
[Samsung Galaxy S 5 Unified Development] Tenaya43:
I've been researching the looming Network Upgrade issue as it affects my SM-G900Ts and as near as I can tell, there is simply no solution. By the middle of 2022, the lack of VoLTE support in LineageOS 18.1, coupled with the 3G network shutdown, will remove all voice call functionality completely - all Galaxy S5s will effectively become tiny little tablets.

I really (REALLY) want to be wrong, but I don't think I am.

This catastrophe will affect every flashed S5 owner who uses a provider who's on the AT&T, T-Mobile or Verizon physical networks. In other words, almost everyone here.

Here's what I don't understand: Why isn't everyone here freaking out?

Tenaya

PS: I have the utmost awe for haggertk and everyone at LoS. In NO way do they bear ANY blame for ANY of this. They can't, not won't, implement VoLTE and that's on Samsung.
[Samsung Galaxy S 5 Unified Development] Boatshow:
Check to see if your carrier or another one in your area still has 2G service.

I was VERY surprised that I could make phone calls over 2G. My carrier is only planning on retiring 3G soon so with any luck I will still be able to make phone calls.

No need, just fullscreen a white screen video, max brightness, pause it and enable caffeine mode for 30 minutes. This will temporarily fix the display.

https://www.youtube.com/results?search_query=white+screen
[Samsung Galaxy S 5 Unified Development] Tenaya43:
I hadn't thought of that, but it doesn't look like they do. As goes AT&T, so goes Consumer Cellular.

I hope you're right, but MY research says it's really, really unlikely. YMMV.

Tenaya
[Samsung Galaxy S 5 Unified Development] kurtn:
Large part of klte community is based in Germany. Many areas here are glad to have a little bit 2G. No LTE coverage in sight.
[Samsung Galaxy S 5 Unified Development] Tenaya43:
Good point. I envy them in this respect (not 2G, though)

That said, I would expect every S5 Modder in North America to be frantically looking for another phone. I am.

Tenaya
[Samsung Galaxy S 5 Unified Development] curiousrom:
Some 3G Networks Shutting Down & S5 LineageOS Not Supporting VoLTE

Not freaking out because the 3G network shutting down is not worldwide and for all network providers.

From this US FCC article Plan Ahead for Phase Out of 3G Cellular Networks and Service (bold by me):

I'm more worried about Mr. haggertk who continuously supported the Galaxy S5 klte family through LineageOS 14.1, 15.1, 16.0, 17.1 and 18.1 not porting it to 19 as he is an american.

Whatever he decides it's been an amazing run so far.

***

Yeah, I was surprised a while ago when I visited https://stats.lineageos.org/model/klte

***
[Samsung Galaxy S 5 Unified Development] EuK_V:
Hi, I've faced a problem - I get a boot loop trying to update (OTA) starting from lineage-18.1-20211205-nightly-klteduos-signed.zip. Hadn't had that before.

The phone tries to boot for a few minutes (lineage boot animation) and then boots into recovery.

TWRP is unable to flash an update, but able to restore a backup, which I made before. So I tried to update several times (12.05 and 12.12) with the same result.

I have klteduos S5

twrp-3.5.2_9-0-klteduos

What can go wrong?

Thanks in advance!
[Samsung Galaxy S 5 Unified Development] Tenaya43:
Earlier in 2021 I learned about this, but didn't fully appreciate all the nuances. I didn't know that LoS couldn't support Samsung (and other ) phones due to their proprietary implementation of IMS/VoLTE. I've always had the utmost contempt for the carriers (AT&T, I'm pointing at you) and manufacturer's efforts to keep us from updating hardware we own and they won't.

I realize not everyone faces this problem, BUT a large portion of the S5 community do, as do a bunch of other phones. Over the past few days I've been researching the LG G5, a phone that's not as "good" as the S5, but perhaps good enough for me. I have since found that LG also uses a proprietary implementation of IMS/VoLTE and any G5 that has LoS or other OS on it will stop making phone calls on the schedule you listed.

I cannot agree more. What he, LoS and everyone here have done is truly remarkable.

Tenaya
[Samsung Galaxy S 5 Unified Development] Tenaya43:
In the face of the North American apocalypse, does anyone know of a smartphone manufacturer who implements IMS/VoLTE in such a way that LoS can utilize it?

Tenaya
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 klteduos OTA Update Bootloop - TWRP Unable to Flash Update?

You don't give any setup description and did not provide any logs which makes it difficult to troubleshoot.

"TWRP is unable to flash an update" - Why not? How did you do it exactly?

Attach a TWRP recovery log to a post maybe?

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.

You can open /external_sd/recovery.log with Wordpad or Notepad++ for example & check for errors and/or rename it recovery_log_your_username.txt & attach it to a reply.

Zip it if the attachment fails which can happen on XDA these days.

***

"...I get a boot loop trying to update (OTA)" - Did you install a GApps package? If so, which one? Magisk version? Magisk modules if any?

If you use Magisk see the Script: Capture Bootloop Logcat chapter in this post & the script attachment.

***

Note: Don't install the TWRP app when offered in TWRP as it may causes bootloop because LineageOS is enforcing privapp whitelisting rules.

***
[Samsung Galaxy S 5 Unified Development] EuK_V:
Thanks for the reply.

I used built-in update tool to download an update and then, after the phone rebooted into recovery, manually installed /data/lineageos_udates/*.zip. I'd always done it this way previously and had no problems.

I'll attach recovery log later today.

Does the log contain any sensative/private information I should be aware of? I've never looked into recovery log before.

I have opengapps pico installed.

Magisk 23 - no additional modules.
[Samsung Galaxy S 5 Unified Development] supachris:
My Google Pixel 3 (blueline) works flawlessly with LOS 18.1 and uses VoLTE as well as Wifi Calling.
[Samsung Galaxy S 5 Unified Development] tortnoise:
Cellular Data Issue Samsung Galaxy S5 (kltekdi)

Hi, I am having issues with the cellular data. Installed the kltekdi rom, everything seems to be ok except for the cellular data, I get the "You don't have a network connection" error when I try to use the mobile network for downloading or login. The APN settings are correct, the mobile network (NTT DOCOMO) is recognized correctly but no connection, no LTE-4G-H- mark.

The sim card works fine on a galaxy s4 sc-04e DOCOMO with a lineage OS 17 customized for DOCOMO.

Any suggestion?
[Samsung Galaxy S 5 Unified Development] zimral.xda:
I switched to the Pixel3 last week with my business simcard. I am still using my last remaining S5 in good condition for some office and banking stuff at home but the ad to sell it in ebay has been placed now. It was a good time with the S5. :cry: bye bye
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: S5 klteduos OTA Update Bootloop - TWRP Unable to Flash Update?

Why? The Updater app works fine. I've used it at least 20 times on 18.1 to update automatically my S5.

I always search logs with the beginning of my email address like blabla@ & replace it with xxxx@ before posting logs.

Please collect logs so we can identify the cause of your issue then you could try flashing both LineageOS and Pico without wiping anything to update.

I've seen users with Open GApps survival script privapp whitelisting rules issues causing bootloops.

***
[Samsung Galaxy S 5 Unified Development] jenssa:
That proved to be a good advice. For some reason LOS lost contact with the internal storage, and I installed everything from scratch several times to no avail. However, flashing the backup of the efs partition rectified the problem.
[Samsung Galaxy S 5 Unified Development] EuK_V:
I made another attempt to update (result is the same). I attached the recovery log.

EDIT: I can't attach the log. Something doesn't work on xda..

EDIT2: See my following post.
[Samsung Galaxy S 5 Unified Development] curiousrom:
That's why I wrote this in the post above:

Busy now, will look at your recovery log later.

Did you notice the last 2 lines?

"I:Copied file /cache/recovery/log.gz to /cache/recovery/last_log.gz

pigz: /cache/recovery/log.gz OK, has trailing junk which was ignored"

Did capture a logcat of the bootloop?

***
[Samsung Galaxy S 5 Unified Development] EuK_V:
Not sure.. I grabbed the log file after the phone booted into recovery again. Is that a wrong log? How do I do this?
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: S5 klteduos OTA Update Bootloop - TWRP Unable to Flash Update?

There is no flashing errors in your recovery log:

552 I: operation_start: 'Flashing'

553 Installing zip file '/data/lineageos_updates/lineage-18.1-20211212-nightly-klteduos-signed.zip'

See the link in my post above about capturing a logcat of the bootloop with a script in Magisk.

***
[Samsung Galaxy S 5 Unified Development] EuK_V:
I copied the logcat_on_boot script to the /data/adb/post-fs-data.d/ and tried to reboot. No files similar to "20210502061513_boot_logcat.log" were created in the /cache/ folder.

It didn't seem to work. What can I do to make it work?
[Samsung Galaxy S 5 Unified Development] curiousrom:
Magisk Script: Capture Bootloop Logcat

Well it works for me as you can see in the screenshot of the /cache/ folder viewed with the awesome root enabled MiXplorer file manager.

Every time I boot the S5, a 30 seconds logcat is automatically captured & replaces the older one of two logcats kept so if I ever have a bootloop issue I just retrieve it and can troubleshoot.

I rebooted to create a new one before I took the screenshot.

Check the permissions of the logcat_on_boot script file maybe? Mine is set at: rwx r-x r-x 755 as seen in the screenshot.

***
[Samsung Galaxy S 5 Unified Development] EuK_V:
Yeap, needed to make it executable. Now log files are created during regular boot, but are not during bootloop: I tried to update again, got bootloop, when the phone booted into recovery, no logs were created.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Continuous logcat of bootloop

You could try capturing a continuous logcat.

After restoring your working backup make sure you can capture a logcat that will be saved in the folder where you are running adb from:

adb devices

adb logcat -d > logcat_before_update.txt

If it works do not close the command window & do not disconnect the device.

Reboot to TWRP & flash LineageOS update package.

Before booting to system and while still in TWRP type this but DO NOT hit enter yet. Note that there is no "-d" this time.

adb logcat > logcat_after_update.txt

In TWRP select boot to System and as soon as the screen goes black hit Enter.

adb logcat will respond - waiting for device -.

Either logcat_after_update.txt will be created when the device boots or when failed to boot & thrown to TWRP or if you hit ctrl+c after waiting for 3-4 minutes or disconnecting the device.

***

Did you try flashing both LineageOS update + the Open GApps package as I suggested in a previous reply?

***
[Samsung Galaxy S 5 Unified Development] BigPulco:
I have following case:

Yesterday I received a call, it was a commercial call (ad call) so after hang-on, I blocked the number. Today I received a call from the same number again! (Normally I was expecting that that number should not be able to call my number again....)

Any idea ...
[Samsung Galaxy S 5 Unified Development] x2k13:
Did you already test to block another number, like of a spare/friends mobile, and try to call yourself with that?
[Samsung Galaxy S 5 Unified Development] EuK_V:
Here's an adb logcat during bootloop.

Interesting thing: when the phone was connected to the pc via usb bootloop didn't end up booting into recovery. The phone was trying to boot forever, so I disconnected it after 3-4 minutes. Despite this, the file is quite big.

Flashing gapps did the job! The phone booted after update!

Though I lost root privileges after that. So I also needed to re-flash Magisk afterwards.

I made a test: my working backup was the lineage build from 11.28, I updated to the 12.05 build flashing lineage update + gapps + magisk, then being on the 12.05 build I updated to the 12.12 build flashing only lineage update (without gapps and magisk) - no bootloop, phone booted, root is OK.

This gives me hope for future updates.

I attached the log in case you're interested in it. There's too much information for me there.

Thanks for the pro assistance!
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: S5 klteduos LineageOS 18.1 + Open GApps Pico Update Bootloop - Fix!

Thanks for the logcat captured during the bootloop & the feedback. :cool: 👍

It confirmed my suspicions as I wrote above: I've seen users with Open GApps survival script privapp whitelisting rules issues causing bootloops:

--------- beginning of crash

12-15 01:56:55.312 715 715 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main

12-15 01:56:55.313 715 715 E AndroidRuntime: java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.google.android.gms...

Glad it worked & thanks for that test. :cool: 👍

I'm in contact with an Open GApps dev and if you can provide an other log it could be useful. That log includes info about the build date of the Pico build that you had before flashing a new one after LineageOS which granted the proper privapp-permissions & that's why "I updated to the 12.12 build flashing only lineage update" worked.

If you sideloaded Open GApps it automatically creates a log named open_gapps_log.txt in the internal sdcard folder.

If you copied to the device the GApps...zip package & installed it from there manually using the recovery then the "open_gapps_log.txt" is created in the same location as the GApps...zip package.

***

For your next update after backing up with TWRP try the built-in Updater to automatically install the update instead of dong it manually.

Tip: To make the TWRP backup smaller I use SD Maid > AppCleaner to clear the cache of all apps which makes the Data partition backup smaller (screenshot). Make sure to delete all downloaded updates in Updater by long pressing them or if rooted move them from /data/lineageos_updates/ to external or internal SD Card.

In case of failing to boot you can restore only the System, Data & Boot (boot.img is actually the kernel) partions from the full backup.

BTW you can create a direct link to Updater & much more with the LineageOS Settings widget.

***
[Samsung Galaxy S 5 Unified Development] BigPulco:
Yes, you are right. I experimented with blocking a friend's phone number. I saw that my phone didn't ring and the caller got a busy tone.

Result: "Blocking" works.

The case I reported before, should be something special... Probably the displayed number is different than the number actually calling...
[Samsung Galaxy S 5 Unified Development] EuK_V:
Here's the opengapps log.

But strangely, the section "Current GApps Version" says: "No GApps Installed". I definitely had opengapps installed before flashing the new version.

So don't know if it will be useful..
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: Cellular Data Issue Samsung Galaxy S5 (kltekdi)

What does it say in > Settings > About phone > Android version > Baseband version?

What is the exact device model number?

A recent modem & vendor's firmware may help: S5 Odin Flashable Modem & Bootloader.

***
[Samsung Galaxy S 5 Unified Development] EuK_V:
Hey!

I have a question about the Messaging app.

I would appreciate it if anyone could help with this.

In Lineage 16, 17.1, I used a great in-app feature - to mark a message as read right in the notification, you didn't really need to open the app to do this. It was very convenient.

Can't find it on 18.1. Has this option been removed in LOS 18.1 or is it possible to enable it?

Thanks! See my screenshots.
[Samsung Galaxy S 5 Unified Development] tortnoise:
The model number is SC-04F, baseband version SC04FOMU1XQH1
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: Cellular Data Issue Samsung Galaxy S5 (kltekdi)

That's from a recent stock Samsung 6.0.1 for your model so it should be OK if the other manufacturer's firmware were also updated.

Is this a network branded S5 SC-04F? Maybe it's SIM locked?

Check > Settings > Network & internet > Mobile network > Advanced > Access Point Names > APN > and make 100% sure that they are identical to your network provider's current recommended settings then turn off the device, wait a few seconds, turn back on, then send an SMS before receiving one.

When you say "the mobile network (NTT DOCOMO) is recognized correctly but no connection" does that mean that you cannot make & receive calls nor send and receive SMS?

***

The best way to confirm or rule out a hardware issue is to flash the most recent stock Samsung manufacturer's OS for your S5.

This will also update the vendor's firmware, modem, bootloader etc.

Their paywall policies varies apparently randomly depending on the device & age of the OS but I used both sammobile.com & updato.com to download stock Samsung OS. Some users recommend samfw.com.

They all have flashing instructions using Odin3 in their respective download pages.

It does not matter for which country as long as it's made for your exact model number.

Usually the more recent, the better.

Test thoroughly while on stock Samsung OS & write down or screenshot the working APN settings.

Then install the most recent TWRP version, backup the EFS partition then flash LineageOS.

***