yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] fipsy:
I misunderstood. As far as the general power consumption is concerned, the bootloader of course also plays a role! Independent from the CPU problem.
[Samsung Galaxy S 5 Unified Development] phalkon30:
Klteusc, running mid November build on stock kernel. Greenify installed, and wifi sleep when idle. Obviously in airplane mode, I doubt this is possible with a cell connection.

https://photos.app.goo.gl/JpdOow1TLpaQqSyY2 (Tapatalk won't upload the picture..)

That's 16 days without a charge, and a day left. Ok, only 45 minutes SOT, but I'm telling you that battery life is the result of misbehaving apps. I went through privacy guard and denied a bunch of permissions to bad apps, I get absolutely amazing battery life.

This rom can idle fine.
[Samsung Galaxy S 5 Unified Development] Arrxa:
Is the Core 4 freq bug a result of this change? I noticed that after the early September builds people started noticing the bug and this commit coincides with that.

review.lineageos.org/#/c/190299/ << add the https:// since I am new I can't post links. :p
[Samsung Galaxy S 5 Unified Development] mmtrt:
Good find, This change causes cpu1 cpu2 cpu3 set governor default to performance instead of interactive and this performance governor uses full cpu frequency so it uses more battery as it activates cpu 1 2 3 on load but I think MP-Decision is broken its making last cpu3 to full frequency OR could be other issue.
[Samsung Galaxy S 5 Unified Development] fitittome:
I did think it could have been to do with that change. If you search for that gerrit number here it crops up a few times. I have come to accept it as being a bug in the 'new' kernel.

The thing is most people wouldn't have noticed. The people who would notice use custom kernels anyway.

I guess reverting the change wouldn't hurt, just to see.
[Samsung Galaxy S 5 Unified Development] systemcrash:
Disagree (notwithstanding that the MPDecision could be 'broken'). I run klte, and watch CPUfreq occasionally, I do not have any cores locked at max freq. I have not run a standard boot.img for a while, 3 months with [MENTION=522292]haggartk[/MENTION] 's ALMK boot.img, and now with [MENTION=5795145]javelinanddart[/MENTION] 's 30 swappiness boot.img. They might request other CPU features, I cannot comment.

What I can say is that SOT, and general battery life could be better - it could also be worse.

From now on, when posting about CPU stuff, include your MODEM, boot.img, nightly version, and model, and uptime.

The other suggestion recently to sandbox the hell out of apps is also good - time-consuming, but good :)
[Samsung Galaxy S 5 Unified Development] Brasscat82:
Those aren't small or simple.apps
[Samsung Galaxy S 5 Unified Development] systemcrash:
read the "," comma as "and", - small and simple apps *AND* gapps (the exceptions) etc...
[Samsung Galaxy S 5 Unified Development] pepe100:
Yes the big issue of this Rom is the battery life if It improves in this area the Rom would be perfect.
[Samsung Galaxy S 5 Unified Development] fitittome:
Good points. But CPU Stats for example doesn't show CPU3 running at max freq. Whereas CPU-Z and KA does. Worse, if you check via KA then you get MP-Decision errors flooding the logcat. :(
[Samsung Galaxy S 5 Unified Development] j1gga84:
Maybe MPdecision should be removed completely and IntelliPlug should become the standard.. :good:

regards
[Samsung Galaxy S 5 Unified Development] mattnin:
I just loaded cpu-z and I also do not see any cores locked at Max freq.
[Samsung Galaxy S 5 Unified Development] fitittome:
Umm. I do! I wonder if it's an app doing this? There's no load on the CPU but it's stuck 2457Mhz. Off to investigate what tools there are to see what processes are running on what CPU.

Edit:

The only thing I can find to help is

toybox ps -A -O CPU

There is one item of interest in the output:-

root 40 2 0 0 erred_free 0 S 3 [system]

Edit2:

