yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] fitittome:
I had to set this earlier with this bog standard app.

https://play.google.com/store/apps/details?id=com.basicapp.gl_compass

the calibration survived a soft reboot, but not a hard one. Maybe that's a clue?
[Samsung Galaxy S 5 Unified Development] fipsy:
There must be a correlation between the OS and the kernel in any case, because at the beginning of August there was the problem that sdcardfs worked with an older version of the Boeffla kernel, but not with the new one. Lord Boeffla could not explain this to himself and the reason is still unknown. The fact is, however, that all problems disappear in my case when I simply disable sdcardfs in build. prop.

Aha! This confirms my hypothesis that a reboot causes the loss of information. In earlier Android versions the calibration survived a restart.
[Samsung Galaxy S 5 Unified Development] jeremywh7:
Telephony fix

Here is a link to the post in that thread, for the telephony fix zip file.
[MENTION=5949099]Brasscat82[/MENTION] - If you highlight text then click the url/link button (chain link icon) and paste the url, it will create the code for you. :)

And thank you, btw, my wife will love this. :P
[Samsung Galaxy S 5 Unified Development] snikerfreak:
+1
[Samsung Galaxy S 5 Unified Development] darzur:
Hello,

Since couple of releases I have to manually update after OTA download as update doesn't start automatically when rebooted into TWRP. It was never a problem, but it looks like now OTA download folder has changed. It always been /data/data/org.lineageos.updater/app_updates but now can't find zip file there. So my question is - where to look for it?

Wysłane z mojego Nexus 7 przy użyciu Tapatalka
[Samsung Galaxy S 5 Unified Development] fitittome:
/data/lineageos_updates/
[Samsung Galaxy S 5 Unified Development] darzur:
Thanks. :)

Wysłane z mojego Nexus 7 przy użyciu Tapatalka
[Samsung Galaxy S 5 Unified Development] systemcrash:
nope. August.

---------- Post added at 11:58 PM ---------- Previous post was at 11:56 PM ----------

Sorry - it was included - I wasn't paying attention to the kernel tags when SDcardFS changes were merged for the older kernel

https://review.lineageos.org/#/q/project:LineageOS/android_kernel_samsung_klte

vs recent changes

https://review.lineageos.org/#/q/project:LineageOS/android_kernel_samsung_msm8974

and

https://review.lineageos.org/#/q/st...e-common+branch:cm-14.1+topic:sam_8974_kernel

But it is also in the msm89xx kernel we went over to recently. Samsung were early adopters of the SDcardFS malarkey.
[Samsung Galaxy S 5 Unified Development] fipsy:
We are always talking about the disadvantages and problems of SDcardFS. I'm just asking myself if there are any advantages for the experienced user?!
[Samsung Galaxy S 5 Unified Development] j1gga84:
I don't know if this was asked before but is WiFi Calling working on LOS?

It is working on a Galaxy S7 with Stock ROM, I am not sure if it is even working on our S5 with stock,

VoLTE does not work and will maybe never work on LOS or LOS based ROMs so I fear it is the same with WiFi calling.

regards
[Samsung Galaxy S 5 Unified Development] fitittome:
Blimey, Mr H has been busy. How come none of this shows up in the Changelog? All I recall is a single entry saying something like, now we are using the new kernel.....
[Samsung Galaxy S 5 Unified Development] fitittome:
I don't know. My carrier, Three, uses this app Three InTouch it will successfully install but it is very permission hungry. It goes through the motions of making the call but fails saying that there is a Temporary Problem with the service. Never looked into it more than that as I sort of assumed that there are a lack of standards etc. VoLTE will not work for the similar reasons, I think. Vodafone do their own thing, as do Samsung etc. A nightmare for LOS to support. I can't find anything with the 'official' LOS position though.
[Samsung Galaxy S 5 Unified Development] cdrivex4:
umm using ampere i have noticed that even if the phone is at 97% charging, it seems to be pulling 1800 mA. seems a bit high draw at this point, don't think it was like that before. i seem to remember it being lower at thus point in the charge cycle. anyone else got this?
[Samsung Galaxy S 5 Unified Development] Nixda99:
Recalibration of compass after reboot

