drgreen/android_frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
android_frameworks_base/data/etc/privapp-permissions-platform.xml

496 lines
29 KiB
XML
Raw Normal View History

Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<?xml version="1.0" encoding="utf-8"?>
<!--
~ Copyright (C) 2016 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
-->
<!--
This XML file declares which signature|privileged permissions should be granted to privileged
applications that come with the platform
-->
<permissions>
Update package name for ExtServices to whitelist permissions. Test: shared images in Camera to verify this. Change-Id: Iebbe7405afa7de5246e02d7dbdb84fb0f319db5f
2017-10-19 11:48:20 -07:00
<privapp-permissions package="android.ext.services">
<permission name="android.permission.PROVIDE_RESOLVER_RANKER_SERVICE" />
Make sure notifications from the default sms app do not get filtered to the non-interruptive section. Bug: 123365364 Test: Unit tests and manual testing. Change-Id: Ide41ff9656ee81aa4fc6f6bcdd00ae886a0e13ee
2019-01-28 11:26:46 -05:00
<permission name="android.permission.MONITOR_DEFAULT_SMS_PACKAGE" />
API changes for NAS - make NAS @SystemApi and guard with permission - Add missing Nullable/NonNull annotations Fixes: 126699678 Fixes: 127146476 Test: make, gts Change-Id: Ie024983f7c440d5b4d3065af031b27958395f2f1
2019-03-03 16:10:52 -05:00
<permission name="android.permission.REQUEST_NOTIFICATION_ASSISTANT_SERVICE" />
Fix crash in ExtServices Bug: 138848702 Test: boot test on aosp targets Change-Id: I50ecbf9e64020821f50da0ad4c798ff292cbca65
2019-08-14 12:56:49 -04:00
<permission name="android.permission.INTERACT_ACROSS_USERS" />
Update package name for ExtServices to whitelist permissions. Test: shared images in Camera to verify this. Change-Id: Iebbe7405afa7de5246e02d7dbdb84fb0f319db5f
2017-10-19 11:48:20 -07:00
</privapp-permissions>
Whitelist READ_PRIVILEGED_PHONE_STATE permission needed by Build.getSerial(). Bug: 144779107 Test: Plugged the phone, no SecurityException, started Phantoscope. Change-Id: I2af21c1318fabb4d9a8b9bc6808dc163a3e353b5
2020-05-15 10:01:53 +00:00
<!-- Needed for Build.getSerial(), which is used to send a unique number for serial, per HUIG. -->
<privapp-permissions package="android.car.usb.handler">
<permission name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>
</privapp-permissions>
Update package name for ExtServices to whitelist permissions. Test: shared images in Camera to verify this. Change-Id: Iebbe7405afa7de5246e02d7dbdb84fb0f319db5f
2017-10-19 11:48:20 -07:00
Allow WRITE_SECURE_SETTINGS for ANGLE to provide developer options. ANGLE is a system library which adds a developer option to control when it is used as the default OpenGL ES driver. Test: manual, ANGLE.apk's developer options work. Bug: 142239747 This is a cherry-pick of https://android-review.googlesource.com/c/platform/frameworks/base/+/1222890 Change-Id: I3e616d6252d0daa0e32c942b05987d17e73a2709
2020-01-31 17:45:32 -05:00
<privapp-permissions package="com.android.angle">
<permission name="android.permission.WRITE_SECURE_SETTINGS"/>
</privapp-permissions>
Updated the whitelist to match the state of platform apps Some apps in frameworks/base are only included in AOSP targets and discrepancies weren't discovered by CI tests. Test: manual Bug: 67718369 Change-Id: If88aa90f4dcab51b6e11562cadbe003948b6c149
2017-10-19 12:26:32 -07:00
<privapp-permissions package="com.android.apps.tag">
<permission name="android.permission.WRITE_SECURE_SETTINGS"/>
</privapp-permissions>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<privapp-permissions package="com.android.backupconfirm">
<permission name="android.permission.BACKUP"/>
<permission name="android.permission.CRYPT_KEEPER"/>
</privapp-permissions>
support cellbroadcast data migration by dafault As part of mainline effort, cellbroadcastreceiver package name has been renamed. Now its a completely new apk with different uid. That said all user data e.g, cellbroadcast history and user preference from legacy app com.android.cellbroadcastreceiver are gone. This change is to support preserve user data when devices upgrate to R and take cellbraodcast. mainline module. 1. create legacy cellbroadcast app with old pakcage name com.android.cellbroadcastreceiver. this app only surface the old data and should not contains any activities/services to handle emergecy apert 2. legacy cellbroadcast app will be included to the system image by default. OEMs are free to remove it if they don't care data loss or after R data migration is done. leagcy app will not be part of com.android.cellbroadcast apex. 3. the real mainline module rename to com.android.cellbroadcast.module Bug: 155844209 Change-Id: I5e61c7e777526e038cd8d9971a2c5b87c00eaacb Merged-in: I5e61c7e777526e038cd8d9971a2c5b87c00eaacb
2020-05-14 10:52:21 -07:00
<privapp-permissions package="com.android.cellbroadcastreceiver.module">
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
<permission name="android.permission.MANAGE_USERS"/>
<permission name="android.permission.MODIFY_PHONE_STATE"/>
<permission name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>
<permission name="android.permission.RECEIVE_EMERGENCY_BROADCAST"/>
Fixed that emergency alert dialog not popped up Fixed by granting START_ACTIVITIES_FROM_BACKGROUND to the cell broadcast receiver. Test: Manual Bug: 130384940 Change-Id: Ie563a8f11ac991ab9568f65df6a4d14eebe47c5e
2019-04-21 17:21:43 -07:00
<permission name="android.permission.START_ACTIVITIES_FROM_BACKGROUND"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
</privapp-permissions>
Move cell broadcast service module directory Update the permissions and resource to reflect this move. Bug: 135956699 Test: manual Change-Id: I8c798f48e3a342cc2ce29d1f7f199ae1337ff2d0
2019-10-14 12:45:23 -07:00
<privapp-permissions package="com.android.cellbroadcastservice">
<permission name="android.permission.MODIFY_PHONE_STATE"/>
<permission name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>
<permission name="android.permission.RECEIVE_EMERGENCY_BROADCAST"/>
</privapp-permissions>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<privapp-permissions package="com.android.externalstorage">
<permission name="android.permission.MOUNT_UNMOUNT_FILESYSTEMS"/>
<permission name="android.permission.WRITE_MEDIA_STORAGE"/>
Whitelist privapp MANAGE_EXTERNAL_STORAGE permission After adding MANAGE_EXTERNAL_STORAGE permission to several apps on the system partition, we should whitelist them Test: m Bug: 144914977 Change-Id: Ia4401904e23193b8628071d6a2a6d789faf0ece5
2020-01-27 13:28:26 +00:00
<permission name="android.permission.MANAGE_EXTERNAL_STORAGE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
</privapp-permissions>
Adding launcher permission to base whitelist - This is a *temporary* permission that we are using to set the system rotation setting via the launcher settings. The framework uses the same setting for forced-rotation, but this currently only is scoped to launcher so it makes more sense as a launcher setting than as a developer option (and we plan on removing it shortly). We are working with jjaggi@ and caen@ to coordinate the fw and launcher settings. Bug: 151611270 Test: Manual Change-Id: If371cac4d580785ed1714c82a67b995a40ecf9a6
2020-03-16 09:20:49 -07:00
<privapp-permissions package="com.android.launcher3">
<permission name="android.permission.WRITE_SECURE_SETTINGS"/>
</privapp-permissions>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<privapp-permissions package="com.android.location.fused">
<permission name="android.permission.INSTALL_LOCATION_PROVIDER"/>
Overhaul FusedLocationProvider Fix some minor bugs and ensure fused location provider correctly supports location bypass. This is especially important for when location bypass is invoked in direct boot. The added UPDATE_DEVICE_STATS permission is necessary for FusedLocation to correctly update WorkSources. FusedLocation receives work from LMS and then further delegates that work to other location providers. The other location providers should be informed of the correct applications for battery blame, and should not be blaming the FusedLocation package. 1) This is the minimally scoped permission necessary to battery blame correctly. 2) There is no way to attribute battery blame without this permission. 3) This is the correct permission - as required by LocationManager, and this permission will likely never be removed (FusedLocation will always need to battery blame). Test: atest FusedLocationTests Change-Id: If7126fffaae5577ddf8e366a0b5c17b3e5286582
2020-01-21 15:16:51 -08:00
<permission name="android.permission.UPDATE_DEVICE_STATS"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
</privapp-permissions>
<privapp-permissions package="com.android.managedprovisioning">
<permission name="android.permission.CHANGE_COMPONENT_ENABLED_STATE"/>
<permission name="android.permission.CHANGE_CONFIGURATION"/>
Give new permission to set cross-profile app-op to ManagedProvisioning This is required for the provisioning cross-profile consent screen which is used to take some apps off INTERACT_ACROSS_USERS. Hidden API CrossProfileApps#setInteractAcrossProfilesAppOp is changed from requiring the broad app-op permissions to requiring CONFIGURE_INTERACT_ACROSS_PROFILES. It then clears identity before calling into AppOpsManager. For convenience, we also allow apps (such as Settings) with the broader app-op permissions to continue to call this method; in that case, we simply don't clear the identity and let AppOpsManager check the permissions (so we allow AppOpsManager to set the requirements if you don't have the new CONFIGURE_INTERACT_ACROSS_PROFILES). The CL also adds 'withCleanCallingIdentity' support to CrossProfileAppsServiceImpl and moves over existing calls. Bug: 136249261 Bug: 140728653 Test: atest --verbose com.android.managedprovisioning.provisioning.crossprofile.CrossProfileConsentActivityRoboTest Change-Id: Ibd304563dd1ef5f16784e3502be5ef1ec4675b63
2020-02-07 14:02:48 +00:00
<permission name="android.permission.CONFIGURE_INTERACT_ACROSS_PROFILES"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.CRYPT_KEEPER"/>
<permission name="android.permission.DELETE_PACKAGES"/>
<permission name="android.permission.INSTALL_PACKAGES"/>
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
<permission name="android.permission.MANAGE_DEVICE_ADMINS"/>
<permission name="android.permission.MANAGE_USERS"/>
<permission name="android.permission.MASTER_CLEAR"/>
AndroidManifest.xml: Add new network permission for managed provisioning Adding a new permission for managed provisioning to access privileged network operations. Bug: 115980767 Test: Compiles Change-Id: I6375c119a7c5e13f1648803c7da5cebd6830d46c
2018-11-14 14:53:53 -08:00
<permission name="android.permission.NETWORK_MANAGED_PROVISIONING"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.PERFORM_CDMA_PROVISIONING"/>
Allow ManagedProvisioning to access imei and serial number. Bug: 122721358 Test: manual Change-Id: I0d8f191f4f1bc1d8a87842db717af329681b012a
2019-01-28 18:32:27 +00:00
<permission name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.SET_TIME"/>
<permission name="android.permission.SET_TIME_ZONE"/>
<permission name="android.permission.SHUTDOWN"/>
<permission name="android.permission.WRITE_SECURE_SETTINGS"/>
Add START_ACTIVITIES_FROM_BACKGROUND to ManagedProvisioning. Fixes: 131240642 Fixes: 130371743 Test: Manual Change-Id: I72a4ab31bc662af4e3580a2c1d50f550e6314f74
2019-04-30 12:46:36 +01:00
<permission name="android.permission.START_ACTIVITIES_FROM_BACKGROUND"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
</privapp-permissions>
<privapp-permissions package="com.android.mms.service">
<permission name="android.permission.BIND_CARRIER_MESSAGING_SERVICE"/>
<permission name="android.permission.BIND_CARRIER_SERVICES"/>
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
</privapp-permissions>
<privapp-permissions package="com.android.mtp">
Migrate MTP service into separate project. As part of getting MediaProvider to compile against supported APIs, we're moving MTP related logic into its own repository. Bug: 135340257 Test: manual Change-Id: Ie274b1c0da435c024385eba1e4301639991a785b
2019-08-12 11:41:44 -06:00
<permission name="android.permission.ACCESS_MTP"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.MANAGE_USB"/>
Progress towards splitting MediaProvider UID. We're working towards making MediaProvider into a Mainline module, which means it can no longer share the "android.media" UID built into the OS. The major reason for this is because they're signed with separate keys, but a secondary reason is that we don't know what database customizations an OEM has performed in their MediaProvider. Ensure that packages are requesting the permissions they actually depend on, instead of relying on permissions requested by other packages under the shared UID. Bug: 144247087 Test: atest --test-mapping packages/providers/MediaProvider Change-Id: Iea42a69dd270682258314126f6540478aece3e59
2019-11-12 15:19:53 -07:00
<permission name="android.permission.MANAGE_USERS"/>
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
<permission name="android.permission.WRITE_MEDIA_STORAGE"/>
Whitelist privapp MANAGE_EXTERNAL_STORAGE permission After adding MANAGE_EXTERNAL_STORAGE permission to several apps on the system partition, we should whitelist them Test: m Bug: 144914977 Change-Id: Ia4401904e23193b8628071d6a2a6d789faf0ece5
2020-01-27 13:28:26 +00:00
<permission name="android.permission.MANAGE_EXTERNAL_STORAGE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
</privapp-permissions>
<privapp-permissions package="com.android.musicfx">
<permission name="android.permission.CHANGE_COMPONENT_ENABLED_STATE"/>
</privapp-permissions>
Add networkrecommendation permissions to privapp perms list. Bug: 34235587 Test: Flashed and checked logcat for crash. Change-Id: Ib35070ea87e23a3be8804eb3796e02c76a5628d0
2017-01-11 20:54:03 -08:00
<privapp-permissions package="com.android.networkrecommendation">
<permission name="android.permission.SCORE_NETWORKS"/>
<permission name="android.permission.SUBSTITUTE_NOTIFICATION_APP_NAME"/>
<permission name="android.permission.WRITE_SECURE_SETTINGS"/>
</privapp-permissions>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<privapp-permissions package="com.android.packageinstaller">
<permission name="android.permission.DELETE_PACKAGES"/>
<permission name="android.permission.INSTALL_PACKAGES"/>
Split PackageInstaller app into installation and permissions management The two components were mostly independant for a long time. Since I1e80a3f5e63d02b3859ecf74af21ca4c61f96874 the installation flow does not grant any permissions anymore and the last connection between these parts was broken. The new app "com.android.packageinstaller" in frameworks/base/packages/PackageInstaller will only handle (side load) package installtion and uninstallation. The exisiting app will be renamed to "com.android.permissioncontroller" and only handle permission granting and permission management. This change does only minimal cleanup cleanup. In particularly it does not move any files in the old permissions controller. This is to not disturb other features currently in development. This change set also updates the make files to install the two apps on the appropriate devices. Further the permisson policy xmls need to be updated to point to the right packages. Test: Installed + uninstalled packages Granted permissions + managed permissions GtsPackageInstallTestCases GtsNoPermissionTestCases GtsNoPermissionTestCases25 GtsPackageInstallerTapjackingTestCases GtsPackageUninstallTestCases Change-Id: I2d3796b837fc0049e712c82a990907f305c8febf
2018-07-25 12:12:30 -07:00
<permission name="android.permission.USE_RESERVED_DISK"/>
<permission name="android.permission.MANAGE_USERS"/>
<permission name="android.permission.UPDATE_APP_OPS_STATS"/>
Show app installed notification from PackageInstaller Bug: 111214100 Change-Id: If3f82bfac740f4f3cf8312f396943f2ebd447c12 Test: Notifications are showing correctly after new apps installed
2018-09-05 20:55:11 +01:00
<permission name="android.permission.SUBSTITUTE_NOTIFICATION_APP_NAME"/>
fragileUserData-apps might keep data on uninstall If an app declares that is has flagile user data, all the user to choose to keep the app-data on uninstall. Test: Unistalled apps that set the new flag and app that did not. Verified that the KEEP_DATA flag was set when checkbox was clicked. Change-Id: I032fb21854352bbc175934ae5eb68a1430b1d403 Fixes: 117578306
2018-12-12 11:28:57 -08:00
<permission name="android.permission.PACKAGE_USAGE_STATS"/>
Split PackageInstaller app into installation and permissions management The two components were mostly independant for a long time. Since I1e80a3f5e63d02b3859ecf74af21ca4c61f96874 the installation flow does not grant any permissions anymore and the last connection between these parts was broken. The new app "com.android.packageinstaller" in frameworks/base/packages/PackageInstaller will only handle (side load) package installtion and uninstallation. The exisiting app will be renamed to "com.android.permissioncontroller" and only handle permission granting and permission management. This change does only minimal cleanup cleanup. In particularly it does not move any files in the old permissions controller. This is to not disturb other features currently in development. This change set also updates the make files to install the two apps on the appropriate devices. Further the permisson policy xmls need to be updated to point to the right packages. Test: Installed + uninstalled packages Granted permissions + managed permissions GtsPackageInstallTestCases GtsNoPermissionTestCases GtsNoPermissionTestCases25 GtsPackageInstallerTapjackingTestCases GtsPackageUninstallTestCases Change-Id: I2d3796b837fc0049e712c82a990907f305c8febf
2018-07-25 12:12:30 -07:00
</privapp-permissions>
<privapp-permissions package="com.android.permissioncontroller">
<permission name="android.permission.CLEAR_APP_CACHE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.MANAGE_USERS"/>
Updated platform privileged permissions Change-Id: I84e27ec023b20205bacb026e0a7cc32c12f67a7b Test: manual Bug: 33499917 Bug: 34128772
2017-01-05 18:45:06 -08:00
<permission name="android.permission.OBSERVE_GRANT_REVOKE_PERMISSIONS"/>
Add a new Intent for seeing permission usages This intent is used by the Permissions Hub. We also give PermissionController the GET_APP_OPS_STATS permission. Bug: 63532550 Test: Used the Permissions Hub. Change-Id: If1254f67c12fc5052d6ad5ff8260778a7c59dccc
2018-09-27 11:18:44 -07:00
<permission name="android.permission.GET_APP_OPS_STATS"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.UPDATE_APP_OPS_STATS"/>
Add IncidentCompanionService It is a helper in the system process that helps dumpstate and incidentd get user confirmation to share reports Bug: 123543706 Test: bit GooglePermissionControllerTest:* Change-Id: Ia3fe4bd5257044ed89fe56ce683876fa03ba6c36
2018-12-18 15:00:25 -08:00
<permission name="android.permission.REQUEST_INCIDENT_REPORT_APPROVAL"/>
Added a new "incidentReportApprover" permission protection flag. This gives the ONE app installed on the system the permission to authorize the sharing of incident and bug reports with an app. Currently that app is PermissionController. Package Manager enforces that there is only one installed, and refused to boot if that isn't the case. Bug: 123543706 Test: bit GooglePermissionControllerTest:* Change-Id: I76a7fad0ea36359bbb0ff09669df46202d059dab
2018-12-18 10:40:04 -08:00
<permission name="android.permission.APPROVE_INCIDENT_REPORTS"/>
Add system API for whether emergency assistance is enabled. This is needed in the emergency role. Bug: 124452117 Test: build Change-Id: I277ad208dfa07d42f3e2daee658d30ef831d4b9b
2019-03-18 16:06:19 -07:00
<permission name="android.permission.READ_PRIVILEGED_PHONE_STATE" />
Grant PermissionController SUBSTITUTE_NOTIFICATION_APP_NAME This app will pretend to be the Settings app when sending location access notifications. Bug: 128608303 Test: boot Change-Id: I447510bbe323f3de40828a5cb4a37abe1c44c990
2019-03-22 16:04:27 +00:00
<permission name="android.permission.SUBSTITUTE_NOTIFICATION_APP_NAME" />
Auto-revoke permissions for unused apps android.permission.PACKAGE_USAGE_STATS is the minimal required permission to get app usage stats, as confirmed by the API author and usage stats is the only place giving us historical app-usage information. Test: reduce thresholds and test with a toy app Change-Id: Id8767cab93802d3fc90dc32a93ffb20a53f45ad9
2020-01-09 11:02:09 -08:00
<permission name="android.permission.PACKAGE_USAGE_STATS" />
Add enable/disable permission to permissioncontroller Ensure the permission controller can enable and disable apps Bug: 146513245 Test: Manual Change-Id: I185335bd729c8fa94b150d3b3adb95b89013aa16
2020-04-07 12:07:54 -07:00
<permission name="android.permission.CHANGE_COMPONENT_ENABLED_STATE" />
Allow permission controller to read audio configuration - Unfortunately there is no read-only permission that allows to read the audio configuration - Unfortunately there is no API bump before the feature ships that would allow us to add such a read-only permission Bug: 162547999 Test: Read audio configuration from permission controller Change-Id: Icfe2b5ae54cae1cfc1be44a1370ffb0692365316
2020-08-04 12:09:05 -07:00
<permission name="android.permission.MODIFY_AUDIO_ROUTING" />
Give Permission Controller the ability to see all accounts. Bug: 161007415 Change-Id: I912cbfdc9a1881a0e9a1755848147cdf23781885
2020-07-14 17:12:15 -07:00
<!-- For permission hub 2 debugging only -->
<permission name="android.permission.GET_ACCOUNTS_PRIVILEGED"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
</privapp-permissions>
<privapp-permissions package="com.android.phone">
<permission name="android.permission.ACCESS_IMS_CALL_SERVICE"/>
<permission name="android.permission.BIND_CARRIER_MESSAGING_SERVICE"/>
<permission name="android.permission.BIND_CARRIER_SERVICES"/>
Add CellBroadcastService and related permissions CellBroadcastService is bound to by the platform to handle cell broadcasts. Bug: 135956699 Test: manual Change-Id: Ib1b20da03d271fc0b2736774b2ca6c6514944093
2019-09-23 13:35:02 -07:00
<permission name="android.permission.BIND_CELL_BROADCAST_SERVICE"/>
Add BIND_IMS_SERVICE to permissions whitelist Adds android.permission.BIND_IMS_SERVICE to the permissions whitelist xml file. Bug: 34813244 Test: Manual Change-Id: I7a7ad1a361c9d2dcc51769bc74a436878ad4adc5
2017-02-03 10:42:25 -08:00
<permission name="android.permission.BIND_IMS_SERVICE"/>
Renamed BIND_DATA_SERVICE to BIND_TELEPHONY_DATA_SERVICE Also grated the permission to the phone process. Test: Manual Bug: 64132030 Change-Id: I1fc82a4e8038b1b05b56dcfa43c0c94955967700
2018-02-02 10:40:11 -08:00
<permission name="android.permission.BIND_TELEPHONY_DATA_SERVICE"/>
Updated platform privileged permissions Change-Id: I84e27ec023b20205bacb026e0a7cc32c12f67a7b Test: manual Bug: 33499917 Bug: 34128772
2017-01-05 18:45:06 -08:00
<permission name="android.permission.BIND_VISUAL_VOICEMAIL_SERVICE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.CALL_PRIVILEGED"/>
<permission name="android.permission.CHANGE_COMPONENT_ENABLED_STATE"/>
<permission name="android.permission.CHANGE_CONFIGURATION"/>
<permission name="android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST"/>
Add CONNECTIVITY_USE_RESTRICTED_NETWORKS permission Add CONNECTIVITY_USE_RESTRICTED_NETWORKS permission to phone package in privapp permission list. Bug: 146222771 Test: build, flash, boot to home Change-Id: I1c88b892b1d2f50856b139a5cad5dc8b07a006be
2019-12-16 16:55:51 +08:00
<permission name="android.permission.CONNECTIVITY_USE_RESTRICTED_NETWORKS"/>
Declare new com.android.phone permission in whitelist. Bug: 35948554 Test: Will verify T/H build Change-Id: I41773160aa6515983a15365905a2cbb6b13e10c6
2017-03-03 17:42:35 -08:00
<permission name="android.permission.CONTROL_INCALL_EXPERIENCE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.DUMP"/>
Add HANDLE_CAR_MODE_CHANGED permission Required to allow DeviceStateMonitor to monitor changes in car mode to get an accurate state of when all screens are on/off. Test: build Bug: 160898432 Change-Id: If3ad86a2564ce3ba53afea44e8ad5bf02b8d51e0
2020-07-16 14:46:23 -07:00
<permission name="android.permission.HANDLE_CAR_MODE_CHANGES"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
<permission name="android.permission.LOCAL_MAC_ADDRESS"/>
<permission name="android.permission.MANAGE_USERS"/>
Add read/write logic for SubscriptionPlan network types field Add permissions for Phone process to access SubscriptionPlans for meteredness Test: manual verification Bug: 169187737 Change-Id: Ib821590a573db87b22619cfe7ebe64c0230c5031 Merged-In: Ib821590a573db87b22619cfe7ebe64c0230c5031
2020-09-23 01:54:01 -07:00
<permission name="android.permission.MANAGE_SUBSCRIPTION_PLANS" />
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.MODIFY_PHONE_STATE"/>
Check for location access on TelephonyRegistry When sending outbound callbacks on CELL_INFO and CELL_LOCATION, check to make sure that the user has authorized us and the receiving app to get information on their location. Bug: 69637693 Test: manual: telephony testapp Change-Id: Iacfc894428b11a7ec973567d7a797eedb281355f
2017-11-22 17:38:15 -08:00
<permission name="android.permission.PACKAGE_USAGE_STATS"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.PERFORM_CDMA_PROVISIONING"/>
Add system service for accessing SystemConfig Add SystemConfigService and associated AIDLs and permissions for accessing SystemConfig. The service returns values obtained from a static instance of com.android.server.SystemConfig. Bug: 143112379 Test: atest SystemConfigTest Change-Id: I1a863ae9f53db21d698376008e5b1da83309b141
2019-12-23 18:11:10 -08:00
<permission name="android.permission.READ_CARRIER_APP_INFO"/>
Adding "Mobile data" and "Data usage" button in mobile settings. Grant "READ_NETWORK_USAGE_HISTORY" permission to phone because "Datat usage" button summary needs it. Settings provides new intent to open mobile data usage page. Bug: 62201918 Test: Manual Change-Id: Ie317109c723f3946ace4d34c743081a7ae046462
2017-06-20 11:36:01 -07:00
<permission name="android.permission.READ_NETWORK_USAGE_HISTORY"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>
<permission name="android.permission.READ_SEARCH_INDEXABLES"/>
<permission name="android.permission.REBOOT"/>
<permission name="android.permission.REGISTER_CALL_PROVIDER"/>
<permission name="android.permission.REGISTER_SIM_SUBSCRIPTION"/>
Telephony statsd atoms. Test: build Bug: 146066107 Bug: 141631489 Bug: 122371089 Bug: 149880090 Bug: 127666858 Change-Id: I124cf2da59ed4c5e92406081aac0df0f347ace74
2020-03-11 10:16:47 -07:00
<permission name="android.permission.REGISTER_STATS_PULL_ATOM"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.SEND_RESPOND_VIA_MESSAGE"/>
<permission name="android.permission.SET_TIME_ZONE"/>
<permission name="android.permission.SHUTDOWN"/>
Explicitly grant START_ACTIVITIES_FROM_BACKGROUND to com.android.phone. It's needed because when we broadcast ACTION_SIM_SLOT_STATUS_CHANGED we want to allow the receiving app to start an activity from the background. The app already has it implicitly, since it has the same shared UID as com.android.stk which has the permission for unrelated reasons. Making it explicit makes it less likely it will lose the permission accidentally re-introducing a subtly bug. Bug: 132691768 Test: Builds Change-Id: I85669423e628b4534a3f28efd17947ca2481454e
2019-06-14 16:06:36 +01:00
<permission name="android.permission.START_ACTIVITIES_FROM_BACKGROUND"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.STATUS_BAR"/>
<permission name="android.permission.STOP_APP_SWITCHES"/>
More renames for API council Renames PhoneTime[|Zone]Suggestion to TelephonyTime[|Zone]Suggestion. Makes changes to generally avoid PHONE and use SLOT_INDEX or telephony as appropriate for the usage. Removes telephony / phone from a few variable names where it doesn't add value. This commit also renames some remaining phoneId instances to slotIndex which were missed when that rename happened. Bug: 148842434 Test: treehugger Change-Id: I4302e68082b802b75b53c02a9c9b1ae39dff6085
2020-02-04 14:30:06 +00:00
<permission name="android.permission.SUGGEST_TELEPHONY_TIME_AND_ZONE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.UPDATE_APP_OPS_STATS"/>
<permission name="android.permission.UPDATE_DEVICE_STATS"/>
<permission name="android.permission.UPDATE_LOCK"/>
<permission name="android.permission.WRITE_APN_SETTINGS"/>
<permission name="android.permission.WRITE_SECURE_SETTINGS"/>
Public EuiccManager APIs. Public EuiccManager and other related necessary files. Mark EuiccCardManager and other related necessary files as @SystemApi. Solve lint errors and warnings. Bug: 35851809 Test: test on phone Change-Id: I68853e134e1e31fa9b91a83af6c491a2a8cca971
2017-12-12 20:17:09 -08:00
<permission name="android.permission.WRITE_EMBEDDED_SUBSCRIPTIONS"/>
Adding READ_PRECISE_CALL_STATE permission in phone app. This is needed if internal component wants to listen to precise call state change. Bug: 117980553 Test: unittest Change-Id: Id5a60519cbf1d724f939fc10b1f03cccfe5c1b5c
2019-01-22 13:46:17 -08:00
<permission name="android.permission.READ_PRECISE_PHONE_STATE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="com.android.voicemail.permission.READ_VOICEMAIL"/>
<permission name="com.android.voicemail.permission.WRITE_VOICEMAIL"/>
</privapp-permissions>
<privapp-permissions package="com.android.providers.calendar">
<permission name="android.permission.GET_ACCOUNTS_PRIVILEGED"/>
Add extra permissions to CalendarProvider. Per requirement of cross profile calendar feature, CalendarProvider will need MANAGE_USER to get work profile user, and INTERACT_WITH_USER to access its work profile equivalent. Personal CalendarProvider needs to get the corp user ID, so it needs to call userManager.getUsers() which requires {@link android.Manifest.permission#MANAGE_USERS} permission. We'll maintain a whitelist of packages set by DPC that are granted access to cross profile Uris in CalendarProvider, so random personal apps won't be able to access those Uris. Bug: 118456304 Test: manual Change-Id: I59e4a7f39f9abc69f0dcc7ff03d822b8d44b4dbc
2018-10-26 18:52:37 +01:00
<permission name="android.permission.INTERACT_ACROSS_USERS" />
<permission name="android.permission.MANAGE_USERS" />
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.UPDATE_APP_OPS_STATS"/>
Start using new reserved disk GID. We recently created a new GID that can be granted to critical system processes, so that the system is usable enough for the user to free up disk space used by abusive apps. Define a permission for the GID so we can grant it to system apps, and add the GID to core apps needed for system stability. (The list was mostly derived from filling a disk and seeing what caused the device to fall over.) Test: builds, boots Bug: 62024591 Change-Id: Icdf471ed3bed4eeb8c01f1d39f0b40c1ea098396
2018-01-05 17:09:52 -07:00
<permission name="android.permission.USE_RESERVED_DISK"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
</privapp-permissions>
<privapp-permissions package="com.android.providers.contacts">
<permission name="android.permission.BIND_DIRECTORY_SEARCH"/>
<permission name="android.permission.GET_ACCOUNTS_PRIVILEGED"/>
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
<permission name="android.permission.MANAGE_USERS"/>
Whitelist READ_PRIVILEGED_PHONE_STATE for the contacts provider In Android 10 access to device identifiers was moved from a runtime permission to the privileged READ_PRIVILEGED_PHONE_STATE permission. One of the non-resettable identifiers missed was SubscriptionInfo# getIccId. The contacts provider currently uses this ID to upgrade to version 1003 of the database; to ensure there are no issues with this upgrade this permission is being whitelisted for the contacts provider. Bug: 131909991 Test: atest ContactsProviderTests Change-Id: I7574f787a7e55aa0337237b9fe916ee143a2f697 Merged-In: I7574f787a7e55aa0337237b9fe916ee143a2f697 (cherry picked from commit 7b484438ec0f1e8763cb50bd9ffc96c155a776ef)
2020-02-19 23:37:42 -08:00
<permission name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.UPDATE_APP_OPS_STATS"/>
Start using new reserved disk GID. We recently created a new GID that can be granted to critical system processes, so that the system is usable enough for the user to free up disk space used by abusive apps. Define a permission for the GID so we can grant it to system apps, and add the GID to core apps needed for system stability. (The list was mostly derived from filling a disk and seeing what caused the device to fall over.) Test: builds, boots Bug: 62024591 Change-Id: Icdf471ed3bed4eeb8c01f1d39f0b40c1ea098396
2018-01-05 17:09:52 -07:00
<permission name="android.permission.USE_RESERVED_DISK"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
</privapp-permissions>
<privapp-permissions package="com.android.providers.downloads">
<permission name="android.permission.ACCESS_CACHE_FILESYSTEM"/>
<permission name="android.permission.CLEAR_APP_CACHE"/>
<permission name="android.permission.CONNECTIVITY_INTERNAL"/>
Add START_ACTIVITIES_FROM_BACKGROUND permission for com.android.providers.downloads Required because DownloadManager needs to whitelist a broadcast for bg activity starts. Bug: 135515407 Test: builds, boots (it wouldn't without this) Change-Id: Id6c22d1397417bbc10e2829e563f29cbccccd8bf
2019-06-18 15:39:46 +01:00
<permission name="android.permission.START_ACTIVITIES_FROM_BACKGROUND"/>
Allow DownloadProvider to have WRITE_MEDIA_STORAGE. It previously got this permission by sharing a UID with the MediaProvider, but now that that has become a mainline module, ask for it explicitly. Bug: 146378784 Test: boots Change-Id: I678efac65c8521ea9b7bec59aa193e637272cd57
2020-01-23 16:52:04 +01:00
<permission name="android.permission.WRITE_MEDIA_STORAGE"/>
Whitelist privapp MANAGE_EXTERNAL_STORAGE permission After adding MANAGE_EXTERNAL_STORAGE permission to several apps on the system partition, we should whitelist them Test: m Bug: 144914977 Change-Id: Ia4401904e23193b8628071d6a2a6d789faf0ece5
2020-01-27 13:28:26 +00:00
<permission name="android.permission.MANAGE_EXTERNAL_STORAGE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.UPDATE_APP_OPS_STATS"/>
<permission name="android.permission.UPDATE_DEVICE_STATS"/>
Add CONNECTIVITY_USE_RESTRICTED_NETWORKS permission to DownloadProvider - DownloadManager will use the requestor app's default network to open a connection. When the VPN app lists the DownloadProvider as a disallowed application, this will fail with EPERM. - This is because in R, the DownloadProvider lost its privileges due to the removal of the CONNECTIVITY_INTERNAL permission. It's removed without considering the corner case where the DownloadProvider is excluded from using the VPN. It's the only case where this makes a difference. - Adding CONNECTIVITY_USE_RESTRICTED_NETWORKS will give DownloadProvider the ability to use the VPN again in this case, fixing the issue. Bug: 165774987 Test: Build, flash rom and boot to home. Manully test that DownloadProvider can download file via VPN. Change-Id: If8fa785568ace1f15f53daec67c06e1207d5dc9c Merged-In: If8fa785568ace1f15f53daec67c06e1207d5dc9c
2020-09-18 16:22:45 +08:00
<permission name="android.permission.CONNECTIVITY_USE_RESTRICTED_NETWORKS"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
</privapp-permissions>
Structure MediaProvider as an APEX. Based on guidance from the Mainline team, we're placing the MediaProvider APK inside a new APEX, as this will allow us to move MediaStore.java inside the module boundary in a future CL. As part of this restructuring, we need the pre-Mainline APK to remain intact to preserve the user's media database. There is already logic in place from previous CLs that will migrate data from the pre-Mainline to the post-Mainline world, including tests to verify that the migration works. Bug: 144247087 Test: atest --test-mapping packages/providers/MediaProvider Change-Id: I4c45dcf019442013da8fce0223ed0be896dedef4
2019-11-21 15:56:46 -07:00
<privapp-permissions package="com.android.providers.media.module">
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
<permission name="android.permission.MANAGE_USERS"/>
Start using new reserved disk GID. We recently created a new GID that can be granted to critical system processes, so that the system is usable enough for the user to free up disk space used by abusive apps. Define a permission for the GID so we can grant it to system apps, and add the GID to core apps needed for system stability. (The list was mostly derived from filling a disk and seeing what caused the device to fall over.) Test: builds, boots Bug: 62024591 Change-Id: Icdf471ed3bed4eeb8c01f1d39f0b40c1ea098396
2018-01-05 17:09:52 -07:00
<permission name="android.permission.USE_RESERVED_DISK"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.WRITE_MEDIA_STORAGE"/>
Whitelist privapp MANAGE_EXTERNAL_STORAGE permission After adding MANAGE_EXTERNAL_STORAGE permission to several apps on the system partition, we should whitelist them Test: m Bug: 144914977 Change-Id: Ia4401904e23193b8628071d6a2a6d789faf0ece5
2020-01-27 13:28:26 +00:00
<permission name="android.permission.MANAGE_EXTERNAL_STORAGE"/>
Aggresive performance optimizations. Now that we have LocalCallingIdentity, we can start caching it in very narrow cases. We must be careful to not cache too long, since any changes to granted permissions for the UID mean we need to re-evaluate any cached answers. The best middle-ground for this in the Q release is to use an active camera session as a proxy for when we should create a cache object and then later invalidate it. (It's very unlikely that a user changes permissions while actively using the camera, and this is a strong signal that the caller is sensitive to performance.) Many other sprinkled optimizations to avoid extra binder calls into the OS, such as aggressively caching VolumeInfo related details. Track IDs that are owned by each LocalCallingIdentity, to speed up all future security checks. Dispatch all change notifications asynchronously, and delay them by several seconds while the camera is being actively used, to give more important foreground work a fighting chance. Invalidate thumbnails asynchronously. Optimizations to ModernMediaScanner where it's safe to skip the "reconcile" and "clean" steps when we're focused on a single file that we successfully scanned. Local tests show this CL improves performance of a test app that takes 100 rapid shots by 45%. (All the collective optimizations done so far this week add up to a 70% improvement.) Bug: 130758409 Test: atest --test-mapping packages/providers/MediaProvider Exempt-From-Owner-Approval: trivial manifest change Change-Id: I38cc826af47d41219ef44eae6fbd293caa0c01d5
2019-05-17 18:48:11 -06:00
<permission name="android.permission.WATCH_APPOPS"/>
Progress towards splitting MediaProvider UID. We're working towards making MediaProvider into a Mainline module, which means it can no longer share the "android.media" UID built into the OS. The major reason for this is because they're signed with separate keys, but a secondary reason is that we don't know what database customizations an OEM has performed in their MediaProvider. Ensure that packages are requesting the permissions they actually depend on, instead of relying on permissions requested by other packages under the shared UID. Bug: 144247087 Test: atest --test-mapping packages/providers/MediaProvider Change-Id: Iea42a69dd270682258314126f6540478aece3e59
2019-11-12 15:19:53 -07:00
<permission name="android.permission.UPDATE_APP_OPS_STATS"/>
Shift call statistics back to the original caller. Most of the time MediaProvider is making Binder calls on behalf of an external caller, so use PropagateWorkSourceTransactListener to ensure that we record the original source. Bug: 125725916 Test: atest --test-mapping packages/apps/MediaProvider Change-Id: I591dfb2903a54239639452954ea2d780e79b280c
2019-05-30 12:18:32 -06:00
<permission name="android.permission.UPDATE_DEVICE_STATS"/>
Whitelist PlatformCompat permissions for MediaProvider Bug: 132649864 Test: builds Change-Id: If3d37a00f607e3cbe16a943c89bfbf3e7c100b5d
2020-02-10 14:25:05 +00:00
<!-- Permissions required for reading and logging compat changes -->
<permission name="android.permission.LOG_COMPAT_CHANGE" />
<permission name="android.permission.READ_COMPAT_CHANGE_CONFIG" />
Allow MediaProvider to request REGISTER_STATS_PULL_ATOM MediaProvider needs the permission to register a StatsPullCallback in statsd to pull the external storage metrics. Test: build Bug: 149669087 Change-Id: I4f7e09c2e514e2290d1cd5ac765bb115e7ade9ef
2020-06-16 13:31:02 +01:00
<permission name="android.permission.REGISTER_STATS_PULL_ATOM" />
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
</privapp-permissions>
<privapp-permissions package="com.android.providers.telephony">
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
<permission name="android.permission.MODIFY_PHONE_STATE"/>
Start using new reserved disk GID. We recently created a new GID that can be granted to critical system processes, so that the system is usable enough for the user to free up disk space used by abusive apps. Define a permission for the GID so we can grant it to system apps, and add the GID to core apps needed for system stability. (The list was mostly derived from filling a disk and seeing what caused the device to fall over.) Test: builds, boots Bug: 62024591 Change-Id: Icdf471ed3bed4eeb8c01f1d39f0b40c1ea098396
2018-01-05 17:09:52 -07:00
<permission name="android.permission.USE_RESERVED_DISK"/>
Add PlatformCompat permissions to TelephonyProvider Add the required permissions for querying PlatformCompat to the whitelist for TelephonyProvider. This is the minimum scoped permission -- PlatformCompat only defines two permissions for access (read and write) and we need both. The alternative for using these permissions is to not call PlatformCompat and enforce the new behavior on all apps. This was deemed unacceptable by the app compat team because it was breaking some popular apps. Bug: 144631034 Test: atest TelephonyProviderHostTest Change-Id: I43a0a66ae381caf8d9e21d0f14d471b20a4e44af
2020-02-25 15:59:03 -08:00
<!-- Permissions required for reading and logging compat changes -->
<permission name="android.permission.LOG_COMPAT_CHANGE" />
<permission name="android.permission.READ_COMPAT_CHANGE_CONFIG" />
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
</privapp-permissions>
Rename NetworkStack package Set the new name to com.android.networkstack. Also rename the stub APK to com.android.networkstack.permissionstub. Also add shared UID to the NetworkStackPermissionStub to enforce signature restrictions on the UID. Test: booted, WiFi working Bug: 124033493 Change-Id: Id8967db08b7faaa659b20f86f1013493eb0e188f
2019-02-08 15:26:06 +09:00
<privapp-permissions package="com.android.networkstack">
Add priv-app permissions for NetworkStack Bug: b/112869080 Test: m, flashed, booted Change-Id: Ia2cf0f708d815a5e5f49924fb15bb9c728f4ad56
2018-12-27 11:49:21 +09:00
<permission name="android.permission.ACCESS_NETWORK_CONDITIONS"/>
<permission name="android.permission.CONNECTIVITY_INTERNAL"/>
<permission name="android.permission.CONNECTIVITY_USE_RESTRICTED_NETWORKS"/>
<permission name="android.permission.CONTROL_VPN"/>
Remove INTERACT_ACROSS_USERS_FULL for NetworkStack Replace with INTERACT_ACROSS_USERS, which is needed to send the ACTION_NETWORK_CONDITIONS_MEASURED broadcast. Also cleanup some non-privileged permissions that were added to the priv-app file. Test: built, booted, broadcast and captive portal login work Bug: 123846255 Change-Id: I3c97c166e80c19bf57fa047709c8b91fca75d635
2019-02-04 14:26:32 +09:00
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
Add priv-app permissions for NetworkStack Bug: b/112869080 Test: m, flashed, booted Change-Id: Ia2cf0f708d815a5e5f49924fb15bb9c728f4ad56
2018-12-27 11:49:21 +09:00
<permission name="android.permission.LOCAL_MAC_ADDRESS"/>
<permission name="android.permission.MANAGE_SUBSCRIPTION_PLANS"/>
<permission name="android.permission.MANAGE_USB"/>
Add privapp permissions to network modules. When built as part of the system, the network stack and the captive portal login app should have the BYPASS_PRIVATE_DNS and CONNECTIVITY_USE_RESTRICTED_NETWORKS permissions. These are necessary to validate restricted networks, bypass VPNs, bypass private DNS for captive portal login, etc. Add these permissions to privapp-permissions-platform.xml. When installed as mainline modules that cannot use signature permissions, the modules get this ability by virtue of having the MAINLINE_NETWORK_STACK permissions. Additionally, add the CONNECTIVITY_USE_RESTRICTED_NETWORKS permission to the captive portal login app manifest, which did not contain it. Bug: 129789428 Test: builds, boots Test: dumpsys package shows permissions Change-Id: I632359f7eff09fed71167733ac75824a5aa57894 Merged-In: I632359f7eff09fed71167733ac75824a5aa57894 (cherry picked from commit 109dbf9c05f325d6f8298ffa81b9e90668fddaf3)
2019-04-24 19:28:20 -07:00
<permission name="android.permission.NETWORK_BYPASS_PRIVATE_DNS"/>
Add priv-app permissions for NetworkStack Bug: b/112869080 Test: m, flashed, booted Change-Id: Ia2cf0f708d815a5e5f49924fb15bb9c728f4ad56
2018-12-27 11:49:21 +09:00
<permission name="android.permission.PACKET_KEEPALIVE_OFFLOAD"/>
<permission name="android.permission.READ_NETWORK_USAGE_HISTORY"/>
<permission name="android.permission.READ_PRECISE_PHONE_STATE"/>
<permission name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>
<permission name="android.permission.READ_WIFI_CREDENTIAL"/>
<permission name="android.permission.RECEIVE_DATA_ACTIVITY_CHANGE"/>
<permission name="android.permission.TETHER_PRIVILEGED"/>
<permission name="android.permission.WRITE_SECURE_SETTINGS"/>
</privapp-permissions>
Change Tethering package name ".apex" is easy to confuse. Rename as below: apex: com.android.tethering.apex -> com.android.tethering apk: com.android.tethering -> com.android.networkstack.tethering Bug: 146471733 Test: build Change-Id: I2c7647abb996539a3af6cfe0e0214a5e8927c0d6
2019-12-18 17:47:26 +08:00
<privapp-permissions package="com.android.networkstack.tethering">
Give tethering bluetooth privilege permission Permisssion of PanService#setBluetoothTethering is change from BLUETOOTH_ADMIN to BLUETOOTH_PRIVILEGED. Tethering service need bluetooth privilege permission to enable bluetooth tethering. Bug: 146045934 Test: on/off bluetooth tethering Merged-In: Ib87a5d5a5bb49390aa55e52713bb3539d4a52348 Change-Id: Ib87a5d5a5bb49390aa55e52713bb3539d4a52348
2020-03-12 15:22:01 +08:00
<permission name="android.permission.BLUETOOTH_PRIVILEGED" />
[Tether11] Grant privileged permissions for tethering Since tethering is moved from systemServer to networkStack process, it would lose privileged capability. Grant privileged permissions for tethering individually. Grant MANAGE_USB to control usb rndis function. Grant MODIFY_PHONE_STATE to know whether DUN is required. Grant READ_NETWORK_USAGE_HISTORY to update tethering usage. Grant UPDATE_APP_OPS_STATS to check WRITE_SETTINGS permission. Bug: 144320246 Test: -build, flash, boot -atest TetheringTests Change-Id: Id6e71b58e027d6ba90551084367ef881652c2555
2019-11-24 23:26:26 +08:00
<permission name="android.permission.MANAGE_USB"/>
<permission name="android.permission.MODIFY_PHONE_STATE"/>
<permission name="android.permission.READ_NETWORK_USAGE_HISTORY"/>
Give tethering TETHER_PRIVILEGED permission This fix the crash when perform "Reset Wi-Fi,mobile & Bluetooth" Bug: 146900199 Test: -build, flash, boot -atest TetheringTests -atest CtsTetheringTest -manual perform "Reset Wi-Fi,mobile & Bluetooth" Change-Id: I036409358ed15a797bdb751bb66513425350d066
2020-01-10 00:21:17 +08:00
<permission name="android.permission.TETHER_PRIVILEGED"/>
[Tether11] Grant privileged permissions for tethering Since tethering is moved from systemServer to networkStack process, it would lose privileged capability. Grant privileged permissions for tethering individually. Grant MANAGE_USB to control usb rndis function. Grant MODIFY_PHONE_STATE to know whether DUN is required. Grant READ_NETWORK_USAGE_HISTORY to update tethering usage. Grant UPDATE_APP_OPS_STATS to check WRITE_SETTINGS permission. Bug: 144320246 Test: -build, flash, boot -atest TetheringTests Change-Id: Id6e71b58e027d6ba90551084367ef881652c2555
2019-11-24 23:26:26 +08:00
<permission name="android.permission.UPDATE_APP_OPS_STATS"/>
[SP06.1] Add UPDATE_DEVICE_STATS permission to Tethering Add corresponding permission to allow tether offload to update network usage through new API that requires UPDATE_DEVICE_STATS permission. This is the minimum permission that required to update network usage with the new system api. Test: atest FrameworksNetTests OffloadControllerTest TetheringTest Bug: 130855321 Change-Id: I9c0c86e20d4797ea3570feed741be3a07f839c7d
2020-01-10 13:27:24 +08:00
<permission name="android.permission.UPDATE_DEVICE_STATS"/>
[Tether11] Grant privileged permissions for tethering Since tethering is moved from systemServer to networkStack process, it would lose privileged capability. Grant privileged permissions for tethering individually. Grant MANAGE_USB to control usb rndis function. Grant MODIFY_PHONE_STATE to know whether DUN is required. Grant READ_NETWORK_USAGE_HISTORY to update tethering usage. Grant UPDATE_APP_OPS_STATS to check WRITE_SETTINGS permission. Bug: 144320246 Test: -build, flash, boot -atest TetheringTests Change-Id: Id6e71b58e027d6ba90551084367ef881652c2555
2019-11-24 23:26:26 +08:00
</privapp-permissions>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<privapp-permissions package="com.android.server.telecom">
<permission name="android.permission.BIND_CONNECTION_SERVICE"/>
<permission name="android.permission.BIND_INCALL_SERVICE"/>
<permission name="android.permission.CALL_PRIVILEGED"/>
Add prioritized enableCarMode API in UiModeManager Per design doc (go/android-car-mode-design), added new system API to enable car mode and specify a priority for the calling app. Also modified UiModeManager to pass the package name of the caller to UiModeManagerService. Bug: 136109592 Test: Added new unit tests and CTS tests. Test: Added Telecom test app functionality to verify. Change-Id: I2848039c9ea18ba93e7694e04c4e5dc70759daa3
2019-09-30 15:12:24 -07:00
<permission name="android.permission.HANDLE_CAR_MODE_CHANGES"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
<permission name="android.permission.MANAGE_USERS"/>
Change command like set-default-dialer to be a test override. RoleManager likes to terminate apps when roles are changed which does not work in CTS tests. We need to use a temp override in Telecom for now. Test: Run the CTS tests over, and over and over again. Bug: 131065482 Change-Id: Id36942f2813abdfa0020ce4805c492a69bd07d0e (cherry picked from commit 509ef150f23531b18fe29ef85337312f54535300)
2019-04-25 14:28:47 -07:00
<permission name="android.permission.MANAGE_ROLE_HOLDERS"/>
Add call recording tone support. Adding carrier configuration option to specify whether the carrier requires the incall recording tone be played. Added phone account extra used in Telephony to communicate this to Telecom. Added permission pregrant for Telecom for MODIFY_AUDIO_ROUTING; this is needed as Telecom listening to the AudioRecordingConfiguration callback from the audio framework. It needs the permission so that it can be informed of the package names of recording apps. Test: Manually enabled for local carrier and confirmed that recording tone plays to remote party when a recording app is started on the device. Bug: 64138141 Change-Id: I1ab521b79cbeeb4ff4dcbf83de7c17c539637bdc
2018-01-29 14:30:52 -08:00
<permission name="android.permission.MODIFY_AUDIO_ROUTING" />
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.MODIFY_PHONE_STATE"/>
<permission name="android.permission.STOP_APP_SWITCHES"/>
Add SUBSTITUTE_NOTIFICATION_APP_NAME pregrant for Telecom. Test: Manual Bug: 36817809 Change-Id: I2d7439e3d0040b617a842812b6ae8bda3c32f1ee
2017-03-31 17:50:56 -07:00
<permission name="android.permission.SUBSTITUTE_NOTIFICATION_APP_NAME"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
</privapp-permissions>
<privapp-permissions package="com.android.sharedstoragebackup">
<permission name="android.permission.WRITE_MEDIA_STORAGE"/>
Whitelist privapp MANAGE_EXTERNAL_STORAGE permission After adding MANAGE_EXTERNAL_STORAGE permission to several apps on the system partition, we should whitelist them Test: m Bug: 144914977 Change-Id: Ia4401904e23193b8628071d6a2a6d789faf0ece5
2020-01-27 13:28:26 +00:00
<permission name="android.permission.MANAGE_EXTERNAL_STORAGE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
</privapp-permissions>
<privapp-permissions package="com.android.shell">
Persist dark mode when set When setting dark mode, the changes dont persist Test: atest UiModeManagerServiceTest Change-Id: I6c18cf096510d79cff9c0d6eac830f7b9209166c
2019-12-12 14:17:22 -05:00
<!-- Needed for test only -->
<permission name="android.permission.MODIFY_DAY_NIGHT_MODE"/>
Crash if not all privileged permissions are whitelisted Test: reboot device - no crashes Test: Ran privapp_permissions.py for fugu/marlin/taimen Bug: 64693550 Change-Id: I9522ccaa75858b9a3d153c95c529eff70cd13994
2017-10-06 17:02:21 -07:00
<permission name="android.permission.ACCESS_LOWPAN_STATE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.BACKUP"/>
<permission name="android.permission.BATTERY_STATS"/>
<permission name="android.permission.BIND_APPWIDGET"/>
Make CHANGE_APP_IDLE_STATE a system API Allows a privileged app to set standby bucket states for apps. Bug: 63527785 Test: adb shell am set-standby-bucket com.example.foo 0 Change-Id: I613f8872ae816e39b167aad1c289187362aa6094
2017-10-31 13:29:00 -07:00
<permission name="android.permission.CHANGE_APP_IDLE_STATE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.CHANGE_COMPONENT_ENABLED_STATE"/>
<permission name="android.permission.CHANGE_CONFIGURATION"/>
Give shell the CHANGE_DEVICE_IDLE_TEMP_WHITELIST permission Shell needs to have this permission in order for the deviceidle tempwhitelist shell command to exist. Bug 34715096 Test: cts-tradefed run cts -m CtsAppTestCases \ -t android.app.cts.ActivityManagerTest#testBackgroundCheckService Change-Id: Ic1fdd87b6020649705ba0c9349dd00dd096037f3
2017-03-21 17:43:47 -07:00
<permission name="android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST" />
Crash if not all privileged permissions are whitelisted Test: reboot device - no crashes Test: Ran privapp_permissions.py for fugu/marlin/taimen Bug: 64693550 Change-Id: I9522ccaa75858b9a3d153c95c529eff70cd13994
2017-10-06 17:02:21 -07:00
<permission name="android.permission.CHANGE_LOWPAN_STATE"/>
Whitelist new CHANGE_OVERLAY_PACKAGES permission The Shell application needs access to change which overlays are enabled in OverlayManagerService. Test: Manual: invoke adb exec-out cmd overlay enable some.package.name when shell is not root (adb unroot on eng builds). Change-Id: I1849f68e244cfc9b1e13eb0e673dde7be03cba6d
2017-02-23 18:17:11 -08:00
<permission name="android.permission.CHANGE_OVERLAY_PACKAGES"/>
Grant Shell ability to clear cached app data. It already has CLEAR_APP_USER_DATA to clear everything inside app storage, and clearing cached data is a subset of that. Test: cts-tradefed run commandAndExit cts-dev -m CtsAppSecurityHostTestCases -t android.appsecurity.cts.StorageHostTest Bug: 36731175 Change-Id: Iefc5be6c80e2562a95424fd6fe413bdb018201a9
2017-04-09 21:37:56 -06:00
<permission name="android.permission.CLEAR_APP_CACHE"/>
Grant Shell ability to clear instant app It already has grant to clear data of application, and instant application is a subset of that. This permission is needed for correct performing of the test: `android.appsecurity.cts.InstantCookieHostTest# testCookieUpdateAndRetrieval`. Bug: 77849650 Test: run several times in a row (at least two), note that first time on the fresh DUT the result is always successful: cts-tradefed run commandAndExit cts-dev \ -m CtsAppSecurityHostTestCases \ -t android.appsecurity.cts.InstantCookieHostTest#testCookieUpdateAndRetrieval Change-Id: I2d6080259e22ebfa40481213238f569e0988d271 Signed-off-by: Sergii Piatakov <sergii.piatakov@globallogic.com>
2018-04-02 16:48:56 +03:00
<permission name="android.permission.ACCESS_INSTANT_APPS" />
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.CONNECTIVITY_INTERNAL"/>
<permission name="android.permission.DELETE_CACHE_FILES"/>
<permission name="android.permission.DELETE_PACKAGES"/>
<permission name="android.permission.DUMP"/>
Add permission for protecting UI tracing The new permission will protect the UI traces, allowing only wanted development tools to start the tracing. At the moment, the permission is planned to be used for WindowManager and InputMethod traces. Bug: 172444310 Test: N/A Change-Id: Ibdeb38dc9a066cb8ed2904adcdac29014b166526
2020-11-16 16:58:10 +00:00
<permission name="android.permission.CONTROL_UI_TRACING"/>
DO NOT MERGE Add permission to launch activities on VD 1. Added permission ACTIVITY_EMBEDDING which allows apps to launch activities on virtual displays. 2. Allow owner of display to launch activities from same app without permission check to owned display. 3. Added permission checks for launching on secondary displays to more target task/stack resolution paths in ActivityStarter. Bug: 63117330 Test: android.server.cts.ActivityManagerDisplayTests Test: go/wm-smoke Change-Id: If169a77fb56241e06f7de20168dc38c4b0a217f5 (cherry picked from commit 71587649836d8e97c2ca00d968fc95293b59b0d3)
2017-07-06 14:28:59 -07:00
<permission name="android.permission.ACTIVITY_EMBEDDING"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.FORCE_STOP_PACKAGES"/>
<permission name="android.permission.GET_APP_OPS_STATS"/>
Grant com.android.shell access to DynamicSystem Add permission INSTALL_DYNAMIC_SYSTEM to Shell's AndroidManifest.xml and privapp-permissions-platform.xml. Bug: 124637092 Test: adb shell am start-activity Change-Id: Id7727a195f61c2fbffa0b2f52f3098784feeee52
2019-02-21 09:58:02 +08:00
<permission name="android.permission.INSTALL_DYNAMIC_SYSTEM"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.INSTALL_LOCATION_PROVIDER"/>
<permission name="android.permission.INSTALL_PACKAGES"/>
Add INTERACT_ACROSS_PROFILES permission to shell for CTS test. Bug: 127804311 Test: atest CrossProfileAppsHostSideTest#testStartActivity Change-Id: I1deb66409fae1ec654555adb8d4a61d670689d2a
2019-05-17 17:28:50 -07:00
<!-- Needed for test only -->
<permission name="android.permission.INTERACT_ACROSS_PROFILES"/>
Permission flag updates now notify listeners Added a version of the onPermissionUpdated and onInstallPermissionUpdated methods which will notify OnPermissionChangedListeners, and added this to the PermissionManagerService "updatePermissionFlags" and "updatePermissionFlagsForAllApps" methods. Also adds OnPermissionsChangedListener to @TestApi Fixes: 135937566 Test: atest PermissionUpdateListenerTest Change-Id: I906598c366234c3daaa202261678bca04837cb13
2019-06-07 13:11:58 -07:00
<!-- Permission required to test onPermissionsChangedListener -->
<permission name="android.permission.OBSERVE_GRANT_REVOKE_PERMISSIONS"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.INTERACT_ACROSS_USERS"/>
Restrict access from apps to bluetooth_address setting BluetoothManagerService for some reason leaks the Android's Bluetooth MAC address via Settings.Secure which is normally readable by all apps. This lets apps bypass the restriction on access to Bluetooth MAC address from apps. This commit fixes the issue by restricting access to bluetooth_address secure setting (Settings.Secure). Only packages which hold the android.permission.LOCAL_MAC_ADDRESS permission retain access. This commit accordingly grants LOCAL_MAC_ADDRESS permission to the system Shell app because a number of scripts (including Android CTS) use "adb shell settings get secure bluetooth_address" as a convenient way to query the device's Bluetooth MAC address over ADB. This is acceptable because the user of the device can see the Bluetooth MAC address and thus it's fine for shell to be able to see the address as well. Test: See CTS test added in the cts project in this topic. Test: "adb shell settings get secure bluetooth_address" returns the Bluetooth MAC address of the Android. Test: "adb shell settings list secure | grep bluetooth_address" returns the Bluetooth MAC address of the Android. Test: Bluetooth works (toggling off/on, pairing, file transfer) Bug: 33701414 Change-Id: I17b110b96eb3794b25c1661e93d29a7a003e3c9a
2017-03-03 14:08:36 -08:00
<permission name="android.permission.LOCAL_MAC_ADDRESS"/>
Make performAccessibilityShortcut a SystemAPI Also create a new MANAGE_ACCESSIBILITY permission to perform the shortcut. Bug: 116118615 Test: make, activate accessibility shortcut Change-Id: Ic65a0cdf7393429e14cb98f4fb0734d20069b05a
2018-10-09 15:01:49 -07:00
<permission name="android.permission.MANAGE_ACCESSIBILITY"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.MANAGE_DEVICE_ADMINS"/>
Make MANAGE_ROLLBACKS a privileged permission. Test: N/A Bug: 144843717 Change-Id: I7118b525256f15ee33a6107a2e39173628306872
2020-01-21 21:18:53 +00:00
<permission name="android.permission.MANAGE_ROLLBACKS"/>
Allow the shell to set USB functions. Bug: 25596495 Test: svc usb setFunction mtp true Change-Id: I4472464a1c7ed100cb257dbad83d1d8cfef88fc7
2017-02-17 11:46:58 -08:00
<permission name="android.permission.MANAGE_USB"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.MODIFY_APPWIDGET_BIND_PERMISSIONS"/>
Add day-night-mode permission to Shell. Without the permission "adb shell cmd uimode night <mode>" doesn't work. Adding the permission to the AndroidManifest file so the shell command will work. Bug: 155584597 Test: run `adb shell cmd uimode night <no|yes|auto>` Change-Id: Ic444f3351cb130d24a2794284c6bf8709c80712c (cherry picked from commit a85cc220442c9a5033f926d8b9f708faa93990ef)
2020-05-11 23:50:19 +00:00
<permission name="android.permission.MODIFY_DAY_NIGHT_MODE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.MODIFY_PHONE_STATE"/>
<permission name="android.permission.MOUNT_FORMAT_FILESYSTEMS"/>
<permission name="android.permission.MOUNT_UNMOUNT_FILESYSTEMS"/>
<permission name="android.permission.MOVE_PACKAGE"/>
Grant shell permissions for Airplane Mode to Shell to support CTS New permission is needed to allow CTS to trigger the new WiFi subsystem restart API. Bug: 175084231 Test: atest android.net.wifi.cts.WifiManagerTest#testRestartWifiSubsystem Change-Id: Id844fb799c61f65580e686d1da7ec38a62dd01d0
2020-12-09 21:22:16 -08:00
<!-- Needed for test only -->
Grant shell permissions for restart WiFi subsystem to Shell to support CTS New permission is needed to allow CTS to trigger the new WiFi subsystem restart API. Bug: 175084231 Bug: 178125790 Test: atest android.net.wifi.cts.WifiManagerTest#testRestartWifiSubsystem Change-Id: I0eb0362e6421480c10ba64f923a9069d1258d4ca
2021-01-21 16:45:46 -08:00
<permission name="android.permission.RESTART_WIFI_SUBSYSTEM"/>
Add OBSERVE_APP_USAGE permission to shell for CTS test. Bug: 123314449 Test: atest android.content.pm.cts.LauncherAppsTest Change-Id: I5e58aefa9920dd4a974d24388f8ecd8dea7936b3
2019-01-24 07:19:14 -08:00
<permission name="android.permission.OBSERVE_APP_USAGE"/>
Add shell permissions for CTS testing Add NETWORK_SCAN to shell permissions to enable CTS testing of the network scan changes Bug: 126779616 Test: CTS Change-Id: I1f75c9005620b3b0e06f066677cba6190f1d266c
2019-02-28 15:29:19 -08:00
<permission name="android.permission.NETWORK_SCAN"/>
Add PACKAGE_USAGE_STATS permission to shell. This is needed for calling AM.registerUidObserver. Fixes: 64400666 Test: cts-tradefed run singleCommand cts-dev -m CtsAppTestCases -t \ android.app.cts.ActivityManagerProcessStateTest Change-Id: I4f500d0d8d516b6b8961ea2f8c083add3ae949a9
2017-09-01 16:41:10 -07:00
<permission name="android.permission.PACKAGE_USAGE_STATS" />
[KA09] add keepalive offload permission to shell This change adds PACKET_KEEPALIVE_OFFLOAD to shell, which allows shell or code with shell permission identity to use privileged tcp keepalive offload API. Bug: 114151147 Test: -atest ConnectivityManagerTest#testCreateTcpKeepalive -build, flash, boot Change-Id: Ib6660a5eaa72f83042596481452be4d415383f02
2019-01-23 17:24:10 +08:00
<!-- Needed for test only -->
<permission name="android.permission.PACKET_KEEPALIVE_OFFLOAD" />
Create APIs to interact with DynamicPowerSaver This creates the PowerManager APIs that allow apps with the appropriate permissions to interact with Dynamic Power Saver. Bug: 111450127 Test: WIP Change-Id: I5b9483fa0fba81a4ade622b1f3dbaec580b68a67
2018-10-19 13:03:20 -07:00
<permission name="android.permission.POWER_SAVER" />
Add system service for accessing SystemConfig Add SystemConfigService and associated AIDLs and permissions for accessing SystemConfig. The service returns values obtained from a static instance of com.android.server.SystemConfig. Bug: 143112379 Test: atest SystemConfigTest Change-Id: I1a863ae9f53db21d698376008e5b1da83309b141
2019-12-23 18:11:10 -08:00
<permission name="android.permission.READ_CARRIER_APP_INFO"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.READ_FRAME_BUFFER"/>
Crash if not all privileged permissions are whitelisted Test: reboot device - no crashes Test: Ran privapp_permissions.py for fugu/marlin/taimen Bug: 64693550 Change-Id: I9522ccaa75858b9a3d153c95c529eff70cd13994
2017-10-06 17:02:21 -07:00
<permission name="android.permission.READ_LOWPAN_CREDENTIAL"/>
new SystemAPI for preciseCallState and DisconnectCause 1. decouple disconnectCause and preciseDisconnectCuase from preciseCallState. 2. expose preciseCallState to SystemAPI and expose onPreciseCallStateChanged to System API 3. remove/hide ImsReasonInfo from PreciseDisconnectCuase 4. expose DiconnectCuase and PreciseDisconnectCause to System API 5. new onDisconnectCauseChanged API on PhoneStateListener for CS call and use ImsCallSessionListener for IMS call(imsreasonInfo) 6. add read_precise_phone_state to shell apk to enable GTS test Bug: 119890559 Test: atest GtsGmscoreHostTestCases:TelephonyHostTest#testPhoneStateListener Change-Id: If9256feff16b6bcaef1dfe194c2b0df2a48436b0
2018-12-12 19:59:30 -08:00
<!-- Needed for test only -->
<permission name="android.permission.READ_PRECISE_PHONE_STATE" />
Protect Device Identifiers behind priv permission and DO/PO checks Bug: 110099294 Test: cts-tradefed run cts -m CtsDevicePolicyManagerTestCases \ -t com.android.cts.devicepolicy.DeviceOwnerTest.testDeviceOwnerCanGetDeviceIdentifiers Test: cts-tradefed run cts -m CtsDevicePolicyManagerTestCases \ -t com.android.cts.devicepolicy.ManagedProfileTest#testGetDeviceIdentifiers Test: cts-tradefed run cts -m CtsTelephonyTestCases -t android.telephony.cts.TelephonyManagerTest Test: cts-tradefed run cts -m CtsPermissionTestCases -t android.permission.cts.TelephonyManagerPermissionTest Change-Id: I3c82c53ec89cd17b34a61166ccc9e9747388efac
2018-10-01 16:14:50 -07:00
<permission name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>
Shell: Allow retrieval of wifi network credentials This permission is needed for some wifi CTS tests. Is the minimally scoped permission that needs to be added? - Yes, this only allows the retireval of the saved wifi network credentials on the device. What options did you explore that did not need this permission? - Possibly creating a UI to ask for manual entry of network credentials. But, that would not let us do automated CTS tests (will need to become CTS verifier tests then). Bug: 150236894 Test: atest android.net.wifi.cts.WifiNetworkSpecifierTest Change-Id: I6881003510191f667950be1ab27a5399fe3914b4
2020-03-02 13:04:17 -08:00
<permission name="android.permission.READ_WIFI_CREDENTIAL"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.REAL_GET_TASKS"/>
Add READ_PRIVILEGED_PHONE_STATE to used permissions Bug: 110099294 Test: cts-tradefed run cts -m CtsTelephonyTestCases -t android.telephony.cts.TelephonyManagerTest Change-Id: I13fec3d397c200ce92883883c96c07007e823efe
2018-10-08 09:39:24 -07:00
<permission name="android.permission.READ_PRIVILEGED_PHONE_STATE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.REGISTER_CALL_PROVIDER"/>
<permission name="android.permission.REGISTER_CONNECTION_MANAGER"/>
<permission name="android.permission.REGISTER_SIM_SUBSCRIPTION"/>
<permission name="android.permission.RETRIEVE_WINDOW_CONTENT"/>
<permission name="android.permission.SET_ALWAYS_FINISH"/>
<permission name="android.permission.SET_ANIMATION_SCALE"/>
<permission name="android.permission.SET_DEBUG_APP"/>
<permission name="android.permission.SET_PROCESS_LIMIT"/>
Add set-time and set-timezone shell cmds to alarm service These commands allow a user to set the time and the timezone from the shell. The shell now has signature|privileged SET_TIME and SET_TIME_ZONE permissions. Bug: 67751701 Test: manual - correctly sets the time and timezone from unrooted adb. Change-Id: I1d2820fd7dadd8b1f3900c0592eb28210370ce88
2018-02-01 10:13:10 -08:00
<permission name="android.permission.SET_TIME"/>
<permission name="android.permission.SET_TIME_ZONE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.SIGNAL_PERSISTENT_PROCESSES"/>
Grant STATUS_BAR permission to com.android.shell Allows for testing APIs protected by this permission from CTS tests Test: adb shell dumpsys package com.android.shell | grep "\bSTATUS_BAR: granted=true" # should find the permission Bug: 130178313 Change-Id: Ida0950664b98217d9c0801c0f19436c754ee6744
2019-04-17 16:47:54 -04:00
<permission name="android.permission.STATUS_BAR"/>
Add a new START_ACTIVITIES_FROM_BACKGROUND signature|privileged|vendorPrivileged|oem permission And grant it to SystemUI and Shell (adb shell am start). Bug: 110956953 Test: atest WmTests:ActivityStarterTests Change-Id: I4885a9a62ee8d47a3aef85f0e34b746c3f51ca2b
2018-12-14 15:17:29 +00:00
<permission name="android.permission.START_ACTIVITIES_FROM_BACKGROUND" />
Allow the shell to start task overlay activities. - Fix issue with testFinishPipActivityWithTaskOverlay failing due to new permission check in the system Bug: 71716434 Test: atest CtsActivityManagerDeviceTestCases:ActivityManagerPinnedStackTests#testFinishPipActivityWithTaskOverlay Change-Id: Ifbcd6c182d928f5aa5372d2db9fa71a142dc8474
2018-03-17 12:51:14 -07:00
<permission name="android.permission.START_TASKS_FROM_RECENTS" />
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.STOP_APP_SWITCHES"/>
<permission name="android.permission.SUBSTITUTE_NOTIFICATION_APP_NAME"/>
Add SUSPEND_APPS permission to shell Since this permission protects system apis, this is required for instrumentation tests. Test: atest com.google.android.suspendapps.gts.SuspendPackagesTest Bug: 79773970 Change-Id: Ib283018c50cc19c3958bd61e2d19befbf2805cc5
2018-07-16 13:23:21 -07:00
<permission name="android.permission.SUSPEND_APPS" />
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.UPDATE_APP_OPS_STATS"/>
Start using new reserved disk GID. We recently created a new GID that can be granted to critical system processes, so that the system is usable enough for the user to free up disk space used by abusive apps. Define a permission for the GID so we can grant it to system apps, and add the GID to core apps needed for system stability. (The list was mostly derived from filling a disk and seeing what caused the device to fall over.) Test: builds, boots Bug: 62024591 Change-Id: Icdf471ed3bed4eeb8c01f1d39f0b40c1ea098396
2018-01-05 17:09:52 -07:00
<permission name="android.permission.USE_RESERVED_DISK"/>
Shell: Allow usage of wifi usability score APIs This permission is needed for wifi CTS tests. Is the minimally scoped permission that needs to be added? - Yes, this only allows the app to influnce wifi vs lte network selection algorithm. What options did you explore that did not need this permission? - Without this permission, it would be impossible to test these API's: WifiManager.setWifiConnectedNetworkScorer() WifiManager.clearWifiConnectedNetworkScorer() WifiManager.clearWifiConnectedNetworkScorer() WifiManager.addOnWifiUsabilityStatsListener() Bug: 150236894 Test: Device boots up. Change-Id: Ic173e44ab818cdfecebde80715ddaec347019db6
2020-03-19 12:28:55 -07:00
<permission name="android.permission.WIFI_UPDATE_USABILITY_STATS_SCORE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.WRITE_MEDIA_STORAGE"/>
Whitelist privapp MANAGE_EXTERNAL_STORAGE permission After adding MANAGE_EXTERNAL_STORAGE permission to several apps on the system partition, we should whitelist them Test: m Bug: 144914977 Change-Id: Ia4401904e23193b8628071d6a2a6d789faf0ece5
2020-01-27 13:28:26 +00:00
<permission name="android.permission.MANAGE_EXTERNAL_STORAGE"/>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<permission name="android.permission.WRITE_SECURE_SETTINGS"/>
Tests for matchesCallFilter Test: cts Bug: 123406095 Change-Id: Ibece70d3e5d77d447ece4f3d3118b315a8d6e5cb
2019-01-29 16:19:36 -05:00
<permission name="android.permission.STATUS_BAR_SERVICE"/>
Add IncidentCompanionService It is a helper in the system process that helps dumpstate and incidentd get user confirmation to share reports Bug: 123543706 Test: bit GooglePermissionControllerTest:* Change-Id: Ia3fe4bd5257044ed89fe56ce683876fa03ba6c36
2018-12-18 15:00:25 -08:00
<permission name="android.permission.REQUEST_INCIDENT_REPORT_APPROVAL"/>
Add CONTROL_KEYGUARD_SECURE_NOTIFICATIONS to shell app Shell app needs the permission when we run KeyguardManager CTS for allowing private notifications as a privileged app. Bug: 127351183 Test: m -j Change-Id: I199bac8c8fed9ff0fc63b8c62f8002a6b273b28f
2019-03-19 21:45:49 +00:00
<permission name="android.permission.CONTROL_KEYGUARD_SECURE_NOTIFICATIONS"/>
Add Shell permission for CTS test. Add Shell permission for new CTS tests to test the multi-display functionality in WallpaperService/WallpaperManagerService. Bug: 123707989 Test: atest WallpaperManagerMultiDisplayTests Test: atest ActivityManagerMultiDisplayTests Change-Id: Id97db050a0b9d1940c2dfaa793fbe526df578105
2019-02-20 23:08:45 +08:00
<permission name="android.permission.SET_WALLPAPER" />
<permission name="android.permission.SET_WALLPAPER_COMPONENT" />
Adjust testapis/permissions for CTS tests Test: cts Bug: 127341023 Change-Id: Ice19dc337a06a3f20edca583ecbe5ef3148fd96d
2019-04-08 10:35:40 -04:00
<permission name="android.permission.REQUEST_NOTIFICATION_ASSISTANT_SERVICE" />
Adding incremental related peremissions to Shell This is expected to be used with adoptShellPermission in the Incremental CTS tests. Test: atest android.content.pm.cts.PackageManagerShellCommandTest (There will be future tests relying on this) Bug: 158024822 Change-Id: I46674498783c5323668ff775c76ff31a304aeadb
2020-06-03 15:12:41 -07:00
<!-- Permissions required for Incremental CTS tests -->
<permission name="com.android.permission.USE_INSTALLER_V2"/>
<permission name="android.permission.LOADER_USAGE_STATS"/>
Add SYSTEM_CAMERA capability to camera2 and define @SystemApi SYSTEM_CAMERA permissions. In order to access system-only cameras client processes need SYSTEM_CAMERA permissions in addition to CAMERA permissions. A permission was preferred over other mechanisms such as having private connections would need to hard-code the package name(s) of clients using system only camera devices. A system | signature permission on the other hand, would make this more flexible and would be better for security. Bug: 133508924 Test: cts CameraManagerTest, CameraDeviceTest Test: Give cts test SYSTEM_CAMERA permissions by using adoptShellPermissions and run some camera tests. Change-Id: Ibcd6ccdb231dcca949ed4fb14712d033a5801d36 Signed-off-by: Jayant Chowdhary <jchowdhary@google.com>
2019-07-17 09:28:50 -07:00
<!-- Permission required to test system only camera devices. -->
<permission name="android.permission.SYSTEM_CAMERA" />
Add ExplicitHealthCheckServiceImplTest Test: atest android.ext.services.watchdog.ExplicitHealthCheckServiceImplTest Bug: 132640467 Change-Id: I2d1820a38adce238a157e925512898c184dadec0
2019-05-14 18:51:32 +01:00
<!-- Permission required to test ExplicitHealthCheckServiceImpl. -->
<permission name="android.permission.BIND_EXPLICIT_HEALTH_CHECK_SERVICE"/>
Car mode InCallService changes. 1. Grant ENTER_CAR_MODE and CONTROL_INCALL_EXPERIENCE permissions to the shell identity for use within CTS tests. 2. Remove un-needed Telecom shell command. Test: unit tests, telecom CTS tests, manual testing Bug: 144345414 Change-Id: I54a2e723d6ef9552117e6cadf4ab7c449dd5e3cb
2019-11-20 07:54:36 -08:00
<!-- Permission required for UiModeManager CTS test. -->
Add prioritized enableCarMode API in UiModeManager Per design doc (go/android-car-mode-design), added new system API to enable car mode and specify a priority for the calling app. Also modified UiModeManager to pass the package name of the caller to UiModeManagerService. Bug: 136109592 Test: Added new unit tests and CTS tests. Test: Added Telecom test app functionality to verify. Change-Id: I2848039c9ea18ba93e7694e04c4e5dc70759daa3
2019-09-30 15:12:24 -07:00
<permission name="android.permission.ENTER_CAR_MODE_PRIORITIZED"/>
Car mode InCallService changes. 1. Grant ENTER_CAR_MODE and CONTROL_INCALL_EXPERIENCE permissions to the shell identity for use within CTS tests. 2. Remove un-needed Telecom shell command. Test: unit tests, telecom CTS tests, manual testing Bug: 144345414 Change-Id: I54a2e723d6ef9552117e6cadf4ab7c449dd5e3cb
2019-11-20 07:54:36 -08:00
<!-- Permission required for Telecom car mode CTS tests. -->
<permission name="android.permission.CONTROL_INCALL_EXPERIENCE"/>
Add TETHER_PRIVILEGED permission to shell for CTS test. Grant TETHER_PRIVILEGED permissions to the shell identity for use within CTS tests. Bug: 145490751 Test: atest CtsTetheringTest Change-Id: Ifad265cdc5e0b1b1b2fa8f4f79eeb7dd18493624
2019-12-17 16:58:20 +08:00
<!-- Permission required for Tethering CTS tests. -->
<permission name="android.permission.TETHER_PRIVILEGED"/>
Add permissions for using PlatformCompat methods - READ_COMPAT_CHANGE_CONFIG is required to read the current state of the config - LOG_COMPAT_CHANGE is required to log the status of a compat change for a package and/or uid to statsd - OVERRIDE_COMPAT_CHANGE_CONFIG is required to add overrides The permissions must be signature|privileged, as there are already examples of code which this would not be sufficient (e.g. MediaProvider). This is a re-landing of https://r.android.com/1209240, which was reverted due to http://b/142942524. The actual fix was done in http://ag/10234812. Bug: 142650523 Test: atest PlatformCompatTest Test: atest PlatformCompatPermissionsTest Change-Id: Ie9429477c9a1725b5cb67756787bf742038e5d2b
2020-01-15 19:09:52 +00:00
<!-- Permissions required for ganting and logging -->
<permission name="android.permission.LOG_COMPAT_CHANGE" />
<permission name="android.permission.READ_COMPAT_CHANGE_CONFIG" />
<permission name="android.permission.OVERRIDE_COMPAT_CHANGE_CONFIG" />
Grant READ_DREAM_STATE & WRITE_DREAM_STATE permissions to shell This is required for ambient display tests. NOTE: This CL is manually cherry-picked from aosp/1215115 due to merge conflict. Bug: 147874708 Test: Run newly added ambient display tests. Change-Id: I61c28e15c4e5c3d0ffee4137ecb86e33f7e8f64d
2020-01-23 14:21:51 +00:00
<!-- Permissions required to test ambient display. -->
<permission name="android.permission.READ_DREAM_STATE" />
<permission name="android.permission.WRITE_DREAM_STATE" />
Give CONTROL_DEVICE_LIGHTS permission to the shell Bug: 144979010 Bug: 144978691 Test: atest LightsManagerTest Change-Id: I2b4224e79e013bae27ee068b0a0898b5afa5489a
2020-01-21 02:06:47 +01:00
<!-- Permission required to test lights control APIs. -->
<permission name="android.permission.CONTROL_DEVICE_LIGHTS" />
Restrict visibility of SHORTCUT_INVOCATION events. UsageStats will not return SHORTCUT_INVOCATION events to callers of #queryEvents and #queryEventsForUser if they don't have visibility, as defined by ShortcutService#hasShortcutHostPermission. Also, add ACCESS_SHORTCUT permission to shell for CTS test and add the ShortcutManagerUsageTest to postsubmit. Bug: 145549490 Test: atest android.app.usage.cts.UsageStatsTest Test: atest android.content.pm.cts.shortcutmanager.ShortcutManagerUsageTest Change-Id: I2a69f061c35c31035a5d0381ab2f42029ec4fffc
2020-01-07 16:33:22 -08:00
<!-- Permission required for ShortcutManagerUsageTest CTS test. -->
<permission name="android.permission.ACCESS_SHORTCUTS"/>
Grant shell REBOOT permission Shell already can reboot a device (via `adb reboot` command). This change allows shell to also trigger a reboot logic inside the system_server. Additionally, it allows to CTS test PowerManager.reboot API. Test: adb shell svc reboot Change-Id: I4545c4f3587fee2840a00648c569f75bb57501fc
2020-02-01 00:08:14 +00:00
<permission name="android.permission.REBOOT"/>
Access to Device Vibrator State Add API to access vibrator state and vibrator state listener. Bug: 135949568 Change-Id: I96636b432d581cea03a9fc9fecba4c08045f5006
2020-01-28 22:54:23 -08:00
<!-- Permission required for access VIBRATOR_STATE. -->
<permission name="android.permission.ACCESS_VIBRATOR_STATE"/>
Obfuscate visibility of notification-related events. UsageStats will return obfuscated NOTIFICATION_SEEN or NOTIFICATION_INTERRUPTION events to callers of #queryEvents and #queryEventsForUser if they don't hold the MANAGE_NOTIFICATIONS permission. Additionaly, refactor the query API in UsageStats to take in flags as defined in UsageEvents to make future obfuscation/visibility parameters cleaner. Also, add the MANAGE_NOTIFICATIONS permission to shell for CTS test. Bug: 144724524 Test: atest android.app.usage.cts.UsageStatsTest Test: atest com.android.server.people.data.UsageStatsQueryHelperTest Test: atest android.content.pm.cts.shortcutmanager.ShortcutManagerUsageTest Change-Id: I118de7e589ac8dd5924d3740c70903fa484b79b5
2020-02-04 14:01:12 -08:00
<!-- Permission required for UsageStatsTest CTS test. -->
<permission name="android.permission.MANAGE_NOTIFICATIONS"/>
Add COMPANION_APPROVE_WIFI_CONNECTIONS to shell permissions 1. This is a minimally scoped permission (which allows the new WiFi API's to silently connect to a wifi network). 2. I explored writing a GTS test instead of a CTS test, with the idea being that it would run inside the Android Auto user. Unfortunately the API under test requires two permissions, MANAGE_COMPANION_DEVICES and COMPANION_APPROVE_WIFI_CONNECTIONS. Android Auto will only have COMPANION_APPROVE_WIFI_CONNECTIONS, and if I elevate to Shell privileges the test will have MANAGE_COMPANION_DEVICES, but not COMPANION_APPROVE_WIFI_CONNECTIONS. Beyond this, I've been told that it's better for us to test this API in CTS than what it is under GTS. The addition of the permission to androis.os.shell could theoretically allow it to connect to a WiFi network using the new WiFi APIs without the user being prompted. Android R will still allow the legacy WiFi API's which also allow wifi connections without users being prompted without this permission. Android Auto requires the new API's as they better handle cases of connecting to WiFi networks with no internet access. The old API's will not always result in fallback to LTE, whereas the new ones do that. Test: Unit test in separate change. Change-Id: Ifd8ae6b7e53307ea8973406fdefa468dfa679bda Bug: b/147748710
2020-02-26 20:42:55 -08:00
<!-- Permission required for CompanionDeviceManager CTS test. -->
<permission name="android.permission.COMPANION_APPROVE_WIFI_CONNECTIONS" />
Make pull atom permission accessible to shell Make REGISTER_STATS_PULL_ATOM permission available to Shell to allow testing it in gts. Is the minimally scoped permission that needs to be added? Yes, it is the only permission to register pulled atoms. What options did you explore that did not need this permission? I explored expanding the permission to be development in addition to privileged, and giving the permission to gmscore. However, this solution was recommended to me by the GTS team. If there are better ways to enable testing the API in GTS, I am open to feedback. Test: atest GtsStatsdHostTestCases Bug: 150329323 Change-Id: I103d937842beaa2d918181b1a952d27179411dcc
2020-02-26 16:57:43 -08:00
<!-- Permission required for testing registering pull atom callbacks. -->
<permission name="android.permission.REGISTER_STATS_PULL_ATOM"/>
Add MODIFY_DEFAULT_AUDIO_EFFECTS permission to shell Add MODIFY_DEFAULT_AUDIO_EFFECTS permission to shell which is needed to run GTS tests on @systemApis for audio effects control. Bug: 148703417 Test: run gts -m GtsAudioTestCases -t com.google.android.audio.gts.DeviceEffectTest#testCreateDeviceEffect Change-Id: Iba579001aeffd85743850727135a6f536579ea17
2020-03-18 11:58:58 -07:00
<!-- Permission required for testing system audio effect APIs. -->
<permission name="android.permission.MODIFY_DEFAULT_AUDIO_EFFECTS"/>
Add tuner permissions to Shell So we can test system APIs in cts. Bug: 150952758 Test: atest android.media.tv.tuner.cts.TunerTest Change-Id: Ife5a5f712cdf3d3c2e5dd747fa1d3bc8c165b85b
2020-03-20 06:32:58 -07:00
<!-- Permissions required for CTS test - TunerTest -->
<permission name="android.permission.ACCESS_TV_DESCRAMBLER" />
<permission name="android.permission.ACCESS_TV_TUNER" />
<permission name="android.permission.TUNER_RESOURCE_ACCESS" />
Add support for TvInputManager.acquireTvInputHardware CTS 1. Add a test api in TvInputManager to add hardware device for testing 2. Add Shell permission for TV_INPUT_HARDWARE 3. Add TUNER_RESOURCE_ACCESS permission for TvInput Framework. Test: atest android.media.tv.cts Bug: 155114656 Change-Id: I227f13cbf14532d8732729412ae9c2518755ef02
2020-05-02 01:17:26 -07:00
<!-- Permissions required for CTS test - TVInputManagerTest -->
<permission name="android.permission.TV_INPUT_HARDWARE" />
Add LOCATION_HARDWARE permission to shell. A few location System APIs require LOCATION_HARDWARE permssion. Adding this permission to shell so CTS tests can adopt this permission. Bug:154347471 Test: atest PrivilegedLocationPermissionTest Change-Id: I4abe4dc044ec4a3ab62352cc0f4a1726bebac633
2020-05-21 20:50:47 -07:00
<!-- Permission required for CTS test - PrivilegedLocationPermissionTest -->
<permission name="android.permission.LOCATION_HARDWARE" />
Add CAPTURE_AUDIO_OUTPUT permission required for GTS test GtsDialerAudioTestCases require this privileged permission for testing in GTS. Bug: 157243201 Test: run gts -m GtsDialerAudioTestCases Change-Id: I32516e5dcf966b05cfb8ab4956a0cdb183298f2a
2020-06-02 21:24:59 -07:00
<!-- Permissions required for GTS test - GtsDialerAudioTestCases -->
<permission name="android.permission.CAPTURE_AUDIO_OUTPUT" />
Add shell permissions for CTS test (AdbManagerTest). Bug: 159936209 Test: atest CtsAdbManagerTests Change-Id: I896b53df582cceb7d1b0d6694d00064b0fb57b94
2020-04-27 13:34:27 -07:00
<!-- Permissions required for CTS test - AdbManagerTest -->
<permission name="android.permission.MANAGE_DEBUGGING" />
Add a new permission in AOSP This adds a new permission in AOSP, so it can be referenced by the Shell command, which presubmit suggests has to be maintained in AOSP. Bug: 159891384 Test: build only Exempt-From-Owner-Approval: jsharkey@ approved but it appears to have reset...? Change-Id: Ic7d403e20731e9d6bd82d5b2e2758cc61989cc59
2020-09-29 18:01:23 +01:00
<!-- Permissions required for CTS test - TimeManagerTest -->
<permission name="android.permission.MANAGE_TIME_AND_ZONE_DETECTION" />
Grant HDMI_CEC permission to Shell Needed for HDMI_CEC CTS tests to call HdmiControlManager. Bug: 169914520 Test: atest CtsHdmiCecHostTestCases with changes to tests Change-Id: Ia997f3910ab4ca3a149b2cbd3b1d3d7e9f7202f2 Merged-In: Ia997f3910ab4ca3a149b2cbd3b1d3d7e9f7202f2
2020-10-22 08:13:33 +02:00
<!-- Permissions required for CTS test - CtsHdmiCecHostTestCases -->
<permission name="android.permission.HDMI_CEC"/>
Add wifi coex permissions to Shell for CTS tests Bug: 153651001 Test: CTS tests pass Change-Id: I7c73bba692ade59731c1881b12f026e3a41891ca
2020-12-18 12:16:17 -08:00
<!-- Permission needed for CTS test - WifiManagerTest -->
<permission name="android.permission.WIFI_ACCESS_COEX_UNSAFE_CHANNELS" />
<permission name="android.permission.WIFI_UPDATE_COEX_UNSAFE_CHANNELS" />
add shell user permissions for Asistant GTS tests Bug: 177271291 Test: gts-tradefed run gts -m GtsAssistIntentTestCases Change-Id: I6c6134a9912a73039556a4d700bbb0bb97b6b3d4 Merged-In: I293d66811f8a27170f2bc4cb74b7d4c9ec55fac8
2021-01-12 10:18:33 -08:00
<!-- Permission required for GTS test - GtsAssistIntentTestCases -->
<permission name="android.permission.MANAGE_SOUND_TRIGGER" />
<permission name="android.permission.CAPTURE_AUDIO_HOTWORD" />
Grant shell QUERY_USERS and MODIFY_QUIET_MODE Added a new permission QUERY_USERS, granted the new permission and MODIFY_USERS to shell. These permissions are required to enable CTS tests to access the following APIs: * UserManager#getUsers and any other API that depend on it * UserManager#getProfileParent * UserManager#requestQuietModeEnabled Test: Confirmed that a CTS test can call these APIs Bug: 178695365 Merged-In: Ifa14d24ee1873161e3986e8d0669fd47a7bcaa7a Change-Id: Ifa14d24ee1873161e3986e8d0669fd47a7bcaa7a
2021-01-28 15:07:18 +00:00
<permission name="android.permission.MODIFY_QUIET_MODE" />
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
</privapp-permissions>
<privapp-permissions package="com.android.statementservice">
<permission name="android.permission.INTENT_FILTER_VERIFICATION_AGENT"/>
</privapp-permissions>
Allow privapp Traceur access to STATUS_BAR and DUMP Modifies the privapp allowlist to allow Traceur to grant Traceur the STATUS_BAR permission, which is needed for quick settings tile functionality, and dump which is needed for the BUGREPORT_STARTED intent. Bug: 166768816 Test: Built user and userdebug, exercised regular and long trace functionality Change-Id: I180527a9a1a30ef6a214b628f37affc69f9ae2f0
2020-08-28 16:25:57 -07:00
<privapp-permissions package="com.android.traceur">
<!-- Permissions required to receive BUGREPORT_STARTED intent -->
<permission name="android.permission.DUMP"/>
Allow Traceur to take START_FOREGROUND_SERVICES_FROM_BACKGROUND As part of targetting the Android S API level, we need to explicitly allow the privapp Traceur to start services from the background. Test: atest TraceurUiTest Bug: 176849372 Change-Id: I58c2a23653541f8516beedf0971d60403eedbb02
2021-01-06 11:41:12 -08:00
<!-- Permissions required to start/stop tracing -->
<permission name="android.permission.START_FOREGROUND_SERVICES_FROM_BACKGROUND"/>
Allow privapp Traceur access to STATUS_BAR and DUMP Modifies the privapp allowlist to allow Traceur to grant Traceur the STATUS_BAR permission, which is needed for quick settings tile functionality, and dump which is needed for the BUGREPORT_STARTED intent. Bug: 166768816 Test: Built user and userdebug, exercised regular and long trace functionality Change-Id: I180527a9a1a30ef6a214b628f37affc69f9ae2f0
2020-08-28 16:25:57 -07:00
<!-- Permissions required for quick settings tile -->
<permission name="android.permission.STATUS_BAR"/>
Introduce TracingServiceProxy System Services Introduces a new SystemService to act as intermediary between the Perfetto trace daemon and Traceur. Bug: 175591887 Test: adb shell service call 1 i32 0/1 Change-Id: Idea7761a8479827f0cfa561e56ba2beac3072939
2020-12-10 16:02:07 -08:00
<!-- Permissions required to query Betterbug -->
<permission name="android.permission.QUERY_ALL_PACKAGES"/>
Allow privapp Traceur access to STATUS_BAR and DUMP Modifies the privapp allowlist to allow Traceur to grant Traceur the STATUS_BAR permission, which is needed for quick settings tile functionality, and dump which is needed for the BUGREPORT_STARTED intent. Bug: 166768816 Test: Built user and userdebug, exercised regular and long trace functionality Change-Id: I180527a9a1a30ef6a214b628f37affc69f9ae2f0
2020-08-28 16:25:57 -07:00
</privapp-permissions>
Declare privileged permissions of Live TV app Test: build Bug: 35782070 Change-Id: Ia1e39dcf8fdd3345837ebec1729ad4d02699763b
2017-03-20 15:19:11 -07:00
<privapp-permissions package="com.android.tv">
Add permissions for LiveTv (AOSP) It crashes without the permissions Bug: 67474061 Test: make; flashall; install and open LiveTv; Change-Id: Ifec8bfb4ee93ac6b9189a9c337fdd2ef9ec34537
2017-10-05 18:31:00 -07:00
<permission name="android.permission.CHANGE_HDMI_CEC_ACTIVE_SOURCE"/>
<permission name="android.permission.DVB_DEVICE"/>
<permission name="android.permission.GLOBAL_SEARCH"/>
<permission name="android.permission.HDMI_CEC"/>
<permission name="android.permission.MODIFY_PARENTAL_CONTROLS"/>
<permission name="android.permission.READ_CONTENT_RATING_SYSTEMS"/>
<permission name="com.android.providers.tv.permission.ACCESS_ALL_EPG_DATA"/>
<permission name="com.android.providers.tv.permission.ACCESS_WATCHED_PROGRAMS"/>
Declare privileged permissions of Live TV app Test: build Bug: 35782070 Change-Id: Ia1e39dcf8fdd3345837ebec1729ad4d02699763b
2017-03-20 15:19:11 -07:00
</privapp-permissions>
Control privileged permissions for priv-apps Added support for privapp-permissions config element. It allows to explicitly control what privileged permissions applications should be granted. Feature is controlled by ro.control_privapp_permissions property. Possible values: - 0/false, the feature is completely disabled - signature|privileged permissions are granted automatically without logging. *Default behavior* - 1/true, enforce that only whitelisted permissions are granted. Only devices with ro.control_privapp_permission=1 will pass CTS tests. Test: Manual Bug:31008485 Change-Id: I93a8c2782cc72b3953f32c237086d08d82ac0d5b
2016-11-09 14:32:27 -08:00
<privapp-permissions package="com.android.vpndialogs">
<permission name="android.permission.CONTROL_VPN"/>
</privapp-permissions>
API review followup: DynamicAndroidClient Some API changes per API reivew: - Move DynamicAndroidClient and ~Manager to android.os.image. - Rename them to DynamicSystemClient and ~Manager. - Rename permission MANAGE_DYNAMIC_ANDROID to MANAGE_DYNAMIC_SYSTEM - Corresponding changes in the installation service. - Corresponding changes in privapp-permissions-platform.xml. - Add missing annotations. - Change setOnStatusChangedListener's parameters order. - Improve documentations. - Re-generate api/system-current.txt. Bug: 126613281 Test: adb shell am Change-Id: Ia920e9ccf6de1dbbd38c52910cb72cb81b9b5b32
2019-03-07 11:57:17 +08:00
<privapp-permissions package="com.android.dynsystem">
Add DynamicAndroidInstallationService DynamicAndroidInstallationService is a framework service to download, unzip and write DynamicAndroid images. Apps should interact with it using DynamicAndroidClient. Or, developers can use adb am commmands. Test: build and run on internal target Bug: 122015653 Change-Id: I7c834ed37de52840a407fb140743eda1f2bd82e8
2019-01-12 00:40:02 +08:00
<permission name="android.permission.REBOOT"/>
API review followup: DynamicAndroidClient Some API changes per API reivew: - Move DynamicAndroidClient and ~Manager to android.os.image. - Rename them to DynamicSystemClient and ~Manager. - Rename permission MANAGE_DYNAMIC_ANDROID to MANAGE_DYNAMIC_SYSTEM - Corresponding changes in the installation service. - Corresponding changes in privapp-permissions-platform.xml. - Add missing annotations. - Change setOnStatusChangedListener's parameters order. - Improve documentations. - Re-generate api/system-current.txt. Bug: 126613281 Test: adb shell am Change-Id: Ia920e9ccf6de1dbbd38c52910cb72cb81b9b5b32
2019-03-07 11:57:17 +08:00
<permission name="android.permission.MANAGE_DYNAMIC_SYSTEM"/>
Key revocation check is permissive when device is unlocked imageValidationThrowOrWarning() logs the error as a warning if device bootloader is unlocked, else re-throw the error. Device lock state is queried via PersistentDataBlockManager service. Bug: 128892201 Test: adb shell am start-activity \ -n com.android.dynsystem/com.android.dynsystem.VerificationActivity \ -a android.os.image.action.START_INSTALL \ --el KEY_USERDATA_SIZE 8192 \ -d file:///storage/emulated/0/Download/aosp_arm64-dsu_test.zip \ --es ${IMAGE_KEY} Test: Observe the logcat Change-Id: I895e70d90624afda2bf7cd3b34ea8d21a1702163
2020-02-19 16:40:46 +08:00
<permission name="android.permission.READ_OEM_UNLOCK_STATE"/>
Add DynamicAndroidInstallationService DynamicAndroidInstallationService is a framework service to download, unzip and write DynamicAndroid images. Apps should interact with it using DynamicAndroidClient. Or, developers can use adb am commmands. Test: build and run on internal target Bug: 122015653 Change-Id: I7c834ed37de52840a407fb140743eda1f2bd82e8
2019-01-12 00:40:02 +08:00
</privapp-permissions>
Allow the DSU Loader to install DSU package The DSU Loader is an Activity for developers to select a DSU package and install. Bug: 140090894 Test: click settings->developer option->debug::DSU Loader Change-Id: If661ee3865ecc6234c19a7cf7376df1677313f60
2019-12-02 19:12:17 +08:00
<privapp-permissions package="com.android.settings">
<permission name="android.permission.INSTALL_DYNAMIC_SYSTEM"/>
Refactored cell broadcast area info support Area info cell broadcast messages are not handled by cell broadcast receiver anymore. Instead, they will be processed in cell broadcast service. Privileged apps that are interested in getting the information will need to get it directly from cell broadcast service. Note this is only enabled for certain countries and carriers. Test: Manual Bug: 141318859 Bug: 141425194 Change-Id: I2245c39f679d0ad94c9a1325edc553f362fdce7c
2020-01-30 00:30:29 -08:00
<permission name="android.permission.BIND_CELL_BROADCAST_SERVICE"/>
Allow the DSU Loader to install DSU package The DSU Loader is an Activity for developers to select a DSU package and install. Bug: 140090894 Test: click settings->developer option->debug::DSU Loader Change-Id: If661ee3865ecc6234c19a7cf7376df1677313f60
2019-12-02 19:12:17 +08:00
</privapp-permissions>
Nicer share target for default print service This was suggested by the share sheet team and I checked that this permission only narrowly adds the ability to present a nicer share target. The default print service cannot be renamed "print" as the name of the app shows up on other print UI. Bug: 150646365 Test: Checked permission after boot Change-Id: I3aa5900605bda90ce0cb58a09fe08128bf4c9531
2020-03-03 16:02:32 -08:00
<privapp-permissions package="com.android.bips">
<permission name="android.permission.SUBSTITUTE_SHARE_TARGET_APP_NAME_AND_ICON"/>
</privapp-permissions>
Add BIND_IMS_SERVICE to permissions whitelist Adds android.permission.BIND_IMS_SERVICE to the permissions whitelist xml file. Bug: 34813244 Test: Manual Change-Id: I7a7ad1a361c9d2dcc51769bc74a436878ad4adc5
2017-02-03 10:42:25 -08:00
</permissions>
Reference in New Issue Copy Permalink