yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] gretchen.m:
Thanks for this. Unfortunately, I fear, this won't solve the problem: SMS messages are actually not received - it's not only about the notification (a message sent to me 2 days just arrived this morning with this morning's time step in the messaging app).

I've been trying the following apps for SMS:

* Stock messaging app (only for a very short while)

* Signal (currently used for SMS)

* Silence (issue occurs here as well)
[Samsung Galaxy S 5 Unified Development] lentm:
Does anybody get the Textnow free plan activated on LineageOS or any other AOSP roms?

On stock or stock based MM roms, it activates successfully and Textnow with LTE signal works great,

then I install LineageOS, never get the data working to have Textnow free plan working without WiFi.

I was able to get the data working when I had the Sprint postpaid plan on LineageOS or any other AOSP roms,

but Textnow free plan probably works in different way.

I have kltedv, the sprint variant.
[Samsung Galaxy S 5 Unified Development] bmwdroid:
Don't know if it helps but the S5 we use has crDroid 6.10=Q on it and SMS (provider Telefonica) are received blaming fast.
[Samsung Galaxy S 5 Unified Development] curiousrom:
LineageOS 16.0 Update 2020-09-20 - Security Bump

FYI the monthly Android security patch Bump Security String to 2020-09-05 is included in LineageOS 16.0 for the S5 klte + variants build 2020-09-20 or newer as well as other changes related to Bluetooth (bt), telephony, etc. as you can see in your model's changelog. For example: https://download.lineageos.org/klte/changes/

Because that Changes page is updated all the time I attached a screenshot for posterity.

View attachment 5101195

See Android Security Bulletin—September 2020 for details about the security fixes.

I updated to LineageOS 2020-09-20 via the built-in LineageOS OTA Updater a Galaxy S5 G900M LineageOS 16.0 klte running build 2020-08-16 + Open GApps Pico + LineageOS AddonSU, no custom kernel or system mods of any kind.

This may be related to the fact that my S5's memory is quite full as it showed > Settings > Storage: 94% full which may causes all kinds of problems but for the first time in over 20 OTA updates the download seemed to freeze @ 12% because for over 3 minutes the download speed & % done was not changing at all.

As you can see in the screenshots in the Updater notification hitting Pause, waiting 4-5 seconds & then Resume unfroze it. I had to do that again later during the download.

View attachment 5101197

It's also possible that there was some problems with the connection to the LineageOS server & Pause/Resume refreshed that connection to an other mirror or connections.

After the update download was completed & automatically checked for integrity by the Updater script, from the moment I clicked OK to install to full boot to system after the automated flashing in TWRP it took 8 minutes instead of the usual +- 5 minutes. That may vary depending on your setup.

After the automatic reboot as seen in the screenshot > Settings > About phone > press on Android version > Android security patch level: September 5, 2020.

View attachment 5101199

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

Thank you to the Lineage Team & Mr. haggertk (who made that bump security patch) for keeping our old S5 up to date. :good::cool:

***

Now I need to stop procrastinating & spend some time cleaning up my setup to free some space especially that pesky /data/media/0/WhatsApp/ folder taking more than 3.5 GB of space in the internal sdcard. :eek:

***
[Samsung Galaxy S 5 Unified Development] snsnse:
There is another issue I forgot about and which I already reported in another klte 17.1 thread.

Email app: adding attachments (at least one image/photo/picture first) to the same email twice causes the app to crash.

How to replicate:

Edit new email -> Attach file -> select image/photo/picture -> Attach (another) file -> select (any) file -> crash

I have tested this with attaching two images/photos/pictures as well as a plain text file after the image/photo/picture; in both cases the app crashes. There is no crash if I attach the plain text file first and then the image/photo/picture.

Logcat attached.
[Samsung Galaxy S 5 Unified Development] 761gg1i3219:
Hi, I'm running LOS 16 on klte, I read that work for 17.1 has started and can't wait for it to be completed!

Anyway I don't know if this is the right place to ask but with 16 I always had these problems:

- the microphone level is very low, whenever I record something the volume is super low, and I received many complaints from people listening to my voice messages.

- whenever I charge my phone while switched off, no matter how long I leave it charging, when I turn it on again the battery is at 91/92%, if I then leave it charging again (while switched on) it reaches 100%. I know for sure the problem is not the battery because I changed it and nothing changed.

Has anyone experienced the same problems? Is there anything I can do?

Also I am rooted with Magisk.

Thanks in advance
[Samsung Galaxy S 5 Unified Development] curiousrom:
Low Mic Recording Fix & Reboot Battery @ 92%

Those are known issues.

See this post with flashable zips S5 Main Mic Recording Boost & Survival Script - WhatsApp

See this post about LineageOS 16.0 for S5 limiting the maximum battery charge voltage: S5 Battery Charging - Fake 100%

***
[Samsung Galaxy S 5 Unified Development] Z.Ilya:
How do I enable USB diag mode on LOS 16?

setprop persist.usb.eng 1

nor

setprop sys.usb.config diag,adb

doesn't do a thing (using ADB and terminal emulator)

I can only manage to do so via stock 6.0.1 Android ROM by entering a number 319712358 in dialpad, then password 996412 for SM-G906S and then I can choose USB settings -> DM+MODEM+ADB

Hopefully, there is a solution for LOS 16.

Just need this to enable missing LTE bands in my SM-G906S for it handles the cellular signal (LTE) much worse than SM-G900F because of soft-locked LTE bands.
[Samsung Galaxy S 5 Unified Development] yoshkapundrick:
Do these BT changes address the problem with BT dropping of signal?

I've had to stay on 14.1 due to this problem

thank you
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: LTE bands S5 SM-G906S

Your Galaxy S5 LTE-A (lentislte) SM-G906S is not the topic of this thread & has a different LineageOS maintainer.

And it's a pretty specific question.

Try this Google site search & change keywords to taste: site:xdaforums.com/ G906S usb diag mode

Good luck!

***
[Samsung Galaxy S 5 Unified Development] rootkitty:
Battery Charging Issue

I have an SM-G900W8 that was charging fine when running lineage-16.0-20191218-nightly-klte. When I updated to lineage-16.0-20200614-nightly-klte I started having charging problems. I can't keep the the phone on the charger and have it stay fully charged. When the device goes to sleep (i.e. screen shuts off) it stops charging and doesn't restart. (I have a charger with a built in ampmeter, so I can tell when it is an is not charging. I recently updated to lineage-16.0-20200920-nightly-klte, but it didn't fix the issue. In all cases I flashed with TWRP wiping both Dalvik/ART cache.

I tried running the battery completely flat, and it seemed to drop very quickly, but it ran for a very long time at very low levels like 4,3,2% which makes me think it's a calibration issue rather than a battery problem. Due to COVID, I haven't been carrying the phone very much... it has spent most of it's time sitting on my desk on charger.

Any suggestions as to how I can get things working again would be much appreciated.
[Samsung Galaxy S 5 Unified Development] Kiastinger:
Tried kernel. Change or do the battery calibration hopefully it should be fine. (My battery 5 years old)
[Samsung Galaxy S 5 Unified Development] rootkitty:
Thanks... This is the procedure I found for recalibrating - is this OK?

Discharge your phone fully until it turns itself off.

Turn it on again and let it turn itself off.

Plug your phone into a charger and, without turning it on, let it charge until the on-screen or LED indicator says 100 percent.

Unplug your charger.

Turn your phone on. It's likely that the battery indicator won't say 100 percent, so plug the charger back in (leave your phone on) and continue charging until it says 100 percent on-screen as well.

Unplug your phone and restart it. If it doesn't say 100 percent, plug the charger back in until it says 100 percent on screen.

Repeat this cycle until it says 100 percent (or as close as you think it's going to get) when you start it up without it being plugged in.

Now, let your battery discharge all the way down to 0 percent and let your phone turn off again.

Fully charge the battery one more time without interruption and you should have reset the Android system's battery percentage.

Do I need to change anything? How closely do I have to watch the process?

Do I have to catch the phone immediately after it turns off/reaches 100%, or can I just leave it for a few hours, come back and if it's done, move to the next step.

I am assuming timing might be important on steps 2, 5 and 6, but I'm not sure so I would appreciate some advice.

***EDIT:*** Steps 1/2 Completed-Step 3: How can I tell when charging is complete? I can tell by the ampmeter on the charger that the phone is charging (Just started charging - currently 1.63A), but the battery charging annimation turns off after a few seconds, and there is no other indication.)
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 Battery Calibration?

This will never happen on an S5 klte + variants running LineageOS unless you charge it while in TWRP recovery.

See S5 Battery Charging - Fake 100% which explains the 90~92% expectation after unplugging & rebooting.

I don't like to discharge batteries completely unless I really try to get all the extra seconds while out & about. 5% is my usual bottom limit.

I don't do calibration even when swapping batteries on my S5. Just charge it to 100% once & use until 5% once & that's it.

As seen in the attachment GSam Battery Monitor > Graph icon > Rate of change could be interesting in your case.

GSam user guide which is a little bit dated but informative.

As seen in the second attachment SoT can vary a lot depending on app usage & screen brightness settings on a given day with the exact same battery & setup on both days.

If your battery drops very fast after reaching 40%, or the battery meter all over the place or drops below 90% after charging it to 100%, unplugging & rebooting then your battery probably needs to be replaced.

See Fake vs OEM S5 Samsung Battery

***
[Samsung Galaxy S 5 Unified Development] liquidraver:
BT is still a little unreliable. (much better than few months ago though)
[Samsung Galaxy S 5 Unified Development] Kiastinger:
Would be a tough thing to follow, download a app instead.
[Samsung Galaxy S 5 Unified Development] kurtn:
17.1 becoming official

https://review.lineageos.org/c/LineageOS/hudson/+/288900/3/lineage-build-targets
[Samsung Galaxy S 5 Unified Development] rootkitty:
Does this mean 16.0 is being dropped? If not, any idea how long till 16.0 stops getting security updates.
[Samsung Galaxy S 5 Unified Development] rootkitty:
Battery Calibration Problems

I have been having some charging issues that when the phone is sitting on the charger with the screen off, the charger doesn't keep the battery topped up the way it used to. Not sure if this is due to a bad battery, but the behaviour makes me think the battery is OK. I am also noticing that connectiong the phone to adb seems to be keeping the charging going.

I also noticed a lot of lines like the following in the logs we do have. Is this normal stuff, or does it indicate there is a hw problem.

10-08 21:40:11.624 597 647 W BroadcastQueue: Permission Denial: receiving Intent { act=android.intent.action.BATTERY_LEVEL_CHANGED flg=0x1000010 (has extras) } to com.google.android.apps.turbo/.nudges.broadcasts.BatteryStatusChangedReceiver requires android.permission.BATTERY_STATS due to sender android (uid 1000)

10-08 21:40:11.632 597 651 E BatteryExternalStatsWorker: no controller energy info supplied for wifi

10-08 21:40:11.632 597 651 E BatteryExternalStatsWorker: no controller energy info supplied for bluetooth

10-08 21:40:11.648 597 651 W BatteryExternalStatsWorker: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}

10-08 21:40:11.756 5853 8029 D BatteryInfoLoader: BatteryInfoLoader post query: 0ms

10-08 21:40:11.759 5853 8029 D BatteryInfo: time for getBatteryInfo: 1ms

10-08 21:40:11.759 5853 8029 D BatteryInfoLoader: BatteryInfoLoader.loadInBackground: 3ms
[Samsung Galaxy S 5 Unified Development] kurtn:
There will be no more nightly 16.0 for klte and friends. But the 16.0 sources will be buildable and getting patches merged for several years. Probably someone will start building and sharing unofficial 16.0 klte with updated security patch. Probably monthly.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Official LineageOS 17.1 for S5 klte + Variants Now Available

FYI official LineageOS 17.1 for S5 klte + Variants builds are now available for all supported models:

klte - SM-G900AZ, SM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8, SM-S902L

klteactivexx - SM-G870F

kltechn - SM-G9006V, SM-G9008V

kltechnduo - SM-G9006W, SM-G9008W

klteduos - SM-G900FD, SM-G900MD

kltedv - SM-G900I, SM-G900P

kltekdi - SCL23 & SC-04F

kltekor - SM-G900K, SM-G900L, SM-G900S

In theory you can dirty flash official 17.1 over official 16.0 but note that if you have GApps installed on 16.0 you must flash GApps for Android 10 ARM right after LineageOS 17.1 without rebooting to system in between.

For official upgrading instructions as it can't be done via the built-in Updater see https://wiki.lineageos.org/devices/ > {your device} > Upgrade to a higher version of LineageOS.

Alternatively it's probably possible to simply copy the files to the external SD card & flash from there with TWRP but note that I did not test this yet.

Will report after upgrading my S5 klte which will be a pain in the butt as both Privacy Guard & Lineage AddonSU are deprecated in 17.1 & it will take some time to free up some space in both the S5 & it's Micro SD card for backups before the plunge.

***
[Samsung Galaxy S 5 Unified Development] 761gg1i3219:
PrivacyGuard alternative

Now that 17.1 has come, what is a good alternative to our beloved PrivacyGuard? Is AppOpsX the closest we can get to it?
[Samsung Galaxy S 5 Unified Development] fitittome:
Mine (self build) went without a hitch. No gapps here. But very reliable, only cosmetic issues with fonts and styling etc.
[Samsung Galaxy S 5 Unified Development] sharktm:
will 16.0 still receive any updates/security bumps from now on ?
[Samsung Galaxy S 5 Unified Development] durukanx:
Not official.
[Samsung Galaxy S 5 Unified Development] dcarvil:
I dirty flashed 17.1 over official 16.0 using TWRP 3.4.0 as follows:

Flash lineage-17.1-20201011-nightly-klte-signed.zip

Clear cache & dalvik

Flash open_gapps-arm-10.0-pico-20201010.zip

Clear cache & dalvik

Flash Magisk-v20.4.zip

Clear cache & dalvik

Reboot system

On initial boot, it was running very slow and laggy while google apps updated. Once the updates were complete, the only problem was my digital clock widget was missing from the home screen. The widget in 17.1 appears to be a different size than 16.0, which may be the cause.

I was previously rooted with Magisk, so I did not remove root before updating. I don't know if it is necessary to remove Lineage AddonSU if you have it, but it seems like a good idea to me. Download link for Magisk is https://github.com/topjohnwu/Magisk
[Samsung Galaxy S 5 Unified Development] Zytrel:
How about dirty flashing 17.1 with encrypted data? Anyone tried that yet?
[Samsung Galaxy S 5 Unified Development] bersem:
I think it is possible to upgrade from unofficial to official:

Download official ROM File

Reboot to TWRP

Mount system

Copy downloaded ROM file to: data/lineageos_updates

Boot to system

Run the updater

EDIT: Doesnt work because its signed maybe
[Samsung Galaxy S 5 Unified Development] Eadn33:
I dirty flashed 17.1 on my G900v with TWRP 3.4 and Open Gapps pico. All went fine except loss of service requiring restore of the EFS partition, which is normal for my G900v whenever I update. However, in this case I had to switch back to TWRP 3.3 to successfully restore the EFS. So far, everything Is working very well. I have not rooted with Magisk yet. I did not unroot from Lineage add on prior to updating.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Dirty Flashing 17.1 Encrypted - EFS Partition Restore No Service

I remember a post where [MENTION=7978913]fitittome[/MENTION] said that his S5 16.0 was encrypted. Maybe he can reply to that question & also specify which recovery version he used?

***

TWRP 3.4 EFS Partition Restore Fail

Thanks :good: for the report. :cool:

Important info that you could not restore the EFS partition with TWRP 3.4 but could with TWRP 3.3.

Do you remember the exact error message?

FYI you can take screenshots in TWRP with Volume down + Power which are saved in external SD card/Pictures.

Also 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.

I wonder if an EFS partition backup made with TWRP 3.4 prior to dirty flashing 17.1 over 16.0 could be restored while running 17.1. :confused:

Because a standalone EFS partition backup is so important (especially for the S5 G900V) & so small @ less than 10MB it does not hurt to have more than one IMO.

For those wondering what we are talking about see EFS Partition Backup - No Service, No IMEI & No SIM Card Fix

***
[Samsung Galaxy S 5 Unified Development] HippoMan:
Successful dirty flash from 16.0-microG to 17.1-gapps on my klte device.

Details here: https://xdaforums.com/showpost.php?p=83689209&postcount=1417

.​
[Samsung Galaxy S 5 Unified Development] fitittome:
Yes, its encrypted. It seemed to take a millennia to boot, but no problems. I had installed TWRP 3.4 some months prior to upgrading.
[Samsung Galaxy S 5 Unified Development] 761gg1i3219:
Help! I need to switch from LOS with microG to official

Is this possible? Do I need to wipe all data?

Also, does anyone have experience with the microG Magisk module? Are there many differences with it on official compared to unofficial LOS with microG?
[Samsung Galaxy S 5 Unified Development] kurtn:
If you are running Lineage.microg.org at the moment, just wait for the next build. Should update to 17.1
[Samsung Galaxy S 5 Unified Development] 761gg1i3219:
I know, but their release schedule has slowed down a lot, used to be weekly OTA and now it is roughly monthly. In switching I would have the release schedule from Official LOS.
[Samsung Galaxy S 5 Unified Development] MapisM:
I just did exactly the same, with the only exception of Magisk, on an official 16.0 non-rooted klte device, and I can confirm the same (great!) result.

A couple of questions:

1) for rooting the device, can I now just boot on TWRP, flash Magisk-v20.4.zip and afterwards install the Magisk Manager APK, or is there any other trick?

