It doesn't hold a wake lock... and unfortunately to correctly use a wake lock with the alarm manager, you need to have the alarm delivered to a broadcast receiver. This is something that we'd really like to improve.
On Sun, May 24, 2009 at 8:21 AM, Mark Murphy <[email protected]>wrote: > > The new IntentService in Android 1.5 looks excellent for handling > AlarmManager-initiated broadcasts for scheduled WAKEUP work...except I > can't see that it uses a WakeLock anywhere, either in itself or > Looper/MessageQueue. > > Does this implicitly hold a WakeLock that I'm not seeing? Or would I > need to create a WakingIntentService that has an active WakeLock so long > as there are messages in the queue? > > Thanks! > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://twitter.com/commonsguy > > _The Busy Coder's Guide to Android Development_ Version 2.0 Available! > > > > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
