<application android:allowClearUserData=["true" | "false"] android:allowTaskReparenting=["true" | "false"] android:debuggable=["true" | "false"] android:description="string resource" android:enabled=["true" | "false"] android:hasCode=["true" | "false"] android:icon="drawable resource" android:label="string resource" android:manageSpaceActivity="string" android:name="string" android:permission="string" android:persistent=["true" | "false"] android:process="string" android:taskAffinity="string" android:theme="resource or theme" > . . . </application>
<manifest>
<activity>
<activity-alias>
<service>
<receiver>
<provider>
<uses-library>
icon
, label
, permission
, process
,
taskAffinity
, and allowTaskReparenting
) set default values
for corresponding attributes of the component elements. Others (such as
debuggable
, enabled
, description
, and
allowClearUserData
) set values for the application as a whole and
cannot be overridden by the components.android:allowClearUserData
true
" if they are, and "false
" if not. If the value is
"true
", as it is by default, the application manager includes an
option that allows users to clear the data.android:allowTaskReparenting
true
" if they can move, and
"false
" if they must remain with the task where they started.
The default value is "false
".
The
<activity>
element has its own
allowTaskReparenting
attribute that can override the value set here. See that attribute for more
information.
android:debuggable
true
" if it can be, and "false
"
if not. The default value is "false
".android:description
android:enabled
true
" if it can, and "false
"
if not. If the value is "true
", each component's
enabled
attribute determines whether that component is enabled
or not. If the value is "false
", it overrides the
component-specific values; all components are disabled.
The default value is "true
".
android:hasCode
true
"
if it does, and "false
" if not. When the value is "false
",
the system does not try to load any application code when launching components.
The default value is "true
".
An application would not have any code of its own only if it's using nothing but built-in component classes, such as an activity that uses the AliasActivity class, a rare occurrence.
android:icon
icon
attributes for
<activity>
,
<activity-alias>
,
<service>
,
<receiver>
, and
<provider>
elements.
This attribute must be set as a reference to a drawable resource containing the image definition. There is no default icon.
android:label
label
attributes for
<activity>
,
<activity-alias>
,
<service>
,
<receiver>
, and
<provider>
elements.
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.
android:manageSpaceActivity
<activity>
element.
android:name
The subclass is optional; most applications won't need one. In the absence of a subclass, Android uses an instance of the base Application class.
android:permission
permission
attributes of individual
components.
For more information on permissions, see the Permissions section in the introduction and another document, Security and Permissions.
android:persistent
true
" if it should, and "false
" if not. The default value
is "false
". Applications should not normally set this flag;
persistence mode is intended only for certain system applications.android:process
process
attribute.
By default, Android creates a process for an application when the first
of its components needs to run. All components then run in that process.
The name of the default process matches the package name set by the
<manifest>
element.
By setting this attribute to a process name that's shared with another application, you can arrange for components of both applications to run in the same process — but only if the two applications also share a user ID and be signed with the same certificate.
If the name assigned to this attribute begins with a colon (':'), a new process, private to the application, is created when it's needed. If the process name begins with a lowercase character, a global process of that name is created. A global process can be shared with other applications, reducing resource usage.
android:taskAffinity
taskAffinity
attributes. See that attribute for more information.
By default, all activities within an application share the same
affinity. The name of that affinity is the same as the package name
set by the
<manifest>
element.
android:theme
theme
attributes; see that attribute for more information.<activity>
<service>
<receiver>
<provider>