On Tue, Aug 17, 2010 at 10:12 AM, mot12 <[email protected]> wrote:
> Thanks for weighing in, Dianne. I misspoke: Actually the alarm > broadcast happens immediately after the display is turned on. But that > may be minutes or even hours after the time for which it was > scheduled. So that has nothing to do with the wake lock since that > would come into play only after the alarm broadcast was received. > That exactly has to do with a wake lock. If the alarm goes off, and no wake lock gets held, the CPU will not run. If nothing else happens to acquire the wake lock for those hours, no code will run. It is only until a wake lock is acquired (which happens when the screen is on) that the CPU can run. Then the question is what code is not holding a wake lock and allowing the CPU to stop running: the kernel driver, the platform's alarm manager impl, or the application code when it receives the broadcast and is doing its resulting work. -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
