That would be the case if the alarm service broadcasts the intent and no wake lock is acquired.
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. All users have reported that the problem goes away if the phone remains plugged in. -- 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