That the compass is loosing it's calibration after hard reboot is an old problem which affects more Samsung modells than the S5 and appears

also on stock rom. It is a bug of the compass chip, not every chip modell has this problem, but more than one.

If your compass has a bad default calibration, you always need to recalibrate it after a reboot (for example with GPS Status & Toolbox).

Found only a german article about that: https://allaboutsamsung.de/2014/05/samsung-galaxy-s5-kompass-problem/
[Samsung Galaxy S 5 Unified Development] j1gga84:
Thanks for the info :good:

I guess we will get problems one day if LOS team will not be able to bring VoLTE to our or other devices, because here in germany 2G/3G is not improved and extended anymore, only 4G, which means that 4G reception is sometimes much better in some regions than 2G or 3G, but we can only phone via 2G or 3G on LOS and not 4G which is not a big thing today but in a few years this will be essential in my opinion..

regards
[Samsung Galaxy S 5 Unified Development] fipsy:
In Europe, 2G and 3G will probably still exist until 2023. Mobile operators have not yet set a deactivation date. As it currently looks like, 3G will be switched off first and 2G will be switched off much later. The frequencies in the 900 and 1800 MHz range were newly auctioned in Germany at the end of 2016 and will run until 2033. Both frequency ranges can be used for both GSM and LTE. Therefore, the transition from GSM to LTE will probably be smooth. According to customer requirements. If many customers continue to use 2G, 2G will no doubt continue to be offered. A problem here are many industrial machines that communicate via GSM and have built-in mobile radio modules. Disconnecting the networks would cost billions, especially in highly industrialized nations like Germany. For this reason alone, the shutdown will undoubtedly take a long time.
[Samsung Galaxy S 5 Unified Development] fitittome:
I use GSam Battery Monitor Pro and it tells me that my 'loaded' phone draws about 450mA. It's battery sucker function will help identify the problem.
[Samsung Galaxy S 5 Unified Development] cdrivex4:
When you say "loaded", i assume you mean that your phone is disconnected from the charger and you are using it and thus the battery is "discharging" in this circumstance am getting -450mA. I am talking about while you are connected to the charger, i would have though that as you approach the 100% fully charged mark, the phone would cut back the amount drawn from the charger i.e 80% 1800mA, 90% 1700 mA 95% 800 98% 600mA 100% 450mA. This in my mind is how it was behaving before, im not sure if that is correct. Currently it seems that it is aggressively drawing 1800 till it stops.
[Samsung Galaxy S 5 Unified Development] fitittome:
Yes, you assumed right, my regular phone, discharging. OK I understand what you are getting at now. You watch these things? ;) Mine seems to work, more or less, like you expect:-

-85% charge 1800mA

86-89% charge 1600mA

89-99% charge 900mA

100% charge still draws 900mA

This is with the 06SEP Nightly on klte. I have recently updated the bootloader (a new one came out end of Aug) and baseband as per signature.
[Samsung Galaxy S 5 Unified Development] fipsy:
This is a very interesting subject for me! The main reason why I use Boeffla kernel and not LOS kernel is that with Boeffla the charge current is adjustable! This means that when charging at night, the battery is not fully charged very quickly after an hour, but only shortly before I get up. This protects the battery very much.

But I also noticed that the charging electronics in the S5 doesn't work very reliable. Sometimes it lowers the charging current after 80% of charge, but sometimes it does not. Therefore, I have set the charging current to 700 mA (but only possible with Boeffla).
[Samsung Galaxy S 5 Unified Development] 10goto10:
Just FYI, the 'charging current' info the S5 reports is the maximum attainable, best-case charging current, i.e. it does not actually reflect the amount it is actually drawing from the power source. And the discharge rates (450mA) is just bogus, that's why the AccuBattery app doesn't support the S5 as it is not actually being measured.

