<receiver android:enabled=["true" | "false"] android:exported=["true" | "false"] android:icon="drawable resource" android:label="string resource" android:name="string" android:permission="string" android:process="string" > . . . </receiver>
BroadcastReceiversubclass) as one of the application's components. Broadcast receivers enable applications to receive intents that are broadcast by the system or by other applications, even when other components of the application are not running.
There are two ways to make a broadcast receiver known to the system: One is
declare it in the manifest file with this element. The other is to create
the receiver dynamically in code and register it with the
method. See the
BroadcastReceiver class description
for more on dynamically created receivers.
true" if it can be, and "
false" if not. The default value is "
<application> element has its own
enabled attribute that applies to all
application components, including broadcast receivers. The
<receiver> attributes must both be "
the broadcast receiver to be enabled. If either is "
false", it is
disabled; it cannot be instantiated.
true" if it can, and "
false" if not. If "
false", the only messages the broadcast receiver can receive are those sent by components of the same application or applications with the same user ID.
The default value depends on whether the broadcast receiver contains intent filters.
The absence of any filters means that it can be invoked only by Intent objects that
specify its exact class name. This implies that the receiver is intended only for
application-internal use (since others would not normally know the class name).
So in this case, the default value is "
On the other hand, the presence of at least one filter implies that the broadcast
receiver is intended to receive intents broadcast by the system or other applications,
so the default value is "
This attribute is not the only way to limit a broadcast receiver's external exposure.
You can also use a permission to limit the external entities that can send it messages
The broadcast receiver's icon — whether set here or by the
<application> element — is also the
default icon for all the receiver's intent filters (see the
The broadcast receiver's label — whether set here or by the
<application> element — is also the
default label for all the receiver's intent filters (see the
The label should be set as a reference to a string resource, so that it can be localized like other strings in the user interface. However, as a convenience while you're developing the application, it can also be set as a raw string.
BroadcastReceiver. This should be a fully qualified class name (such as, "
com.example.project.ReportReceiver"). However, as a shorthand, if the first character of the name is a period (for example, "
. ReportReceiver"), it is appended to the package name specified in the
There is no default. The name must be specified.
permissionattribute applies to the broadcast receiver. If neither attribute is set, the receiver is not protected by a permission.
For more information on permissions, see the Permissions section in the introduction and a separate document, Security and Permissions.
processattribute can set a different default for all components. But each component can override the default with its own
processattribute, allowing you to spread your application across multiple processes.
If the name assigned to this attribute begins with a colon (':'), a new process, private to the application, is created when it's needed and the broadcast receiver runs in that process. If the process name begins with a lowercase character, the receiver will run in a global process of that name, provided that it has permission to do so. This allows components in different applications to share a process, reducing resource usage.