Adds DEVICE_LOCK permission to Shell to support the
CarDevicePolicyManagerTest. This permission is needed to call
DevicePolicyManager#lockNow which locks the device.
Bug: 187199256
Test: atest CarDevicePolicyManagerTest
Merged-In: I3fa20b53b929c97a6760d65b432a74c3415d6a08
Change-Id: I3fa20b53b929c97a6760d65b432a74c3415d6a08
So we can test system APIs in cts.
Bug: 201017875
Test: atest android.settings.cts.SettingsMultiPaneDeepLinkTest
Change-Id: I8bedd571a4d3385042533fe7dd5ded250894d14a
Merged-In: I8bedd571a4d3385042533fe7dd5ded250894d14a
The new name better aligns with the component and permission names.
Follow up review comments on https://r.android.com/1784487
Bug: 183487233
Test: presubmit
Change-Id: Ibe3a3e51b0dc154ee3e43b27e561fd541b62cc54
For the service to be able to check permission, the AIDL interface is
exported to the virt APEX where virtualizationservice is in.
In addition, the VM permissions are granted to shell so that developers
can use the 'vm' tool on the shell.
Bug: 168588769
Test: /apex/com.android.virt/bin/vm run-app --log /dev/null
/data/local/tmp/virt/MicrodroidDemoApp.apk
/data/local/tmp/virt/MicrodroidDemoApp.apk.idsig assets/vm_config.json
Change-Id: I00db58ba9cef3b83f43db68ef86f062b59a0e6e1
Shell doesn't need this permission and it confusing to the user
if visible in Settings.
Test: Shell doesn't appear in Settings under
Settings -> Apps -> Special app access -> Alarms & Reminders ->
3 dot menu -> Show system
Bug: 190775895
Change-Id: I98b051f37f3edf4f616f8847f691b956dafbdd12
Merged-In: I98b051f37f3edf4f616f8847f691b956dafbdd12
This is required for GTS testing it, rather than having to instrument
GMS Core.
Bug: 182271592
Test: tested as part of other CLs in this topic
Change-Id: Id56e0d206afe0a9069d1510a3dae9a07141fff60
Both of NetworkPolicyManager#isUidNetworkingBlocked() and
NetworkPolicyManager#isUidRestrictedOnMeteredNetworks() are
required OBSERVE_NETWORK_POLICY but OBSERVE_NETWORK_POLICY is a
signature permission that CTS cannot acquire.
So add this permission for shell and call these 2 APIs with
shell identity to fix the problem.
Bug: 176289731
Test: atest CtsHostsideNetworkTests:HostsideNetworkPolicyManagerTests
Original-Change: https://android-review.googlesource.com/1737413
Merged-In: Iba7321c82e1a3ed773f99ccd4b9e3c24c607353f
Change-Id: Iba7321c82e1a3ed773f99ccd4b9e3c24c607353f
Both of NetworkPolicyManager#isUidNetworkingBlocked() and
NetworkPolicyManager#isUidRestrictedOnMeteredNetworks() are
required OBSERVE_NETWORK_POLICY but OBSERVE_NETWORK_POLICY is a
signature permission that CTS cannot acquire.
So add this permission for shell and call these 2 APIs with
shell identity to fix the problem.
Bug: 176289731
Test: atest CtsHostsideNetworkTests:HostsideNetworkPolicyManagerTests
Change-Id: Iba7321c82e1a3ed773f99ccd4b9e3c24c607353f
Shell doesn't need this permission and it confusing to the user
if visible in Settings.
Test: Shell doesn't appear in Settings under
Settings -> Apps -> Special app access -> Alarms & Reminders ->
3 dot menu -> Show system
Bug: 190775895
Change-Id: I98b051f37f3edf4f616f8847f691b956dafbdd12
Grant shell android.permission.GET_TOP_ACTIVITY_INFO for testing Launcher
tests that need access to AssistContentRequester in shell context.
Bug: 190344718
Test: Local build and flash, ran test
Merged-In: I551e0bee413432653f39c91664d716f695311b6f
Change-Id: I551e0bee413432653f39c91664d716f695311b6f
Grant shell android.permission.GET_TOP_ACTIVITY_INFO for testing Launcher
tests that need access to AssistContentRequester in shell context.
Bug: 190344718
Test: Local build and flash, ran test
Merged-In: I551e0bee413432653f39c91664d716f695311b6f
Change-Id: I551e0bee413432653f39c91664d716f695311b6f
Stop exporting HeapDumpProvider so apps can only access generated dumps
when the user explicitly shares them.
Bug: 184046948
Test: capture system heap dump in developer options and confirm test app
get SecurityException if it tries to access the dump directly, but gets
access when the dump is shared through the notification flow
Change-Id: Ibdca7cde4f563baa39163869289da5b79fc3a6db
