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