yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] Tenaya43:
Perhaps so, but I would rather use regular cellular phone service.

As I said, that works now, but I'm trying to discover why it works. Besides just normal curiosity, I'm also trying to determine if my "work around" will continue working or if it, too, will be shut down.

Any thoughts on why it works and what, exactly, AT&T did and did not shut down?

Thanks,

Tenaya
[Samsung Galaxy S 5 Unified Development] Laugh2:
Possible Solution for S5 and VoLTE?

​

Hi Tenaya43, I am also facing this "catastrophe" - our family has 3 S5's all on LOS18.1 and facing 3G shutdown just as 2G was shutdown in 2020/2021.

Official LineageOS probably won't enable support, however, SOME HOPE might be found if the following solution works for the Samsung Galaxy S5:

https://xdaforums.com/t/guide-how-t...builds-from-4th-jan-to-current-build.3536031/

If you (or anyone else?) would like to try this with an S5 then maybe VoLTE and Wifi Calling might become available? (It's never worked for S5 where I live so this solution is even less likely to work for me.)
[Samsung Galaxy S 5 Unified Development] kurtn:
Sorry. That is really leeco le 2 specific. Only solution (besides messenger apps) i see is going back to stock rom.
[Samsung Galaxy S 5 Unified Development] Tenaya43:
Yeah . . . (deep sigh).

Anyway, I've been doing some additional DDGing and I think I have a slightly better understanding what's making my S5s work when they really shouldn't.

Some other discussions seem to indicate that not ALL of the 3G protocols on AT&T have been shut down. In some places in the U.S., including where I live, at least one 3G protocol is up, likely HPSA, HPSA+ and/or WCDMA. On every such thread, someone came along and said something like "not for long".

Eventually, every S5/LoS user who lives where 3G is being shuttered will be forced to revert or change phones.

Subject to radical change from one zeptosecond to the next, MY current plan is to continue enjoying my S5 until the unpredictable moment when it finally stops making calls and settings don't fix that. I will then temporarily revert it to the last/latest stock rom. I've gotten way too used to non-bloated phones to daily drive a stock ROM, so I will migrate to a (non-Samsung) phone on which VoLTE is supported by LineageOS (18.1 for now). The most promising candidate seems to be the Motorola Moto G7 Play (for me, at least). I will lose several S5 features I really want, especially the removable battery, but life isn't fair (and the brochure never said it would be).

Tenaya
[Samsung Galaxy S 5 Unified Development] Hasan1122behj:
Excuse me does the internal sound recording in " screen recording " suppose to work ?

Cause when i put " device audio " in setting , all i hear is total silence...

Rom version : 18.1-20220123-NIGHTLY-klteduos
[Samsung Galaxy S 5 Unified Development] sirrooke:
Well, this is interesting. Usually my phone shows "LTE" on the status bar when making calls:

Starting today (first day after AT&T said they would switch off 3G), the "LTE" changes to "4G" when I make a call (and the call goes through):

Anyone else??
[Samsung Galaxy S 5 Unified Development] harmoglass:
How stable are the current builds? I sit at 17, I tried the early 18, I was scared off by stability. the choice is between RR 10 android and Los 18 (11)
[Samsung Galaxy S 5 Unified Development] kurtn:
LineageOS 18.1 is stable.
[Samsung Galaxy S 5 Unified Development] Laugh2:
The bit I found encouraging was at the beginning where CYB3R0ID694 seems to identify the phone's Modem and Baseband as being the critical items, and then suggests that if LineageOS is already installed VoLTE might be made to work by flashing suitable Modem firmware using TWRP with a reboot (and possibly then needing to follow a procedure as described by CYB3R0ID694).

I was hoping that if I found Modem firmware for exactly my model of Galaxy S5 from a Provider who offers VoLTE for the S5 then I could flash this using TWRP and have a chance at success. (I think I know of such as Provider.)

Might this work? My Provider/Carrier has said they don't mind other Carriers' phones. Also, when LOS 18.1 is freshly installed (or reset) then my S5 offers VoLTE (although it won't actually work).
[Samsung Galaxy S 5 Unified Development] Laugh2:
Agreed. We've been using LOS 18.1 on several Galaxy S5's for many months now with great success. It's an excellent ROM.
[Samsung Galaxy S 5 Unified Development] Laugh2:
I think many (most?) more recent Samsung models support VoLTE on many carriers - I think often too using recent LineageOS versions. The Provider's homepage can give some idea where they state their VoLTE prerequisites - mine for example doesn't require users to have a phone bought from them just specific models and a recent Android version.

For example, after installing LOS 18.1 onto my Galaxy S5 it offered VoLTE (but doesn't actually work), which probably means that the Provider doesn't mind but the phone/firmware isn't suitable.
[Samsung Galaxy S 5 Unified Development] Tenaya43:
I don't know if providers/carriers mind or not, probably only to the extent that they would like to sell new phones and/or multi-year contracts.

I haven't been able to confirm it, but I believe that when AT&T turned off GSM on February 22nd, they left other 3G protocols up, specifically WCDMA. That allowed LoS 18.01 on our S5s to make calls WITHOUT VoLTE by simply changing the Preferred Network Type setting. Last Tuesday both of our phones stopped making phone calls regardless of any Preferred Network Type setting (LTE data still works). I believe that over the night of February 28th, AT&T pulled down the rest of their 3G protocols, never to return.

Our S5s offer LTE, too. The Preferred Network Type setting in LoS 18.1 offers a bunch of protocols, but that doesn't mean they're actually functional. I have read that LoS 18.1 supports VoLTE on a variety of phones, but it is my understanding that regardless of carrier, VoLTE cannot be implemented is not possible with LoS on Samsung phones, including the S5, because Samsung declines to provide the API for their proprietary implementation of VoLTE.

As near as I can tell, there is NO way around this. I have given up trying and am proceeding full speed ahead with the process of replacing our S5s (2 in use, plus spares) with the Motorola Moto G7 Play.

NOTE: Everything I'm saying about this issue is the result of my incomplete and imprecise Internet research. I am certain that haggertk could shed a massively better informed light on this issue.

Tenaya
[Samsung Galaxy S 5 Unified Development] Laugh2:
In most regions it's probably sensible to replace S5's due to minimal VoLTE support, especially if 3G is now gone. There are still a few outliers e.g. Vodafone in Australia:

https://www.vodafone.com.au/support/network/volte?accordion-id=samsung

so maybe their modem would work in other S5-G900I on other Carriers offering VoLTE? Maybe even with LOS? (Unfortunately I don't live in Australia.) Comments about Carriers blocking 3rd party phones by some Carriers can be found for example in:

https://forums.whirlpool.net.au/archive/2700390 for some individual Carriers.

Many Carriers are offering VoLTE for later model Samsung phones e.g.

AT&T https://www.att.com/idpassets/image...Capabilities-Unlocked-Devices-ATT-Network.pdf

Vodafone Australia https://www.vodafone.com.au/support/network/volte?accordion-id=samsung

2Degrees NZ https://www.2degrees.nz/help/mobile...phones-compatible-with-volte-and-wifi-calling

Maybe their Modem firmware can be used with LOS? Can anyone comment on this?

I still have a year or two before I lose 3G. If I can't find a solution before then I'll be replacing them too, probably with another Samsung since they often support LOS. Hopefully I can find compatible Modem firmware and hopefully it'll enable VoLTE on my S5's using LOS before then, as I described above in a recent posting.
[Samsung Galaxy S 5 Unified Development] zimral.xda:
Sadly, the glory days of the Galaxy S5 have been passed by :-( I sold mine (total of 4) before last christmas. Did that with my Pixel2 either. Now i have 2 Pixel5, one of them running CalyxOS, one Pixel4a with Calyx and a Pixel3 running LOS18.1. Maybe i will sell the Pixel3 either or stay with it for test/spare device.
[Samsung Galaxy S 5 Unified Development] x2k13:
Galaxy S5 will _never_ have VoLTE, on any ROM. End of story.
[Samsung Galaxy S 5 Unified Development] Tenaya43:
Yes, my comments are from the USA perspective - I live in Texas - if you're in a different country/market, with different providers/carriers, you may well have a better experience in this regard. Color me green with envy.

I wish that were possible, but my reasearch to date seems to say it's not, due to Samsung's proprietary VolTE API.

My best understanding is that firmware/software components like VoLTE rarely work on other models.

Also, if there were a solution like this, haggertk would have implemented it already (he lives in the USA).

I wish you well.

Tenaya
[Samsung Galaxy S 5 Unified Development] Tenaya43:
As much as I hate this circumstance, I have to agree.

Tenaya
[Samsung Galaxy S 5 Unified Development] Lederhose:
I installed a bunch of apps and now I get an error message from Play Store that I need to free up space to be able to install some more, despite 9 GB of free space being reported in device settings.

As far as I know, one has to resize some partitions? What's the best solution?

I have a klte that had German Vodafone branding, I used Heimdall to pull it's PIT and flashed DBT stock ROM files to those partitions except for system and EFS. Then I flashed TWRP, did format data + wipes and installed this ROM with a custom OpenGapps configuration (basically pico with TTS, Speech, Camera, Chrome, Maps and Youtube).
[Samsung Galaxy S 5 Unified Development] kurtn:
Your bug is probably related to usage of an sd card as adopted storage.
[Samsung Galaxy S 5 Unified Development] sirrooke:
This happens to me every few days. (I know when it's occuring because I get an error trying to open my "to do list" text file on the SD Card). I just reboot the phone & all is well for another few days.
[Samsung Galaxy S 5 Unified Development] Lederhose:
The SD card was never configured as adopted storage.

Indeed, meanwhile the problem disappeared. "Have you tried turning it off and on again?" probably really did the trick. Thank you! I'm so glad I don't have to tinker with the partitions ...

ROM works very well. The only other minor problem I found so far, when device is encrypted, on the first password prompt while booting, if I do not enter the password but try to use the menu to 'Power off' the phone, it shows a "Shutting down..." screen but won't actually shut off; the power menu can still be reopened but also won't do anything else, and it won't go back to the password prompt. Even holding the hardware button to shut off doesn't work - I have to remove the battery to restart the phone.
[Samsung Galaxy S 5 Unified Development] g000n:
Stable with frequent updates
[Samsung Galaxy S 5 Unified Development] yoshkapundrick:
Sorry I'm late to the conversation. AT&T did the same to me as I have a 900T. But I could see that the 900A was approved so I knew it was baloney. They shut my phone off twice before the end date and I had them reinstate it. They sent us a $5 type phone from Samsung for free saying mine would not work. They tried hard but as expected they were wrong. My phone works perfectly fine.
[Samsung Galaxy S 5 Unified Development] stephendt0:
Hey guys, maybe a silly question here. It looks like my touchscreen on my cheap replacement LCD died (doesn't work in TWRP anymore). Now my device won't boot into LineageOS anymore. Lastest 6th March build. I went back to stock and that booted (no touch of course), but reflashed Lineage and still no change. Is anyone able to comment on whether this is normal...? I know it seems like an odd question but I expected LineageOS to at least boot... just sits at the boot screen endlessly :(
[Samsung Galaxy S 5 Unified Development] gw1024gb:
Mod edit - translated by https://translate.google.com/?hl=en

Except for recovery, sc-04f cannot be charged when powered on or off

*******************

sc-04f除recovery外，开机或关机都不能充电
[Samsung Galaxy S 5 Unified Development] Oswald Boelcke:
@guogaowen

As courtesy I've translated your above post - and I'm very sorry to recognise that it's not the first time that a moderator had to translate your posts. This is just a friendly reminder that English is the mandatory language! With reference to rule no. 4 of the XDA Forum Rules, please post in English or add at least an English translation to your Chinese posts.

Spoiler content hidden.

Please read my message as a friendly warning now to refrain from posting only in Chinese!

Thanks for your cooperation!

Regards

Oswald Boelcke

Senior Moderator
[Samsung Galaxy S 5 Unified Development] gw1024gb:
thanks
[Samsung Galaxy S 5 Unified Development] RainbowMixed:
@haggertk Could you please make lineageos sm-g906L version?

I really need it! Thanks
[Samsung Galaxy S 5 Unified Development] kurtn:
That's a completely different device. Codename lentislte. Processsor Qualcomm.
[Samsung Galaxy S 5 Unified Development] yoshkapundrick:
I was wrong again. Phone can no longer make or receive calls due to the aforementioned lack of VOLTE as of March 11, 2022.
[Samsung Galaxy S 5 Unified Development] MYEUHD:
Which one is preferred for the /data partition: ext4 or f2fs ?
[Samsung Galaxy S 5 Unified Development] kurtn:
Ext4
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 LineageOS 18.1 Update 2022-03-20 - Android Security Bump

Using the built-in Updater I OTA updated S5 G900M LineageOS 18.1 klte build 2022-03-13 + MindTheGapps + Magisk 23.0 + TWRP 3.6.0_9-0 to build 2022-03-20: everything went smoothly as usual & GApps + Magisk survived the update.

There are several changes listed in https://download.lineageos.org/klte/changes/ but most importantly it includes the monthly Android security bump: Bump Security String to 2022-03-05.

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

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 - March 2022 for details about the security fixes.

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

***
[Samsung Galaxy S 5 Unified Development] sirrooke:
My 900T is still working fine on the AT&T network!
[Samsung Galaxy S 5 Unified Development] yoshkapundrick:
How did you enable VOLTE?
[Samsung Galaxy S 5 Unified Development] sirrooke:
I haven't 'enabled' anything that I know of. The phone just continues to work. I mentioned this in a post on March 2 (#927)
[Samsung Galaxy S 5 Unified Development] yoshkapundrick:
Yeah mine worked ok for 3 weeks than it went south. Perhaps the full conversion hasn't/won't take place in your area.

Have you looked at the VOLTE toggle?
[Samsung Galaxy S 5 Unified Development] sirrooke:
There's a VOLTE togggle?? Where is that?

As far as the full conversion: I'm in Chicago but I travel thru Indiana, lower Michigan, Iowa, WIsconsin... it has worked in all those places.
[Samsung Galaxy S 5 Unified Development] yoshkapundrick:
Dial

*#*#4636#*#*​

then look under phone information to see if you have VOLTE toggle.

Of course mine does not.
[Samsung Galaxy S 5 Unified Development] sirrooke:
Well, when I try dialing that string, everything is fine until I press the final asterisk -- when I do, the whole string vanishes as if erased.
[Samsung Galaxy S 5 Unified Development] yoshkapundrick:
It is supposed to do that. And if it displays nothing you may not have the toggle. You can also search in the Settings for VOLTE. It will have a VOLTE setting which in my case leads to cellular settings without a toggle, since on my phone it cannot be done.
[Samsung Galaxy S 5 Unified Development] curiousrom:
No VoLTE on LineageOS for the S5 klte* Family

LineageOS does no support VoLTE on any Samsung devices @ the present because the devs could not reverse engineer Samsung's proprietary VoLTE implementation so far.

That could be a deal breaker if your network provider drops both 2G & 3G as only VoLTE will work for voice calls after that.

If it's your case don't let the S5 die in a drawer!

Sell it on eBay because in many regions around the world 3G & 2G are still supported like here in Central America.

Or return to the most recent stock Samsung OS for your model (Android 6.0.1) which supports VoLTE.

***
[Samsung Galaxy S 5 Unified Development] yoshkapundrick:
Understood. But it is curious that his 900T is still working in multiple locations with AT&T after the deadline.
[Samsung Galaxy S 5 Unified Development] minoo14534:
Hello

Since the last lineage update for Galaxy S5 Klte and Galaxy S4 I have the following problem.

The root function of the device is deactivated despite the installation of Twrp and Magisk, both current versions.

Lineage recovery is also not enabled and both devices are only rooted with Magisk.

I tried to root the whole thing again with the current Magisk, unfortunately without any result

Does anyone have similar experience.

Thanks
[Samsung Galaxy S 5 Unified Development] kurtn:
What's your root method? Do you patch boot.img or do you flash magisk.apk ? There are reports, latest magisk has problems. Try an older one.
[Samsung Galaxy S 5 Unified Development] minoo14534:
Thanks for the answer I installed Magisk as a zip directly into twrp.

I also tried with older version of Magisk unfortunately without result
[Samsung Galaxy S 5 Unified Development] BigPulco:
To be precise, I am using twrp version 3.6.0_9-0 on my KLTE device and V23.0 as Magisk and I have no root problems.

PS: I just saw new twrp version exist as 3.6.1_9-0 ...
[Samsung Galaxy S 5 Unified Development] minoo14534:
After I installed the TWRP twrp-3.6.1_9-0-klte today, the problem with root is OK again.

The problem is when I install new Lineageos update the same thing happens, then the root function is disabled. I've had the same problem with Galaxy S4 for a long time.
[Samsung Galaxy S 5 Unified Development] hk133hk:
Hi, I am facing a strange problem on my SC-04F after the battery have been pull out when the phone is booting the kernal.

At first, it couldn't charge no matter I turn on or turn off the phone. So I did everything that I know how to do, like factory reset and wipe system partition in recovery, then reinstall the system. But it didn't fix the problem, so I tried to flash the modem and bootloader from this post #740 using Odin: https://xdaforums.com/t/rom-official-lineageos-16-x-all-variants.3850840/page-37#post-78485099

I have use the modem and bootloader from that post to fix the bootloop problem of my phone, and I have tried to charge the phone and it works normally before the battery have been pull out when the phone is booting the kernal, so I am quite sure that's not the problem of this file.

After flashing this modem and bootloader, although the phone still couldn't shows the charge status, and no update for battery percentage information when I turn on the phone and plug in the charger, but it actually is charging (checked by USB voltage and current meter), and it would update the battery percentage information after restarting the phone, when I using the phone without charging, it could shows the correct and up-to-date battery percentage information.

But here is another problem occurs, at this time if I get into recovery and wipe the cache, the phone couldn't charge again, and the only solution that I found out now is to flash the modem and bootloader again, without wiping any other stuff.

Please let me know if you have any idea or suggestions about this situation, and if any logs is needed, please let me know how could I get it, thank you, and also thank you for making this great ROM.
[Samsung Galaxy S 5 Unified Development] XantheFIN:
Polite request for G9009D / k3gduosctc. Not much love got this one.:whistle:
[Samsung Galaxy S 5 Unified Development] jian1:
Will it install the Emergency Alert App and actually allows the S5 to receive Presidential Alerts?

The default S5 (Bell Canada) has 6.0.1 and currently doesn't receive any alerts in Canada, and since Canada stupid CRTC broadcast every message in presidential level, thus I don't want to get the LineageOS should it somehow enables the Emergency Alert message system.

Someone can confirm with me would be greatly appreciated.
[Samsung Galaxy S 5 Unified Development] MYEUHD:
Bug report: The default lineageOS SMS app sends notifications late.

as much as 17 minutes late.

I tried a 3rd party app and got the notifications (almost) instantly, but the problem is, the notification LED didn't light up (whereas it does with the default app)
[Samsung Galaxy S 5 Unified Development] hk133hk:
It seems like the Emergency Alert system is included in Android 11 and lineageOS didn't change anything about this. I am in Hong Kong and I could disable it on all of my mobile phones, but I wonder could it be disabled in Canada.
[Samsung Galaxy S 5 Unified Development] jian1:
Presidential alert requires rooting permission, not your normal alerts.
[Samsung Galaxy S 5 Unified Development] hk133hk:
Then I would suggest you to send a complaint to that CRTC broadcast, this is not the problem of Android or LineageOS.
[Samsung Galaxy S 5 Unified Development] jenssa:
April 2nd: I now replaced the Trebuchet launcher with the Nova launcher. I don't experience that the launcher stops and the constant waiting for apps. At least so far, it seems much better
[Samsung Galaxy S 5 Unified Development] minoo14534:
I found a solution to the problem with Magisk. In case anyone has similar problems updating Lineageos. Should just install the Magisk v20.zip in TWRP and then update it in Magisk Manager. It helped me

Here is the report and link.

https://xdaforums.com/t/magisk-general-support-discussion.3432382/page-2568

- on klte, TWRP cannot be updated using IMG format (on PocoF1 no problems).

- you are allowed to flash a single partition in Odin.

Coming to magisk, occasionally when I do OTA from LOS I lose magisk. In theory this should not happen, but it does. So I need to reboot from TWRP, reinstall magisk and reboot. This always worked in the past, but now with 24.3 this is not working anymore as 24.3 fails in TWRP. Instead, 24.0 works perfectly. So now, in case it would happen again, if LOS update removes magisk, I need to flash 24.0 from TWRP and then update it to latest directly from Magisk Manager. For me it is a regression. I hope it will be fixed.
[Samsung Galaxy S 5 Unified Development] curiousrom:
TWRP & S5 LineageOS 18.1 Update 2022-04-03

FYI I just updated TWRP 3.6.0_9-0 using twrp-3.6.1_9-0-klte.img as described in How to Update TWRP Using TWRP Itself.

You do need to use the ...img.tar version if you are using Odin3 as mentioned in that post.

After that I used TWRP 3.6.1_9-0 to create a full backup then OTA updated Galaxy S5 G900M LineageOS 18.1 klte build 2022-03-20 to 2022-04-03.

MindTheGapps and Magisk 23.0 survived the update.

TWRP changelog: https://twrp.me/site/update/2022/03/10/twrp-3.6.1-released.html

Magisk 23.0 works fine for me on the S5 like BigPulco wrote so I don't see a reason to update it so far.

***
[Samsung Galaxy S 5 Unified Development] BigPulco:
When both launcher co exist, even if Nova selected as default by "Home App" when "Recents Apps" button pressed Trebuchet is launched. Did you find any solution for this case?
[Samsung Galaxy S 5 Unified Development] Massedil:
https://review.lineageos.org/c/LineageOS/android_packages_apps_LineageParts/+/309023/ :

So I think it is normal you can't see the new option ?
[Samsung Galaxy S 5 Unified Development] graciano262:
la rom no es compatible con magisk
[Samsung Galaxy S 5 Unified Development] yoshkapundrick:
I had the same problem as I updated from 17.1. First I updated TWRP (mine was outdated) then I uninstalled Magisk using the App and then reinstalled Magisk using the App and finally it worked.