Whyzor
Android Expert
Thanks for the info. Smartassv2 should be fine nothing was changed for that governor between the two versions.
It was only Interactive using the new code from CM that seems to be having an issue.
And if you're charging, I wouldn't expect the phone to go into deep sleep. Pretty much any time that you have you're phone hooked up to something, I wouldn't expect it go into deep sleep.
Right, deep sleep is not possible when charging. It's only available when screen is off. When screen is on and nothing is happening, it should be at the min freq. When processing (buttons pressed, things happening), it should be at max (or close to it) to get it done as quickly as possible so it can ramp down to save battery again. I find smartassv2 spends too much time at the higher freqs even when nothing is going on. (It's very slow at ramping down compared to interactive, interactiveX, or even ondemand).
I think right now my favorite is classic interactive with 20ms check intervals & 95% ramp-up threshold (old algorithm, newer timing).