[Sprint Samsung Galaxy S III] mw86:
On Ktoonservative with even wjth agressive ramping with up thresholds under the 50% mark and even using 2106mhz which drains more juice on AOSP i have made out decently. Im still trying to cutomize my own myself. Its still Ktoonservative just different tunables for me. I find I like the way hotplugging works in Ktoonservative. I had going on 8 hours screen time on a -50mv undervolt so less of an undervolt than the voltage table above and 1 day 8 hours on.

http://xdaforums.com/showthread.php?p=33485996

I moved to even more aggressive thresholds since then and I am experimenting with how its been written but not investigated enough how performance governor gives the fast race to idle and in some ways could be superior in powersavings to many others. This though is theoretical and its positive or negative impact is directly related to the used max frequency and also the voltage used. So I also took interest in Ktoonservative from the beginning, performance, wheatley and also Min Max governor. Each a different theory on the race to idle by meeting load head on. Essentially tackling load with the full throttled approach. What i find is if the max frequency and its supplied voltage is kept to efficient values like most use in other governors, this type of governor provides excellent battery life and almost as much if not indistinguishable performance from the actual performance governor.

Ive been tinkering with it more recently in that type of config. I decided based on that info I want to scale not based on load to a target frequency as mentioned in the post above its helpful not needing to jump through frequencies. At first i did not see this but used Ktoonservative with frequency scale of 3% on 96-2106mhz. Watching cpu spy for my frequency range it would hit each frequency in between. To combat the delay of that i had set as low a sample rate as I could. But even at 10000 (10ms) scaling through 15-20 frequencies means if a load only suited for max frequency hits youll need 200ms to reach it. In computer cpu terms thats ages and more resembles conservative and traditional dynamic governor.

Next i tried a scale frequency percent around 25% which isnt a bad idea i witnessed it use from 96-500-1000-1500-2106 or a 100mhz or so over those intervals. It scaled decent and stayed at a frequency more often but did not suit the load as well as going through the frequency more. So i moved to 50% essentially 96-1000-2106mhz. The performance improved drastically from the first config to 25% more so at 50%. Using lower up thresholds made it respond to load much closer to how performance governor is already primed and ready. So to get as close to that as possible im am now playing around with 100% upscale. Running minimum frequency when idle or barely loaded on backround tasks and max under the load. It gives benefit of performance but powersavings and cooler temperatures of dynamic governors. It has hotplugging so it save power on idle. I have hot plug up threshold lower than frequency up so core two uses minimum frequency dual core first before upscale in case while idle that may prevent upscale. So essentially Ktoonservative tuned as a Min/Max governor with hotplugging and low response times to race to idle as fast as possible and save juice as soon as being idle is possible. Using a lower max frequency then 2106mhz would prevent extreme drain so using as above 1500mhz would do fine as a max. To mention wheatley also uses max frequency when possible and at a lw sample rate for quick response time but with up threshold for wheatley defaulting at 95%.

One issue i had with a 95% up threshold is from complete idle i can witness thread one get fully loaded but core 2 was on at the time, so essentially the percent used to say up the frequency says 50% (1 thread out of 2 fully loaded) and would stay calculating at 96mhz. So in this extreme performance governor im trying to manage I keep frequency up threshold at under 50% so that if dual core is still enabled at any given point it wont prevent upscale. The above governor being made DMservative doesn't have that one issue by design. Essentially the way I set it though hot plugging only occurs once you hit idle frequency or one above that step. Since dual core will always finish faster as single core at lower speeds and using max frequency in a performance governor is fastest to idle i tuned it to turn on dual core early and hopefully finish workloads single or dual core asap.

What ive been tinkering with is not for those worried of battery life though. My current work and early work gave good battery life anyway as a result of finishing workload sooner.

As mentioned im am still tinkering.

Ktoonservative (min/max, wheatley, performance, hot plugging, dynamic governors)

96-2106

Up thresh frequency 49%

Up threshold hot plug 25%

Down Threshold 12%

Scaling percent 100%

Sampling rate 10000 (10ms)

Sampling down factor 1

Ignore nice load 0

Most times i have a screen off profile with 486mhz max.

Hey Freecharlesmanson hows it going?

Paranoid Galaxy S3 on Tapatalk 2