[Sprint Samsung Galaxy S III] mw86:
I think in having lower up thresholds i have seen a very similar efficiency of racing to idle if needed. I think yours in fact has a better battery life simce it may help avoid higher frequency. I still am trying to lean into the work load myself and prevent workloads as high as 75%-100% as possible by turning on core two early and then only as necessary raising cpu frequency. I still figure kind of like i think you do that utilizing core two ahead of the curve is better than raising speed and just one execution core even though dmservative turns core two on at medium high loads its not utilizing the efficiency in most cases multi core presents. Its not like we need four cores on our phones like the exynos cpu in the international version. Two cores are enough but shouldn't be waisted. If Ktoonservative can compensate for needs of constant load and unnecessary use of upper frequency it may be just perfect. Its not easy to do in any case on any governor to balance performance and battery or even enhancing one. I think though that if you enhance performance but filter the need to ramp to max limits and only use max when its to much for known efficient ranges... then should we see boost to the max speed we prefer to as quick as possible get cpu usage down to ranges preferred in the first place... like what you would use just doing mundane tasks.(sending a message, browsing a basic webpage) I think its very important if usage gets out of hand to race to the target frequency. Idle isn't always an option but it helps if core two is off in scenarios that cpu is just calculating mundane basic tasks like media. As long as up threshold hotplug is high enough and cpu frequency up threshold is lower than that Ktoonservative is tuned to be conservative and save battery. Core two also shuts off if cpu reaches the lowest or second lowest cpu speed. I think both governors have merit and Ktoonservative as is is able to fit many scenarios. Changing sample rate and even how far between up and down threshold can make a big difference. The larger the span though the more likely the workload is to be finished before changing speed or core status and more fit for the required amount of cores active and or speed needed. Still core two being used is important to finish many threads faster. Two jobs at one moment vs one is faster then most frequency increases. I think yes there is a method to the madness. I also think there is merrit in getting to these idle, sleep etc states quickly when it is possible to complete a job. I think no matter how much we observe and read it always will be jard to have all aspects covered. If one of these governors could maintain about a quarter or half max cpu speed most times and blast max speed at a workload at any other cpu usage other than that it would be perfect for speed and battery. We need not have max speed pop in but any heavy workload that pops in and would take awhile a lower speeds or core counts then that workload in the end could possibly draw more power than if more.cores or more speed was applied to finish faster even knowing more speed more core raises power draw in itself.

Decimalman when i was using your kernel file i flashed even after rebooting and being returned to your stock settings my phone was freezing up and having problems. It was from your settings of when to ramp up or down on your dmservative but seemed like it was not made to be used. It didnt have the other governors working example performance gov was not staying on max but acting weird like a on demand that wasnt working. I rebooted after a freeze and again after third time i ended up flashing a rom update for paranoid android and the stock latest Kt747 aosp version again. Maybe your version had trouble with my rom, gapps version... who knows its not a prob. When your governor did work it still seemed to act like my tunings on Ktoonservative at times often hitting 1500mhz anyway. Still i think that is tge path in the end to power savings... run a certain range based ln usage or a target usage and if load is over an amount throw all you can at it to return to its previous state or in both cases if and when possible idle, sleep or whatever core state they can get too.

I think all governors have a bit of work to make them any viable a solution. I wish the best of luck too to Decimalman and perhaps I will try out a more refined version later on. For other the kernel posted may have worked but the kernel itself was not functioning correct kn my phone. Perhaps it was missing commits on your phone only. It did allow me to try your governor though. When i did have it function I noticed it went back between those freqencies mentioned a lot but seemed to delay performance when tested on benchmarks. Testing should reveal a similar score on an average of a few tests under the same settings. Your governor did but perhaps from a simple compatibility issue with my rom or something scored pretty low on cpu side vs my ktoonservative settings... The revised above and Freechalres mansons he posted. I am not saying any is better, I am pointing out there was a serious performance issue and im not sure where it came from. The theory makes sense on the description of your governor. Thank you for taking the time to explain its way of judging needed speed or cores. I think my issue was your experimenting with newer versions of ktoonsez ghub commits and somewhere there in my phone was not happy with it. If you post a revised version ill still try it out. This was using a kernel cleaner and wipe caches and fixed permission in recovery. To be sure the message is conveyed, your governor has an interesting premise and I hope to see how it progresses but from the start to attain your goal you will as you have mentioned will have to look into performance to save cpu time. 5-10min at max speed should still be better than 20-30 min at low to medium speeds.(as long as cpu speed max doesnt draw a few times more power per second) the same should go for multi core as in two cores at low or high speed will almost always out weigh completing the task with just one core. To consider... max load on any frequency often can pull more power than using a cpu speed on the same conditions that pegs cpu under max load. Max load can lead to more power draw and more heat. Its not easy but its important to consider all factors and all i have mentioned may not be the whole picture or answer to anything or everything. It certainly has to do with how it works though. We are seeing more use on ktoonservative over time in lower frequencies instead of high. The job gets done and core two shuts off and either core one shuts off at idle or cpu calculates backround tasks at minimum speed and in single core mode. Most times over a long period ive monitored how my phone idles and runs 96-500mhz were the most used speeds at idle or just above. 1500-2106 were for all other scenarios and very short times since it would get right back to the 96-500mhz range. Over past day ive not minded the way the Ktoonservative governor runs on the pictured settings.

Paranoid Galaxy S3 on Tapatalk 2