Thanks. I'am using the AlarmManager to send PendingIntent.getService with a "Explicit Intent" to an IntentService.
Read this post from July 2008: "The "Alarm Service" sample code in ApiDemos at http://code.google.com/android/samples/ApiDemos/src/com/google/androi... is intended to provide the best practices for this. The current example is a little overly complex because of the need of the intermediate receiver. In a future SDK where you can have the alarm manager directly start a service, this is a lot cleaner." On Nov 11, 1:10 am, Mark Murphy <[email protected]> wrote: > On Wed, Nov 10, 2010 at 7:00 PM, Henrik Lindqvist > > <[email protected]> wrote: > > I've read comment that the AlarmManager in a earlier API version > > couldn't start services. Prior to which API Level was that? > > I don't know where you read that. PendingIntents have been able to > start services since the beginning. > > I am a bit nervous about how WakeLocks work when starting a service > directly versus going through a BroadcastReceiver, but otherwise > AlarmManager starting services works like a champ. It's great for app > widgets, if you have an IntentService that is doing the updates and > you are controlling the update schedule yourself rather than using > android:updatePeriodMillis, for example. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > _Android Programming Tutorials_ Version 3.0.1 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 at http://groups.google.com/group/android-developers?hl=en
