1 <?xml version="1.0" encoding="utf-8"?>
3 /* Copyright 2006, The Android Open Source Project
5 ** Licensed under the Apache License, Version 2.0 (the "License");
6 ** you may not use this file except in compliance with the License.
7 ** You may obtain a copy of the License at
9 ** http://www.apache.org/licenses/LICENSE-2.0
11 ** Unless required by applicable law or agreed to in writing, software
12 ** distributed under the License is distributed on an "AS IS" BASIS,
13 ** WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
14 ** See the License for the specific language governing permissions and
15 ** limitations under the License.
19 <!-- **************************************************************** -->
20 <!-- These are the attributes used in AndroidManifest.xml. -->
21 <!-- **************************************************************** -->
24 <!-- The overall theme to use for an activity. Use with either the
25 application tag (to supply a default theme for all activities) or
26 the activity tag (to supply a specific theme for that activity).
28 <p>This automatically sets
29 your activity's Context to use this theme, and may also be used
30 for "starting" animations prior to the activity being launched (to
31 better match what the activity actually looks like). It is a reference
32 to a style resource defining the theme. If not set, the default
33 system theme will be used. -->
34 <attr name="theme" format="reference" />
36 <!-- A user-legible name for the given item. Use with the
37 application tag (to supply a default label for all application
38 components), or with the activity, receiver, service, or instrumentation
39 tag (to supply a specific label for that component). It may also be
40 used with the intent-filter tag to supply a label to show to the
41 user when an activity is being selected based on a particular Intent.
43 <p>The given label will be used wherever the user sees information
44 about its associated component; for example, as the name of a
45 main activity that is displayed in the launcher. You should
46 generally set this to a reference to a string resource, so that
47 it can be localized, however it is also allowed to supply a plain
48 string for quick and dirty programming. -->
49 <attr name="label" format="reference|string" />
51 <!-- A Drawable resource providing a graphical representation of its
52 associated item. Use with the
53 application tag (to supply a default icon for all application
54 components), or with the activity, receiver, service, or instrumentation
55 tag (to supply a specific icon for that component). It may also be
56 used with the intent-filter tag to supply an icon to show to the
57 user when an activity is being selected based on a particular Intent.
59 <p>The given icon will be used to display to the user a graphical
60 representation of its associated component; for example, as the icon
61 for main activity that is displayed in the launcher. This must be
62 a reference to a Drawable resource containing the image definition. -->
63 <attr name="icon" format="reference" />
65 <!-- A Drawable resource providing a graphical representation of its
66 associated item. Use with the
67 application tag (to supply a default round icon for all application
68 components), or with the activity, receiver, service, or instrumentation
69 tag (to supply a specific round icon for that component). It may also be
70 used with the intent-filter tag to supply a round icon to show to the
71 user when an activity is being selected based on a particular Intent.
73 <p>The given round icon will be used to display to the user a graphical
74 representation of its associated component; for example, as the round icon
75 for main activity that is displayed in the launcher. This must be
76 a reference to a Drawable resource containing the image definition. -->
77 <attr name="roundIcon" format="reference" />
79 <!-- A Drawable resource providing an extended graphical banner for its
80 associated item. Use with the application tag (to supply a default
81 banner for all application activities), or with the activity, tag to
82 supply a banner for a specific activity.
84 <p>The given banner will be used to display to the user a graphical
85 representation of an activity in the Leanback application launcher.
86 Since banners are displayed only in the Leanback launcher, they should
87 only be used with activities (and applications) that support Leanback
88 mode. These are activities that handle Intents of category
89 {@link android.content.Intent#CATEGORY_LEANBACK_LAUNCHER
90 Intent.CATEGORY_LEANBACK_LAUNCHER}.
91 <p>This must be a reference to a Drawable resource containing the image definition. -->
92 <attr name="banner" format="reference" />
94 <!-- A Drawable resource providing an extended graphical logo for its
95 associated item. Use with the application tag (to supply a default
96 logo for all application components), or with the activity, receiver,
97 service, or instrumentation tag (to supply a specific logo for that
98 component). It may also be used with the intent-filter tag to supply
99 a logo to show to the user when an activity is being selected based
100 on a particular Intent.
102 <p>The given logo will be used to display to the user a graphical
103 representation of its associated component; for example as the
104 header in the Action Bar. The primary differences between an icon
105 and a logo are that logos are often wider and more detailed, and are
106 used without an accompanying text caption. This must be a reference
107 to a Drawable resource containing the image definition. -->
108 <attr name="logo" format="reference" />
110 <!-- Name of the activity to be launched to manage application's space on
111 device. The specified activity gets automatically launched when the
112 application's space needs to be managed and is usually invoked
113 through user actions. Applications can thus provide their own custom
114 behavior for managing space for various scenarios like out of memory
115 conditions. This is an optional attribute and
116 applications can choose not to specify a default activity to
118 <attr name="manageSpaceActivity" format="string" />
120 <!-- Option to let applications specify that user data can/cannot be
121 cleared. This flag is turned on by default.
122 <em>This attribute is usable only by applications
123 included in the system image. Third-party apps cannot use it.</em> -->
124 <attr name="allowClearUserData" format="boolean" />
126 <!-- Option to indicate this application is only for testing purposes.
127 For example, it may expose functionality or data outside of itself
128 that would cause a security hole, but is useful for testing. This
129 kind of application can not be installed without the
130 INSTALL_ALLOW_TEST flag, which means only through adb install. -->
131 <attr name="testOnly" format="boolean" />
133 <!-- A unique name for the given item. This must use a Java-style naming
134 convention to ensure the name is unique, for example
135 "com.mycompany.MyName". -->
136 <attr name="name" format="string" />
138 <!-- Specify a permission that a client is required to have in order to
139 use the associated object. If the client does not hold the named
140 permission, its request will fail. See the
141 <a href="{@docRoot}guide/topics/security/security.html">Security and Permissions</a>
142 document for more information on permissions. -->
143 <attr name="permission" format="string" />
145 <!-- A specific {@link android.R.attr#permission} name for read-only
146 access to a {@link android.content.ContentProvider}. See the
147 <a href="{@docRoot}guide/topics/security/security.html">Security and Permissions</a>
148 document for more information on permissions. -->
149 <attr name="readPermission" format="string" />
151 <!-- A specific {@link android.R.attr#permission} name for write
152 access to a {@link android.content.ContentProvider}. See the
153 <a href="{@docRoot}guide/topics/security/security.html">Security and Permissions</a>
154 document for more information on permissions. -->
155 <attr name="writePermission" format="string" />
157 <!-- If true, the {@link android.content.Context#grantUriPermission
158 Context.grantUriPermission} or corresponding Intent flags can
159 be used to allow others to access specific URIs in the content
160 provider, even if they do not have an explicit read or write
161 permission. If you are supporting this feature, you must be
162 sure to call {@link android.content.Context#revokeUriPermission
163 Context.revokeUriPermission} when URIs are deleted from your
165 <attr name="grantUriPermissions" format="boolean" />
167 <!-- Characterizes the potential risk implied in a permission and
168 indicates the procedure the system should follow when determining
169 whether to grant the permission to an application requesting it. {@link
170 android.Manifest.permission Standard permissions} have a predefined and
171 permanent protectionLevel. If you are creating a custom permission in an
172 application, you can define a protectionLevel attribute with one of the
173 values listed below. If no protectionLevel is defined for a custom
174 permission, the system assigns the default ("normal"). -->
175 <attr name="protectionLevel">
176 <!-- A lower-risk permission that gives an application access to isolated
177 application-level features, with minimal risk to other applications,
178 the system, or the user. The system automatically grants this type
179 of permission to a requesting application at installation, without
180 asking for the user's explicit approval (though the user always
181 has the option to review these permissions before installing). -->
182 <flag name="normal" value="0" />
183 <!-- A higher-risk permission that would give a requesting application
184 access to private user data or control over the device that can
185 negatively impact the user. Because this type of permission
186 introduces potential risk, the system may not automatically
187 grant it to the requesting application. For example, any dangerous
188 permissions requested by an application may be displayed to the
189 user and require confirmation before proceeding, or some other
190 approach may be taken to avoid the user automatically allowing
191 the use of such facilities. -->
192 <flag name="dangerous" value="1" />
193 <!-- A permission that the system is to grant only if the requesting
194 application is signed with the same certificate as the application
195 that declared the permission. If the certificates match, the system
196 automatically grants the permission without notifying the user or
197 asking for the user's explicit approval. -->
198 <flag name="signature" value="2" />
199 <!-- A permission that the system is to grant only to packages in the
200 Android system image <em>or</em> that are signed with the same
201 certificates. Please avoid using this option, as the
202 signature protection level should be sufficient for most needs and
203 works regardless of exactly where applications are installed. This
204 permission is used for certain special situations where multiple
205 vendors have applications built in to a system image which need
206 to share specific features explicitly because they are being built
208 <flag name="signatureOrSystem" value="3" />
209 <!-- Additional flag from base permission type: this permission can also
210 be granted to any applications installed as privileged apps on the system image.
211 Please avoid using this option, as the
212 signature protection level should be sufficient for most needs and
213 works regardless of exactly where applications are installed. This
214 permission flag is used for certain special situations where multiple
215 vendors have applications built in to a system image which need
216 to share specific features explicitly because they are being built
218 <flag name="privileged" value="0x10" />
219 <!-- Old synonym for "privileged". -->
220 <flag name="system" value="0x10" />
221 <!-- Additional flag from base permission type: this permission can also
222 (optionally) be granted to development applications. -->
223 <flag name="development" value="0x20" />
224 <!-- Additional flag from base permission type: this permission is closely
225 associated with an app op for controlling access. -->
226 <flag name="appop" value="0x40" />
227 <!-- Additional flag from base permission type: this permission can be automatically
228 granted to apps that target API levels below
229 {@link android.os.Build.VERSION_CODES#M} (before runtime permissions
230 were introduced). -->
231 <flag name="pre23" value="0x80" />
232 <!-- Additional flag from base permission type: this permission can be automatically
233 granted to system apps that install packages. -->
234 <flag name="installer" value="0x100" />
235 <!-- Additional flag from base permission type: this permission can be automatically
236 granted to system apps that verify packages. -->
237 <flag name="verifier" value="0x200" />
238 <!-- Additional flag from base permission type: this permission can be automatically
239 granted any application pre-installed on the system image (not just privileged
241 <flag name="preinstalled" value="0x400" />
242 <!-- Additional flag from base permission type: this permission can be automatically
243 granted to the setup wizard app -->
244 <flag name="setup" value="0x800" />
247 <!-- Flags indicating more context for a permission group. -->
248 <attr name="permissionGroupFlags">
249 <!-- Set to indicate that this permission group contains permissions
250 protecting access to some information that is considered
251 personal to the user (such as contacts, e-mails, etc). -->
252 <flag name="personalInfo" value="0x0001" />
255 <!-- Flags indicating more context for a permission. -->
256 <attr name="permissionFlags">
257 <!-- Set to indicate that this permission allows an operation that
258 may cost the user money. Such permissions may be highlighted
259 when shown to the user with this additional information. -->
260 <flag name="costsMoney" value="0x0001" />
261 <!-- Additional flag from base permission type: this permission has been
262 removed and it is no longer enforced. It shouldn't be shown in the
263 UI. Removed permissions are kept as normal permissions for backwards
264 compatibility as apps may be checking them before calling an API.
266 <flag name="removed" value="0x2" />
269 <!-- Specified the name of a group that this permission is associated
270 with. The group must have been defined with the
271 {@link android.R.styleable#AndroidManifestPermissionGroup permission-group} tag. -->
272 <attr name="permissionGroup" format="string" />
274 <!-- Specify the name of a user ID that will be shared between multiple
275 packages. By default, each package gets its own unique user-id.
276 By setting this value on two or more packages, each of these packages
277 will be given a single shared user ID, so they can for example run
278 in the same process. Note that for them to actually get the same
279 user ID, they must also be signed with the same signature. -->
280 <attr name="sharedUserId" format="string" />
282 <!-- Specify a label for the shared user UID of this package. This is
283 only used if you have also used android:sharedUserId. This must
284 be a reference to a string resource; it can not be an explicit
286 <attr name="sharedUserLabel" format="reference" />
288 <!-- Internal version code. This is the number used to determine whether
289 one version is more recent than another: it has no other meaning than
290 that higher numbers are more recent. You could use this number to
291 encode a "x.y" in the lower and upper 16 bits, make it a build
292 number, simply increase it by one each time a new version is
293 released, or define it however else you want, as long as each
294 successive version has a higher number. This is not a version
295 number generally shown to the user, that is usually supplied
296 with {@link android.R.attr#versionName}. When an app is delivered
297 as multiple split APKs, each APK must have the exact same versionCode. -->
298 <attr name="versionCode" format="integer" />
300 <!-- Internal revision code. This number is the number used to determine
301 whether one APK is more recent than another: it has no other meaning
302 than that higher numbers are more recent. This value is only meaningful
303 when the two {@link android.R.attr#versionCode} values are already
304 identical. When an app is delivered as multiple split APKs, each
305 APK may have a different revisionCode value. -->
306 <attr name="revisionCode" format="integer" />
308 <!-- The text shown to the user to indicate the version they have. This
309 is used for no other purpose than display to the user; the actual
310 significant version number is given by {@link android.R.attr#versionCode}. -->
311 <attr name="versionName" format="string" />
313 <!-- Flag to control special persistent mode of an application. This should
314 not normally be used by applications; it requires that the system keep
315 your application running at all times. -->
316 <attr name="persistent" format="boolean" />
318 <!-- Flag to specify if this application needs to be present for all users. Only pre-installed
319 applications can request this feature. Default value is false. -->
320 <attr name="requiredForAllUsers" format="boolean" />
322 <!-- Flag indicating whether the application can be debugged, even when
323 running on a device that is running in user mode. -->
324 <attr name="debuggable" format="boolean" />
326 <!-- Flag indicating whether the application requests the VM to operate in
328 <attr name="vmSafeMode" format="boolean" />
330 <!-- <p>Flag indicating whether the application's rendering should be hardware
331 accelerated if possible. This flag is turned on by default for applications
332 that are targeting {@link android.os.Build.VERSION_CODES#ICE_CREAM_SANDWICH}
334 <p>This flag can be set on the application and any activity declared
335 in the manifest. When enabled for the application, each activity is
336 automatically assumed to be hardware accelerated. This flag can be
337 overridden in the activity tags, either turning it off (if on for the
338 application) or on (if off for the application.)</p>
339 <p>When this flag is turned on for an activity (either directly or via
340 the application tag), every window created from the activity, including
341 the activity's own window, will be hardware accelerated, if possible.</p>
342 <p>Please refer to the documentation of
343 {@link android.view.WindowManager.LayoutParams#FLAG_HARDWARE_ACCELERATED}
344 for more information on how to control this flag programmatically.</p> -->
345 <attr name="hardwareAccelerated" format="boolean" />
347 <!-- Flag indicating whether the given application component is available
348 to other applications. If false, it can only be accessed by
349 applications with its same user id (which usually means only by
350 code in its own package). If true, it can be invoked by external
351 entities, though which ones can do so may be controlled through
352 permissions. The default value is false for activity, receiver,
353 and service components that do not specify any intent filters; it
354 is true for activity, receiver, and service components that do
355 have intent filters (implying they expect to be invoked by others
356 who do not know their particular component name) and for all
357 content providers. -->
358 <attr name="exported" format="boolean" />
360 <!-- A boolean flag used to indicate if an application is a Game or not.
361 <p>This information can be used by the system to group together
362 applications that are classified as games, and display them separately
363 from the other applications. -->
364 <attr name="isGame" format="boolean" />
366 <!-- If set to true, a single instance of this component will run for
367 all users. That instance will run as user 0, the default/primary
368 user. When the app running is in processes for other users and interacts
369 with this component (by binding to a service for example) those processes will
370 always interact with the instance running for user 0. Enabling
371 single user mode forces "exported" of the component to be false, to
372 help avoid introducing multi-user security bugs. This feature is only
373 available to applications built in to the system image; you must hold the
374 permission INTERACT_ACROSS_USERS in order
375 to use this feature. This flag can only be used with services,
376 receivers, and providers; it can not be used with activities. -->
377 <attr name="singleUser" format="boolean" />
379 <!-- Specify a specific process that the associated code is to run in.
380 Use with the application tag (to supply a default process for all
381 application components), or with the activity, receiver, service,
382 or provider tag (to supply a specific icon for that component).
384 <p>Application components are normally run in a single process that
385 is created for the entire application. You can use this tag to modify
386 where they run. If the process name begins with a ':' character,
387 a new process private to that application will be created when needed
388 to run that component (allowing you to spread your application across
389 multiple processes). If the process name begins with a lower-case
390 character, the component will be run in a global process of that name,
391 provided that you have permission to do so, allowing multiple
392 applications to share one process to reduce resource usage. -->
393 <attr name="process" format="string" />
395 <!-- Specify a task name that activities have an "affinity" to.
396 Use with the application tag (to supply a default affinity for all
397 activities in the application), or with the activity tag (to supply
398 a specific affinity for that component).
400 <p>The default value for this attribute is the same as the package
401 name, indicating that all activities in the manifest should generally
402 be considered a single "application" to the user. You can use this
403 attribute to modify that behavior: either giving them an affinity
404 for another task, if the activities are intended to be part of that
405 task from the user's perspective, or using an empty string for
406 activities that have no affinity to a task. -->
407 <attr name="taskAffinity" format="string" />
409 <!-- Specify that an activity can be moved out of a task it is in to
410 the task it has an affinity for when appropriate. Use with the
411 application tag (to supply a default for all activities in the
412 application), or with an activity tag (to supply a specific
413 setting for that component).
415 <p>Normally when an application is started, it is associated with
416 the task of the activity that started it and stays there for its
417 entire lifetime. You can use the allowTaskReparenting feature to force an
418 activity to be re-parented to a different task when the task it is
419 in goes to the background. Typically this is used to cause the
420 activities of an application to move back to the main task associated
421 with that application. The activity is re-parented to the task
422 with the same {@link android.R.attr#taskAffinity} as it has. -->
423 <attr name="allowTaskReparenting" format="boolean" />
425 <!-- Declare that this application may use cleartext traffic, such as HTTP rather than HTTPS;
426 WebSockets rather than WebSockets Secure; XMPP, IMAP, STMP without STARTTLS or TLS.
427 Defaults to true. If set to false {@code false}, the application declares that it does not
428 intend to use cleartext network traffic, in which case platform components (e.g. HTTP
429 stacks, {@code DownloadManager}, {@code MediaPlayer}) will refuse applications's requests
430 to use cleartext traffic. Third-party libraries are encouraged to honor this flag as well.
432 <attr name="usesCleartextTraffic" format="boolean" />
434 <!-- Declare that code from this application will need to be loaded into other
435 applications' processes. On devices that support multiple instruction sets,
436 this implies the code might be loaded into a process that's using any of the devices
437 supported instruction sets.
439 <p> The system might treat such applications specially, for eg., by
440 extracting the application's native libraries for all supported instruction
441 sets or by compiling the application's dex code for all supported instruction
443 <attr name="multiArch" format ="boolean" />
445 <!-- Specify whether the 32 bit version of the ABI should be used in a
446 multiArch application. If both abioverride flag (i.e. using abi option of abd install)
447 and use32bitAbi are used, then use32bit is ignored.-->
448 <attr name="use32bitAbi" />
450 <!-- Specify whether a component is allowed to have multiple instances
451 of itself running in different processes. Use with the activity
454 <p>Normally the system will ensure that all instances of a particular
455 component are only running in a single process. You can use this
456 attribute to disable that behavior, allowing the system to create
457 instances wherever they are used (provided permissions allow it).
458 This is most often used with content providers, so that instances
459 of a provider can be created in each client process, allowing them
460 to be used without performing IPC. -->
461 <attr name="multiprocess" format="boolean" />
463 <!-- Specify whether an activity should be finished when its task is
464 brought to the foreground by relaunching from the home screen.
466 <p>If both this option and {@link android.R.attr#allowTaskReparenting} are
467 specified, the finish trumps the affinity: the affinity will be
468 ignored and the activity simply finished. -->
469 <attr name="finishOnTaskLaunch" format="boolean" />
471 <!-- Specify whether an activity should be finished when a "close system
472 windows" request has been made. This happens, for example, when
473 the home key is pressed, when the device is locked, when a system
474 dialog showing recent applications is displayed, etc. -->
475 <attr name="finishOnCloseSystemDialogs" format="boolean" />
477 <!-- Specify whether an activity's task should be cleared when it
478 is re-launched from the home screen. As a result, every time the
479 user starts the task, they will be brought to its root activity,
480 regardless of whether they used BACK or HOME to last leave it.
481 This flag only applies to activities that
482 are used to start the root of a new task.
484 <p>An example of the use of this flag would be for the case where
485 a user launches activity A from home, and from there goes to
486 activity B. They now press home, and then return to activity A.
487 Normally they would see activity B, since that is what they were
488 last doing in A's task. However, if A has set this flag to true,
489 then upon going to the background all of the tasks on top of it (B
490 in this case) are removed, so when the user next returns to A they
491 will restart at its original activity.
493 <p>When this option is used in conjunction with
494 {@link android.R.attr#allowTaskReparenting}, the allowTaskReparenting trumps the
495 clear. That is, all activities above the root activity of the
496 task will be removed: those that have an affinity will be moved
497 to the task they are associated with, otherwise they will simply
498 be dropped as described here. -->
499 <attr name="clearTaskOnLaunch" format="boolean" />
501 <!-- Specify whether an activity should be kept in its history stack.
502 If this attribute is set, then as soon as the user navigates away
503 from the activity it will be finished and they will no longer be
504 able to return to it. -->
505 <attr name="noHistory" format="boolean" />
507 <!-- Specify whether an acitivty's task state should always be maintained
508 by the system, or if it is allowed to reset the task to its initial
509 state in certain situations.
511 <p>Normally the system will reset a task (remove all activities from
512 the stack and reset the root activity) in certain situations when
513 the user re-selects that task from the home screen. Typically this
514 will be done if the user hasn't visited that task for a certain
515 amount of time, such as 30 minutes.
517 <p>By setting this attribute, the user will always return to your
518 task in its last state, regardless of how they get there. This is
519 useful, for example, in an application like the web browser where there
520 is a lot of state (such as multiple open tabs) that the application
521 would not like to lose. -->
522 <attr name="alwaysRetainTaskState" format="boolean" />
524 <!-- Indicates that an Activity does not need to have its freeze state
525 (as returned by {@link android.app.Activity#onSaveInstanceState}
526 retained in order to be restarted. Generally you use this for activities
527 that do not store any state. When this flag is set, if for some reason
528 the activity is killed before it has a chance to save its state,
529 then the system will not remove it from the activity stack like
530 it normally would. Instead, the next time the user navigates to
531 it its {@link android.app.Activity#onCreate} method will be called
532 with a null icicle, just like it was starting for the first time.
534 <p>This is used by the Home activity to make sure it does not get
535 removed if it crashes for some reason. -->
536 <attr name="stateNotNeeded" format="boolean" />
538 <!-- Indicates that an Activity should be excluded from the list of
539 recently launched activities. -->
540 <attr name="excludeFromRecents" format="boolean" />
542 <!-- Specify that an Activity should be shown over the lock screen and,
543 in a multiuser environment, across all users' windows.
544 @deprecated use {@link android.R.attr#showForAllUsers} instead. -->
545 <attr name="showOnLockScreen" format="boolean" />
547 <!-- Specify that an Activity should be shown even if the current/foreground user
548 is different from the user of the Activity. This will also force the
549 <code>android.view.LayoutParams.FLAG_SHOW_WHEN_LOCKED</code> flag
550 to be set for all windows of this activity -->
551 <attr name="showForAllUsers" format="boolean" />
553 <!-- Specify the authorities under which this content provider can be
554 found. Multiple authorities may be supplied by separating them
555 with a semicolon. Authority names should use a Java-style naming
556 convention (such as <code>com.google.provider.MyProvider</code>)
557 in order to avoid conflicts. Typically this name is the same
558 as the class implementation describing the provider's data structure. -->
559 <attr name="authorities" format="string" />
561 <!-- Flag indicating whether this content provider would like to
562 participate in data synchronization. -->
563 <attr name="syncable" format="boolean" />
565 <!-- Flag declaring this activity to be 'immersive'; immersive activities
566 should not be interrupted with other activities or notifications. -->
567 <attr name="immersive" format="boolean" />
569 <!-- Flag declaring that this activity will be run in VR mode, and specifying
570 the component of the {@link android.service.vr.VrListenerService} that should be
571 bound while this Activity is visible if it is installed and enabled on this device.
572 This is equivalent to calling {@link android.app.Activity#setVrModeEnabled} with the
573 the given component name within the Activity that this attribute is set for.
574 Declaring this will prevent the system from leaving VR mode during an Activity
575 transtion from one VR activity to another. -->
576 <attr name="enableVrMode" format="string" />
578 <!-- Specify the order in which content providers hosted by a process
579 are instantiated when that process is created. Not needed unless
580 you have providers with dependencies between each other, to make
581 sure that they are created in the order needed by those dependencies.
582 The value is a simple integer, with higher numbers being
583 initialized first. -->
584 <attr name="initOrder" format="integer" />
586 <!-- Specify the relative importance or ability in handling a particular
587 Intent. For receivers, this controls the order in which they are
588 executed to receive a broadcast (note that for
589 asynchronous broadcasts, this order is ignored). For activities,
590 this provides information about how good an activity is handling an
591 Intent; when multiple activities match an intent and have different
592 priorities, only those with the higher priority value will be
595 <p>Only use if you really need to impose some specific
596 order in which the broadcasts are received, or want to forcibly
597 place an activity to always be preferred over others. The value is a
598 single integer, with higher numbers considered to be better. -->
599 <attr name="priority" format="integer" />
601 <!-- Indicate if this component is aware of direct boot lifecycle, and can be
602 safely run before the user has entered their credentials (such as a lock
604 <attr name="directBootAware" format="boolean" />
606 <!-- Specify how an activity should be launched. See the
607 <a href="{@docRoot}guide/topics/fundamentals/tasks-and-back-stack.html">Tasks and Back
608 Stack</a> document for important information on how these options impact
609 the behavior of your application.
611 <p>If this attribute is not specified, <code>standard</code> launch
612 mode will be used. Note that the particular launch behavior can
613 be changed in some ways at runtime through the
614 {@link android.content.Intent} flags
615 {@link android.content.Intent#FLAG_ACTIVITY_SINGLE_TOP},
616 {@link android.content.Intent#FLAG_ACTIVITY_NEW_TASK}, and
617 {@link android.content.Intent#FLAG_ACTIVITY_MULTIPLE_TASK}. -->
618 <attr name="launchMode">
619 <!-- The default mode, which will usually create a new instance of
620 the activity when it is started, though this behavior may change
621 with the introduction of other options such as
622 {@link android.content.Intent#FLAG_ACTIVITY_NEW_TASK
623 Intent.FLAG_ACTIVITY_NEW_TASK}. -->
624 <enum name="standard" value="0" />
625 <!-- If, when starting the activity, there is already an
626 instance of the same activity class in the foreground that is
627 interacting with the user, then
628 re-use that instance. This existing instance will receive a call to
629 {@link android.app.Activity#onNewIntent Activity.onNewIntent()} with
630 the new Intent that is being started. -->
631 <enum name="singleTop" value="1" />
632 <!-- If, when starting the activity, there is already a task running
633 that starts with this activity, then instead of starting a new
634 instance the current task is brought to the front. The existing
635 instance will receive a call to {@link android.app.Activity#onNewIntent
636 Activity.onNewIntent()}
637 with the new Intent that is being started, and with the
638 {@link android.content.Intent#FLAG_ACTIVITY_BROUGHT_TO_FRONT
639 Intent.FLAG_ACTIVITY_BROUGHT_TO_FRONT} flag set. This is a superset
640 of the singleTop mode, where if there is already an instance
641 of the activity being started at the top of the stack, it will
642 receive the Intent as described there (without the
643 FLAG_ACTIVITY_BROUGHT_TO_FRONT flag set). See the
644 <a href="{@docRoot}guide/topics/fundamentals/tasks-and-back-stack.html">Tasks and Back
645 Stack</a> document for more details about tasks.-->
646 <enum name="singleTask" value="2" />
647 <!-- Only allow one instance of this activity to ever be
648 running. This activity gets a unique task with only itself running
649 in it; if it is ever launched again with the same Intent, then that
650 task will be brought forward and its
651 {@link android.app.Activity#onNewIntent Activity.onNewIntent()}
652 method called. If this
653 activity tries to start a new activity, that new activity will be
654 launched in a separate task. See the
655 <a href="{@docRoot}guide/topics/fundamentals/tasks-and-back-stack.html">Tasks and Back
656 Stack</a> document for more details about tasks.-->
657 <enum name="singleInstance" value="3" />
660 <!-- Specify the orientation an activity should be run in. If not
661 specified, it will run in the current preferred orientation
663 <p>This attribute is supported by the <a
664 href="{@docRoot}guide/topics/manifest/activity-element.html">{@code <activity>}</a>
666 <attr name="screenOrientation">
667 <!-- No preference specified: let the system decide the best
668 orientation. This will either be the orientation selected
669 by the activity below, or the user's preferred orientation
670 if this activity is the bottom of a task. If the user
671 explicitly turned off sensor based orientation through settings
672 sensor based device rotation will be ignored. If not by default
673 sensor based orientation will be taken into account and the
674 orientation will changed based on how the user rotates the device.
676 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_UNSPECIFIED}. -->
677 <enum name="unspecified" value="-1" />
678 <!-- Would like to have the screen in a landscape orientation: that
679 is, with the display wider than it is tall, ignoring sensor data.
681 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_LANDSCAPE}. -->
682 <enum name="landscape" value="0" />
683 <!-- Would like to have the screen in a portrait orientation: that
684 is, with the display taller than it is wide, ignoring sensor data.
686 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_PORTRAIT}. -->
687 <enum name="portrait" value="1" />
688 <!-- Use the user's current preferred orientation of the handset.
690 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_USER}. -->
691 <enum name="user" value="2" />
692 <!-- Keep the screen in the same orientation as whatever is behind
695 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_BEHIND}. -->
696 <enum name="behind" value="3" />
697 <!-- Orientation is determined by a physical orientation sensor:
698 the display will rotate based on how the user moves the device.
699 Ignores user's setting to turn off sensor-based rotation.
701 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_SENSOR}. -->
702 <enum name="sensor" value="4" />
703 <!-- Always ignore orientation determined by orientation sensor:
704 the display will not rotate when the user moves the device.
706 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_NOSENSOR}. -->
707 <enum name="nosensor" value="5" />
708 <!-- Would like to have the screen in landscape orientation, but can
709 use the sensor to change which direction the screen is facing.
711 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_SENSOR_LANDSCAPE}. -->
712 <enum name="sensorLandscape" value="6" />
713 <!-- Would like to have the screen in portrait orientation, but can
714 use the sensor to change which direction the screen is facing.
716 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_SENSOR_PORTRAIT}. -->
717 <enum name="sensorPortrait" value="7" />
718 <!-- Would like to have the screen in landscape orientation, turned in
719 the opposite direction from normal landscape.
721 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_REVERSE_LANDSCAPE}. -->
722 <enum name="reverseLandscape" value="8" />
723 <!-- Would like to have the screen in portrait orientation, turned in
724 the opposite direction from normal portrait.
726 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_REVERSE_PORTRAIT}. -->
727 <enum name="reversePortrait" value="9" />
728 <!-- Orientation is determined by a physical orientation sensor:
729 the display will rotate based on how the user moves the device.
730 This allows any of the 4 possible rotations, regardless of what
731 the device will normally do (for example some devices won't
732 normally use 180 degree rotation).
734 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_FULL_SENSOR}. -->
735 <enum name="fullSensor" value="10" />
736 <!-- Would like to have the screen in landscape orientation, but if
737 the user has enabled sensor-based rotation then we can use the
738 sensor to change which direction the screen is facing.
740 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_USER_LANDSCAPE}. -->
741 <enum name="userLandscape" value="11" />
742 <!-- Would like to have the screen in portrait orientation, but if
743 the user has enabled sensor-based rotation then we can use the
744 sensor to change which direction the screen is facing.
746 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_USER_PORTRAIT}. -->
747 <enum name="userPortrait" value="12" />
748 <!-- Respect the user's sensor-based rotation preference, but if
749 sensor-based rotation is enabled then allow the screen to rotate
750 in all 4 possible directions regardless of what
751 the device will normally do (for example some devices won't
752 normally use 180 degree rotation).
754 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_FULL_USER}. -->
755 <enum name="fullUser" value="13" />
756 <!-- Screen is locked to its current rotation, whatever that is.
758 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_LOCKED}. -->
759 <enum name="locked" value="14" />
762 <!-- Specify one or more configuration changes that the activity will
763 handle itself. If not specified, the activity will be restarted
764 if any of these configuration changes happen in the system. Otherwise,
765 the activity will remain running and its
766 {@link android.app.Activity#onConfigurationChanged Activity.onConfigurationChanged}
767 method called with the new configuration.
769 <p>Note that all of these configuration changes can impact the
770 resource values seen by the application, so you will generally need
771 to re-retrieve all resources (including view layouts, drawables, etc)
772 to correctly handle any configuration change.
774 <p>These values must be kept in sync with those in
775 {@link android.content.pm.ActivityInfo} and
776 include/utils/ResourceTypes.h. -->
777 <attr name="configChanges">
778 <!-- The IMSI MCC has changed, that is a SIM has been detected and
779 updated the Mobile Country Code. -->
780 <flag name="mcc" value="0x0001" />
781 <!-- The IMSI MNC has changed, that is a SIM has been detected and
782 updated the Mobile Network Code. -->
783 <flag name="mnc" value="0x0002" />
784 <!-- The locale has changed, that is the user has selected a new
785 language that text should be displayed in. -->
786 <flag name="locale" value="0x0004" />
787 <!-- The touchscreen has changed. Should never normally happen. -->
788 <flag name="touchscreen" value="0x0008" />
789 <!-- The keyboard type has changed, for example the user has plugged
790 in an external keyboard. -->
791 <flag name="keyboard" value="0x0010" />
792 <!-- The keyboard or navigation accessibility has changed, for example
793 the user has slid the keyboard out to expose it. Note that
794 despite its name, this applied to any accessibility: keyboard
796 <flag name="keyboardHidden" value="0x0020" />
797 <!-- The navigation type has changed. Should never normally happen. -->
798 <flag name="navigation" value="0x0040" />
799 <!-- The screen orientation has changed, that is the user has
800 rotated the device. -->
801 <flag name="orientation" value="0x0080" />
802 <!-- The screen layout has changed. This might be caused by a
803 different display being activated. -->
804 <flag name="screenLayout" value="0x0100" />
805 <!-- The global user interface mode has changed. For example,
806 going in or out of car mode, night mode changing, etc. -->
807 <flag name="uiMode" value="0x0200" />
808 <!-- The current available screen size has changed. If applications don't
809 target at least {@link android.os.Build.VERSION_CODES#HONEYCOMB_MR2}
810 then the activity will always handle this itself (the change
811 will not result in a restart). This represents a change in the
812 currently available size, so will change when the user switches
813 between landscape and portrait. -->
814 <flag name="screenSize" value="0x0400" />
815 <!-- The physical screen size has changed. If applications don't
816 target at least {@link android.os.Build.VERSION_CODES#HONEYCOMB_MR2}
817 then the activity will always handle this itself (the change
818 will not result in a restart). This represents a change in size
819 regardless of orientation, so will only change when the actual
820 physical screen size has changed such as switching to an external
822 <flag name="smallestScreenSize" value="0x0800" />
823 <!-- The display density has changed. This might be caused by the user
824 specifying a different display scale, or it might be caused by a
825 different display being activated. -->
826 <flag name="density" value="0x1000" />
827 <!-- The layout direction has changed. For example going from LTR to RTL. -->
828 <flag name="layoutDirection" value="0x2000" />
829 <!-- The font scaling factor has changed, that is the user has
830 selected a new global font size. -->
831 <flag name="fontScale" value="0x40000000" />
834 <!-- Indicate that the activity can be launched as the embedded child of another
835 activity. Particularly in the case where the child lives in a container
836 such as a Display owned by another activity.
838 <p>The default value of this attribute is <code>false</code>. -->
839 <attr name="allowEmbedded" format="boolean" />
841 <!-- Descriptive text for the associated data. -->
842 <attr name="description" format="reference" />
844 <!-- The name of the application package that an Instrumentation object
845 will run against. -->
846 <attr name="targetPackage" format="string" />
848 <!-- Flag indicating that an Instrumentation class wants to take care
849 of starting/stopping profiling itself, rather than relying on
850 the default behavior of profiling the complete time it is running.
851 This allows it to target profiling data at a specific set of
853 <attr name="handleProfiling" format="boolean" />
855 <!-- Flag indicating that an Instrumentation class should be run as a
857 <attr name="functionalTest" format="boolean" />
859 <!-- The touch screen type used by an application. -->
860 <attr name="reqTouchScreen">
861 <enum name="undefined" value="0" />
862 <enum name="notouch" value="1" />
863 <enum name="stylus" value="2" />
864 <enum name="finger" value="3" />
867 <!-- The input method preferred by an application. -->
868 <attr name="reqKeyboardType">
869 <enum name="undefined" value="0" />
870 <enum name="nokeys" value="1" />
871 <enum name="qwerty" value="2" />
872 <enum name="twelvekey" value="3" />
875 <!-- Application's requirement for a hard keyboard -->
876 <attr name="reqHardKeyboard" format="boolean" />
878 <!-- The navigation device preferred by an application. -->
879 <attr name="reqNavigation">
880 <enum name="undefined" value="0" />
881 <enum name="nonav" value="1" />
882 <enum name="dpad" value="2" />
883 <enum name="trackball" value="3" />
884 <enum name="wheel" value="4" />
887 <!-- Application's requirement for five way navigation -->
888 <attr name="reqFiveWayNav" format="boolean" />
890 <!-- The name of the class subclassing <code>BackupAgent</code> to manage
891 backup and restore of the application's data on external storage. -->
892 <attr name="backupAgent" format="string" />
894 <!-- Whether to allow the application to participate in the backup
895 and restore infrastructure. If this attribute is set to <code>false</code>,
896 no backup or restore of the application will ever be performed, even by a
897 full-system backup that would otherwise cause all application data to be saved
898 via adb. The default value of this attribute is <code>true</code>. -->
899 <attr name="allowBackup" format="boolean" />
901 <!-- Applications will set this in their manifest to opt-in to or out of full app data back-up
902 and restore. Alternatively they can set it to an xml resource within their app that will
903 be parsed by the BackupAgent to selectively backup files indicated within that xml. -->
904 <attr name="fullBackupContent" format="reference|boolean" />
906 <!-- Indicates that even though the application provides a <code>BackupAgent</code>,
907 only full-data streaming backup operations are to be performed to save the app's
908 data. This lets the app rely on full-data backups while still participating in
909 the backup and restore process via the BackupAgent's full-data backup APIs.
910 When this attribute is <code>true</code> the app's BackupAgent overrides of
911 the onBackup() and onRestore() callbacks can be empty stubs. -->
912 <attr name="fullBackupOnly" format="boolean" />
914 <!-- Whether the application in question should be terminated after its
915 settings have been restored during a full-system restore operation.
916 Single-package restore operations will never cause the application to
917 be shut down. Full-system restore operations typically only occur once,
918 when the phone is first set up. Third-party applications will not usually
919 need to use this attribute.
921 <p>The default is <code>true</code>, which means that after the application
922 has finished processing its data during a full-system restore, it will be
924 <attr name="killAfterRestore" format="boolean" />
926 <!-- @deprecated This attribute is not used by the Android operating system. -->
927 <attr name="restoreNeedsApplication" format="boolean" />
929 <!-- Indicate that the application is prepared to attempt a restore of any
930 backed-up dataset, even if the backup is apparently from a newer version
931 of the application than is currently installed on the device. Setting
932 this attribute to <code>true</code> will permit the Backup Manager to
933 attempt restore even when a version mismatch suggests that the data are
934 incompatible. <em>Use with caution!</em>
936 <p>The default value of this attribute is <code>false</code>. -->
937 <attr name="restoreAnyVersion" format="boolean" />
939 <!-- Indicates that full-data backup operations for this application may
940 be performed even if the application is in a foreground-equivalent
941 state. <em>Use with caution!</em> Setting this flag to <code>true</code>
942 can impact app behavior while the user is interacting with the device.
944 <p>If unspecified, the default value of this attribute is <code>false</code>,
945 which means that the OS will avoid backing up the application while it is
946 running in the foreground (such as a music app that is actively playing
947 music via a service in the startForeground() state). -->
948 <attr name="backupInForeground" format="boolean" />
950 <!-- The default install location defined by an application. -->
951 <attr name="installLocation">
952 <!-- Let the system decide ideal install location -->
953 <enum name="auto" value="0" />
954 <!-- Explicitly request to be installed on internal phone storage
956 <enum name="internalOnly" value="1" />
957 <!-- Prefer to be installed on SD card. There is no guarantee that
958 the system will honor this request. The application might end
959 up being installed on internal storage if external media
960 is unavailable or too full. -->
961 <enum name="preferExternal" value="2" />
964 <!-- Extra options for an activity's UI. Applies to either the {@code <activity>} or
965 {@code <application>} tag. If specified on the {@code <application>}
966 tag these will be considered defaults for all activities in the
968 <attr name="uiOptions">
969 <!-- No extra UI options. This is the default. -->
970 <flag name="none" value="0" />
971 <!-- Split the options menu into a separate bar at the bottom of
972 the screen when severely constrained for horizontal space.
973 (e.g. portrait mode on a phone.) Instead of a small number
974 of action buttons appearing in the action bar at the top
975 of the screen, the action bar will split into the top navigation
976 section and the bottom menu section. Menu items will not be
977 split across the two bars; they will always appear together. -->
978 <flag name="splitActionBarWhenNarrow" value="1" />
981 <!-- The name of the logical parent of the activity as it appears in the manifest. -->
982 <attr name="parentActivityName" format="string" />
984 <!-- Define how an activity persist across reboots. Activities defined as "never" will not
985 be persisted. Those defined as "always" will be persisted. Those defined as "taskOnly"
986 will persist the root activity of the task only. See below for more detail as to
987 what gets persisted. -->
988 <attr name="persistableMode">
989 <!-- The default. If this activity forms the root of a task then that task will be
990 persisted across reboots but only the launching intent will be used. If the task
991 relinquishes its identity then the intent used is that of the topmost inherited
992 identity. All activities above this activity in the task will not be persisted.
993 In addition this activity will not be passed a PersistableBundle into which it
994 could have stored its state. -->
995 <enum name="persistRootOnly" value="0" />
996 <!-- If this activity forms the root of a task then that task will not be persisted
998 <enum name="persistNever" value="1" />
999 <!-- If this activity forms the root of a task then the task and this activity will
1000 be persisted across reboots. If the activity above this activity is also
1001 tagged with the attribute <code>"persist"</code> then it will be persisted as well.
1002 And so on up the task stack until either an activity without the
1003 <code>persistableMode="persistAcrossReboots"</code> attribute or one that was launched
1004 with the flag Intent.FLAG_CLEAR_TASK_WHEN_RESET is encountered.
1006 <p>Activities that are declared with the persistAcrossReboots attribute will be
1007 provided with a PersistableBundle in onSavedInstanceState(), These activities may
1008 use this PeristableBundle to save their state. Then, following a reboot, that
1009 PersistableBundle will be provided back to the activity in its onCreate() method. -->
1010 <enum name="persistAcrossReboots" value="2" />
1013 <!-- This attribute specifies that an activity shall become the root activity of a
1014 new task each time it is launched. Using this attribute permits the user to
1015 have multiple documents from the same applications appear in the recent tasks list.
1017 <p>Such a document is any kind of item for which an application may want to
1018 maintain multiple simultaneous instances. Examples might be text files, web
1019 pages, spreadsheets, or emails. Each such document will be in a separate
1020 task in the recent taskss list.
1022 <p>This attribute is equivalent to adding the flag {@link
1023 android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT} to every Intent used to launch
1026 <p>The documentLaunchMode attribute may be assigned one of four values, "none",
1027 "intoExisting", "always" and "never", described in detail below. For values other than
1028 <code>none</code> and <code>never</code> the activity must be defined with
1029 {@link android.R.attr#launchMode} <code>standard</code>.
1030 If this attribute is not specified, <code>none</code> will be used.
1031 Note that <code>none</code> can be overridden at run time if the Intent used
1032 to launch it contains the flag {@link android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT
1033 Intent.FLAG_ACTIVITY_NEW_DOCUMENT}.
1034 Similarly <code>intoExisting</code> will be overridden by the flag
1035 {@link android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT
1036 Intent.FLAG_ACTIVITY_NEW_DOCUMENT} combined with
1037 {@link android.content.Intent#FLAG_ACTIVITY_MULTIPLE_TASK
1038 Intent.FLAG_ACTIVITY_MULTIPLE_TASK}. If the value of
1039 documentLaunchModes is <code>never</code> then any use of
1040 {@link android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT
1041 Intent.FLAG_ACTIVITY_NEW_DOCUMENT} to launch this activity will be ignored. -->
1042 <attr name="documentLaunchMode">
1043 <!-- The default mode, which will create a new task only when
1044 {@link android.content.Intent#FLAG_ACTIVITY_NEW_TASK
1045 Intent.FLAG_ACTIVITY_NEW_TASK} is set. -->
1046 <enum name="none" value="0" />
1047 <!-- All tasks will be searched for one whose base Intent's ComponentName and
1048 data URI match those of the launching Intent. If such a task is found
1049 that task will be cleared and restarted with the root activity receiving a call
1050 to {@link android.app.Activity#onNewIntent Activity.onNewIntent}. If no
1051 such task is found a new task will be created.
1052 <p>This is the equivalent of launching an activity with {@link
1053 android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT Intent.FLAG_ACTIVITY_NEW_DOCUMENT}
1054 set and without {@link android.content.Intent#FLAG_ACTIVITY_MULTIPLE_TASK
1055 Intent.FLAG_ACTIVITY_MULTIPLE_TASK} set. -->
1056 <enum name="intoExisting" value="1" />
1057 <!-- A new task rooted at this activity will be created. This will happen whether or
1058 not there is an existing task whose ComponentName and data URI match
1059 that of the launcing intent This is the equivalent of launching an activity
1061 android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT Intent.FLAG_ACTIVITY_NEW_DOCUMENT}
1062 and {@link android.content.Intent#FLAG_ACTIVITY_MULTIPLE_TASK
1063 Intent.FLAG_ACTIVITY_MULTIPLE_TASK} both set. -->
1064 <enum name="always" value="2" />
1065 <!-- This activity will not be launched into a new document even if the Intent contains
1066 {@link android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT
1067 Intent.FLAG_ACTIVITY_NEW_DOCUMENT}. This gives the activity writer ultimate
1068 control over how their activity is used. Note that applications prior to api
1069 21 will default to documentLaunchMode="none" so only activities that explicitly
1070 opt out with <code>"never"</code> may do so. -->
1071 <enum name="never" value="3" />
1074 <!-- The maximum number of entries of tasks rooted at this activity in the recent task list.
1075 When this number of entries is reached the least recently used instance of this activity
1076 will be removed from recents. The value will be clamped between 1 and 100 inclusive.
1077 The default value for this if it is not specified is 15. -->
1078 <attr name="maxRecents" format="integer" />
1080 <!-- Tasks launched by activities with this attribute will remain in the recent tasks
1081 list until the last activity in the task is completed. When that happens the task
1082 will be automatically removed from the recent tasks list. This overrides the caller's
1083 use of {@link android.content.Intent#FLAG_ACTIVITY_RETAIN_IN_RECENTS
1084 Intent.FLAG_ACTIVITY_RETAIN_IN_RECENTS} -->
1085 <attr name="autoRemoveFromRecents" format="boolean" />
1087 <!-- Tasks whose root has this attribute set to true will replace baseIntent with that of the
1088 next activity in the task. If the next activity also has this attribute set to true then
1089 it will yield the baseIntent to any activity that it launches in the same task. This
1090 continues until an activity is encountered which has this attribute set to false. False
1091 is the default. This attribute set to true also permits activity's use of the
1092 TaskDescription to change labels, colors and icons in the recent task list. -->
1093 <attr name="relinquishTaskIdentity" format="boolean" />
1095 <!-- Indicate that it is okay for this activity be resumed while the previous
1096 activity is in the process of pausing, without waiting for the previous pause
1097 to complete. Use this with caution: your activity can not acquire any exclusive
1098 resources (such as opening the camera or recording audio) when it launches, or it
1099 may conflict with the previous activity and fail.
1101 <p>The default value of this attribute is <code>false</code>. -->
1102 <attr name="resumeWhilePausing" format="boolean" />
1104 <!-- Indicates that it is okay for this activity to be resized to any dimension. Intended for a
1105 multi-window device where there can be multiple activities of various sizes on the screen
1108 <p>The default value is <code>false</code> for applications with
1109 <code>targetSdkVersion</code> lesser than {@link android.os.Build.VERSION_CODES#N} and
1110 <code>true</code> otherwise.
1112 <p>NOTE: A task's root activity value is applied to all additional activities launched in
1113 the task. That is if the root activity of a task is resizeable then the system will treat
1114 all other activities in the task as resizeable and will not if the root activity isn't
1117 <p>NOTE: The value of {@link android.R.attr#screenOrientation} is ignored for
1118 resizeable activities when in multi-window mode. -->
1119 <attr name="resizeableActivity" format="boolean" />
1121 <!-- Indicates that the activity supports the picture-in-picture (PiP) form of multi-window.
1122 While it makes sense to be able to resize most activities types in multi-window mode when
1123 {@link android.R.attr#resizeableActivity} is set. It only makes sense to put specific types
1124 of activities in PiP mode of multi-window. For example, activities that play video. When
1125 set the activity will be allowed to enter PiP mode when the system deems it appropriate on
1126 devices that support PiP.
1128 <p>The default value is <code>false</code> for applications with
1129 <code>targetSdkVersion</code> lesser than {@link android.os.Build.VERSION_CODES#N} and
1130 <code>true</code> otherwise.
1132 <p>NOTE: Attribute is only used if {@link android.R.attr#resizeableActivity} is true. -->
1133 <attr name="supportsPictureInPicture" format="boolean" />
1135 <!-- This value indicates how tasks rooted at this activity will behave in lockTask mode.
1136 While in lockTask mode the system will not launch non-permitted tasks until
1137 lockTask mode is disabled.
1138 <p>While in lockTask mode with multiple permitted tasks running, each launched task is
1139 permitted to finish, transitioning to the previous locked task, until there is only one
1140 task remaining. At that point the last task running is not permitted to finish, unless it
1141 uses the value always. -->
1142 <attr name="lockTaskMode">
1143 <!-- This is the default value. Tasks will not launch into lockTask mode but can be
1144 placed there by calling {@link android.app.Activity#startLockTask}. If a task with
1145 this mode has been whitelisted using {@link
1146 android.app.admin.DevicePolicyManager#setLockTaskPackages} then calling
1147 {@link android.app.Activity#startLockTask} will enter lockTask mode immediately,
1148 otherwise the user will be presented with a dialog to approve entering pinned mode.
1149 <p>If the system is already in lockTask mode when a new task rooted at this activity
1150 is launched that task will or will not start depending on whether the package of this
1151 activity has been whitelisted.
1152 <p>Tasks rooted at this activity can only exit lockTask mode using
1153 {@link android.app.Activity#stopLockTask}. -->
1154 <enum name="normal" value="0"/>
1155 <!-- Tasks will not launch into lockTask mode and cannot be placed there using
1156 {@link android.app.Activity#startLockTask} or be pinned from the Overview screen.
1157 If the system is already in lockTask mode when a new task rooted at this activity is
1158 launched that task will not be started.
1159 <p>Note: This mode is only available to system and privileged applications.
1160 Non-privileged apps with this value will be treated as normal.
1162 <enum name="never" value="1"/>
1163 <!-- Tasks rooted at this activity will always launch into lockTask mode. If the system is
1164 already in lockTask mode when this task is launched then the new task will be launched
1165 on top of the current task. Tasks launched in this mode are capable of exiting
1166 lockTask mode using {@link android.app.Activity#finish()}.
1167 <p>Note: This mode is only available to system and privileged applications.
1168 Non-privileged apps with this value will be treated as normal.
1170 <enum name="always" value="2"/>
1171 <!-- If the DevicePolicyManager (DPM) authorizes this package ({@link
1172 android.app.admin.DevicePolicyManager#setLockTaskPackages}) then this mode is
1173 identical to always, except that the activity needs to call
1174 {@link android.app.Activity#stopLockTask} before being able to finish if it is the last
1176 If the DPM does not authorize this package then this mode is identical to normal. -->
1177 <enum name="if_whitelisted" value="3"/>
1179 <!-- When set installer will extract native libraries. If set to false
1180 libraries in the apk must be stored and page-aligned. -->
1181 <attr name="extractNativeLibs" format="boolean"/>
1183 <!-- Specify whether an activity intent filter will need to be verified thru its set
1184 of data URIs. This will only be used when the Intent's action is set to
1185 {@link android.content.Intent#ACTION_VIEW Intent.ACTION_VIEW} and the Intent's category is
1186 set to {@link android.content.Intent#CATEGORY_BROWSABLE Intent.CATEGORY_BROWSABLE} and the
1187 intern filter data scheme is set to "http" or "https". When set to true, the intent filter
1188 will need to use its data tag for getting the URIs to verify with.
1190 For each URI, an HTTPS network request will be done to <code>/.well-known/statements.json</code>
1191 host to verify that the web site is okay with the app intercepting the URI.
1193 <attr name="autoVerify" format="boolean" />
1195 <!-- An XML resource with the application's Network Security Config. -->
1196 <attr name="networkSecurityConfig" format="reference" />
1198 <!-- The <code>manifest</code> tag is the root of an
1199 <code>AndroidManifest.xml</code> file,
1200 describing the contents of an Android package (.apk) file. One
1201 attribute must always be supplied: <code>package</code> gives a
1202 unique name for the package, using a Java-style naming convention
1203 to avoid name collisions. For example, applications published
1204 by Google could have names of the form
1205 <code>com.google.app.<em>appname</em></code>
1207 <p>Inside of the manifest tag, may appear the following tags
1208 in any order: {@link #AndroidManifestPermission permission},
1209 {@link #AndroidManifestPermissionGroup permission-group},
1210 {@link #AndroidManifestPermissionTree permission-tree},
1211 {@link #AndroidManifestUsesSdk uses-sdk},
1212 {@link #AndroidManifestUsesPermission uses-permission},
1213 {@link #AndroidManifestUsesConfiguration uses-configuration},
1214 {@link #AndroidManifestApplication application},
1215 {@link #AndroidManifestInstrumentation instrumentation},
1216 {@link #AndroidManifestUsesFeature uses-feature}. -->
1217 <declare-styleable name="AndroidManifest">
1218 <attr name="versionCode" />
1219 <attr name="versionName" />
1220 <attr name="revisionCode" />
1221 <attr name="sharedUserId" />
1222 <attr name="sharedUserLabel" />
1223 <attr name="installLocation" />
1224 </declare-styleable>
1226 <!-- The <code>application</code> tag describes application-level components
1227 contained in the package, as well as general application
1228 attributes. Many of the attributes you can supply here (such
1229 as theme, label, icon, permission, process, taskAffinity,
1230 and allowTaskReparenting) serve
1231 as default values for the corresponding attributes of components
1232 declared inside of the application.
1234 <p>Inside of this element you specify what the application contains,
1235 using the elements {@link #AndroidManifestProvider provider},
1236 {@link #AndroidManifestService service},
1237 {@link #AndroidManifestReceiver receiver},
1238 {@link #AndroidManifestActivity activity},
1239 {@link #AndroidManifestActivityAlias activity-alias}, and
1240 {@link #AndroidManifestUsesLibrary uses-library}. The application tag
1241 appears as a child of the root {@link #AndroidManifest manifest} tag in
1242 an application's manifest file. -->
1243 <declare-styleable name="AndroidManifestApplication" parent="AndroidManifest">
1244 <!-- The (optional) fully-qualified name for a subclass of
1245 {@link android.app.Application} that the system instantiates before
1246 any other class when an app's process starts. Most applications
1247 don't need this attribute. If it's not specified, the system
1248 instantiates the base Application class instead.-->
1249 <attr name="name" />
1250 <attr name="theme" />
1251 <attr name="label" />
1252 <attr name="icon" />
1253 <attr name="roundIcon" />
1254 <attr name="banner" />
1255 <attr name="logo" />
1256 <attr name="description" />
1257 <attr name="permission" />
1258 <attr name="process" />
1259 <attr name="taskAffinity" />
1260 <attr name="allowTaskReparenting" />
1261 <!-- Indicate whether this application contains code. If set to false,
1262 there is no code associated with it and thus the system will not
1263 try to load its code when launching components. The default is true
1264 for normal behavior. -->
1265 <attr name="hasCode" format="boolean" />
1266 <attr name="persistent" />
1267 <attr name="requiredForAllUsers" />
1268 <!-- Specify whether the components in this application are enabled or not (that is, can be
1269 instantiated by the system).
1270 If "false", it overrides any component specific values (a value of "true" will not
1271 override the component specific values). -->
1272 <attr name="enabled" />
1273 <attr name="debuggable" />
1274 <attr name="vmSafeMode" />
1275 <attr name="hardwareAccelerated" />
1276 <!-- Name of activity to be launched for managing the application's space on the device. -->
1277 <attr name="manageSpaceActivity" />
1278 <attr name="allowClearUserData" />
1279 <attr name="testOnly" />
1280 <attr name="backupAgent" />
1281 <attr name="allowBackup" />
1282 <attr name="fullBackupOnly" />
1283 <attr name="fullBackupContent" />
1284 <attr name="killAfterRestore" />
1285 <attr name="restoreNeedsApplication" />
1286 <attr name="restoreAnyVersion" />
1287 <attr name="backupInForeground" />
1288 <!-- Request that your application's processes be created with
1289 a large Dalvik heap. This applies to <em>all</em> processes
1290 created for the application. It only applies to the first
1291 application loaded into a process; if using a sharedUserId
1292 to allow multiple applications to use a process, they all must
1293 use this option consistently or will get unpredictable results. -->
1294 <attr name="largeHeap" format="boolean" />
1295 <!-- Declare that this application can't participate in the normal
1296 state save/restore mechanism. Since it is not able to save and
1297 restore its state on demand,
1298 it can not participate in the normal activity lifecycle. It will
1299 not be killed while in the background; the user must explicitly
1300 quit it. Only one such app can be running at a time; if the user
1301 tries to launch a second such app, they will be prompted
1302 to quit the first before doing so. While the
1303 application is running, the user will be informed of this.
1305 <attr name="cantSaveState" format="boolean" />
1306 <attr name="uiOptions" />
1307 <!-- Declare that your application will be able to deal with RTL (right to left) layouts.
1308 If set to false (default value), your application will not care about RTL layouts. -->
1309 <attr name="supportsRtl" format="boolean" />
1310 <!-- Declare that this application requires access to restricted accounts of a certain
1311 type. The default value is null and restricted accounts won\'t be visible to this
1312 application. The type should correspond to the account authenticator type, such as
1314 <attr name="restrictedAccountType" format="string"/>
1315 <!-- Declare that this application requires an account of a certain
1316 type. The default value is null and indicates that the application can work without
1317 any accounts. The type should correspond to the account authenticator type, such as
1319 <attr name="requiredAccountType" format="string"/>
1320 <attr name="isGame" />
1321 <!-- Declare that this application may use cleartext traffic, such as HTTP rather than
1322 HTTPS; WebSockets rather than WebSockets Secure; XMPP, IMAP, STMP without STARTTLS or
1323 TLS). Defaults to true. If set to false {@code false}, the application declares that it
1324 does not intend to use cleartext network traffic, in which case platform components
1325 (e.g. HTTP stacks, {@code DownloadManager}, {@code MediaPlayer}) will refuse
1326 applications's requests to use cleartext traffic. Third-party libraries are encouraged
1327 to honor this flag as well. -->
1328 <attr name="usesCleartextTraffic" />
1329 <attr name="multiArch" />
1330 <attr name="extractNativeLibs" />
1331 <attr name="defaultToDeviceProtectedStorage" format="boolean" />
1332 <attr name="directBootAware" />
1333 <attr name="resizeableActivity" />
1334 <attr name="networkSecurityConfig" />
1335 </declare-styleable>
1336 <!-- The <code>permission</code> tag declares a security permission that can be
1337 used to control access from other packages to specific components or
1338 features in your package (or other packages). See the
1339 <a href="{@docRoot}guide/topics/security/security.html">Security and Permissions</a>
1340 document for more information on permissions.
1342 <p>This appears as a child tag of the root
1343 {@link #AndroidManifest manifest} tag. -->
1344 <declare-styleable name="AndroidManifestPermission" parent="AndroidManifest">
1345 <!-- Required public name of the permission, which other components and
1346 packages will use when referring to this permission. This is a string using
1347 Java-style scoping to ensure it is unique. The prefix will often
1348 be the same as our overall package name, for example
1349 "com.mycompany.android.myapp.SomePermission". -->
1350 <attr name="name" />
1351 <attr name="label" />
1352 <attr name="icon" />
1353 <attr name="roundIcon" />
1354 <attr name="banner" />
1355 <attr name="logo" />
1356 <attr name="permissionGroup" />
1357 <attr name="description" />
1358 <attr name="protectionLevel" />
1359 <attr name="permissionFlags" />
1360 </declare-styleable>
1362 <!-- The <code>permission-group</code> tag declares a logical grouping of
1363 related permissions.
1365 <p>Note that this tag does not declare a permission itself, only
1366 a namespace in which further permissions can be placed. See
1367 the {@link #AndroidManifestPermission <permission>} tag for
1370 <p>This appears as a child tag of the root
1371 {@link #AndroidManifest manifest} tag. -->
1372 <declare-styleable name="AndroidManifestPermissionGroup" parent="AndroidManifest">
1373 <!-- Required public name of the permission group, permissions will use
1374 to specify the group they are in. This is a string using
1375 Java-style scoping to ensure it is unique. The prefix will often
1376 be the same as our overall package name, for example
1377 "com.mycompany.android.myapp.SomePermission". -->
1378 <attr name="name" />
1379 <attr name="label" />
1380 <attr name="icon" />
1381 <attr name="roundIcon" />
1382 <attr name="banner" />
1383 <attr name="logo" />
1384 <attr name="description" />
1385 <attr name="permissionGroupFlags" />
1386 <attr name="priority" />
1387 </declare-styleable>
1389 <!-- The <code>permission-tree</code> tag declares the base of a tree of
1390 permission values: it declares that this package has ownership of
1391 the given permission name, as well as all names underneath it
1392 (separated by '.'). This allows you to use the
1393 {@link android.content.pm.PackageManager#addPermission
1394 PackageManager.addPermission()} method to dynamically add new
1395 permissions under this tree.
1397 <p>Note that this tag does not declare a permission itself, only
1398 a namespace in which further permissions can be placed. See
1399 the {@link #AndroidManifestPermission <permission>} tag for
1402 <p>This appears as a child tag of the root
1403 {@link #AndroidManifest manifest} tag. -->
1404 <declare-styleable name="AndroidManifestPermissionTree" parent="AndroidManifest">
1405 <!-- Required public name of the permission tree, which is the base name
1406 of all permissions under it. This is a string using
1407 Java-style scoping to ensure it is unique. The prefix will often
1408 be the same as our overall package name, for example
1409 "com.mycompany.android.myapp.SomePermission". A permission tree name
1410 must have more than two segments in its path; that is,
1411 "com.me.foo" is okay, but not "com.me" or "com". -->
1412 <attr name="name" />
1413 <attr name="label" />
1414 <attr name="icon" />
1415 <attr name="roundIcon" />
1416 <attr name="banner" />
1417 <attr name="logo" />
1418 </declare-styleable>
1420 <!-- The <code>uses-permission</code> tag requests a
1421 {@link #AndroidManifestPermission <permission>} that the containing
1422 package must be granted in order for it to operate correctly. For runtime
1423 permissions, i.e. ones with <code>dangerous</code> protection level, on a
1424 platform that supports runtime permissions, the permission will not be
1425 granted until the app explicitly requests it at runtime and the user approves
1426 the grant. You cannot request at runtime permissions that are not declared
1427 as used in the manifest. See the
1428 <a href="{@docRoot}guide/topics/security/security.html">Security and Permissions</a>
1429 document for more information on permissions. Also available is a
1430 {@link android.Manifest.permission list of permissions} included
1431 with the base platform.
1433 <p>This appears as a child tag of the root
1434 {@link #AndroidManifest manifest} tag. -->
1435 <declare-styleable name="AndroidManifestUsesPermission" parent="AndroidManifest">
1436 <!-- Required name of the permission you use, as published with the
1437 corresponding name attribute of a
1438 {@link android.R.styleable#AndroidManifestPermission <permission>}
1439 tag; often this is one of the {@link android.Manifest.permission standard
1440 system permissions}. -->
1441 <attr name="name" />
1442 <!-- Optional: specify the maximum version of the Android OS for which the
1443 application wishes to request the permission. When running on a version
1444 of Android higher than the number given here, the permission will not
1446 <attr name="maxSdkVersion" format="integer" />
1447 </declare-styleable>
1449 <!-- The <code>uses-configuration</code> tag specifies
1450 a specific hardware configuration value used by the application.
1451 For example an application might specify that it requires
1452 a physical keyboard or a particular navigation method like
1453 trackball. Multiple such attribute values can be specified by the
1456 <p>This appears as a child tag of the root
1457 {@link #AndroidManifest manifest} tag.
1459 @deprecated Use <code>feature-group</code> instead.-->
1460 <declare-styleable name="AndroidManifestUsesConfiguration" parent="AndroidManifest">
1461 <!-- The type of touch screen used by an application. -->
1462 <attr name="reqTouchScreen" />
1463 <attr name="reqKeyboardType" />
1464 <attr name="reqHardKeyboard" />
1465 <attr name="reqNavigation" />
1466 <attr name="reqFiveWayNav" />
1467 </declare-styleable>
1469 <!-- The <code>uses-feature</code> tag specifies a specific device
1470 hardware or software feature used by the application. For
1471 example an application might specify that it requires
1472 a camera. Multiple attribute values can be specified by the
1475 <p>This appears as a child tag of the root
1476 {@link #AndroidManifest manifest} tag. -->
1477 <declare-styleable name="AndroidManifestUsesFeature" parent="AndroidManifest">
1478 <!-- The name of the feature that is being used. -->
1479 <attr name="name" />
1480 <!-- The version of the feature that is being used. -->
1481 <attr name="version" format="integer" />
1482 <!-- The GLES driver version number needed by an application.
1483 The higher 16 bits represent the major number and the lower 16 bits
1484 represent the minor number. For example for GL 1.2 referring to
1485 0x00000102, the actual value should be set as 0x00010002. -->
1486 <attr name="glEsVersion" format="integer" />
1487 <!-- Specify whether this feature is required for the application.
1488 The default is true, meaning the application requires the
1489 feature, and does not want to be installed on devices that
1490 don't support it. If you set this to false, then this will
1491 not impose a restriction on where the application can be
1493 <attr name="required" format="boolean" />
1494 </declare-styleable>
1496 <!-- The <code>feature-group</code> tag specifies
1497 a set of one or more <code>uses-feature</code> elements that
1498 the application can utilize. An application uses multiple
1499 <code>feature-group</code> sets to indicate that it can support
1500 different combinations of features.
1502 <p>This appears as a child tag of the root
1503 {@link #AndroidManifest manifest} tag. -->
1504 <declare-styleable name="AndroidManifestFeatureGroup">
1505 <!-- The human-readable name of the feature group. -->
1506 <attr name="label" />
1507 </declare-styleable>
1509 <!-- The <code>uses-sdk</code> tag describes the SDK features that the
1510 containing package must be running on to operate correctly.
1512 <p>This appears as a child tag of the root
1513 {@link #AndroidManifest manifest} tag. -->
1514 <declare-styleable name="AndroidManifestUsesSdk" parent="AndroidManifest">
1515 <!-- This is the minimum SDK version number that the application
1516 requires. This number is an abstract integer, from the list
1517 in {@link android.os.Build.VERSION_CODES} If
1518 not supplied, the application will work on any SDK. This
1519 may also be string (such as "Donut") if the application was built
1520 against a development branch, in which case it will only work against
1521 the development builds. -->
1522 <attr name="minSdkVersion" format="integer|string" />
1523 <!-- This is the SDK version number that the application is targeting.
1524 It is able to run on older versions (down to minSdkVersion), but
1525 was explicitly tested to work with the version specified here.
1526 Specifying this version allows the platform to disable compatibility
1527 code that are not required or enable newer features that are not
1528 available to older applications. This may also be a string
1529 (such as "Donut") if this is built against a development
1530 branch, in which case minSdkVersion is also forced to be that
1532 <attr name="targetSdkVersion" format="integer|string" />
1533 <!-- This is the maximum SDK version number that an application works
1534 on. You can use this to ensure your application is filtered out
1535 of later versions of the platform when you know you have
1536 incompatibility with them. -->
1537 <attr name="maxSdkVersion" />
1538 </declare-styleable>
1540 <!-- The <code>library</code> tag declares that this apk is providing itself
1541 as a shared library for other applications to use. It can only be used
1542 with apks that are built in to the system image. Other apks can link to
1543 it with the {@link #AndroidManifestUsesLibrary uses-library} tag.
1545 <p>This appears as a child tag of the
1546 {@link #AndroidManifestApplication application} tag. -->
1547 <declare-styleable name="AndroidManifestLibrary" parent="AndroidManifest">
1548 <!-- Required public name of the library, which other components and
1549 packages will use when referring to this library. This is a string using
1550 Java-style scoping to ensure it is unique. The name should typically
1551 be the same as the apk's package name. -->
1552 <attr name="name" />
1553 </declare-styleable>
1555 <!-- The <code>uses-libraries</code> specifies a shared library that this
1556 package requires to be linked against. Specifying this flag tells the
1557 system to include this library's code in your class loader.
1559 <p>This appears as a child tag of the
1560 {@link #AndroidManifestApplication application} tag. -->
1561 <declare-styleable name="AndroidManifestUsesLibrary" parent="AndroidManifestApplication">
1562 <!-- Required name of the library you use. -->
1563 <attr name="name" />
1564 <!-- Specify whether this library is required for the application.
1565 The default is true, meaning the application requires the
1566 library, and does not want to be installed on devices that
1567 don't support it. If you set this to false, then this will
1568 allow the application to be installed even if the library
1569 doesn't exist, and you will need to check for its presence
1570 dynamically at runtime. -->
1571 <attr name="required" />
1572 </declare-styleable>
1574 <!-- The <code>supports-screens</code> specifies the screen dimensions an
1575 application supports. By default a modern application supports all
1576 screen sizes and must explicitly disable certain screen sizes here;
1577 older applications are assumed to only support the traditional normal
1578 (HVGA) screen size. Note that screen size is a separate axis from
1579 density, and is determined as the available pixels to an application
1580 after density scaling has been applied.
1582 <p>This appears as a child tag of the
1583 {@link #AndroidManifest manifest} tag. -->
1584 <declare-styleable name="AndroidManifestSupportsScreens" parent="AndroidManifest">
1585 <!-- Starting with {@link android.os.Build.VERSION_CODES#HONEYCOMB_MR2},
1586 this is the new way to specify the minimum screen size an application is
1587 compatible with. This attribute provides the required minimum
1588 "smallest screen width" (as per the -swNNNdp resource configuration)
1589 that the application can run on. For example, a typical phone
1590 screen is 320, a 7" tablet 600, and a 10" tablet 720. If the
1591 smallest screen width of the device is below the value supplied here,
1592 then the application is considered incompatible with that device.
1593 If not supplied, then any old smallScreens, normalScreens, largeScreens,
1594 or xlargeScreens attributes will be used instead. -->
1595 <attr name="requiresSmallestWidthDp" format="integer" />
1596 <!-- Starting with {@link android.os.Build.VERSION_CODES#HONEYCOMB_MR2},
1597 this is the new way to specify the largest screens an application is
1598 compatible with. This attribute provides the maximum
1599 "smallest screen width" (as per the -swNNNdp resource configuration)
1600 that the application is designed for. If this value is smaller than
1601 the "smallest screen width" of the device it is running on, the user
1602 is offered to run it in a compatibility mode that emulates a
1603 smaller screen and zooms it to fit the screen. Currently the compatibility mode only
1604 emulates phone screens with a 320dp width, so compatibility mode is not applied if the
1605 value for compatibleWidthLimitDp is larger than 320. -->
1606 <attr name="compatibleWidthLimitDp" format="integer" />
1607 <!-- Starting with {@link android.os.Build.VERSION_CODES#HONEYCOMB_MR2},
1608 this is the new way to specify the screens an application is
1609 compatible with. This attribute provides the maximum
1610 "smallest screen width" (as per the -swNNNdp resource configuration)
1611 that the application can work well on. If this value is smaller than
1612 the "smallest screen width" of the device it is running on, the
1613 application will be forced in to screen compatibility mode with
1614 no way for the user to turn it off. Currently the compatibility mode only
1615 emulates phone screens with a 320dp width, so compatibility mode is not applied if the
1616 value for largestWidthLimitDp is larger than 320. -->
1617 <attr name="largestWidthLimitDp" format="integer" />
1618 <!-- Indicates whether the application supports smaller screen form-factors.
1619 A small screen is defined as one with a smaller aspect ratio than
1620 the traditional HVGA screen; that is, for a portrait screen, less
1621 tall than an HVGA screen. In practice, this means a QVGA low
1622 density or VGA high density screen. An application that does
1623 not support small screens <em>will not be available</em> for
1624 small screen devices, since there is little the platform can do
1625 to make such an application work on a smaller screen. -->
1626 <attr name="smallScreens" format="boolean" />
1627 <!-- Indicates whether an application supports the normal screen
1628 form-factors. Traditionally this is an HVGA normal density
1629 screen, but WQVGA low density and WVGA high density are also
1630 considered to be normal. This attribute is true by default,
1631 and applications currently should leave it that way. -->
1632 <attr name="normalScreens" format="boolean" />
1633 <!-- Indicates whether the application supports larger screen form-factors.
1634 A large screen is defined as a screen that is significantly larger
1635 than a normal phone screen, and thus may require some special care
1636 on the application's part to make good use of it. An example would
1637 be a VGA <em>normal density</em> screen, though even larger screens
1638 are certainly possible. An application that does not support
1639 large screens will be placed as a postage stamp on such a
1640 screen, so that it retains the dimensions it was originally
1642 <attr name="largeScreens" format="boolean" />
1643 <!-- Indicates whether the application supports extra large screen form-factors. -->
1644 <attr name="xlargeScreens" format="boolean" />
1645 <!-- Indicates whether the application can resize itself to newer
1646 screen sizes. This is mostly used to distinguish between old
1647 applications that may not be compatible with newly introduced
1648 screen sizes and newer applications that should be; it will be
1649 set for you automatically based on whether you are targeting
1650 a newer platform that supports more screens. -->
1651 <attr name="resizeable" format="boolean" />
1652 <!-- Indicates whether the application can accommodate any screen
1653 density. Older applications are assumed to not be able to,
1654 new ones able to. You can explicitly supply your abilities
1656 <attr name="anyDensity" format="boolean" />
1657 </declare-styleable>
1659 <!-- Private tag to declare system protected broadcast actions.
1661 <p>This appears as a child tag of the root
1662 {@link #AndroidManifest manifest} tag. -->
1663 <declare-styleable name="AndroidManifestProtectedBroadcast" parent="AndroidManifest">
1664 <attr name="name" />
1665 </declare-styleable>
1667 <!-- Private tag to declare the original package name that this package is
1668 based on. Only used for packages installed in the system image. If
1669 given, and different than the actual package name, and the given
1670 original package was previously installed on the device but the new
1671 one was not, then the data for the old one will be renamed to be
1672 for the new package.
1674 <p>This appears as a child tag of the root
1675 {@link #AndroidManifest manifest} tag. -->
1676 <declare-styleable name="AndroidManifestOriginalPackage" parent="AndroidManifest">
1677 <attr name="name" />
1678 </declare-styleable>
1680 <!-- The <code>provider</code> tag declares a
1681 {@link android.content.ContentProvider} class that is available
1682 as part of the package's application components, supplying structured
1683 access to data managed by the application.
1685 <p>This appears as a child tag of the
1686 {@link #AndroidManifestApplication application} tag. -->
1687 <declare-styleable name="AndroidManifestProvider" parent="AndroidManifestApplication">
1688 <!-- Required name of the class implementing the provider, deriving from
1689 {@link android.content.ContentProvider}. This is a fully
1690 qualified class name (for example, com.mycompany.myapp.MyProvider); as a
1691 short-hand if the first character of the class
1692 is a period then it is appended to your package name. -->
1693 <attr name="name" />
1694 <attr name="label" />
1695 <attr name="description" />
1696 <attr name="icon" />
1697 <attr name="roundIcon" />
1698 <attr name="banner" />
1699 <attr name="logo" />
1700 <attr name="process" />
1701 <attr name="authorities" />
1702 <attr name="syncable" />
1703 <attr name="readPermission" />
1704 <attr name="writePermission" />
1705 <attr name="grantUriPermissions" />
1706 <attr name="permission" />
1707 <attr name="multiprocess" />
1708 <attr name="initOrder" />
1709 <!-- Specify whether this provider is enabled or not (that is, can be instantiated by the system).
1710 It can also be specified for an application as a whole, in which case a value of "false"
1711 will override any component specific values (a value of "true" will not override the
1712 component specific values). -->
1713 <attr name="enabled" />
1714 <attr name="exported" />
1715 <attr name="singleUser" />
1716 <attr name="directBootAware" />
1717 </declare-styleable>
1719 <!-- Attributes that can be supplied in an AndroidManifest.xml
1720 <code>grant-uri-permission</code> tag, a child of the
1721 {@link #AndroidManifestProvider provider} tag, describing a specific
1722 URI path that can be granted as a permission. This tag can be
1723 specified multiple time to supply multiple paths. -->
1724 <declare-styleable name="AndroidManifestGrantUriPermission" parent="AndroidManifestProvider">
1725 <!-- Specify a URI path that must exactly match, as per
1726 {@link android.os.PatternMatcher} with
1727 {@link android.os.PatternMatcher#PATTERN_LITERAL}. -->
1728 <attr name="path" format="string" />
1729 <!-- Specify a URI path that must be a prefix to match, as per
1730 {@link android.os.PatternMatcher} with
1731 {@link android.os.PatternMatcher#PATTERN_PREFIX}. -->
1732 <attr name="pathPrefix" format="string" />
1733 <!-- Specify a URI path that matches a simple pattern, as per
1734 {@link android.os.PatternMatcher} with
1735 {@link android.os.PatternMatcher#PATTERN_SIMPLE_GLOB}.
1736 Note that because '\' is used as an escape character when
1737 reading the string from XML (before it is parsed as a pattern),
1738 you will need to double-escape: for example a literal "*" would
1739 be written as "\\*" and a literal "\" would be written as
1740 "\\\\". This is basically the same as what you would need to
1741 write if constructing the string in Java code. -->
1742 <attr name="pathPattern" format="string" />
1743 </declare-styleable>
1745 <!-- Attributes that can be supplied in an AndroidManifest.xml
1746 <code>path-permission</code> tag, a child of the
1747 {@link #AndroidManifestProvider provider} tag, describing a permission
1748 that allows access to a specific path in the provider. This tag can be
1749 specified multiple time to supply multiple paths. -->
1750 <declare-styleable name="AndroidManifestPathPermission" parent="AndroidManifestProvider">
1751 <attr name="path" />
1752 <attr name="pathPrefix" />
1753 <attr name="pathPattern" />
1754 <attr name="permission" />
1755 <attr name="readPermission" />
1756 <attr name="writePermission" />
1757 </declare-styleable>
1759 <!-- The <code>service</code> tag declares a
1760 {@link android.app.Service} class that is available
1761 as part of the package's application components, implementing
1762 long-running background operations or a rich communication API
1763 that can be called by other packages.
1765 <p>Zero or more {@link #AndroidManifestIntentFilter intent-filter}
1766 tags can be included inside of a service, to specify the Intents
1767 that can connect with it. If none are specified, the service can
1768 only be accessed by direct specification of its class name.
1769 The service tag appears as a child tag of the
1770 {@link #AndroidManifestApplication application} tag. -->
1771 <declare-styleable name="AndroidManifestService" parent="AndroidManifestApplication">
1772 <!-- Required name of the class implementing the service, deriving from
1773 {@link android.app.Service}. This is a fully
1774 qualified class name (for example, com.mycompany.myapp.MyService); as a
1775 short-hand if the first character of the class
1776 is a period then it is appended to your package name. -->
1777 <attr name="name" />
1778 <attr name="label" />
1779 <attr name="description" />
1780 <attr name="icon" />
1781 <attr name="roundIcon" />
1782 <attr name="banner" />
1783 <attr name="logo" />
1784 <attr name="permission" />
1785 <attr name="process" />
1786 <!-- Specify whether the service is enabled or not (that is, can be instantiated by the system).
1787 It can also be specified for an application as a whole, in which case a value of "false"
1788 will override any component specific values (a value of "true" will not override the
1789 component specific values). -->
1790 <attr name="enabled" />
1791 <attr name="exported" />
1792 <!-- If set to true, this service with be automatically stopped
1793 when the user remove a task rooted in an activity owned by
1794 the application. The default is false. -->
1795 <attr name="stopWithTask" format="boolean" />
1796 <!-- If set to true, this service will run under a special process
1797 that is isolated from the rest of the system. The only communication
1798 with it is through the Service API (binding and starting). -->
1799 <attr name="isolatedProcess" format="boolean" />
1800 <attr name="singleUser" />
1801 <attr name="directBootAware" />
1802 <!-- If the service is an {@link android.R.attr#isolatedProcess} service, this permits a
1803 client to bind to the service as if it were running it its own package. The service
1804 must also be {@link android.R.attr#exported} if this flag is set. -->
1805 <attr name="externalService" format="boolean" />
1806 </declare-styleable>
1808 <!-- The <code>receiver</code> tag declares an
1809 {@link android.content.BroadcastReceiver} class that is available
1810 as part of the package's application components, allowing the
1811 application to receive actions or data broadcast by other
1812 applications even if it is not currently running.
1814 <p>Zero or more {@link #AndroidManifestIntentFilter intent-filter}
1815 tags can be included inside of a receiver, to specify the Intents
1816 it will receive. If none are specified, the receiver will only
1817 be run when an Intent is broadcast that is directed at its specific
1818 class name. The receiver tag appears as a child tag of the
1819 {@link #AndroidManifestApplication application} tag. -->
1820 <declare-styleable name="AndroidManifestReceiver" parent="AndroidManifestApplication">
1821 <!-- Required name of the class implementing the receiver, deriving from
1822 {@link android.content.BroadcastReceiver}. This is a fully
1823 qualified class name (for example, com.mycompany.myapp.MyReceiver); as a
1824 short-hand if the first character of the class
1825 is a period then it is appended to your package name. -->
1826 <attr name="name" />
1827 <attr name="label" />
1828 <attr name="description" />
1829 <attr name="icon" />
1830 <attr name="roundIcon" />
1831 <attr name="banner" />
1832 <attr name="logo" />
1833 <attr name="permission" />
1834 <attr name="process" />
1835 <!-- Specify whether the receiver is enabled or not (that is, can be instantiated by the system).
1836 It can also be specified for an application as a whole, in which case a value of "false"
1837 will override any component specific values (a value of "true" will not override the
1838 component specific values). -->
1839 <attr name="enabled" />
1840 <attr name="exported" />
1841 <attr name="singleUser" />
1842 <attr name="directBootAware" />
1843 </declare-styleable>
1845 <!-- The <code>activity</code> tag declares an
1846 {@link android.app.Activity} class that is available
1847 as part of the package's application components, implementing
1848 a part of the application's user interface.
1850 <p>Zero or more {@link #AndroidManifestIntentFilter intent-filter}
1851 tags can be included inside of an activity, to specify the Intents
1852 that it can handle. If none are specified, the activity can
1853 only be started through direct specification of its class name.
1854 The activity tag appears as a child tag of the
1855 {@link #AndroidManifestApplication application} tag. -->
1856 <declare-styleable name="AndroidManifestActivity" parent="AndroidManifestApplication">
1857 <!-- Required name of the class implementing the activity, deriving from
1858 {@link android.app.Activity}. This is a fully
1859 qualified class name (for example, com.mycompany.myapp.MyActivity); as a
1860 short-hand if the first character of the class
1861 is a period then it is appended to your package name. -->
1862 <attr name="name" />
1863 <attr name="theme" />
1864 <attr name="label" />
1865 <attr name="description" />
1866 <attr name="icon" />
1867 <attr name="roundIcon" />
1868 <attr name="banner" />
1869 <attr name="logo" />
1870 <attr name="launchMode" />
1871 <attr name="screenOrientation" />
1872 <attr name="configChanges" />
1873 <attr name="permission" />
1874 <attr name="multiprocess" />
1875 <attr name="process" />
1876 <attr name="taskAffinity" />
1877 <attr name="allowTaskReparenting" />
1878 <attr name="finishOnTaskLaunch" />
1879 <attr name="finishOnCloseSystemDialogs" />
1880 <attr name="clearTaskOnLaunch" />
1881 <attr name="noHistory" />
1882 <attr name="alwaysRetainTaskState" />
1883 <attr name="stateNotNeeded" />
1884 <attr name="excludeFromRecents" />
1885 <!-- @deprecated use {@link android.R.attr#showForAllUsers} instead. -->
1886 <attr name="showOnLockScreen" />
1887 <!-- Specify whether the activity is enabled or not (that is, can be instantiated by the system).
1888 It can also be specified for an application as a whole, in which case a value of "false"
1889 will override any component specific values (a value of "true" will not override the
1890 component specific values). -->
1891 <attr name="enabled" />
1892 <attr name="exported" />
1893 <!-- Specify the default soft-input mode for the main window of
1894 this activity. A value besides "unspecified" here overrides
1895 any value in the theme. -->
1896 <attr name="windowSoftInputMode" />
1897 <attr name="immersive" />
1898 <attr name="hardwareAccelerated" />
1899 <attr name="uiOptions" />
1900 <attr name="parentActivityName" />
1901 <attr name="singleUser" />
1902 <!-- @hide This broadcast receiver or activity will only receive broadcasts for the
1904 <attr name="systemUserOnly" format="boolean" />
1905 <attr name="persistableMode" />
1906 <attr name="allowEmbedded" />
1907 <attr name="documentLaunchMode" />
1908 <attr name="maxRecents" />
1909 <attr name="autoRemoveFromRecents" />
1910 <attr name="relinquishTaskIdentity" />
1911 <attr name="resumeWhilePausing" />
1912 <attr name="resizeableActivity" />
1913 <attr name="supportsPictureInPicture" />
1914 <attr name="lockTaskMode" />
1915 <attr name="showForAllUsers" />
1916 <attr name="directBootAware" />
1917 <!-- @hide This activity is always focusable regardless of if it is in a task/stack whose
1918 activities are normally not focusable.
1919 For example, {@link android.R.attr#supportsPictureInPicture} activities are placed
1920 in a task/stack that isn't focusable. This flag allows them to be focusable.-->
1921 <attr name="alwaysFocusable" format="boolean" />
1922 <attr name="enableVrMode" />
1923 </declare-styleable>
1925 <!-- The <code>activity-alias</code> tag declares a new
1926 name for an existing {@link #AndroidManifestActivity activity}
1929 <p>Zero or more {@link #AndroidManifestIntentFilter intent-filter}
1930 tags can be included inside of an activity-alias, to specify the Intents
1931 that it can handle. If none are specified, the activity can
1932 only be started through direct specification of its class name.
1933 The activity-alias tag appears as a child tag of the
1934 {@link #AndroidManifestApplication application} tag. -->
1935 <declare-styleable name="AndroidManifestActivityAlias" parent="AndroidManifestApplication">
1936 <!-- Required name of the class implementing the activity, deriving from
1937 {@link android.app.Activity}. This is a fully
1938 qualified class name (for example, com.mycompany.myapp.MyActivity); as a
1939 short-hand if the first character of the class
1940 is a period then it is appended to your package name. -->
1941 <attr name="name" />
1942 <!-- The name of the activity this alias should launch. The activity
1943 must be in the same manifest as the alias, and have been defined
1944 in that manifest before the alias here. This must use a Java-style
1945 naming convention to ensure the name is unique, for example
1946 "com.mycompany.MyName". -->
1947 <attr name="targetActivity" format="string" />
1948 <attr name="label" />
1949 <attr name="description" />
1950 <attr name="icon" />
1951 <attr name="roundIcon" />
1952 <attr name="banner" />
1953 <attr name="logo" />
1954 <attr name="permission" />
1955 <!-- Specify whether the activity-alias is enabled or not (that is, can be instantiated by the system).
1956 It can also be specified for an application as a whole, in which case a value of "false"
1957 will override any component specific values (a value of "true" will not override the
1958 component specific values). -->
1959 <attr name="enabled" />
1960 <attr name="exported" />
1961 <attr name="parentActivityName" />
1962 </declare-styleable>
1964 <!-- The <code>meta-data</code> tag is used to attach additional
1965 arbitrary data to an application component. The data can later
1966 be retrieved programmatically from the
1967 {@link android.content.pm.ComponentInfo#metaData
1968 ComponentInfo.metaData} field. There is no meaning given to this
1969 data by the system. You may supply the data through either the
1970 <code>value</code> or <code>resource</code> attribute; if both
1971 are given, then <code>resource</code> will be used.
1973 <p>It is highly recommended that you avoid supplying related data as
1974 multiple separate meta-data entries. Instead, if you have complex
1975 data to associate with a component, then use the <code>resource</code>
1976 attribute to assign an XML resource that the client can parse to
1977 retrieve the complete data. -->
1978 <declare-styleable name="AndroidManifestMetaData"
1979 parent="AndroidManifestApplication
1980 AndroidManifestActivity
1981 AndroidManifestReceiver
1982 AndroidManifestProvider
1983 AndroidManifestService
1984 AndroidManifestPermission
1985 AndroidManifestPermissionGroup
1986 AndroidManifestInstrumentation">
1987 <attr name="name" />
1988 <!-- Concrete value to assign to this piece of named meta-data.
1989 The data can later be retrieved from the meta data Bundle
1990 through {@link android.os.Bundle#getString Bundle.getString},
1991 {@link android.os.Bundle#getInt Bundle.getInt},
1992 {@link android.os.Bundle#getBoolean Bundle.getBoolean},
1993 or {@link android.os.Bundle#getFloat Bundle.getFloat} depending
1994 on the type used here. -->
1995 <attr name="value" format="string|integer|color|float|boolean" />
1996 <!-- Resource identifier to assign to this piece of named meta-data.
1997 The resource identifier can later be retrieved from the meta data
1998 Bundle through {@link android.os.Bundle#getInt Bundle.getInt}. -->
1999 <attr name="resource" format="reference" />
2000 </declare-styleable>
2002 <!-- The <code>intent-filter</code> tag is used to construct an
2003 {@link android.content.IntentFilter} object that will be used
2004 to determine which component can handle a particular
2005 {@link android.content.Intent} that has been given to the system.
2006 It can be used as a child of the
2007 {@link #AndroidManifestActivity activity},
2008 {@link #AndroidManifestReceiver receiver} and
2009 {@link #AndroidManifestService service}
2012 <p> Zero or more {@link #AndroidManifestAction action},
2013 {@link #AndroidManifestCategory category}, and/or
2014 {@link #AndroidManifestData data} tags should be
2015 included inside to describe the contents of the filter.
2017 <p> The optional label and icon attributes here are used with
2018 an activity to supply an alternative description of that activity
2019 when it is being started through an Intent matching this filter. -->
2020 <declare-styleable name="AndroidManifestIntentFilter"
2021 parent="AndroidManifestActivity AndroidManifestReceiver AndroidManifestService">
2022 <attr name="label" />
2023 <attr name="icon" />
2024 <attr name="roundIcon" />
2025 <attr name="banner" />
2026 <attr name="logo" />
2027 <attr name="priority" />
2028 <attr name="autoVerify" />
2029 </declare-styleable>
2031 <!-- Attributes that can be supplied in an AndroidManifest.xml
2032 <code>action</code> tag, a child of the
2033 {@link #AndroidManifestIntentFilter intent-filter} tag.
2034 See {@link android.content.IntentFilter#addAction} for
2035 more information. -->
2036 <declare-styleable name="AndroidManifestAction" parent="AndroidManifestIntentFilter">
2037 <!-- The name of an action that is handled, using the Java-style
2038 naming convention. For example, to support
2039 {@link android.content.Intent#ACTION_VIEW Intent.ACTION_VIEW}
2040 you would put <code>android.intent.action.VIEW</code> here.
2041 Custom actions should generally use a prefix matching the
2043 <attr name="name" />
2044 </declare-styleable>
2046 <!-- Attributes that can be supplied in an AndroidManifest.xml
2047 <code>data</code> tag, a child of the
2048 {@link #AndroidManifestIntentFilter intent-filter} tag, describing
2049 the types of data that match. This tag can be specified multiple
2050 times to supply multiple data options, as described in the
2051 {@link android.content.IntentFilter} class. Note that all such
2052 tags are adding options to the same IntentFilter so that, for example,
2053 <code><data android:scheme="myscheme" android:host="me.com" /></code>
2054 is equivalent to <code><data android:scheme="myscheme" />
2055 <data android:host="me.com" /></code>. -->
2056 <declare-styleable name="AndroidManifestData" parent="AndroidManifestIntentFilter">
2057 <!-- Specify a MIME type that is handled, as per
2058 {@link android.content.IntentFilter#addDataType
2059 IntentFilter.addDataType()}.
2060 <p><em>Note: MIME type matching in the Android framework is
2061 case-sensitive, unlike formal RFC MIME types. As a result,
2062 MIME types here should always use lower case letters.</em></p> -->
2063 <attr name="mimeType" format="string" />
2064 <!-- Specify a URI scheme that is handled, as per
2065 {@link android.content.IntentFilter#addDataScheme
2066 IntentFilter.addDataScheme()}.
2067 <p><em>Note: scheme matching in the Android framework is
2068 case-sensitive, unlike the formal RFC. As a result,
2069 schemes here should always use lower case letters.</em></p> -->
2070 <attr name="scheme" format="string" />
2071 <!-- Specify a URI scheme specific part that must exactly match, as per
2072 {@link android.content.IntentFilter#addDataSchemeSpecificPart
2073 IntentFilter.addDataSchemeSpecificPart()} with
2074 {@link android.os.PatternMatcher#PATTERN_LITERAL}. -->
2075 <attr name="ssp" format="string" />
2076 <!-- Specify a URI scheme specific part that must be a prefix to match, as per
2077 {@link android.content.IntentFilter#addDataSchemeSpecificPart
2078 IntentFilter.addDataSchemeSpecificPart()} with
2079 {@link android.os.PatternMatcher#PATTERN_PREFIX}. -->
2080 <attr name="sspPrefix" format="string" />
2081 <!-- Specify a URI scheme specific part that matches a simple pattern, as per
2082 {@link android.content.IntentFilter#addDataSchemeSpecificPart
2083 IntentFilter.addDataSchemeSpecificPart()} with
2084 {@link android.os.PatternMatcher#PATTERN_SIMPLE_GLOB}.
2085 Note that because '\' is used as an escape character when
2086 reading the string from XML (before it is parsed as a pattern),
2087 you will need to double-escape: for example a literal "*" would
2088 be written as "\\*" and a literal "\" would be written as
2089 "\\\\". This is basically the same as what you would need to
2090 write if constructing the string in Java code. -->
2091 <attr name="sspPattern" format="string" />
2092 <!-- Specify a URI authority host that is handled, as per
2093 {@link android.content.IntentFilter#addDataAuthority
2094 IntentFilter.addDataAuthority()}.
2095 <p><em>Note: host name matching in the Android framework is
2096 case-sensitive, unlike the formal RFC. As a result,
2097 host names here should always use lower case letters.</em></p> -->
2098 <attr name="host" format="string" />
2099 <!-- Specify a URI authority port that is handled, as per
2100 {@link android.content.IntentFilter#addDataAuthority
2101 IntentFilter.addDataAuthority()}. If a host is supplied
2102 but not a port, any port is matched. -->
2103 <attr name="port" format="string" />
2104 <!-- Specify a URI path that must exactly match, as per
2105 {@link android.content.IntentFilter#addDataPath
2106 IntentFilter.addDataPath()} with
2107 {@link android.os.PatternMatcher#PATTERN_LITERAL}. -->
2108 <attr name="path" />
2109 <!-- Specify a URI path that must be a prefix to match, as per
2110 {@link android.content.IntentFilter#addDataPath
2111 IntentFilter.addDataPath()} with
2112 {@link android.os.PatternMatcher#PATTERN_PREFIX}. -->
2113 <attr name="pathPrefix" />
2114 <!-- Specify a URI path that matches a simple pattern, as per
2115 {@link android.content.IntentFilter#addDataPath
2116 IntentFilter.addDataPath()} with
2117 {@link android.os.PatternMatcher#PATTERN_SIMPLE_GLOB}.
2118 Note that because '\' is used as an escape character when
2119 reading the string from XML (before it is parsed as a pattern),
2120 you will need to double-escape: for example a literal "*" would
2121 be written as "\\*" and a literal "\" would be written as
2122 "\\\\". This is basically the same as what you would need to
2123 write if constructing the string in Java code. -->
2124 <attr name="pathPattern" />
2125 </declare-styleable>
2127 <!-- Attributes that can be supplied in an AndroidManifest.xml
2128 <code>category</code> tag, a child of the
2129 {@link #AndroidManifestIntentFilter intent-filter} tag.
2130 See {@link android.content.IntentFilter#addCategory} for
2131 more information. -->
2132 <declare-styleable name="AndroidManifestCategory" parent="AndroidManifestIntentFilter">
2133 <!-- The name of category that is handled, using the Java-style
2134 naming convention. For example, to support
2135 {@link android.content.Intent#CATEGORY_LAUNCHER Intent.CATEGORY_LAUNCHER}
2136 you would put <code>android.intent.category.LAUNCHER</code> here.
2137 Custom actions should generally use a prefix matching the
2139 <attr name="name" />
2140 </declare-styleable>
2142 <!-- Attributes that can be supplied in an AndroidManifest.xml
2143 <code>instrumentation</code> tag, a child of the root
2144 {@link #AndroidManifest manifest} tag. -->
2145 <declare-styleable name="AndroidManifestInstrumentation" parent="AndroidManifest">
2146 <!-- Required name of the class implementing the instrumentation, deriving from
2147 {@link android.app.Instrumentation}. This is a fully
2148 qualified class name (for example, com.mycompany.myapp.MyActivity); as a
2149 short-hand if the first character of the class
2150 is a period then it is appended to your package name. -->
2151 <attr name="name" />
2152 <attr name="targetPackage" />
2153 <attr name="label" />
2154 <attr name="icon" />
2155 <attr name="roundIcon" />
2156 <attr name="banner" />
2157 <attr name="logo" />
2158 <attr name="handleProfiling" />
2159 <attr name="functionalTest" />
2160 </declare-styleable>
2162 <!-- Attributes that can be supplied in an AndroidManifest.xml
2163 <code>screen</code> tag, a child of <code>compatible-screens</code>,
2164 which is itself a child of the root
2165 {@link #AndroidManifest manifest} tag. -->
2166 <declare-styleable name="AndroidManifestCompatibleScreensScreen"
2167 parent="AndroidManifest.AndroidManifestCompatibleScreens">
2168 <!-- Specifies a compatible screen size, as per the device
2169 configuration screen size bins. -->
2170 <attr name="screenSize">
2171 <!-- A small screen configuration, at least 240x320dp. -->
2172 <enum name="small" value="200" />
2173 <!-- A normal screen configuration, at least 320x480dp. -->
2174 <enum name="normal" value="300" />
2175 <!-- A large screen configuration, at least 400x530dp. -->
2176 <enum name="large" value="400" />
2177 <!-- An extra large screen configuration, at least 600x800dp. -->
2178 <enum name="xlarge" value="500" />
2180 <!-- Specifies a compatible screen density, as per the device
2181 configuration screen density bins. -->
2182 <attr name="screenDensity" format="integer">
2183 <!-- A low density screen, approximately 120dpi. -->
2184 <enum name="ldpi" value="120" />
2185 <!-- A medium density screen, approximately 160dpi. -->
2186 <enum name="mdpi" value="160" />
2187 <!-- A high density screen, approximately 240dpi. -->
2188 <enum name="hdpi" value="240" />
2189 <!-- An extra high density screen, approximately 320dpi. -->
2190 <enum name="xhdpi" value="320" />
2191 <!-- An extra extra high density screen, approximately 480dpi. -->
2192 <enum name="xxhdpi" value="480" />
2193 <!-- An extra extra extra high density screen, approximately 640dpi. -->
2194 <enum name="xxxhdpi" value="640" />
2196 </declare-styleable>
2198 <!-- The <code>input-type</code> tag is a child of the <code>supports-input</code> tag, which
2199 is itself a child of the root {@link #AndroidManifest manifest} tag. Each
2200 <code>input-type</code> tag specifices the name of a specific input device type. When
2201 grouped with the other elements of the parent <code>supports-input</code> tag it defines
2202 a collection of input devices, which when all used together, are considered a supported
2203 input mechanism for the application. There may be multiple <code>supports-input</code>
2204 tags defined, each containing a different combination of input device types. -->
2205 <declare-styleable name="AndroidManifestSupportsInputInputType"
2206 parent="AndroidManifest.AndroidManifestSupportsInput">
2207 <!-- Specifices the name of the input device type -->
2208 <attr name="name" />
2209 </declare-styleable>
2211 <!-- The attribute that holds a Base64-encoded public key. -->
2212 <attr name="publicKey" format="string" />
2214 <!-- Attributes relating to a package verifier. -->
2215 <declare-styleable name="AndroidManifestPackageVerifier" parent="AndroidManifest">
2216 <!-- Specifies the Java-style package name that defines this
2217 package verifier. -->
2218 <attr name="name" />
2220 <!-- The Base64 encoded public key of the package verifier's
2222 <attr name="publicKey" />
2223 </declare-styleable>
2225 <!-- Attributes relating to resource overlay packages. -->
2226 <declare-styleable name="AndroidManifestResourceOverlay" parent="AndroidManifest">
2227 <!-- Package name of base package whose resources will be overlaid. -->
2228 <attr name="targetPackage" />
2230 <!-- Load order of overlay package. -->
2231 <attr name="priority" />
2233 </declare-styleable>
2235 <!-- Declaration of an {@link android.content.Intent} object in XML. May
2236 also include zero or more {@link #IntentCategory <category> and
2237 {@link #Extra <extra>} tags. -->
2238 <declare-styleable name="Intent">
2239 <!-- The action name to assign to the Intent, as per
2240 {@link android.content.Intent#setAction Intent.setAction()}. -->
2241 <attr name="action" format="string" />
2242 <!-- The data URI to assign to the Intent, as per
2243 {@link android.content.Intent#setData Intent.setData()}.
2244 <p><em>Note: scheme and host name matching in the Android framework is
2245 case-sensitive, unlike the formal RFC. As a result,
2246 URIs here should always be normalized to use lower case letters
2247 for these elements (as well as other proper Uri normalization).</em></p> -->
2248 <attr name="data" format="string" />
2249 <!-- The MIME type name to assign to the Intent, as per
2250 {@link android.content.Intent#setType Intent.setType()}.
2251 <p><em>Note: MIME type matching in the Android framework is
2252 case-sensitive, unlike formal RFC MIME types. As a result,
2253 MIME types here should always use lower case letters.</em></p> -->
2254 <attr name="mimeType" />
2255 <!-- The package part of the ComponentName to assign to the Intent, as per
2256 {@link android.content.Intent#setComponent Intent.setComponent()}. -->
2257 <attr name="targetPackage" />
2258 <!-- The class part of the ComponentName to assign to the Intent, as per
2259 {@link android.content.Intent#setComponent Intent.setComponent()}. -->
2260 <attr name="targetClass" format="string" />
2261 </declare-styleable>
2263 <!-- A category to add to an Intent, as per
2264 {@link android.content.Intent#addCategory Intent.addCategory()}. -->
2265 <declare-styleable name="IntentCategory" parent="Intent">
2266 <!-- Required name of the category. -->
2267 <attr name="name" />
2268 </declare-styleable>
2270 <!-- An extra data value to place into a an extra/name value pair held
2271 in a Bundle, as per {@link android.os.Bundle}. -->
2272 <declare-styleable name="Extra" parent="Intent">
2273 <!-- Required name of the extra data. -->
2274 <attr name="name" />
2275 <!-- Concrete value to put for this named extra data. -->
2276 <attr name="value" />
2277 </declare-styleable>
2279 <!-- Groups signing keys into a {@code KeySet} for easier reference in
2280 other APIs. However, currently no APIs use this. -->
2281 <attr name="keySet" />
2282 <declare-styleable name="AndroidManifestPublicKey">
2283 <attr name="name" />
2284 <attr name="value" />
2285 </declare-styleable>
2286 <declare-styleable name="AndroidManifestKeySet">
2287 <attr name="name" />
2288 </declare-styleable>
2290 <!-- Associate declared KeySets with upgrading capability. -->
2291 <declare-styleable name="AndroidManifestUpgradeKeySet" parent="AndroidManifest">
2292 <attr name="name" />
2293 </declare-styleable>
2295 <!-- <code>layout</code> tag allows configuring the layout for the activity within multi-window
2297 <declare-styleable name="AndroidManifestLayout" parent="AndroidManifestActivity">
2298 <!-- Default width of the activity. Can be either a fixed value or fraction, in which case
2299 the width will be constructed as a fraction of the total available width. -->
2300 <attr name="defaultWidth" format="dimension|fraction" />
2301 <!-- Default height of the activity. Can be either a fixed value or fraction, in which case
2302 the height will be constructed as a fraction of the total available height. -->
2303 <attr name="defaultHeight" format="dimension|fraction" />
2304 <!-- Where to initially position the activity inside the available space. Uses constants
2305 defined in {@link android.view.Gravity}. -->
2306 <attr name="gravity" />
2307 <!-- Minimal width of the activity.
2309 <p><strong>NOTE:</strong> A task's root activity value is applied to all additional
2310 activities launched in the task. That is if the root activity of a task set minimal width,
2311 then the system will set the same minimal width on all other activities in the task. It
2312 will also ignore any other minimal width attributes of non-root activities. -->
2313 <attr name="minWidth" />
2315 <attr name="minimalWidth" format="dimension" />
2316 <!-- Minimal height of the activity.
2318 <p><strong>NOTE:</strong> A task's root activity value is applied to all additional
2319 activities launched in the task. That is if the root activity of a task set minimal height,
2320 then the system will set the same minimal height on all other activities in the task. It
2321 will also ignore any other minimal height attributes of non-root activities. -->
2322 <attr name="minHeight" />
2324 <attr name="minimalHeight" format="dimension" />
2325 </declare-styleable>
2327 <!-- <code>restrict-update</code> tag restricts system apps from being updated unless the
2328 SHA-512 hash equals the specified value.
2330 <declare-styleable name="AndroidManifestRestrictUpdate" parent="AndroidManifest">
2331 <!-- The SHA-512 hash of the only APK that can be used to update a package.
2332 <p>NOTE: This is only applicable to system packages.
2334 <attr name="hash" format="string" />
2335 </declare-styleable>