Thanks for that information. These are the actions documented with that behavior -
ACTION_BATTERY_CHANGED ACTION_CONFIGURATION_CHANGED ACTION_TIME_TICK On Feb 19, 11:00 am, Mark Murphy <[email protected]> wrote: > jotobjects wrote: > > On Feb 19, 4:38 am, Mark Murphy <[email protected]> wrote: > >> You can try registering the BroadcastReceiver as part of some other > >> component (Activity, Service) via registerReceiver(). Not all broadcast > >> Intents work with manifest-registered receivers. > > > What is the reason that a BroadcastReceiver would function differently > > depending on registration in Manifest vs. registerReceiver() ? > > For example, for ACTION_BATTERY_CHANGED, Android does not want to start > up a whole 'nuther process just because the battery level shifted. > Hence, to receive that broadcast Intent, you need to use registerReceiver(). > > Also, ACTION_BOOT_COMPLETED only really works from a manifest-registered > receiver, because by the time your code is in position to call > registerReceiver(), the boot is long gone. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > Android Training...At Your Office:http://commonsware.com/training -- 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
