[Sprint Samsung Galaxy S III] mw86:
E=freecharlesmanson;31080488]What you are shooting for is the opposite end of the stick so. Getting the same results off a diametrically opposed idea is awesome keep it up

thanks bro! you too! your work is very interesting and this governor is very unqiue. I realized after more reading the freq step is a percent. where I thought it was the amount of cpu bins being thats how computers run cpu. now i get it. I'll keep tinkering. The config as before is very performance oriented but needs a lot to get it to save juice and not ramp up core 2 when uneeded. So i am sure i will need hotplug very close to the up threshold. You've taught ght me a lot thusfar and I use this for reference too.

http://xdaforums.com/showthread.php?t=1369817

Edit: today's adjustments I'm trying are as follows

SAMPLING_RATE="13500"

UP_THRESHOLD="49"

DOWN_THRESHOLD="25"

FREQ_STEP="2"

SAMPLING_DOWN_FACTOR="1"

IGNORE_NICE_LOAD="1"

UP_THRESHOLD_HOTPLUG="51"

I saw what you mentioned and see having hotplug above up threshold is probably good to prevent core two from activating unless load is greater than about 100% one core or 50% dual core. It doesn't activate core two as much now and with other adjustments it ramps up or down faster than my previous settings. I have frequency step at 2% but may set 3% if you think going over target percent is better. Target percent being about 2.5% for me. Here how I figure that, does it seem to be accurate? 2106mhz max for me 96mhz min. (I don't get lag from using 96mhz step if governor is set good) so 2106-96=2010mhz from min to max range. 50mhz is the smallest frequency step between some of the available frequency steps... 100mhz for some. So i did 50/2010=. 02487 ~2.5%.

If up threshold is way to high I see it won't even switch frequency unless under a extreme load. I noticed having hotplug at 100 maybe little less will keep it from even activating unless at max speed and full load still assuming the up threshold is set lower than the hotplug. Hmm still watching and tinkering. I see lazy theory may be not a good idea as its based on a minimum time in state and this governor doesn't use that. If I attempt to emulate that it's just going to be laggy. So instead I think fast response up and down will save juice just as well since the most energy we can save if we are not limiting the cpu a lot is having it use the best suited frequency as fast as possible and finish work ASAP so speed can drop to idle once again. Where as if I make it more LAZY its going to lag and possible use more power if it has to stay in a state of calculating much longer. So i see as you said using two cores will always take more power and at the same time max speed vs a lower dual core speed can also take more power. Ie like 2106mhz single core at 1350mv vs two cores at 1500mhz at 1200mv stock volts I'm guessing the way it works the dual 1.5ghz may save more power and accomplish more than the single core running faster. Same can be said for the opposite dual core can save power or use more vs single core at higher speeds. So priority is raise speed but not to max just enough for the work load and if load is going over the speed threshold the second core will finally activate. The requirements is set to hit each frequency may save juice as well as the hotplug over the up threshold. I was going to use 45down threshold and may still but I wanted to know what you think. If I set down threshold lower like I did it seems it may stay at a set frequency more often rather than dropping the moment speed is increased and therefore not finishing the load optimally if it's bouncing speed up and down. So I'm hoping that down threshold will make the cpu finish what's its doing more at same speed before deciding its done and idling back.

Funny I keep pushing in different directions. Have you been using the same settings still you posted in the OP freecharlesmanson?

Edit2: okay watching behavior is see its not necessary for down threshold to be that low. I pushed it all the way up to 45 and the rest the same and seems to be better at saving power now since the rest of the governor settings I've leaned greatly towards performance other than hotplug which is a balanced value to keep the need for max frequency down. I'm tooling in Chrome and with the new down threshold I see cpu getting calculations done and quickly dropping back down spending less of the unnecessary time in upper frequency states. That's it for now.