On Thu, Jun 17, 2010 at 6:40 PM, Onomp <avtsolution...@gmail.com> wrote: > Are you saying that the alarm is still registered but that it does or > doesn't fire with or with out the WakefulIntentService code?
I am saying alarms registered by a BroadcastReceiver work, despite the fact that the BroadcastReceiver component is destroyed after onReceive() ends. This is true for all Android components -- the component that registers the alarm does not need to remain running for the alarm to occur. I am also saying that you can see this effect in action by looking at the WakefulIntentService demo project. > also., I use system panel to check what is running... There is a way > to have my service out of memory and the alarmmanager still > triggering?? Yes. That is the whole point behind AlarmManager. > when I end the actie, background,inactive tasks... its > typically game over for my alarm manager. Then quit using a task killer. Task killers are the exception to the rule, and those too will start to behave better starting with Android 2.2. If you wish to test terminating your process forcibly, use DDMS. Do not use a task killer. -- Mark Murphy CommonsWare mmur...@commonsware.com http://commonsware.com -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to android-disc...@googlegroups.com. To unsubscribe from this group, send email to android-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
