As part of the new O Preview Background Execution Limits, apps that target the O Developer Preview can no longer register broadcast receivers for implicit broadcasts in their manifest. However, several broadcasts are currently exempted from these limitations. Apps can continue to register listeners for the following broadcasts, no matter what API level the apps target.
Exempted because these broadcasts are only sent only once, at first boot, and many apps need to receive this broadcast to schedule jobs, alarms, and so forth.
These broadcasts are protected by privileged permissions, so most normal apps cannot receive them anyway.
Clock apps may need to receive these broadcasts to update alarms when the time, timezone, or alarms are changed.
Only sent when the locale changes, which is not often. Apps might need to update their data when the locale changes.
If an app needs to know about these USB-related events, there is not currently a good alternative to registering for the broadcast.
Since this broadcast is only sent when the user physically connects or disconnects a plug, it's not likely to affect user experience if apps respond to this broadcast.
ACTION_HEADSET_PLUG, user experience is not likely to suffer if apps receive broadcasts for these Bluetooth events.
OEM telephony apps may need to receive these broadcasts.
Some apps need to know about changes to login accounts so they can set up scheduled operations for the new and changed accounts.
Only sent when the user explicitly clears their data from Settings, so broadcast receivers are unlikely to significantly affect user experience.
Some apps may need to update their stored data when another package is removed; for those apps, there is no good alternative to registering for this broadcast.
Note: Other package-related broadcasts (such as
ACTION_PACKAGE_REPLACED) are not exempted from the new restrictions. These broadcasts are common enough that there is a potential performance impact to exempting them.
Apps that take action in response to users placing calls need to receive this broadcast.
This broadcast is not sent very often; some apps need to receive it, so that they know that the device's security status has changed.
Sent by the calendar provider to post an event reminder to the calendar app. Since the calendar provider doesn't know what the calendar app is, this broadcast has to be implicit.
These broadcasts are sent as a result of the user's physical interactions with the device (installing or removing storage volumes) or as part of boot initialization (as available volumes get mounted), so they are not a common occurrence and are generally under the user’s control.
These broadcasts are relied on by SMS recipient apps.