1<?xml version="1.0" encoding="utf-8"?> 2<!-- 3/* Copyright 2006, The Android Open Source Project 4** 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 8** 9** http://www.apache.org/licenses/LICENSE-2.0 10** 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. 16*/ 17--> 18<resources> 19 <!-- **************************************************************** --> 20 <!-- These are the attributes used in AndroidManifest.xml. --> 21 <!-- **************************************************************** --> 22 <eat-comment /> 23 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). 27 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" /> 35 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. 42 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" /> 50 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. 58 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" /> 64 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. 72 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" /> 78 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. 83 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" /> 93 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. 101 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" /> 109 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 117 manage space. --> 118 <attr name="manageSpaceActivity" format="string" /> 119 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" /> 125 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" /> 132 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" /> 137 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" /> 144 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" /> 150 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" /> 156 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 164 provider.--> 165 <attr name="grantUriPermissions" format="boolean" /> 166 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 207 together. --> 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 217 together. --> 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 240 apps). --> 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" /> 245 <!-- Additional flag from base permission type: this permission can be granted to ephemeral 246 apps --> 247 <flag name="ephemeral" value="0x1000" /> 248 <!-- Additional flag from base permission type: this permission can only be granted to apps 249 that target runtime permissions ({@link android.os.Build.VERSION_CODES#M} and above) 250 --> 251 <flag name="runtime" value="0x2000" /> 252 </attr> 253 254 <!-- Flags indicating more context for a permission group. --> 255 <attr name="permissionGroupFlags"> 256 <!-- Set to indicate that this permission group contains permissions 257 protecting access to some information that is considered 258 personal to the user (such as contacts, e-mails, etc). --> 259 <flag name="personalInfo" value="0x0001" /> 260 </attr> 261 262 <!-- Flags indicating more context for a permission. --> 263 <attr name="permissionFlags"> 264 <!-- Set to indicate that this permission allows an operation that 265 may cost the user money. Such permissions may be highlighted 266 when shown to the user with this additional information. --> 267 <flag name="costsMoney" value="0x0001" /> 268 <!-- Additional flag from base permission type: this permission has been 269 removed and it is no longer enforced. It shouldn't be shown in the 270 UI. Removed permissions are kept as normal permissions for backwards 271 compatibility as apps may be checking them before calling an API. 272 --> 273 <flag name="removed" value="0x2" /> 274 </attr> 275 276 <!-- Specified the name of a group that this permission is associated 277 with. The group must have been defined with the 278 {@link android.R.styleable#AndroidManifestPermissionGroup permission-group} tag. --> 279 <attr name="permissionGroup" format="string" /> 280 281 <!-- Specify the name of a user ID that will be shared between multiple 282 packages. By default, each package gets its own unique user-id. 283 By setting this value on two or more packages, each of these packages 284 will be given a single shared user ID, so they can for example run 285 in the same process. Note that for them to actually get the same 286 user ID, they must also be signed with the same signature. --> 287 <attr name="sharedUserId" format="string" /> 288 289 <!-- Specify a label for the shared user UID of this package. This is 290 only used if you have also used android:sharedUserId. This must 291 be a reference to a string resource; it can not be an explicit 292 string. --> 293 <attr name="sharedUserLabel" format="reference" /> 294 295 <!-- Internal version code. This is the number used to determine whether 296 one version is more recent than another: it has no other meaning than 297 that higher numbers are more recent. You could use this number to 298 encode a "x.y" in the lower and upper 16 bits, make it a build 299 number, simply increase it by one each time a new version is 300 released, or define it however else you want, as long as each 301 successive version has a higher number. This is not a version 302 number generally shown to the user, that is usually supplied 303 with {@link android.R.attr#versionName}. When an app is delivered 304 as multiple split APKs, each APK must have the exact same versionCode. --> 305 <attr name="versionCode" format="integer" /> 306 307 <!-- Internal revision code. This number is the number used to determine 308 whether one APK is more recent than another: it has no other meaning 309 than that higher numbers are more recent. This value is only meaningful 310 when the two {@link android.R.attr#versionCode} values are already 311 identical. When an app is delivered as multiple split APKs, each 312 APK may have a different revisionCode value. --> 313 <attr name="revisionCode" format="integer" /> 314 315 <!-- The text shown to the user to indicate the version they have. This 316 is used for no other purpose than display to the user; the actual 317 significant version number is given by {@link android.R.attr#versionCode}. --> 318 <attr name="versionName" format="string" /> 319 320 <!-- Flag to control special persistent mode of an application. This should 321 not normally be used by applications; it requires that the system keep 322 your application running at all times. --> 323 <attr name="persistent" format="boolean" /> 324 325 <!-- If set, the "persistent" attribute will only be honored if the feature 326 specified here is present on the device. --> 327 <attr name="persistentWhenFeatureAvailable" format="string" /> 328 329 <!-- Flag to specify if this application needs to be present for all users. Only pre-installed 330 applications can request this feature. Default value is false. --> 331 <attr name="requiredForAllUsers" format="boolean" /> 332 333 <!-- Flag indicating whether the application can be debugged, even when 334 running on a device that is running in user mode. --> 335 <attr name="debuggable" format="boolean" /> 336 337 <!-- Flag indicating whether the application requests the VM to operate in 338 the safe mode. --> 339 <attr name="vmSafeMode" format="boolean" /> 340 341 <!-- <p>Flag indicating whether the application's rendering should be hardware 342 accelerated if possible. This flag is turned on by default for applications 343 that are targeting {@link android.os.Build.VERSION_CODES#ICE_CREAM_SANDWICH} 344 or later.</p> 345 <p>This flag can be set on the application and any activity declared 346 in the manifest. When enabled for the application, each activity is 347 automatically assumed to be hardware accelerated. This flag can be 348 overridden in the activity tags, either turning it off (if on for the 349 application) or on (if off for the application.)</p> 350 <p>When this flag is turned on for an activity (either directly or via 351 the application tag), every window created from the activity, including 352 the activity's own window, will be hardware accelerated, if possible.</p> 353 <p>Please refer to the documentation of 354 {@link android.view.WindowManager.LayoutParams#FLAG_HARDWARE_ACCELERATED} 355 for more information on how to control this flag programmatically.</p> --> 356 <attr name="hardwareAccelerated" format="boolean" /> 357 358 <!-- Flag indicating whether the given application component is available 359 to other applications. If false, it can only be accessed by 360 applications with its same user id (which usually means only by 361 code in its own package). If true, it can be invoked by external 362 entities, though which ones can do so may be controlled through 363 permissions. The default value is false for activity, receiver, 364 and service components that do not specify any intent filters; it 365 is true for activity, receiver, and service components that do 366 have intent filters (implying they expect to be invoked by others 367 who do not know their particular component name) and for all 368 content providers. --> 369 <attr name="exported" format="boolean" /> 370 371 <!-- A boolean flag used to indicate if an application is a Game or not. 372 <p>This information can be used by the system to group together 373 applications that are classified as games, and display them separately 374 from the other applications. --> 375 <attr name="isGame" format="boolean" /> 376 377 <!-- If set to true, a single instance of this component will run for 378 all users. That instance will run as user 0, the default/primary 379 user. When the app running is in processes for other users and interacts 380 with this component (by binding to a service for example) those processes will 381 always interact with the instance running for user 0. Enabling 382 single user mode forces "exported" of the component to be false, to 383 help avoid introducing multi-user security bugs. This feature is only 384 available to applications built in to the system image; you must hold the 385 permission INTERACT_ACROSS_USERS in order 386 to use this feature. This flag can only be used with services, 387 receivers, and providers; it can not be used with activities. --> 388 <attr name="singleUser" format="boolean" /> 389 390 <!-- Specify a specific process that the associated code is to run in. 391 Use with the application tag (to supply a default process for all 392 application components), or with the activity, receiver, service, 393 or provider tag (to supply a specific icon for that component). 394 395 <p>Application components are normally run in a single process that 396 is created for the entire application. You can use this tag to modify 397 where they run. If the process name begins with a ':' character, 398 a new process private to that application will be created when needed 399 to run that component (allowing you to spread your application across 400 multiple processes). If the process name begins with a lower-case 401 character, the component will be run in a global process of that name, 402 provided that you have permission to do so, allowing multiple 403 applications to share one process to reduce resource usage. --> 404 <attr name="process" format="string" /> 405 406 <!-- Specify a task name that activities have an "affinity" to. 407 Use with the application tag (to supply a default affinity for all 408 activities in the application), or with the activity tag (to supply 409 a specific affinity for that component). 410 411 <p>The default value for this attribute is the same as the package 412 name, indicating that all activities in the manifest should generally 413 be considered a single "application" to the user. You can use this 414 attribute to modify that behavior: either giving them an affinity 415 for another task, if the activities are intended to be part of that 416 task from the user's perspective, or using an empty string for 417 activities that have no affinity to a task. --> 418 <attr name="taskAffinity" format="string" /> 419 420 <!-- Specify that an activity can be moved out of a task it is in to 421 the task it has an affinity for when appropriate. Use with the 422 application tag (to supply a default for all activities in the 423 application), or with an activity tag (to supply a specific 424 setting for that component). 425 426 <p>Normally when an application is started, it is associated with 427 the task of the activity that started it and stays there for its 428 entire lifetime. You can use the allowTaskReparenting feature to force an 429 activity to be re-parented to a different task when the task it is 430 in goes to the background. Typically this is used to cause the 431 activities of an application to move back to the main task associated 432 with that application. The activity is re-parented to the task 433 with the same {@link android.R.attr#taskAffinity} as it has. --> 434 <attr name="allowTaskReparenting" format="boolean" /> 435 436 <!-- Declare that this application may use cleartext traffic, such as HTTP rather than HTTPS; 437 WebSockets rather than WebSockets Secure; XMPP, IMAP, STMP without STARTTLS or TLS. 438 Defaults to true. If set to false {@code false}, the application declares that it does not 439 intend to use cleartext network traffic, in which case platform components (e.g. HTTP 440 stacks, {@code DownloadManager}, {@code MediaPlayer}) will refuse applications's requests 441 to use cleartext traffic. Third-party libraries are encouraged to honor this flag as well. 442 --> 443 <attr name="usesCleartextTraffic" format="boolean" /> 444 445 <!-- Declare that code from this application will need to be loaded into other 446 applications' processes. On devices that support multiple instruction sets, 447 this implies the code might be loaded into a process that's using any of the devices 448 supported instruction sets. 449 450 <p> The system might treat such applications specially, for eg., by 451 extracting the application's native libraries for all supported instruction 452 sets or by compiling the application's dex code for all supported instruction 453 sets. --> 454 <attr name="multiArch" format ="boolean" /> 455 456 <!-- Specify whether the 32 bit version of the ABI should be used in a 457 multiArch application. If both abioverride flag (i.e. using abi option of abd install) 458 and use32bitAbi are used, then use32bit is ignored.--> 459 <attr name="use32bitAbi" /> 460 461 <!-- Specify whether a component is allowed to have multiple instances 462 of itself running in different processes. Use with the activity 463 and provider tags. 464 465 <p>Normally the system will ensure that all instances of a particular 466 component are only running in a single process. You can use this 467 attribute to disable that behavior, allowing the system to create 468 instances wherever they are used (provided permissions allow it). 469 This is most often used with content providers, so that instances 470 of a provider can be created in each client process, allowing them 471 to be used without performing IPC. --> 472 <attr name="multiprocess" format="boolean" /> 473 474 <!-- Specify whether an activity should be finished when its task is 475 brought to the foreground by relaunching from the home screen. 476 477 <p>If both this option and {@link android.R.attr#allowTaskReparenting} are 478 specified, the finish trumps the affinity: the affinity will be 479 ignored and the activity simply finished. --> 480 <attr name="finishOnTaskLaunch" format="boolean" /> 481 482 <!-- Specify whether an activity should be finished when a "close system 483 windows" request has been made. This happens, for example, when 484 the home key is pressed, when the device is locked, when a system 485 dialog showing recent applications is displayed, etc. --> 486 <attr name="finishOnCloseSystemDialogs" format="boolean" /> 487 488 <!-- Specify whether an activity's task should be cleared when it 489 is re-launched from the home screen. As a result, every time the 490 user starts the task, they will be brought to its root activity, 491 regardless of whether they used BACK or HOME to last leave it. 492 This flag only applies to activities that 493 are used to start the root of a new task. 494 495 <p>An example of the use of this flag would be for the case where 496 a user launches activity A from home, and from there goes to 497 activity B. They now press home, and then return to activity A. 498 Normally they would see activity B, since that is what they were 499 last doing in A's task. However, if A has set this flag to true, 500 then upon going to the background all of the tasks on top of it (B 501 in this case) are removed, so when the user next returns to A they 502 will restart at its original activity. 503 504 <p>When this option is used in conjunction with 505 {@link android.R.attr#allowTaskReparenting}, the allowTaskReparenting trumps the 506 clear. That is, all activities above the root activity of the 507 task will be removed: those that have an affinity will be moved 508 to the task they are associated with, otherwise they will simply 509 be dropped as described here. --> 510 <attr name="clearTaskOnLaunch" format="boolean" /> 511 512 <!-- Specify whether an activity should be kept in its history stack. 513 If this attribute is set, then as soon as the user navigates away 514 from the activity it will be finished and they will no longer be 515 able to return to it. --> 516 <attr name="noHistory" format="boolean" /> 517 518 <!-- Specify whether an acitivty's task state should always be maintained 519 by the system, or if it is allowed to reset the task to its initial 520 state in certain situations. 521 522 <p>Normally the system will reset a task (remove all activities from 523 the stack and reset the root activity) in certain situations when 524 the user re-selects that task from the home screen. Typically this 525 will be done if the user hasn't visited that task for a certain 526 amount of time, such as 30 minutes. 527 528 <p>By setting this attribute, the user will always return to your 529 task in its last state, regardless of how they get there. This is 530 useful, for example, in an application like the web browser where there 531 is a lot of state (such as multiple open tabs) that the application 532 would not like to lose. --> 533 <attr name="alwaysRetainTaskState" format="boolean" /> 534 535 <!-- Indicates that an Activity does not need to have its freeze state 536 (as returned by {@link android.app.Activity#onSaveInstanceState} 537 retained in order to be restarted. Generally you use this for activities 538 that do not store any state. When this flag is set, if for some reason 539 the activity is killed before it has a chance to save its state, 540 then the system will not remove it from the activity stack like 541 it normally would. Instead, the next time the user navigates to 542 it its {@link android.app.Activity#onCreate} method will be called 543 with a null icicle, just like it was starting for the first time. 544 545 <p>This is used by the Home activity to make sure it does not get 546 removed if it crashes for some reason. --> 547 <attr name="stateNotNeeded" format="boolean" /> 548 549 <!-- Indicates that an Activity should be excluded from the list of 550 recently launched activities. --> 551 <attr name="excludeFromRecents" format="boolean" /> 552 553 <!-- Specify that an Activity should be shown over the lock screen and, 554 in a multiuser environment, across all users' windows. 555 @deprecated use {@link android.R.attr#showForAllUsers} instead. --> 556 <attr name="showOnLockScreen" format="boolean" /> 557 558 <!-- Specify that an Activity should be shown even if the current/foreground user 559 is different from the user of the Activity. This will also force the 560 <code>android.view.LayoutParams.FLAG_SHOW_WHEN_LOCKED</code> flag 561 to be set for all windows of this activity --> 562 <attr name="showForAllUsers" format="boolean" /> 563 564 <!-- Specify the authorities under which this content provider can be 565 found. Multiple authorities may be supplied by separating them 566 with a semicolon. Authority names should use a Java-style naming 567 convention (such as <code>com.google.provider.MyProvider</code>) 568 in order to avoid conflicts. Typically this name is the same 569 as the class implementation describing the provider's data structure. --> 570 <attr name="authorities" format="string" /> 571 572 <!-- Flag indicating whether this content provider would like to 573 participate in data synchronization. --> 574 <attr name="syncable" format="boolean" /> 575 576 <!-- Flag declaring this activity to be 'immersive'; immersive activities 577 should not be interrupted with other activities or notifications. --> 578 <attr name="immersive" format="boolean" /> 579 580 <!-- Flag declaring that this activity will be run in VR mode, and specifying 581 the component of the {@link android.service.vr.VrListenerService} that should be 582 bound while this Activity is visible if it is installed and enabled on this device. 583 This is equivalent to calling {@link android.app.Activity#setVrModeEnabled} with the 584 the given component name within the Activity that this attribute is set for. 585 Declaring this will prevent the system from leaving VR mode during an Activity 586 transtion from one VR activity to another. --> 587 <attr name="enableVrMode" format="string" /> 588 589 <!-- Flag allowing the activity to specify which screen rotation animation 590 it desires. Valid values are "rotate", "crossfade", and "jumpcut" 591 as described in {@link android.view.WindowManager.LayoutParams#rotationAnimation}. 592 Specifying your Rotation animation in the WindowManager.LayoutParams 593 may be racy with app startup and updattransitions occuring during application startup and thusly 594 the manifest attribute is preferred. 595 --> 596 <attr name="rotationAnimation"> 597 <flag name="rotate" value= "0" /> 598 <flag name="crossfade" value = "1" /> 599 <flag name="jumpcut" value = "2" /> 600 <flag name="seamless" value = "3" /> 601 </attr> 602 603 <!-- Specify the order in which content providers hosted by a process 604 are instantiated when that process is created. Not needed unless 605 you have providers with dependencies between each other, to make 606 sure that they are created in the order needed by those dependencies. 607 The value is a simple integer, with higher numbers being 608 initialized first. --> 609 <attr name="initOrder" format="integer" /> 610 611 <!-- Specify the relative importance or ability in handling a particular 612 Intent. For receivers, this controls the order in which they are 613 executed to receive a broadcast (note that for 614 asynchronous broadcasts, this order is ignored). For activities, 615 this provides information about how good an activity is handling an 616 Intent; when multiple activities match an intent and have different 617 priorities, only those with the higher priority value will be 618 considered a match. 619 620 <p>Only use if you really need to impose some specific 621 order in which the broadcasts are received, or want to forcibly 622 place an activity to always be preferred over others. The value is a 623 single integer, with higher numbers considered to be better. --> 624 <attr name="priority" format="integer" /> 625 626 <!-- Indicate if this component is aware of direct boot lifecycle, and can be 627 safely run before the user has entered their credentials (such as a lock 628 pattern or PIN). --> 629 <attr name="directBootAware" format="boolean" /> 630 631 <!-- Specify how an activity should be launched. See the 632 <a href="{@docRoot}guide/topics/fundamentals/tasks-and-back-stack.html">Tasks and Back 633 Stack</a> document for important information on how these options impact 634 the behavior of your application. 635 636 <p>If this attribute is not specified, <code>standard</code> launch 637 mode will be used. Note that the particular launch behavior can 638 be changed in some ways at runtime through the 639 {@link android.content.Intent} flags 640 {@link android.content.Intent#FLAG_ACTIVITY_SINGLE_TOP}, 641 {@link android.content.Intent#FLAG_ACTIVITY_NEW_TASK}, and 642 {@link android.content.Intent#FLAG_ACTIVITY_MULTIPLE_TASK}. --> 643 <attr name="launchMode"> 644 <!-- The default mode, which will usually create a new instance of 645 the activity when it is started, though this behavior may change 646 with the introduction of other options such as 647 {@link android.content.Intent#FLAG_ACTIVITY_NEW_TASK 648 Intent.FLAG_ACTIVITY_NEW_TASK}. --> 649 <enum name="standard" value="0" /> 650 <!-- If, when starting the activity, there is already an 651 instance of the same activity class in the foreground that is 652 interacting with the user, then 653 re-use that instance. This existing instance will receive a call to 654 {@link android.app.Activity#onNewIntent Activity.onNewIntent()} with 655 the new Intent that is being started. --> 656 <enum name="singleTop" value="1" /> 657 <!-- If, when starting the activity, there is already a task running 658 that starts with this activity, then instead of starting a new 659 instance the current task is brought to the front. The existing 660 instance will receive a call to {@link android.app.Activity#onNewIntent 661 Activity.onNewIntent()} 662 with the new Intent that is being started, and with the 663 {@link android.content.Intent#FLAG_ACTIVITY_BROUGHT_TO_FRONT 664 Intent.FLAG_ACTIVITY_BROUGHT_TO_FRONT} flag set. This is a superset 665 of the singleTop mode, where if there is already an instance 666 of the activity being started at the top of the stack, it will 667 receive the Intent as described there (without the 668 FLAG_ACTIVITY_BROUGHT_TO_FRONT flag set). See the 669 <a href="{@docRoot}guide/topics/fundamentals/tasks-and-back-stack.html">Tasks and Back 670 Stack</a> document for more details about tasks.--> 671 <enum name="singleTask" value="2" /> 672 <!-- Only allow one instance of this activity to ever be 673 running. This activity gets a unique task with only itself running 674 in it; if it is ever launched again with the same Intent, then that 675 task will be brought forward and its 676 {@link android.app.Activity#onNewIntent Activity.onNewIntent()} 677 method called. If this 678 activity tries to start a new activity, that new activity will be 679 launched in a separate task. See the 680 <a href="{@docRoot}guide/topics/fundamentals/tasks-and-back-stack.html">Tasks and Back 681 Stack</a> document for more details about tasks.--> 682 <enum name="singleInstance" value="3" /> 683 </attr> 684 685 <!-- Specify the orientation an activity should be run in. If not 686 specified, it will run in the current preferred orientation 687 of the screen. 688 <p>This attribute is supported by the <a 689 href="{@docRoot}guide/topics/manifest/activity-element.html">{@code <activity>}</a> 690 element. --> 691 <attr name="screenOrientation"> 692 <!-- No preference specified: let the system decide the best 693 orientation. This will either be the orientation selected 694 by the activity below, or the user's preferred orientation 695 if this activity is the bottom of a task. If the user 696 explicitly turned off sensor based orientation through settings 697 sensor based device rotation will be ignored. If not by default 698 sensor based orientation will be taken into account and the 699 orientation will changed based on how the user rotates the device. 700 Corresponds to 701 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_UNSPECIFIED}. --> 702 <enum name="unspecified" value="-1" /> 703 <!-- Would like to have the screen in a landscape orientation: that 704 is, with the display wider than it is tall, ignoring sensor data. 705 Corresponds to 706 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_LANDSCAPE}. --> 707 <enum name="landscape" value="0" /> 708 <!-- Would like to have the screen in a portrait orientation: that 709 is, with the display taller than it is wide, ignoring sensor data. 710 Corresponds to 711 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_PORTRAIT}. --> 712 <enum name="portrait" value="1" /> 713 <!-- Use the user's current preferred orientation of the handset. 714 Corresponds to 715 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_USER}. --> 716 <enum name="user" value="2" /> 717 <!-- Keep the screen in the same orientation as whatever is behind 718 this activity. 719 Corresponds to 720 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_BEHIND}. --> 721 <enum name="behind" value="3" /> 722 <!-- Orientation is determined by a physical orientation sensor: 723 the display will rotate based on how the user moves the device. 724 Ignores user's setting to turn off sensor-based rotation. 725 Corresponds to 726 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_SENSOR}. --> 727 <enum name="sensor" value="4" /> 728 <!-- Always ignore orientation determined by orientation sensor: 729 the display will not rotate when the user moves the device. 730 Corresponds to 731 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_NOSENSOR}. --> 732 <enum name="nosensor" value="5" /> 733 <!-- Would like to have the screen in landscape orientation, but can 734 use the sensor to change which direction the screen is facing. 735 Corresponds to 736 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_SENSOR_LANDSCAPE}. --> 737 <enum name="sensorLandscape" value="6" /> 738 <!-- Would like to have the screen in portrait orientation, but can 739 use the sensor to change which direction the screen is facing. 740 Corresponds to 741 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_SENSOR_PORTRAIT}. --> 742 <enum name="sensorPortrait" value="7" /> 743 <!-- Would like to have the screen in landscape orientation, turned in 744 the opposite direction from normal landscape. 745 Corresponds to 746 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_REVERSE_LANDSCAPE}. --> 747 <enum name="reverseLandscape" value="8" /> 748 <!-- Would like to have the screen in portrait orientation, turned in 749 the opposite direction from normal portrait. 750 Corresponds to 751 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_REVERSE_PORTRAIT}. --> 752 <enum name="reversePortrait" value="9" /> 753 <!-- Orientation is determined by a physical orientation sensor: 754 the display will rotate based on how the user moves the device. 755 This allows any of the 4 possible rotations, regardless of what 756 the device will normally do (for example some devices won't 757 normally use 180 degree rotation). 758 Corresponds to 759 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_FULL_SENSOR}. --> 760 <enum name="fullSensor" value="10" /> 761 <!-- Would like to have the screen in landscape orientation, but if 762 the user has enabled sensor-based rotation then we can use the 763 sensor to change which direction the screen is facing. 764 Corresponds to 765 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_USER_LANDSCAPE}. --> 766 <enum name="userLandscape" value="11" /> 767 <!-- Would like to have the screen in portrait orientation, but if 768 the user has enabled sensor-based rotation then we can use the 769 sensor to change which direction the screen is facing. 770 Corresponds to 771 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_USER_PORTRAIT}. --> 772 <enum name="userPortrait" value="12" /> 773 <!-- Respect the user's sensor-based rotation preference, but if 774 sensor-based rotation is enabled then allow the screen to rotate 775 in all 4 possible directions regardless of what 776 the device will normally do (for example some devices won't 777 normally use 180 degree rotation). 778 Corresponds to 779 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_FULL_USER}. --> 780 <enum name="fullUser" value="13" /> 781 <!-- Screen is locked to its current rotation, whatever that is. 782 Corresponds to 783 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_LOCKED}. --> 784 <enum name="locked" value="14" /> 785 </attr> 786 787 <!-- Specify the configuration changes that trigger the system to recreate the 788 current activity if any of these configuration changes happen in the system. 789 The valid configuration changes include mcc and mnc which are the same with 790 those in configChanges. By default from Android O, we don't recreate the activity 791 even the app doesn't specify mcc or mnc in configChanges. If the app wants to 792 be recreated, specify them in recreateOnConfigChanges. --> 793 <attr name="recreateOnConfigChanges"> 794 <!-- The IMSI MCC has changed, that is a SIM has been detected and 795 updated the Mobile Country Code. --> 796 <flag name="mcc" value="0x0001" /> 797 <!-- The IMSI MNC has changed, that is a SIM has been detected and 798 updated the Mobile Network Code. --> 799 <flag name="mnc" value="0x0002" /> 800 </attr> 801 802 <!-- Specify one or more configuration changes that the activity will 803 handle itself. If not specified, the activity will be restarted 804 if any of these configuration changes happen in the system. Otherwise, 805 the activity will remain running and its 806 {@link android.app.Activity#onConfigurationChanged Activity.onConfigurationChanged} 807 method called with the new configuration. 808 809 <p>Note that all of these configuration changes can impact the 810 resource values seen by the application, so you will generally need 811 to re-retrieve all resources (including view layouts, drawables, etc) 812 to correctly handle any configuration change. 813 814 <p>These values must be kept in sync with those in 815 {@link android.content.pm.ActivityInfo} and 816 include/utils/ResourceTypes.h. --> 817 <attr name="configChanges"> 818 <!-- The IMSI MCC has changed, that is a SIM has been detected and 819 updated the Mobile Country Code. By default from Android O, we 820 don't recreate the activity even the app doesn't specify mcc in 821 configChanges. If the app wants to recreate the activity, specify 822 mcc in recreateOnConfigChanges. --> 823 <flag name="mcc" value="0x0001" /> 824 <!-- The IMSI MNC has changed, that is a SIM has been detected and 825 updated the Mobile Network Code. By default from Android O, we 826 don't recreate the activity even the app doesn't specify mnc in 827 configChanges. If the app wants to recreate the acvitity, specify 828 mnc in recreateOnConfigChanges. --> 829 <flag name="mnc" value="0x0002" /> 830 <!-- The locale has changed, that is the user has selected a new 831 language that text should be displayed in. --> 832 <flag name="locale" value="0x0004" /> 833 <!-- The touchscreen has changed. Should never normally happen. --> 834 <flag name="touchscreen" value="0x0008" /> 835 <!-- The keyboard type has changed, for example the user has plugged 836 in an external keyboard. --> 837 <flag name="keyboard" value="0x0010" /> 838 <!-- The keyboard or navigation accessibility has changed, for example 839 the user has slid the keyboard out to expose it. Note that 840 despite its name, this applied to any accessibility: keyboard 841 or navigation. --> 842 <flag name="keyboardHidden" value="0x0020" /> 843 <!-- The navigation type has changed. Should never normally happen. --> 844 <flag name="navigation" value="0x0040" /> 845 <!-- The screen orientation has changed, that is the user has 846 rotated the device. --> 847 <flag name="orientation" value="0x0080" /> 848 <!-- The screen layout has changed. This might be caused by a 849 different display being activated. --> 850 <flag name="screenLayout" value="0x0100" /> 851 <!-- The global user interface mode has changed. For example, 852 going in or out of car mode, night mode changing, etc. --> 853 <flag name="uiMode" value="0x0200" /> 854 <!-- The current available screen size has changed. If applications don't 855 target at least {@link android.os.Build.VERSION_CODES#HONEYCOMB_MR2} 856 then the activity will always handle this itself (the change 857 will not result in a restart). This represents a change in the 858 currently available size, so will change when the user switches 859 between landscape and portrait. --> 860 <flag name="screenSize" value="0x0400" /> 861 <!-- The physical screen size has changed. If applications don't 862 target at least {@link android.os.Build.VERSION_CODES#HONEYCOMB_MR2} 863 then the activity will always handle this itself (the change 864 will not result in a restart). This represents a change in size 865 regardless of orientation, so will only change when the actual 866 physical screen size has changed such as switching to an external 867 display. --> 868 <flag name="smallestScreenSize" value="0x0800" /> 869 <!-- The display density has changed. This might be caused by the user 870 specifying a different display scale, or it might be caused by a 871 different display being activated. --> 872 <flag name="density" value="0x1000" /> 873 <!-- The layout direction has changed. For example going from LTR to RTL. --> 874 <flag name="layoutDirection" value="0x2000" /> 875 <!-- The color mode of the screen has changed (color gamut or dynamic range). --> 876 <flag name="colorMode" value="0x4000" /> 877 <!-- The font scaling factor has changed, that is the user has 878 selected a new global font size. --> 879 <flag name="fontScale" value="0x40000000" /> 880 </attr> 881 882 <!-- Indicate that the activity can be launched as the embedded child of another 883 activity. Particularly in the case where the child lives in a container 884 such as a Display owned by another activity. 885 886 <p>The default value of this attribute is <code>false</code>. --> 887 <attr name="allowEmbedded" format="boolean" /> 888 889 <!-- Descriptive text for the associated data. --> 890 <attr name="description" format="reference" /> 891 892 <!-- The name of the application package that an Instrumentation object 893 will run against. --> 894 <attr name="targetPackage" format="string" /> 895 896 <!-- The name of an application's processes that an Instrumentation object 897 will run against. If not specified, only runs in the main process of the targetPackage. 898 Can either be a comma-separated list of process names or '*' for any process that 899 launches to run targetPackage code. --> 900 <attr name="targetProcesses" format="string" /> 901 902 <!-- Flag indicating that an Instrumentation class wants to take care 903 of starting/stopping profiling itself, rather than relying on 904 the default behavior of profiling the complete time it is running. 905 This allows it to target profiling data at a specific set of 906 operations. --> 907 <attr name="handleProfiling" format="boolean" /> 908 909 <!-- Flag indicating that an Instrumentation class should be run as a 910 functional test. --> 911 <attr name="functionalTest" format="boolean" /> 912 913 <!-- The touch screen type used by an application. --> 914 <attr name="reqTouchScreen"> 915 <enum name="undefined" value="0" /> 916 <enum name="notouch" value="1" /> 917 <enum name="stylus" value="2" /> 918 <enum name="finger" value="3" /> 919 </attr> 920 921 <!-- The input method preferred by an application. --> 922 <attr name="reqKeyboardType"> 923 <enum name="undefined" value="0" /> 924 <enum name="nokeys" value="1" /> 925 <enum name="qwerty" value="2" /> 926 <enum name="twelvekey" value="3" /> 927 </attr> 928 929 <!-- Application's requirement for a hard keyboard --> 930 <attr name="reqHardKeyboard" format="boolean" /> 931 932 <!-- The navigation device preferred by an application. --> 933 <attr name="reqNavigation"> 934 <enum name="undefined" value="0" /> 935 <enum name="nonav" value="1" /> 936 <enum name="dpad" value="2" /> 937 <enum name="trackball" value="3" /> 938 <enum name="wheel" value="4" /> 939 </attr> 940 941 <!-- Application's requirement for five way navigation --> 942 <attr name="reqFiveWayNav" format="boolean" /> 943 944 <!-- The name of the class subclassing <code>BackupAgent</code> to manage 945 backup and restore of the application's data on external storage. --> 946 <attr name="backupAgent" format="string" /> 947 948 <!-- Whether to allow the application to participate in the backup 949 and restore infrastructure. If this attribute is set to <code>false</code>, 950 no backup or restore of the application will ever be performed, even by a 951 full-system backup that would otherwise cause all application data to be saved 952 via adb. The default value of this attribute is <code>true</code>. --> 953 <attr name="allowBackup" format="boolean" /> 954 955 <!-- Applications will set this in their manifest to opt-in to or out of full app data back-up 956 and restore. Alternatively they can set it to an xml resource within their app that will 957 be parsed by the BackupAgent to selectively backup files indicated within that xml. --> 958 <attr name="fullBackupContent" format="reference|boolean" /> 959 960 <!-- Indicates that even though the application provides a <code>BackupAgent</code>, 961 only full-data streaming backup operations are to be performed to save the app's 962 data. This lets the app rely on full-data backups while still participating in 963 the backup and restore process via the BackupAgent's full-data backup APIs. 964 When this attribute is <code>true</code> the app's BackupAgent overrides of 965 the onBackup() and onRestore() callbacks can be empty stubs. --> 966 <attr name="fullBackupOnly" format="boolean" /> 967 968 <!-- Whether the application in question should be terminated after its 969 settings have been restored during a full-system restore operation. 970 Single-package restore operations will never cause the application to 971 be shut down. Full-system restore operations typically only occur once, 972 when the phone is first set up. Third-party applications will not usually 973 need to use this attribute. 974 975 <p>The default is <code>true</code>, which means that after the application 976 has finished processing its data during a full-system restore, it will be 977 terminated. --> 978 <attr name="killAfterRestore" format="boolean" /> 979 980 <!-- @deprecated This attribute is not used by the Android operating system. --> 981 <attr name="restoreNeedsApplication" format="boolean" /> 982 983 <!-- Indicate that the application is prepared to attempt a restore of any 984 backed-up dataset, even if the backup is apparently from a newer version 985 of the application than is currently installed on the device. Setting 986 this attribute to <code>true</code> will permit the Backup Manager to 987 attempt restore even when a version mismatch suggests that the data are 988 incompatible. <em>Use with caution!</em> 989 990 <p>The default value of this attribute is <code>false</code>. --> 991 <attr name="restoreAnyVersion" format="boolean" /> 992 993 <!-- Indicates that full-data backup operations for this application may 994 be performed even if the application is in a foreground-equivalent 995 state. <em>Use with caution!</em> Setting this flag to <code>true</code> 996 can impact app behavior while the user is interacting with the device. 997 998 <p>If unspecified, the default value of this attribute is <code>false</code>, 999 which means that the OS will avoid backing up the application while it is 1000 running in the foreground (such as a music app that is actively playing 1001 music via a service in the startForeground() state). --> 1002 <attr name="backupInForeground" format="boolean" /> 1003 1004 <!-- The default install location defined by an application. --> 1005 <attr name="installLocation"> 1006 <!-- Let the system decide ideal install location --> 1007 <enum name="auto" value="0" /> 1008 <!-- Explicitly request to be installed on internal phone storage 1009 only. --> 1010 <enum name="internalOnly" value="1" /> 1011 <!-- Prefer to be installed on SD card. There is no guarantee that 1012 the system will honor this request. The application might end 1013 up being installed on internal storage if external media 1014 is unavailable or too full. --> 1015 <enum name="preferExternal" value="2" /> 1016 </attr> 1017 1018 <!-- If set to <code>true</code>, indicates to the platform that any split APKs 1019 installed for this application should be loaded into their own Context 1020 objects and not appear in the base application's Context. 1021 1022 <p>The default value of this attribute is <code>false</code>. --> 1023 <attr name="isolatedSplits" format="boolean" /> 1024 1025 <!-- If set to <code>true</code>, indicates to the platform that this APK is 1026 a 'feature' split and that it implicitly depends on the base APK. This distinguishes 1027 this split APK from a 'configuration' split, which provides resource overrides 1028 for a particular 'feature' split. Only useful when the base APK specifies 1029 <code>android:isolatedSplits="true"</code>. 1030 1031 <p>The default value of this attribute is <code>false</code>. --> 1032 <attr name="isFeatureSplit" format="boolean" /> 1033 1034 <!-- Extra options for an activity's UI. Applies to either the {@code <activity>} or 1035 {@code <application>} tag. If specified on the {@code <application>} 1036 tag these will be considered defaults for all activities in the 1037 application. --> 1038 <attr name="uiOptions"> 1039 <!-- No extra UI options. This is the default. --> 1040 <flag name="none" value="0" /> 1041 <!-- Split the options menu into a separate bar at the bottom of 1042 the screen when severely constrained for horizontal space. 1043 (e.g. portrait mode on a phone.) Instead of a small number 1044 of action buttons appearing in the action bar at the top 1045 of the screen, the action bar will split into the top navigation 1046 section and the bottom menu section. Menu items will not be 1047 split across the two bars; they will always appear together. --> 1048 <flag name="splitActionBarWhenNarrow" value="1" /> 1049 </attr> 1050 1051 <!-- The name of the logical parent of the activity as it appears in the manifest. --> 1052 <attr name="parentActivityName" format="string" /> 1053 1054 <!-- Define how an activity persist across reboots. Activities defined as "never" will not 1055 be persisted. Those defined as "always" will be persisted. Those defined as "taskOnly" 1056 will persist the root activity of the task only. See below for more detail as to 1057 what gets persisted. --> 1058 <attr name="persistableMode"> 1059 <!-- The default. If this activity forms the root of a task then that task will be 1060 persisted across reboots but only the launching intent will be used. If the task 1061 relinquishes its identity then the intent used is that of the topmost inherited 1062 identity. All activities above this activity in the task will not be persisted. 1063 In addition this activity will not be passed a PersistableBundle into which it 1064 could have stored its state. --> 1065 <enum name="persistRootOnly" value="0" /> 1066 <!-- If this activity forms the root of a task then that task will not be persisted 1067 across reboots --> 1068 <enum name="persistNever" value="1" /> 1069 <!-- If this activity forms the root of a task then the task and this activity will 1070 be persisted across reboots. If the activity above this activity is also 1071 tagged with the attribute <code>"persist"</code> then it will be persisted as well. 1072 And so on up the task stack until either an activity without the 1073 <code>persistableMode="persistAcrossReboots"</code> attribute or one that was launched 1074 with the flag Intent.FLAG_CLEAR_TASK_WHEN_RESET is encountered. 1075 1076 <p>Activities that are declared with the persistAcrossReboots attribute will be 1077 provided with a PersistableBundle in onSavedInstanceState(), These activities may 1078 use this PeristableBundle to save their state. Then, following a reboot, that 1079 PersistableBundle will be provided back to the activity in its onCreate() method. --> 1080 <enum name="persistAcrossReboots" value="2" /> 1081 </attr> 1082 1083 <!-- This attribute specifies that an activity shall become the root activity of a 1084 new task each time it is launched. Using this attribute permits the user to 1085 have multiple documents from the same applications appear in the recent tasks list. 1086 1087 <p>Such a document is any kind of item for which an application may want to 1088 maintain multiple simultaneous instances. Examples might be text files, web 1089 pages, spreadsheets, or emails. Each such document will be in a separate 1090 task in the recent taskss list. 1091 1092 <p>This attribute is equivalent to adding the flag {@link 1093 android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT} to every Intent used to launch 1094 the activity. 1095 1096 <p>The documentLaunchMode attribute may be assigned one of four values, "none", 1097 "intoExisting", "always" and "never", described in detail below. For values other than 1098 <code>none</code> and <code>never</code> the activity must be defined with 1099 {@link android.R.attr#launchMode} <code>standard</code>. 1100 If this attribute is not specified, <code>none</code> will be used. 1101 Note that <code>none</code> can be overridden at run time if the Intent used 1102 to launch it contains the flag {@link android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT 1103 Intent.FLAG_ACTIVITY_NEW_DOCUMENT}. 1104 Similarly <code>intoExisting</code> will be overridden by the flag 1105 {@link android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT 1106 Intent.FLAG_ACTIVITY_NEW_DOCUMENT} combined with 1107 {@link android.content.Intent#FLAG_ACTIVITY_MULTIPLE_TASK 1108 Intent.FLAG_ACTIVITY_MULTIPLE_TASK}. If the value of 1109 documentLaunchModes is <code>never</code> then any use of 1110 {@link android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT 1111 Intent.FLAG_ACTIVITY_NEW_DOCUMENT} to launch this activity will be ignored. --> 1112 <attr name="documentLaunchMode"> 1113 <!-- The default mode, which will create a new task only when 1114 {@link android.content.Intent#FLAG_ACTIVITY_NEW_TASK 1115 Intent.FLAG_ACTIVITY_NEW_TASK} is set. --> 1116 <enum name="none" value="0" /> 1117 <!-- All tasks will be searched for one whose base Intent's ComponentName and 1118 data URI match those of the launching Intent. If such a task is found 1119 that task will be cleared and restarted with the root activity receiving a call 1120 to {@link android.app.Activity#onNewIntent Activity.onNewIntent}. If no 1121 such task is found a new task will be created. 1122 <p>This is the equivalent of launching an activity with {@link 1123 android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT Intent.FLAG_ACTIVITY_NEW_DOCUMENT} 1124 set and without {@link android.content.Intent#FLAG_ACTIVITY_MULTIPLE_TASK 1125 Intent.FLAG_ACTIVITY_MULTIPLE_TASK} set. --> 1126 <enum name="intoExisting" value="1" /> 1127 <!-- A new task rooted at this activity will be created. This will happen whether or 1128 not there is an existing task whose ComponentName and data URI match 1129 that of the launcing intent This is the equivalent of launching an activity 1130 with {@link 1131 android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT Intent.FLAG_ACTIVITY_NEW_DOCUMENT} 1132 and {@link android.content.Intent#FLAG_ACTIVITY_MULTIPLE_TASK 1133 Intent.FLAG_ACTIVITY_MULTIPLE_TASK} both set. --> 1134 <enum name="always" value="2" /> 1135 <!-- This activity will not be launched into a new document even if the Intent contains 1136 {@link android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT 1137 Intent.FLAG_ACTIVITY_NEW_DOCUMENT}. This gives the activity writer ultimate 1138 control over how their activity is used. Note that applications prior to api 1139 21 will default to documentLaunchMode="none" so only activities that explicitly 1140 opt out with <code>"never"</code> may do so. --> 1141 <enum name="never" value="3" /> 1142 </attr> 1143 1144 <!-- The maximum number of entries of tasks rooted at this activity in the recent task list. 1145 When this number of entries is reached the least recently used instance of this activity 1146 will be removed from recents. The value will be clamped between 1 and 100 inclusive. 1147 The default value for this if it is not specified is 15. --> 1148 <attr name="maxRecents" format="integer" /> 1149 1150 <!-- Tasks launched by activities with this attribute will remain in the recent tasks 1151 list until the last activity in the task is completed. When that happens the task 1152 will be automatically removed from the recent tasks list. This overrides the caller's 1153 use of {@link android.content.Intent#FLAG_ACTIVITY_RETAIN_IN_RECENTS 1154 Intent.FLAG_ACTIVITY_RETAIN_IN_RECENTS} --> 1155 <attr name="autoRemoveFromRecents" format="boolean" /> 1156 1157 <!-- Tasks whose root has this attribute set to true will replace baseIntent with that of the 1158 next activity in the task. If the next activity also has this attribute set to true then 1159 it will yield the baseIntent to any activity that it launches in the same task. This 1160 continues until an activity is encountered which has this attribute set to false. False 1161 is the default. This attribute set to true also permits activity's use of the 1162 TaskDescription to change labels, colors and icons in the recent task list. --> 1163 <attr name="relinquishTaskIdentity" format="boolean" /> 1164 1165 <!-- Indicate that it is okay for this activity be resumed while the previous 1166 activity is in the process of pausing, without waiting for the previous pause 1167 to complete. Use this with caution: your activity can not acquire any exclusive 1168 resources (such as opening the camera or recording audio) when it launches, or it 1169 may conflict with the previous activity and fail. 1170 1171 <p>The default value of this attribute is <code>false</code>. --> 1172 <attr name="resumeWhilePausing" format="boolean" /> 1173 1174 <!-- Indicates that it is okay for this activity to be resized to any dimension. Intended for a 1175 multi-window device where there can be multiple activities of various sizes on the screen 1176 at the same time. 1177 1178 <p>The default value is <code>false</code> for applications with 1179 <code>targetSdkVersion</code> lesser than {@link android.os.Build.VERSION_CODES#N} and 1180 <code>true</code> otherwise. 1181 1182 <p>NOTE: A task's root activity value is applied to all additional activities launched in 1183 the task. That is if the root activity of a task is resizeable then the system will treat 1184 all other activities in the task as resizeable and will not if the root activity isn't 1185 resizeable. 1186 1187 <p>NOTE: The value of {@link android.R.attr#screenOrientation} is ignored for 1188 resizeable activities when in multi-window mode. --> 1189 <attr name="resizeableActivity" format="boolean" /> 1190 1191 <!-- Indicates that the activity specifically supports the picture-in-picture form of 1192 multi-window. If true, this activity will support entering picture-in-picture, but will 1193 only support split-screen and other forms of multi-window if 1194 {@link android.R.attr#resizeableActivity} is also set to true. 1195 1196 Note that your activity may still be resized even if this attribute is true and 1197 {@link android.R.attr#resizeableActivity} is false. 1198 1199 <p>The default value is <code>false</code>. --> 1200 <attr name="supportsPictureInPicture" format="boolean" /> 1201 1202 <!-- This value indicates the maximum aspect ratio the activity supports. If the app runs on a 1203 device with a wider aspect ratio, the system automatically letterboxes the app, leaving 1204 portions of the screen unused so the app can run at its specified maximum aspect ratio. 1205 <p> 1206 Maximum aspect ratio, expressed as (longer dimension / shorter dimension) in decimal 1207 form. For example, if the maximum aspect ratio is 7:3, set value to 2.33. 1208 <p> 1209 Value needs to be greater or equal to 1.0, otherwise it is ignored. 1210 <p> 1211 NOTE: This attribute is ignored if the activity has 1212 {@link android.R.attr#resizeableActivity} set to true, since that means your activity 1213 supports any size. --> 1214 <attr name="maxAspectRatio" format="float" /> 1215 1216 <!-- This value indicates how tasks rooted at this activity will behave in lockTask mode. 1217 While in lockTask mode the system will not launch non-permitted tasks until 1218 lockTask mode is disabled. 1219 <p>While in lockTask mode with multiple permitted tasks running, each launched task is 1220 permitted to finish, transitioning to the previous locked task, until there is only one 1221 task remaining. At that point the last task running is not permitted to finish, unless it 1222 uses the value always. --> 1223 <attr name="lockTaskMode"> 1224 <!-- This is the default value. Tasks will not launch into lockTask mode but can be 1225 placed there by calling {@link android.app.Activity#startLockTask}. If a task with 1226 this mode has been whitelisted using {@link 1227 android.app.admin.DevicePolicyManager#setLockTaskPackages} then calling 1228 {@link android.app.Activity#startLockTask} will enter lockTask mode immediately, 1229 otherwise the user will be presented with a dialog to approve entering pinned mode. 1230 <p>If the system is already in lockTask mode when a new task rooted at this activity 1231 is launched that task will or will not start depending on whether the package of this 1232 activity has been whitelisted. 1233 <p>Tasks rooted at this activity can only exit lockTask mode using 1234 {@link android.app.Activity#stopLockTask}. --> 1235 <enum name="normal" value="0"/> 1236 <!-- Tasks will not launch into lockTask mode and cannot be placed there using 1237 {@link android.app.Activity#startLockTask} or be pinned from the Overview screen. 1238 If the system is already in lockTask mode when a new task rooted at this activity is 1239 launched that task will not be started. 1240 <p>Note: This mode is only available to system and privileged applications. 1241 Non-privileged apps with this value will be treated as normal. 1242 --> 1243 <enum name="never" value="1"/> 1244 <!-- Tasks rooted at this activity will always launch into lockTask mode. If the system is 1245 already in lockTask mode when this task is launched then the new task will be launched 1246 on top of the current task. Tasks launched in this mode are capable of exiting 1247 lockTask mode using {@link android.app.Activity#finish()}. 1248 <p>Note: This mode is only available to system and privileged applications. 1249 Non-privileged apps with this value will be treated as normal. 1250 --> 1251 <enum name="always" value="2"/> 1252 <!-- If the DevicePolicyManager (DPM) authorizes this package ({@link 1253 android.app.admin.DevicePolicyManager#setLockTaskPackages}) then this mode is 1254 identical to always, except that the activity needs to call 1255 {@link android.app.Activity#stopLockTask} before being able to finish if it is the last 1256 locked task. 1257 If the DPM does not authorize this package then this mode is identical to normal. --> 1258 <enum name="if_whitelisted" value="3"/> 1259 </attr> 1260 <!-- When set installer will extract native libraries. If set to false 1261 libraries in the apk must be stored and page-aligned. --> 1262 <attr name="extractNativeLibs" format="boolean"/> 1263 1264 <!-- Specify whether an activity intent filter will need to be verified thru its set 1265 of data URIs. This will only be used when the Intent's action is set to 1266 {@link android.content.Intent#ACTION_VIEW Intent.ACTION_VIEW} and the Intent's category is 1267 set to {@link android.content.Intent#CATEGORY_BROWSABLE Intent.CATEGORY_BROWSABLE} and the 1268 intern filter data scheme is set to "http" or "https". When set to true, the intent filter 1269 will need to use its data tag for getting the URIs to verify with. 1270 1271 For each URI, an HTTPS network request will be done to <code>/.well-known/statements.json</code> 1272 host to verify that the web site is okay with the app intercepting the URI. 1273 --> 1274 <attr name="autoVerify" format="boolean" /> 1275 1276 <!-- Specify whether a component should be visible to instant apps. 1277 --> 1278 <attr name="visibleToInstantApps" format="boolean" /> 1279 1280 <!-- An XML resource with the application's Network Security Config. --> 1281 <attr name="networkSecurityConfig" format="reference" /> 1282 1283 <!-- When an application is partitioned into splits, this is the name of the 1284 split that contains the defined component. --> 1285 <attr name="splitName" format="string" /> 1286 1287 <!-- Specifies the target sandbox this app wants to use. Higher sanbox versions 1288 will have increasing levels of security. 1289 1290 <p>The default value of this attribute is <code>1</code>. --> 1291 <attr name="targetSandboxVersion" format="integer" /> 1292 1293 <!-- The <code>manifest</code> tag is the root of an 1294 <code>AndroidManifest.xml</code> file, 1295 describing the contents of an Android package (.apk) file. One 1296 attribute must always be supplied: <code>package</code> gives a 1297 unique name for the package, using a Java-style naming convention 1298 to avoid name collisions. For example, applications published 1299 by Google could have names of the form 1300 <code>com.google.app.<em>appname</em></code> 1301 1302 <p>Inside of the manifest tag, may appear the following tags 1303 in any order: {@link #AndroidManifestPermission permission}, 1304 {@link #AndroidManifestPermissionGroup permission-group}, 1305 {@link #AndroidManifestPermissionTree permission-tree}, 1306 {@link #AndroidManifestUsesSdk uses-sdk}, 1307 {@link #AndroidManifestUsesPermission uses-permission}, 1308 {@link #AndroidManifestUsesConfiguration uses-configuration}, 1309 {@link #AndroidManifestApplication application}, 1310 {@link #AndroidManifestInstrumentation instrumentation}, 1311 {@link #AndroidManifestUsesFeature uses-feature}. --> 1312 <declare-styleable name="AndroidManifest"> 1313 <attr name="versionCode" /> 1314 <attr name="versionName" /> 1315 <attr name="revisionCode" /> 1316 <attr name="sharedUserId" /> 1317 <attr name="sharedUserLabel" /> 1318 <attr name="installLocation" /> 1319 <attr name="isolatedSplits" /> 1320 <attr name="isFeatureSplit" /> 1321 <attr name="targetSandboxVersion" /> 1322 </declare-styleable> 1323 1324 <!-- The <code>application</code> tag describes application-level components 1325 contained in the package, as well as general application 1326 attributes. Many of the attributes you can supply here (such 1327 as theme, label, icon, permission, process, taskAffinity, 1328 and allowTaskReparenting) serve 1329 as default values for the corresponding attributes of components 1330 declared inside of the application. 1331 1332 <p>Inside of this element you specify what the application contains, 1333 using the elements {@link #AndroidManifestProvider provider}, 1334 {@link #AndroidManifestService service}, 1335 {@link #AndroidManifestReceiver receiver}, 1336 {@link #AndroidManifestActivity activity}, 1337 {@link #AndroidManifestActivityAlias activity-alias}, and 1338 {@link #AndroidManifestUsesLibrary uses-library}. The application tag 1339 appears as a child of the root {@link #AndroidManifest manifest} tag in 1340 an application's manifest file. --> 1341 <declare-styleable name="AndroidManifestApplication" parent="AndroidManifest"> 1342 <!-- The (optional) fully-qualified name for a subclass of 1343 {@link android.app.Application} that the system instantiates before 1344 any other class when an app's process starts. Most applications 1345 don't need this attribute. If it's not specified, the system 1346 instantiates the base Application class instead.--> 1347 <attr name="name" /> 1348 <attr name="theme" /> 1349 <attr name="label" /> 1350 <attr name="icon" /> 1351 <attr name="roundIcon" /> 1352 <attr name="banner" /> 1353 <attr name="logo" /> 1354 <attr name="description" /> 1355 <attr name="permission" /> 1356 <attr name="process" /> 1357 <attr name="taskAffinity" /> 1358 <attr name="allowTaskReparenting" /> 1359 <!-- Indicate whether this application contains code. If set to false, 1360 there is no code associated with it and thus the system will not 1361 try to load its code when launching components. The default is true 1362 for normal behavior. --> 1363 <attr name="hasCode" format="boolean" /> 1364 <attr name="persistent" /> 1365 <attr name="persistentWhenFeatureAvailable" /> 1366 <attr name="requiredForAllUsers" /> 1367 <!-- Specify whether the components in this application are enabled or not (that is, can be 1368 instantiated by the system). 1369 If "false", it overrides any component specific values (a value of "true" will not 1370 override the component specific values). --> 1371 <attr name="enabled" /> 1372 <attr name="debuggable" /> 1373 <attr name="vmSafeMode" /> 1374 <attr name="hardwareAccelerated" /> 1375 <!-- Name of activity to be launched for managing the application's space on the device. --> 1376 <attr name="manageSpaceActivity" /> 1377 <attr name="allowClearUserData" /> 1378 <attr name="testOnly" /> 1379 <attr name="backupAgent" /> 1380 <attr name="allowBackup" /> 1381 <attr name="fullBackupOnly" /> 1382 <attr name="fullBackupContent" /> 1383 <attr name="killAfterRestore" /> 1384 <attr name="restoreNeedsApplication" /> 1385 <attr name="restoreAnyVersion" /> 1386 <attr name="backupInForeground" /> 1387 <!-- Request that your application's processes be created with 1388 a large Dalvik heap. This applies to <em>all</em> processes 1389 created for the application. It only applies to the first 1390 application loaded into a process; if using a sharedUserId 1391 to allow multiple applications to use a process, they all must 1392 use this option consistently or will get unpredictable results. --> 1393 <attr name="largeHeap" format="boolean" /> 1394 <!-- Declare that this application can't participate in the normal 1395 state save/restore mechanism. Since it is not able to save and 1396 restore its state on demand, 1397 it can not participate in the normal activity lifecycle. It will 1398 not be killed while in the background; the user must explicitly 1399 quit it. Only one such app can be running at a time; if the user 1400 tries to launch a second such app, they will be prompted 1401 to quit the first before doing so. While the 1402 application is running, the user will be informed of this. 1403 @hide --> 1404 <attr name="cantSaveState" format="boolean" /> 1405 <attr name="uiOptions" /> 1406 <!-- Declare that your application will be able to deal with RTL (right to left) layouts. 1407 The default value is false. --> 1408 <attr name="supportsRtl" format="boolean" /> 1409 <!-- Declare that this application requires access to restricted accounts of a certain 1410 type. The default value is null and restricted accounts won\'t be visible to this 1411 application. The type should correspond to the account authenticator type, such as 1412 "com.google". --> 1413 <attr name="restrictedAccountType" format="string"/> 1414 <!-- Declare that this application requires an account of a certain 1415 type. The default value is null and indicates that the application can work without 1416 any accounts. The type should correspond to the account authenticator type, such as 1417 "com.google". --> 1418 <attr name="requiredAccountType" format="string"/> 1419 <!-- @deprecated replaced by setting appCategory attribute to "game" --> 1420 <attr name="isGame" /> 1421 <!-- Declare that this application may use cleartext traffic, such as HTTP rather than 1422 HTTPS; WebSockets rather than WebSockets Secure; XMPP, IMAP, STMP without STARTTLS or 1423 TLS). Defaults to true. If set to false {@code false}, the application declares that it 1424 does not intend to use cleartext network traffic, in which case platform components 1425 (e.g. HTTP stacks, {@code DownloadManager}, {@code MediaPlayer}) will refuse 1426 applications's requests to use cleartext traffic. Third-party libraries are encouraged 1427 to honor this flag as well. --> 1428 <attr name="usesCleartextTraffic" /> 1429 <attr name="multiArch" /> 1430 <attr name="extractNativeLibs" /> 1431 <attr name="defaultToDeviceProtectedStorage" format="boolean" /> 1432 <attr name="directBootAware" /> 1433 <attr name="resizeableActivity" /> 1434 <attr name="maxAspectRatio" /> 1435 <attr name="networkSecurityConfig" /> 1436 <!-- Declare the category of this app. Categories are used to cluster multiple apps 1437 together into meaningful groups, such as when summarizing battery, network, or 1438 disk usage. Apps should only define this value when they fit well into one of 1439 the specific categories. --> 1440 <attr name="appCategory"> 1441 <!-- Apps which are primarily games. --> 1442 <enum name="game" value="0" /> 1443 <!-- Apps which primarily work with audio or music, such as music players. --> 1444 <enum name="audio" value="1" /> 1445 <!-- Apps which primarily work with video or movies, such as streaming video apps. --> 1446 <enum name="video" value="2" /> 1447 <!-- Apps which primarily work with images or photos, such as camera or gallery apps. --> 1448 <enum name="image" value="3" /> 1449 <!-- Apps which are primarily social apps, such as messaging, communication, email, or social network apps. --> 1450 <enum name="social" value="4" /> 1451 <!-- Apps which are primarily news apps, such as newspapers, magazines, or sports apps. --> 1452 <enum name="news" value="5" /> 1453 <!-- Apps which are primarily maps apps, such as navigation apps. --> 1454 <enum name="maps" value="6" /> 1455 <!-- Apps which are primarily productivity apps, such as cloud storage or workplace apps. --> 1456 <enum name="productivity" value="7" /> 1457 </attr> 1458 1459 </declare-styleable> 1460 <!-- The <code>permission</code> tag declares a security permission that can be 1461 used to control access from other packages to specific components or 1462 features in your package (or other packages). See the 1463 <a href="{@docRoot}guide/topics/security/security.html">Security and Permissions</a> 1464 document for more information on permissions. 1465 1466 <p>This appears as a child tag of the root 1467 {@link #AndroidManifest manifest} tag. --> 1468 <declare-styleable name="AndroidManifestPermission" parent="AndroidManifest"> 1469 <!-- Required public name of the permission, which other components and 1470 packages will use when referring to this permission. This is a string using 1471 Java-style scoping to ensure it is unique. The prefix will often 1472 be the same as our overall package name, for example 1473 "com.mycompany.android.myapp.SomePermission". --> 1474 <attr name="name" /> 1475 <attr name="label" /> 1476 <attr name="icon" /> 1477 <attr name="roundIcon" /> 1478 <attr name="banner" /> 1479 <attr name="logo" /> 1480 <attr name="permissionGroup" /> 1481 <attr name="description" /> 1482 <attr name="protectionLevel" /> 1483 <attr name="permissionFlags" /> 1484 </declare-styleable> 1485 1486 <!-- The <code>permission-group</code> tag declares a logical grouping of 1487 related permissions. 1488 1489 <p>Note that this tag does not declare a permission itself, only 1490 a namespace in which further permissions can be placed. See 1491 the {@link #AndroidManifestPermission <permission>} tag for 1492 more information. 1493 1494 <p>This appears as a child tag of the root 1495 {@link #AndroidManifest manifest} tag. --> 1496 <declare-styleable name="AndroidManifestPermissionGroup" parent="AndroidManifest"> 1497 <!-- Required public name of the permission group, permissions will use 1498 to specify the group they are in. This is a string using 1499 Java-style scoping to ensure it is unique. The prefix will often 1500 be the same as our overall package name, for example 1501 "com.mycompany.android.myapp.SomePermission". --> 1502 <attr name="name" /> 1503 <attr name="label" /> 1504 <attr name="icon" /> 1505 <attr name="roundIcon" /> 1506 <attr name="banner" /> 1507 <attr name="logo" /> 1508 <attr name="description" /> 1509 <attr name="permissionGroupFlags" /> 1510 <attr name="priority" /> 1511 </declare-styleable> 1512 1513 <!-- The <code>permission-tree</code> tag declares the base of a tree of 1514 permission values: it declares that this package has ownership of 1515 the given permission name, as well as all names underneath it 1516 (separated by '.'). This allows you to use the 1517 {@link android.content.pm.PackageManager#addPermission 1518 PackageManager.addPermission()} method to dynamically add new 1519 permissions under this tree. 1520 1521 <p>Note that this tag does not declare a permission itself, only 1522 a namespace in which further permissions can be placed. See 1523 the {@link #AndroidManifestPermission <permission>} tag for 1524 more information. 1525 1526 <p>This appears as a child tag of the root 1527 {@link #AndroidManifest manifest} tag. --> 1528 <declare-styleable name="AndroidManifestPermissionTree" parent="AndroidManifest"> 1529 <!-- Required public name of the permission tree, which is the base name 1530 of all permissions under it. This is a string using 1531 Java-style scoping to ensure it is unique. The prefix will often 1532 be the same as our overall package name, for example 1533 "com.mycompany.android.myapp.SomePermission". A permission tree name 1534 must have more than two segments in its path; that is, 1535 "com.me.foo" is okay, but not "com.me" or "com". --> 1536 <attr name="name" /> 1537 <attr name="label" /> 1538 <attr name="icon" /> 1539 <attr name="roundIcon" /> 1540 <attr name="banner" /> 1541 <attr name="logo" /> 1542 </declare-styleable> 1543 1544 <!-- The <code>uses-permission</code> tag requests a 1545 {@link #AndroidManifestPermission <permission>} that the containing 1546 package must be granted in order for it to operate correctly. For runtime 1547 permissions, i.e. ones with <code>dangerous</code> protection level, on a 1548 platform that supports runtime permissions, the permission will not be 1549 granted until the app explicitly requests it at runtime and the user approves 1550 the grant. You cannot request at runtime permissions that are not declared 1551 as used in the manifest. See the 1552 <a href="{@docRoot}guide/topics/security/security.html">Security and Permissions</a> 1553 document for more information on permissions. Also available is a 1554 {@link android.Manifest.permission list of permissions} included 1555 with the base platform. 1556 1557 <p>This appears as a child tag of the root 1558 {@link #AndroidManifest manifest} tag. --> 1559 <declare-styleable name="AndroidManifestUsesPermission" parent="AndroidManifest"> 1560 <!-- Required name of the permission you use, as published with the 1561 corresponding name attribute of a 1562 {@link android.R.styleable#AndroidManifestPermission <permission>} 1563 tag; often this is one of the {@link android.Manifest.permission standard 1564 system permissions}. --> 1565 <attr name="name" /> 1566 <!-- Optional: specify the maximum version of the Android OS for which the 1567 application wishes to request the permission. When running on a version 1568 of Android higher than the number given here, the permission will not 1569 be requested. --> 1570 <attr name="maxSdkVersion" format="integer" /> 1571 <!-- Optional: the system must support this feature for the permission to be 1572 requested. If it doesn't support the feature, it will be as if the manifest didn't 1573 request it at all. --> 1574 <attr name="requiredFeature" format="string" /> 1575 <!-- Optional: the system must NOT support this feature for the permission to be 1576 requested. If it does support the feature, it will be as if the manifest didn't 1577 request it at all. --> 1578 <attr name="requiredNotFeature" format="string" /> 1579 </declare-styleable> 1580 1581 <!-- The <code>uses-configuration</code> tag specifies 1582 a specific hardware configuration value used by the application. 1583 For example an application might specify that it requires 1584 a physical keyboard or a particular navigation method like 1585 trackball. Multiple such attribute values can be specified by the 1586 application. 1587 1588 <p>This appears as a child tag of the root 1589 {@link #AndroidManifest manifest} tag. 1590 1591 @deprecated Use <code>feature-group</code> instead.--> 1592 <declare-styleable name="AndroidManifestUsesConfiguration" parent="AndroidManifest"> 1593 <!-- The type of touch screen used by an application. --> 1594 <attr name="reqTouchScreen" /> 1595 <attr name="reqKeyboardType" /> 1596 <attr name="reqHardKeyboard" /> 1597 <attr name="reqNavigation" /> 1598 <attr name="reqFiveWayNav" /> 1599 </declare-styleable> 1600 1601 <!-- The <code>uses-feature</code> tag specifies a specific device 1602 hardware or software feature used by the application. For 1603 example an application might specify that it requires 1604 a camera. Multiple attribute values can be specified by the 1605 application. 1606 1607 <p>This appears as a child tag of the root 1608 {@link #AndroidManifest manifest} tag. --> 1609 <declare-styleable name="AndroidManifestUsesFeature" parent="AndroidManifest"> 1610 <!-- The name of the feature that is being used. --> 1611 <attr name="name" /> 1612 <!-- The version of the feature that is being used. --> 1613 <attr name="version" format="integer" /> 1614 <!-- The GLES driver version number needed by an application. 1615 The higher 16 bits represent the major number and the lower 16 bits 1616 represent the minor number. For example for GL 1.2 referring to 1617 0x00000102, the actual value should be set as 0x00010002. --> 1618 <attr name="glEsVersion" format="integer" /> 1619 <!-- Specify whether this feature is required for the application. 1620 The default is true, meaning the application requires the 1621 feature, and does not want to be installed on devices that 1622 don't support it. If you set this to false, then this will 1623 not impose a restriction on where the application can be 1624 installed. --> 1625 <attr name="required" format="boolean" /> 1626 </declare-styleable> 1627 1628 <!-- The <code>feature-group</code> tag specifies 1629 a set of one or more <code>uses-feature</code> elements that 1630 the application can utilize. An application uses multiple 1631 <code>feature-group</code> sets to indicate that it can support 1632 different combinations of features. 1633 1634 <p>This appears as a child tag of the root 1635 {@link #AndroidManifest manifest} tag. --> 1636 <declare-styleable name="AndroidManifestFeatureGroup"> 1637 <!-- The human-readable name of the feature group. --> 1638 <attr name="label" /> 1639 </declare-styleable> 1640 1641 <!-- The <code>uses-sdk</code> tag describes the SDK features that the 1642 containing package must be running on to operate correctly. 1643 1644 <p>This appears as a child tag of the root 1645 {@link #AndroidManifest manifest} tag. --> 1646 <declare-styleable name="AndroidManifestUsesSdk" parent="AndroidManifest"> 1647 <!-- This is the minimum SDK version number that the application 1648 requires. This number is an abstract integer, from the list 1649 in {@link android.os.Build.VERSION_CODES} If 1650 not supplied, the application will work on any SDK. This 1651 may also be string (such as "Donut") if the application was built 1652 against a development branch, in which case it will only work against 1653 the development builds. --> 1654 <attr name="minSdkVersion" format="integer|string" /> 1655 <!-- This is the SDK version number that the application is targeting. 1656 It is able to run on older versions (down to minSdkVersion), but 1657 was explicitly tested to work with the version specified here. 1658 Specifying this version allows the platform to disable compatibility 1659 code that are not required or enable newer features that are not 1660 available to older applications. This may also be a string 1661 (such as "Donut") if this is built against a development 1662 branch, in which case minSdkVersion is also forced to be that 1663 string. --> 1664 <attr name="targetSdkVersion" format="integer|string" /> 1665 <!-- This is the maximum SDK version number that an application works 1666 on. You can use this to ensure your application is filtered out 1667 of later versions of the platform when you know you have 1668 incompatibility with them. --> 1669 <attr name="maxSdkVersion" /> 1670 </declare-styleable> 1671 1672 <!-- The <code>library</code> tag declares that this apk is providing itself 1673 as a shared library for other applications to use. It can only be used 1674 with apks that are built in to the system image. Other apks can link to 1675 it with the {@link #AndroidManifestUsesLibrary uses-library} tag. 1676 1677 <p>This appears as a child tag of the 1678 {@link #AndroidManifestApplication application} tag. --> 1679 <declare-styleable name="AndroidManifestLibrary" parent="AndroidManifest"> 1680 <!-- Required public name of the library, which other components and 1681 packages will use when referring to this library. This is a string using 1682 Java-style scoping to ensure it is unique. The name should typically 1683 be the same as the apk's package name. --> 1684 <attr name="name" /> 1685 </declare-styleable> 1686 1687 1688 <!-- The <code>static-library</code> tag declares that this apk is providing itself 1689 as a static shared library for other applications to use. Any app can declare such 1690 a library and there can be only one static shared library per package. These libraries 1691 are updatable, multiple versions can be installed at the same time, and an app links 1692 against a specific version simulating static linking while allowing code sharing. 1693 Other apks can link to it with the {@link #AndroidManifestUsesLibrary uses-static-library} 1694 tag. 1695 1696 <p>This appears as a child tag of the 1697 {@link #AndroidManifestApplication application} tag. --> 1698 <declare-styleable name="AndroidManifestStaticLibrary" parent="AndroidManifestApplication"> 1699 <!-- Required public name of the library, which other components and 1700 packages will use when referring to this library. This is a string using 1701 Java-style scoping to ensure it is unique. The name should typically 1702 be the same as the apk's package name. --> 1703 <attr name="name" /> 1704 <!-- Required specific library version. --> 1705 <attr name="version" /> 1706 </declare-styleable> 1707 1708 <!-- The <code>uses-libraries</code> specifies a shared library that this 1709 package requires to be linked against. Specifying this flag tells the 1710 system to include this library's code in your class loader. 1711 1712 <p>This appears as a child tag of the 1713 {@link #AndroidManifestApplication application} tag. --> 1714 <declare-styleable name="AndroidManifestUsesLibrary" parent="AndroidManifestApplication"> 1715 <!-- Required name of the library you use. --> 1716 <attr name="name" /> 1717 <!-- Specify whether this library is required for the application. 1718 The default is true, meaning the application requires the 1719 library, and does not want to be installed on devices that 1720 don't support it. If you set this to false, then this will 1721 allow the application to be installed even if the library 1722 doesn't exist, and you will need to check for its presence 1723 dynamically at runtime. --> 1724 <attr name="required" /> 1725 </declare-styleable> 1726 1727 <!-- The <code>uses-static-library</code> specifies a shared <strong>static</strong> 1728 library that this package requires to be statically linked against. Specifying 1729 this tag tells the system to include this library's code in your class loader. 1730 Depending on a static shared library is equivalent to statically linking with 1731 the library at build time while it offers apps to share code defined in such 1732 libraries. Hence, static libraries are strictly required. 1733 1734 <p>This appears as a child tag of the 1735 {@link #AndroidManifestApplication application} tag. --> 1736 <declare-styleable name="AndroidManifestUsesStaticLibrary" parent="AndroidManifestApplication"> 1737 <!-- Required name of the library you use. --> 1738 <attr name="name" /> 1739 <!-- Specify which version of the shared library should be statically linked. --> 1740 <attr name="version" /> 1741 <!-- The SHA-256 digest of the library signing certificate. --> 1742 <attr name="certDigest" format="string" /> 1743 </declare-styleable> 1744 1745 <!-- The <code>supports-screens</code> specifies the screen dimensions an 1746 application supports. By default a modern application supports all 1747 screen sizes and must explicitly disable certain screen sizes here; 1748 older applications are assumed to only support the traditional normal 1749 (HVGA) screen size. Note that screen size is a separate axis from 1750 density, and is determined as the available pixels to an application 1751 after density scaling has been applied. 1752 1753 <p>This appears as a child tag of the 1754 {@link #AndroidManifest manifest} tag. --> 1755 <declare-styleable name="AndroidManifestSupportsScreens" parent="AndroidManifest"> 1756 <!-- Starting with {@link android.os.Build.VERSION_CODES#HONEYCOMB_MR2}, 1757 this is the new way to specify the minimum screen size an application is 1758 compatible with. This attribute provides the required minimum 1759 "smallest screen width" (as per the -swNNNdp resource configuration) 1760 that the application can run on. For example, a typical phone 1761 screen is 320, a 7" tablet 600, and a 10" tablet 720. If the 1762 smallest screen width of the device is below the value supplied here, 1763 then the application is considered incompatible with that device. 1764 If not supplied, then any old smallScreens, normalScreens, largeScreens, 1765 or xlargeScreens attributes will be used instead. --> 1766 <attr name="requiresSmallestWidthDp" format="integer" /> 1767 <!-- Starting with {@link android.os.Build.VERSION_CODES#HONEYCOMB_MR2}, 1768 this is the new way to specify the largest screens an application is 1769 compatible with. This attribute provides the maximum 1770 "smallest screen width" (as per the -swNNNdp resource configuration) 1771 that the application is designed for. If this value is smaller than 1772 the "smallest screen width" of the device it is running on, the user 1773 is offered to run it in a compatibility mode that emulates a 1774 smaller screen and zooms it to fit the screen. Currently the compatibility mode only 1775 emulates phone screens with a 320dp width, so compatibility mode is not applied if the 1776 value for compatibleWidthLimitDp is larger than 320. --> 1777 <attr name="compatibleWidthLimitDp" format="integer" /> 1778 <!-- Starting with {@link android.os.Build.VERSION_CODES#HONEYCOMB_MR2}, 1779 this is the new way to specify the screens an application is 1780 compatible with. This attribute provides the maximum 1781 "smallest screen width" (as per the -swNNNdp resource configuration) 1782 that the application can work well on. If this value is smaller than 1783 the "smallest screen width" of the device it is running on, the 1784 application will be forced in to screen compatibility mode with 1785 no way for the user to turn it off. Currently the compatibility mode only 1786 emulates phone screens with a 320dp width, so compatibility mode is not applied if the 1787 value for largestWidthLimitDp is larger than 320. --> 1788 <attr name="largestWidthLimitDp" format="integer" /> 1789 <!-- Indicates whether the application supports smaller screen form-factors. 1790 A small screen is defined as one with a smaller aspect ratio than 1791 the traditional HVGA screen; that is, for a portrait screen, less 1792 tall than an HVGA screen. In practice, this means a QVGA low 1793 density or VGA high density screen. An application that does 1794 not support small screens <em>will not be available</em> for 1795 small screen devices, since there is little the platform can do 1796 to make such an application work on a smaller screen. --> 1797 <attr name="smallScreens" format="boolean" /> 1798 <!-- Indicates whether an application supports the normal screen 1799 form-factors. Traditionally this is an HVGA normal density 1800 screen, but WQVGA low density and WVGA high density are also 1801 considered to be normal. This attribute is true by default, 1802 and applications currently should leave it that way. --> 1803 <attr name="normalScreens" format="boolean" /> 1804 <!-- Indicates whether the application supports larger screen form-factors. 1805 A large screen is defined as a screen that is significantly larger 1806 than a normal phone screen, and thus may require some special care 1807 on the application's part to make good use of it. An example would 1808 be a VGA <em>normal density</em> screen, though even larger screens 1809 are certainly possible. An application that does not support 1810 large screens will be placed as a postage stamp on such a 1811 screen, so that it retains the dimensions it was originally 1812 designed for. --> 1813 <attr name="largeScreens" format="boolean" /> 1814 <!-- Indicates whether the application supports extra large screen form-factors. --> 1815 <attr name="xlargeScreens" format="boolean" /> 1816 <!-- Indicates whether the application can resize itself to newer 1817 screen sizes. This is mostly used to distinguish between old 1818 applications that may not be compatible with newly introduced 1819 screen sizes and newer applications that should be; it will be 1820 set for you automatically based on whether you are targeting 1821 a newer platform that supports more screens. --> 1822 <attr name="resizeable" format="boolean" /> 1823 <!-- Indicates whether the application can accommodate any screen 1824 density. Older applications are assumed to not be able to, 1825 new ones able to. You can explicitly supply your abilities 1826 here. --> 1827 <attr name="anyDensity" format="boolean" /> 1828 </declare-styleable> 1829 1830 <!-- Private tag to declare system protected broadcast actions. 1831 1832 <p>This appears as a child tag of the root 1833 {@link #AndroidManifest manifest} tag. --> 1834 <declare-styleable name="AndroidManifestProtectedBroadcast" parent="AndroidManifest"> 1835 <attr name="name" /> 1836 </declare-styleable> 1837 1838 <!-- Private tag to declare the original package name that this package is 1839 based on. Only used for packages installed in the system image. If 1840 given, and different than the actual package name, and the given 1841 original package was previously installed on the device but the new 1842 one was not, then the data for the old one will be renamed to be 1843 for the new package. 1844 1845 <p>This appears as a child tag of the root 1846 {@link #AndroidManifest manifest} tag. --> 1847 <declare-styleable name="AndroidManifestOriginalPackage" parent="AndroidManifest"> 1848 <attr name="name" /> 1849 </declare-styleable> 1850 1851 <!-- The <code>provider</code> tag declares a 1852 {@link android.content.ContentProvider} class that is available 1853 as part of the package's application components, supplying structured 1854 access to data managed by the application. 1855 1856 <p>This appears as a child tag of the 1857 {@link #AndroidManifestApplication application} tag. --> 1858 <declare-styleable name="AndroidManifestProvider" parent="AndroidManifestApplication"> 1859 <!-- Required name of the class implementing the provider, deriving from 1860 {@link android.content.ContentProvider}. This is a fully 1861 qualified class name (for example, com.mycompany.myapp.MyProvider); as a 1862 short-hand if the first character of the class 1863 is a period then it is appended to your package name. --> 1864 <attr name="name" /> 1865 <attr name="label" /> 1866 <attr name="description" /> 1867 <attr name="icon" /> 1868 <attr name="roundIcon" /> 1869 <attr name="banner" /> 1870 <attr name="logo" /> 1871 <attr name="process" /> 1872 <attr name="authorities" /> 1873 <attr name="syncable" /> 1874 <attr name="readPermission" /> 1875 <attr name="writePermission" /> 1876 <attr name="grantUriPermissions" /> 1877 <attr name="permission" /> 1878 <attr name="multiprocess" /> 1879 <attr name="initOrder" /> 1880 <!-- Specify whether this provider is enabled or not (that is, can be instantiated by the system). 1881 It can also be specified for an application as a whole, in which case a value of "false" 1882 will override any component specific values (a value of "true" will not override the 1883 component specific values). --> 1884 <attr name="enabled" /> 1885 <attr name="exported" /> 1886 <attr name="singleUser" /> 1887 <attr name="directBootAware" /> 1888 <attr name="visibleToInstantApps" /> 1889 <!-- The code for this component is located in the given split. --> 1890 <attr name="splitName" /> 1891 </declare-styleable> 1892 1893 <!-- Attributes that can be supplied in an AndroidManifest.xml 1894 <code>grant-uri-permission</code> tag, a child of the 1895 {@link #AndroidManifestProvider provider} tag, describing a specific 1896 URI path that can be granted as a permission. This tag can be 1897 specified multiple time to supply multiple paths. --> 1898 <declare-styleable name="AndroidManifestGrantUriPermission" parent="AndroidManifestProvider"> 1899 <!-- Specify a URI path that must exactly match, as per 1900 {@link android.os.PatternMatcher} with 1901 {@link android.os.PatternMatcher#PATTERN_LITERAL}. --> 1902 <attr name="path" format="string" /> 1903 <!-- Specify a URI path that must be a prefix to match, as per 1904 {@link android.os.PatternMatcher} with 1905 {@link android.os.PatternMatcher#PATTERN_PREFIX}. --> 1906 <attr name="pathPrefix" format="string" /> 1907 <!-- Specify a URI path that matches a simple pattern, as per 1908 {@link android.os.PatternMatcher} with 1909 {@link android.os.PatternMatcher#PATTERN_SIMPLE_GLOB}. 1910 Note that because '\' is used as an escape character when 1911 reading the string from XML (before it is parsed as a pattern), 1912 you will need to double-escape: for example a literal "*" would 1913 be written as "\\*" and a literal "\" would be written as 1914 "\\\\". This is basically the same as what you would need to 1915 write if constructing the string in Java code. --> 1916 <attr name="pathPattern" format="string" /> 1917 </declare-styleable> 1918 1919 <!-- Attributes that can be supplied in an AndroidManifest.xml 1920 <code>path-permission</code> tag, a child of the 1921 {@link #AndroidManifestProvider provider} tag, describing a permission 1922 that allows access to a specific path in the provider. This tag can be 1923 specified multiple time to supply multiple paths. --> 1924 <declare-styleable name="AndroidManifestPathPermission" parent="AndroidManifestProvider"> 1925 <attr name="path" /> 1926 <attr name="pathPrefix" /> 1927 <attr name="pathPattern" /> 1928 <attr name="pathAdvancedPattern" /> 1929 <attr name="permission" /> 1930 <attr name="readPermission" /> 1931 <attr name="writePermission" /> 1932 </declare-styleable> 1933 1934 <!-- The <code>service</code> tag declares a 1935 {@link android.app.Service} class that is available 1936 as part of the package's application components, implementing 1937 long-running background operations or a rich communication API 1938 that can be called by other packages. 1939 1940 <p>Zero or more {@link #AndroidManifestIntentFilter intent-filter} 1941 tags can be included inside of a service, to specify the Intents 1942 that can connect with it. If none are specified, the service can 1943 only be accessed by direct specification of its class name. 1944 The service tag appears as a child tag of the 1945 {@link #AndroidManifestApplication application} tag. --> 1946 <declare-styleable name="AndroidManifestService" parent="AndroidManifestApplication"> 1947 <!-- Required name of the class implementing the service, deriving from 1948 {@link android.app.Service}. This is a fully 1949 qualified class name (for example, com.mycompany.myapp.MyService); as a 1950 short-hand if the first character of the class 1951 is a period then it is appended to your package name. --> 1952 <attr name="name" /> 1953 <attr name="label" /> 1954 <attr name="description" /> 1955 <attr name="icon" /> 1956 <attr name="roundIcon" /> 1957 <attr name="banner" /> 1958 <attr name="logo" /> 1959 <attr name="permission" /> 1960 <attr name="process" /> 1961 <!-- Specify whether the service is enabled or not (that is, can be instantiated by the system). 1962 It can also be specified for an application as a whole, in which case a value of "false" 1963 will override any component specific values (a value of "true" will not override the 1964 component specific values). --> 1965 <attr name="enabled" /> 1966 <attr name="exported" /> 1967 <!-- If set to true, this service with be automatically stopped 1968 when the user remove a task rooted in an activity owned by 1969 the application. The default is false. --> 1970 <attr name="stopWithTask" format="boolean" /> 1971 <!-- If set to true, this service will run under a special process 1972 that is isolated from the rest of the system. The only communication 1973 with it is through the Service API (binding and starting). --> 1974 <attr name="isolatedProcess" format="boolean" /> 1975 <attr name="singleUser" /> 1976 <attr name="directBootAware" /> 1977 <!-- If the service is an {@link android.R.attr#isolatedProcess} service, this permits a 1978 client to bind to the service as if it were running it its own package. The service 1979 must also be {@link android.R.attr#exported} if this flag is set. --> 1980 <attr name="externalService" format="boolean" /> 1981 <attr name="visibleToInstantApps" /> 1982 <!-- The code for this component is located in the given split. --> 1983 <attr name="splitName" /> 1984 </declare-styleable> 1985 1986 <!-- The <code>receiver</code> tag declares an 1987 {@link android.content.BroadcastReceiver} class that is available 1988 as part of the package's application components, allowing the 1989 application to receive actions or data broadcast by other 1990 applications even if it is not currently running. 1991 1992 <p>Zero or more {@link #AndroidManifestIntentFilter intent-filter} 1993 tags can be included inside of a receiver, to specify the Intents 1994 it will receive. If none are specified, the receiver will only 1995 be run when an Intent is broadcast that is directed at its specific 1996 class name. The receiver tag appears as a child tag of the 1997 {@link #AndroidManifestApplication application} tag. --> 1998 <declare-styleable name="AndroidManifestReceiver" parent="AndroidManifestApplication"> 1999 <!-- Required name of the class implementing the receiver, deriving from 2000 {@link android.content.BroadcastReceiver}. This is a fully 2001 qualified class name (for example, com.mycompany.myapp.MyReceiver); as a 2002 short-hand if the first character of the class 2003 is a period then it is appended to your package name. --> 2004 <attr name="name" /> 2005 <attr name="label" /> 2006 <attr name="description" /> 2007 <attr name="icon" /> 2008 <attr name="roundIcon" /> 2009 <attr name="banner" /> 2010 <attr name="logo" /> 2011 <attr name="permission" /> 2012 <attr name="process" /> 2013 <!-- Specify whether the receiver is enabled or not (that is, can be instantiated by the system). 2014 It can also be specified for an application as a whole, in which case a value of "false" 2015 will override any component specific values (a value of "true" will not override the 2016 component specific values). --> 2017 <attr name="enabled" /> 2018 <attr name="exported" /> 2019 <attr name="singleUser" /> 2020 <attr name="directBootAware" /> 2021 </declare-styleable> 2022 2023 <!-- The <code>activity</code> tag declares an 2024 {@link android.app.Activity} class that is available 2025 as part of the package's application components, implementing 2026 a part of the application's user interface. 2027 2028 <p>Zero or more {@link #AndroidManifestIntentFilter intent-filter} 2029 tags can be included inside of an activity, to specify the Intents 2030 that it can handle. If none are specified, the activity can 2031 only be started through direct specification of its class name. 2032 The activity tag appears as a child tag of the 2033 {@link #AndroidManifestApplication application} tag. --> 2034 <declare-styleable name="AndroidManifestActivity" parent="AndroidManifestApplication"> 2035 <!-- Required name of the class implementing the activity, deriving from 2036 {@link android.app.Activity}. This is a fully 2037 qualified class name (for example, com.mycompany.myapp.MyActivity); as a 2038 short-hand if the first character of the class 2039 is a period then it is appended to your package name. --> 2040 <attr name="name" /> 2041 <attr name="theme" /> 2042 <attr name="label" /> 2043 <attr name="description" /> 2044 <attr name="icon" /> 2045 <attr name="roundIcon" /> 2046 <attr name="banner" /> 2047 <attr name="logo" /> 2048 <attr name="launchMode" /> 2049 <attr name="screenOrientation" /> 2050 <attr name="configChanges" /> 2051 <attr name="recreateOnConfigChanges" /> 2052 <attr name="permission" /> 2053 <attr name="multiprocess" /> 2054 <attr name="process" /> 2055 <attr name="taskAffinity" /> 2056 <attr name="allowTaskReparenting" /> 2057 <attr name="finishOnTaskLaunch" /> 2058 <attr name="finishOnCloseSystemDialogs" /> 2059 <attr name="clearTaskOnLaunch" /> 2060 <attr name="noHistory" /> 2061 <attr name="alwaysRetainTaskState" /> 2062 <attr name="stateNotNeeded" /> 2063 <attr name="excludeFromRecents" /> 2064 <!-- @deprecated use {@link android.R.attr#showForAllUsers} instead. --> 2065 <attr name="showOnLockScreen" /> 2066 <!-- Specify whether the activity is enabled or not (that is, can be instantiated by the system). 2067 It can also be specified for an application as a whole, in which case a value of "false" 2068 will override any component specific values (a value of "true" will not override the 2069 component specific values). --> 2070 <attr name="enabled" /> 2071 <attr name="exported" /> 2072 <!-- Specify the default soft-input mode for the main window of 2073 this activity. A value besides "unspecified" here overrides 2074 any value in the theme. --> 2075 <attr name="windowSoftInputMode" /> 2076 <attr name="immersive" /> 2077 <attr name="hardwareAccelerated" /> 2078 <attr name="uiOptions" /> 2079 <attr name="parentActivityName" /> 2080 <attr name="singleUser" /> 2081 <!-- @hide This broadcast receiver or activity will only receive broadcasts for the 2082 system user--> 2083 <attr name="systemUserOnly" format="boolean" /> 2084 <attr name="persistableMode" /> 2085 <attr name="allowEmbedded" /> 2086 <attr name="documentLaunchMode" /> 2087 <attr name="maxRecents" /> 2088 <attr name="autoRemoveFromRecents" /> 2089 <attr name="relinquishTaskIdentity" /> 2090 <attr name="resumeWhilePausing" /> 2091 <attr name="resizeableActivity" /> 2092 <attr name="supportsPictureInPicture" /> 2093 <attr name="maxAspectRatio" /> 2094 <attr name="lockTaskMode" /> 2095 <attr name="showForAllUsers" /> 2096 <attr name="directBootAware" /> 2097 <!-- @hide This activity is always focusable regardless of if it is in a task/stack whose 2098 activities are normally not focusable. 2099 For example, {@link android.R.attr#supportsPictureInPicture} activities are placed 2100 in a task/stack that isn't focusable. This flag allows them to be focusable.--> 2101 <attr name="alwaysFocusable" format="boolean" /> 2102 <attr name="enableVrMode" /> 2103 <attr name="rotationAnimation" /> 2104 <attr name="visibleToInstantApps" /> 2105 <!-- The code for this component is located in the given split. --> 2106 <attr name="splitName" /> 2107 <!-- Specify the color mode the activity desires. The requested color mode may be ignored 2108 depending on the capabilities of the display the activity is displayed on. --> 2109 <attr name="colorMode"> 2110 <!-- The default color mode (typically sRGB, low-dynamic range). --> 2111 <enum name="default" value="0" /> 2112 <!-- Wide color gamut color mode. --> 2113 <enum name="wideColorGamut" value="1" /> 2114 <!-- High dynamic range color mode. --> 2115 <enum name="hdr" value="2" /> 2116 </attr> 2117 </declare-styleable> 2118 2119 <!-- The <code>activity-alias</code> tag declares a new 2120 name for an existing {@link #AndroidManifestActivity activity} 2121 tag. 2122 2123 <p>Zero or more {@link #AndroidManifestIntentFilter intent-filter} 2124 tags can be included inside of an activity-alias, to specify the Intents 2125 that it can handle. If none are specified, the activity can 2126 only be started through direct specification of its class name. 2127 The activity-alias tag appears as a child tag of the 2128 {@link #AndroidManifestApplication application} tag. --> 2129 <declare-styleable name="AndroidManifestActivityAlias" parent="AndroidManifestApplication"> 2130 <!-- Required name of the class implementing the activity, deriving from 2131 {@link android.app.Activity}. This is a fully 2132 qualified class name (for example, com.mycompany.myapp.MyActivity); as a 2133 short-hand if the first character of the class 2134 is a period then it is appended to your package name. --> 2135 <attr name="name" /> 2136 <!-- The name of the activity this alias should launch. The activity 2137 must be in the same manifest as the alias, and have been defined 2138 in that manifest before the alias here. This must use a Java-style 2139 naming convention to ensure the name is unique, for example 2140 "com.mycompany.MyName". --> 2141 <attr name="targetActivity" format="string" /> 2142 <attr name="label" /> 2143 <attr name="description" /> 2144 <attr name="icon" /> 2145 <attr name="roundIcon" /> 2146 <attr name="banner" /> 2147 <attr name="logo" /> 2148 <attr name="permission" /> 2149 <!-- Specify whether the activity-alias is enabled or not (that is, can be instantiated by the system). 2150 It can also be specified for an application as a whole, in which case a value of "false" 2151 will override any component specific values (a value of "true" will not override the 2152 component specific values). --> 2153 <attr name="enabled" /> 2154 <attr name="exported" /> 2155 <attr name="parentActivityName" /> 2156 </declare-styleable> 2157 2158 <!-- The <code>meta-data</code> tag is used to attach additional 2159 arbitrary data to an application component. The data can later 2160 be retrieved programmatically from the 2161 {@link android.content.pm.ComponentInfo#metaData 2162 ComponentInfo.metaData} field. There is no meaning given to this 2163 data by the system. You may supply the data through either the 2164 <code>value</code> or <code>resource</code> attribute; if both 2165 are given, then <code>resource</code> will be used. 2166 2167 <p>It is highly recommended that you avoid supplying related data as 2168 multiple separate meta-data entries. Instead, if you have complex 2169 data to associate with a component, then use the <code>resource</code> 2170 attribute to assign an XML resource that the client can parse to 2171 retrieve the complete data. --> 2172 <declare-styleable name="AndroidManifestMetaData" 2173 parent="AndroidManifestApplication 2174 AndroidManifestActivity 2175 AndroidManifestReceiver 2176 AndroidManifestProvider 2177 AndroidManifestService 2178 AndroidManifestPermission 2179 AndroidManifestPermissionGroup 2180 AndroidManifestInstrumentation"> 2181 <attr name="name" /> 2182 <!-- Concrete value to assign to this piece of named meta-data. 2183 The data can later be retrieved from the meta data Bundle 2184 through {@link android.os.Bundle#getString Bundle.getString}, 2185 {@link android.os.Bundle#getInt Bundle.getInt}, 2186 {@link android.os.Bundle#getBoolean Bundle.getBoolean}, 2187 or {@link android.os.Bundle#getFloat Bundle.getFloat} depending 2188 on the type used here. --> 2189 <attr name="value" format="string|integer|color|float|boolean" /> 2190 <!-- Resource identifier to assign to this piece of named meta-data. 2191 The resource identifier can later be retrieved from the meta data 2192 Bundle through {@link android.os.Bundle#getInt Bundle.getInt}. --> 2193 <attr name="resource" format="reference" /> 2194 </declare-styleable> 2195 2196 <!-- The <code>intent-filter</code> tag is used to construct an 2197 {@link android.content.IntentFilter} object that will be used 2198 to determine which component can handle a particular 2199 {@link android.content.Intent} that has been given to the system. 2200 It can be used as a child of the 2201 {@link #AndroidManifestActivity activity}, 2202 {@link #AndroidManifestReceiver receiver} and 2203 {@link #AndroidManifestService service} 2204 tags. 2205 2206 <p> Zero or more {@link #AndroidManifestAction action}, 2207 {@link #AndroidManifestCategory category}, and/or 2208 {@link #AndroidManifestData data} tags should be 2209 included inside to describe the contents of the filter. 2210 2211 <p> The optional label and icon attributes here are used with 2212 an activity to supply an alternative description of that activity 2213 when it is being started through an Intent matching this filter. --> 2214 <declare-styleable name="AndroidManifestIntentFilter" 2215 parent="AndroidManifestActivity AndroidManifestReceiver AndroidManifestService"> 2216 <attr name="label" /> 2217 <attr name="icon" /> 2218 <attr name="roundIcon" /> 2219 <attr name="banner" /> 2220 <attr name="logo" /> 2221 <attr name="priority" /> 2222 <attr name="autoVerify" /> 2223 </declare-styleable> 2224 2225 <!-- Attributes that can be supplied in an AndroidManifest.xml 2226 <code>action</code> tag, a child of the 2227 {@link #AndroidManifestIntentFilter intent-filter} tag. 2228 See {@link android.content.IntentFilter#addAction} for 2229 more information. --> 2230 <declare-styleable name="AndroidManifestAction" parent="AndroidManifestIntentFilter"> 2231 <!-- The name of an action that is handled, using the Java-style 2232 naming convention. For example, to support 2233 {@link android.content.Intent#ACTION_VIEW Intent.ACTION_VIEW} 2234 you would put <code>android.intent.action.VIEW</code> here. 2235 Custom actions should generally use a prefix matching the 2236 package name. --> 2237 <attr name="name" /> 2238 </declare-styleable> 2239 2240 <!-- Attributes that can be supplied in an AndroidManifest.xml 2241 <code>data</code> tag, a child of the 2242 {@link #AndroidManifestIntentFilter intent-filter} tag, describing 2243 the types of data that match. This tag can be specified multiple 2244 times to supply multiple data options, as described in the 2245 {@link android.content.IntentFilter} class. Note that all such 2246 tags are adding options to the same IntentFilter so that, for example, 2247 <code><data android:scheme="myscheme" android:host="me.com" /></code> 2248 is equivalent to <code><data android:scheme="myscheme" /> 2249 <data android:host="me.com" /></code>. --> 2250 <declare-styleable name="AndroidManifestData" parent="AndroidManifestIntentFilter"> 2251 <!-- Specify a MIME type that is handled, as per 2252 {@link android.content.IntentFilter#addDataType 2253 IntentFilter.addDataType()}. 2254 <p><em>Note: MIME type matching in the Android framework is 2255 case-sensitive, unlike formal RFC MIME types. As a result, 2256 MIME types here should always use lower case letters.</em></p> --> 2257 <attr name="mimeType" format="string" /> 2258 <!-- Specify a URI scheme that is handled, as per 2259 {@link android.content.IntentFilter#addDataScheme 2260 IntentFilter.addDataScheme()}. 2261 <p><em>Note: scheme matching in the Android framework is 2262 case-sensitive, unlike the formal RFC. As a result, 2263 schemes here should always use lower case letters.</em></p> --> 2264 <attr name="scheme" format="string" /> 2265 <!-- Specify a URI scheme specific part that must exactly match, as per 2266 {@link android.content.IntentFilter#addDataSchemeSpecificPart 2267 IntentFilter.addDataSchemeSpecificPart()} with 2268 {@link android.os.PatternMatcher#PATTERN_LITERAL}. --> 2269 <attr name="ssp" format="string" /> 2270 <!-- Specify a URI scheme specific part that must be a prefix to match, as per 2271 {@link android.content.IntentFilter#addDataSchemeSpecificPart 2272 IntentFilter.addDataSchemeSpecificPart()} with 2273 {@link android.os.PatternMatcher#PATTERN_PREFIX}. --> 2274 <attr name="sspPrefix" format="string" /> 2275 <!-- Specify a URI scheme specific part that matches a simple pattern, as per 2276 {@link android.content.IntentFilter#addDataSchemeSpecificPart 2277 IntentFilter.addDataSchemeSpecificPart()} with 2278 {@link android.os.PatternMatcher#PATTERN_SIMPLE_GLOB}. 2279 Note that because '\' is used as an escape character when 2280 reading the string from XML (before it is parsed as a pattern), 2281 you will need to double-escape: for example a literal "*" would 2282 be written as "\\*" and a literal "\" would be written as 2283 "\\\\". This is basically the same as what you would need to 2284 write if constructing the string in Java code. --> 2285 <attr name="sspPattern" format="string" /> 2286 <!-- Specify a URI authority host that is handled, as per 2287 {@link android.content.IntentFilter#addDataAuthority 2288 IntentFilter.addDataAuthority()}. 2289 <p><em>Note: host name matching in the Android framework is 2290 case-sensitive, unlike the formal RFC. As a result, 2291 host names here should always use lower case letters.</em></p> --> 2292 <attr name="host" format="string" /> 2293 <!-- Specify a URI authority port that is handled, as per 2294 {@link android.content.IntentFilter#addDataAuthority 2295 IntentFilter.addDataAuthority()}. If a host is supplied 2296 but not a port, any port is matched. --> 2297 <attr name="port" format="string" /> 2298 <!-- Specify a URI path that must exactly match, as per 2299 {@link android.content.IntentFilter#addDataPath 2300 IntentFilter.addDataPath()} with 2301 {@link android.os.PatternMatcher#PATTERN_LITERAL}. --> 2302 <attr name="path" /> 2303 <!-- Specify a URI path that must be a prefix to match, as per 2304 {@link android.content.IntentFilter#addDataPath 2305 IntentFilter.addDataPath()} with 2306 {@link android.os.PatternMatcher#PATTERN_PREFIX}. --> 2307 <attr name="pathPrefix" /> 2308 <!-- Specify a URI path that matches a simple pattern, as per 2309 {@link android.content.IntentFilter#addDataPath 2310 IntentFilter.addDataPath()} with 2311 {@link android.os.PatternMatcher#PATTERN_SIMPLE_GLOB}. 2312 Note that because '\' is used as an escape character when 2313 reading the string from XML (before it is parsed as a pattern), 2314 you will need to double-escape: for example a literal "*" would 2315 be written as "\\*" and a literal "\" would be written as 2316 "\\\\". This is basically the same as what you would need to 2317 write if constructing the string in Java code. --> 2318 <attr name="pathPattern" /> 2319 <!-- Specify a URI path that matches an advanced pattern, as per 2320 {@link android.content.IntentFilter#addDataPath 2321 IntentFilter.addDataPath()} with 2322 {@link android.os.PatternMatcher#PATTERN_ADVANCED_GLOB}. 2323 Note that because '\' is used as an escape character when 2324 reading the string from XML (before it is parsed as a pattern), 2325 you will need to double-escape: for example a literal "*" would 2326 be written as "\\*" and a literal "\" would be written as 2327 "\\\\". This is basically the same as what you would need to 2328 write if constructing the string in Java code. --> 2329 <attr name="pathAdvancedPattern" /> 2330 </declare-styleable> 2331 2332 <!-- Attributes that can be supplied in an AndroidManifest.xml 2333 <code>category</code> tag, a child of the 2334 {@link #AndroidManifestIntentFilter intent-filter} tag. 2335 See {@link android.content.IntentFilter#addCategory} for 2336 more information. --> 2337 <declare-styleable name="AndroidManifestCategory" parent="AndroidManifestIntentFilter"> 2338 <!-- The name of category that is handled, using the Java-style 2339 naming convention. For example, to support 2340 {@link android.content.Intent#CATEGORY_LAUNCHER Intent.CATEGORY_LAUNCHER} 2341 you would put <code>android.intent.category.LAUNCHER</code> here. 2342 Custom actions should generally use a prefix matching the 2343 package name. --> 2344 <attr name="name" /> 2345 </declare-styleable> 2346 2347 <!-- Attributes that can be supplied in an AndroidManifest.xml 2348 <code>instrumentation</code> tag, a child of the root 2349 {@link #AndroidManifest manifest} tag. --> 2350 <declare-styleable name="AndroidManifestInstrumentation" parent="AndroidManifest"> 2351 <!-- Required name of the class implementing the instrumentation, deriving from 2352 {@link android.app.Instrumentation}. This is a fully 2353 qualified class name (for example, com.mycompany.myapp.MyActivity); as a 2354 short-hand if the first character of the class 2355 is a period then it is appended to your package name. --> 2356 <attr name="name" /> 2357 <attr name="targetPackage" /> 2358 <attr name="targetProcesses" /> 2359 <attr name="label" /> 2360 <attr name="icon" /> 2361 <attr name="roundIcon" /> 2362 <attr name="banner" /> 2363 <attr name="logo" /> 2364 <attr name="handleProfiling" /> 2365 <attr name="functionalTest" /> 2366 </declare-styleable> 2367 2368 <!-- Attributes that can be supplied in an AndroidManifest.xml 2369 <code>screen</code> tag, a child of <code>compatible-screens</code>, 2370 which is itself a child of the root 2371 {@link #AndroidManifest manifest} tag. --> 2372 <declare-styleable name="AndroidManifestCompatibleScreensScreen" 2373 parent="AndroidManifest.AndroidManifestCompatibleScreens"> 2374 <!-- Specifies a compatible screen size, as per the device 2375 configuration screen size bins. --> 2376 <attr name="screenSize"> 2377 <!-- A small screen configuration, at least 240x320dp. --> 2378 <enum name="small" value="200" /> 2379 <!-- A normal screen configuration, at least 320x480dp. --> 2380 <enum name="normal" value="300" /> 2381 <!-- A large screen configuration, at least 400x530dp. --> 2382 <enum name="large" value="400" /> 2383 <!-- An extra large screen configuration, at least 600x800dp. --> 2384 <enum name="xlarge" value="500" /> 2385 </attr> 2386 <!-- Specifies a compatible screen density, as per the device 2387 configuration screen density bins. --> 2388 <attr name="screenDensity" format="integer"> 2389 <!-- A low density screen, approximately 120dpi. --> 2390 <enum name="ldpi" value="120" /> 2391 <!-- A medium density screen, approximately 160dpi. --> 2392 <enum name="mdpi" value="160" /> 2393 <!-- A high density screen, approximately 240dpi. --> 2394 <enum name="hdpi" value="240" /> 2395 <!-- An extra high density screen, approximately 320dpi. --> 2396 <enum name="xhdpi" value="320" /> 2397 <!-- An extra extra high density screen, approximately 480dpi. --> 2398 <enum name="xxhdpi" value="480" /> 2399 <!-- An extra extra extra high density screen, approximately 640dpi. --> 2400 <enum name="xxxhdpi" value="640" /> 2401 </attr> 2402 </declare-styleable> 2403 2404 <!-- The <code>input-type</code> tag is a child of the <code>supports-input</code> tag, which 2405 is itself a child of the root {@link #AndroidManifest manifest} tag. Each 2406 <code>input-type</code> tag specifices the name of a specific input device type. When 2407 grouped with the other elements of the parent <code>supports-input</code> tag it defines 2408 a collection of input devices, which when all used together, are considered a supported 2409 input mechanism for the application. There may be multiple <code>supports-input</code> 2410 tags defined, each containing a different combination of input device types. --> 2411 <declare-styleable name="AndroidManifestSupportsInputInputType" 2412 parent="AndroidManifest.AndroidManifestSupportsInput"> 2413 <!-- Specifices the name of the input device type --> 2414 <attr name="name" /> 2415 </declare-styleable> 2416 2417 <!-- The attribute that holds a Base64-encoded public key. --> 2418 <attr name="publicKey" format="string" /> 2419 2420 <!-- Attributes relating to a package verifier. --> 2421 <declare-styleable name="AndroidManifestPackageVerifier" parent="AndroidManifest"> 2422 <!-- Specifies the Java-style package name that defines this 2423 package verifier. --> 2424 <attr name="name" /> 2425 2426 <!-- The Base64 encoded public key of the package verifier's 2427 signature. --> 2428 <attr name="publicKey" /> 2429 </declare-styleable> 2430 2431 <!-- Attributes relating to resource overlay packages. --> 2432 <declare-styleable name="AndroidManifestResourceOverlay" parent="AndroidManifest"> 2433 <!-- Package name of base package whose resources will be overlaid. --> 2434 <attr name="targetPackage" /> 2435 2436 <!-- Load order of overlay package. --> 2437 <attr name="priority" /> 2438 2439 <!-- Whether the given RRO is static or not. --> 2440 <attr name="isStatic" format="boolean" /> 2441 2442 <!-- Required property name/value pair used to enable this overlay. 2443 e.g. name=ro.oem.sku value=MKT210. 2444 Overlay will be ignored unless system property exists and is 2445 set to specified value --> 2446 <!-- @hide @SystemApi This shouldn't be public. --> 2447 <attr name="requiredSystemPropertyName" format="string" /> 2448 <!-- @hide @SystemApi This shouldn't be public. --> 2449 <attr name="requiredSystemPropertyValue" format="string" /> 2450 </declare-styleable> 2451 2452 <!-- Declaration of an {@link android.content.Intent} object in XML. May 2453 also include zero or more {@link #IntentCategory <category>} and 2454 {@link #Extra <extra>} tags. --> 2455 <declare-styleable name="Intent"> 2456 <!-- The action name to assign to the Intent, as per 2457 {@link android.content.Intent#setAction Intent.setAction()}. --> 2458 <attr name="action" format="string" /> 2459 <!-- The data URI to assign to the Intent, as per 2460 {@link android.content.Intent#setData Intent.setData()}. 2461 <p><em>Note: scheme and host name matching in the Android framework is 2462 case-sensitive, unlike the formal RFC. As a result, 2463 URIs here should always be normalized to use lower case letters 2464 for these elements (as well as other proper Uri normalization).</em></p> --> 2465 <attr name="data" format="string" /> 2466 <!-- The MIME type name to assign to the Intent, as per 2467 {@link android.content.Intent#setType Intent.setType()}. 2468 <p><em>Note: MIME type matching in the Android framework is 2469 case-sensitive, unlike formal RFC MIME types. As a result, 2470 MIME types here should always use lower case letters.</em></p> --> 2471 <attr name="mimeType" /> 2472 <!-- The package part of the ComponentName to assign to the Intent, as per 2473 {@link android.content.Intent#setComponent Intent.setComponent()}. --> 2474 <attr name="targetPackage" /> 2475 <!-- The class part of the ComponentName to assign to the Intent, as per 2476 {@link android.content.Intent#setComponent Intent.setComponent()}. --> 2477 <attr name="targetClass" format="string" /> 2478 </declare-styleable> 2479 2480 <!-- A category to add to an Intent, as per 2481 {@link android.content.Intent#addCategory Intent.addCategory()}. --> 2482 <declare-styleable name="IntentCategory" parent="Intent"> 2483 <!-- Required name of the category. --> 2484 <attr name="name" /> 2485 </declare-styleable> 2486 2487 <!-- An extra data value to place into a an extra/name value pair held 2488 in a Bundle, as per {@link android.os.Bundle}. --> 2489 <declare-styleable name="Extra" parent="Intent"> 2490 <!-- Required name of the extra data. --> 2491 <attr name="name" /> 2492 <!-- Concrete value to put for this named extra data. --> 2493 <attr name="value" /> 2494 </declare-styleable> 2495 2496 <!-- Groups signing keys into a {@code KeySet} for easier reference in 2497 other APIs. However, currently no APIs use this. --> 2498 <attr name="keySet" /> 2499 <declare-styleable name="AndroidManifestPublicKey"> 2500 <attr name="name" /> 2501 <attr name="value" /> 2502 </declare-styleable> 2503 <declare-styleable name="AndroidManifestKeySet"> 2504 <attr name="name" /> 2505 </declare-styleable> 2506 2507 <!-- Associate declared KeySets with upgrading capability. --> 2508 <declare-styleable name="AndroidManifestUpgradeKeySet" parent="AndroidManifest"> 2509 <attr name="name" /> 2510 </declare-styleable> 2511 2512 <!-- <code>layout</code> tag allows configuring the layout for the activity within multi-window 2513 environment. --> 2514 <declare-styleable name="AndroidManifestLayout" parent="AndroidManifestActivity"> 2515 <!-- Default width of the activity. Can be either a fixed value or fraction, in which case 2516 the width will be constructed as a fraction of the total available width. --> 2517 <attr name="defaultWidth" format="dimension|fraction" /> 2518 <!-- Default height of the activity. Can be either a fixed value or fraction, in which case 2519 the height will be constructed as a fraction of the total available height. --> 2520 <attr name="defaultHeight" format="dimension|fraction" /> 2521 <!-- Where to initially position the activity inside the available space. Uses constants 2522 defined in {@link android.view.Gravity}. --> 2523 <attr name="gravity" /> 2524 <!-- Minimal width of the activity. 2525 2526 <p><strong>NOTE:</strong> A task's root activity value is applied to all additional 2527 activities launched in the task. That is if the root activity of a task set minimal width, 2528 then the system will set the same minimal width on all other activities in the task. It 2529 will also ignore any other minimal width attributes of non-root activities. --> 2530 <attr name="minWidth" /> 2531 <!-- Minimal height of the activity. 2532 2533 <p><strong>NOTE:</strong> A task's root activity value is applied to all additional 2534 activities launched in the task. That is if the root activity of a task set minimal height, 2535 then the system will set the same minimal height on all other activities in the task. It 2536 will also ignore any other minimal height attributes of non-root activities. --> 2537 <attr name="minHeight" /> 2538 </declare-styleable> 2539 2540 <!-- <code>restrict-update</code> tag restricts system apps from being updated unless the 2541 SHA-512 hash equals the specified value. 2542 @hide --> 2543 <declare-styleable name="AndroidManifestRestrictUpdate" parent="AndroidManifest"> 2544 <!-- The SHA-512 hash of the only APK that can be used to update a package. 2545 <p>NOTE: This is only applicable to system packages. 2546 @hide --> 2547 <attr name="hash" format="string" /> 2548 </declare-styleable> 2549 2550 <declare-styleable name="AndroidManifestUsesSplit" parent="AndroidManifest"> 2551 <attr name="name" format="string" /> 2552 </declare-styleable> 2553 2554</resources> 2555