> On the other hand, if you are saying the alarm broadcast simply never > happens, even once the device is turned on... that is a very different > problem then any I am aware of. That is not a problem with the device > sleeping at all, but simply some issue with the alarm getting lost. You can > use "adb shell dumpsys alarm" to look at the currently registered alarms to > see if your alarm is actually there. During development we have had bugs > with alarms getting lost, but those are typically very obvious and get fixed > before release. I am not aware of a final versions of the source having > such a bug. Note that the "force stop" operation that task managers abuse > also removes an application's alarms.
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. Martin mobitobi Gentle Alarm Sleep Now -- 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