2) I have another identical device already flashed with Resurrection Remix Q.

Would it be possible to dirty flash Lineage 17.1 as above, also on that device, or should I follow another procedure?

Many thanks in advance!
[Samsung Galaxy S 5 Unified Development] kurtn:
1 only flash magisk. Magisk manager usually is installed be zip

2 clean flash strongly recommended. Wipe system and data. Then flash LineageOS
[Samsung Galaxy S 5 Unified Development] sharktm:
i cannot adjust the screen brightness on the latest twrp 3.4.0.0, does anyone else encounter this problem ? i reflashed the previous version again (3.3.1.0) and the screen brightness works.
[Samsung Galaxy S 5 Unified Development] dcarvil:
1. Flashing via TWRP is what I usually do. The Magisk zip is supposed to include the Manager, but it does not always work, so you may need to install the apk.

2. Sorry, no idea.
[Samsung Galaxy S 5 Unified Development] hjfeih:
Smart Lock

After 17.1 is now officially released I'm not sure if this is the right forum for my problem. I had installed the Unofficial Release of 17 and since today the official one. From the start I face the problem that Smart Lock ("Reliable Location") is not working. Is there any idea what I caan do about this??
[Samsung Galaxy S 5 Unified Development] Eadn33:
EFS restore after upgrade to 17.1