and to make it even more tricky it is intermittent...... but once locked it stays locked. However, it does happen on a virgin install (which I just upgraded to 7DEC), which I guess eliminates most of my other software.... I was thinking that AF-Wall may have been causing it at one point.
[Samsung Galaxy S 5 Unified Development] fipsy:
I think [MENTION=7978913]fitittome[/MENTION] had already noticed this some time ago and asked this question more than once. But this change is about frequency control and not hot plugging. I don't think that there's any connection. It seems to be a kernel problem because custom kernels are not affected.
[Samsung Galaxy S 5 Unified Development] fbs:
did you try my kernel (TUNED kernel)? just install it, no tweaks necessary.. :P
[Samsung Galaxy S 5 Unified Development] pepe100:
I will try it
[Samsung Galaxy S 5 Unified Development] fitittome:
Ah, I remember that and I had a copy so I installed it (boot.20170912_almk_klte.img) and the CPU3 locked at 2457Mhz problem seems to go away. But that pesky SIM card icon reappeared! So reinstalled the kltelowerswappiness.img kernel and my Sim was sorted!
[Samsung Galaxy S 5 Unified Development] Panzerknakker:
According to cmxlog "CPU3 locked at 2457Mhz problem" will be fixed in next nightly.
[Samsung Galaxy S 5 Unified Development] huawei92:
I tried to install the beta drivers of 330 and I noticed that seeing the videos the phone goes into randoom reboot, there is a way to install them the same, because the graphics is affected a lot with the current driver you notice a degradation of quality graphics from v.145 to current v.140 di lineage os,even the brightness is affected.
[Samsung Galaxy S 5 Unified Development] fipsy:
Can confirm that. I tested the new kernel and the problem has gone. Thanks a lot to [MENTION=5795145]javelinanddart[/MENTION]!
[Samsung Galaxy S 5 Unified Development] HulkSmashBurgers:
Which kernel? Link, please.
[Samsung Galaxy S 5 Unified Development] fipsy:
It was just a test version. It will be integrated into the next LOS weekly (https://review.lineageos.org/#/c/198298/).
[Samsung Galaxy S 5 Unified Development] Blackburn119:
You can manually disable the core on kernel audiutor app if you don't want to wait for next week.
[Samsung Galaxy S 5 Unified Development] 7mick7:
Till night I lost 13% of battery.

When I make screenshot and post it here I lost 4%. It's very bad.
[Samsung Galaxy S 5 Unified Development] fitittome:
What model exactly, what baseband version?
[Samsung Galaxy S 5 Unified Development] 7mick7:
G900FD.

Last official release.GGaps mini
[Samsung Galaxy S 5 Unified Development] fitittome:
That maybe OK but a version number would have been handy. Anyway, what is the Bootloader version? You can find that at the terminal prompt with:-

getprop ro.bootloader
[Samsung Galaxy S 5 Unified Development] phalkon30:
Also, were you in bad signal? If cell standby is number one, that points to the phone hunting for a tower
[Samsung Galaxy S 5 Unified Development] Ranniel:
This ROM Has Battery Drain? I want to know why I'm thinking about installing it and I do not want to have to flash another ROM again by battery drain[emoji848]
[Samsung Galaxy S 5 Unified Development] somebully:
When is next weekly released? I guess weekly is a bit more "safe" choice than nightly

Supposedly fixed in nightly (check few posts up).
[Samsung Galaxy S 5 Unified Development] fipsy:
Battery drain is something different for everyone. For one it is 10%/h, for the other 2%/h. Consumption depends very much on the installed apps. That's why everyone has to try it out for oneself. However, there are very few who complain about a real battery drain that really deserves its name. Positive reports of low battery consumption are much more common.

---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------

There are only weeklies. They are called "nightly" but they are released weekly. That's why I call them weeklies. ;)
[Samsung Galaxy S 5 Unified Development] O_oaa:
FM Radio for SM-G900P

I recently purchased a SM-G900P (Sprint), and it appears as if the FM radio for this phone is unavailable as of the latest build (14.1-20171208-NIGHTLY-kltedv w/ included kernel using SpiritF and NextRadio). After hours of digging and trying pre-canned "fixes" to try to get the FM radio to work, I believe this may not be enabled in the unified build. I even tried some custom kernels to see if that would help... nope. =(

According to the research I've done, SM-G900P's running stock are able to use the FM radio tuner, generally with NextRadio. It also appears LineageOS has support for FM radio tuners for other phone builds. Is there any particular reason why this isn't available in the KLTEDV builds? Am I simply mistaken or am ignorant that this somehow works out-of-the-box and I'm just doing it wrong?

While I'm not an Android developer by any means (though I am a software developer by trade), I'm willing (and probably will just for the fun of it) try building from source. However, any tips/tricks/information/advice/knowledge/wisdom anyone has about this is appreciated. I don't mind building myself if this is a limitation in the unified build or some other reason, but I just want to get the FM tuner working.

Thanks to everyone in advance!
[Samsung Galaxy S 5 Unified Development] fitittome:
New version of TWRP (3.2.1-0) has been released. Restore now works, apparently! https://twrp.me/samsung/samsunggalaxys5qualcomm.html
[Samsung Galaxy S 5 Unified Development] godofsalt:
Darn good info

Tanx
[Samsung Galaxy S 5 Unified Development] phalkon30:
Have you actually tried it on your device on stock? I doubt it's high on the list of things to look into (lots of work going toward Android O), but it would be nice to confirm that it could work on your device before developers put time into it.
[Samsung Galaxy S 5 Unified Development] fipsy:
[MENTION=8781358]O_oaa[/MENTION]: Are you really sure the G900P has an FM tuner? With the G900F, I'm pretty sure there was never an FM tuner inside.
[Samsung Galaxy S 5 Unified Development] jeremywh7:
klte and all the other Galaxy S5 LTE builds are released on Thursday currently (it used to be Wed.). The LOS build schedule is here and sometimes gets adjusted as devices are added/removed.
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
I had made a similar post to the following on the TWRP thread and was curious about it here regarding this and the last release of TWRP for the klte.

While in TWRP, If you select, from the main screen in TWRP, "Reboot" then "Power Off", and then turn on the device normally (with just the power button), the device boots into TWRP recovery.

I've got a feeling that this was not realized yet since just powering down in TWRP, followed by a normal boot, isn't a function that is used often in that combination.

Hopefully another member can also (Please) confirm this bug/issue?

Thank you very much! :)

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

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] fipsy:
I think it's always been like this: once you chose to boot into TWRP, it always boots the TWRP partition until you switch it to "system", which seems to be quite logical.
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
Please don't take this the wrong way but, what your stating is that when you select the "Power Off" option in TWRP and then the device Powers Off and, when you turn the device back on (via the Power Button only), the device automatically entering TWRP is Logical?

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

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] fipsy:
Smile :cyclops: It depends on the way you look at it. If you have initiated booting up TWRP from the OS, you could call it "switching to TWRP". Kind of like a switch you flipped. The switch must then be set back to "system". However, if you started TWRP by pressing HOME / VOL UP / PWR ON, I'd share your opinion that it's illogical. ;)
[Samsung Galaxy S 5 Unified Development] O_oaa:
According to this (ancient) thread post, some have had success getting it to work, but only for the G900P. I also found this (again ancient) thread praising Spring for keeping the FM radio in the G900P. I've tried out various MM stock images all afternoon, but so far I'm turning up empty handed. I'm downloading the G900PVPU1AND2 stock image now which is from around 05 Apr 2014 according to Sammobile. I'll report findings soon.