If the reported charging rate goes down as the battery gets close to full, it is usually because the device is limiting it because of temperature limits or unstable power. The actual charging rate will naturally be lower than reported if the battery gets close to full (trickle-charging.)

There's no need to manually drop down the charging rate unless you want to prolong the battery life even more; the built in algorithms should be smart enough.
[Samsung Galaxy S 5 Unified Development] fitittome:
I am not sure whether to laugh or cry. Is it not possible for there to be certainty with things android/manufactuer/custom rom? Everything seems to be built on sand. :(
[Samsung Galaxy S 5 Unified Development] alex19EP:
Caught You provide Me Last Boot Loader and modem firmware Thank you very Match for do it
[Samsung Galaxy S 5 Unified Development] Crickets0812:
is it just me or is the battery life excellent on the new lineage OS nightly? I'm getting 6.5 hours sot without any modifications
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
Please correct me if I'm wrong but, It looks a your asking:

"Can you provide me with the last Bootloader and modem firmware? Thank you very much."

I've got a feeling that you may actually be searching for the Firmware Modem Update.

If that's the case, then the following thread should be where you can locate it and ask if you aren't sure.

[BASEBAND-FIRMWARE-MODEMS]Verizon Samsung Galaxy S5 {SM-G900V/KLTEVZW}[ODIN] by Ibuprophen

Good Luck!

~~~~~~~~~~~~~~~

I Am The Egg Man,

They Are The Egg Men.

I Am The Walrus!

Coo Coo Cachoo!

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Samsung Galaxy S 5 Unified Development] alex19EP:
yes exactly. but i hev smg 900f. I'm from Russia so please forgive me for grammatical errors.

i do'nt find bootloader and modem in this fred.
[Samsung Galaxy S 5 Unified Development] willes74:
https://www.androidfilehost.com/?w=files&flid=18025

Here you are. For G900f
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
Nothing to forgive... I already could tell that there was a language barrier. I've always understood this and never had a problem with it. This is why I asked the questions that I did for clarification.

I can sometimes tell which approximate area the member is from based on how the words are placed as well as the structure.

I used to talk to individuals from other regions throughout the world and picked up on allot of these things.

***EDIT: Just as an FYI... The following thread is also a good place for Noob Friendly questions:

[SUPPORT THREAD] The Galaxy ~S5~ All in one support thread!**NOOB FRIENDLY** by Ricky Divjakovski

Thank you very much for helping aarnaarn2 out since it was cleared up as to what the member was asking for exactly. LOL! :)

~~~~~~~~~~~~~~~

I Am The Egg Man,

They Are The Egg Men.

I Am The Walrus!

Coo Coo Cachoo!

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Samsung Galaxy S 5 Unified Development] alex19EP:
please, Tell me: does the flash fire work on the los?
[Samsung Galaxy S 5 Unified Development] SuperSandro2000:
Never got it to work. Not sure about tw. Just use twrp.
[Samsung Galaxy S 5 Unified Development] alex19EP:
not long ago I lost my sight so it's hard for me to use recovery. can there be a way to automate the commands and then reboot?
[Samsung Galaxy S 5 Unified Development] SuperSandro2000:
I know fur sure flashify has that feature and Boeffla donate app. Just Google and you should find something.
[Samsung Galaxy S 5 Unified Development] Rahmsuppe:
Is there any way to light up the (my) too dark LED Notification light? I know there is no switch in LOS, but maybe there is another way?

(G 900f)
[Samsung Galaxy S 5 Unified Development] Saber:
Settings->Notifications->Gear icon ->Notification light
[Samsung Galaxy S 5 Unified Development] aniksha:
FlashFire

Yes, read my post #7868

