在Android应用开发中会遇到各种奇怪的属性标签并且由于网上相关资料较少因此无法查询到相关含义因此将frameworks/base/core/res/res/values/attrs_manifest.xml属性定义文件黏贴自此以便后期查阅,后期若时间充足也会对注释部分进翻译
<?xml version="1.0" encoding="utf-8"?> <!-- /* Copyright 2006, The Android Open Source Project ** ** Licensed under the Apache License, Version 2.0 (the "License"); ** you may not use this file except in compliance with the License. ** You may obtain a copy of the License at ** ** http://www.apache.org/licenses/LICENSE-2.0 ** ** Unless required by applicable law or agreed to in writing, software ** distributed under the License is distributed on an "AS IS" BASIS, ** WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. ** See the License for the specific language governing permissions and ** limitations under the License. */ --> <resources> <!-- **************************************************************** --> <!-- These are the attributes used in AndroidManifest.xml. --> <!-- **************************************************************** --> <eat-comment /> <!-- The overall theme to use for an activity. Use with either the application tag (to supply a default theme for all activities) or the activity tag (to supply a specific theme for that activity). <p>This automatically sets your activity's Context to use this theme, and may also be used for "starting" animations prior to the activity being launched (to better match what the activity actually looks like). It is a reference to a style resource defining the theme. If not set, the default system theme will be used. --> <attr name="theme" format="reference" /> <!-- A user-legible name for the given item. Use with the application tag (to supply a default label for all application components), or with the activity, receiver, service, or instrumentation tag (to supply a specific label for that component). It may also be used with the intent-filter tag to supply a label to show to the user when an activity is being selected based on a particular Intent. <p>The given label will be used wherever the user sees information about its associated component; for example, as the name of a main activity that is displayed in the launcher. You should generally set this to a reference to a string resource, so that it can be localized, however it is also allowed to supply a plain string for quick and dirty programming. --> <attr name="label" format="reference|string" /> <!-- A Drawable resource providing a graphical representation of its associated item. Use with the application tag (to supply a default icon for all application components), or with the activity, receiver, service, or instrumentation tag (to supply a specific icon for that component). It may also be used with the intent-filter tag to supply an icon to show to the user when an activity is being selected based on a particular Intent. <p>The given icon will be used to display to the user a graphical representation of its associated component; for example, as the icon for main activity that is displayed in the launcher. This must be a reference to a Drawable resource containing the image definition. --> <attr name="icon" format="reference" /> <!-- A Drawable resource providing a graphical representation of its associated item. Use with the application tag (to supply a default round icon for all application components), or with the activity, receiver, service, or instrumentation tag (to supply a specific round icon for that component). It may also be used with the intent-filter tag to supply a round icon to show to the user when an activity is being selected based on a particular Intent. <p>The given round icon will be used to display to the user a graphical representation of its associated component; for example, as the round icon for main activity that is displayed in the launcher. This must be a reference to a Drawable resource containing the image definition. --> <attr name="roundIcon" format="reference" /> <!-- A Drawable resource providing an extended graphical banner for its associated item. Use with the application tag (to supply a default banner for all application activities), or with the activity, tag to supply a banner for a specific activity. <p>The given banner will be used to display to the user a graphical representation of an activity in the Leanback application launcher. Since banners are displayed only in the Leanback launcher, they should only be used with activities (and applications) that support Leanback mode. These are activities that handle Intents of category {@link android.content.Intent#CATEGORY_LEANBACK_LAUNCHER Intent.CATEGORY_LEANBACK_LAUNCHER}. <p>This must be a reference to a Drawable resource containing the image definition. --> <attr name="banner" format="reference" /> <!-- A Drawable resource providing an extended graphical logo for its associated item. Use with the application tag (to supply a default logo for all application components), or with the activity, receiver, service, or instrumentation tag (to supply a specific logo for that component). It may also be used with the intent-filter tag to supply a logo to show to the user when an activity is being selected based on a particular Intent. <p>The given logo will be used to display to the user a graphical representation of its associated component; for example as the header in the Action Bar. The primary differences between an icon and a logo are that logos are often wider and more detailed, and are used without an accompanying text caption. This must be a reference to a Drawable resource containing the image definition. --> <attr name="logo" format="reference" /> <!-- Name of the activity to be launched to manage application's space on device. The specified activity gets automatically launched when the application's space needs to be managed and is usually invoked through user actions. Applications can thus provide their own custom behavior for managing space for various scenarios like out of memory conditions. This is an optional attribute and applications can choose not to specify a default activity to manage space. --> <attr name="manageSpaceActivity" format="string" /> <!-- Option to let applications specify that user data can/cannot be cleared. This flag is turned on by default. <p>Starting from API level 29 this flag only controls if the user can clear app data from Settings. To control clearing the data after a failed restore use allowClearUserDataOnFailedRestore flag. <p><em>This attribute is usable only by applications included in the system image. Third-party apps cannot use it.</em> --> <attr name="allowClearUserData" format="boolean" /> <!-- Option to indicate this application is only for testing purposes. For example, it may expose functionality or data outside of itself that would cause a security hole, but is useful for testing. This kind of application can not be installed without the INSTALL_ALLOW_TEST flag, which means only through adb install. --> <attr name="testOnly" format="boolean" /> <!-- A unique name for the given item. This must use a Java-style naming convention to ensure the name is unique, for example "com.mycompany.MyName". --> <attr name="name" format="string" /> <!-- Specify a permission that a client is required to have in order to use the associated object. If the client does not hold the named permission, its request will fail. See the <a href="{@docRoot}guide/topics/security/security.html">Security and Permissions</a> document for more information on permissions. --> <attr name="permission" format="string" /> <!-- A specific {@link android.R.attr#permission} name for read-only access to a {@link android.content.ContentProvider}. See the <a href="{@docRoot}guide/topics/security/security.html">Security and Permissions</a> document for more information on permissions. --> <attr name="readPermission" format="string" /> <!-- A specific {@link android.R.attr#permission} name for write access to a {@link android.content.ContentProvider}. See the <a href="{@docRoot}guide/topics/security/security.html">Security and Permissions</a> document for more information on permissions. --> <attr name="writePermission" format="string" /> <!-- If true, the {@link android.content.Context#grantUriPermission Context.grantUriPermission} or corresponding Intent flags can be used to allow others to access specific URIs in the content provider, even if they do not have an explicit read or write permission. If you are supporting this feature, you must be sure to call {@link android.content.Context#revokeUriPermission Context.revokeUriPermission} when URIs are deleted from your provider.--> <attr name="grantUriPermissions" format="boolean" /> <!-- If true, the system will always create URI permission grants in the cases where {@link android.content.Intent#FLAG_GRANT_READ_URI_PERMISSION} or {@link android.content.Intent#FLAG_GRANT_WRITE_URI_PERMISSION} would apply. This is useful for a content provider that dynamically enforces permissions on calls in to the provider, instead of through the manifest: the system needs to know that it should always apply permission grants, even if it looks like the target of the grant would already have access to the URI. --> <attr name="forceUriPermissions" format="boolean" /> <!-- Characterizes the potential risk implied in a permission and indicates the procedure the system should follow when determining whether to grant the permission to an application requesting it. {@link android.Manifest.permission Standard permissions} have a predefined and permanent protectionLevel. If you are creating a custom permission in an application, you can define a protectionLevel attribute with one of the values listed below. If no protectionLevel is defined for a custom permission, the system assigns the default ("normal"). <p>Each protection level consists of a base permission type and zero or more flags. Use the following functions to extract those. <pre> int basePermissionType = permissionInfo.getProtection(); int permissionFlags = permissionInfo.getProtectionFlags(); </pre> --> <attr name="protectionLevel"> <!-- <strong>Base permission type</strong>: a lower-risk permission that gives an application access to isolated application-level features, with minimal risk to other applications, the system, or the user. The system automatically grants this type of permission to a requesting application at installation, without asking for the user's explicit approval (though the user always has the option to review these permissions before installing). --> <flag name="normal" value="0" /> <!-- <strong>Base permission type</strong>: a higher-risk permission that would give a requesting application access to private user data or control over the device that can negatively impact the user. Because this type of permission introduces potential risk, the system may not automatically grant it to the requesting application. For example, any dangerous permissions requested by an application may be displayed to the user and require confirmation before proceeding, or some other approach may be taken to avoid the user automatically allowing the use of such facilities. --> <flag name="dangerous" value="1" /> <!-- <strong>Base permission type</strong>: a permission that the system is to grant only if the requesting application is signed with the same certificate as the application that declared the permission. If the certificates match, the system automatically grants the permission without notifying the user or asking for the user's explicit approval. --> <flag name="signature" value="2" /> <!-- Old synonym for "signature|privileged". Deprecated in API level 23. Base permission type: a permission that the system is to grant only to packages in the Android system image <em>or</em> that are signed with the same certificates. Please avoid using this option, as the signature protection level should be sufficient for most needs and works regardless of exactly where applications are installed. This permission is used for certain special situations where multiple vendors have applications built in to a system image which need to share specific features explicitly because they are being built together. --> <flag name="signatureOrSystem" value="3" /> <!-- Additional flag from base permission type: this permission can also be granted to any applications installed as privileged apps on the system image. Please avoid using this option, as the signature protection level should be sufficient for most needs and works regardless of exactly where applications are installed. This permission flag is used for certain special situations where multiple vendors have applications built in to a system image which need to share specific features explicitly because they are being built together. --> <flag name="privileged" value="0x10" /> <!-- Old synonym for "privileged". Deprecated in API level 23. --> <flag name="system" value="0x10" /> <!-- Additional flag from base permission type: this permission can also (optionally) be granted to development applications. --> <flag name="development" value="0x20" /> <!-- Additional flag from base permission type: this permission is closely associated with an app op for controlling access. --> <flag name="appop" value="0x40" /> <!-- Additional flag from base permission type: this permission can be automatically granted to apps that target API levels below {@link android.os.Build.VERSION_CODES#M} (before runtime permissions were introduced). --> <flag name="pre23" value="0x80" /> <!-- Additional flag from base permission type: this permission can be automatically granted to system apps that install packages. --> <flag name="installer" value="0x100" /> <!-- Additional flag from base permission type: this permission can be automatically granted to system apps that verify packages. --> <flag name="verifier" value="0x200" /> <!-- Additional flag from base permission type: this permission can be automatically granted any application pre-installed on the system image (not just privileged apps). --> <flag name="preinstalled" value="0x400" /> <!-- Additional flag from base permission type: this permission can be automatically granted to the setup wizard app --> <flag name="setup" value="0x800" /> <!-- Additional flag from base permission type: this permission can be granted to instant apps --> <flag name="instant" value="0x1000" /> <!-- Additional flag from base permission type: this permission can only be granted to apps that target runtime permissions ({@link android.os.Build.VERSION_CODES#M} and above) --> <flag name="runtime" value="0x2000" /> <!-- Additional flag from base permission type: this permission can be granted only if its protection level is signature, the requesting app resides on the OEM partition, and the OEM has white-listed the app to receive this permission by the OEM. --> <flag name="oem" value="0x4000" /> <!-- Additional flag from base permission type: this permission can be granted to privileged apps in vendor partition. --> <flag name="vendorPrivileged" value="0x8000" /> <!-- Additional flag from base permission type: this permission can be automatically granted to the system default text classifier --> <flag name="textClassifier" value="0x10000" /> <!-- Additional flag from base permission type: this permission will be granted to the wellbeing app, as defined by the OEM. --> <flag name="wellbeing" value="0x20000" /> <!-- Additional flag from base permission type: this permission can be automatically granted to the document manager --> <flag name="documenter" value="0x40000" /> <!-- Additional flag from base permission type: this permission automatically granted to device configurator --> <flag name="configurator" value="0x80000" /> <!-- Additional flag from base permission type: this permission designates the app that will approve the sharing of incident reports. --> <flag name="incidentReportApprover" value="0x100000" /> <!-- Additional flag from base permission type: this permission can be automatically granted to the system app predictor --> <flag name="appPredictor" value="0x200000" /> <!-- Additional flag from base permission type: this permission can be automatically granted to the system companion device manager service --> <flag name="companion" value="0x800000" /> <!-- Additional flag from base permission type: this permission will be granted to the retail demo app, as defined by the OEM. --> <flag name="retailDemo" value="0x1000000" /> </attr> <!-- Flags indicating more context for a permission group. --> <attr name="permissionGroupFlags"> <!-- Set to indicate that this permission group contains permissions protecting access to some information that is considered personal to the user (such as contacts, e-mails, etc). --> <flag name="personalInfo" value="0x0001" /> </attr> <!-- Flags indicating more context for a permission. --> <attr name="permissionFlags"> <!-- Set to indicate that this permission allows an operation that may cost the user money. Such permissions may be highlighted when shown to the user with this additional information. --> <flag name="costsMoney" value="0x1" /> <!-- Additional flag from base permission type: this permission has been removed and it is no longer enforced. It shouldn't be shown in the UI. Removed permissions are kept as normal permissions for backwards compatibility as apps may be checking them before calling an API. --> <flag name="removed" value="0x2" /> <!-- This permission is restricted by the platform and it would be grantable only to apps that meet special criteria per platform policy. --> <flag name="hardRestricted" value="0x4" /> <!-- This permission is restricted by the platform and it would be grantable in its full form to apps that meet special criteria per platform policy. Otherwise, a weaker form of the permission would be granted. The weak grant depends on the permission. <p>What weak grant means is described in the documentation of the permissions. --> <flag name="softRestricted" value="0x8" /> <!-- This permission is restricted immutably which means that its restriction state may be specified only on the first install of the app and will stay in this initial whitelist state until the app is uninstalled. --> <flag name="immutablyRestricted" value="0x10" /> </attr> <!-- Specified the name of a group that this permission is associated with. The group must have been defined with the {@link android.R.styleable#AndroidManifestPermissionGroup permission-group} tag. --> <attr name="permissionGroup" format="string" /> <!-- Specify the name of a user ID that will be shared between multiple packages. By default, each package gets its own unique user-id. By setting this value on two or more packages, each of these packages will be given a single shared user ID, so they can for example run in the same process. Note that for them to actually get the same user ID, they must also be signed with the same signature. @deprecated Shared user IDs cause non-deterministic behavior within the package manager. As such, its use is strongly discouraged and may be removed in a future version of Android. Instead, apps should use proper communication mechanisms, such as services and content providers, to facilitate interoperability between shared components. --> <attr name="sharedUserId" format="string" /> <!-- Specify a label for the shared user UID of this package. This is only used if you have also used android:sharedUserId. This must be a reference to a string resource; it can not be an explicit string. @deprecated There is no replacement for this attribute. {@link android.R.attr#sharedUserId} has been deprecated making this attribute unnecessary. --> <attr name="sharedUserLabel" format="reference" /> <!-- Internal version code. This is the number used to determine whether one version is more recent than another: it has no other meaning than that higher numbers are more recent. You could use this number to encode a "x.y" in the lower and upper 16 bits, make it a build number, simply increase it by one each time a new version is released, or define it however else you want, as long as each successive version has a higher number. This is not a version number generally shown to the user, that is usually supplied with {@link android.R.attr#versionName}. When an app is delivered as multiple split APKs, each APK must have the exact same versionCode. --> <attr name="versionCode" format="integer" /> <!-- Internal major version code. This is essentially additional high bits for the base version code; it has no other meaning than that higher numbers are more recent. This is not a version number generally shown to the user, that is usually supplied with {@link android.R.attr#versionName}. --> <attr name="versionCodeMajor" format="integer" /> <!-- Internal revision code. This number is the number used to determine whether one APK is more recent than another: it has no other meaning than that higher numbers are more recent. This value is only meaningful when the two {@link android.R.attr#versionCode} values are already identical. When an app is delivered as multiple split APKs, each APK may have a different revisionCode value. --> <attr name="revisionCode" format="integer" /> <!-- The text shown to the user to indicate the version they have. This is used for no other purpose than display to the user; the actual significant version number is given by {@link android.R.attr#versionCode}. --> <attr name="versionName" format="string" /> <!-- Flag to control special persistent mode of an application. This should not normally be used by applications; it requires that the system keep your application running at all times. --> <attr name="persistent" format="boolean" /> <!-- If set, the "persistent" attribute will only be honored if the feature specified here is present on the device. --> <attr name="persistentWhenFeatureAvailable" format="string" /> <!-- Flag to specify if this application needs to be present for all users. Only pre-installed applications can request this feature. Default value is false. --> <attr name="requiredForAllUsers" format="boolean" /> <!-- Flag indicating whether the application can be debugged, even when running on a device that is running in user mode. --> <attr name="debuggable" format="boolean" /> <!-- Flag indicating whether the application requests the VM to operate in the safe mode. --> <attr name="vmSafeMode" format="boolean" /> <!-- <p>Flag indicating whether the application's rendering should be hardware accelerated if possible. This flag is turned on by default for applications that are targeting {@link android.os.Build.VERSION_CODES#ICE_CREAM_SANDWICH} or later.</p> <p>This flag can be set on the application and any activity declared in the manifest. When enabled for the application, each activity is automatically assumed to be hardware accelerated. This flag can be overridden in the activity tags, either turning it off (if on for the application) or on (if off for the application.)</p> <p>When this flag is turned on for an activity (either directly or via the application tag), every window created from the activity, including the activity's own window, will be hardware accelerated, if possible.</p> <p>Please refer to the documentation of {@link android.view.WindowManager.LayoutParams#FLAG_HARDWARE_ACCELERATED} for more information on how to control this flag programmatically.</p> --> <attr name="hardwareAccelerated" format="boolean" /> <!-- Flag indicating whether the given application component is available to other applications. If false, it can only be accessed by applications with its same user id (which usually means only by code in its own package). If true, it can be invoked by external entities, though which ones can do so may be controlled through permissions. The default value is false for activity, receiver, and service components that do not specify any intent filters; it is true for activity, receiver, and service components that do have intent filters (implying they expect to be invoked by others who do not know their particular component name) and for all content providers. --> <attr name="exported" format="boolean" /> <!-- A boolean flag used to indicate if an application is a Game or not. <p>This information can be used by the system to group together applications that are classified as games, and display them separately from the other applications. --> <attr name="isGame" format="boolean" /> <!-- If set to true, a single instance of this component will run for all users. That instance will run as user 0, the default/primary user. When the app running is in processes for other users and interacts with this component (by binding to a service for example) those processes will always interact with the instance running for user 0. Enabling single user mode forces "exported" of the component to be false, to help avoid introducing multi-user security bugs. This feature is only available to applications built in to the system image; you must hold the permission INTERACT_ACROSS_USERS in order to use this feature. This flag can only be used with services, receivers, and providers; it can not be used with activities. --> <attr name="singleUser" format="boolean" /> <!-- Specify a specific process that the associated code is to run in. Use with the application tag (to supply a default process for all application components), or with the activity, receiver, service, or provider tag (to supply a specific icon for that component). <p>Application components are normally run in a single process that is created for the entire application. You can use this tag to modify where they run. If the process name begins with a ':' character, a new process private to that application will be created when needed to run that component (allowing you to spread your application across multiple processes). If the process name begins with a lower-case character, the component will be run in a global process of that name, provided that you have permission to do so, allowing multiple applications to share one process to reduce resource usage. --> <attr name="process" format="string" /> <!-- Specify a task name that activities have an "affinity" to. Use with the application tag (to supply a default affinity for all activities in the application), or with the activity tag (to supply a specific affinity for that component). <p>The default value for this attribute is the same as the package name, indicating that all activities in the manifest should generally be considered a single "application" to the user. You can use this attribute to modify that behavior: either giving them an affinity for another task, if the activities are intended to be part of that task from the user's perspective, or using an empty string for activities that have no affinity to a task. --> <attr name="taskAffinity" format="string" /> <!-- Specify that an activity can be moved out of a task it is in to the task it has an affinity for when appropriate. Use with the application tag (to supply a default for all activities in the application), or with an activity tag (to supply a specific setting for that component). <p>Normally when an application is started, it is associated with the task of the activity that started it and stays there for its entire lifetime. You can use the allowTaskReparenting feature to force an activity to be re-parented to a different task when the task it is in goes to the background. Typically this is used to cause the activities of an application to move back to the main task associated with that application. The activity is re-parented to the task with the same {@link android.R.attr#taskAffinity} as it has. --> <attr name="allowTaskReparenting" format="boolean" /> <!-- Declare that this application may use cleartext traffic, such as HTTP rather than HTTPS; WebSockets rather than WebSockets Secure; XMPP, IMAP, STMP without STARTTLS or TLS. Defaults to true. If set to false {@code false}, the application declares that it does not intend to use cleartext network traffic, in which case platform components (e.g. HTTP stacks, {@code DownloadManager}, {@code MediaPlayer}) will refuse applications's requests to use cleartext traffic. Third-party libraries are encouraged to honor this flag as well. --> <attr name="usesCleartextTraffic" format="boolean" /> <!-- Declare that code from this application will need to be loaded into other applications' processes. On devices that support multiple instruction sets, this implies the code might be loaded into a process that's using any of the devices supported instruction sets. <p> The system might treat such applications specially, for eg., by extracting the application's native libraries for all supported instruction sets or by compiling the application's dex code for all supported instruction sets. --> <attr name="multiArch" format ="boolean" /> <!-- Specify whether the 32 bit version of the ABI should be used in a multiArch application. If both abioverride flag (i.e. using abi option of abd install) and use32bitAbi are used, then use32bit is ignored.--> <attr name="use32bitAbi" /> <!-- Specify whether a component is allowed to have multiple instances of itself running in different processes. Use with the activity and provider tags. <p>Normally the system will ensure that all instances of a particular component are only running in a single process. You can use this attribute to disable that behavior, allowing the system to create instances wherever they are used (provided permissions allow it). This is most often used with content providers, so that instances of a provider can be created in each client process, allowing them to be used without performing IPC. --> <attr name="multiprocess" format="boolean" /> <!-- Specify whether an activity should be finished when its task is brought to the foreground by relaunching from the home screen. <p>If both this option and {@link android.R.attr#allowTaskReparenting} are specified, the finish trumps the affinity: the affinity will be ignored and the activity simply finished. --> <attr name="finishOnTaskLaunch" format="boolean" /> <!-- Specify whether an activity should be finished when a "close system windows" request has been made. This happens, for example, when the home key is pressed, when the device is locked, when a system dialog showing recent applications is displayed, etc. --> <attr name="finishOnCloseSystemDialogs" format="boolean" /> <!-- Specify whether an activity's task should be cleared when it is re-launched from the home screen. As a result, every time the user starts the task, they will be brought to its root activity, regardless of whether they used BACK or HOME to last leave it. This flag only applies to activities that are used to start the root of a new task. <p>An example of the use of this flag would be for the case where a user launches activity A from home, and from there goes to activity B. They now press home, and then return to activity A. Normally they would see activity B, since that is what they were last doing in A's task. However, if A has set this flag to true, then upon going to the background all of the tasks on top of it (B in this case) are removed, so when the user next returns to A they will restart at its original activity. <p>When this option is used in conjunction with {@link android.R.attr#allowTaskReparenting}, the allowTaskReparenting trumps the clear. That is, all activities above the root activity of the task will be removed: those that have an affinity will be moved to the task they are associated with, otherwise they will simply be dropped as described here. --> <attr name="clearTaskOnLaunch" format="boolean" /> <!-- Specify whether an activity should be kept in its history stack. If this attribute is set, then as soon as the user navigates away from the activity it will be finished and they will no longer be able to return to it. --> <attr name="noHistory" format="boolean" /> <!-- Specify whether an acitivty's task state should always be maintained by the system, or if it is allowed to reset the task to its initial state in certain situations. <p>Normally the system will reset a task (remove all activities from the stack and reset the root activity) in certain situations when the user re-selects that task from the home screen. Typically this will be done if the user hasn't visited that task for a certain amount of time, such as 30 minutes. <p>By setting this attribute, the user will always return to your task in its last state, regardless of how they get there. This is useful, for example, in an application like the web browser where there is a lot of state (such as multiple open tabs) that the application would not like to lose. --> <attr name="alwaysRetainTaskState" format="boolean" /> <!-- Indicates that an Activity does not need to have its freeze state (as returned by {@link android.app.Activity#onSaveInstanceState} retained in order to be restarted. Generally you use this for activities that do not store any state. When this flag is set, if for some reason the activity is killed before it has a chance to save its state, then the system will not remove it from the activity stack like it normally would. Instead, the next time the user navigates to it its {@link android.app.Activity#onCreate} method will be called with a null icicle, just like it was starting for the first time. <p>This is used by the Home activity to make sure it does not get removed if it crashes for some reason. --> <attr name="stateNotNeeded" format="boolean" /> <!-- Indicates that an Activity should be excluded from the list of recently launched activities. --> <attr name="excludeFromRecents" format="boolean" /> <!-- Specify that an Activity should be shown over the lock screen and, in a multiuser environment, across all users' windows. @deprecated use {@link android.R.attr#showForAllUsers} instead. --> <attr name="showOnLockScreen" format="boolean" /> <!-- Specify that an Activity should be shown even if the current/foreground user is different from the user of the Activity. This will also force the <code>android.view.LayoutParams.FLAG_SHOW_WHEN_LOCKEDflag to be set for all windows of this activity --> <!-- Specifies whether an {@link android.app.Activity} should be shown on top of the lock screen whenever the lockscreen is up and the activity is resumed. Normally an activity will be transitioned to the stopped state if it is started while the lockscreen is up, but with this flag set the activity will remain in the resumed state visible on-top of the lock screen.This should be used instead of {@link android.view.WindowManager.LayoutParams#FLAG_SHOW_WHEN_LOCKED} flag set for Windows. When using the Window flag during activity startup, there may not be time to add it before the system stops your activity for being behind the lock-screen. This leads to a double life-cycle as it is then restarted.
--> <!-- Specifies whether the screen should be turned on when the {@link android.app.Activity} is resumed. Normally an activity will be transitioned to the stopped state if it is started while the screen if off, but with this flag set the activity will cause the screen to turn on if the activity will be visible and resumed due to the screen coming on. The screen will not be turned on if the activity won't be visible after the screen is turned on. This flag is normally used in conjunction with the {@link android.R.attr#showWhenLocked} flag to make sure the activity is visible after the screen is turned on when the lockscreen is up. In addition, if this flag is set and the activity calls {@link android.app.KeyguardManager#requestDismissKeyguard} the screen will turn on.This should be used instead of {@link android.view.WindowManager.LayoutParams#FLAG_TURN_SCREEN_ON} flag set for Windows. When using the Window flag during activity startup, there may not be time to add it before the system stops your activity because the screen has not yet turned on. This leads to a double life-cycle as it is then restarted.
--> <!-- Specify the authorities under which this content provider can be found. Multiple authorities may be supplied by separating them with a semicolon. Authority names should use a Java-style naming convention (such ascom.google.provider.MyProvider) in order to avoid conflicts. Typically this name is the same as the class implementation describing the provider's data structure. --> <!-- Specify the relative importance or ability in handling a particular Intent. For receivers, this controls the order in which they are executed to receive a broadcast (note that for asynchronous broadcasts, this order is ignored). For activities, this provides information about how good an activity is handling an Intent; when multiple activities match an intent and have different priorities, only those with the higher priority value will be considered a match.Only use if you really need to impose some specific order in which the broadcasts are received, or want to forcibly place an activity to always be preferred over others. The value is a single integer, with higher numbers considered to be better. --> <!-- Specify how an activity should be launched. See the Tasks and Back Stack document for important information on how these options impact the behavior of your application.
If this attribute is not specified,
standardlaunch mode will be used. Note that the particular launch behavior can be changed in some ways at runtime through the {@link android.content.Intent} flags {@link android.content.Intent#FLAG_ACTIVITY_SINGLE_TOP}, {@link android.content.Intent#FLAG_ACTIVITY_NEW_TASK}, and {@link android.content.Intent#FLAG_ACTIVITY_MULTIPLE_TASK}. --> <!-- If, when starting the activity, there is already a task running that starts with this activity, then instead of starting a new instance the current task is brought to the front. The existing instance will receive a call to {@link android.app.Activity#onNewIntent Activity.onNewIntent()} with the new Intent that is being started, and with the {@link android.content.Intent#FLAG_ACTIVITY_BROUGHT_TO_FRONT Intent.FLAG_ACTIVITY_BROUGHT_TO_FRONT} flag set. This is a superset of the singleTop mode, where if there is already an instance of the activity being started at the top of the stack, it will receive the Intent as described there (without the FLAG_ACTIVITY_BROUGHT_TO_FRONT flag set). See the Tasks and Back Stack document for more details about tasks.--> <!-- Only allow one instance of this activity to ever be running. This activity gets a unique task with only itself running in it; if it is ever launched again with the same Intent, then that task will be brought forward and its {@link android.app.Activity#onNewIntent Activity.onNewIntent()} method called. If this activity tries to start a new activity, that new activity will be launched in a separate task. See the Tasks and Back Stack document for more details about tasks.--> <!-- Specify the orientation an activity should be run in. If not specified, it will run in the current preferred orientation of the screen.This attribute is supported by the {@code } element. --> <!-- Specify one or more configuration changes that the activity will handle itself. If not specified, the activity will be restarted if any of these configuration changes happen in the system. Otherwise, the activity will remain running and its {@link android.app.Activity#onConfigurationChanged Activity.onConfigurationChanged} method called with the new configuration.
Note that all of these configuration changes can impact the resource values seen by the application, so you will generally need to re-retrieve all resources (including view layouts, drawables, etc) to correctly handle any configuration change.
These values must be kept in sync with those in {@link android.content.pm.ActivityInfo} and include/utils/ResourceTypes.h. --> <!-- Indicate that the activity can be launched as the embedded child of another activity. Particularly in the case where the child lives in a container such as a Display owned by another activity.
The default value of this attribute is
false. --> <!-- Specifies whether this {@link android.app.Activity} should be shown on top of the lock screen whenever the lockscreen is up and this activity has another activity behind it with the {@link android.R.attr#showWhenLocked} attribute set. That is, this activity is only visible on the lock screen if there is another activity with the {@link android.R.attr#showWhenLocked} attribute visible at the same time on the lock screen. A use case for this is permission dialogs, that should only be visible on the lock screen if their requesting activity is also visible.The default value of this attribute is
false. --> <!-- The name of the class subclassingBackupAgentto manage backup and restore of the application's data on external storage. --> <!-- Whether to allow the application to participate in the backup and restore infrastructure. If this attribute is set tofalse, no backup or restore of the application will ever be performed, even by a full-system backup that would otherwise cause all application data to be saved via adb. The default value of this attribute istrue. --> <!-- Indicates that even though the application provides aBackupAgent, only full-data streaming backup operations are to be performed to save the app's data. This lets the app rely on full-data backups while still participating in the backup and restore process via the BackupAgent's full-data backup APIs. When this attribute istruethe app's BackupAgent overrides of the onBackup() and onRestore() callbacks can be empty stubs. --> <!-- Whether the application in question should be terminated after its settings have been restored during a full-system restore operation. Single-package restore operations will never cause the application to be shut down. Full-system restore operations typically only occur once, when the phone is first set up. Third-party applications will not usually need to use this attribute.The default is
true, which means that after the application has finished processing its data during a full-system restore, it will be terminated. --> <!-- Indicate that the application is prepared to attempt a restore of any backed-up dataset, even if the backup is apparently from a newer version of the application than is currently installed on the device. Setting this attribute totruewill permit the Backup Manager to attempt restore even when a version mismatch suggests that the data are incompatible. Use with caution!The default value of this attribute is
false. --> <!-- Indicates that full-data backup operations for this application may be performed even if the application is in a foreground-equivalent state. Use with caution! Setting this flag totruecan impact app behavior while the user is interacting with the device.If unspecified, the default value of this attribute is
false, which means that the OS will avoid backing up the application while it is running in the foreground (such as a music app that is actively playing music via a service in the startForeground() state). --> <!-- If set totrue, indicates to the platform that any split APKs installed for this application should be loaded into their own Context objects and not appear in the base application's Context.The default value of this attribute is
false. --> <!-- The classname of the classloader used to load the application's classes from its APK. The APK in question can either be the 'base' APK or any of the application's 'split' APKs if it's using a feature split.The supported values for this attribute are
dalvik.system.PathClassLoaderanddalvik.system.DelegateLastClassLoader. If unspecified, the default value of this attribute isdalvik.system.PathClassLoader. If an unknown classloader is provided, a PackageParserException with causePackageManager.INSTALL_PARSE_FAILED_MANIFEST_MALFORMEDwill be thrown and the app will not be installed. --> <!-- Name of the class that gets invoked for preloading application code, when starting an {@link android.R.attr#isolatedProcess} service that has {@link android.R.attr#useAppZygote} set totrue. This is a fully qualified class name (for example, com.mycompany.myapp.MyZygotePreload); as a short-hand if the first character of the class is a period then it is appended to your package name. The class must implement the {@link android.app.ZygotePreload} interface. --> <!-- If set totrue, indicates to the platform that this APK is a 'feature' split and that it implicitly depends on the base APK. This distinguishes this split APK from a 'configuration' split, which provides resource overrides for a particular 'feature' split. Only useful when the base APK specifiesandroid:isolatedSplits="true".The default value of this attribute is
false. --> <!-- Extra options for an activity's UI. Applies to either the {@code } or {@code } tag. If specified on the {@code } tag these will be considered defaults for all activities in the application. --> <!-- If this activity forms the root of a task then the task and this activity will be persisted across reboots. If the activity above this activity is also tagged with the attribute"persist"then it will be persisted as well. And so on up the task stack until either an activity without thepersistableMode="persistAcrossReboots"attribute or one that was launched with the flag Intent.FLAG_CLEAR_TASK_WHEN_RESET is encountered.Activities that are declared with the persistAcrossReboots attribute will be provided with a PersistableBundle in onSavedInstanceState(), These activities may use this PeristableBundle to save their state. Then, following a reboot, that PersistableBundle will be provided back to the activity in its onCreate() method. --> <!-- This attribute specifies that an activity shall become the root activity of a new task each time it is launched. Using this attribute permits the user to have multiple documents from the same applications appear in the recent tasks list.
Such a document is any kind of item for which an application may want to maintain multiple simultaneous instances. Examples might be text files, web pages, spreadsheets, or emails. Each such document will be in a separate task in the recent taskss list.
This attribute is equivalent to adding the flag {@link android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT} to every Intent used to launch the activity.
The documentLaunchMode attribute may be assigned one of four values, "none", "intoExisting", "always" and "never", described in detail below. For values other than
noneandneverthe activity must be defined with {@link android.R.attr#launchMode}standard. If this attribute is not specified,nonewill be used. Note thatnonecan be overridden at run time if the Intent used to launch it contains the flag {@link android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT Intent.FLAG_ACTIVITY_NEW_DOCUMENT}. SimilarlyintoExistingwill be overridden by the flag {@link android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT Intent.FLAG_ACTIVITY_NEW_DOCUMENT} combined with {@link android.content.Intent#FLAG_ACTIVITY_MULTIPLE_TASK Intent.FLAG_ACTIVITY_MULTIPLE_TASK}. If the value of documentLaunchModes isneverthen any use of {@link android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT Intent.FLAG_ACTIVITY_NEW_DOCUMENT} to launch this activity will be ignored. --> <!-- All tasks will be searched for one whose base Intent's ComponentName and data URI match those of the launching Intent. If such a task is found that task will be cleared and restarted with the root activity receiving a call to {@link android.app.Activity#onNewIntent Activity.onNewIntent}. If no such task is found a new task will be created.This is the equivalent of launching an activity with {@link android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT Intent.FLAG_ACTIVITY_NEW_DOCUMENT} set and without {@link android.content.Intent#FLAG_ACTIVITY_MULTIPLE_TASK Intent.FLAG_ACTIVITY_MULTIPLE_TASK} set. --> <!-- This activity will not be launched into a new document even if the Intent contains {@link android.content.Intent#FLAG_ACTIVITY_NEW_DOCUMENT Intent.FLAG_ACTIVITY_NEW_DOCUMENT}. This gives the activity writer ultimate control over how their activity is used. Note that applications prior to api 21 will default to documentLaunchMode="none" so only activities that explicitly opt out with
"never"may do so. --> <!-- Tasks whose root has this attribute set to true will replace baseIntent with that of the next activity in the task. If the next activity also has this attribute set to true then it will yield the baseIntent to any activity that it launches in the same task. This continues until an activity is encountered which has this attribute set to false. False is the default. This attribute set to true also permits activity's use of the TaskDescription to change labels, colors and icons in the recent task list.NOTE: Setting this flag to
truewill not change the affinity of the task, which is used for intent resolution during activity launch. The task's root activity will always define its affinity. --> <!-- Indicate that it is okay for this activity be resumed while the previous activity is in the process of pausing, without waiting for the previous pause to complete. Use this with caution: your activity can not acquire any exclusive resources (such as opening the camera or recording audio) when it launches, or it may conflict with the previous activity and fail.The default value of this attribute is
false. --> <!-- Indicates that it is okay for this activity to be put in multi-window mode. Intended for a multi-window device where there can be multiple activities of various sizes on the screen at the same time.The default value is
falsefor applications withtargetSdkVersionlesser than {@link android.os.Build.VERSION_CODES#N} andtrueotherwise.Setting this flag to
falselets the system know that the app may not be tested or optimized for multi-window environment. The system may still put such activity in multi-window with compatibility mode applied. It also does not guarantee that there will be no other apps in multi-window visible on screen (e.g. picture-in-picture) or on other displays. Therefore, this flag cannot be used to assure an exclusive resource access.NOTE: A task's root activity value is applied to all additional activities launched in the task. That is if the root activity of a task is resizeable then the system will treat all other activities in the task as resizeable and will not if the root activity isn't resizeable.
NOTE: The value of {@link android.R.attr#screenOrientation} is ignored for resizeable activities when in multi-window mode. --> <!-- Indicates that the activity specifically supports the picture-in-picture form of multi-window. If true, this activity will support entering picture-in-picture, but will only support split-screen and other forms of multi-window if {@link android.R.attr#resizeableActivity} is also set to true. Note that your activity may still be resized even if this attribute is true and {@link android.R.attr#resizeableActivity} is false.
The default value is
false. --> <!-- This value indicates the maximum aspect ratio the activity supports. If the app runs on a device with a wider aspect ratio, the system automatically letterboxes the app, leaving portions of the screen unused so the app can run at its specified maximum aspect ratio.Maximum aspect ratio, expressed as (longer dimension / shorter dimension) in decimal form. For example, if the maximum aspect ratio is 7:3, set value to 2.33.
Value needs to be greater or equal to 1.0, otherwise it is ignored.
NOTE: This attribute is ignored if the activity has {@link android.R.attr#resizeableActivity} set to true. --> <!-- This value indicates the minimum aspect ratio the activity supports. If the app runs on a device with a narrower aspect ratio, the system automatically letterboxes the app, leaving portions of the screen unused so the app can run at its specified minimum aspect ratio.
Minimum aspect ratio, expressed as (longer dimension / shorter dimension) in decimal form. For example, if the minimum aspect ratio is 4:3, set value to 1.33.
Value needs to be greater or equal to 1.0, otherwise it is ignored.
NOTE: This attribute is ignored if the activity has {@link android.R.attr#resizeableActivity} set to true. --> <!-- This value indicates how tasks rooted at this activity will behave in lockTask mode. While in lockTask mode the system will not launch non-permitted tasks until lockTask mode is disabled.
While in lockTask mode with multiple permitted tasks running, each launched task is permitted to finish, transitioning to the previous locked task, until there is only one task remaining. At that point the last task running is not permitted to finish, unless it uses the value always. --> <!-- This is the default value. Tasks will not launch into lockTask mode but can be placed there by calling {@link android.app.Activity#startLockTask}. If a task with this mode has been whitelisted using {@link android.app.admin.DevicePolicyManager#setLockTaskPackages} then calling {@link android.app.Activity#startLockTask} will enter lockTask mode immediately, otherwise the user will be presented with a dialog to approve entering pinned mode.
If the system is already in lockTask mode when a new task rooted at this activity is launched that task will or will not start depending on whether the package of this activity has been whitelisted.
Tasks rooted at this activity can only exit lockTask mode using {@link android.app.Activity#stopLockTask}. --> <!-- Tasks will not launch into lockTask mode and cannot be placed there using {@link android.app.Activity#startLockTask} or be pinned from the Overview screen. If the system is already in lockTask mode when a new task rooted at this activity is launched that task will not be started.
Note: This mode is only available to system and privileged applications. Non-privileged apps with this value will be treated as normal. --> <!-- Tasks rooted at this activity will always launch into lockTask mode. If the system is already in lockTask mode when this task is launched then the new task will be launched on top of the current task. Tasks launched in this mode are capable of exiting lockTask mode using {@link android.app.Activity#finish()}.
Note: This mode is only available to system and privileged applications. Non-privileged apps with this value will be treated as normal. --> <!-- Specify whether an activity intent filter will need to be verified thru its set of data URIs. This will only be used when the Intent's action is set to {@link android.content.Intent#ACTION_VIEW Intent.ACTION_VIEW} and the Intent's category is set to {@link android.content.Intent#CATEGORY_BROWSABLE Intent.CATEGORY_BROWSABLE} and the intern filter data scheme is set to "http" or "https". When set to true, the intent filter will need to use its data tag for getting the URIs to verify with. For each URI, an HTTPS network request will be done to
/.well-known/statements.jsonhost to verify that the web site is okay with the app intercepting the URI. --> <!-- Specifies the target sandbox this app wants to use. Higher sandbox versions will have increasing levels of security.The default value of this attribute is
1.@deprecated The security properties have been moved to {@link android.os.Build.VERSION Build.VERSION} 27 and 28. --> <!-- The user-visible SDK version (ex. 26) of the framework against which the application was compiled. This attribute is automatically specified by the Android build tools and should NOT be manually specified.
This attribute is the compile-time equivalent of {@link android.os.Build.VERSION#SDK_INT Build.VERSION.SDK_INT}. --> <!-- The development codename (ex. "O") of the framework against which the application was compiled, or "REL" if the application was compiled against a release build. This attribute is automatically specified by the Android build tools and should NOT be manually specified.
This attribute is the compile-time equivalent of {@link android.os.Build.VERSION#CODENAME Build.VERSION.CODENAME}. --> <!-- Use the camera device or record video.
For apps with
targetSdkVersion{@link android.os.Build.VERSION_CODES#R} and above, a foreground service will not be able to access the camera if this type is not specified in the manifest and in {@link android.app.Service#startForeground(int, android.app.Notification, int)}. --> <!--Use the microphone device or record audio.For apps with
targetSdkVersion{@link android.os.Build.VERSION_CODES#R} and above, a foreground service will not be able to access the microphone if this type is not specified in the manifest and in {@link android.app.Service#startForeground(int, android.app.Notification, int)}. --> <!-- Enable sampled memory bug detection in this process. When enabled, a very small, random subset of native memory allocations are protected with guard pages, providing an ASan-like error report in case of a memory corruption bug. GWP-ASan is a recursive acronym. It stands for “GWP-ASan Will Provide Allocation SANity”. See the LLVM documentation for more information about this feature.This attribute can be applied to a {@link android.R.styleable#AndroidManifestProcess process} tag, or to an {@link android.R.styleable#AndroidManifestApplication application} tag (to supply a default setting for all application components). --> <!-- The
manifesttag is the root of anAndroidManifest.xmlfile, describing the contents of an Android package (.apk) file. One attribute must always be supplied:packagegives a unique name for the package, using a Java-style naming convention to avoid name collisions. For example, applications published by Google could have names of the formcom.google.app.<em>appname</em>Inside of the manifest tag, may appear the following tags in any order: {@link #AndroidManifestAttribution attribution}, {@link #AndroidManifestPermission permission}, {@link #AndroidManifestPermissionGroup permission-group}, {@link #AndroidManifestPermissionTree permission-tree}, {@link #AndroidManifestUsesSdk uses-sdk}, {@link #AndroidManifestUsesPermission uses-permission}, {@link #AndroidManifestUsesConfiguration uses-configuration}, {@link #AndroidManifestApplication application}, {@link #AndroidManifestInstrumentation instrumentation}, {@link #AndroidManifestUsesFeature uses-feature}. --> <!-- The
applicationtag describes application-level components contained in the package, as well as general application attributes. Many of the attributes you can supply here (such as theme, label, icon, permission, process, taskAffinity, and allowTaskReparenting) serve as default values for the corresponding attributes of components declared inside of the application.Inside of this element you specify what the application contains, using the elements {@link #AndroidManifestProvider provider}, {@link #AndroidManifestService service}, {@link #AndroidManifestReceiver receiver}, {@link #AndroidManifestActivity activity}, {@link #AndroidManifestActivityAlias activity-alias}, {@link #AndroidManifestUsesLibrary uses-library}, {@link #AndroidManifestUsesStaticLibrary uses-static-library}, and {@link #AndroidManifestUsesPackage uses-package}. The application tag appears as a child of the root {@link #AndroidManifest manifest} tag in an application's manifest file. --> <!-- Request that your application's processes be created with a large Dalvik heap. This applies to all processes created for the application. It only applies to the first application loaded into a process; if using a sharedUserId to allow multiple applications to use a process, they all must use this option consistently or will get unpredictable results. --> <!-- If {@code true} the system will clear app's data if a restore operation fails. This flag is turned on by default. This attribute is usable only by system apps. --> <!-- If {@code true} the app's non sensitive audio can be captured by other apps with {@link android.media.AudioPlaybackCaptureConfiguration} and a {@link android.media.projection.MediaProjection}. If {@code false} the audio played by the application will never be captured by non system apps. It is equivalent to limiting {@link android.media.AudioManager#setAllowedCapturePolicy(int)} to {@link android.media.AudioAttributes#ALLOW_CAPTURE_BY_SYSTEM}.
Non sensitive audio is defined as audio whose {@code AttributeUsage} is {@code USAGE_UNKNOWN}), {@code USAGE_MEDIA}) or {@code USAGE_GAME}). All other usages like {@code USAGE_VOICE_COMMUNICATION} will not be captured.
The default value is: - {@code true} for apps with targetSdkVersion >= 29 (Q). - {@code false} for apps with targetSdkVersion < 29.
See {@link android.media.AudioPlaybackCaptureConfiguration} for more detail. --> <!-- If {@code true} this app would like to run under the legacy storage model. Note that this may not always be respected due to policy or backwards compatibility reasons.
Apps not requesting legacy storage can continue to discover and read media belonging to other apps via {@code MediaStore}.
The default value is: - {@code false} for apps with targetSdkVersion >= 29 (Q). - {@code true} for apps with targetSdkVersion <!-- If {@code true} this app would like to preserve the legacy storage model from a previously installed version. Note that this may not always be respected due to policy or backwards compatibility reasons.
This has no effect on the first install of an app on a device. For an updating app, setting this to {@code true} will preserve the legacy behaviour configured by the {@code requestLegacyExternalStorage} flag. If on an update, this flag is set to {@code false} then the legacy access is not preserved, such an app can only have legacy access with the {@code requestLegacyExternalStorage} flag.
The default value is {@code false}. --> <!-- If {@code true} this app will receive tagged pointers to native heap allocations from functions like malloc() on compatible devices. Note that this may not always be respected due to policy or backwards compatibility reasons. See the Tagged Pointers document for more information on this feature. The default value is {@code true}. --> <!-- An attribution is a logical part of an app and is identified by a tag. E.g. a photo sharing app might include a direct messaging component. To tag certain code as belonging to an attribution, use a context created via {@link android.content.Context#createAttributionContext(String)} for any interaction with the system.
This appears as a child tag of the root {@link #AndroidManifest manifest} tag.
In case this attribution inherits from another attribution, this tag can contain one or multiple {@link #AndroidManifestAttributionInheritFrom inherit-from} tags. --> <!-- The
permissiontag declares a security permission that can be used to control access from other packages to specific components or features in your package (or other packages). See the Security and Permissions document for more information on permissions.This appears as a child tag of the root {@link #AndroidManifest manifest} tag. --> <!-- The
permission-grouptag declares a logical grouping of related permissions.Note that this tag does not declare a permission itself, only a namespace in which further permissions can be placed. See the {@link #AndroidManifestPermission } tag for more information.
This appears as a child tag of the root {@link #AndroidManifest manifest} tag. --> <!-- The
permission-treetag declares the base of a tree of permission values: it declares that this package has ownership of the given permission name, as well as all names underneath it (separated by '.'). This allows you to use the {@link android.content.pm.PackageManager#addPermission PackageManager.addPermission()} method to dynamically add new permissions under this tree.Note that this tag does not declare a permission itself, only a namespace in which further permissions can be placed. See the {@link #AndroidManifestPermission } tag for more information.
This appears as a child tag of the root {@link #AndroidManifest manifest} tag. --> <!-- The
uses-permissiontag requests a {@link #AndroidManifestPermission } that the containing package must be granted in order for it to operate correctly. For runtime permissions, i.e. ones withdangerousprotection level, on a platform that supports runtime permissions, the permission will not be granted until the app explicitly requests it at runtime and the user approves the grant. You cannot request at runtime permissions that are not declared as used in the manifest. See the Security and Permissions document for more information on permissions. Also available is a {@link android.Manifest.permission list of permissions} included with the base platform.This appears as a child tag of the root {@link #AndroidManifest manifest} tag. --> <!-- Required name of the permission you use, as published with the corresponding name attribute of a {@link android.R.styleable#AndroidManifestPermission } tag; often this is one of the {@link android.Manifest.permission standard system permissions}. --> <!-- The
uses-configurationtag specifies a specific hardware configuration value used by the application. For example an application might specify that it requires a physical keyboard or a particular navigation method like trackball. Multiple such attribute values can be specified by the application.This appears as a child tag of the root {@link #AndroidManifest manifest} tag. @deprecated Use
feature-groupinstead.--> <!-- Theuses-featuretag specifies a specific device hardware or software feature used by the application. For example an application might specify that it requires a camera. Multiple attribute values can be specified by the application.This appears as a child tag of the root {@link #AndroidManifest manifest} tag. --> <!-- The
feature-grouptag specifies a set of one or moreuses-featureelements that the application can utilize. An application uses multiplefeature-groupsets to indicate that it can support different combinations of features.This appears as a child tag of the root {@link #AndroidManifest manifest} tag. --> <!-- The
uses-sdktag describes the SDK features that the containing package must be running on to operate correctly.This appears as a child tag of the root {@link #AndroidManifest manifest} tag. --> <!-- The
extension-sdktag is a child of the tag, and specifies required extension sdk features. --> <!-- Thelibrarytag declares that this apk is providing itself as a shared library for other applications to use. It can only be used with apks that are built in to the system image. Other apks can link to it with the {@link #AndroidManifestUsesLibrary uses-library} tag.This appears as a child tag of the {@link #AndroidManifestApplication application} tag. --> <!-- The
static-librarytag declares that this apk is providing itself as a static shared library for other applications to use. Any app can declare such a library and there can be only one static shared library per package. These libraries are updatable, multiple versions can be installed at the same time, and an app links against a specific version simulating static linking while allowing code sharing. Other apks can link to it with the {@link #AndroidManifestUsesLibrary uses-static-library} tag.This appears as a child tag of the {@link #AndroidManifestApplication application} tag. --> <!-- The
uses-librariesspecifies a shared library that this package requires to be linked against. Specifying this flag tells the system to include this library's code in your class loader.This appears as a child tag of the {@link #AndroidManifestApplication application} tag. --> <!-- The
uses-static-libraryspecifies a shared static library that this package requires to be statically linked against. Specifying this tag tells the system to include this library's code in your class loader. Depending on a static shared library is equivalent to statically linking with the library at build time while it offers apps to share code defined in such libraries. Hence, static libraries are strictly required.On devices running O MR1 or higher, if the library is singed with multiple signing certificates you must to specify the SHA-256 hashes of the additional certificates via adding {@link #AndroidManifestAdditionalCertificate additional-certificate} tags.
This appears as a child tag of the {@link #AndroidManifestApplication application} tag. --> <!-- The
additional-certificatespecifies the SHA-256 digest of a static shared library's additional signing certificate. You need to use this tag if the library is singed with more than one certificate.This appears as a child tag of the {@link #AndroidManifestUsesStaticLibrary uses-static-library} or {@link #AndroidManifestUsesPackage uses-package} tag. --> <!-- The
uses-packagespecifies some kind of dependency on another package. It does not have any impact on the app's execution on the device, but provides information about dependencies it has on other packages that need to be satisfied for it to run correctly. That is, this is primarily for installers to know what other apps need to be installed along with this one.This appears as a child tag of the {@link #AndroidManifestApplication application} tag. --> <!-- The
supports-screensspecifies the screen dimensions an application supports. By default a modern application supports all screen sizes and must explicitly disable certain screen sizes here; older applications are assumed to only support the traditional normal (HVGA) screen size. Note that screen size is a separate axis from density, and is determined as the available pixels to an application after density scaling has been applied.This appears as a child tag of the {@link #AndroidManifest manifest} tag. --> <!-- Indicates whether the application supports smaller screen form-factors. A small screen is defined as one with a smaller aspect ratio than the traditional HVGA screen; that is, for a portrait screen, less tall than an HVGA screen. In practice, this means a QVGA low density or VGA high density screen. An application that does not support small screens will not be available for small screen devices, since there is little the platform can do to make such an application work on a smaller screen. --> <!-- Indicates whether the application supports larger screen form-factors. A large screen is defined as a screen that is significantly larger than a normal phone screen, and thus may require some special care on the application's part to make good use of it. An example would be a VGA normal density screen, though even larger screens are certainly possible. An application that does not support large screens will be placed as a postage stamp on such a screen, so that it retains the dimensions it was originally designed for. --> <!-- Private tag to declare system protected broadcast actions.
This appears as a child tag of the root {@link #AndroidManifest manifest} tag. --> <!-- Private tag to declare the original package name that this package is based on. Only used for packages installed in the system image. If given, and different than the actual package name, and the given original package was previously installed on the device but the new one was not, then the data for the old one will be renamed to be for the new package.
This appears as a child tag of the root {@link #AndroidManifest manifest} tag. --> <!-- The
processestag specifies the processes the application will run code in and optionally characteristics of those processes. This tag is optional; if not specified, components will simply run in the processes they specify. If supplied, they can only specify processes that are enumerated here, and if they don't this will be treated as a corrupt apk and result in an install failure.This appears as a child tag of the {@link #AndroidManifestApplication application} tag. --> <!-- The
processtag enumerates one of the available processes under its containingprocessestag.This appears as a child tag of the {@link #AndroidManifestProcesses processes} tag. --> <!-- The
deny-permissiontag specifies that a permission is to be denied for a particular process (if specified under the {@link #AndroidManifestProcess process} tag) or by default for all processes {if specified under the @link #AndroidManifestProcesses processes} tag).This appears as a child tag of the {@link #AndroidManifestProcesses processes} and {@link #AndroidManifestProcess process} tags. --> <!-- The
allow-permissiontag specifies that a permission is to be allowed for a particular process, when it was previously denied for all processes through {@link #AndroidManifestDenyPermission deny-permission}This appears as a child tag of the {@link #AndroidManifestProcesses processes} and {@link #AndroidManifestProcess process} tags. --> <!-- The
providertag declares a {@link android.content.ContentProvider} class that is available as part of the package's application components, supplying structured access to data managed by the application.This appears as a child tag of the {@link #AndroidManifestApplication application} tag. --> <!-- Attributes that can be supplied in an AndroidManifest.xml
grant-uri-permissiontag, a child of the {@link #AndroidManifestProvider provider} tag, describing a specific URI path that can be granted as a permission. This tag can be specified multiple time to supply multiple paths. --> <!-- Attributes that can be supplied in an AndroidManifest.xmlpath-permissiontag, a child of the {@link #AndroidManifestProvider provider} tag, describing a permission that allows access to a specific path in the provider. This tag can be specified multiple time to supply multiple paths. --> <!-- Theservicetag declares a {@link android.app.Service} class that is available as part of the package's application components, implementing long-running background operations or a rich communication API that can be called by other packages.Zero or more {@link #AndroidManifestIntentFilter intent-filter} tags can be included inside of a service, to specify the Intents that can connect with it. If none are specified, the service can only be accessed by direct specification of its class name. The service tag appears as a child tag of the {@link #AndroidManifestApplication application} tag. --> <!-- If true, and this is an {@link android.R.attr#isolatedProcess} service, the service will be spawned from an Application Zygote, instead of the regular Zygote.
The Application Zygote will first pre-initialize the application's class loader. Then, if the application has defined the {@link android.R.attr#zygotePreloadName} attribute, the Application Zygote will call into that class to allow it to perform application-specific preloads (such as loading a shared library). Therefore, spawning from the Application Zygote will typically reduce the service launch time and reduce its memory usage. The downside of using this flag is that you will have an additional process (the app zygote itself) that is taking up memory. Whether actual memory usage is improved therefore strongly depends on the number of isolated services that an application starts, and how much memory those services save by preloading and sharing memory with the app zygote. Therefore, it is recommended to measure memory usage under typical workloads to determine whether it makes sense to use this flag. --> <!-- The
receivertag declares an {@link android.content.BroadcastReceiver} class that is available as part of the package's application components, allowing the application to receive actions or data broadcast by other applications even if it is not currently running.Zero or more {@link #AndroidManifestIntentFilter intent-filter} tags can be included inside of a receiver, to specify the Intents it will receive. If none are specified, the receiver will only be run when an Intent is broadcast that is directed at its specific class name. The receiver tag appears as a child tag of the {@link #AndroidManifestApplication application} tag. --> <!-- The
activitytag declares an {@link android.app.Activity} class that is available as part of the package's application components, implementing a part of the application's user interface.Zero or more {@link #AndroidManifestIntentFilter intent-filter} tags can be included inside of an activity, to specify the Intents that it can handle. If none are specified, the activity can only be started through direct specification of its class name. The activity tag appears as a child tag of the {@link #AndroidManifestApplication application} tag. --> <!-- Indicates whether the activity wants the connected display to do minimal post processing on the produced image or video frames. This will only be requested if this activity's main window is visible on the screen.
This setting should be used when low latency has a higher priority than image enhancement processing (e.g. for games or video conferencing).
If the Display sink is connected via HDMI, the device will begin to send infoframes with Auto Low Latency Mode enabled and Game Content Type. This will switch the connected display to a minimal image processing mode (if available), which reduces latency, improving the user experience for gaming or video conferencing applications. For more information, see HDMI 2.1 specification.
If the Display sink has an internal connection or uses some other protocol than HDMI, effects may be similar but implementation-defined.
The ability to switch to a mode with minimal post proessing may be disabled by a user setting in the system settings menu. In that case, this field is ignored and the display will remain in its current mode.
See {@link android.content.pm.ActivityInfo#FLAG_PREFER_MINIMAL_POST_PROCESSING} --> <!-- The
activity-aliastag declares a new name for an existing {@link #AndroidManifestActivity activity} tag.Zero or more {@link #AndroidManifestIntentFilter intent-filter} tags can be included inside of an activity-alias, to specify the Intents that it can handle. If none are specified, the activity can only be started through direct specification of its class name. The activity-alias tag appears as a child tag of the {@link #AndroidManifestApplication application} tag. --> <!-- The
meta-datatag is used to attach additional arbitrary data to an application component. The data can later be retrieved programmatically from the {@link android.content.pm.ComponentInfo#metaData ComponentInfo.metaData} field. There is no meaning given to this data by the system. You may supply the data through either thevalueorresourceattribute; if both are given, thenresourcewill be used.It is highly recommended that you avoid supplying related data as multiple separate meta-data entries. Instead, if you have complex data to associate with a component, then use the
resourceattribute to assign an XML resource that the client can parse to retrieve the complete data. --> <!-- Theintent-filtertag is used to construct an {@link android.content.IntentFilter} object that will be used to determine which component can handle a particular {@link android.content.Intent} that has been given to the system. It can be used as a child of the {@link #AndroidManifestActivity activity}, {@link #AndroidManifestReceiver receiver} and {@link #AndroidManifestService service} tags.Zero or more {@link #AndroidManifestAction action}, {@link #AndroidManifestCategory category}, and/or {@link #AndroidManifestData data} tags should be included inside to describe the contents of the filter.
The optional label and icon attributes here are used with an activity to supply an alternative description of that activity when it is being started through an Intent matching this filter. --> <!-- Within an application, multiple intent filters may match a particular intent. This allows the app author to specify the order filters should be considered. We don't want to use priority because that is global across applications.
Only use if you really need to forcibly set the order in which filters are evaluated. It is preferred to target an activity with a directed intent instead.
The value is a single integer, with higher numbers considered to be better. If not specified, the default order is 0. --> <!-- Attributes that can be supplied in an AndroidManifest.xml
actiontag, a child of the {@link #AndroidManifestIntentFilter intent-filter} tag. See {@link android.content.IntentFilter#addAction} for more information. --> <!-- The name of an action that is handled, using the Java-style naming convention. For example, to support {@link android.content.Intent#ACTION_VIEW Intent.ACTION_VIEW} you would putandroid.intent.action.VIEWhere. Custom actions should generally use a prefix matching the package name. --> <!-- Attributes that can be supplied in an AndroidManifest.xmldatatag, a child of the {@link #AndroidManifestIntentFilter intent-filter} tag, describing the types of data that match. This tag can be specified multiple times to supply multiple data options, as described in the {@link android.content.IntentFilter} class. Note that all such tags are adding options to the same IntentFilter so that, for example,<data android:scheme="myscheme" android:host="me.com" />is equivalent to<data android:scheme="myscheme" /> <data android:host="me.com" />. --> <!-- Specify a MIME type that is handled, as per {@link android.content.IntentFilter#addDataType IntentFilter.addDataType()}.Note: MIME type matching in the Android framework is case-sensitive, unlike formal RFC MIME types. As a result, MIME types here should always use lower case letters.
--> <!-- Specify a URI scheme that is handled, as per {@link android.content.IntentFilter#addDataScheme IntentFilter.addDataScheme()}.Note: scheme matching in the Android framework is case-sensitive, unlike the formal RFC. As a result, schemes here should always use lower case letters.
--> <!-- Specify a URI authority host that is handled, as per {@link android.content.IntentFilter#addDataAuthority IntentFilter.addDataAuthority()}.Note: host name matching in the Android framework is case-sensitive, unlike the formal RFC. As a result, host names here should always use lower case letters.
--> <!-- Attributes that can be supplied in an AndroidManifest.xmlcategorytag, a child of the {@link #AndroidManifestIntentFilter intent-filter} tag. See {@link android.content.IntentFilter#addCategory} for more information. --> <!-- The name of category that is handled, using the Java-style naming convention. For example, to support {@link android.content.Intent#CATEGORY_LAUNCHER Intent.CATEGORY_LAUNCHER} you would putandroid.intent.category.LAUNCHERhere. Custom actions should generally use a prefix matching the package name. --> <!-- Attributes that can be supplied in an AndroidManifest.xmlinstrumentationtag, a child of the root {@link #AndroidManifest manifest} tag. --> <!-- Attributes that can be supplied in an AndroidManifest.xmlscreentag, a child ofcompatible-screens, which is itself a child of the root {@link #AndroidManifest manifest} tag. --> <!-- Theinput-typetag is a child of thesupports-inputtag, which is itself a child of the root {@link #AndroidManifest manifest} tag. Eachinput-typetag specifices the name of a specific input device type. When grouped with the other elements of the parentsupports-inputtag it defines a collection of input devices, which when all used together, are considered a supported input mechanism for the application. There may be multiplesupports-inputtags defined, each containing a different combination of input device types. --> <!-- Declaration of an {@link android.content.Intent} object in XML. May also include zero or more {@link #IntentCategory } and {@link #Extra } tags. --> <!-- The data URI to assign to the Intent, as per {@link android.content.Intent#setData Intent.setData()}.Note: scheme and host name matching in the Android framework is case-sensitive, unlike the formal RFC. As a result, URIs here should always be normalized to use lower case letters for these elements (as well as other proper Uri normalization).
--> <!-- The MIME type name to assign to the Intent, as per {@link android.content.Intent#setType Intent.setType()}.Note: MIME type matching in the Android framework is case-sensitive, unlike formal RFC MIME types. As a result, MIME types here should always use lower case letters.
--> <!--layouttag allows configuring the layout for the activity within multi-window environment. --> <!-- Minimal width of the activity.NOTE: A task's root activity value is applied to all additional activities launched in the task. That is if the root activity of a task set minimal width, then the system will set the same minimal width on all other activities in the task. It will also ignore any other minimal width attributes of non-root activities. --> <!-- Minimal height of the activity.
NOTE: A task's root activity value is applied to all additional activities launched in the task. That is if the root activity of a task set minimal height, then the system will set the same minimal height on all other activities in the task. It will also ignore any other minimal height attributes of non-root activities. --> <!--
restrict-updatetag restricts system apps from being updated unless the SHA-512 hash equals the specified value. @hide --> <!-- The SHA-512 hash of the only APK that can be used to update a package.NOTE: This is only applicable to system packages. @hide -->
