[Sprint Samsung Galaxy S III] mw86:
I believe you haven't had any reboots and problems on your volts while using yoir phone day to day. One thing i have also noticed is the average voltage can be a bit lower if one doesn't overclock ie default max or less on the mhz and the cpu from that seems to withstand lower voltage during changes while scaling. Say 96-2106mhz. 96mhz is going to handle on some phones only at a smaller undervolt than using a lower max frequency. It seems the transitions can be so fast in scaling process that voltage of the higher frequencies doesn't end up being enough voltage by time it changes or in haw fast it was applied before the higher mhz was used, in anycase side effects are usually a reboot or app closing to home screen are or apps stating they crashed that never have problems when one of them was too low. If a volt is off by a little mostly just heavy apps may close to desktop or tasks quickly waking from idle from idle mhz at low volts.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2

---------- Post added at 02:24 AM ---------- Previous post was at 02:08 AM ----------

Guys two big suggestions before diagnosing issues on battery drain try only draining down battery when not plugged in charger and when its time to charge make sure not to really be using it maybe turn a few unneeded radios or clear ram quick on task/recent apps screen and let it charge straight to full give it a hour or so extra at one hundred percent if you can. The charging mechanism stops it at one hundred but immediately after charge it will drop very quick ln battery if you remove charger and check. If left longer at one hundred plus the above tip you should get a fuller charge out of the battery. The volts keep rising after one hundred to even out at the actual nominal voltage of the particular battery one may have. The thing that helps the above tip is that the charge drops a few times at one hundred enough to start charging again and fully fill the battery's capacity. No need for hours after one hundred just even one will do. One other tip i read and forgot which thread, if charging is clearly going slow simply unplug charger and plug ot back in and if ot was in fact charging slow it seems to start charging at the normal fast rate again.

Anyone with a aftermarket or extended battery its just as important in fact more important to be sure you let the charging occur for long than hitting one hundred percent if you want to be getting the full capacity of the battery. Use a app if necessary to see that the battery voltage rests at the proper voltages and mah at full capacity if concerned.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2

---------- Post added at 02:53 AM ---------- Previous post was at 02:24 AM ----------

:) you talking about core one or two :)

If your on ktoonservative and using tunables that have a high number in up threshold it holds back more so on raising core ones cpu frequency so only raising when load is too much for the cpu to calculate at the used frequency without hitting the cpu load in the up threshold (which is for raising mhz). Core two activity which only a few apps show frequency of core two as core two will ramp to max frequency as needed but usually more often when core two is on as it has its own governor tunables which are not adjustable by amy of our means. Cpu spy doesn't show core two activity so the mhz isn't tracked. Core two when its on is on demand based so any load applied to core two hits a low observed up threshold of 25-50 it seems at a low sample rate and depending on min max ive seen mine set to 96-2106mhz scale core two as 96 486 1000mhz 1500mhz 2106mhz. Not the exact then scales down but hits diffrent mhz on way down.

So almost a 15-30% frequency step on core two. This all happens at the governor sample rate or quicker i believe in any scenario core twos own governor tunables have a fast sample rate so a low number from 10-40k sample rate likely. So core two turns on and off based on governor hotplug settings and once ona nd a load applied tl core two it has its own settings that cant be adjust governing its speed and it always easily hits whatever is set in max frequency easily, many times a second in most cases but core two always takes half or less on cpu load unless irregularly forced or both cores are full its not loaded heavy and as a result core two takes less energy than core one since core one takes workload consistently no matter if core two is active. Core two saving power especially if only active for a couple 10-40ms in a whole second and even at max cpu speed that statement follows.

If core one wont max out under obvious heavy load uncheck lock min max, toggle overclock box and set max again and lock frequency again. Sometimes it takes a toggle of them or two to get the desired effect of bekng able to hit cpu frequency max that was set over 1500mhz.

Don't forget guys frequency step in Ktoonservative governor is relative to the minimum and maximum frequency you decided to choose. Too high you wont hit frequencies between min max and too low the cpu will not even scale up or down from the frequency its on at the time governor tunable is applied.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2