12/20/2012, 09:03 AM
I'm about a week into my new Pre3 and I am using the Screenstate reduced CPU freq setting in Govnah+UberKernel to reduce my battery usage when the screen is off. I have the maximum freq when the screen is off set to 245Mhz. It seems to me that this setting "breaks" the Alarm feature on the phone. My alarms don't go off on-time. So, far, they've never gone off on time, and they've ranged from going off 2 minutes late to 10 minutes late. If I use Govnah and set a profile that does NOT reduce the CPU at all (i.e., keeps it at 1.4Ghz), the alarm goes off on-time.
Is this normal? Do other people have this issue? It makes intuitive sense that reducing the CPU means it's going to take longer for things to happen (i.e., callbacks to fire, timers to increment, etc.), but this will be quite annoying and force me into a touch decision on battery life versus expected functionality.
I haven't done enough testing to determine the exact freq at which the alarm will still go off on-time, but I will look into it and post the result here.