When I use the method above. Even after I kill my app and service with task manager my alarms still trigger. I believe its because the AlarmManager service has been given a pending intent that will relaunch my service which handles the alarms.
Both alarmmanager and the pending intent are allocated outside of the activity, so even if the application's virtual memory space is deleted, the pending intent still exists and the alarmmanager is still scheduled. Sorry if I missed the theme of the post. Good luck :) On Oct 15, 11:53 am, String <[email protected]> wrote: > On Oct 15, 4:34 pm, "Jason B." <[email protected]> wrote: > > > Using that approach works great for my app. That way it doesn't > > matter if my app ever gets killed. The alarm will trigger in the > > future and the intent will restart my service > > I believe the point of this thread is that Task Killer apps will kill > all future alarms you had scheduled. > > String --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
