page.title=<receiver> @jd:body
<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>
<application>
<intent-filter>
<meta-data>
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 {@link
android.content.Context#registerReceiver Context.registerReceiver()}
method. See the {@link android.content.BroadcastReceiver} class description
for more on dynamically created receivers.
The <application>
element has its own
enabled
attribute that applies to all
application components, including broadcast receivers. The
<application>
and
{@code <receiver>} attributes must both be "{@code true}" for
the broadcast receiver to be enabled. If either is "{@code false}", it is
disabled; it cannot be instantiated.
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 "{@code false}". 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 "{@code true}".
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
(see the permission
attribute).
<application>
element's icon
attribute).
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
<intent-filter>
element's
icon
attribute).
<application>
element's
label
attribute).
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
<intent-filter>
element's
label
attribute).
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.
<manifest>
element.
There is no default. The name must be specified.
<application>
element's
permission
attribute 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.
<application>
element's
process
attribute can set a different
default for all components. But each component can override the default
with its own {@code process} attribute, 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.