On Wed, Aug 18, 2010 at 12:23 AM, mot12 <martin.hu...@gmail.com> wrote:
> That would be the case if the alarm service broadcasts the intent and > no wake lock is acquired. > The platform does hold a wake lock while broadcasting an alarm, and always has. > I was talking about a different situation in which the broadcast of > the alarm intent doesn't happen at the designated time because the > device is in some funky state. The broadcast happens later, when the > user manually turns the display on. (After that, the receiving app > should, of course, acquire a wake lock to process the alarm action but > that is not a problem if properly coded). The problem is that the > broadcast of the alarm intent does not happen at the time for which > the alarm was set (otherwise I would see it in the logs, correct?). > And that is a major problem for alarm clocks. > This is exactly what you will see if someone is not holding a wake lock when they should. The CPU goes to sleep, and won't run again until something else wakes it up and holds a wake lock. Turning on the screen on does this. > All users have reported that the problem goes away if the phone > remains plugged in. > Often having a device plugged in will cause a wake lock to be held for the duration. Definitely, having the screen on (such as when the clock is displayed while in a desk dock) will keep a wake lock held. -- Dianne Hackborn Android framework engineer hack...@android.com 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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