There's several threads that says it does, but only the G900P. There's posts upon posts for other models that don't appear to work at all. I'll keep digging.
[Samsung Galaxy S 5 Unified Development] fipsy:
[MENTION=8781358]O_oaa[/MENTION]: It is quite possible that parts of the G900P series have been equipped with chips containing an FM tuner. I suspect that the tuner is not its own chip, but is included in some other chip. I could imagine that Samsung might have been putting such chips in place for a while until they were used up.
[Samsung Galaxy S 5 Unified Development] O_oaa:
The Snapdragon 801 SOC has integrated FM radio, but it appears as if the International versions of the S5 (G900P being one of them) have it actually enabled/accessible. Thanks, [MENTION=7518817]cal002[/MENTION] for the chip clarification:

At any rate, I ran into issues downgrading to the 4.2.2 stock image (I think the bootloader is keeping me from flashing old images) and reflashed G900PVPS3CQC1. I also did a factory reset wipe from stock recovery before starting it up. Once booted, I reinstalled NextRadio v4.0.2198-release, and all of a sudden the Basic Tuner actually used the FM radio (with headphones connected)! No data, no WiFi, static on frequencies without broadcasts... The works!

Going to try to get SpiritF working, but I foresee issues getting it to play nice. All of the basic FM tuner APKs I've found are either uninstallable or FC immediately after opening. If anyone can point me to a good FM tuner app for 6.0.1 (and hopefully 7.1.2), I'd appreciate it. Juat want to find something other than NextRadio.

I'll try LineageOS 14.1 again when I can be sure I have a good backup. Depending on how things go, I might need some of the system libraries from the stock image to interact with the tuner.
[Samsung Galaxy S 5 Unified Development] huawei92:
still the twrp results with a bug, if you want to start the aroma gapps the installation is blocked and the phone will restart in recovery I hope that will solve with future versions.
[Samsung Galaxy S 5 Unified Development] cal002:
The FM receiver isn't part of the 801 SoC, it is part of the BCM4354 Wifi/BT combo chip. I.e. every S5 has it.