---------- Post added at 12:07 AM ---------- Previous post was at 12:07 AM ----------

Yes it does, read my post #7868
[Samsung Galaxy S 5 Unified Development] Rahmsuppe:
[/COLOR]

I know that option :)

The LED as itself is working.

My problem is, that the LED light is always too dark. Thats the (hardware?)-problem.

And I don't find any configuration to make it brighter e.g. so you can see the notification on sunlight or even NOT by looking directly to the device.
[Samsung Galaxy S 5 Unified Development] heshan_1010:
The only option as far I know is for you to flash the boeffla kernel and increase the brightness using the boeffla-config app.
[Samsung Galaxy S 5 Unified Development] Saber:
AFAIK, the led brightness should be at max already (or a least a lot brighter than stock Sammy ROM). On stock Sammy ROM, the notification light was a lot dimmer for me. It could be hardware, unless it's the color that you selected for your notification led (select manually, not auto).
[Samsung Galaxy S 5 Unified Development] Rahmsuppe:
Thanks,

I've tried now the Boeffla Kernel with the config tool and I was able to bright up the LED Notification light. Set it to max. 255, but still a little bit too dark imho. Seems this is a hardware limit now. Well...

- Would be nice to see those option in the official LOS Kernel!
[Samsung Galaxy S 5 Unified Development] gjiam:
Does anyone have a problem with location services on the latest nightly build? I can't get it to work in any mode, with or without GPS. I'm running g900p with G900PVPU3BOG1 modem.
[Samsung Galaxy S 5 Unified Development] fitittome:
That modem dates from Aug 2015. Update it and try again.
[Samsung Galaxy S 5 Unified Development] E_Ben:
Yes. TWRP supports openrecovery scripts:

http://wiki.rootzwiki.com/OpenRecoveryScript

Probably other apps like the mentioned flashfire use openrecovery scripts, too.
[Samsung Galaxy S 5 Unified Development] fatkpirok:
Hi,

I download the latest lineage-14.1-20170906-nightly-klte-signed, but does not recognize the SIM card. Is this "lineage-14.1-20170906-nightly-klte-signed" OK for my samsung s5 KLTE?

Thanks
[Samsung Galaxy S 5 Unified Development] Il Gerry:
Performance Menu Missing

Hi I noticed a "strange" thing on the menu: Missing the Performance Menu ...

there is something in the Battery Menu like Profiles but no way to change frequencies to the CPU, Governator or even the ZRam.

Is it normal or missing something to me?:confused:

Thank you
[Samsung Galaxy S 5 Unified Development] heshan_1010:
Those settings were removed back in CM12 in favor of the battery profiles. Use an app like kernel auditor to change those settings now.
[Samsung Galaxy S 5 Unified Development] Il Gerry:
Ok thanks for the explanation then it is time I try the Boeffla-Kernel,: D

that the comments I read seems the best for this Rom.
[Samsung Galaxy S 5 Unified Development] a11cf0:
Does the latest build support GLONASS / BDS on the G900F?
[Samsung Galaxy S 5 Unified Development] fitittome:
GPS Test shows this, I think Glonass satellites normally use the range of 65 to 88, but I could be wrong.

[IMG="GLONASS"]https://i.imgur.com/ddZ2ESX.png[/IMG]

But apparently GLONASS has been disabled on klte due to the high volume of GPS changes in Android N. Not sure if that's still the case.

https://jira.lineageos.org/plugins/servlet/mobile#issue/BUGBASH-383
[Samsung Galaxy S 5 Unified Development] cal002:
Use SatStat from f-droid, then you don't have to guess about SvIds used by Glonass.

Jira comment is misleading, I think Glonass works except for the "used in fix" information

that is lost due to Qcom bug, see my earlier posting about it.
[Samsung Galaxy S 5 Unified Development] hiaschey:
G900F Broadpwn Broadcom exploit seems patched