I think some correction/clarification to my previous post is needed. I reflashed TWRP 3.4 to take another look at this and it looks like it is just looking for my backups in a different folder. When I tried to restore my EFS partition, it only showed the TWRP/BACKUPS/bdxxxxx folder that houses all of my previous TWRP backups, i.e. all I saw after hitting Restore was the bdxxxxx folder.

I tried to open this folder to get to the backups, but It acted as if the bdxxxxx folder was the backup and asked what partition to restore but gave no partition options. I then used TWRP file manager to move my EFS backup from TWRP/BACKUPS/bdxxxx to TWRP/BACKUPS folder and it was then available to restore.

Then reflashed back to TWRP 3.4 and made a backup of EFS. It placed that backup in a new folder it created TWRP/BACKUPS/SM-G900v and now that is the only folder it accesses when hit the Restore button.

So in summary, no error, it seems just a change in folder name used for backups with new TWRP and /or my operator error. :)

Separately, for reasons unknown, my EFS is surviving reboots after this upgrade. Prior to, I had to restore EFS every time after initial boot or restart.

Thanks all very much for all the information shared here.
[Samsung Galaxy S 5 Unified Development] Sub_Zero2:
Lineage-17.1 (I'm posting here since there's no forum thread yet): G900F: During calls, mobile data connection drops from 4g (lte) to edge. When hanging up the call, mobile data connection goes back up to 4g. I'm using M baseband FXXS1CQD2.

