On Mon, Jun 13, 2011 at 5:21 PM, Simon Platten <[email protected]> wrote: > Ty, makes sense I guess, but then how does the alarm clock keep its > scheduled alarms? > I'm sure that no alarm clock is running or at least it does appear to be...
Correct. A user can only task-kill or force-stop you when your code is actively running. That's what you did to your own app, and it nuked the scheduled alarms. One imagines that if you do the same to the alarm clock app, it would have the same effect. The alarm clock app's code is only running around the time the user is setting an alarm or when an alarm is occurring. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Warescription: Three Android Books, Plus Updates, One Low Price! -- 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
