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