When I cooked up interactiveX V1 (for other phones), I took Mike Chan's interactive code, optimized it for the phones, and then added early_suspend support (screen-off/on trigger). I then added logic to the code so the governor does not scale higher than a certain frequency when screen is off.
With interactiveX V2 (for gnexus), things are a bit different, since gnexus has built-in support for screen-off-max-freq for all its governors. I took the new interactive code in gnexus, added early_suspend support (screen off/on trigger), and then added logic to the code so the governor uses the phone's built-in hotplugging capability to turn off cpu1 when screen is off (and then turn it back on when screen comes back on). Cpu1 goes offline entirely - no idle, no sleep.
You can see this in action if you traverse /sys/devices/system/cpu on the phone.
stickjohnsonaah, on 28 December 2011 - 03:11 PM, said:
Just looking for interactivex governor breakdown. Is it interactive governor with built in Max clock speed for screen off? <br /><br />Hot plug is 1cpu turn completely off during screen off sleep?<br /><br />I read through the xda post on governors and couldn't find them all listed. <br /><br />Sent from my Galaxy Nexus using Tapatalk
Edit: I also saw mention of not going above 1400 because it is not stable. For those that can run 1420 fine would you be able to add or change a slot to 1500 in an experimental versions so we can see what ours tops out at? Is it really silicone limiting our CPU frequency?
Edited by imoseyon, 30 December 2011 - 11:30 PM.