I had thought that it was something to do with the alarm manager because moving the call seemed to fix things. Turns out things are actually still broken. Now I'm checking to see if moving my function from Service.onCreate to Service.onStart fixes things. Seems to work so far except that it can't connect to the internet when the phone first wakes up.
On Nov 20, 1:04 am, "Dianne Hackborn" <[EMAIL PROTECTED]> wrote: > The alarm manager knows absolutely nothing about activities, so this would > not be the normal behavior. It certainly works fine in other places. > > > > On Thu, Nov 20, 2008 at 12:46 AM, songs <[EMAIL PROTECTED]> wrote: > > > Is the following behavior documented somewhere and I just missed it? > > > When I set a repeating alarm in response to a button click, the alarm > > triggers the expected event only if the activity is in the > > foreground. If I close or pause the activity, the alarm seems to > > disappear. > > > When I set the same repeating alarm in the onPause method, the alarm > > triggers as expected even after the activity is destroyed/paused. > > > Is it just me, or does this seem like it's not behaving the way it > > should? > > -- > Dianne Hackborn > [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