seems it has been patched:

KLTE:

net: wireless: bcmdhd: update bcm4354/56 FW (7.35.101.6)
android_hardware_broadcom_wlan

since Changes included in lineage-14.1-20170816-nightly-klte-signed.zip (found at lineageos klte changes-log)

This seems to fix BroadPWN as described at blog.exodusintel.com (the wmm buffer as referenced i think).

Supported devices according to LineageOS wiki on "klte":

SM-G900F

SM-G900AZ

SM-G900M

SM-G900R4

SM-G900R7

SM-G900T

SM-G900V

SM-G900W8

SM-S902L

(PS: Sorry for not posting links i'm not allowed due to less than 10 posts. Also weird: URLs can't be reposted in quotes due to that reason)
[Samsung Galaxy S 5 Unified Development] aniksha:
[MENTION=2693412]haggertk[/MENTION]

BITMASK VPN APP

Bitmask (LEAP Encryption Access Project) from Playstore does not function proper anymore. It was working correct during all August nightly, but now I can't login anymore. I hope there is a solution.

G900F (nightly 06/09/2017)

SuperSU 2.82

TWRP 3.1.0.1

G900FXXU1CQE1_G900FXXU1CQB2_Baseband_Firmware by haggertk
[Samsung Galaxy S 5 Unified Development] Efraimjb:
Hi

I am a long time cm/los user on my trusty old galaxy S5 Sprint.

After seeing multiple references to the Boeffla-Kernel.

Can anyone please explain me what are the advantages and disadvantages of installing this kernel.
[Samsung Galaxy S 5 Unified Development] fitittome:
Yes, I noticed that too. But the Lineage CVE Tracker doesn't seem to have any reference for any device or kernel (as far as I can see) regarding CVE-2017-9417.

---------- Post added at 07:47 AM ---------- Previous post was at 07:41 AM ----------

It allows you to fiddle with lots of kernel parameters. But it will make your phone more difficult to support so you will not be able to submit bug reports. See OP. Also, Boeffla is discontinuing support for the S5 when LOS15 hits. https://boeffla.de/
[Samsung Galaxy S 5 Unified Development] hiaschey:
did you read my entire post?

I looked at the methology of Broadpwn, which uses an wmm buffer overflow, and someone touched that it in klte (specifically, the firmware which you have to check via terminal whether you are affected by broadpwn), NOT globally in LineageOS.

