AuxOne wrote: > Then maybe it's the Service that is dependent? All I know is it works > after reboot, but not after immediately installing (and starting Alarm > from Activity). It's a 1 hour+ timer.
Like I said, I am not aware of any such limitation. As I wrote, the only times I know of when alarms get nuked are: -- on a reboot, all alarms go "poof!" -- if the user has a so-called "task killer" app and kills your app that way, your alarms go "poof!" (though alarms from other un-killed apps remain in place) Conversely, there are places in Android itself where AlarmManager is used from an Activity -- alarm clock and calendar, to name two. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.0 Available! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com 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.
