On Aug 17, 12:25 am, mot12 <[email protected]> wrote: > The alarm service has many pitfalls but even if programmed correctly, > it doesn't work reliably on some devices. The standard alarm clock > doesn't run reliably on those same devices; that's a strong hint that > something is wrong.
We've had similar discussions a while back here. At least how I understood it, the skinny was that services can become victim of Android's efforts to manage resources and that that's the way it's supposed to work. In that sense, things are perfectly fine. It's just that implementing alarms seems like a bad idea. I've since backed off from including features such as alarms (secondary to my apps) or dynamic app widgets (suffer similar fate), because they seem impossible to support, at least at this point. -- 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
