On Fri, Apr 22, 2011 at 2:02 AM, Zsolt Vasvari <[email protected]> wrote: > You MUST > start the alarm when the app starts, so it can recover from Force > Closes or for whatever reason the system decides to terminate it, but > once you do that, you can get yourself into a cycle where you end up > never firing the alarm if its period is long enough.
The only scenarios that get rid of scheduled alarms that I am aware of are: -- Pre-2.2 task killers -- reboots -- upgrades of your app I have seen no evidence that a crash in your app, or Android shutting down an everlasting service, has any impact on scheduled alarms. If you have evidence to the contrary, I'd love to see it. The pre-2.2 task killers is still a big-time annoyance today, and definitely could cause problems in your scenario. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training in NYC: http://marakana.com/training/android/ -- 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