Anyone else experiencing this issue?
[Samsung Galaxy S 5 Unified Development] curiousrom:
LineageOS for S5 klte + variants does not support VoLTE

Sadly LineageOS for S5 klte + variants does not support VoLTE (Voice over LTE).

As I can see in the status bar of my S5 G900M klte 16.0 it automatically switches from LTE (4g) to 3g (H+ or H) during calls & automatically back to LTE after I hang up.

Samsung implemented VoLTE on the S5 with a proprietary method that nobody could port to non-Samsung OS custom ROMs.

I found this in the OP of [MENTION=2693412]haggertk[/MENTION]'s old thread [ROM] [OFFICIAL] LineageOS 14.X for Galaxy S5 | Android 7.X Nougat:

C'est la vie!

The fact that it drops to Edge instead of 3G on your S5 during calls may depend on your network provider & the bands it supports.

What happens on your G900F if in > Settings > Network & internet > Mobile network > Advanced panel > Preferred network type > you select GSM/WCDMA auto after writing down or screenshot the default setting?

Does it still drops to Edge during a call?

Maybe some S5 17.1 users could chime in?

***

Edit: [MENTION=2696268]Sub_Zero2[/MENTION] "...I'm using M baseband FXXS1CQD2" - You could update to G900FXXU1CQK3.

See S5 Odin Flashable Modem & Bootloader

***
[Samsung Galaxy S 5 Unified Development] guest4711:
This will not work. MagiskManager needs root permissions for installing Magisk. Without root access it could patch a given boot.img but not install it.
[Samsung Galaxy S 5 Unified Development] Sub_Zero2:
Thanks for clarifying, I didn't realize VoLTE was required for this.