It just occurred to me that if I create it from a static context it shouldn't really die with the Activity. That's what I used to be doing, but later I switched it to an instantiated class. I'll see what happens.
On Mar 27, 9:12 am, AuxOne <[email protected]> wrote: > I'm starting the AlarmManager from a BOOT_RECEIVED broadcast and it > works like a charm. I've noticed, however, that it requires a restart > to take effect because it's triggered from a broadcast. In light of > this I also start the AlarmManager from the onCreate() of my activity > so that the user doesn't have to restart their phones, in this case it > doesn't really work. > > I've read that Alarms/Services set from the Activity are destroyed > when the Activity is. Is there some way around this? Perhaps have the > Activity bounce a Broadcast off something such that the Service is not > directly created from the Activity and thus doesn't get destroyed? > > Thanks -- 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 To unsubscribe from this group, send email to android-developers+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
