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 <p>Starting from API level 29 this flag only controls if the user can 123 clear app data from Settings. To control clearing the data after a 124 failed restore use allowClearUserDataOnFailedRestore flag. 125 <p><em>This attribute is usable only by applications 126 included in the system image. Third-party apps cannot use it.</em> --> 127 <attr name="allowClearUserData" format="boolean" /> 128 129 <!-- Option to indicate this application is only for testing purposes. 130 For example, it may expose functionality or data outside of itself 131 that would cause a security hole, but is useful for testing. This 132 kind of application can not be installed without the 133 INSTALL_ALLOW_TEST flag, which means only through adb install. --> 134 <attr name="testOnly" format="boolean" /> 135 136 <!-- A unique name for the given item. This must use a Java-style naming 137 convention to ensure the name is unique, for example 138 "com.mycompany.MyName". --> 139 <attr name="name" format="string" /> 140 141 <!-- Specify a permission that a client is required to have in order to 142 use the associated object. If the client does not hold the named 143 permission, its request will fail. See the 144 <a href="{@docRoot}guide/topics/security/security.html">Security and Permissions</a> 145 document for more information on permissions. --> 146 <attr name="permission" format="string" /> 147 148 <!-- A specific {@link android.R.attr#permission} name for read-only 149 access to a {@link android.content.ContentProvider}. See the 150 <a href="{@docRoot}guide/topics/security/security.html">Security and Permissions</a> 151 document for more information on permissions. --> 152 <attr name="readPermission" format="string" /> 153 154 <!-- A specific {@link android.R.attr#permission} name for write 155 access to a {@link android.content.ContentProvider}. See the 156 <a href="{@docRoot}guide/topics/security/security.html">Security and Permissions</a> 157 document for more information on permissions. --> 158 <attr name="writePermission" format="string" /> 159 160 <!-- If true, the {@link android.content.Context#grantUriPermission 161 Context.grantUriPermission} or corresponding Intent flags can 162 be used to allow others to access specific URIs in the content 163 provider, even if they do not have an explicit read or write 164 permission. If you are supporting this feature, you must be 165 sure to call {@link android.content.Context#revokeUriPermission 166 Context.revokeUriPermission} when URIs are deleted from your 167 provider.--> 168 <attr name="grantUriPermissions" format="boolean" /> 169 170 <!-- If true, the system will always create URI permission grants 171 in the cases where {@link android.content.Intent#FLAG_GRANT_READ_URI_PERMISSION} 172 or {@link android.content.Intent#FLAG_GRANT_WRITE_URI_PERMISSION} would apply. 173 This is useful for a content provider that dynamically enforces permissions 174 on calls in to the provider, instead of through the manifest: the system 175 needs to know that it should always apply permission grants, even if it 176 looks like the target of the grant would already have access to the URI. --> 177 <attr name="forceUriPermissions" format="boolean" /> 178 179 <!-- Characterizes the potential risk implied in a permission and 180 indicates the procedure the system should follow when determining 181 whether to grant the permission to an application requesting it. {@link 182 android.Manifest.permission Standard permissions} have a predefined and 183 permanent protectionLevel. If you are creating a custom permission in an 184 application, you can define a protectionLevel attribute with one of the 185 values listed below. If no protectionLevel is defined for a custom 186 permission, the system assigns the default ("normal"). 187 <p>Each protection level consists of a base permission type and zero or 188 more flags. Use the following functions to extract those. 189 <pre> 190 int basePermissionType = permissionInfo.getProtection(); 191 int permissionFlags = permissionInfo.getProtectionFlags(); 192 </pre> 193 --> 194 <attr name="protectionLevel"> 195 <!-- <strong>Base permission type</strong>: a lower-risk permission that gives 196 an application access to isolated application-level features, with minimal 197 risk to other applications, the system, or the user. The system 198 automatically grants this type of permission to a requesting application at 199 installation, without asking for the user's explicit approval (though the 200 user always has the option to review these permissions before installing). --> 201 <flag name="normal" value="0" /> 202 <!-- <strong>Base permission type</strong>: a higher-risk permission that 203 would give a requesting application access to private user data or 204 control over the device that can negatively impact the user. Because 205 this type of permission introduces potential risk, the system may 206 not automatically grant it to the requesting application. For example, 207 any dangerous permissions requested by an application may be displayed 208 to the user and require confirmation before proceeding, or some other 209 approach may be taken to avoid the user automatically allowing 210 the use of such facilities. --> 211 <flag name="dangerous" value="1" /> 212 <!-- <strong>Base permission type</strong>: a permission that the system is 213 to grant only if the requesting application is signed with the same 214 certificate as the application that declared the permission. If the 215 certificates match, the system automatically grants the permission 216 without notifying the user or asking for the user's explicit approval. --> 217 <flag name="signature" value="2" /> 218 <!-- Old synonym for "signature|privileged". Deprecated in API level 23. 219 Base permission type: a permission that the system is to grant only 220 to packages in the Android system image <em>or</em> that are signed 221 with the same certificates. Please avoid using this option, as the 222 signature protection level should be sufficient for most needs and 223 works regardless of exactly where applications are installed. This 224 permission is used for certain special situations where multiple 225 vendors have applications built in to a system image which need 226 to share specific features explicitly because they are being built 227 together. --> 228 <flag name="signatureOrSystem" value="3" /> 229 <!-- <strong>Base permission type</strong>: a permission that is managed internally by the 230 system and only granted according to the protection flags. --> 231 <flag name="internal" value="4" /> 232 <!-- Additional flag from base permission type: this permission can also 233 be granted to any applications installed as privileged apps on the system image. 234 Please avoid using this option, as the 235 signature protection level should be sufficient for most needs and 236 works regardless of exactly where applications are installed. This 237 permission flag is used for certain special situations where multiple 238 vendors have applications built in to a system image which need 239 to share specific features explicitly because they are being built 240 together. --> 241 <flag name="privileged" value="0x10" /> 242 <!-- Old synonym for "privileged". Deprecated in API level 23. --> 243 <flag name="system" value="0x10" /> 244 <!-- Additional flag from base permission type: this permission can also 245 (optionally) be granted to development applications. Although undocumented, the 246 permission state used to be shared by all users (including future users), but it is 247 managed per-user since API level 31. --> 248 <flag name="development" value="0x20" /> 249 <!-- Additional flag from base permission type: this permission is closely 250 associated with an app op for controlling access. --> 251 <flag name="appop" value="0x40" /> 252 <!-- Additional flag from base permission type: this permission can be automatically 253 granted to apps that target API levels below 254 {@link android.os.Build.VERSION_CODES#M} (before runtime permissions 255 were introduced). --> 256 <flag name="pre23" value="0x80" /> 257 <!-- Additional flag from base permission type: this permission can be automatically 258 granted to system apps that install packages. --> 259 <flag name="installer" value="0x100" /> 260 <!-- Additional flag from base permission type: this permission can be automatically 261 granted to system apps that verify packages. --> 262 <flag name="verifier" value="0x200" /> 263 <!-- Additional flag from base permission type: this permission can be automatically 264 granted any application pre-installed on the system image (not just privileged 265 apps). --> 266 <flag name="preinstalled" value="0x400" /> 267 <!-- Additional flag from base permission type: this permission can be automatically 268 granted to the setup wizard app --> 269 <flag name="setup" value="0x800" /> 270 <!-- Additional flag from base permission type: this permission can be granted to instant 271 apps --> 272 <flag name="instant" value="0x1000" /> 273 <!-- Additional flag from base permission type: this permission can only be granted to apps 274 that target runtime permissions ({@link android.os.Build.VERSION_CODES#M} and above) 275 --> 276 <flag name="runtime" value="0x2000" /> 277 <!-- Additional flag from base permission type: this permission can be granted only 278 if its protection level is signature, the requesting app resides on the OEM partition, 279 and the OEM has allowlisted the app to receive this permission by the OEM. 280 --> 281 <flag name="oem" value="0x4000" /> 282 <!-- Additional flag from base permission type: this permission can be granted to 283 privileged apps in vendor partition. --> 284 <flag name="vendorPrivileged" value="0x8000" /> 285 <!-- Additional flag from base permission type: this permission can be automatically 286 granted to the system default text classifier --> 287 <flag name="textClassifier" value="0x10000" /> 288 <!-- Additional flag from base permission type: this permission automatically 289 granted to device configurator --> 290 <flag name="configurator" value="0x80000" /> 291 <!-- Additional flag from base permission type: this permission designates the app 292 that will approve the sharing of incident reports. --> 293 <flag name="incidentReportApprover" value="0x100000" /> 294 <!-- Additional flag from base permission type: this permission can be automatically 295 granted to the system app predictor --> 296 <flag name="appPredictor" value="0x200000" /> 297 <!-- Additional flag from base permission type: this permission can also be granted if the 298 requesting application is included in the mainline module}. --> 299 <flag name="module" value="0x400000" /> 300 <!-- Additional flag from base permission type: this permission can be automatically 301 granted to the system companion device manager service --> 302 <flag name="companion" value="0x800000" /> 303 <!-- Additional flag from base permission type: this permission will be granted to the 304 retail demo app, as defined by the OEM. 305 This flag has been replaced by the retail demo role and is a no-op since Android V. 306 --> 307 <flag name="retailDemo" value="0x1000000" /> 308 <!-- Additional flag from base permission type: this permission will be granted to the 309 recents app. --> 310 <flag name="recents" value="0x2000000" /> 311 <!-- Additional flag from base permission type: this permission is managed by role. --> 312 <flag name="role" value="0x4000000" /> 313 <!-- Additional flag from base permission type: this permission can also be granted if the 314 requesting application is signed by, or has in its signing lineage, any of the 315 certificate digests declared in {@link android.R.attr#knownCerts}. --> 316 <flag name="knownSigner" value="0x8000000" /> 317 </attr> 318 319 <!-- Flags indicating more context for a permission group. --> 320 <attr name="permissionGroupFlags"> 321 <!-- Set to indicate that this permission group contains permissions 322 protecting access to some information that is considered 323 personal to the user (such as contacts, e-mails, etc). --> 324 <flag name="personalInfo" value="0x0001" /> 325 </attr> 326 327 <!-- Flags indicating more context for a permission. --> 328 <attr name="permissionFlags"> 329 <!-- Set to indicate that this permission allows an operation that 330 may cost the user money. Such permissions may be highlighted 331 when shown to the user with this additional information. --> 332 <flag name="costsMoney" value="0x1" /> 333 <!-- Additional flag from base permission type: this permission has been 334 removed and it is no longer enforced. It shouldn't be shown in the 335 UI. Removed permissions are kept as normal permissions for backwards 336 compatibility as apps may be checking them before calling an API. 337 --> 338 <flag name="removed" value="0x2" /> 339 <!-- This permission is restricted by the platform and it would be 340 grantable only to apps that meet special criteria per platform 341 policy. 342 --> 343 <flag name="hardRestricted" value="0x4" /> 344 <!-- This permission is restricted by the platform and it would be 345 grantable in its full form to apps that meet special criteria 346 per platform policy. Otherwise, a weaker form of the permission 347 would be granted. The weak grant depends on the permission. 348 <p>What weak grant means is described in the documentation of 349 the permissions. 350 --> 351 <flag name="softRestricted" value="0x8" /> 352 <!-- This permission is restricted immutably which means that its 353 restriction state may be specified only on the first install of 354 the app and will stay in this initial allowlist state until 355 the app is uninstalled. 356 --> 357 <flag name="immutablyRestricted" value="0x10" /> 358 <!-- 359 Modifier for permission restriction. This permission cannot 360 be exempted by the installer. 361 --> 362 <flag name="installerExemptIgnored" value="0x20" /> 363 </attr> 364 365 <!-- Specified the name of a group that this permission is associated 366 with. The group must have been defined with the 367 {@link android.R.styleable#AndroidManifestPermissionGroup permission-group} tag. --> 368 <attr name="permissionGroup" format="string" /> 369 370 <!-- A reference to an array resource containing the signing certificate digests to be granted 371 this permission when using the {@code knownSigner} protection flag. The digest should 372 be computed over the DER encoding of the trusted certificate using the SHA-256 digest 373 algorithm. 374 <p> 375 If only a single signer is declared this can also be a string resource, or the digest 376 can be declared inline as the value for this attribute. --> 377 <attr name="knownCerts" format="reference|string" /> 378 379 <!-- Specify the name of a user ID that will be shared between multiple 380 packages. By default, each package gets its own unique user-id. 381 By setting this value on two or more packages, each of these packages 382 will be given a single shared user ID, so they can for example run 383 in the same process. Note that for them to actually get the same 384 user ID, they must also be signed with the same signature. 385 @deprecated Shared user IDs cause non-deterministic behavior within the 386 package manager. As such, its use is strongly discouraged and may be 387 removed in a future version of Android. Instead, apps should use proper 388 communication mechanisms, such as services and content providers, 389 to facilitate interoperability between shared components. Note that 390 existing apps cannot remove this value, as migrating off a 391 shared user ID is not supported. --> 392 <attr name="sharedUserId" format="string" /> 393 394 <!-- Specify a label for the shared user UID of this package. This is 395 only used if you have also used android:sharedUserId. This must 396 be a reference to a string resource; it can not be an explicit 397 string. 398 @deprecated There is no replacement for this attribute. 399 {@link android.R.attr#sharedUserId} has been deprecated making 400 this attribute unnecessary. --> 401 <attr name="sharedUserLabel" format="reference" /> 402 403 <!-- The maximum device SDK version for which the application will remain in the user ID 404 defined in sharedUserId. Used when the application wants to migrate out of using shared 405 user ID, but has to maintain backwards compatibility with the API level specified 406 and before. --> 407 <attr name="sharedUserMaxSdkVersion" format="integer" /> 408 409 <!-- Internal version code. This is the number used to determine whether 410 one version is more recent than another: it has no other meaning than 411 that higher numbers are more recent. You could use this number to 412 encode a "x.y" in the lower and upper 16 bits, make it a build 413 number, simply increase it by one each time a new version is 414 released, or define it however else you want, as long as each 415 successive version has a higher number. This is not a version 416 number generally shown to the user, that is usually supplied 417 with {@link android.R.attr#versionName}. When an app is delivered 418 as multiple split APKs, each APK must have the exact same versionCode. --> 419 <attr name="versionCode" format="integer" /> 420 421 <!-- Internal major version code. This is essentially additional high bits 422 for the base version code; it has no other meaning than 423 that higher numbers are more recent. This is not a version 424 number generally shown to the user, that is usually supplied 425 with {@link android.R.attr#versionName}. --> 426 <attr name="versionCodeMajor" format="integer" /> 427 428 <!-- Internal revision code. This number is the number used to determine 429 whether one APK is more recent than another: it has no other meaning 430 than that higher numbers are more recent. This value is only meaningful 431 when the two {@link android.R.attr#versionCode} values are already 432 identical. When an app is delivered as multiple split APKs, each 433 APK may have a different revisionCode value. --> 434 <attr name="revisionCode" format="integer" /> 435 436 <!-- The text shown to the user to indicate the version they have. This 437 is used for no other purpose than display to the user; the actual 438 significant version number is given by {@link android.R.attr#versionCode}. --> 439 <attr name="versionName" format="string" /> 440 441 <!-- Flag to control special persistent mode of an application. This should 442 not normally be used by applications; it requires that the system keep 443 your application running at all times. --> 444 <attr name="persistent" format="boolean" /> 445 446 <!-- If set, the "persistent" attribute will only be honored if the feature 447 specified here is present on the device. --> 448 <attr name="persistentWhenFeatureAvailable" format="string" /> 449 450 <!-- Flag to specify if this application needs to be present for all users. Only pre-installed 451 applications can request this feature. Default value is false. --> 452 <attr name="requiredForAllUsers" format="boolean" /> 453 454 <!-- Flag indicating whether the application can be debugged, even when 455 running on a device that is running in user mode. --> 456 <attr name="debuggable" format="boolean" /> 457 458 <!-- Flag indicating whether the application requests the VM to operate in 459 the safe mode. --> 460 <attr name="vmSafeMode" format="boolean" /> 461 462 <!-- <p>Flag indicating whether the application's rendering should be hardware 463 accelerated if possible. This flag is turned on by default for applications 464 that are targeting {@link android.os.Build.VERSION_CODES#ICE_CREAM_SANDWICH} 465 or later.</p> 466 <p>This flag can be set on the application and any activity declared 467 in the manifest. When enabled for the application, each activity is 468 automatically assumed to be hardware accelerated. This flag can be 469 overridden in the activity tags, either turning it off (if on for the 470 application) or on (if off for the application.)</p> 471 <p>When this flag is turned on for an activity (either directly or via 472 the application tag), every window created from the activity, including 473 the activity's own window, will be hardware accelerated, if possible.</p> 474 <p>Please refer to the documentation of 475 {@link android.view.WindowManager.LayoutParams#FLAG_HARDWARE_ACCELERATED} 476 for more information on how to control this flag programmatically.</p> --> 477 <attr name="hardwareAccelerated" format="boolean" /> 478 479 <!-- Flag indicating whether the given application component is available 480 to other applications. If false, it can only be accessed by 481 applications with its same user id (which usually means only by 482 code in its own package). If true, it can be invoked by external 483 entities, though which ones can do so may be controlled through 484 permissions. The default value is false for activity, receiver, 485 and service components that do not specify any intent filters; it 486 is true for activity, receiver, and service components that do 487 have intent filters (implying they expect to be invoked by others 488 who do not know their particular component name) and for all 489 content providers. --> 490 <attr name="exported" format="boolean" /> 491 492 <!-- A boolean flag used to indicate if an application is a Game or not. 493 <p>This information can be used by the system to group together 494 applications that are classified as games, and display them separately 495 from the other applications. --> 496 <attr name="isGame" format="boolean" /> 497 498 <!-- If set to true, a single instance of this component will run for 499 all users. That instance will run as user 0, the default/primary 500 user. When the app running is in processes for other users and interacts 501 with this component (by binding to a service for example) those processes will 502 always interact with the instance running for user 0. Enabling 503 single user mode forces "exported" of the component to be false, to 504 help avoid introducing multi-user security bugs. This feature is only 505 available to applications built in to the system image; you must hold the 506 permission INTERACT_ACROSS_USERS in order 507 to use this feature. This flag can only be used with services, 508 receivers, and providers; it can not be used with activities. --> 509 <attr name="singleUser" format="boolean" /> 510 511 <!-- If set to true, only a single instance of this component will 512 run and be available for the SYSTEM user. Non SYSTEM users will not be 513 allowed to access the component if this flag is enabled. 514 This flag can be used with services, receivers, providers and activities. --> 515 <attr name="systemUserOnly" format="boolean" /> 516 517 <!-- Specify a specific process that the associated code is to run in. 518 Use with the application tag (to supply a default process for all 519 application components), or with the activity, receiver, service, 520 or provider tag (to supply a specific icon for that component). 521 522 <p>Application components are normally run in a single process that 523 is created for the entire application. You can use this tag to modify 524 where they run. If the process name begins with a ':' character, 525 a new process private to that application will be created when needed 526 to run that component (allowing you to spread your application across 527 multiple processes). If the process name begins with a lower-case 528 character, the component will be run in a global process of that name, 529 provided that you have permission to do so, allowing multiple 530 applications to share one process to reduce resource usage. --> 531 <attr name="process" format="string" /> 532 533 <!-- Specify a task name that activities have an "affinity" to. 534 Use with the application tag (to supply a default affinity for all 535 activities in the application), or with the activity tag (to supply 536 a specific affinity for that component). 537 538 <p>The default value for this attribute is the same as the package 539 name, indicating that all activities in the manifest should generally 540 be considered a single "application" to the user. You can use this 541 attribute to modify that behavior: either giving them an affinity 542 for another task, if the activities are intended to be part of that 543 task from the user's perspective, or using an empty string for 544 activities that have no affinity to a task. --> 545 <attr name="taskAffinity" format="string" /> 546 547 <!-- Specify that an activity can be moved out of a task it is in to 548 the task it has an affinity for when appropriate. Use with the 549 application tag (to supply a default for all activities in the 550 application), or with an activity tag (to supply a specific 551 setting for that component). 552 553 <p>Normally when an application is started, it is associated with 554 the task of the activity that started it and stays there for its 555 entire lifetime. You can use the allowTaskReparenting feature to force an 556 activity to be re-parented to a different task when the task it is 557 in goes to the background. Typically this is used to cause the 558 activities of an application to move back to the main task associated 559 with that application. The activity is re-parented to the task 560 with the same {@link android.R.attr#taskAffinity} as it has. --> 561 <attr name="allowTaskReparenting" format="boolean" /> 562 563 <!-- Declare that this application may use cleartext traffic, such as HTTP rather than HTTPS; 564 WebSockets rather than WebSockets Secure; XMPP, IMAP, SMTP without STARTTLS or TLS. 565 Defaults to true. If set to false {@code false}, the application declares that it does not 566 intend to use cleartext network traffic, in which case platform components (e.g. HTTP 567 stacks, {@code DownloadManager}, {@code MediaPlayer}) will refuse applications's requests 568 to use cleartext traffic. Third-party libraries are encouraged to honor this flag as well. 569 --> 570 <attr name="usesCleartextTraffic" format="boolean" /> 571 572 <!-- Declare that code from this application will need to be loaded into other 573 applications' processes. On devices that support multiple instruction sets, 574 this implies the code might be loaded into a process that's using any of the devices 575 supported instruction sets. 576 577 <p> The system might treat such applications specially, for eg., by 578 extracting the application's native libraries for all supported instruction 579 sets or by compiling the application's dex code for all supported instruction 580 sets. --> 581 <attr name="multiArch" format ="boolean" /> 582 583 <!-- Specify whether the 32 bit version of the ABI should be used in a 584 multiArch application. If both abioverride flag (i.e. using abi option of abd install) 585 and use32bitAbi are used, then use32bit is ignored.--> 586 <attr name="use32bitAbi" /> 587 588 <!-- Specify whether a component is allowed to have multiple instances 589 of itself running in different processes. Use with the activity 590 and provider tags. 591 592 <p>Normally the system will ensure that all instances of a particular 593 component are only running in a single process. You can use this 594 attribute to disable that behavior, allowing the system to create 595 instances wherever they are used (provided permissions allow it). 596 This is most often used with content providers, so that instances 597 of a provider can be created in each client process, allowing them 598 to be used without performing IPC. --> 599 <attr name="multiprocess" format="boolean" /> 600 601 <!-- Specify whether an activity should be finished when its task is 602 brought to the foreground by relaunching from the home screen. 603 604 <p>If both this option and {@link android.R.attr#allowTaskReparenting} are 605 specified, the finish trumps the affinity: the affinity will be 606 ignored and the activity simply finished. --> 607 <attr name="finishOnTaskLaunch" format="boolean" /> 608 609 <!-- Specify whether an activity should be finished when a "close system 610 windows" request has been made. This happens, for example, when 611 the home key is pressed, when the device is locked, when a system 612 dialog showing recent applications is displayed, etc. --> 613 <attr name="finishOnCloseSystemDialogs" format="boolean" /> 614 615 <!-- Specify whether an activity's task should be cleared when it 616 is re-launched from the home screen. As a result, every time the 617 user starts the task, they will be brought to its root activity, 618 regardless of whether they used BACK or HOME to last leave it. 619 This flag only applies to activities that 620 are used to start the root of a new task. 621 622 <p>An example of the use of this flag would be for the case where 623 a user launches activity A from home, and from there goes to 624 activity B. They now press home, and then return to activity A. 625 Normally they would see activity B, since that is what they were 626 last doing in A's task. However, if A has set this flag to true, 627 then upon going to the background all of the tasks on top of it (B 628 in this case) are removed, so when the user next returns to A they 629 will restart at its original activity. 630 631 <p>When this option is used in conjunction with 632 {@link android.R.attr#allowTaskReparenting}, the allowTaskReparenting trumps the 633 clear. That is, all activities above the root activity of the 634 task will be removed: those that have an affinity will be moved 635 to the task they are associated with, otherwise they will simply 636 be dropped as described here. --> 637 <attr name="clearTaskOnLaunch" format="boolean" /> 638 639 <!-- Specify whether an activity should be kept in its history stack. 640 If this attribute is set, then as soon as the user navigates away 641 from the activity it will be finished and they will no longer be 642 able to return to it. --> 643 <attr name="noHistory" format="boolean" /> 644 645 <!-- Specify whether an activity's task state should always be maintained 646 by the system, or if it is allowed to reset the task to its initial 647 state in certain situations. 648 649 <p>Normally the system will reset a task (remove all activities from 650 the stack and reset the root activity) in certain situations when 651 the user re-selects that task from the home screen. Typically this 652 will be done if the user hasn't visited that task for a certain 653 amount of time, such as 30 minutes. 654 655 <p>By setting this attribute, the user will always return to your 656 task in its last state, regardless of how they get there. This is 657 useful, for example, in an application like the web browser where there 658 is a lot of state (such as multiple open tabs) that the application 659 would not like to lose. --> 660 <attr name="alwaysRetainTaskState" format="boolean" /> 661 662 <!-- Indicates that an Activity does not need to have its freeze state 663 (as returned by {@link android.app.Activity#onSaveInstanceState} 664 retained in order to be restarted. Generally you use this for activities 665 that do not store any state. When this flag is set, if for some reason 666 the activity is killed before it has a chance to save its state, 667 then the system will not remove it from the activity stack like 668 it normally would. Instead, the next time the user navigates to 669 it its {@link android.app.Activity#onCreate} method will be called 670 with a null icicle, just like it was starting for the first time. 671 672 <p>This is used by the Home activity to make sure it does not get 673 removed if it crashes for some reason. --> 674 <attr name="stateNotNeeded" format="boolean" /> 675 676 <!-- Indicates that an Activity should be excluded from the list of 677 recently launched activities. --> 678 <attr name="excludeFromRecents" format="boolean" /> 679 680 <!-- Specify that an Activity should be shown over the lock screen and, 681 in a multiuser environment, across all users' windows. 682 @deprecated use {@link android.R.attr#showForAllUsers} instead. --> 683 <attr name="showOnLockScreen" format="boolean" /> 684 685 <!-- Specify that an Activity should be shown even if the current/foreground user 686 is different from the user of the Activity. This will also force the 687 <code>android.view.LayoutParams.FLAG_SHOW_WHEN_LOCKED</code> flag 688 to be set for all windows of this activity --> 689 <attr name="showForAllUsers" format="boolean" /> 690 691 <!-- Specifies whether an {@link android.app.Activity} should be shown on top of the lock screen 692 whenever the lockscreen is up and the activity is resumed. Normally an activity will be 693 transitioned to the stopped state if it is started while the lockscreen is up, but with 694 this flag set the activity will remain in the resumed state visible on-top of the lock 695 screen. 696 697 <p>This should be used instead of {@link android.view.WindowManager.LayoutParams#FLAG_SHOW_WHEN_LOCKED} 698 flag set for Windows. When using the Window flag during activity startup, there may not be 699 time to add it before the system stops your activity for being behind the lock-screen. 700 This leads to a double life-cycle as it is then restarted.</p> --> 701 <attr name="showWhenLocked" format="boolean" /> 702 703 <!-- Specifies whether the screen should be turned on when the {@link android.app.Activity} is resumed. 704 Normally an activity will be transitioned to the stopped state if it is started while the 705 screen if off, but with this flag set the activity will cause the screen to turn on if the 706 activity will be visible and resumed due to the screen coming on. The screen will not be 707 turned on if the activity won't be visible after the screen is turned on. This flag is 708 normally used in conjunction with the {@link android.R.attr#showWhenLocked} flag to make 709 sure the activity is visible after the screen is turned on when the lockscreen is up. In 710 addition, if this flag is set and the activity calls 711 {@link android.app.KeyguardManager#requestDismissKeyguard} 712 the screen will turn on. 713 714 <p>This should be used instead of {@link android.view.WindowManager.LayoutParams#FLAG_TURN_SCREEN_ON} 715 flag set for Windows. When using the Window flag during activity startup, there may not be 716 time to add it before the system stops your activity because the screen has not yet turned 717 on. This leads to a double life-cycle as it is then restarted.</p> --> 718 <attr name="turnScreenOn" format="boolean" /> 719 720 <!-- Specify the authorities under which this content provider can be 721 found. Multiple authorities may be supplied by separating them 722 with a semicolon. Authority names should use a Java-style naming 723 convention (such as <code>com.google.provider.MyProvider</code>) 724 in order to avoid conflicts. Typically this name is the same 725 as the class implementation describing the provider's data structure. --> 726 <attr name="authorities" format="string" /> 727 728 <!-- Flag indicating whether this content provider would like to 729 participate in data synchronization. --> 730 <attr name="syncable" format="boolean" /> 731 732 <!-- Flag declaring this activity to be 'immersive'; immersive activities 733 should not be interrupted with other activities or notifications. --> 734 <attr name="immersive" format="boolean" /> 735 736 <!-- Flag declaring that this activity will be run in VR mode, and specifying 737 the component of the {@link android.service.vr.VrListenerService} that should be 738 bound while this Activity is visible if it is installed and enabled on this device. 739 This is equivalent to calling {@link android.app.Activity#setVrModeEnabled} with the 740 the given component name within the Activity that this attribute is set for. 741 Declaring this will prevent the system from leaving VR mode during an Activity 742 transition from one VR activity to another. --> 743 <attr name="enableVrMode" format="string" /> 744 745 <!-- Flag that specifies the activity's preferred screen rotation animation. 746 Valid values are "rotate", "crossfade", "jumpcut", and "seamless" as 747 described in 748 {@link android.view.WindowManager.LayoutParams#rotationAnimation}. 749 Specifying your rotation animation in 750 <code>WindowManager.LayoutParams</code> may be racy with app startup 751 and update transitions that occur during application startup; and so, 752 specify the animation in the manifest attribute. 753 --> 754 <attr name="rotationAnimation"> 755 <flag name="rotate" value= "0" /> 756 <flag name="crossfade" value = "1" /> 757 <flag name="jumpcut" value = "2" /> 758 <flag name="seamless" value = "3" /> 759 </attr> 760 761 <!-- Specify the order in which content providers hosted by a process 762 are instantiated when that process is created. Not needed unless 763 you have providers with dependencies between each other, to make 764 sure that they are created in the order needed by those dependencies. 765 The value is a simple integer, with higher numbers being 766 initialized first. --> 767 <attr name="initOrder" format="integer" /> 768 769 <!-- Specify the relative importance or ability in handling a particular 770 Intent. For receivers, this controls the order in which they are 771 executed to receive a broadcast (note that for 772 asynchronous broadcasts, this order is ignored). For activities, 773 this provides information about how good an activity is handling an 774 Intent; when multiple activities match an intent and have different 775 priorities, only those with the higher priority value will be 776 considered a match. 777 778 <p>Only use if you really need to impose some specific 779 order in which the broadcasts are received, or want to forcibly 780 place an activity to always be preferred over others. The value is a 781 single integer, with higher numbers considered to be better. --> 782 <attr name="priority" format="integer" /> 783 784 <!-- Indicate if this component is aware of direct boot lifecycle, and can be 785 safely run before the user has entered their credentials (such as a lock 786 pattern or PIN). --> 787 <attr name="directBootAware" format="boolean" /> 788 789 <!-- Specify how an activity should be launched. See the 790 <a href="{@docRoot}guide/topics/fundamentals/tasks-and-back-stack.html">Tasks and Back 791 Stack</a> document for important information on how these options impact 792 the behavior of your application. 793 794 <p>If this attribute is not specified, <code>standard</code> launch 795 mode will be used. Note that the particular launch behavior can 796 be changed in some ways at runtime through the 797 {@link android.content.Intent} flags 798 {@link android.content.Intent#FLAG_ACTIVITY_SINGLE_TOP}, 799 {@link android.content.Intent#FLAG_ACTIVITY_NEW_TASK}, and 800 {@link android.content.Intent#FLAG_ACTIVITY_MULTIPLE_TASK}. --> 801 <attr name="launchMode"> 802 <!-- The default mode, which will usually create a new instance of 803 the activity when it is started, though this behavior may change 804 with the introduction of other options such as 805 {@link android.content.Intent#FLAG_ACTIVITY_NEW_TASK 806 Intent.FLAG_ACTIVITY_NEW_TASK}. --> 807 <enum name="standard" value="0" /> 808 <!-- If, when starting the activity, there is already an 809 instance of the same activity class in the foreground that is 810 interacting with the user, then 811 re-use that instance. This existing instance will receive a call to 812 {@link android.app.Activity#onNewIntent Activity.onNewIntent()} with 813 the new Intent that is being started. --> 814 <enum name="singleTop" value="1" /> 815 <!-- If, when starting the activity, there is already a task running 816 that starts with this activity, then instead of starting a new 817 instance the current task is brought to the front. The existing 818 instance will receive a call to {@link android.app.Activity#onNewIntent 819 Activity.onNewIntent()} 820 with the new Intent that is being started, and with the 821 {@link android.content.Intent#FLAG_ACTIVITY_BROUGHT_TO_FRONT 822 Intent.FLAG_ACTIVITY_BROUGHT_TO_FRONT} flag set. This is a superset 823 of the singleTop mode, where if there is already an instance 824 of the activity being started at the top of the stack, it will 825 receive the Intent as described there (without the 826 FLAG_ACTIVITY_BROUGHT_TO_FRONT flag set). See the 827 <a href="{@docRoot}guide/topics/fundamentals/tasks-and-back-stack.html">Tasks and Back 828 Stack</a> document for more details about tasks.--> 829 <enum name="singleTask" value="2" /> 830 <!-- Only allow one instance of this activity to ever be 831 running. This activity gets a unique task with only itself running 832 in it; if it is ever launched again with the same Intent, then that 833 task will be brought forward and its 834 {@link android.app.Activity#onNewIntent Activity.onNewIntent()} 835 method called. If this 836 activity tries to start a new activity, that new activity will be 837 launched in a separate task. See the 838 <a href="{@docRoot}guide/topics/fundamentals/tasks-and-back-stack.html">Tasks and Back 839 Stack</a> document for more details about tasks.--> 840 <enum name="singleInstance" value="3" /> 841 <!-- The activity can only be running as the root activity of the task, the first activity 842 that created the task, and therefore there will only be one instance of this activity 843 in a task. In contrast to the {@code singleTask} launch mode, this activity can be 844 started in multiple instances in different tasks if the 845 {@code FLAG_ACTIVITY_MULTIPLE_TASK} or {@code FLAG_ACTIVITY_NEW_DOCUMENT} is set. 846 This enum value is introduced in API level 31. --> 847 <enum name="singleInstancePerTask" value="4" /> 848 </attr> 849 <!-- Specify the orientation an activity should be run in. If not 850 specified, it will run in the current preferred orientation 851 of the screen. 852 <p>This attribute is supported by the <a 853 href="{@docRoot}guide/topics/manifest/activity-element.html">{@code <activity>}</a> 854 element. 855 <aside class="note"><b>Note:</b> Device manufacturers can configure devices to override 856 (ignore) this attribute to improve the layout of apps. See 857 <a href="{@docRoot}guide/practices/device-compatibility-mode"> 858 Device compatibility mode</a>. 859 </aside> --> 860 <attr name="screenOrientation"> 861 <!-- No preference specified: let the system decide the best 862 orientation. This will either be the orientation selected 863 by the activity below, or the user's preferred orientation 864 if this activity is the bottom of a task. If the user 865 explicitly turned off sensor based orientation through settings 866 sensor based device rotation will be ignored. If not by default 867 sensor based orientation will be taken into account and the 868 orientation will changed based on how the user rotates the device. 869 Corresponds to 870 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_UNSPECIFIED}. --> 871 <enum name="unspecified" value="-1" /> 872 <!-- Would like to have the screen in a landscape orientation: that 873 is, with the display wider than it is tall, ignoring sensor data. 874 Corresponds to 875 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_LANDSCAPE}. --> 876 <enum name="landscape" value="0" /> 877 <!-- Would like to have the screen in a portrait orientation: that 878 is, with the display taller than it is wide, ignoring sensor data. 879 Corresponds to 880 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_PORTRAIT}. --> 881 <enum name="portrait" value="1" /> 882 <!-- Use the user's current preferred orientation of the handset. 883 Corresponds to 884 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_USER}. --> 885 <enum name="user" value="2" /> 886 <!-- Keep the screen in the same orientation as whatever is behind 887 this activity. 888 Corresponds to 889 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_BEHIND}. --> 890 <enum name="behind" value="3" /> 891 <!-- Orientation is determined by a physical orientation sensor: 892 the display will rotate based on how the user moves the device. 893 Ignores user's setting to turn off sensor-based rotation. 894 Corresponds to 895 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_SENSOR}. --> 896 <enum name="sensor" value="4" /> 897 <!-- Always ignore orientation determined by orientation sensor: 898 the display will not rotate when the user moves the device. 899 Corresponds to 900 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_NOSENSOR}. --> 901 <enum name="nosensor" value="5" /> 902 <!-- Would like to have the screen in landscape orientation, but can 903 use the sensor to change which direction the screen is facing. 904 Corresponds to 905 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_SENSOR_LANDSCAPE}. --> 906 <enum name="sensorLandscape" value="6" /> 907 <!-- Would like to have the screen in portrait orientation, but can 908 use the sensor to change which direction the screen is facing. 909 Corresponds to 910 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_SENSOR_PORTRAIT}. --> 911 <enum name="sensorPortrait" value="7" /> 912 <!-- Would like to have the screen in landscape orientation, turned in 913 the opposite direction from normal landscape. 914 Corresponds to 915 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_REVERSE_LANDSCAPE}. --> 916 <enum name="reverseLandscape" value="8" /> 917 <!-- Would like to have the screen in portrait orientation, turned in 918 the opposite direction from normal portrait. 919 Corresponds to 920 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_REVERSE_PORTRAIT}. --> 921 <enum name="reversePortrait" value="9" /> 922 <!-- Orientation is determined by a physical orientation sensor: 923 the display will rotate based on how the user moves the device. 924 This allows any of the 4 possible rotations, regardless of what 925 the device will normally do (for example some devices won't 926 normally use 180 degree rotation). 927 Corresponds to 928 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_FULL_SENSOR}. --> 929 <enum name="fullSensor" value="10" /> 930 <!-- Would like to have the screen in landscape orientation, but if 931 the user has enabled sensor-based rotation then we can use the 932 sensor to change which direction the screen is facing. 933 Corresponds to 934 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_USER_LANDSCAPE}. --> 935 <enum name="userLandscape" value="11" /> 936 <!-- Would like to have the screen in portrait orientation, but if 937 the user has enabled sensor-based rotation then we can use the 938 sensor to change which direction the screen is facing. 939 Corresponds to 940 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_USER_PORTRAIT}. --> 941 <enum name="userPortrait" value="12" /> 942 <!-- Respect the user's sensor-based rotation preference, but if 943 sensor-based rotation is enabled then allow the screen to rotate 944 in all 4 possible directions regardless of what 945 the device will normally do (for example some devices won't 946 normally use 180 degree rotation). 947 Corresponds to 948 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_FULL_USER}. --> 949 <enum name="fullUser" value="13" /> 950 <!-- Screen is locked to its current rotation, whatever that is. 951 Corresponds to 952 {@link android.content.pm.ActivityInfo#SCREEN_ORIENTATION_LOCKED}. --> 953 <enum name="locked" value="14" /> 954 </attr> 955 956 <!-- Specify the configuration changes that trigger the system to recreate the 957 current activity if any of these configuration changes happen in the system. 958 The valid configuration changes include mcc and mnc which are the same with 959 those in configChanges. By default from Android O, we don't recreate the activity 960 even the app doesn't specify mcc or mnc in configChanges. If the app wants to 961 be recreated, specify them in recreateOnConfigChanges. --> 962 <attr name="recreateOnConfigChanges"> 963 <!-- The IMSI MCC has changed, that is a SIM has been detected and 964 updated the Mobile Country Code. --> 965 <flag name="mcc" value="0x0001" /> 966 <!-- The IMSI MNC has changed, that is a SIM has been detected and 967 updated the Mobile Network Code. --> 968 <flag name="mnc" value="0x0002" /> 969 </attr> 970 971 <!-- Specify one or more configuration changes that the activity will 972 handle itself. If not specified, the activity will be restarted 973 if any of these configuration changes happen in the system. Otherwise, 974 the activity will remain running and its 975 {@link android.app.Activity#onConfigurationChanged Activity.onConfigurationChanged} 976 method called with the new configuration. 977 978 <p>Note that all of these configuration changes can impact the 979 resource values seen by the application, so you will generally need 980 to re-retrieve all resources (including view layouts, drawables, etc) 981 to correctly handle any configuration change. 982 983 <p>These values must be kept in sync with those in 984 {@link android.content.pm.ActivityInfo} and 985 include/utils/ResourceTypes.h. --> 986 <attr name="configChanges"> 987 <!-- The IMSI MCC has changed, that is a SIM has been detected and 988 updated the Mobile Country Code. By default from Android O, we 989 don't recreate the activity even the app doesn't specify mcc in 990 configChanges. If the app wants to recreate the activity, specify 991 mcc in recreateOnConfigChanges. --> 992 <flag name="mcc" value="0x0001" /> 993 <!-- The IMSI MNC has changed, that is a SIM has been detected and 994 updated the Mobile Network Code. By default from Android O, we 995 don't recreate the activity even the app doesn't specify mnc in 996 configChanges. If the app wants to recreate the acvitity, specify 997 mnc in recreateOnConfigChanges. --> 998 <flag name="mnc" value="0x0002" /> 999 <!-- The locale has changed, that is the user has selected a new 1000 language that text should be displayed in. --> 1001 <flag name="locale" value="0x0004" /> 1002 <!-- The touchscreen has changed. Should never normally happen. --> 1003 <flag name="touchscreen" value="0x0008" /> 1004 <!-- The keyboard type has changed, for example the user has plugged 1005 in an external keyboard. --> 1006 <flag name="keyboard" value="0x0010" /> 1007 <!-- The keyboard or navigation accessibility has changed, for example 1008 the user has slid the keyboard out to expose it. Note that 1009 despite its name, this applied to any accessibility: keyboard 1010 or navigation. --> 1011 <flag name="keyboardHidden" value="0x0020" /> 1012 <!-- The navigation type has changed. Should never normally happen. --> 1013 <flag name="navigation" value="0x0040" /> 1014 <!-- The screen orientation has changed, that is the user has 1015 rotated the device. --> 1016 <flag name="orientation" value="0x0080" /> 1017 <!-- The screen layout has changed. This might be caused by a 1018 different display being activated. --> 1019 <flag name="screenLayout" value="0x0100" /> 1020 <!-- The global user interface mode has changed. For example, 1021 going in or out of car mode, night mode changing, etc. --> 1022 <flag name="uiMode" value="0x0200" /> 1023 <!-- The current available screen size has changed. If applications don't 1024 target at least {@link android.os.Build.VERSION_CODES#HONEYCOMB_MR2} 1025 then the activity will always handle this itself (the change 1026 will not result in a restart). This represents a change in the 1027 currently available size, so will change when the user switches 1028 between landscape and portrait. --> 1029 <flag name="screenSize" value="0x0400" /> 1030 <!-- The physical screen size has changed. If applications don't 1031 target at least {@link android.os.Build.VERSION_CODES#HONEYCOMB_MR2} 1032 then the activity will always handle this itself (the change 1033 will not result in a restart). This represents a change in size 1034 regardless of orientation, so will only change when the actual 1035 physical screen size has changed such as switching to an external 1036 display. --> 1037 <flag name="smallestScreenSize" value="0x0800" /> 1038 <!-- The display density has changed. This might be caused by the user 1039 specifying a different display scale, or it might be caused by a 1040 different display being activated. --> 1041 <flag name="density" value="0x1000" /> 1042 <!-- The layout direction has changed. For example going from LTR to RTL. --> 1043 <flag name="layoutDirection" value="0x2000" /> 1044 <!-- The color mode of the screen has changed (color gamut or dynamic range). --> 1045 <flag name="colorMode" value="0x4000" /> 1046 <!-- The grammatical gender has changed, for example the user set the grammatical gender 1047 from the UI. --> 1048 <flag name="grammaticalGender" value="0x8000" /> 1049 <!-- The font scaling factor has changed, that is the user has 1050 selected a new global font size. --> 1051 <flag name="fontScale" value="0x40000000" /> 1052 <!-- The font weight adjustment value has changed. Used to reflect the user increasing font 1053 weight. --> 1054 <flag name="fontWeightAdjustment" value="0x10000000" /> 1055 </attr> 1056 1057 <!-- Indicate that the activity can be launched as the embedded child of another 1058 activity. Particularly in the case where the child lives in a container 1059 such as a Display owned by another activity. 1060 1061 <p>The default value of this attribute is <code>false</code>. --> 1062 <attr name="allowEmbedded" format="boolean" /> 1063 1064 <!-- A reference to an array resource containing the signing certificate digests, one of which a 1065 client is required to be signed with in order to embed the activity. If the client is not 1066 signed with one of the certificates in the set, and the activity does not allow embedding 1067 by untrusted hosts via {@link android.R.attr#allowUntrustedActivityEmbedding} flag, the 1068 embedding request will fail. 1069 <p>The digest should be computed over the DER encoding of the trusted certificate using the 1070 SHA-256 digest algorithm. 1071 <p>If only a single signer is declared this can also be a string resource, or the digest 1072 can be declared inline as the value for this attribute. 1073 <p>If the attribute is declared both on the application and the activity level, the value 1074 on the activity level takes precedence. --> 1075 <attr name="knownActivityEmbeddingCerts" format="reference|string" /> 1076 1077 <!-- Indicate that the activity can be embedded by untrusted hosts. In this case the 1078 interactions and visibility of the embedded activity may be limited. 1079 <p>The default value of this attribute is <code>false</code>. --> 1080 <attr name="allowUntrustedActivityEmbedding" format="boolean" /> 1081 1082 <!-- Specifies whether this {@link android.app.Activity} should be shown on 1083 top of the lock screen whenever the lockscreen is up and this activity has another 1084 activity behind it with the {@link android.R.attr#showWhenLocked} attribute set. That 1085 is, this activity is only visible on the lock screen if there is another activity with 1086 the {@link android.R.attr#showWhenLocked} attribute visible at the same time on the 1087 lock screen. A use case for this is permission dialogs, that should only be visible on 1088 the lock screen if their requesting activity is also visible. 1089 1090 <p>The default value of this attribute is <code>false</code>. --> 1091 <attr name="inheritShowWhenLocked" format="boolean" /> 1092 1093 <!-- Descriptive text for the associated data. --> 1094 <attr name="description" format="reference" /> 1095 1096 <!-- The name of the application package that an Instrumentation object 1097 will run against. --> 1098 <attr name="targetPackage" format="string" /> 1099 1100 <!-- The name of an application's processes that an Instrumentation object 1101 will run against. If not specified, only runs in the main process of the targetPackage. 1102 Can either be a comma-separated list of process names or '*' for any process that 1103 launches to run targetPackage code. --> 1104 <attr name="targetProcesses" format="string" /> 1105 1106 <!-- Flag indicating that an Instrumentation class wants to take care 1107 of starting/stopping profiling itself, rather than relying on 1108 the default behavior of profiling the complete time it is running. 1109 This allows it to target profiling data at a specific set of 1110 operations. --> 1111 <attr name="handleProfiling" format="boolean" /> 1112 1113 <!-- Flag indicating that an Instrumentation class should be run as a 1114 functional test. --> 1115 <attr name="functionalTest" format="boolean" /> 1116 1117 <!-- The touch screen type used by an application. --> 1118 <attr name="reqTouchScreen"> 1119 <enum name="undefined" value="0" /> 1120 <enum name="notouch" value="1" /> 1121 <enum name="stylus" value="2" /> 1122 <enum name="finger" value="3" /> 1123 </attr> 1124 1125 <!-- The input method preferred by an application. --> 1126 <attr name="reqKeyboardType"> 1127 <enum name="undefined" value="0" /> 1128 <enum name="nokeys" value="1" /> 1129 <enum name="qwerty" value="2" /> 1130 <enum name="twelvekey" value="3" /> 1131 </attr> 1132 1133 <!-- Application's requirement for a hard keyboard --> 1134 <attr name="reqHardKeyboard" format="boolean" /> 1135 1136 <!-- The navigation device preferred by an application. --> 1137 <attr name="reqNavigation"> 1138 <enum name="undefined" value="0" /> 1139 <enum name="nonav" value="1" /> 1140 <enum name="dpad" value="2" /> 1141 <enum name="trackball" value="3" /> 1142 <enum name="wheel" value="4" /> 1143 </attr> 1144 1145 <!-- Application's requirement for five way navigation --> 1146 <attr name="reqFiveWayNav" format="boolean" /> 1147 1148 <!-- The name of the class subclassing <code>BackupAgent</code> to manage 1149 backup and restore of the application's data on external storage. --> 1150 <attr name="backupAgent" format="string" /> 1151 1152 <!-- Whether to allow the application to participate in the backup 1153 and restore infrastructure. If this attribute is set to <code>false</code>, 1154 no backup or restore of the application will ever be performed, even by a 1155 full-system backup that would otherwise cause all application data to be saved 1156 via adb. The default value of this attribute is <code>true</code>. --> 1157 <attr name="allowBackup" format="boolean" /> 1158 1159 <!-- Applications will set this in their manifest to opt-in to or out of full app data back-up 1160 and restore. Alternatively they can set it to an xml resource within their app that will 1161 be parsed by the BackupAgent to selectively backup files indicated within that xml. --> 1162 <attr name="fullBackupContent" format="reference|boolean" /> 1163 1164 <!-- Indicates that even though the application provides a <code>BackupAgent</code>, 1165 only full-data streaming backup operations are to be performed to save the app's 1166 data. This lets the app rely on full-data backups while still participating in 1167 the backup and restore process via the BackupAgent's full-data backup APIs. 1168 When this attribute is <code>true</code> the app's BackupAgent overrides of 1169 the onBackup() and onRestore() callbacks can be empty stubs. --> 1170 <attr name="fullBackupOnly" format="boolean" /> 1171 1172 <!-- Whether the application in question should be terminated after its 1173 settings have been restored during a full-system restore operation. 1174 Single-package restore operations will never cause the application to 1175 be shut down. Full-system restore operations typically only occur once, 1176 when the phone is first set up. Third-party applications will not usually 1177 need to use this attribute. 1178 1179 <p>The default is <code>true</code>, which means that after the application 1180 has finished processing its data during a full-system restore, it will be 1181 terminated. --> 1182 <attr name="killAfterRestore" format="boolean" /> 1183 1184 <!-- @deprecated This attribute is not used by the Android operating system. --> 1185 <attr name="restoreNeedsApplication" format="boolean" /> 1186 1187 <!-- Indicate that the application is prepared to attempt a restore of any 1188 backed-up dataset, even if the backup is apparently from a newer version 1189 of the application than is currently installed on the device. Setting 1190 this attribute to <code>true</code> will permit the Backup Manager to 1191 attempt restore even when a version mismatch suggests that the data are 1192 incompatible. <em>Use with caution!</em> 1193 1194 <p>The default value of this attribute is <code>false</code>. --> 1195 <attr name="restoreAnyVersion" format="boolean" /> 1196 1197 <!-- Indicates that full-data backup operations for this application may 1198 be performed even if the application is in a foreground-equivalent 1199 state. <em>Use with caution!</em> Setting this flag to <code>true</code> 1200 can impact app behavior while the user is interacting with the device. 1201 1202 <p>If unspecified, the default value of this attribute is <code>false</code>, 1203 which means that the OS will avoid backing up the application while it is 1204 running in the foreground (such as a music app that is actively playing 1205 music via a service in the startForeground() state). --> 1206 <attr name="backupInForeground" format="boolean" /> 1207 1208 <!-- The default install location defined by an application. --> 1209 <attr name="installLocation"> 1210 <!-- Let the system decide ideal install location --> 1211 <enum name="auto" value="0" /> 1212 <!-- Explicitly request to be installed on internal phone storage 1213 only. --> 1214 <enum name="internalOnly" value="1" /> 1215 <!-- Prefer to be installed on SD card. There is no guarantee that 1216 the system will honor this request. The application might end 1217 up being installed on internal storage if external media 1218 is unavailable or too full. --> 1219 <enum name="preferExternal" value="2" /> 1220 </attr> 1221 1222 <!-- If set to <code>true</code>, indicates to the platform that any split APKs 1223 installed for this application should be loaded into their own Context 1224 objects and not appear in the base application's Context. 1225 1226 <p>The default value of this attribute is <code>false</code>. --> 1227 <attr name="isolatedSplits" format="boolean" /> 1228 1229 <!-- The classname of the classloader used to load the application's classes 1230 from its APK. The APK in question can either be the 'base' APK or any 1231 of the application's 'split' APKs if it's using a feature split. 1232 1233 <p> 1234 The supported values for this attribute are 1235 <code>dalvik.system.PathClassLoader</code> and 1236 <code>dalvik.system.DelegateLastClassLoader</code>. If unspecified, 1237 the default value of this attribute is <code>dalvik.system.PathClassLoader</code>. 1238 1239 If an unknown classloader is provided, a PackageManagerException with cause 1240 <code>PackageManager.INSTALL_PARSE_FAILED_MANIFEST_MALFORMED</code> will be 1241 thrown and the app will not be installed. 1242 --> 1243 <attr name="classLoader" format="string" /> 1244 1245 <!-- Name of the class that gets invoked for preloading application code, when starting an 1246 {@link android.R.attr#isolatedProcess} service that has 1247 {@link android.R.attr#useAppZygote} set to <code>true</code>. This is a fully 1248 qualified class name (for example, com.mycompany.myapp.MyZygotePreload); as a 1249 short-hand if the first character of the class is a period then it is appended 1250 to your package name. The class must implement the {@link android.app.ZygotePreload} 1251 interface. --> 1252 <attr name="zygotePreloadName" format="string"/> 1253 1254 <!-- If set to <code>true</code>, indicates to the platform that this APK is 1255 a 'feature' split and that it implicitly depends on the base APK. This distinguishes 1256 this split APK from a 'configuration' split, which provides resource overrides 1257 for a particular 'feature' split. Only useful when the base APK specifies 1258 <code>android:isolatedSplits="true"</code>. 1259 1260 <p>The default value of this attribute is <code>false</code>. --> 1261 <attr name="isFeatureSplit" format="boolean" /> 1262 1263 <!-- Flag to specify if this APK requires at least one split [either feature or 1264 resource] to be present in order to function. Default value is false. 1265 @deprecated Use {@link android.R.attr#requiredSplitTypes} instead. --> 1266 <attr name="isSplitRequired" format="boolean" /> 1267 1268 <!-- List of split types required by this APK to be present in order to function properly, 1269 separated by commas. The platform will reject installation of an app that is missing 1270 any required split types. Each split type is a string, and is only used for matching 1271 <code>requiredSplitTypes</code> and <code>splitTypes</code>. As an example, if this 1272 APK requires localized string resources, screen density resources, and native code 1273 this value could be "language,density,abi". Default value is null to indicate no split 1274 types are required. --> 1275 <attr name="requiredSplitTypes" format="string" /> 1276 1277 <!-- List of split types offered by this APK, separated by commas. Each split type is a 1278 string, and is only used for matching <code>requiredSplitTypes</code> and 1279 <code>splitTypes</code>. As an example, if this split offers localized string resources, 1280 and screen density resources the value could be "language,density". Default value is 1281 null to indicate no split types are offered. --> 1282 <attr name="splitTypes" format="string" /> 1283 1284 <!-- Flag to specify if this app (or process) wants to run the dex within its APK but not 1285 extracted or locally compiled variants. This keeps the dex code protected by the APK 1286 signature. Such apps (or processes) will always run in JIT mode (same when they are first 1287 installed). If enabled at the app level, the system will never generate ahead-of-time 1288 compiled code for the app. Depending on the app's workload, there may be some run time 1289 performance change, noteably the cold start time. 1290 1291 <p>This attribute can be applied to either 1292 {@link android.R.styleable#AndroidManifestProcess process} or 1293 {@link android.R.styleable#AndroidManifestApplication application} tags. If enabled at the 1294 app level, any process level attribute is effectively ignored. --> 1295 <attr name="useEmbeddedDex" format="boolean" /> 1296 1297 <!-- Extra options for an activity's UI. Applies to either the {@code <activity>} or 1298 {@code <application>} tag. If specified on the {@code <application>} 1299 tag these will be considered defaults for all activities in the 1300 application. --> 1301 <attr name="uiOptions"> 1302 <!-- No extra UI options. This is the default. --> 1303 <flag name="none" value="0" /> 1304 <!-- Split the options menu into a separate bar at the bottom of 1305 the screen when severely constrained for horizontal space. 1306 (e.g. portrait mode on a phone.) Instead of a small number 1307 of action buttons appearing in the action bar at the top 1308 of the screen, the action bar will split into the top navigation 1309 section and the bottom menu section. Menu items will not be 1310 split across the two bars; they will always appear together. --> 1311 <flag name="splitActionBarWhenNarrow" value="1" /> 1312 </attr> 1313 1314 <!-- The name of the logical parent of the activity as it appears in the manifest. --> 1315 <attr name="parentActivityName" format="string" /> 1316 1317 <!-- Define how an activity persist across reboots. Activities defined as "never" will not 1318 be persisted. Those defined as "always" will be persisted. Those defined as "taskOnly" 1319 will persist the root activity of the task only. See below for more detail as to 1320 what gets persisted. --> 1321 <attr name="persistableMode"> 1322 <!-- The default. If this activity forms the root of a task then that task will be 1323 persisted across reboots but only the launching intent will be used. If the task 1324 relinquishes its identity then the intent used is that of the topmost inherited 1325 identity. All activities above this activity in the task will not be persisted. 1326 In addition this activity will not be passed a PersistableBundle into which it 1327 could have stored its state. --> 1328 <enum name="persistRootOnly" value="0" /> 1329 <!-- If this activity forms the root of a task then that task will not be persisted 1330 across reboots --> 1331 <enum name="persistNever" value="1" /> 1332 <!-- If this activity forms the root of a task then the task and this activity will 1333 be persisted across reboots. If the activity above this activity is also 1334 tagged with the attribute <code>"persist"</code> then it will be persisted as well. 1335 And so on up the task stack until either an activity without the 1336 <code>persistableMode="persistAcrossReboots"</code> attribute or one that was launched 1337 with the flag Intent.FLAG_CLEAR_TASK_WHEN_RESET is encountered. 1338 1339 <p>Activities that are declared with the persistAcrossReboots attribute will be 1340 provided with a PersistableBundle in onSavedInstanceState(), These activities may 1341 use this PeristableBundle to save their state. Then, following a reboot, that 1342 PersistableBundle will be provided back to the activity in its onCreate() method. --> 1343 <enum name="persistAcrossReboots" value="2" /> 1344 </attr> 1345 1346 <!-- This attribute specifies that an activity shall become the root activity of a 1347 new task each time it is launched. Using this attribute permits the user to 1348 have multiple documents from the same applications appear in the recent tasks list. 1349 1350 <p>Such a document is any kind of item for which an application may want to 1351 maintain multiple simultaneous instances. Examples might be text files, web 1352 pages, spreadsheets, or emails. Each such document will be in a separate 1353 task in the recent tasks list. 1354 1355 <p>This attribute is equivalent to adding the flag {@link 1356 android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT} to every Intent used to launch 1357 the activity. 1358 1359 <p>The documentLaunchMode attribute may be assigned one of four values, "none", 1360 "intoExisting", "always" and "never", described in detail below. For values other than 1361 <code>none</code> and <code>never</code> the activity must be defined with 1362 {@link android.R.attr#launchMode} <code>standard</code>. 1363 If this attribute is not specified, <code>none</code> will be used. 1364 Note that <code>none</code> can be overridden at run time if the Intent used 1365 to launch it contains the flag {@link android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT 1366 Intent.FLAG_ACTIVITY_NEW_DOCUMENT}. 1367 Similarly <code>intoExisting</code> will be overridden by the flag 1368 {@link android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT 1369 Intent.FLAG_ACTIVITY_NEW_DOCUMENT} combined with 1370 {@link android.content.Intent#FLAG_ACTIVITY_MULTIPLE_TASK 1371 Intent.FLAG_ACTIVITY_MULTIPLE_TASK}. If the value of 1372 documentLaunchModes is <code>never</code> then any use of 1373 {@link android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT 1374 Intent.FLAG_ACTIVITY_NEW_DOCUMENT} to launch this activity will be ignored. --> 1375 <attr name="documentLaunchMode"> 1376 <!-- The default mode, which will create a new task only when 1377 {@link android.content.Intent#FLAG_ACTIVITY_NEW_TASK 1378 Intent.FLAG_ACTIVITY_NEW_TASK} is set. --> 1379 <enum name="none" value="0" /> 1380 <!-- All tasks will be searched for one whose base Intent's ComponentName and 1381 data URI match those of the launching Intent. If such a task is found 1382 that task will be cleared and restarted with the root activity receiving a call 1383 to {@link android.app.Activity#onNewIntent Activity.onNewIntent}. If no 1384 such task is found a new task will be created. 1385 <p>This is the equivalent of launching an activity with {@link 1386 android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT Intent.FLAG_ACTIVITY_NEW_DOCUMENT} 1387 set and without {@link android.content.Intent#FLAG_ACTIVITY_MULTIPLE_TASK 1388 Intent.FLAG_ACTIVITY_MULTIPLE_TASK} set. --> 1389 <enum name="intoExisting" value="1" /> 1390 <!-- A new task rooted at this activity will be created. This will happen whether or 1391 not there is an existing task whose ComponentName and data URI match 1392 that of the launcing intent This is the equivalent of launching an activity 1393 with {@link 1394 android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT Intent.FLAG_ACTIVITY_NEW_DOCUMENT} 1395 and {@link android.content.Intent#FLAG_ACTIVITY_MULTIPLE_TASK 1396 Intent.FLAG_ACTIVITY_MULTIPLE_TASK} both set. --> 1397 <enum name="always" value="2" /> 1398 <!-- This activity will not be launched into a new document even if the Intent contains 1399 {@link android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT 1400 Intent.FLAG_ACTIVITY_NEW_DOCUMENT}. This gives the activity writer ultimate 1401 control over how their activity is used. Note that applications prior to api 1402 21 will default to documentLaunchMode="none" so only activities that explicitly 1403 opt out with <code>"never"</code> may do so. --> 1404 <enum name="never" value="3" /> 1405 </attr> 1406 1407 <!-- The maximum number of entries of tasks rooted at this activity in the recent task list. 1408 When this number of entries is reached the least recently used instance of this activity 1409 will be removed from recents. The value will be clamped between 1 and 100 inclusive. 1410 The default value for this if it is not specified is 15. --> 1411 <attr name="maxRecents" format="integer" /> 1412 1413 <!-- Tasks launched by activities with this attribute will remain in the recent tasks 1414 list until the last activity in the task is completed. When that happens the task 1415 will be automatically removed from the recent tasks list. This overrides the caller's 1416 use of {@link android.content.Intent#FLAG_ACTIVITY_RETAIN_IN_RECENTS 1417 Intent.FLAG_ACTIVITY_RETAIN_IN_RECENTS} --> 1418 <attr name="autoRemoveFromRecents" format="boolean" /> 1419 1420 <!-- Tasks whose root has this attribute set to true will replace baseIntent with that of the 1421 next activity in the task. If the next activity also has this attribute set to true then 1422 it will yield the baseIntent to any activity that it launches in the same task. This 1423 continues until an activity is encountered which has this attribute set to false. False 1424 is the default. This attribute set to true also permits activity's use of the 1425 TaskDescription to change labels, colors and icons in the recent task list. 1426 1427 <p>NOTE: Setting this flag to <code>true</code> will not change the affinity of the task, 1428 which is used for intent resolution during activity launch. The task's root activity will 1429 always define its affinity. --> 1430 <attr name="relinquishTaskIdentity" format="boolean" /> 1431 1432 <!-- Indicate that it is okay for this activity be resumed while the previous 1433 activity is in the process of pausing, without waiting for the previous pause 1434 to complete. Use this with caution: your activity can not acquire any exclusive 1435 resources (such as opening the camera or recording audio) when it launches, or it 1436 may conflict with the previous activity and fail. 1437 1438 <p>The default value of this attribute is <code>false</code>. --> 1439 <attr name="resumeWhilePausing" format="boolean" /> 1440 1441 <!-- Hint to platform that the activity works well in multi-window mode. Intended for a 1442 multi-window device where there can be multiple activities of various sizes on the screen 1443 at the same time. 1444 1445 <p>The default value is <code>false</code> for applications with 1446 <code>targetSdkVersion</code> lesser than {@link android.os.Build.VERSION_CODES#N} and 1447 <code>true</code> otherwise. 1448 1449 <p>Setting this flag to <code>false</code> lets the system know that the app may not be 1450 tested or optimized for multi-window environment. The system may still put such activity in 1451 multi-window with compatibility mode applied. It also does not guarantee that there will be 1452 no other apps in multi-window visible on screen (e.g. picture-in-picture) or on other 1453 displays. Therefore, this flag cannot be used to assure an exclusive resource access. 1454 1455 <p>A task's root activity value is applied to all additional activities launched in 1456 the task. That is if the root activity of a task is resizeable then the system will treat 1457 all other activities in the task as resizeable and will not if the root activity isn't 1458 resizeable. 1459 1460 <aside class="note"><b>Note:</b> 1461 <ul> 1462 <li>On Android 11 (API level 30) and lower, the value of 1463 {@link android.R.attr#screenOrientation} is ignored for resizeable activities 1464 in multi-window mode. 1465 <li>Device manufacturers can configure devices to override (ignore) this attribute 1466 to force apps to resize. The override does not affect the app's support for 1467 multi-window mode. See 1468 <a href="{@docRoot}guide/practices/device-compatibility-mode"> 1469 Device compatibility mode</a>. 1470 </ul> 1471 </aside> --> 1472 <attr name="resizeableActivity" format="boolean" /> 1473 1474 <!-- Indicates that the activity specifically supports the picture-in-picture form of 1475 multi-window. If true, this activity will support entering picture-in-picture, but will 1476 only support split-screen and other forms of multi-window if 1477 {@link android.R.attr#resizeableActivity} is also set to true. 1478 1479 Note that your activity may still be resized even if this attribute is true and 1480 {@link android.R.attr#resizeableActivity} is false. 1481 1482 <p>The default value is <code>false</code>. --> 1483 <attr name="supportsPictureInPicture" format="boolean" /> 1484 1485 <!-- This value indicates the maximum aspect ratio the activity supports. If the app runs on a 1486 device with a wider aspect ratio, the system automatically letterboxes the app, leaving 1487 portions of the screen unused so the app can run at its specified maximum aspect ratio. 1488 <p>Maximum aspect ratio, expressed as (longer dimension / shorter dimension) in decimal 1489 form. For example, if the maximum aspect ratio is 7:3, set value to 2.33. 1490 <p>Value needs to be greater or equal to 1.0, otherwise it is ignored. 1491 <aside class="note"><b>Note:</b> 1492 <ul> 1493 <li>This attribute is ignored if the activity has 1494 {@link android.R.attr#resizeableActivity} set to {@code true}. 1495 <li>Device manufacturers can configure devices to override (ignore) this attribute 1496 to improve the layout of apps. See 1497 <a href="{@docRoot}guide/practices/device-compatibility-mode"> 1498 Device compatibility mode</a>. 1499 </ul> 1500 </aside> --> 1501 <attr name="maxAspectRatio" format="float" /> 1502 1503 <!-- This value indicates the minimum aspect ratio the activity supports. If the app runs on a 1504 device with a narrower aspect ratio, the system automatically letterboxes the app, leaving 1505 portions of the screen unused so the app can run at its specified minimum aspect ratio. 1506 <p>Minimum aspect ratio, expressed as (longer dimension / shorter dimension) in decimal 1507 form. For example, if the minimum aspect ratio is 4:3, set value to 1.33. 1508 <p>Value needs to be greater or equal to 1.0, otherwise it is ignored. 1509 <aside class="note"><b>Note:</b> 1510 <ul> 1511 <li>This attribute is ignored if the activity has 1512 {@link android.R.attr#resizeableActivity} set to {@code true}. 1513 <li>Device manufacturers can configure devices to override (ignore) this attribute 1514 to improve the layout of apps. See 1515 <a href="{@docRoot}guide/practices/device-compatibility-mode"> 1516 Device compatibility mode</a>. 1517 </ul> 1518 </aside> --> 1519 <attr name="minAspectRatio" format="float" /> 1520 1521 <!-- This value indicates how tasks rooted at this activity will behave in lockTask mode. 1522 While in lockTask mode the system will not launch non-permitted tasks until 1523 lockTask mode is disabled. 1524 <p>While in lockTask mode with multiple permitted tasks running, each launched task is 1525 permitted to finish, transitioning to the previous locked task, until there is only one 1526 task remaining. At that point the last task running is not permitted to finish, unless it 1527 uses the value always. --> 1528 <attr name="lockTaskMode"> 1529 <!-- This is the default value. Tasks will not launch into lockTask mode but can be 1530 placed there by calling {@link android.app.Activity#startLockTask}. If a task with 1531 this mode has been allowlisted using {@link 1532 android.app.admin.DevicePolicyManager#setLockTaskPackages} then calling 1533 {@link android.app.Activity#startLockTask} will enter lockTask mode immediately, 1534 otherwise the user will be presented with a dialog to approve entering pinned mode. 1535 <p>If the system is already in lockTask mode when a new task rooted at this activity 1536 is launched that task will or will not start depending on whether the package of this 1537 activity has been allowlisted. 1538 <p>Tasks rooted at this activity can only exit lockTask mode using 1539 {@link android.app.Activity#stopLockTask}. --> 1540 <enum name="normal" value="0"/> 1541 <!-- Tasks will not launch into lockTask mode and cannot be placed there using 1542 {@link android.app.Activity#startLockTask} or be pinned from the Overview screen. 1543 If the system is already in lockTask mode when a new task rooted at this activity is 1544 launched that task will not be started. 1545 <p>Note: This mode is only available to system and privileged applications. 1546 Non-privileged apps with this value will be treated as normal. 1547 --> 1548 <enum name="never" value="1"/> 1549 <!-- Tasks rooted at this activity will always launch into lockTask mode. If the system is 1550 already in lockTask mode when this task is launched then the new task will be launched 1551 on top of the current task. Tasks launched in this mode are capable of exiting 1552 lockTask mode using {@link android.app.Activity#finish()}. 1553 <p>Note: This mode is only available to system and privileged applications. 1554 Non-privileged apps with this value will be treated as normal. 1555 --> 1556 <enum name="always" value="2"/> 1557 <!-- If the DevicePolicyManager (DPM) authorizes this package ({@link 1558 android.app.admin.DevicePolicyManager#setLockTaskPackages}) then this mode is 1559 identical to always, except that the activity needs to call 1560 {@link android.app.Activity#stopLockTask} before being able to finish if it is the last 1561 locked task. 1562 If the DPM does not authorize this package then this mode is identical to normal. --> 1563 <enum name="if_whitelisted" value="3"/> 1564 </attr> 1565 <!-- When set installer will extract native libraries. If set to false 1566 libraries in the apk must be stored and page-aligned. --> 1567 <attr name="extractNativeLibs" format="boolean"/> 1568 1569 <!-- Specify whether an activity intent filter will need to be verified thru its set 1570 of data URIs. This will only be used when the Intent's action is set to 1571 {@link android.content.Intent#ACTION_VIEW Intent.ACTION_VIEW} and the Intent's category is 1572 set to {@link android.content.Intent#CATEGORY_BROWSABLE Intent.CATEGORY_BROWSABLE} and the 1573 intern filter data scheme is set to "http" or "https". When set to true, the intent filter 1574 will need to use its data tag for getting the URIs to verify with. 1575 1576 For each URI, an HTTPS network request will be done to <code>/.well-known/statements.json</code> 1577 host to verify that the web site is okay with the app intercepting the URI. 1578 --> 1579 <attr name="autoVerify" format="boolean" /> 1580 1581 <!-- Specify whether a component should be visible to instant apps. 1582 --> 1583 <attr name="visibleToInstantApps" format="boolean" /> 1584 1585 <!-- An XML resource with the application's Network Security Config. --> 1586 <attr name="networkSecurityConfig" format="reference" /> 1587 1588 <!-- An XML resource with the application's {@link android.app.LocaleConfig} --> 1589 <attr name="localeConfig" format="reference" /> 1590 1591 <!-- When an application is partitioned into splits, this is the name of the 1592 split that contains the defined component. --> 1593 <attr name="splitName" format="string" /> 1594 1595 <!-- Specifies the target sandbox this app wants to use. Higher sandbox versions 1596 will have increasing levels of security. 1597 1598 <p>The default value of this attribute is <code>1</code>. 1599 <p> 1600 @deprecated The security properties have been moved to 1601 {@link android.os.Build.VERSION Build.VERSION} 27 and 28. --> 1602 <attr name="targetSandboxVersion" format="integer" /> 1603 1604 <!-- The user-visible SDK version (ex. 26) of the framework against which the application was 1605 compiled. This attribute is automatically specified by the Android build tools and should 1606 NOT be manually specified. 1607 <p> 1608 This attribute is the compile-time equivalent of 1609 {@link android.os.Build.VERSION#SDK_INT Build.VERSION.SDK_INT}. --> 1610 <attr name="compileSdkVersion" format="integer" /> 1611 1612 <!-- The development codename (ex. "O") of the framework against which the application was 1613 compiled, or "REL" if the application was compiled against a release build. This attribute 1614 is automatically specified by the Android build tools and should NOT be manually 1615 specified. 1616 <p> 1617 This attribute is the compile-time equivalent of 1618 {@link android.os.Build.VERSION#CODENAME Build.VERSION.CODENAME}. --> 1619 <attr name="compileSdkVersionCodename" format="string" /> 1620 1621 <!-- The (optional) fully-qualified name for a subclass of 1622 {@link android.app.AppComponentFactory} that the system uses to instantiate 1623 every other manifest defined class. Most applications 1624 don't need this attribute. If it's not specified, the system 1625 instantiates items without it.--> 1626 <attr name="appComponentFactory" format="string" /> 1627 1628 <attr name="usesNonSdkApi" format="boolean" /> 1629 1630 <!-- Whether attributions provided are meant to be user-visible. --> 1631 <attr name="attributionsAreUserVisible" format="boolean" /> 1632 1633 <!-- If a preloaded APK is marked updatableSystem = false, any request for an update will be rejected. 1634 If an APK marked updatableSystem = false is being installed, regardless of the updatableSystem state 1635 of the version it's replacing, the install will be rejected. 1636 This is a private attribute, used without android: namespace. --> 1637 <attr name="updatableSystem" format="boolean" /> 1638 1639 <!-- Allows each installer in the system image to designate another app in the system image to 1640 update the installer. --> 1641 <attr name="emergencyInstaller" format="string" /> 1642 1643 <!-- Specify the type of foreground service. Multiple types can be specified by ORing the flags 1644 together. --> 1645 <attr name="foregroundServiceType"> 1646 <!-- Data (photo, file, account) upload/download, backup/restore, import/export, fetch, 1647 transfer over network between device and cloud. 1648 1649 <p>For apps with <code>targetSdkVersion</code> 1650 {@link android.os.Build.VERSION_CODES#UPSIDE_DOWN_CAKE} and above, this type should NOT 1651 be used: calling 1652 {@link android.app.Service#startForeground(int, android.app.Notification, int)} with 1653 this type on devices running {@link android.os.Build.VERSION_CODES#UPSIDE_DOWN_CAKE} 1654 is still allowed, but calling it with this type on devices running future platform 1655 releases may get a {@link android.app.InvalidForegroundServiceTypeException}. 1656 --> 1657 <flag name="dataSync" value="0x01" /> 1658 <!-- Music, video, news or other media play. 1659 1660 <p>For apps with <code>targetSdkVersion</code> 1661 {@link android.os.Build.VERSION_CODES#UPSIDE_DOWN_CAKE} and above, starting a foreground 1662 service with this type will require permission 1663 {@link android.Manifest.permission#FOREGROUND_SERVICE_MEDIA_PLAYBACK}. 1664 --> 1665 <flag name="mediaPlayback" value="0x02" /> 1666 <!-- Ongoing operations related to phone calls, video conferencing, 1667 or similar interactive communication. 1668 1669 <p>For apps with <code>targetSdkVersion</code> 1670 {@link android.os.Build.VERSION_CODES#UPSIDE_DOWN_CAKE} and above, starting a foreground 1671 service with this type will require permission 1672 {@link android.Manifest.permission#FOREGROUND_SERVICE_PHONE_CALL} and 1673 {@link android.Manifest.permission#MANAGE_OWN_CALLS} or holding the default 1674 {@link android.app.role.RoleManager#ROLE_DIALER dialer role}. 1675 --> 1676 <flag name="phoneCall" value="0x04" /> 1677 <!-- GPS, map, navigation location update. 1678 1679 <p>For apps with <code>targetSdkVersion</code> 1680 {@link android.os.Build.VERSION_CODES#UPSIDE_DOWN_CAKE} and above, starting a foreground 1681 service with this type will require permission 1682 {@link android.Manifest.permission#FOREGROUND_SERVICE_LOCATION} and one of the 1683 following permissions: 1684 {@link android.Manifest.permission#ACCESS_COARSE_LOCATION}, 1685 {@link android.Manifest.permission#ACCESS_FINE_LOCATION}. 1686 --> 1687 <flag name="location" value="0x08" /> 1688 <!-- Auto, bluetooth, TV or other devices connection, monitoring and interaction. 1689 1690 <p>For apps with <code>targetSdkVersion</code> 1691 {@link android.os.Build.VERSION_CODES#UPSIDE_DOWN_CAKE} and above, starting a foreground 1692 service with this type will require permission 1693 {@link android.Manifest.permission#FOREGROUND_SERVICE_CONNECTED_DEVICE} and one of the 1694 following permissions: 1695 {@link android.Manifest.permission#BLUETOOTH_CONNECT}, 1696 {@link android.Manifest.permission#CHANGE_NETWORK_STATE}, 1697 {@link android.Manifest.permission#CHANGE_WIFI_STATE}, 1698 {@link android.Manifest.permission#CHANGE_WIFI_MULTICAST_STATE}, 1699 {@link android.Manifest.permission#NFC}, 1700 {@link android.Manifest.permission#TRANSMIT_IR}, 1701 or has been granted the access to one of the attached USB devices/accessories. 1702 --> 1703 <flag name="connectedDevice" value="0x10" /> 1704 <!-- Managing a {@link android.media.projection.MediaProjection MediaProjection} session, 1705 e.g., for screen recording or takingscreenshots. 1706 1707 <p> 1708 To capture through {@link android.media.projection.MediaProjection}, an app must start 1709 a foreground service with the type corresponding to this constant. This type should 1710 only be used for {@link android.media.projection.MediaProjection}. Capturing screen 1711 contents via 1712 {@link android.media.projection.MediaProjection#createVirtualDisplay(String, int, int, 1713 int, int, android.view.Surface, android.hardware.display.VirtualDisplay.Callback, 1714 android.os.Handler) createVirtualDisplay} conveniently allows recording, presenting 1715 screen contents into a meeting, taking screenshots, or several other scenarios. 1716 </p> 1717 1718 <p>For apps with <code>targetSdkVersion</code> 1719 {@link android.os.Build.VERSION_CODES#UPSIDE_DOWN_CAKE} and above, starting a 1720 foreground service with this type will require permission 1721 {@link android.Manifest.permission#FOREGROUND_SERVICE_MEDIA_PROJECTION}, and the user 1722 must have allowed the screen capture request from this app. 1723 --> 1724 <flag name="mediaProjection" value="0x20" /> 1725 <!-- Use the camera device or record video. 1726 1727 <p>For apps with <code>targetSdkVersion</code> {@link android.os.Build.VERSION_CODES#R} 1728 and above, a foreground service will not be able to access the camera if this type is 1729 not specified in the manifest and in 1730 {@link android.app.Service#startForeground(int, android.app.Notification, int)}. 1731 1732 <p>For apps with <code>targetSdkVersion</code> 1733 {@link android.os.Build.VERSION_CODES#UPSIDE_DOWN_CAKE} and above, starting a foreground 1734 service with this type will require permission 1735 {@link android.Manifest.permission#FOREGROUND_SERVICE_CAMERA} and 1736 {@link android.Manifest.permission#CAMERA}. 1737 --> 1738 <flag name="camera" value="0x40" /> 1739 <!--Use the microphone device or record audio. 1740 1741 <p>For apps with <code>targetSdkVersion</code> {@link android.os.Build.VERSION_CODES#R} 1742 and above, a foreground service will not be able to access the microphone if this type 1743 is not specified in the manifest and in 1744 {@link android.app.Service#startForeground(int, android.app.Notification, int)}. 1745 1746 <p>For apps with <code>targetSdkVersion</code> 1747 {@link android.os.Build.VERSION_CODES#UPSIDE_DOWN_CAKE} and above, starting a foreground 1748 service with this type will require permission 1749 {@link android.Manifest.permission#FOREGROUND_SERVICE_MICROPHONE} and one of the 1750 following permissions: 1751 {@link android.Manifest.permission#CAPTURE_AUDIO_OUTPUT}, 1752 {@link android.Manifest.permission#RECORD_AUDIO}. 1753 --> 1754 <flag name="microphone" value="0x80" /> 1755 <!--Health, wellness and fitness. 1756 <p>Requires the app to hold the permission 1757 {@link android.Manifest.permission#FOREGROUND_SERVICE_HEALTH} and one of the following 1758 permissions 1759 {@link android.Manifest.permission#ACTIVITY_RECOGNITION}, 1760 {@link android.Manifest.permission#BODY_SENSORS}, 1761 {@link android.Manifest.permission#HIGH_SAMPLING_RATE_SENSORS}. 1762 --> 1763 <flag name="health" value="0x100" /> 1764 <!-- Messaging use cases which host local server to relay messages across devices. 1765 <p>Requires the app to hold the permission 1766 {@link android.Manifest.permission#FOREGROUND_SERVICE_REMOTE_MESSAGING} in order to use 1767 this type. 1768 --> 1769 <flag name="remoteMessaging" value="0x200" /> 1770 <!-- The system exempted foreground service use cases. 1771 <p>Requires the app to hold the permission 1772 {@link android.Manifest.permission#FOREGROUND_SERVICE_SYSTEM_EXEMPTED} in order to use 1773 this type. Apps are allowed to use this type only in the use cases listed in 1774 {@link android.content.pm.ServiceInfo#FOREGROUND_SERVICE_TYPE_SYSTEM_EXEMPTED}. 1775 --> 1776 <flag name="systemExempted" value="0x400" /> 1777 <!-- "Short service" foreground service type. See 1778 {@link android.content.pm.ServiceInfo#FOREGROUND_SERVICE_TYPE_SHORT_SERVICE}. 1779 for more details. 1780 --> 1781 <flag name="shortService" value="0x800" /> 1782 <!-- The file management use case which manages files/directories, often involving file I/O 1783 across the file system. 1784 <p>Requires the app to hold the permission 1785 {@link android.Manifest.permission#FOREGROUND_SERVICE_FILE_MANAGEMENT} in order to use 1786 this type. 1787 1788 TODO: b/258855262 mark this field as {@code hide} once this bug is fixed. 1789 <flag name="fileManagement" value="0x1000" /> 1790 --> 1791 <!-- Media processing use cases such as video or photo editing and processing. 1792 <p>Requires the app to hold the permission 1793 {@link android.Manifest.permission#FOREGROUND_SERVICE_MEDIA_PROCESSING} in order to use 1794 this type. 1795 --> 1796 <flag name="mediaProcessing" value="0x2000" /> 1797 <!-- Use cases that can't be categorized into any other foreground service types, but also 1798 can't use @link android.app.job.JobInfo.Builder} APIs. 1799 See {@link android.content.pm.ServiceInfo#FOREGROUND_SERVICE_TYPE_SPECIAL_USE} for the 1800 best practice of the use of this type. 1801 1802 <p>Requires the app to hold the permission 1803 {@link android.Manifest.permission#FOREGROUND_SERVICE_SPECIAL_USE} in order to use 1804 this type. 1805 --> 1806 <flag name="specialUse" value="0x40000000" /> 1807 </attr> 1808 1809 <!-- Enable sampled memory bug detection in this process. 1810 When enabled, a very small, random subset of native 1811 memory allocations are protected with guard pages, providing an 1812 ASan-like error report in case of a memory corruption bug. 1813 1814 GWP-ASan is a recursive acronym. It stands for “GWP-ASan Will Provide Allocation SANity”. 1815 See the <a href="http://llvm.org/docs/GwpAsan.html">LLVM documentation</a> 1816 for more information about this feature. 1817 1818 <p>This attribute can be applied to a 1819 {@link android.R.styleable#AndroidManifestProcess process} tag, or to an 1820 {@link android.R.styleable#AndroidManifestApplication application} tag (to supply 1821 a default setting for all application components). --> 1822 <attr name="gwpAsanMode"> 1823 <!-- Default behavior: GwpAsan is disabled in user apps, randomly enabled in system apps. --> 1824 <enum name="default" value="-1" /> 1825 <!-- Never enable GwpAsan. --> 1826 <enum name="never" value="0" /> 1827 <!-- Always enable GwpAsan. --> 1828 <enum name="always" value="1" /> 1829 </attr> 1830 1831 <!-- Enable hardware memory tagging (ARM MTE) in this process. 1832 When enabled, heap memory bugs like use-after-free and buffer overflow 1833 are detected and result in an immediate ("sync" mode) or delayed ("async" 1834 mode) crash instead of a silent memory corruption. Sync mode, while slower, 1835 provides enhanced bug reports including stack traces at the time of allocation 1836 and deallocation of memory, similar to AddressSanitizer. 1837 1838 See the <a href="https://community.arm.com/developer/ip-products/processors/b/processors-ip-blog/posts/enhancing-memory-safety">ARM announcement</a> 1839 for more details. 1840 1841 <p>This attribute can be applied to a 1842 {@link android.R.styleable#AndroidManifestProcess process} tag, or to an 1843 {@link android.R.styleable#AndroidManifestApplication application} tag (to supply 1844 a default setting for all application components). --> 1845 <attr name="memtagMode"> 1846 <enum name="default" value="-1" /> 1847 <enum name="off" value="0" /> 1848 <enum name="async" value="1" /> 1849 <enum name="sync" value="2" /> 1850 </attr> 1851 1852 <!-- Attribution tag to be used for permission sub-attribution if a 1853 permission is checked in {@link android.content.Context#sendBroadcast(Intent, String)}. 1854 Multiple tags can be specified separated by '|'. 1855 --> 1856 <attr name="attributionTags" format="string" /> 1857 1858 <attr name="allowUpdateOwnership" format="boolean" /> 1859 1860 <!-- This attribute can be applied to any tag in the manifest. The system uses its value to 1861 determine whether the element (e.g., a permission) should be enabled or disabled 1862 depending on the state of feature flags. 1863 @hide @SystemApi @FlaggedApi("android.content.res.manifest_flagging") --> 1864 <attr name="featureFlag" format="string" /> 1865 1866 <!-- The <code>manifest</code> tag is the root of an 1867 <code>AndroidManifest.xml</code> file, 1868 describing the contents of an Android package (.apk) file. One 1869 attribute must always be supplied: <code>package</code> gives a 1870 unique name for the package, using a Java-style naming convention 1871 to avoid name collisions. For example, applications published 1872 by Google could have names of the form 1873 <code>com.google.app.<em>appname</em></code> 1874 1875 <p>Inside of the manifest tag, may appear the following tags 1876 in any order: {@link #AndroidManifestAttribution attribution}, 1877 {@link #AndroidManifestPermission permission}, 1878 {@link #AndroidManifestPermissionGroup permission-group}, 1879 {@link #AndroidManifestPermissionTree permission-tree}, 1880 {@link #AndroidManifestUsesSdk uses-sdk}, 1881 {@link #AndroidManifestUsesPermission uses-permission}, 1882 {@link #AndroidManifestUsesConfiguration uses-configuration}, 1883 {@link #AndroidManifestApplication application}, 1884 {@link #AndroidManifestInstrumentation instrumentation}, 1885 {@link #AndroidManifestUsesFeature uses-feature}. --> 1886 <declare-styleable name="AndroidManifest"> 1887 <attr name="versionCode" /> 1888 <attr name="versionCodeMajor" /> 1889 <attr name="versionName" /> 1890 <attr name="revisionCode" /> 1891 <attr name="sharedUserId" /> 1892 <attr name="sharedUserLabel" /> 1893 <attr name="sharedUserMaxSdkVersion" /> 1894 <attr name="installLocation" /> 1895 <attr name="isolatedSplits" /> 1896 <attr name="isFeatureSplit" /> 1897 <attr name="targetSandboxVersion" /> 1898 <attr name="compileSdkVersion" /> 1899 <attr name="compileSdkVersionCodename" /> 1900 <attr name="isSplitRequired" /> 1901 <attr name="requiredSplitTypes" /> 1902 <attr name="splitTypes" /> 1903 </declare-styleable> 1904 1905 <!-- The <code>application</code> tag describes application-level components 1906 contained in the package, as well as general application 1907 attributes. Many of the attributes you can supply here (such 1908 as theme, label, icon, permission, process, taskAffinity, 1909 and allowTaskReparenting) serve 1910 as default values for the corresponding attributes of components 1911 declared inside of the application. 1912 1913 <p>Inside of this element you specify what the application contains, 1914 using the elements {@link #AndroidManifestProvider provider}, 1915 {@link #AndroidManifestService service}, 1916 {@link #AndroidManifestReceiver receiver}, 1917 {@link #AndroidManifestActivity activity}, 1918 {@link #AndroidManifestActivityAlias activity-alias}, 1919 {@link #AndroidManifestUsesLibrary uses-library}, 1920 {@link #AndroidManifestUsesStaticLibrary uses-static-library}, and 1921 {@link #AndroidManifestUsesPackage uses-package}. 1922 The application tag 1923 appears as a child of the root {@link #AndroidManifest manifest} tag in 1924 an application's manifest file. --> 1925 <declare-styleable name="AndroidManifestApplication" parent="AndroidManifest"> 1926 <!-- The (optional) fully-qualified name for a subclass of 1927 {@link android.app.Application} that the system instantiates before 1928 any other class when an app's process starts. Most applications 1929 don't need this attribute. If it's not specified, the system 1930 instantiates the base Application class instead.--> 1931 <attr name="name" /> 1932 <attr name="theme" /> 1933 <attr name="label" /> 1934 <attr name="icon" /> 1935 <attr name="roundIcon" /> 1936 <attr name="banner" /> 1937 <attr name="logo" /> 1938 <attr name="description" /> 1939 <attr name="permission" /> 1940 <attr name="process" /> 1941 <attr name="taskAffinity" /> 1942 <attr name="allowTaskReparenting" /> 1943 <!-- Indicate whether this application contains code. If set to false, 1944 there is no code associated with it and thus the system will not 1945 try to load its code when launching components. The default is true 1946 for normal behavior. --> 1947 <attr name="hasCode" format="boolean" /> 1948 <!-- Specifies if activities can be launched on top of this application by activities from 1949 other applications in the same task. If set to false, activity launches which would 1950 replace this application with another when in the user's view will be blocked. 1951 The default is true. --> 1952 <!-- @FlaggedApi("android.security.asm_restrictions_enabled") --> 1953 <attr name="allowCrossUidActivitySwitchFromBelow" format="boolean" /> 1954 <attr name="persistent" /> 1955 <attr name="persistentWhenFeatureAvailable" /> 1956 <attr name="requiredForAllUsers" /> 1957 <!-- Specify whether the components in this application are enabled or not (that is, can be 1958 instantiated by the system). 1959 If "false", it overrides any component specific values (a value of "true" will not 1960 override the component specific values). --> 1961 <attr name="enabled" /> 1962 <attr name="debuggable" /> 1963 <attr name="vmSafeMode" /> 1964 <attr name="hardwareAccelerated" /> 1965 <!-- Name of activity to be launched for managing the application's space on the device. --> 1966 <attr name="manageSpaceActivity" /> 1967 <attr name="allowClearUserData" /> 1968 <attr name="testOnly" /> 1969 <attr name="backupAgent" /> 1970 <attr name="allowBackup" /> 1971 <attr name="fullBackupOnly" /> 1972 <attr name="fullBackupContent" /> 1973 <attr name="killAfterRestore" /> 1974 <attr name="restoreNeedsApplication" /> 1975 <attr name="restoreAnyVersion" /> 1976 <attr name="backupInForeground" /> 1977 <!-- Request that your application's processes be created with 1978 a large Dalvik heap. This applies to <em>all</em> processes 1979 created for the application. It only applies to the first 1980 application loaded into a process; if using a sharedUserId 1981 to allow multiple applications to use a process, they all must 1982 use this option consistently or will get unpredictable results. --> 1983 <attr name="largeHeap" format="boolean" /> 1984 <!-- Declare that this application can't participate in the normal 1985 state save/restore mechanism. Since it is not able to save and 1986 restore its state on demand, 1987 it can not participate in the normal activity lifecycle. It will 1988 not be killed while in the background; the user must explicitly 1989 quit it. Only one such app can be running at a time; if the user 1990 tries to launch a second such app, they will be prompted 1991 to quit the first before doing so. While the 1992 application is running, the user will be informed of this. --> 1993 <attr name="cantSaveState" format="boolean" /> 1994 <attr name="uiOptions" /> 1995 <!-- Declare that your application will be able to deal with RTL (right to left) layouts. 1996 The default value is false. --> 1997 <attr name="supportsRtl" format="boolean" /> 1998 <!-- Declare that this application requires access to restricted accounts of a certain 1999 type. The default value is null and restricted accounts won\'t be visible to this 2000 application. The type should correspond to the account authenticator type, such as 2001 "com.google". --> 2002 <attr name="restrictedAccountType" format="string"/> 2003 <!-- Declare that this application requires an account of a certain 2004 type. The default value is null and indicates that the application can work without 2005 any accounts. The type should correspond to the account authenticator type, such as 2006 "com.google". --> 2007 <attr name="requiredAccountType" format="string"/> 2008 <!-- @deprecated replaced by setting appCategory attribute to "game" --> 2009 <attr name="isGame" /> 2010 <!-- Declare that this application may use cleartext traffic, such as HTTP rather than 2011 HTTPS; WebSockets rather than WebSockets Secure; XMPP, IMAP, SMTP without STARTTLS or 2012 TLS). Defaults to true. If set to false {@code false}, the application declares that it 2013 does not intend to use cleartext network traffic, in which case platform components 2014 (e.g. HTTP stacks, {@code DownloadManager}, {@code MediaPlayer}) will refuse 2015 applications's requests to use cleartext traffic. Third-party libraries are encouraged 2016 to honor this flag as well. --> 2017 <attr name="usesCleartextTraffic" /> 2018 <attr name="multiArch" /> 2019 <attr name="useEmbeddedDex" /> 2020 <attr name="extractNativeLibs" /> 2021 <attr name="defaultToDeviceProtectedStorage" format="boolean" /> 2022 <attr name="directBootAware" /> 2023 <attr name="resizeableActivity" /> 2024 <attr name="maxAspectRatio" /> 2025 <attr name="minAspectRatio" /> 2026 <attr name="networkSecurityConfig" /> 2027 <attr name="localeConfig" /> 2028 <!-- Declare the category of this app. Categories are used to cluster multiple apps 2029 together into meaningful groups, such as when summarizing battery, network, or 2030 disk usage. Apps should only define this value when they fit well into one of 2031 the specific categories. --> 2032 <attr name="appCategory"> 2033 <!-- Apps which are primarily games. --> 2034 <enum name="game" value="0" /> 2035 <!-- Apps which primarily work with audio or music, such as music players. --> 2036 <enum name="audio" value="1" /> 2037 <!-- Apps which primarily work with video or movies, such as streaming video apps. --> 2038 <enum name="video" value="2" /> 2039 <!-- Apps which primarily work with images or photos, such as camera or gallery apps. --> 2040 <enum name="image" value="3" /> 2041 <!-- Apps which are primarily social apps, such as messaging, communication, email, or social network apps. --> 2042 <enum name="social" value="4" /> 2043 <!-- Apps which are primarily news apps, such as newspapers, magazines, or sports apps. --> 2044 <enum name="news" value="5" /> 2045 <!-- Apps which are primarily maps apps, such as navigation apps. --> 2046 <enum name="maps" value="6" /> 2047 <!-- Apps which are primarily productivity apps, such as cloud storage or workplace apps. --> 2048 <enum name="productivity" value="7" /> 2049 <!-- Apps which are primarily accessibility apps, such as screen-readers. --> 2050 <enum name="accessibility" value="8" /> 2051 </attr> 2052 2053 <!-- Declares the kind of classloader this application's classes must be loaded with --> 2054 <attr name="classLoader" /> 2055 2056 <attr name="appComponentFactory" /> 2057 2058 <!-- Declares that this application should be invoked without non-SDK API enforcement --> 2059 <attr name="usesNonSdkApi" /> 2060 2061 <!-- If {@code true} the user is prompted to keep the app's data on uninstall --> 2062 <attr name="hasFragileUserData" format="boolean"/> 2063 2064 <attr name="zygotePreloadName" /> 2065 2066 <!-- If {@code true} the system will clear app's data if a restore operation fails. 2067 This flag is turned on by default. <em>This attribute is usable only by system apps. 2068 </em> --> 2069 <attr name="allowClearUserDataOnFailedRestore" format="boolean"/> 2070 <!-- If {@code true} the app's non sensitive audio can be captured by other apps with 2071 {@link android.media.AudioPlaybackCaptureConfiguration} and a 2072 {@link android.media.projection.MediaProjection}. 2073 2074 If {@code false} the audio played by the application will never be captured by non 2075 system apps. It is equivalent to limiting 2076 {@link android.media.AudioManager#setAllowedCapturePolicy(int)} to 2077 {@link android.media.AudioAttributes#ALLOW_CAPTURE_BY_SYSTEM}. 2078 2079 <p> 2080 Non sensitive audio is defined as audio whose {@code AttributeUsage} is 2081 {@code USAGE_UNKNOWN}), {@code USAGE_MEDIA}) or {@code USAGE_GAME}). 2082 All other usages like {@code USAGE_VOICE_COMMUNICATION} will not be captured. 2083 2084 <p> 2085 The default value is: 2086 - {@code true} for apps with targetSdkVersion >= 29 (Q). 2087 - {@code false} for apps with targetSdkVersion < 29. 2088 2089 <p> 2090 See {@link android.media.AudioPlaybackCaptureConfiguration} for more detail. 2091 --> 2092 <attr name="allowAudioPlaybackCapture" format="boolean" /> 2093 <!-- If {@code true} this app would like to run under the legacy storage 2094 model. Note that this may not always be respected due to policy or 2095 backwards compatibility reasons. 2096 2097 <p>Apps not requesting legacy storage can continue to discover and 2098 read media belonging to other apps via {@code MediaStore}. 2099 <p> 2100 The default value is: 2101 - {@code false} for apps with targetSdkVersion >= 29 (Q). 2102 - {@code true} for apps with targetSdkVersion < 29. 2103 --> 2104 <attr name="requestLegacyExternalStorage" format="boolean" /> 2105 2106 <!-- If {@code true} this app would like to preserve the legacy storage 2107 model from a previously installed version. Note that this may not always be 2108 respected due to policy or backwards compatibility reasons. 2109 2110 <p>This has no effect on the first install of an app on a device. 2111 For an updating app, setting this to {@code true} will preserve the legacy behaviour 2112 configured by the {@code requestLegacyExternalStorage} flag. If on an update, this 2113 flag is set to {@code false} then the legacy access is not preserved, such an app can 2114 only have legacy access with the {@code requestLegacyExternalStorage} flag. 2115 <p> 2116 2117 The default value is {@code false}. 2118 --> 2119 <attr name="preserveLegacyExternalStorage" format="boolean" /> 2120 2121 <!-- If {@code true} this app would like raw external storage access. 2122 2123 <p> This flag can only be used by apps holding 2124 <ul> 2125 <li>{@link android.Manifest.permission#MANAGE_EXTERNAL_STORAGE} permission or 2126 <li>{@link android.app.role}#SYSTEM_GALLERY role. 2127 </ul> 2128 <p> When the flag is set, all file path access on external storage will bypass database 2129 operations that update MediaStore collection. Raw external storage access as a side effect 2130 can improve performance of bulk file path operations but can cause unexpected behavior in 2131 apps due to inconsistencies in MediaStore collection and lower file system. 2132 When the flag is set, app should scan the file after file path operations to ensure 2133 consistency of MediaStore collection. 2134 <p> The flag can be set to false if the app doesn't do many bulk file path operations or if 2135 app prefers the system to ensure the consistency of the MediaStore collection for file path 2136 operations without scanning the file. 2137 2138 <p> The default value is {@code true} if 2139 <ul> 2140 <li>app has {@link android.Manifest.permission#MANAGE_EXTERNAL_STORAGE} permission and 2141 targets targetSDK<=30. 2142 <li>app has {@link android.app.role}#SYSTEM_GALLERY role and targetSDK<=29 2143 </ul> 2144 {@code false} otherwise. 2145 --> 2146 <attr name="requestRawExternalStorageAccess" format="boolean" /> 2147 2148 <!-- If {@code true} this app declares that it should be visible to all other apps on 2149 device, regardless of what they declare via the {@code queries} tags in their 2150 manifest. 2151 2152 The default value is {@code false}. --> 2153 <attr name="forceQueryable" format="boolean" /> 2154 2155 <!-- If {@code true} indicates that this application is capable of presenting a unified 2156 interface representing multiple profiles. 2157 2158 The default value is {@code false}. --> 2159 <attr name="crossProfile" format="boolean" /> 2160 2161 <!-- If {@code true} this app will receive tagged pointers to native heap allocations 2162 from functions like malloc() on compatible devices. Note that this may not always 2163 be respected due to policy or backwards compatibility reasons. See the 2164 <a href="https://source.android.com/devices/tech/debug/tagged-pointers">Tagged Pointers</a> 2165 document for more information on this feature. 2166 2167 The default value is {@code true}. --> 2168 <attr name="allowNativeHeapPointerTagging" format="boolean" /> 2169 2170 <attr name="gwpAsanMode" /> 2171 2172 <attr name="memtagMode" /> 2173 2174 <!-- If {@code true} enables automatic zero initialization of all native heap 2175 allocations. --> 2176 <attr name="nativeHeapZeroInitialized" format="boolean" /> 2177 2178 <!-- @hide no longer used, kept to preserve padding --> 2179 <attr name="allowAutoRevokePermissionsExemption" format="boolean" /> 2180 2181 <!-- No longer used. Declaring this does nothing --> 2182 <attr name="autoRevokePermissions"> 2183 <!-- No longer used --> 2184 <enum name="allowed" value="0" /> 2185 <!-- No longer used --> 2186 <enum name="discouraged" value="1" /> 2187 <!-- No longer used --> 2188 <enum name="disallowed" value="2" /> 2189 </attr> 2190 2191 <!-- Declare the policy to deal with user data when rollback is committed. --> 2192 <attr name="rollbackDataPolicy"> 2193 <!-- User data will be restored during rollback. --> 2194 <enum name="restore" value="0" /> 2195 <!-- User data will be wiped out during rollback. --> 2196 <enum name="wipe" value="1" /> 2197 <!-- User data will remain unchanged during rollback. --> 2198 <enum name="retain" value="2" /> 2199 </attr> 2200 2201 <!-- Applications can set this attribute to an xml resource within their app where they 2202 specified the rules determining which files and directories can be copied from the device 2203 as part of backup or transfer operations. 2204 2205 See the <a href="{@docRoot}about/versions/12/backup-restore">Changes in backup and restore</a> 2206 document for the format of the XML file.--> 2207 <attr name="dataExtractionRules" format="reference"/> 2208 2209 <!-- @hide Request exemption from the foreground service restrictions introduced in S 2210 (https://developer.android.com/about/versions/12/foreground-services) 2211 Note the framework <b>ignores</b> this attribute at this time. Once apps target S or above, 2212 there's no way to be exempted (without using a privileged permission). 2213 --> 2214 <attr name="requestForegroundServiceExemption" format="boolean" /> 2215 2216 <!-- Whether attributions provided are meant to be user-visible. --> 2217 <attr name="attributionsAreUserVisible" format="boolean" /> 2218 2219 <!-- Specifies whether enabled settings of components in the application should be 2220 reset to {@link android.content.pm.PackageManager#COMPONENT_ENABLED_STATE_DEFAULT} 2221 when the application's user data is cleared. The default value is false. 2222 --> 2223 <attr name="resetEnabledSettingsOnAppDataCleared" format="boolean" /> 2224 <attr name="knownActivityEmbeddingCerts" /> 2225 2226 <!-- If false, {@link android.view.KeyEvent#KEYCODE_BACK KEYCODE_BACK} and 2227 {@link android.app.Activity#onBackPressed Activity.onBackPressed()} 2228 and related event will be forwarded to the Activities and View, otherwise those events 2229 will be replaced by a call to 2230 {@link android.window.OnBackInvokedCallback#onBackInvoked 2231 OnBackInvokedCallback.onBackInvoked()} on the focused window. --> 2232 <attr name="enableOnBackInvokedCallback" format="boolean"/> 2233 </declare-styleable> 2234 2235 <!-- An attribution is a logical part of an app and is identified by a tag. 2236 E.g. a photo sharing app might include a direct messaging component. To tag certain code as 2237 belonging to an attribution, use a context created via 2238 {@link android.content.Context#createAttributionContext(String)} for any interaction with the 2239 system. 2240 2241 <p>This appears as a child tag of the root {@link #AndroidManifest manifest} tag. 2242 2243 <p>In case this attribution inherits from another attribution, this tag can contain one or 2244 multiple {@link #AndroidManifestAttributionInheritFrom inherit-from} tags. --> 2245 <declare-styleable name="AndroidManifestAttribution" parent="AndroidManifest"> 2246 <!-- Required identifier for a attribution. Can be passed to 2247 {@link android.content.Context#createAttributionContext} to create a context tagged with 2248 this attribution 2249 --> 2250 <attr name="tag" format="string" /> 2251 <!-- Required user visible label for a attribution. --> 2252 <attr name="label" format="string" /> 2253 </declare-styleable> 2254 2255 <!-- Declares previously declared attributions this attribution inherits from. --> 2256 <declare-styleable name="AndroidManifestAttributionInheritFrom" 2257 parent="AndroidManifestAttribution"> 2258 <!-- Identifier of the attribution this attribution inherits from --> 2259 <attr name="tag" format="string" /> 2260 </declare-styleable> 2261 2262 <!-- The <code>permission</code> tag declares a security permission that can be 2263 used to control access from other packages to specific components or 2264 features in your package (or other packages). See the 2265 <a href="{@docRoot}guide/topics/security/security.html">Security and Permissions</a> 2266 document for more information on permissions. 2267 2268 <p>This appears as a child tag of the root 2269 {@link #AndroidManifest manifest} tag. --> 2270 <declare-styleable name="AndroidManifestPermission" parent="AndroidManifest"> 2271 <!-- Required public name of the permission, which other components and 2272 packages will use when referring to this permission. This is a string using 2273 Java-style scoping to ensure it is unique. The prefix will often 2274 be the same as our overall package name, for example 2275 "com.mycompany.android.myapp.SomePermission". --> 2276 <attr name="name" /> 2277 <attr name="label" /> 2278 <attr name="icon" /> 2279 <attr name="roundIcon" /> 2280 <attr name="banner" /> 2281 <attr name="logo" /> 2282 <attr name="permissionGroup" /> 2283 <attr name="backgroundPermission" format="string"/> 2284 <attr name="description" /> 2285 <attr name="request" /> 2286 <attr name="protectionLevel" /> 2287 <attr name="permissionFlags" /> 2288 <attr name="knownCerts" /> 2289 <!-- Optional: specify the maximum version of the Android OS for which the 2290 application wishes to create the permission. When running on a version 2291 of Android higher than the number given here, the permission will not 2292 be created. --> 2293 <attr name="maxSdkVersion" /> 2294 </declare-styleable> 2295 2296 <!-- The <code>permission-group</code> tag declares a logical grouping of 2297 related permissions. 2298 2299 <p>Note that this tag does not declare a permission itself, only 2300 a namespace in which further permissions can be placed. See 2301 the {@link #AndroidManifestPermission <permission>} tag for 2302 more information. 2303 2304 <p>This appears as a child tag of the root 2305 {@link #AndroidManifest manifest} tag. --> 2306 <declare-styleable name="AndroidManifestPermissionGroup" parent="AndroidManifest"> 2307 <!-- Required public name of the permission group, permissions will use 2308 to specify the group they are in. This is a string using 2309 Java-style scoping to ensure it is unique. The prefix will often 2310 be the same as our overall package name, for example 2311 "com.mycompany.android.myapp.SomePermission". --> 2312 <attr name="name" /> 2313 <attr name="label" /> 2314 <attr name="icon" /> 2315 <attr name="roundIcon" /> 2316 <attr name="banner" /> 2317 <attr name="logo" /> 2318 <attr name="description" /> 2319 <attr name="request" format="string"/> 2320 <attr name="requestDetail" format="string"/> 2321 <attr name="backgroundRequest" format="string"/> 2322 <attr name="backgroundRequestDetail" format="string"/> 2323 <attr name="permissionGroupFlags" /> 2324 <attr name="priority" /> 2325 </declare-styleable> 2326 2327 <!-- The <code>permission-tree</code> tag declares the base of a tree of 2328 permission values: it declares that this package has ownership of 2329 the given permission name, as well as all names underneath it 2330 (separated by '.'). This allows you to use the 2331 {@link android.content.pm.PackageManager#addPermission 2332 PackageManager.addPermission()} method to dynamically add new 2333 permissions under this tree. 2334 2335 <p>Note that this tag does not declare a permission itself, only 2336 a namespace in which further permissions can be placed. See 2337 the {@link #AndroidManifestPermission <permission>} tag for 2338 more information. 2339 2340 <p>This appears as a child tag of the root 2341 {@link #AndroidManifest manifest} tag. --> 2342 <declare-styleable name="AndroidManifestPermissionTree" parent="AndroidManifest"> 2343 <!-- Required public name of the permission tree, which is the base name 2344 of all permissions under it. This is a string using 2345 Java-style scoping to ensure it is unique. The prefix will often 2346 be the same as our overall package name, for example 2347 "com.mycompany.android.myapp.SomePermission". A permission tree name 2348 must have more than two segments in its path; that is, 2349 "com.me.foo" is okay, but not "com.me" or "com". --> 2350 <attr name="name" /> 2351 <attr name="label" /> 2352 <attr name="icon" /> 2353 <attr name="roundIcon" /> 2354 <attr name="banner" /> 2355 <attr name="logo" /> 2356 </declare-styleable> 2357 2358 <!-- The <code>uses-permission</code> tag requests a 2359 {@link #AndroidManifestPermission <permission>} that the containing 2360 package must be granted in order for it to operate correctly. For runtime 2361 permissions, i.e. ones with <code>dangerous</code> protection level, on a 2362 platform that supports runtime permissions, the permission will not be 2363 granted until the app explicitly requests it at runtime and the user approves 2364 the grant. You cannot request at runtime permissions that are not declared 2365 as used in the manifest. See the 2366 <a href="{@docRoot}guide/topics/security/security.html">Security and Permissions</a> 2367 document for more information on permissions. Also available is a 2368 {@link android.Manifest.permission list of permissions} included 2369 with the base platform. 2370 2371 <p>This appears as a child tag of the root 2372 {@link #AndroidManifest manifest} tag. --> 2373 <declare-styleable name="AndroidManifestUsesPermission" parent="AndroidManifest"> 2374 <!-- Required name of the permission you use, as published with the 2375 corresponding name attribute of a 2376 {@link android.R.styleable#AndroidManifestPermission <permission>} 2377 tag; often this is one of the {@link android.Manifest.permission standard 2378 system permissions}. --> 2379 <attr name="name" /> 2380 <!-- Optional: specify the minimum version of the Android OS for which the 2381 application wishes to request the permission. When running on a version 2382 of Android lower than the number given here, the permission will not 2383 be requested. --> 2384 <attr name="minSdkVersion" format="integer|string" /> 2385 <!-- Optional: specify the maximum version of the Android OS for which the 2386 application wishes to request the permission. When running on a version 2387 of Android higher than the number given here, the permission will not 2388 be requested. --> 2389 <attr name="maxSdkVersion" format="integer" /> 2390 <!-- Optional: the system must support this feature for the permission to be 2391 requested. If it doesn't support the feature, it will be as if the manifest didn't 2392 request it at all. --> 2393 <attr name="requiredFeature" format="string" /> 2394 <!-- Optional: the system must NOT support this feature for the permission to be 2395 requested. If it does support the feature, it will be as if the manifest didn't 2396 request it at all. --> 2397 <attr name="requiredNotFeature" format="string" /> 2398 <!-- Optional: set of flags that should apply to this permission request. Note that 2399 these flags start at 0x4 to match PackageInfo.requestedPermissionsFlags. --> 2400 <attr name="usesPermissionFlags"> 2401 <!-- Strong assertion by a developer that they will never use this 2402 permission to derive the physical location of the device, even 2403 when the app has been granted the ACCESS_FINE_LOCATION and/or 2404 ACCESS_COARSE_LOCATION permissions. --> 2405 <flag name="neverForLocation" value="0x00010000" /> 2406 </attr> 2407 </declare-styleable> 2408 2409 <!-- <code>required-feature</code> and <code>required-not-feature</code> elements inside 2410 <code>uses-permission<code/> can be used to request the permission based on the fact 2411 whether the system supports or does not support certain features. 2412 If multiple <code>required-feature</code> and/or <code>required-not-feature</code> elements 2413 are present, the permission will be “requested” only if the system supports all of the 2414 listed "required-features" and does not support any of the "required-not-features". 2415 --> 2416 <declare-styleable name="AndroidManifestRequiredFeature"> 2417 <!-- The name of the feature. --> 2418 <attr name="name" /> 2419 </declare-styleable> 2420 <declare-styleable name="AndroidManifestRequiredNotFeature"> 2421 <!-- The name of the feature. --> 2422 <attr name="name" /> 2423 </declare-styleable> 2424 2425 <!-- The <code>uses-configuration</code> tag specifies 2426 a specific hardware configuration value used by the application. 2427 For example an application might specify that it requires 2428 a physical keyboard or a particular navigation method like 2429 trackball. Multiple such attribute values can be specified by the 2430 application. 2431 2432 <p>This appears as a child tag of the root 2433 {@link #AndroidManifest manifest} tag. 2434 2435 @deprecated Use <code>feature-group</code> instead.--> 2436 <declare-styleable name="AndroidManifestUsesConfiguration" parent="AndroidManifest"> 2437 <!-- The type of touch screen used by an application. --> 2438 <attr name="reqTouchScreen" /> 2439 <attr name="reqKeyboardType" /> 2440 <attr name="reqHardKeyboard" /> 2441 <attr name="reqNavigation" /> 2442 <attr name="reqFiveWayNav" /> 2443 </declare-styleable> 2444 2445 <!-- The <code>uses-feature</code> tag specifies a specific device 2446 hardware or software feature used by the application. For 2447 example an application might specify that it requires 2448 a camera. Multiple attribute values can be specified by the 2449 application. 2450 2451 <p>This appears as a child tag of the root 2452 {@link #AndroidManifest manifest} tag. --> 2453 <declare-styleable name="AndroidManifestUsesFeature" parent="AndroidManifest"> 2454 <!-- The name of the feature that is being used. --> 2455 <attr name="name" /> 2456 <!-- The version of the feature that is being used. --> 2457 <attr name="version" format="integer" /> 2458 <!-- The GLES driver version number needed by an application. 2459 The higher 16 bits represent the major number and the lower 16 bits 2460 represent the minor number. For example for GL 1.2 referring to 2461 0x00000102, the actual value should be set as 0x00010002. --> 2462 <attr name="glEsVersion" format="integer" /> 2463 <!-- Specify whether this feature is required for the application. 2464 The default is true, meaning the application requires the 2465 feature, and does not want to be installed on devices that 2466 don't support it. If you set this to false, then this will 2467 not impose a restriction on where the application can be 2468 installed. --> 2469 <attr name="required" format="boolean" /> 2470 </declare-styleable> 2471 2472 <!-- The <code>feature-group</code> tag specifies 2473 a set of one or more <code>uses-feature</code> elements that 2474 the application can utilize. An application uses multiple 2475 <code>feature-group</code> sets to indicate that it can support 2476 different combinations of features. 2477 2478 <p>This appears as a child tag of the root 2479 {@link #AndroidManifest manifest} tag. --> 2480 <declare-styleable name="AndroidManifestFeatureGroup"> 2481 <!-- The human-readable name of the feature group. --> 2482 <attr name="label" /> 2483 </declare-styleable> 2484 2485 <!-- The <code>uses-sdk</code> tag describes the SDK features that the 2486 containing package must be running on to operate correctly. 2487 2488 <p>This appears as a child tag of the root 2489 {@link #AndroidManifest manifest} tag. --> 2490 <declare-styleable name="AndroidManifestUsesSdk" parent="AndroidManifest"> 2491 <!-- This is the minimum SDK version number that the application 2492 requires. This number is an abstract integer, from the list 2493 in {@link android.os.Build.VERSION_CODES} If 2494 not supplied, the application will work on any SDK. This 2495 may also be string (such as "Donut") if the application was built 2496 against a development branch, in which case it will only work against 2497 the development builds. --> 2498 <attr name="minSdkVersion" format="integer|string" /> 2499 <!-- This is the SDK version number that the application is targeting. 2500 It is able to run on older versions (down to minSdkVersion), but 2501 was explicitly tested to work with the version specified here. 2502 Specifying this version allows the platform to disable compatibility 2503 code that are not required or enable newer features that are not 2504 available to older applications. This may also be a string 2505 (such as "Donut") if this is built against a development 2506 branch, in which case minSdkVersion is also forced to be that 2507 string. --> 2508 <attr name="targetSdkVersion" format="integer|string" /> 2509 <!-- This is the maximum SDK version number that an application works 2510 on. You can use this to ensure your application is filtered out 2511 of later versions of the platform when you know you have 2512 incompatibility with them. --> 2513 <attr name="maxSdkVersion" /> 2514 </declare-styleable> 2515 2516 <!-- The <code>extension-sdk</code> tag is a child of the <uses-sdk> tag, 2517 and specifies required extension sdk features. --> 2518 <declare-styleable name="AndroidManifestExtensionSdk"> 2519 <!-- The extension SDK version that this tag refers to. --> 2520 <attr name="sdkVersion" format="integer" /> 2521 <!-- The minimum version of the extension SDK this application requires.--> 2522 <attr name="minExtensionVersion" format="integer" /> 2523 </declare-styleable> 2524 2525 <!-- The <code>library</code> tag declares that this apk is providing itself 2526 as a shared library for other applications to use. It can only be used 2527 with apks that are built in to the system image. Other apks can link to 2528 it with the {@link #AndroidManifestUsesLibrary uses-library} tag. 2529 2530 <p>This appears as a child tag of the 2531 {@link #AndroidManifestApplication application} tag. --> 2532 <declare-styleable name="AndroidManifestLibrary" parent="AndroidManifest"> 2533 <!-- Required public name of the library, which other components and 2534 packages will use when referring to this library. This is a string using 2535 Java-style scoping to ensure it is unique. The name should typically 2536 be the same as the apk's package name. --> 2537 <attr name="name" /> 2538 </declare-styleable> 2539 2540 <declare-styleable name="AndroidManifestQueries" parent="AndroidManifest" /> 2541 <declare-styleable name="AndroidManifestQueriesPackage" parent="AndroidManifestQueries"> 2542 <attr name="name" /> 2543 </declare-styleable> 2544 <declare-styleable name="AndroidManifestQueriesIntent" parent="AndroidManifestQueries" /> 2545 <declare-styleable name="AndroidManifestQueriesProvider" parent="AndroidManifestQueries" > 2546 <attr name="authorities" /> 2547 </declare-styleable> 2548 2549 <!-- The <code>sdk-library</code> tag declares that this apk is providing itself 2550 as an SDK library for other applications to use. Any app can declare an SDK library and there 2551 can be only one SDK library per package. These SDK libraries are updatable, multiple major 2552 versions can be installed at the same time, and an app depends on a specific version. 2553 Other apks can link to it with the {@link #AndroidManifestUsesSdkLibrary uses-sdk-library} tag. 2554 2555 <p>This appears as a child tag of the {@link #AndroidManifestApplication application} tag. --> 2556 <declare-styleable name="AndroidManifestSdkLibrary" parent="AndroidManifestApplication"> 2557 <!-- Required public name of the SDK library, which other components and packages will use 2558 when referring to this SDK library. This is a string using Java-style scoping to ensure 2559 it is unique. 2560 Both name and version should typically form the apk's package name: name_versionMajor. --> 2561 <attr name="name" /> 2562 <!-- Required major version of the SDK library. --> 2563 <attr name="versionMajor" format="integer" /> 2564 </declare-styleable> 2565 2566 2567 <!-- The <code>uses-sdk-library</code> specifies a shared <strong>SDK</strong> library that this 2568 package requires to be present on the device. 2569 2570 <p>This appears as a child tag of the {@link #AndroidManifestApplication application} tag. --> 2571 <declare-styleable name="AndroidManifestUsesSdkLibrary" parent="AndroidManifestApplication"> 2572 <!-- Required name of the SDK library you use. --> 2573 <attr name="name" /> 2574 <!-- Specify which major version of the SDK library you use. --> 2575 <attr name="versionMajor" format="integer" /> 2576 <!-- The SHA-256 digest of the SDK library signing certificate. --> 2577 <attr name="certDigest" format="string" /> 2578 <!-- Specify whether the SDK is optional. The default is false, false means app can be 2579 installed even if the SDK library doesn't exist, and the SDK library can be uninstalled 2580 when the app is still installed. --> 2581 <attr name="optional" format="boolean" /> 2582 </declare-styleable> 2583 2584 <!-- The <code>static-library</code> tag declares that this apk is providing itself 2585 as a static shared library for other applications to use. Any app can declare such 2586 a library and there can be only one static shared library per package. These libraries 2587 are updatable, multiple versions can be installed at the same time, and an app links 2588 against a specific version simulating static linking while allowing code sharing. 2589 Other apks can link to it with the {@link #AndroidManifestUsesLibrary uses-static-library} 2590 tag. 2591 2592 <p>This appears as a child tag of the 2593 {@link #AndroidManifestApplication application} tag. --> 2594 <declare-styleable name="AndroidManifestStaticLibrary" parent="AndroidManifestApplication"> 2595 <!-- Required public name of the library, which other components and 2596 packages will use when referring to this library. This is a string using 2597 Java-style scoping to ensure it is unique. The name should typically 2598 be the same as the apk's package name. --> 2599 <attr name="name" /> 2600 <!-- Required specific library version. --> 2601 <attr name="version" /> 2602 <!-- Required specific library major version code. This matches 2603 android:versionCodeMajor of the library. --> 2604 <!-- Required specific library version. --> 2605 <attr name="versionMajor" format="integer" /> 2606 </declare-styleable> 2607 2608 <!-- The <code>uses-libraries</code> specifies a shared library that this 2609 package requires to be linked against. Specifying this flag tells the 2610 system to include this library's code in your class loader. 2611 2612 <p>This appears as a child tag of the 2613 {@link #AndroidManifestApplication application} tag. --> 2614 <declare-styleable name="AndroidManifestUsesLibrary" parent="AndroidManifestApplication"> 2615 <!-- Required name of the library you use. --> 2616 <attr name="name" /> 2617 <!-- Specify whether this library is required for the application. 2618 The default is true, meaning the application requires the 2619 library, and does not want to be installed on devices that 2620 don't support it. If you set this to false, then this will 2621 allow the application to be installed even if the library 2622 doesn't exist, and you will need to check for its presence 2623 dynamically at runtime. --> 2624 <attr name="required" /> 2625 </declare-styleable> 2626 2627 <!-- The <code>uses-native-library</code> specifies a native shared library that this 2628 package requires to be linked against. Specifying this flag tells the 2629 system to make the native library to be available to your app. 2630 2631 <p>On devices running R or lower, this is ignored and the app has access to all 2632 the public native shared libraries that are exported from the platform. This is 2633 also ignored if the app is targeting R or lower. 2634 2635 <p>This appears as a child tag of the 2636 {@link #AndroidManifestApplication application} tag. --> 2637 <declare-styleable name="AndroidManifestUsesNativeLibrary" parent="AndroidManifestApplication"> 2638 <!-- Required name of the library you use. --> 2639 <attr name="name" /> 2640 <!-- Specify whether this native library is required for the application. 2641 The default is true, meaning the application requires the 2642 library, and does not want to be installed on devices that 2643 don't support it. If you set this to false, then this will 2644 allow the application to be installed even if the library 2645 doesn't exist, and you will need to check for its presence 2646 dynamically at runtime. --> 2647 <attr name="required" /> 2648 </declare-styleable> 2649 2650 <!-- The <code>uses-static-library</code> specifies a shared <strong>static</strong> 2651 library that this package requires to be statically linked against. Specifying 2652 this tag tells the system to include this library's code in your class loader. 2653 Depending on a static shared library is equivalent to statically linking with 2654 the library at build time while it offers apps to share code defined in such 2655 libraries. Hence, static libraries are strictly required. 2656 2657 <p>On devices running O MR1 or higher, if the library is singed with multiple 2658 signing certificates you must to specify the SHA-256 hashes of the additional 2659 certificates via adding 2660 {@link #AndroidManifestAdditionalCertificate additional-certificate} tags. 2661 2662 <p>This appears as a child tag of the 2663 {@link #AndroidManifestApplication application} tag. --> 2664 <declare-styleable name="AndroidManifestUsesStaticLibrary" parent="AndroidManifestApplication"> 2665 <!-- Required name of the library you use. --> 2666 <attr name="name" /> 2667 <!-- Specify which version of the shared library should be statically linked. --> 2668 <attr name="version" /> 2669 <!-- The SHA-256 digest of the library signing certificate. --> 2670 <attr name="certDigest" format="string" /> 2671 </declare-styleable> 2672 2673 <!-- The <code>additional-certificate</code> specifies the SHA-256 digest of a static 2674 shared library's additional signing certificate. You need to use this tag if the 2675 library is singed with more than one certificate. 2676 2677 <p>This appears as a child tag of the 2678 {@link #AndroidManifestUsesStaticLibrary uses-static-library} or 2679 {@link #AndroidManifestUsesPackage uses-package} tag. --> 2680 <declare-styleable name="AndroidManifestAdditionalCertificate" parent="AndroidManifestUsesStaticLibrary"> 2681 <!-- The SHA-256 digest of the library signing certificate. --> 2682 <attr name="certDigest" /> 2683 </declare-styleable> 2684 2685 <!-- The <code>uses-package</code> specifies some kind of dependency on another 2686 package. It does not have any impact on the app's execution on the device, 2687 but provides information about dependencies it has on other packages that need 2688 to be satisfied for it to run correctly. That is, this is primarily for 2689 installers to know what other apps need to be installed along with this one. 2690 2691 <p>This appears as a child tag of the 2692 {@link #AndroidManifestApplication application} tag. --> 2693 <declare-styleable name="AndroidManifestUsesPackage" parent="AndroidManifestApplication"> 2694 <!-- Required type of association with the package, for example "android.package.ad_service" 2695 if it provides an advertising service. This should use the standard scoped naming 2696 convention as used for other things such as package names, based on the Java naming 2697 convention. --> 2698 <attr name="packageType" format="string" /> 2699 <!-- Required name of the package you use. --> 2700 <attr name="name" /> 2701 <!-- Optional minimum version of the package that satisfies the dependency. --> 2702 <attr name="version" /> 2703 <!-- Optional minimum major version of the package that satisfies the dependency. --> 2704 <attr name="versionMajor" format="integer" /> 2705 <!-- Optional SHA-256 digest of the package signing certificate. --> 2706 <attr name="certDigest" format="string" /> 2707 </declare-styleable> 2708 2709 <!-- The <code>supports-screens</code> specifies the screen dimensions an 2710 application supports. By default a modern application supports all 2711 screen sizes and must explicitly disable certain screen sizes here; 2712 older applications are assumed to only support the traditional normal 2713 (HVGA) screen size. Note that screen size is a separate axis from 2714 density, and is determined as the available pixels to an application 2715 after density scaling has been applied. 2716 2717 <p>This appears as a child tag of the 2718 {@link #AndroidManifest manifest} tag. --> 2719 <declare-styleable name="AndroidManifestSupportsScreens" parent="AndroidManifest"> 2720 <!-- Starting with {@link android.os.Build.VERSION_CODES#HONEYCOMB_MR2}, 2721 this is the new way to specify the minimum screen size an application is 2722 compatible with. This attribute provides the required minimum 2723 "smallest screen width" (as per the -swNNNdp resource configuration) 2724 that the application can run on. For example, a typical phone 2725 screen is 320, a 7" tablet 600, and a 10" tablet 720. If the 2726 smallest screen width of the device is below the value supplied here, 2727 then the application is considered incompatible with that device. 2728 If not supplied, then any old smallScreens, normalScreens, largeScreens, 2729 or xlargeScreens attributes will be used instead. --> 2730 <attr name="requiresSmallestWidthDp" format="integer" /> 2731 <!-- Starting with {@link android.os.Build.VERSION_CODES#HONEYCOMB_MR2}, 2732 this is the new way to specify the largest screens an application is 2733 compatible with. This attribute provides the maximum 2734 "smallest screen width" (as per the -swNNNdp resource configuration) 2735 that the application is designed for. If this value is smaller than 2736 the "smallest screen width" of the device it is running on, the user 2737 is offered to run it in a compatibility mode that emulates a 2738 smaller screen and zooms it to fit the screen. Currently the compatibility mode only 2739 emulates phone screens with a 320dp width, so compatibility mode is not applied if the 2740 value for compatibleWidthLimitDp is larger than 320. --> 2741 <attr name="compatibleWidthLimitDp" format="integer" /> 2742 <!-- Starting with {@link android.os.Build.VERSION_CODES#HONEYCOMB_MR2}, 2743 this is the new way to specify the screens an application is 2744 compatible with. This attribute provides the maximum 2745 "smallest screen width" (as per the -swNNNdp resource configuration) 2746 that the application can work well on. If this value is smaller than 2747 the "smallest screen width" of the device it is running on, the 2748 application will be forced in to screen compatibility mode with 2749 no way for the user to turn it off. Currently the compatibility mode only 2750 emulates phone screens with a 320dp width, so compatibility mode is not applied if the 2751 value for largestWidthLimitDp is larger than 320. --> 2752 <attr name="largestWidthLimitDp" format="integer" /> 2753 <!-- Indicates whether the application supports smaller screen form-factors. 2754 A small screen is defined as one with a smaller aspect ratio than 2755 the traditional HVGA screen; that is, for a portrait screen, less 2756 tall than an HVGA screen. In practice, this means a QVGA low 2757 density or VGA high density screen. An application that does 2758 not support small screens <em>will not be available</em> for 2759 small screen devices, since there is little the platform can do 2760 to make such an application work on a smaller screen. --> 2761 <attr name="smallScreens" format="boolean" /> 2762 <!-- Indicates whether an application supports the normal screen 2763 form-factors. Traditionally this is an HVGA normal density 2764 screen, but WQVGA low density and WVGA high density are also 2765 considered to be normal. This attribute is true by default, 2766 and applications currently should leave it that way. --> 2767 <attr name="normalScreens" format="boolean" /> 2768 <!-- Indicates whether the application supports larger screen form-factors. 2769 A large screen is defined as a screen that is significantly larger 2770 than a normal phone screen, and thus may require some special care 2771 on the application's part to make good use of it. An example would 2772 be a VGA <em>normal density</em> screen, though even larger screens 2773 are certainly possible. An application that does not support 2774 large screens will be placed as a postage stamp on such a 2775 screen, so that it retains the dimensions it was originally 2776 designed for. --> 2777 <attr name="largeScreens" format="boolean" /> 2778 <!-- Indicates whether the application supports extra large screen form-factors. --> 2779 <attr name="xlargeScreens" format="boolean" /> 2780 <!-- Indicates whether the application can resize itself to newer 2781 screen sizes. This is mostly used to distinguish between old 2782 applications that may not be compatible with newly introduced 2783 screen sizes and newer applications that should be; it will be 2784 set for you automatically based on whether you are targeting 2785 a newer platform that supports more screens. --> 2786 <attr name="resizeable" format="boolean" /> 2787 <!-- Indicates whether the application can accommodate any screen 2788 density. This is assumed true if targetSdkVersion is 4 or higher. 2789 @deprecated Should always be true by default and not overridden. 2790 --> 2791 <attr name="anyDensity" format="boolean" /> 2792 </declare-styleable> 2793 2794 <!-- Private tag to declare system protected broadcast actions. 2795 2796 <p>This appears as a child tag of the root 2797 {@link #AndroidManifest manifest} tag. --> 2798 <declare-styleable name="AndroidManifestProtectedBroadcast" parent="AndroidManifest"> 2799 <attr name="name" /> 2800 </declare-styleable> 2801 2802 <!-- Private tag to declare the original package name that this package is 2803 based on. Only used for packages installed in the system image. If 2804 given, and different than the actual package name, and the given 2805 original package was previously installed on the device but the new 2806 one was not, then the data for the old one will be renamed to be 2807 for the new package. 2808 2809 <p>This appears as a child tag of the root 2810 {@link #AndroidManifest manifest} tag. --> 2811 <declare-styleable name="AndroidManifestOriginalPackage" parent="AndroidManifest"> 2812 <attr name="name" /> 2813 </declare-styleable> 2814 2815 <!-- The <code>processes</code> tag specifies the processes the application will run code in 2816 and optionally characteristics of those processes. This tag is optional; if not 2817 specified, components will simply run in the processes they specify. If supplied, 2818 they can only specify processes that are enumerated here, and if they don't this 2819 will be treated as a corrupt apk and result in an install failure. 2820 2821 <p>This appears as a child tag of the 2822 {@link #AndroidManifestApplication application} tag. --> 2823 <declare-styleable name="AndroidManifestProcesses" parent="AndroidManifestApplication"> 2824 </declare-styleable> 2825 2826 <!-- The <code>process</code> tag enumerates one of the available processes under its 2827 containing <code>processes</code> tag. 2828 2829 <p>This appears as a child tag of the 2830 {@link #AndroidManifestProcesses processes} tag. --> 2831 <declare-styleable name="AndroidManifestProcess" parent="AndroidManifestProcesses"> 2832 <!-- Required name of the process that is allowed --> 2833 <attr name="process" /> 2834 <!-- custom Application class name. We use call it "name", not "className", to be 2835 consistent with the Application tag. --> 2836 <attr name="name" /> 2837 <attr name="gwpAsanMode" /> 2838 <attr name="memtagMode" /> 2839 <attr name="nativeHeapZeroInitialized" /> 2840 <attr name="useEmbeddedDex" /> 2841 </declare-styleable> 2842 2843 <!-- The <code>deny-permission</code> tag specifies that a permission is to be denied 2844 for a particular process (if specified under the 2845 {@link #AndroidManifestProcess process} tag) or by default for all 2846 processes {if specified under the 2847 @link #AndroidManifestProcesses processes} tag). 2848 2849 <p>This appears as a child tag of the 2850 {@link #AndroidManifestProcesses processes} and 2851 {@link #AndroidManifestProcess process} tags. --> 2852 <declare-styleable name="AndroidManifestDenyPermission" 2853 parent="AndroidManifestProcesses"> 2854 <!-- Required name of the permission that is to be denied --> 2855 <attr name="name" /> 2856 </declare-styleable> 2857 2858 <!-- The <code>allow-permission</code> tag specifies that a permission is to be allowed 2859 for a particular process, when it was previously denied for all processes through 2860 {@link #AndroidManifestDenyPermission deny-permission} 2861 2862 <p>This appears as a child tag of the 2863 {@link #AndroidManifestProcesses processes} and 2864 {@link #AndroidManifestProcess process} tags. --> 2865 <declare-styleable name="AndroidManifestAllowPermission" 2866 parent="AndroidManifestProcesses"> 2867 <!-- Required name of the permission that is to be allowed. --> 2868 <attr name="name" /> 2869 </declare-styleable> 2870 2871 <!-- The <code>provider</code> tag declares a 2872 {@link android.content.ContentProvider} class that is available 2873 as part of the package's application components, supplying structured 2874 access to data managed by the application. 2875 2876 <p>This appears as a child tag of the 2877 {@link #AndroidManifestApplication application} tag. --> 2878 <declare-styleable name="AndroidManifestProvider" parent="AndroidManifestApplication"> 2879 <!-- Required name of the class implementing the provider, deriving from 2880 {@link android.content.ContentProvider}. This is a fully 2881 qualified class name (for example, com.mycompany.myapp.MyProvider); as a 2882 short-hand if the first character of the class 2883 is a period then it is appended to your package name. --> 2884 <attr name="name" /> 2885 <attr name="label" /> 2886 <attr name="description" /> 2887 <attr name="icon" /> 2888 <attr name="roundIcon" /> 2889 <attr name="banner" /> 2890 <attr name="logo" /> 2891 <attr name="process" /> 2892 <attr name="authorities" /> 2893 <attr name="syncable" /> 2894 <attr name="readPermission" /> 2895 <attr name="writePermission" /> 2896 <attr name="grantUriPermissions" /> 2897 <attr name="forceUriPermissions" /> 2898 <attr name="permission" /> 2899 <attr name="multiprocess" /> 2900 <attr name="initOrder" /> 2901 <!-- Specify whether this provider is enabled or not (that is, can be instantiated by the system). 2902 It can also be specified for an application as a whole, in which case a value of "false" 2903 will override any component specific values (a value of "true" will not override the 2904 component specific values). --> 2905 <attr name="enabled" /> 2906 <attr name="exported" /> 2907 <attr name="singleUser" /> 2908 <attr name="directBootAware" /> 2909 <attr name="visibleToInstantApps" /> 2910 <!-- The code for this component is located in the given split. 2911 <p>NOTE: This is only applicable to instant app. --> 2912 <attr name="splitName" /> 2913 <!-- Set of attribution tags that should be automatically applied to this component. 2914 <p> 2915 Each instance of this ContentProvider will be automatically configured with 2916 Context.createAttributionContext() using the first attribution tag 2917 contained here. --> 2918 <attr name="attributionTags" /> 2919 <attr name="systemUserOnly" format="boolean" /> 2920 </declare-styleable> 2921 2922 <!-- Attributes that can be supplied in an AndroidManifest.xml 2923 <code>grant-uri-permission</code> tag, a child of the 2924 {@link #AndroidManifestProvider provider} tag, describing a specific 2925 URI path that can be granted as a permission. This tag can be 2926 specified multiple time to supply multiple paths. If multiple 2927 path matching attributes are supplied, they will be evaluated in the 2928 following order with the first attribute being the only one honored: 2929 <code>pathAdvancedPattern</code>, <code>pathPattern</code>, 2930 <code>pathPrefix</code>, <code>pathSuffix</code>, <code>path</code>. --> 2931 <declare-styleable name="AndroidManifestGrantUriPermission" parent="AndroidManifestProvider"> 2932 <!-- Specify a URI path that must exactly match, as per 2933 {@link android.os.PatternMatcher} with 2934 {@link android.os.PatternMatcher#PATTERN_LITERAL}. --> 2935 <attr name="path" format="string" /> 2936 <!-- Specify a URI path that must be a prefix to match, as per 2937 {@link android.os.PatternMatcher} with 2938 {@link android.os.PatternMatcher#PATTERN_PREFIX}. --> 2939 <attr name="pathPrefix" format="string" /> 2940 <!-- Specify a URI path that matches a simple pattern, as per 2941 {@link android.os.PatternMatcher} with 2942 {@link android.os.PatternMatcher#PATTERN_SIMPLE_GLOB}. 2943 Note that because '\' is used as an escape character when 2944 reading the string from XML (before it is parsed as a pattern), 2945 you will need to double-escape: for example a literal "*" would 2946 be written as "\\*" and a literal "\" would be written as 2947 "\\\\". This is basically the same as what you would need to 2948 write if constructing the string in Java code. --> 2949 <attr name="pathPattern" format="string" /> 2950 <!-- Specify a URI path that matches an advanced pattern, as per 2951 {@link android.os.PatternMatcher} with 2952 {@link android.os.PatternMatcher#PATTERN_ADVANCED_GLOB}. 2953 Note that because '\' is used as an escape character when 2954 reading the string from XML (before it is parsed as a pattern), 2955 you will need to double-escape: for example a literal "*" would 2956 be written as "\\*" and a literal "\" would be written as 2957 "\\\\". This is basically the same as what you would need to 2958 write if constructing the string in Java code. --> 2959 <attr name="pathAdvancedPattern" format="string"/> 2960 <!-- Specify a URI path that must be a suffix to match, as per 2961 {@link android.os.PatternMatcher} with 2962 {@link android.os.PatternMatcher#PATTERN_SUFFIX}. --> 2963 <attr name="pathSuffix" format="string" /> 2964 </declare-styleable> 2965 2966 <!-- Attributes that can be supplied in an AndroidManifest.xml 2967 <code>path-permission</code> tag, a child of the 2968 {@link #AndroidManifestProvider provider} tag, describing a permission 2969 that allows access to a specific path in the provider. This tag can be 2970 specified multiple time to supply multiple paths. If multiple 2971 path matching attributes are supplied, they will be evaluated in the 2972 following order with the first attribute being the only one honored: 2973 <code>pathAdvancedPattern</code>, <code>pathPattern</code>, 2974 <code>pathPrefix</code>, <code>pathSuffix</code>, <code>path</code>.--> 2975 <declare-styleable name="AndroidManifestPathPermission" parent="AndroidManifestProvider"> 2976 <attr name="path" /> 2977 <attr name="pathPrefix" /> 2978 <attr name="pathPattern" /> 2979 <attr name="pathAdvancedPattern" format="string"/> 2980 <attr name="pathSuffix" /> 2981 <attr name="permission" /> 2982 <attr name="readPermission" /> 2983 <attr name="writePermission" /> 2984 </declare-styleable> 2985 2986 <!-- The <code>service</code> tag declares a 2987 {@link android.app.Service} class that is available 2988 as part of the package's application components, implementing 2989 long-running background operations or a rich communication API 2990 that can be called by other packages. 2991 2992 <p>Zero or more {@link #AndroidManifestIntentFilter intent-filter} 2993 tags can be included inside of a service, to specify the Intents 2994 that can connect with it. If none are specified, the service can 2995 only be accessed by direct specification of its class name. 2996 The service tag appears as a child tag of the 2997 {@link #AndroidManifestApplication application} tag. --> 2998 <declare-styleable name="AndroidManifestService" parent="AndroidManifestApplication"> 2999 <!-- Required name of the class implementing the service, deriving from 3000 {@link android.app.Service}. This is a fully 3001 qualified class name (for example, com.mycompany.myapp.MyService); as a 3002 short-hand if the first character of the class 3003 is a period then it is appended to your package name. --> 3004 <attr name="name" /> 3005 <attr name="label" /> 3006 <attr name="description" /> 3007 <attr name="icon" /> 3008 <attr name="roundIcon" /> 3009 <attr name="banner" /> 3010 <attr name="logo" /> 3011 <attr name="permission" /> 3012 <attr name="process" /> 3013 <!-- Specify whether the service is enabled or not (that is, can be instantiated by the system). 3014 It can also be specified for an application as a whole, in which case a value of "false" 3015 will override any component specific values (a value of "true" will not override the 3016 component specific values). --> 3017 <attr name="enabled" /> 3018 <attr name="exported" /> 3019 <!-- If set to true, this service with be automatically stopped 3020 when the user remove a task rooted in an activity owned by 3021 the application. The default is false. --> 3022 <attr name="stopWithTask" format="boolean" /> 3023 <!-- If set to true, this service will run under a special process 3024 that is isolated from the rest of the system. The only communication 3025 with it is through the Service API (binding and starting). --> 3026 <attr name="isolatedProcess" format="boolean" /> 3027 <attr name="singleUser" /> 3028 <attr name="directBootAware" /> 3029 <!-- If the service is an {@link android.R.attr#isolatedProcess} service, this permits a 3030 client to bind to the service as if it were running it its own package. The service 3031 must also be {@link android.R.attr#exported} if this flag is set. --> 3032 <attr name="externalService" format="boolean" /> 3033 <attr name="visibleToInstantApps" /> 3034 <!-- The code for this component is located in the given split. 3035 <p>NOTE: This is only applicable to instant app. --> 3036 <attr name="splitName" /> 3037 <!-- If true, and this is an {@link android.R.attr#isolatedProcess} service, the service 3038 will be spawned from an Application Zygote, instead of the regular Zygote. 3039 <p> 3040 The Application Zygote will first pre-initialize the application's class loader. Then, 3041 if the application has defined the {@link android.R.attr#zygotePreloadName} attribute, 3042 the Application Zygote will call into that class to allow it to perform 3043 application-specific preloads (such as loading a shared library). Therefore, 3044 spawning from the Application Zygote will typically reduce the service 3045 launch time and reduce its memory usage. The downside of using this flag 3046 is that you will have an additional process (the app zygote itself) that 3047 is taking up memory. Whether actual memory usage is improved therefore strongly 3048 depends on the number of isolated services that an application starts, 3049 and how much memory those services save by preloading and sharing memory with 3050 the app zygote. Therefore, it is recommended to measure memory usage under 3051 typical workloads to determine whether it makes sense to use this flag. 3052 3053 <p>There is a limit to the number of isolated services that can be spawned from 3054 the Application Zygote; the absolute limit is 100, but due to potential 3055 delays in service process cleanup, a much safer limit to use in practice is 50. 3056 --> 3057 <attr name="useAppZygote" format="boolean" /> 3058 <!-- If this is a foreground service, specify its category. --> 3059 <attr name="foregroundServiceType" /> 3060 <!-- Set of attribution tags that should be automatically applied to this component. 3061 <p> 3062 Each instance of this Service will be automatically configured with 3063 Context.createAttributionContext() using the first attribution tag 3064 contained here. --> 3065 <attr name="attributionTags" /> 3066 <!-- If true, and this is an {@link android.R.attr#isolatedProcess} service, the service 3067 is allowed to be bound in a shared isolated process with other isolated services. 3068 Note that these other isolated services can also belong to other apps from different 3069 vendors. 3070 <p> 3071 Shared isolated processes are created when using the 3072 {@link android.content.Context#BIND_SHARED_ISOLATED_PROCESS) during service binding. 3073 <p> 3074 Note that when this flag is used, the {@link android.R.attr#process} attribute is 3075 ignored when the process is bound into a shared isolated process by a client. 3076 --> 3077 <attr name="allowSharedIsolatedProcess" format="boolean" /> 3078 <attr name="systemUserOnly" format="boolean" /> 3079 </declare-styleable> 3080 3081 <!-- @hide The <code>apex-system-service</code> tag declares an apex system service 3082 that is contained within an application. 3083 3084 The apex system service tag appears as a child tag of the 3085 {@link #AndroidManifestApplication application} tag. --> 3086 <declare-styleable name="AndroidManifestApexSystemService" 3087 parent="AndroidManifestApplication"> 3088 <!-- The fully qualified class name of the system service. --> 3089 <attr name="name" /> 3090 <!-- The filepath to the .jar that contains the system service. If this is not provided, it 3091 is assumed that the system service exists in SYSTEMSERVERCLASSPATH. --> 3092 <attr name="path" /> 3093 <attr name="minSdkVersion" /> 3094 <attr name="maxSdkVersion" /> 3095 <!-- The order in which the apex system services are initiated. When there are dependencies 3096 among apex system services, setting this attribute for each of them ensures that they are 3097 created in the order required by those dependencies. The apex-system-services that are 3098 started manually within SystemServer ignore the initOrder and are not considered for 3099 automatic starting of the other services. 3100 The value is a simple integer, with higher number being initialized first. If not specified, 3101 the default order is 0. --> 3102 <attr name="initOrder" format="integer" /> 3103 </declare-styleable> 3104 3105 <!-- The <code>receiver</code> tag declares an 3106 {@link android.content.BroadcastReceiver} class that is available 3107 as part of the package's application components, allowing the 3108 application to receive actions or data broadcast by other 3109 applications even if it is not currently running. 3110 3111 <p>Zero or more {@link #AndroidManifestIntentFilter intent-filter} 3112 tags can be included inside of a receiver, to specify the Intents 3113 it will receive. If none are specified, the receiver will only 3114 be run when an Intent is broadcast that is directed at its specific 3115 class name. The receiver tag appears as a child tag of the 3116 {@link #AndroidManifestApplication application} tag. --> 3117 <declare-styleable name="AndroidManifestReceiver" parent="AndroidManifestApplication"> 3118 <!-- Required name of the class implementing the receiver, deriving from 3119 {@link android.content.BroadcastReceiver}. This is a fully 3120 qualified class name (for example, com.mycompany.myapp.MyReceiver); as a 3121 short-hand if the first character of the class 3122 is a period then it is appended to your package name. --> 3123 <attr name="name" /> 3124 <attr name="label" /> 3125 <attr name="description" /> 3126 <attr name="icon" /> 3127 <attr name="roundIcon" /> 3128 <attr name="banner" /> 3129 <attr name="logo" /> 3130 <attr name="permission" /> 3131 <attr name="process" /> 3132 <!-- Specify whether the receiver is enabled or not (that is, can be instantiated by the system). 3133 It can also be specified for an application as a whole, in which case a value of "false" 3134 will override any component specific values (a value of "true" will not override the 3135 component specific values). --> 3136 <attr name="enabled" /> 3137 <attr name="exported" /> 3138 <attr name="singleUser" /> 3139 <attr name="directBootAware" /> 3140 <!-- Set of attribution tags that should be automatically applied to this component. 3141 <p> 3142 Each instance of this BroadcastReceiver will be automatically configured with 3143 Context.createAttributionContext() using the first attribution tag 3144 contained here. --> 3145 <attr name="attributionTags" /> 3146 </declare-styleable> 3147 3148 <!-- The <code>activity</code> tag declares an 3149 {@link android.app.Activity} class that is available 3150 as part of the package's application components, implementing 3151 a part of the application's user interface. 3152 3153 <p>Zero or more {@link #AndroidManifestIntentFilter intent-filter} 3154 tags can be included inside of an activity, to specify the Intents 3155 that it can handle. If none are specified, the activity can 3156 only be started through direct specification of its class name. 3157 The activity tag appears as a child tag of the 3158 {@link #AndroidManifestApplication application} tag. --> 3159 <declare-styleable name="AndroidManifestActivity" parent="AndroidManifestApplication"> 3160 <!-- Required name of the class implementing the activity, deriving from 3161 {@link android.app.Activity}. This is a fully 3162 qualified class name (for example, com.mycompany.myapp.MyActivity); as a 3163 short-hand if the first character of the class 3164 is a period then it is appended to your package name. --> 3165 <attr name="name" /> 3166 <attr name="theme" /> 3167 <attr name="label" /> 3168 <attr name="description" /> 3169 <attr name="icon" /> 3170 <attr name="roundIcon" /> 3171 <attr name="banner" /> 3172 <attr name="logo" /> 3173 <attr name="launchMode" /> 3174 <attr name="screenOrientation" /> 3175 <attr name="configChanges" /> 3176 <attr name="recreateOnConfigChanges" /> 3177 <attr name="permission" /> 3178 <attr name="multiprocess" /> 3179 <attr name="process" /> 3180 <attr name="taskAffinity" /> 3181 <attr name="allowTaskReparenting" /> 3182 <attr name="finishOnTaskLaunch" /> 3183 <attr name="finishOnCloseSystemDialogs" /> 3184 <attr name="clearTaskOnLaunch" /> 3185 <attr name="noHistory" /> 3186 <attr name="alwaysRetainTaskState" /> 3187 <attr name="stateNotNeeded" /> 3188 <attr name="excludeFromRecents" /> 3189 <!-- @deprecated use {@link android.R.attr#showForAllUsers} instead. --> 3190 <attr name="showOnLockScreen" /> 3191 <!-- Specify whether the activity is enabled or not (that is, can be instantiated by the system). 3192 It can also be specified for an application as a whole, in which case a value of "false" 3193 will override any component specific values (a value of "true" will not override the 3194 component specific values). --> 3195 <attr name="enabled" /> 3196 <attr name="exported" /> 3197 <!-- Specify the default soft-input mode for the main window of 3198 this activity. A value besides "unspecified" here overrides 3199 any value in the theme. --> 3200 <attr name="windowSoftInputMode" /> 3201 <attr name="immersive" /> 3202 <attr name="hardwareAccelerated" /> 3203 <attr name="uiOptions" /> 3204 <attr name="parentActivityName" /> 3205 <attr name="singleUser" /> 3206 <!-- This broadcast receiver or activity will only receive broadcasts for the 3207 system user--> 3208 <attr name="systemUserOnly" format="boolean" /> 3209 <attr name="persistableMode" /> 3210 <attr name="allowEmbedded" /> 3211 <attr name="documentLaunchMode" /> 3212 <attr name="maxRecents" /> 3213 <attr name="autoRemoveFromRecents" /> 3214 <attr name="relinquishTaskIdentity" /> 3215 <attr name="resumeWhilePausing" /> 3216 <attr name="resizeableActivity" /> 3217 <attr name="supportsPictureInPicture" /> 3218 <attr name="maxAspectRatio" /> 3219 <attr name="minAspectRatio" /> 3220 <attr name="lockTaskMode" /> 3221 <attr name="showForAllUsers" /> 3222 3223 <attr name="showWhenLocked" /> 3224 <attr name="inheritShowWhenLocked" /> 3225 <attr name="turnScreenOn" /> 3226 3227 <attr name="directBootAware" /> 3228 <!-- @hide This activity is always focusable regardless of if it is in a task/stack whose 3229 activities are normally not focusable. 3230 For example, {@link android.R.attr#supportsPictureInPicture} activities are placed 3231 in a task/stack that isn't focusable. This flag allows them to be focusable.--> 3232 <attr name="alwaysFocusable" format="boolean" /> 3233 <attr name="enableVrMode" /> 3234 <attr name="rotationAnimation" /> 3235 <attr name="visibleToInstantApps" /> 3236 <!-- The code for this component is located in the given split. --> 3237 <attr name="splitName" /> 3238 <!-- Specify the color mode the activity desires. The requested color mode may be ignored 3239 depending on the capabilities of the display the activity is displayed on. --> 3240 <attr name="colorMode"> 3241 <!-- The default color mode (typically sRGB, low-dynamic range). --> 3242 <enum name="default" value="0" /> 3243 <!-- Wide color gamut color mode. --> 3244 <enum name="wideColorGamut" value="1" /> 3245 <!-- High dynamic range color mode. --> 3246 <enum name="hdr" value="2" /> 3247 </attr> 3248 <attr name="forceQueryable" format="boolean" /> 3249 <!-- Indicates whether the activity wants the connected display to do minimal 3250 post processing on the produced image or video frames. This will only be 3251 requested if this activity's main window is visible on the screen. 3252 3253 <p> This setting should be used when low latency has a higher priority than 3254 image enhancement processing (e.g. for games or video conferencing). 3255 3256 <p> If the Display sink is connected via HDMI, the device will begin to 3257 send infoframes with Auto Low Latency Mode enabled and Game Content Type. 3258 This will switch the connected display to a minimal image processing mode 3259 (if available), which reduces latency, improving the user experience for 3260 gaming or video conferencing applications. For more information, 3261 see HDMI 2.1 specification. 3262 3263 <p> If the Display sink has an internal connection or uses some other 3264 protocol than HDMI, effects may be similar but implementation-defined. 3265 3266 <p> The ability to switch to a mode with minimal post proessing may be 3267 disabled by a user setting in the system settings menu. In that case, 3268 this field is ignored and the display will remain in its current 3269 mode. 3270 3271 <p> See {@link android.content.pm.ActivityInfo#FLAG_PREFER_MINIMAL_POST_PROCESSING} --> 3272 <attr name="preferMinimalPostProcessing" format="boolean"/> 3273 <!-- Set of attribution tags that should be automatically applied to this component. 3274 <p> 3275 Each instance of this Activity will be automatically configured with 3276 Context.createAttributionContext() using the first attribution tag 3277 contained here. --> 3278 <attr name="attributionTags" /> 3279 <!-- Specifies whether a home sound effect should be played if the home app moves to 3280 front after an activity with this flag set to <code>true</code>. 3281 <p>The default value of this attribute is <code>true</code>. 3282 <p>Also note that home sounds are only played if the device supports home sounds, 3283 usually TVs. 3284 <p>Requires permission {@code android.permission.DISABLE_SYSTEM_SOUND_EFFECTS}. --> 3285 <attr name="playHomeTransitionSound" format="boolean"/> 3286 <!-- Indicates whether the activity can be displayed on a remote device which may or 3287 may not be running Android. --> 3288 <attr name="canDisplayOnRemoteDevices" format="boolean"/> 3289 <attr name="allowUntrustedActivityEmbedding" /> 3290 <attr name="knownActivityEmbeddingCerts" /> 3291 <!-- Specifies the required display category of the activity. Upon creation, a display can 3292 specify which display categories it supports and one of the categories must be present 3293 in the {@code <activity>} element to allow this activity to run. The default value is 3294 {@code null}, which indicates the activity does not have a required display category 3295 and thus can only run on a display that didn't specify any display categories. Each 3296 activity can only specify one required category but a display can accommodate multiple 3297 display categories. 3298 3299 <p> This field should be formatted as a Java-language-style free form string(for 3300 example, com.google.automotive_entertainment), which may contain uppercase or lowercase 3301 letters ('A' through 'Z'), numbers, and underscores ('_') but may only start with 3302 letters. 3303 --> 3304 <attr name="requiredDisplayCategory" format="string"/> 3305 <!-- If false, {@link android.view.KeyEvent#KEYCODE_BACK KEYCODE_BACK} and 3306 {@link android.app.Activity#onBackPressed Activity.onBackPressed()} 3307 and related event will be forwarded to the Activity and its views. 3308 3309 <p> If true, those events will be replaced by a call to 3310 {@link android.window.OnBackInvokedCallback#onBackInvoked} on the focused window. 3311 3312 <p> By default, the behavior is configured by the same attribute in application. 3313 --> 3314 <attr name="enableOnBackInvokedCallback" format="boolean"/> 3315 3316 <!-- Specifies permissions necessary to launch this activity when passing content URIs. The 3317 default value is {@code none}, meaning no specific permissions are required. Setting 3318 this attribute restricts activity invocation based on the invoker's permissions. If the 3319 invoker doesn't have the required permissions, the activity start will be denied via a 3320 {@link java.lang.SecurityException}. 3321 3322 <p> Note that the enforcement works for content URIs inside 3323 {@link android.content.Intent#getData}, {@link android.content.Intent#EXTRA_STREAM}, 3324 and {@link android.content.Intent#getClipData}. 3325 @FlaggedApi("android.security.content_uri_permission_apis") --> 3326 <attr name="requireContentUriPermissionFromCaller" format="string"> 3327 <!-- Default, no specific permissions are required. --> 3328 <enum name="none" value="0" /> 3329 <!-- Enforces the invoker to have read access to the passed content URIs. --> 3330 <enum name="read" value="1" /> 3331 <!-- Enforces the invoker to have write access to the passed content URIs. --> 3332 <enum name="write" value="2" /> 3333 <!-- Enforces the invoker to have either read or write access to the passed content 3334 URIs. --> 3335 <enum name="readOrWrite" value="3" /> 3336 <!-- Enforces the invoker to have both read and write access to the passed content 3337 URIs. --> 3338 <enum name="readAndWrite" value="4" /> 3339 </attr> 3340 </declare-styleable> 3341 3342 <!-- The <code>activity-alias</code> tag declares a new 3343 name for an existing {@link #AndroidManifestActivity activity} 3344 tag. 3345 3346 <p>Zero or more {@link #AndroidManifestIntentFilter intent-filter} 3347 tags can be included inside of an activity-alias, to specify the Intents 3348 that it can handle. If none are specified, the activity can 3349 only be started through direct specification of its class name. 3350 The activity-alias tag appears as a child tag of the 3351 {@link #AndroidManifestApplication application} tag. --> 3352 <declare-styleable name="AndroidManifestActivityAlias" parent="AndroidManifestApplication"> 3353 <!-- Required name of the class implementing the activity, deriving from 3354 {@link android.app.Activity}. This is a fully 3355 qualified class name (for example, com.mycompany.myapp.MyActivity); as a 3356 short-hand if the first character of the class 3357 is a period then it is appended to your package name. --> 3358 <attr name="name" /> 3359 <!-- The name of the activity this alias should launch. The activity 3360 must be in the same manifest as the alias, and have been defined 3361 in that manifest before the alias here. This must use a Java-style 3362 naming convention to ensure the name is unique, for example 3363 "com.mycompany.MyName". --> 3364 <attr name="targetActivity" format="string" /> 3365 <attr name="label" /> 3366 <attr name="description" /> 3367 <attr name="icon" /> 3368 <attr name="roundIcon" /> 3369 <attr name="banner" /> 3370 <attr name="logo" /> 3371 <attr name="permission" /> 3372 <!-- Specify whether the activity-alias is enabled or not (that is, can be instantiated by the system). 3373 It can also be specified for an application as a whole, in which case a value of "false" 3374 will override any component specific values (a value of "true" will not override the 3375 component specific values). --> 3376 <attr name="enabled" /> 3377 <attr name="exported" /> 3378 <attr name="parentActivityName" /> 3379 <attr name="attributionTags" /> 3380 <attr name="allowUntrustedActivityEmbedding" /> 3381 <attr name="knownActivityEmbeddingCerts" /> 3382 </declare-styleable> 3383 3384 <!-- The <code>meta-data</code> tag is used to attach additional 3385 arbitrary data to an application component. The data can later 3386 be retrieved programmatically from the 3387 {@link android.content.pm.ComponentInfo#metaData 3388 ComponentInfo.metaData} field. There is no meaning given to this 3389 data by the system. You may supply the data through either the 3390 <code>value</code> or <code>resource</code> attribute; if both 3391 are given, then <code>resource</code> will be used. 3392 3393 <p>It is highly recommended that you avoid supplying related data as 3394 multiple separate meta-data entries. Instead, if you have complex 3395 data to associate with a component, then use the <code>resource</code> 3396 attribute to assign an XML resource that the client can parse to 3397 retrieve the complete data. --> 3398 <declare-styleable name="AndroidManifestMetaData" 3399 parent="AndroidManifestApplication 3400 AndroidManifestActivity 3401 AndroidManifestReceiver 3402 AndroidManifestProvider 3403 AndroidManifestService 3404 AndroidManifestPermission 3405 AndroidManifestPermissionGroup 3406 AndroidManifestInstrumentation"> 3407 <attr name="name" /> 3408 <!-- Concrete value to assign to this piece of named meta-data. 3409 The data can later be retrieved from the meta data Bundle 3410 through {@link android.os.Bundle#getString Bundle.getString}, 3411 {@link android.os.Bundle#getInt Bundle.getInt}, 3412 {@link android.os.Bundle#getBoolean Bundle.getBoolean}, 3413 or {@link android.os.Bundle#getFloat Bundle.getFloat} depending 3414 on the type used here. --> 3415 <attr name="value" format="string|integer|color|float|boolean" /> 3416 <!-- Resource identifier to assign to this piece of named meta-data. 3417 The resource identifier can later be retrieved from the meta data 3418 Bundle through {@link android.os.Bundle#getInt Bundle.getInt}. --> 3419 <attr name="resource" format="reference" /> 3420 </declare-styleable> 3421 3422 <!-- The <code>property</code> tag is used to attach additional data that can 3423 be supplied to the parent component. A component element can contain any 3424 number of <code>property</code> subelements. Valid names are any of the 3425 <code>PROPERTY_</code> constants defined in the 3426 {@link android.content.pm.PackageManager PackageManager} class. Values 3427 are obtained using the appropriate method on the 3428 {@link android.content.pm.PackageManager.Property PackageManager.Property} class. 3429 <p>Ordinary values are specified through the value attribute. Resource IDs are 3430 specified through the resource attribute. 3431 <p>It is invalid to specify both a value and resource attributes. --> 3432 <declare-styleable name="AndroidManifestProperty" 3433 parent="AndroidManifestApplication 3434 AndroidManifestActivity 3435 AndroidManifestReceiver 3436 AndroidManifestProvider 3437 AndroidManifestService"> 3438 <attr name="name" /> 3439 <!-- Concrete value to assign to this property. 3440 The data can later be retrieved from the property object 3441 through 3442 {@link android.content.pm.PackageManager.Property#getString Property.getString}, 3443 {@link android.content.pm.PackageManager.Property#getInteger Property.getInteger}, 3444 {@link android.content.pm.PackageManager.Property#getBoolean Property.getBoolean}, 3445 or {@link android.content.pm.PackageManager.Property#getFloat Property.getFloat} 3446 depending on the type used here. --> 3447 <attr name="value" /> 3448 <!-- The resource identifier to assign to this property. 3449 The resource identifier can later be retrieved from the property object through 3450 {@link android.content.pm.PackageManager.Property#getResourceId Property.getResourceId}. --> 3451 <attr name="resource" /> 3452 </declare-styleable> 3453 3454 <!-- The <code>intent-filter</code> tag is used to construct an 3455 {@link android.content.IntentFilter} object that will be used 3456 to determine which component can handle a particular 3457 {@link android.content.Intent} that has been given to the system. 3458 It can be used as a child of the 3459 {@link #AndroidManifestActivity activity}, 3460 {@link #AndroidManifestReceiver receiver} and 3461 {@link #AndroidManifestService service} 3462 tags. 3463 3464 <p> Zero or more {@link #AndroidManifestAction action}, 3465 {@link #AndroidManifestCategory category}, and/or 3466 {@link #AndroidManifestData data} tags should be 3467 included inside to describe the contents of the filter. 3468 3469 <p> The optional label and icon attributes here are used with 3470 an activity to supply an alternative description of that activity 3471 when it is being started through an Intent matching this filter. --> 3472 <declare-styleable name="AndroidManifestIntentFilter" 3473 parent="AndroidManifestActivity AndroidManifestReceiver AndroidManifestService"> 3474 <attr name="label" /> 3475 <attr name="icon" /> 3476 <attr name="roundIcon" /> 3477 <attr name="banner" /> 3478 <attr name="logo" /> 3479 <attr name="priority" /> 3480 <attr name="autoVerify" /> 3481 <!-- Within an application, multiple intent filters may match a particular 3482 intent. This allows the app author to specify the order filters should 3483 be considered. We don't want to use priority because that is global 3484 across applications. 3485 <p>Only use if you really need to forcibly set the order in which 3486 filters are evaluated. It is preferred to target an activity with a 3487 directed intent instead. 3488 <p>The value is a single integer, with higher numbers considered to 3489 be better. If not specified, the default order is 0. --> 3490 <attr name="order" /> 3491 </declare-styleable> 3492 3493 <!-- Attributes that can be supplied in an AndroidManifest.xml 3494 <code>action</code> tag, a child of the 3495 {@link #AndroidManifestIntentFilter intent-filter} tag. 3496 See {@link android.content.IntentFilter#addAction} for 3497 more information. --> 3498 <declare-styleable name="AndroidManifestAction" parent="AndroidManifestIntentFilter"> 3499 <!-- The name of an action that is handled, using the Java-style 3500 naming convention. For example, to support 3501 {@link android.content.Intent#ACTION_VIEW Intent.ACTION_VIEW} 3502 you would put <code>android.intent.action.VIEW</code> here. 3503 Custom actions should generally use a prefix matching the 3504 package name. --> 3505 <attr name="name" /> 3506 </declare-styleable> 3507 3508 <!-- Attributes that can be supplied in an AndroidManifest.xml 3509 <code>data</code> tag, a child of the 3510 {@link #AndroidManifestIntentFilter intent-filter} tag, describing 3511 a group matching rule consisting of one or more 3512 {@link #AndroidManifestData data} tags that must all match. This 3513 tag can be specified multiple times to create multiple groups that 3514 will be matched in the order they are defined. --> 3515 <declare-styleable name="AndroidManifestUriRelativeFilterGroup" 3516 parent="AndroidManifestIntentFilter"> 3517 <!-- Specify if this group is allow rule or disallow rule. If this 3518 attribute is not specified then it is assumed to be true --> 3519 <attr name="allow" format="boolean"/> 3520 </declare-styleable> 3521 3522 <!-- Attributes that can be supplied in an AndroidManifest.xml 3523 <code>data</code> tag, a child of the 3524 {@link #AndroidManifestIntentFilter intent-filter} tag, describing 3525 the types of data that match. This tag can be specified multiple 3526 times to supply multiple data options, as described in the 3527 {@link android.content.IntentFilter} class. Note that all such 3528 tags are adding options to the same IntentFilter so that, for example, 3529 <code><data android:scheme="myscheme" android:host="me.com" /></code> 3530 is equivalent to <code><data android:scheme="myscheme" /> 3531 <data android:host="me.com" /></code>. --> 3532 <declare-styleable name="AndroidManifestData" 3533 parent="AndroidManifestIntentFilter AndroidManifestUriRelativeFilterGroup"> 3534 <!-- Specify a MIME type that is handled, as per 3535 {@link android.content.IntentFilter#addDataType 3536 IntentFilter.addDataType()}. 3537 <p><em>Note: MIME type matching in the Android framework is 3538 case-sensitive, unlike formal RFC MIME types. As a result, 3539 MIME types here should always use lower case letters.</em></p> --> 3540 <attr name="mimeType" format="string" /> 3541 <!-- Specify a group of MIME types that are handled. MIME types can be added and 3542 removed to a package's MIME group via the PackageManager. --> 3543 <attr name="mimeGroup" format="string" /> 3544 <!-- Specify a URI scheme that is handled, as per 3545 {@link android.content.IntentFilter#addDataScheme 3546 IntentFilter.addDataScheme()}. 3547 <p><em>Note: scheme matching in the Android framework is 3548 case-sensitive, unlike the formal RFC. As a result, 3549 schemes here should always use lower case letters.</em></p> --> 3550 <attr name="scheme" format="string" /> 3551 <!-- Specify a URI scheme specific part that must exactly match, as per 3552 {@link android.content.IntentFilter#addDataSchemeSpecificPart 3553 IntentFilter.addDataSchemeSpecificPart()} with 3554 {@link android.os.PatternMatcher#PATTERN_LITERAL}. --> 3555 <attr name="ssp" format="string" /> 3556 <!-- Specify a URI scheme specific part that must be a prefix to match, as per 3557 {@link android.content.IntentFilter#addDataSchemeSpecificPart 3558 IntentFilter.addDataSchemeSpecificPart()} with 3559 {@link android.os.PatternMatcher#PATTERN_PREFIX}. --> 3560 <attr name="sspPrefix" format="string" /> 3561 <!-- Specify a URI scheme specific part that matches a simple pattern, as per 3562 {@link android.content.IntentFilter#addDataSchemeSpecificPart 3563 IntentFilter.addDataSchemeSpecificPart()} with 3564 {@link android.os.PatternMatcher#PATTERN_SIMPLE_GLOB}. 3565 Note that because '\' is used as an escape character when 3566 reading the string from XML (before it is parsed as a pattern), 3567 you will need to double-escape: for example a literal "*" would 3568 be written as "\\*" and a literal "\" would be written as 3569 "\\\\". This is basically the same as what you would need to 3570 write if constructing the string in Java code. --> 3571 <attr name="sspPattern" format="string" /> 3572 <!-- Specify a URI scheme specific part that matches an advanced pattern, as per 3573 {@link android.content.IntentFilter#addDataSchemeSpecificPart 3574 IntentFilter.addDataSchemeSpecificPart()} with 3575 {@link android.os.PatternMatcher#PATTERN_ADVANCED_GLOB}. 3576 Note that because '\' is used as an escape character when 3577 reading the string from XML (before it is parsed as a pattern), 3578 you will need to double-escape: for example a literal "*" would 3579 be written as "\\*" and a literal "\" would be written as 3580 "\\\\". This is basically the same as what you would need to 3581 write if constructing the string in Java code. --> 3582 <attr name="sspAdvancedPattern" format="string" /> 3583 <!-- Specify a URI scheme specific part that must be a suffix to match, as per 3584 {@link android.content.IntentFilter#addDataSchemeSpecificPart 3585 IntentFilter.addDataSchemeSpecificPart()} with 3586 {@link android.os.PatternMatcher#PATTERN_SUFFIX}. --> 3587 <attr name="sspSuffix" format="string" /> 3588 <!-- Specify a URI authority host that is handled, as per 3589 {@link android.content.IntentFilter#addDataAuthority 3590 IntentFilter.addDataAuthority()}. 3591 <p><em>Note: host name matching in the Android framework is 3592 case-sensitive, unlike the formal RFC. As a result, 3593 host names here should always use lower case letters.</em></p> --> 3594 <attr name="host" format="string" /> 3595 <!-- Specify a URI authority port that is handled, as per 3596 {@link android.content.IntentFilter#addDataAuthority 3597 IntentFilter.addDataAuthority()}. If a host is supplied 3598 but not a port, any port is matched. --> 3599 <attr name="port" format="string" /> 3600 <!-- Specify a URI path that must exactly match, as per 3601 {@link android.content.IntentFilter#addDataPath 3602 IntentFilter.addDataPath()} with 3603 {@link android.os.PatternMatcher#PATTERN_LITERAL}. --> 3604 <attr name="path" /> 3605 <!-- Specify a URI path that must be a prefix to match, as per 3606 {@link android.content.IntentFilter#addDataPath 3607 IntentFilter.addDataPath()} with 3608 {@link android.os.PatternMatcher#PATTERN_PREFIX}. --> 3609 <attr name="pathPrefix" /> 3610 <!-- Specify a URI path that matches a simple pattern, as per 3611 {@link android.content.IntentFilter#addDataPath 3612 IntentFilter.addDataPath()} with 3613 {@link android.os.PatternMatcher#PATTERN_SIMPLE_GLOB}. 3614 Note that because '\' is used as an escape character when 3615 reading the string from XML (before it is parsed as a pattern), 3616 you will need to double-escape: for example a literal "*" would 3617 be written as "\\*" and a literal "\" would be written as 3618 "\\\\". This is basically the same as what you would need to 3619 write if constructing the string in Java code. --> 3620 <attr name="pathPattern" /> 3621 <!-- Specify a URI path that matches an advanced pattern, as per 3622 {@link android.content.IntentFilter#addDataPath 3623 IntentFilter.addDataPath()} with 3624 {@link android.os.PatternMatcher#PATTERN_ADVANCED_GLOB}. 3625 Note that because '\' is used as an escape character when 3626 reading the string from XML (before it is parsed as a pattern), 3627 you will need to double-escape: for example a literal "*" would 3628 be written as "\\*" and a literal "\" would be written as 3629 "\\\\". This is basically the same as what you would need to 3630 write if constructing the string in Java code. --> 3631 <attr name="pathAdvancedPattern" /> 3632 <!-- Specify a URI path that must be a suffix to match, as per 3633 {@link android.content.IntentFilter#addDataPath 3634 IntentFilter.addDataPath()} with 3635 {@link android.os.PatternMatcher#PATTERN_SUFFIX}. --> 3636 <attr name="pathSuffix" /> 3637 <!-- Specify a URI query that must exactly match, as a 3638 {@link android.content.UriRelativeFilter UriRelativeFilter} with 3639 {@link android.os.PatternMatcher#PATTERN_LITERAL}. --> 3640 <attr name="query" format="string" /> 3641 <!-- Specify a URI query that must be a prefix to match, as a 3642 {@link android.content.UriRelativeFilter UriRelativeFilter} with 3643 {@link android.os.PatternMatcher#PATTERN_PREFIX}. --> 3644 <attr name="queryPrefix" format="string" /> 3645 <!-- Specify a URI query that matches a simple pattern, as a 3646 {@link android.content.UriRelativeFilter UriRelativeFilter} with 3647 {@link android.os.PatternMatcher#PATTERN_SIMPLE_GLOB}. 3648 Note that because '\' is used as an escape character when 3649 reading the string from XML (before it is parsed as a pattern), 3650 you will need to double-escape: for example a literal "*" would 3651 be written as "\\*" and a literal "\" would be written as 3652 "\\\\". This is basically the same as what you would need to 3653 write if constructing the string in Java code. --> 3654 <attr name="queryPattern" format="string" /> 3655 <!-- Specify a URI query that matches an advanced pattern, as a 3656 {@link android.content.UriRelativeFilter UriRelativeFilter} with 3657 {@link android.os.PatternMatcher#PATTERN_ADVANCED_GLOB}. 3658 Note that because '\' is used as an escape character when 3659 reading the string from XML (before it is parsed as a pattern), 3660 you will need to double-escape: for example a literal "*" would 3661 be written as "\\*" and a literal "\" would be written as 3662 "\\\\". This is basically the same as what you would need to 3663 write if constructing the string in Java code. --> 3664 <attr name="queryAdvancedPattern" format="string" /> 3665 <!-- Specify a URI query that must be a suffix to match, as a 3666 {@link android.content.UriRelativeFilter UriRelativeFilter} with 3667 {@link android.os.PatternMatcher#PATTERN_SUFFIX}. --> 3668 <attr name="querySuffix" format="string" /> 3669 <!-- Specify a URI fragment that must exactly match, as a 3670 {@link android.content.UriRelativeFilter UriRelativeFilter} with 3671 {@link android.os.PatternMatcher#PATTERN_LITERAL}. --> 3672 <attr name="fragment" format="string" /> 3673 <!-- Specify a URI fragment that must be a prefix to match, as a 3674 {@link android.content.UriRelativeFilter UriRelativeFilter} with 3675 {@link android.os.PatternMatcher#PATTERN_PREFIX}. --> 3676 <attr name="fragmentPrefix" format="string" /> 3677 <!-- Specify a URI fragment that matches a simple pattern, as a 3678 {@link android.content.UriRelativeFilter UriRelativeFilter} with 3679 {@link android.os.PatternMatcher#PATTERN_SIMPLE_GLOB}. 3680 Note that because '\' is used as an escape character when 3681 reading the string from XML (before it is parsed as a pattern), 3682 you will need to double-escape: for example a literal "*" would 3683 be written as "\\*" and a literal "\" would be written as 3684 "\\\\". This is basically the same as what you would need to 3685 write if constructing the string in Java code. --> 3686 <attr name="fragmentPattern" format="string" /> 3687 <!-- Specify a URI fragment that matches an advanced pattern, as a 3688 {@link android.content.UriRelativeFilter UriRelativeFilter} with 3689 {@link android.os.PatternMatcher#PATTERN_ADVANCED_GLOB}. 3690 Note that because '\' is used as an escape character when 3691 reading the string from XML (before it is parsed as a pattern), 3692 you will need to double-escape: for example a literal "*" would 3693 be written as "\\*" and a literal "\" would be written as 3694 "\\\\". This is basically the same as what you would need to 3695 write if constructing the string in Java code. --> 3696 <attr name="fragmentAdvancedPattern" format="string" /> 3697 <!-- Specify a URI fragment that must be a suffix to match, as a 3698 {@link android.content.UriRelativeFilter UriRelativeFilter} with 3699 {@link android.os.PatternMatcher#PATTERN_SUFFIX}. --> 3700 <attr name="fragmentSuffix" format="string" /> 3701 </declare-styleable> 3702 3703 <!-- Attributes that can be supplied in an AndroidManifest.xml 3704 <code>category</code> tag, a child of the 3705 {@link #AndroidManifestIntentFilter intent-filter} tag. 3706 See {@link android.content.IntentFilter#addCategory} for 3707 more information. --> 3708 <declare-styleable name="AndroidManifestCategory" parent="AndroidManifestIntentFilter"> 3709 <!-- The name of category that is handled, using the Java-style 3710 naming convention. For example, to support 3711 {@link android.content.Intent#CATEGORY_LAUNCHER Intent.CATEGORY_LAUNCHER} 3712 you would put <code>android.intent.category.LAUNCHER</code> here. 3713 Custom actions should generally use a prefix matching the 3714 package name. --> 3715 <attr name="name" /> 3716 </declare-styleable> 3717 3718 <!-- Attributes that can be supplied in an AndroidManifest.xml 3719 <code>instrumentation</code> tag, a child of the root 3720 {@link #AndroidManifest manifest} tag. --> 3721 <declare-styleable name="AndroidManifestInstrumentation" parent="AndroidManifest"> 3722 <!-- Required name of the class implementing the instrumentation, deriving from 3723 {@link android.app.Instrumentation}. This is a fully 3724 qualified class name (for example, com.mycompany.myapp.MyActivity); as a 3725 short-hand if the first character of the class 3726 is a period then it is appended to your package name. --> 3727 <attr name="name" /> 3728 <attr name="targetPackage" /> 3729 <attr name="targetProcesses" /> 3730 <attr name="label" /> 3731 <attr name="icon" /> 3732 <attr name="roundIcon" /> 3733 <attr name="banner" /> 3734 <attr name="logo" /> 3735 <attr name="handleProfiling" /> 3736 <attr name="functionalTest" /> 3737 </declare-styleable> 3738 3739 <!-- Attributes that can be supplied in an AndroidManifest.xml 3740 <code>screen</code> tag, a child of <code>compatible-screens</code>, 3741 which is itself a child of the root 3742 {@link #AndroidManifest manifest} tag. --> 3743 <declare-styleable name="AndroidManifestCompatibleScreensScreen" 3744 parent="AndroidManifest.AndroidManifestCompatibleScreens"> 3745 <!-- Specifies a compatible screen size, as per the device 3746 configuration screen size bins. --> 3747 <attr name="screenSize"> 3748 <!-- A small screen configuration, at least 240x320dp. --> 3749 <enum name="small" value="200" /> 3750 <!-- A normal screen configuration, at least 320x480dp. --> 3751 <enum name="normal" value="300" /> 3752 <!-- A large screen configuration, at least 400x530dp. --> 3753 <enum name="large" value="400" /> 3754 <!-- An extra large screen configuration, at least 600x800dp. --> 3755 <enum name="xlarge" value="500" /> 3756 </attr> 3757 <!-- Specifies a compatible screen density, as per the device 3758 configuration screen density bins. --> 3759 <attr name="screenDensity" format="integer"> 3760 <!-- A low density screen, approximately 120dpi. --> 3761 <enum name="ldpi" value="120" /> 3762 <!-- A medium density screen, approximately 160dpi. --> 3763 <enum name="mdpi" value="160" /> 3764 <!-- A high density screen, approximately 240dpi. --> 3765 <enum name="hdpi" value="240" /> 3766 <!-- An extra high density screen, approximately 320dpi. --> 3767 <enum name="xhdpi" value="320" /> 3768 <!-- An extra extra high density screen, approximately 480dpi. --> 3769 <enum name="xxhdpi" value="480" /> 3770 <!-- An extra extra extra high density screen, approximately 640dpi. --> 3771 <enum name="xxxhdpi" value="640" /> 3772 </attr> 3773 </declare-styleable> 3774 3775 <!-- The <code>input-type</code> tag is a child of the <code>supports-input</code> tag, which 3776 is itself a child of the root {@link #AndroidManifest manifest} tag. Each 3777 <code>input-type</code> tag specifices the name of a specific input device type. When 3778 grouped with the other elements of the parent <code>supports-input</code> tag it defines 3779 a collection of input devices, which when all used together, are considered a supported 3780 input mechanism for the application. There may be multiple <code>supports-input</code> 3781 tags defined, each containing a different combination of input device types. --> 3782 <declare-styleable name="AndroidManifestSupportsInputInputType" 3783 parent="AndroidManifest.AndroidManifestSupportsInput"> 3784 <!-- Specifices the name of the input device type --> 3785 <attr name="name" /> 3786 </declare-styleable> 3787 3788 <!-- The attribute that holds a Base64-encoded public key. --> 3789 <attr name="publicKey" format="string" /> 3790 3791 <!-- Attributes relating to a package verifier. --> 3792 <declare-styleable name="AndroidManifestPackageVerifier" parent="AndroidManifest"> 3793 <!-- Specifies the Java-style package name that defines this 3794 package verifier. --> 3795 <attr name="name" /> 3796 3797 <!-- The Base64 encoded public key of the package verifier's 3798 signature. --> 3799 <attr name="publicKey" /> 3800 </declare-styleable> 3801 3802 <!-- Attributes relating to resource overlay packages. --> 3803 <declare-styleable name="AndroidManifestResourceOverlay" parent="AndroidManifest"> 3804 <!-- Package name of base package whose resources will be overlaid. --> 3805 <attr name="targetPackage" /> 3806 3807 <!-- Category of the resource overlay. --> 3808 <attr name="category" format="string"/> 3809 3810 <!-- Load order of overlay package. --> 3811 <attr name="priority" /> 3812 3813 <!-- Whether the given RRO is static or not. --> 3814 <attr name="isStatic" format="boolean" /> 3815 3816 <!-- Required property name/value pair used to enable this overlay. 3817 e.g. name=ro.oem.sku value=MKT210. 3818 Overlay will be ignored unless system property exists and is 3819 set to specified value --> 3820 <!-- @hide This shouldn't be public. --> 3821 <attr name="requiredSystemPropertyName" format="string" /> 3822 <!-- @hide This shouldn't be public. --> 3823 <attr name="requiredSystemPropertyValue" format="string" /> 3824 3825 <!-- The name of the overlayable whose resources will be overlaid. --> 3826 <attr name="targetName" /> 3827 3828 <!-- The xml file that defines the target id to overlay value mappings. --> 3829 <attr name="resourcesMap" format="reference" /> 3830 </declare-styleable> 3831 3832 <!-- Declaration of an {@link android.content.Intent} object in XML. May 3833 also include zero or more {@link #IntentCategory <category>} and 3834 {@link #Extra <extra>} tags. --> 3835 <declare-styleable name="Intent"> 3836 <!-- The action name to assign to the Intent, as per 3837 {@link android.content.Intent#setAction Intent.setAction()}. --> 3838 <attr name="action" format="string" /> 3839 <!-- The data URI to assign to the Intent, as per 3840 {@link android.content.Intent#setData Intent.setData()}. 3841 <p><em>Note: scheme and host name matching in the Android framework is 3842 case-sensitive, unlike the formal RFC. As a result, 3843 URIs here should always be normalized to use lower case letters 3844 for these elements (as well as other proper Uri normalization).</em></p> --> 3845 <attr name="data" format="string" /> 3846 <!-- The MIME type name to assign to the Intent, as per 3847 {@link android.content.Intent#setType Intent.setType()}. 3848 <p><em>Note: MIME type matching in the Android framework is 3849 case-sensitive, unlike formal RFC MIME types. As a result, 3850 MIME types here should always use lower case letters.</em></p> --> 3851 <attr name="mimeType" /> 3852 <!-- The identifier to assign to the intent, as per 3853 {@link android.content.Intent#setIdentifier Intent.setIdentifier()}. --> 3854 <attr name="identifier" format="string" /> 3855 <!-- The package part of the ComponentName to assign to the Intent, as per 3856 {@link android.content.Intent#setComponent Intent.setComponent()}. --> 3857 <attr name="targetPackage" /> 3858 <!-- The class part of the ComponentName to assign to the Intent, as per 3859 {@link android.content.Intent#setComponent Intent.setComponent()}. --> 3860 <attr name="targetClass" format="string" /> 3861 </declare-styleable> 3862 3863 <!-- A category to add to an Intent, as per 3864 {@link android.content.Intent#addCategory Intent.addCategory()}. --> 3865 <declare-styleable name="IntentCategory" parent="Intent"> 3866 <!-- Required name of the category. --> 3867 <attr name="name" /> 3868 </declare-styleable> 3869 3870 <!-- An extra data value to place into a an extra/name value pair held 3871 in a Bundle, as per {@link android.os.Bundle}. --> 3872 <declare-styleable name="Extra" parent="Intent"> 3873 <!-- Required name of the extra data. --> 3874 <attr name="name" /> 3875 <!-- Concrete value to put for this named extra data. --> 3876 <attr name="value" /> 3877 </declare-styleable> 3878 3879 <!-- Groups signing keys into a {@code KeySet} for easier reference in 3880 other APIs. However, currently no APIs use this. --> 3881 <attr name="keySet" /> 3882 <declare-styleable name="AndroidManifestPublicKey"> 3883 <attr name="name" /> 3884 <attr name="value" /> 3885 </declare-styleable> 3886 <declare-styleable name="AndroidManifestKeySet"> 3887 <attr name="name" /> 3888 </declare-styleable> 3889 3890 <!-- Associate declared KeySets with upgrading capability. --> 3891 <declare-styleable name="AndroidManifestUpgradeKeySet" parent="AndroidManifest"> 3892 <attr name="name" /> 3893 </declare-styleable> 3894 3895 <!-- <code>layout</code> tag allows configuring the layout for the activity within multi-window 3896 environment. --> 3897 <declare-styleable name="AndroidManifestLayout" parent="AndroidManifestActivity"> 3898 <!-- Default width of the activity. Can be either a fixed value or fraction, in which case 3899 the width will be constructed as a fraction of the total available width. --> 3900 <attr name="defaultWidth" format="dimension|fraction" /> 3901 <!-- Default height of the activity. Can be either a fixed value or fraction, in which case 3902 the height will be constructed as a fraction of the total available height. --> 3903 <attr name="defaultHeight" format="dimension|fraction" /> 3904 <!-- Where to initially position the activity inside the available space. Uses constants 3905 defined in {@link android.view.Gravity}. --> 3906 <attr name="gravity" /> 3907 <!-- Minimal width of the activity. 3908 3909 <p><strong>NOTE:</strong> A task's root activity value is applied to all additional 3910 activities launched in the task. That is if the root activity of a task set minimal width, 3911 then the system will set the same minimal width on all other activities in the task. It 3912 will also ignore any other minimal width attributes of non-root activities. --> 3913 <attr name="minWidth" /> 3914 <!-- Minimal height of the activity. 3915 3916 <p><strong>NOTE:</strong> A task's root activity value is applied to all additional 3917 activities launched in the task. That is if the root activity of a task set minimal height, 3918 then the system will set the same minimal height on all other activities in the task. It 3919 will also ignore any other minimal height attributes of non-root activities. --> 3920 <attr name="minHeight" /> 3921 3922 <!-- Window layout affinity of this activity. Activities with the same window layout 3923 affinity will share the same layout record. That is, if a user is opening an activity in 3924 a new task on a display that can host freeform windows, and the user had opened a task 3925 before and that task had a root activity who had the same window layout affinity, the 3926 new task's window will be created in the same window mode and around the location which 3927 the previously opened task was in. 3928 3929 <p>For example, if a user maximizes a task with root activity A and opens another 3930 activity B that has the same window layout affinity as activity A has, activity B will 3931 be created in fullscreen window mode. Similarly, if they move/resize a task with root 3932 activity C and open another activity D that has the same window layout affinity as 3933 activity C has, activity D will be in freeform window mode and as close to the position 3934 of activity C as conditions permit. It doesn't require the user to keep the task with 3935 activity A or activity C open. It won't, however, put any task into split-screen or PIP 3936 window mode on launch. 3937 3938 <p>If the user is opening an activity with its window layout affinity for the first time, 3939 the window mode and position is OEM defined. 3940 3941 <p>By default activity doesn't share any affinity with other activities. --> 3942 <attr name="windowLayoutAffinity" format="string" /> 3943 </declare-styleable> 3944 3945 <!-- <code>restrict-update</code> tag restricts system apps from being updated unless the 3946 SHA-512 hash equals the specified value. 3947 @hide --> 3948 <declare-styleable name="AndroidManifestRestrictUpdate" parent="AndroidManifest"> 3949 <!-- The SHA-512 hash of the only APK that can be used to update a package. 3950 <p>NOTE: This is only applicable to system packages. 3951 @hide --> 3952 <attr name="hash" format="string" /> 3953 </declare-styleable> 3954 3955 <declare-styleable name="AndroidManifestUsesSplit" parent="AndroidManifest"> 3956 <attr name="name" format="string" /> 3957 </declare-styleable> 3958 3959 3960 <declare-styleable name="AndroidManifestProfileable" parent="AndroidManifestApplication"> 3961 <!-- Flag indicating whether the application can be profiled by the shell user, 3962 even when running on a device that is running in user mode. --> 3963 <attr name="shell" format="boolean" /> 3964 <!-- Flag indicating whether the application can be profiled by system services, but not 3965 necessarily via shell tools (for which also android:shell="true" must be set). If 3966 false, the application cannot be profiled at all. Defaults to true. --> 3967 <attr name="enabled" format="boolean" /> 3968 </declare-styleable> 3969 3970 <!-- <code>install-constraints</code> tag rejects installs unless one the constraints defined by 3971 its child elements is true. 3972 It is possible to have multiple <code>install-constraints</code> tags in a single manifest, 3973 where each tag is evaluated independently. 3974 @hide --> 3975 <declare-styleable name="AndroidManifestInstallConstraints" parent="AndroidManifest" /> 3976 3977 <!-- A constraint for <code>install-constraints</code>. Checks that the device fingerprint 3978 starts with the given prefix. 3979 @hide --> 3980 <declare-styleable name="AndroidManifestInstallConstraintsFingerprintPrefix" 3981 parent="AndroidManifestInstallConstraints"> 3982 <attr name="value" /> 3983 </declare-styleable> 3984</resources> 3985