Well, I had done that. I just required the broadcastreceiver to start the alarm manager only when the phone rebooted...
For rest I didnot use the broadcastreceiver but I started the alarmmanager from the app. On May 25, 1:12 pm, Mark Murphy <[email protected]> wrote: > nikhil wrote: > >http://github.com/commonsguy/cwac-wakeful > > Actually, he's seeking an answer to a question that I couldn't answer > (at least not without more experimentation). > > My implementation uses a BroadcastReceiver to get the WakeLock and start > the WakefulIntentService. > > The OP is wondering if we can skip the BroadcastReceiver, and just have > the AlarmManager invoke an IntentService directly, with the > IntentService grabbing the WakeLock in onStartCommand(). > > Personally, I am nervous that this might be too late, and there might be > a gap where there's no WakeLock in force, so the phone may fall asleep. > However, I don't know that for certain. > > Has anyone experimented with WakeLocks and IntentServices, besides my > WakefulIntentService? > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > _The Busy Coder's Guide to *Advanced* Android Development_ > Version 1.5 Available! > > -- > 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 > athttp://groups.google.com/group/android-developers?hl=en -- 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
