pperotti wrote: > Hi Everyone, > > Can anyone give a hint if you know why there are some ACTIONS that do > not trigger their associated receivers when they are registered in the > manifest while they are received when they are register through > registerReceiver() ?
Usually, it's for performance reasons. Take your desired Intent, for example. ACTION_NEW_OUTGOING_CALL is something the user is particularly paying attention to. If Android has to fire off a bunch of processes, load up the receivers, and pass the Intent to each, that's going to slow down how quickly Android is able to place the call. Another example is ACTION_BATTERY_CHANGED -- they don't want to fire up a bunch of processes just to tell apps that the battery level changed. After all, firing off all those processes and doing all that work might decrease the battery level, requiring another round of ACTION_BATTERY_CHANGED, which will either eventually drain the battery or create a rupture in the space-time continuum. I get those two cases confused a lot. Sometimes, Intents that do not support manifest-registered receivers are documented, sometimes not. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android Training in US: 14-18 June 2010: http://bignerdranch.com -- 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