But it is useless if the antenna isn't connected, my assumption is that Samsung had difficulties to make it fit since the FM signal needs special routing considerations to protect it from interference (Cypress had published an application note about it). If Sprint made them do it, then it's good for the Sprint users.
[Samsung Galaxy S 5 Unified Development] fitittome:
Grrr: Just flashing stock (G900FXXS1CQI6_G900FPHN1CQI2_G900FXXS1CQA9_HOME) onto a 900F to check this radio thingy and Odin errors close to the end:-

<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>

I'm guessing one of the partitions is the wrong size. Any ideas?

Edit: PIT!

Solution: https://xdaforums.com/showthread.php?t=2716151
[Samsung Galaxy S 5 Unified Development] godofsalt:
Very nice edit! Dam good thing to know IMO.

TANX

---------- Post added at 02:07 PM ---------- Previous post was at 01:58 PM ----------

Short bit on radio. Yep, I have sm-g900p. In the binging, (2014)....

Yes, fact is did work at that time. I also if I can recall correctly, the FM Radio worked only though an app. Samsung or Sprint, at first had one. Also, let it be none, they both stopped working on it. In the frimware or 2, it was gone. Just like many other things, that make this phone Galaxy S5 Snapdragon chip, one of the best to have.

Ok back LOS...
[Samsung Galaxy S 5 Unified Development] fitittome:
Want to test it on stock. Can you put the .apk somewhere. I can't get it from the Play store on a 900F. Tried Yalp. :( Tried spoofing the device. :(
[Samsung Galaxy S 5 Unified Development] O_oaa:
Aye, thanks for the clarification - I'll go back and modify my original post. Trying to find the technical details about how this thing works has been... challenging but informative.

