I've a RAZR MAXX, rooted, with ICS.
I installed SetCPU yesterday and, early on, marveled at increased battery life.
However, with my phone in full view and screen off, I - randomly - see the screen blip on then off again.
The IN CALL, NOT IN CALL, and SCREEN OFF profiles are set to "hotplug" for the governor, and "not exclusive". Every other profile below those is exclusive and those pertain to battery life levels (50% or lower) or game/app settings to ramp up the CPU when desired.
Only NOT IN CALL is set to 600/300. The others (IN CALL, SCREEN OFF) are set to 300/300 to keep power usage way down. Could "SCREEN OFF" be too slow, prompting random waking up/re-sleeps blips?
I did try, for the governor, "interactive" and "ondemand". Those had no effect.
When the screen does blip on and I catch it, the top left corner of the screen in the top bar shows the icon of a CPU for a brief moment - it's the only suggestion that would add weight to the problem emanating from SetCPU.
I've looked at SetCPU's help page, but there's not much there.
Granted, there could be a bug so I might contact them as well -- but if you've had similar issues, please chime in.
Thanks!
I installed SetCPU yesterday and, early on, marveled at increased battery life.
However, with my phone in full view and screen off, I - randomly - see the screen blip on then off again.
The IN CALL, NOT IN CALL, and SCREEN OFF profiles are set to "hotplug" for the governor, and "not exclusive". Every other profile below those is exclusive and those pertain to battery life levels (50% or lower) or game/app settings to ramp up the CPU when desired.
Only NOT IN CALL is set to 600/300. The others (IN CALL, SCREEN OFF) are set to 300/300 to keep power usage way down. Could "SCREEN OFF" be too slow, prompting random waking up/re-sleeps blips?
I did try, for the governor, "interactive" and "ondemand". Those had no effect.
When the screen does blip on and I catch it, the top left corner of the screen in the top bar shows the icon of a CPU for a brief moment - it's the only suggestion that would add weight to the problem emanating from SetCPU.
I've looked at SetCPU's help page, but there's not much there.
Granted, there could be a bug so I might contact them as well -- but if you've had similar issues, please chime in.
Thanks!