I refer to blog.exodusintel.com + broadpwn (google that, i can't put links here).

If you just want "CVE-2017-9417" to appear in the changelog you may be out of luck, to me it seems they wanted to fix it quickly rather than putting the proper label on.

Also, since this is kind-of chip firmware dependent, it may very well be different for each device!
[Samsung Galaxy S 5 Unified Development] fitittome:
Yes.

---------- Post added at 09:05 AM ---------- Previous post was at 08:59 AM ----------

Have you seen this? This is what I was talking about it is processor and device specific, so as to include issues like this.

https://cve.lineageos.org/
[Samsung Galaxy S 5 Unified Development] cdrivex4:
does anyone have any suggestions, recent builds are seeing really high swap and cpu spikes in general use. 900fd is almost unuseable.. have made sure i have 2gb internal free but it's not helping anymore

additionally... according to https://review.lineageos.org/#/c/185102

the heap limit was increased from 192 to 1024 but according to kernel auditor

nothing has changed.. this is the only location i can see a value of 192 am i looking in the right place?

Should this even matter?
[Samsung Galaxy S 5 Unified Development] 10goto10:
You're reading the changelog incorrectly, it was increased to 192 _for_ devices with 1024MB of RAM.

As for performance problems, can't confirm as I'm on another ROM. Maybe it's time to back up your data and apps, update your baseband and bootloader and clean flash...
[Samsung Galaxy S 5 Unified Development] fipsy:
For me, the main advantage of this kernel is that you can set the maximum charging current of the battery. This is for the AC adapter charger, the USB connection and the wireless charger independently from each other.
[Samsung Galaxy S 5 Unified Development] tdallagnol:
6.5 SOT is my dream that never came true (to me)

Hi Crickets0812

I recently switched to LOS (lineage-14.1-20170906-nightly) and I don't get more than 3h, so 6.5h is a dream to me :)

It looks like a great firmware, very fast, responsive and stable. I'm pretty happy with it besides the battery behavior (of my klteduos)...

I was using CM13 before, and battery was better than I have now, but it wasn't that better... I don't know, maybe my product is defective, I already bought a new battery like 9 months ago and it was better than the old one, but still not great. I always think how people can get 6.5h SOT as I never got that even with stock firmware.

Also the standby consumption looks a bit disapointing in my case. The device looks like to spend 10% in a period of 6h when just resting at the side of the bed (wi-fi connected and one SIM card operating only, as I'm not using both now).

I'm using Gapps stock. Maybe it is the culprit of some battery drain? I tried to use "wakelock detector" but its output looked strange to me in LOS 14, a lot of apps show *launch* and *alarms* wakelock which looks pretty strange. I don't have any modifications in my firmware, it's not rooted, just have installed Gapps.

Best regards,

Dallagnol
[Samsung Galaxy S 5 Unified Development] jdrch:
FWIW the GPS disconnecting/connecting Waze bug seems to have been fixed in the latest build.

It's happening to pretty much everybody across all builds and S5 models (see other reports on the thread) for this to be a solution. Updating baseband, bootloader, etc. doesn't fix it. Also, as someone else pointed out, problems started after a variable that affects the "swappiness" of the OS was changed, so the problem definitely lies in development somewhere.

Wipe and clean flash should be the absolute last resort fix to any issue.

---------- Post added at 15:10 ---------- Previous post was at 15:08 ----------

So the phone should be getting LOS 15, then?
[Samsung Galaxy S 5 Unified Development] 10goto10:
Ah, that's too bad then. Glad my current ROM hasn't merged the newer changes yet, lol. And I think swappiness for the S5 was set to 100 since the CM13 days, so I think that's a red herring. There must be a memory leak or something somewhere that's causing the excessive swap usage in the first place...

And yes, I think our device will be getting Oreo (there has been some commits for it), which is super awesome!
[Samsung Galaxy S 5 Unified Development] shinobusensui:
fixed for me NFC ,i had a wrong ROM from me firtst time flash (kltedv) work 99% not work NFC in G900M

i not read the description only flash up from kltedv and change tp klte, SM-G900M works 100%
[Samsung Galaxy S 5 Unified Development] j1gga84:
I ask myself why there is still no security fix released for september :confused:

or do I look on the wrong place?

https://android.googlesource.com/platform/cts/+refs

regards
[Samsung Galaxy S 5 Unified Development] fitittome:
Lineage are no longer a manufacturer like CM was. The manufacturers get a months advanced warning of the security issues so they can develop patches. So there will be a lag of about a month whilst the devs figure them out and implement them. You can track *kernel* related security issues at https://cve.lineageos.org/ but if you have a specific non-kernel CVE it is probably best to check Gerrit with a simple query e.g. https://review.lineageos.org/#/q/CVE-2017-9417 then scan the results.

Hope that helps! :)

---------- Post added at 11:15 AM ---------- Previous post was at 11:00 AM ----------

I'm glad it's working for you. But, I think that there would be an 'assert' to stop you doing that by accident. Did you get an error 7 when you installed the wrong one?
[Samsung Galaxy S 5 Unified Development] Atento:
900M has always been KLTE. You should be careful when flashing roms and kernels, because it can be a big problem in certain situations.
[Samsung Galaxy S 5 Unified Development] shinobusensui:
its rare no stop to flash twrp or compared to are correct version rom/hard, flash and work 99%