I'm 99% sure users of the G900F couldn't get it working (only the G900I/P appeared to work). However, I've attached the APK I used just in case.
[Samsung Galaxy S 5 Unified Development] fitittome:
Thanks. I can confirm that it won't install on 900F Samsung Stock. I wonder how it checks which device it is installed on?
[Samsung Galaxy S 5 Unified Development] fipsy:
The question is: What repartitioned the device? Did you ever check "repartition" when flashing with Odin?
[Samsung Galaxy S 5 Unified Development] fipsy:
You could also try SpiritF. ;) It used to work on my S3.
[Samsung Galaxy S 5 Unified Development] fitittome:
No but I think I recall that the LineageOS install fiddles with partition sizes.
[Samsung Galaxy S 5 Unified Development] javelinanddart:
Yeah, it looks like Sprint is the only one that actually had the antenna connected. My N900P on stock supports FM Radio wonderfully, and I'll be trying my G860P later. I have a soft place in my heart for FM Radio, but support for it is a hot mess, so we'll have to see whether or not it can reasonably be supported. There is no standardized interface for the support of FM (while a HAL definition does exist, no one uses it, it's incomplete, among other things). If I do work on this, it will probably be on O.
[Samsung Galaxy S 5 Unified Development] O_oaa:
Running SpiritF as a user app states it requires root to run, so I flashed UPDATE-SuperSU-v2.76-20160630161323.zip and wiped dalvik/cache. After reboot, I gave SpiritF root permissions when prompted by SuperSU, then hit the play button. After about 10 seconds of trying to start the tuner API, this message appears:

SpiritF 2015_03_17_beta
ERROR: Tuner API did not start or stop.
This device may need a kernel with a working FM driver.

I tried making it a system app by using TWRP to move the APK under /system/app/SpiritF/SpiritF.apk, but the app keeps crashing when I open it. Any suggestions? Am I using the correct SuperSU updater zip?

I realize SpiritF may no longer be in development, so it could be stock became more updated than the app as designed to handle.
[Samsung Galaxy S 5 Unified Development] fipsy:
This is an interesting piece of information and it fits with what javelinanddart wrote. If the kernel doesn't support the radio, it will probably not work...

Yes, it's ancient and not in development anymore as most phones do not support FM Radio anymore. I still use it on my old S3 with CyanogenMod 11 and the Boeffla Kernel.

If javelinanddart can't take care of this special purpose with the S5 kernel, you could ask Lord Boeffla if he would like to do it with his kernel. But I'm afraid not, because he has mostly stopped working on the S5 kernel.
[Samsung Galaxy S 5 Unified Development] fitittome:
WTF! is that. Why does it want root!
[Samsung Galaxy S 5 Unified Development] fipsy:
It's a very simple FM Radio. I used it for many years now on my S3. Don't know why it needs root but it works and is harmless.
[Samsung Galaxy S 5 Unified Development] fitittome:
It fails, just says it needs a kernel with an FM Driver which mine may not have.
[Samsung Galaxy S 5 Unified Development] fipsy:
It doesn't run on my G900F either. I only posted it for testing purposes. I wanted to add another app to the NextRadio posted by O_oaa. It proves that the kernel is missing the FM driver. :D
[Samsung Galaxy S 5 Unified Development] O_oaa:
So, NextRadio utilizing the hardware without these "drivers". Does it contain some device-specific libraries that is invoking the chip? I might need to do some spelunking either with the app or the stock ROM to find these features.
[Samsung Galaxy S 5 Unified Development] fipsy:
If Samsung has never had support for the FM hardware in the kernel / Stock ROM, it won't work with SpiritF. And then it will also be difficult to extend the kernel with a suitable driver. I don't think anyone wants to write their own driver. But on the other hand: If NextRadio accesses the hardware directly, why doesn't it also work with LOS on G900P? Huh?!
[Samsung Galaxy S 5 Unified Development] O_oaa:
Great question! I don't know, but that's what I'm going to try to find out. :cyclops:

I greatly appreciate everyone's input. More data points are always better than too few. Maybe I can get it working wit LOS, but that's a big maybe. LOS/CM has/had it working for other variants, so I'm going to dig around those branches and see what I can find. At least I have some direction now. I'll report back when (if) I figure anything out.
[Samsung Galaxy S 5 Unified Development] cal002:
It pokes directly at device drivers, something that apps shouldn't do. It's a gross hack.

A stripped down open source version of SpiritF is on github.
[Samsung Galaxy S 5 Unified Development] uVSthem:
Is anyone else having problems with their screen not auto rotating after installing LIneageOS? My screen rotated fine using the standard rom that came with my phone.
[Samsung Galaxy S 5 Unified Development] fitittome:
I have two motherboards with dodgy gyros and now two phones where they intermittent. I have concluded that these sensors are failing as the phones get older. I use this app to test. https://f-droid.org/packages/com.mustafaali.sensorssandbox/

As a side note. I think I have noticed that if the device is configured to auto-rotate in LOS, then you reboot into TWRP (3.2.1) goto Advanced in TWRP then choose rebbot, system. Auto rotate then works. I'm not saying this 100% reproducible but something I have noticed, thought wtf, I need to look into that, then got distracted. In fact, I have just done this on my current device (with what I thought was a broken gyro) and it now works! then after typing this it went to sleep and now it doesn't! Dodgy gyro or bug? idk.

edit: just tried the TWRP trick again and gyros didn't start to work. :(
[Samsung Galaxy S 5 Unified Development] uVSthem:
I tired the TWTP thing and it didn't work for me but the problem you described is similar to mine. Sometimes after rebooting the auto rotation will work for a few minutes and then just stop. Definitely a bug and not an issue with the phone's hardware.
[Samsung Galaxy S 5 Unified Development] fitittome:
I don't think you have proof! I thought the same, a year ago. I recall my [MENTION=5110154]fipsy[/MENTION] like insistence got me 'shouted at' by [MENTION=2693412]haggertk[/MENTION]. :o I am more cautious nowadays! ;)

I have go as far as reinstalling Samsung Stock and the gyros were failing there too. It is horrible because I believe they fail in an intermittent way. Anyway, try out different things. Try and get something reproducible, once you have that get a logcat. Then progress can be made.
[Samsung Galaxy S 5 Unified Development] fipsy:
I wouldn't want to make a definitive statement on the subject. I had the same problem twice within a week using the latest kernel from fbs. Before and after that, I never had it again. That's why I tend to think that it's a software problem. I would therefore recommend to try a different kernel. For example, the Boeffla.
[Samsung Galaxy S 5 Unified Development] fitittome:
My gyro worked once with the Boeffla 4.0 stable but after a sleep it wouldn't work again. So I installed the Boeffla 4.1 beta 19 and the gyro didn't work at all. Dodgy gyro or bug?
[Samsung Galaxy S 5 Unified Development] paulcarroty:
New build - 20171214

https://mirrorbits.lineageos.org//full/klte/20171214/lineage-14.1-20171214-nightly-klte-signed.zip
[Samsung Galaxy S 5 Unified Development] fitittome:
Uh? :confused:
[Samsung Galaxy S 5 Unified Development] fipsy:
Maybe both is possible. It could one day be a software bug and another time a hardware problem.