DEVICE_POWER is very powerful, so introduce the BATTERY_PREDICTION
permission to allow privileged apps with the permission to provide the
system with battery predictions.
Bug: 139413884
Test: atest android.os.cts.PowerManagerTest
Test: atest android.permission.cts.PowerManagerServicePermissionTest
Test: atest CtsPermission2TestCases
Test: atest SettingsProviderTest
Change-Id: Ib52f20b5145785a5fc363601757ad9c57f40e254
Provides new APIs so that shortcuts can preset the theme of the splash
screen window.
- Static way: android:splashScreenTheme
Preset the splash screen theme from xml.
- Dynamic way: ShortcutInfo.Builder#setStartingTheme
Preset the splash screen theme when construct the ShortcutInfo
programmatically.
Bug: 73289295
Test: build/flash
Test: atest AppWindowTokenTests ActivityRecordTests
Change-Id: Ie5e73f9b22fea22659e496c12198c942f4bc93cd
Adds a new permission (privileged or signature) which will
allow the holder to register callbacks with the
RebootReadinessManager. Also grants this permission to the
shell for testing purposes.
Test: atest CtsRebootReadinessTestCases
Bug: 161353402
Change-Id: Ide2ec7a0c2b905b4986031f2b6448182b45bb07a
The refactoring in S unintendedly introduced a change that allowed
signature|privileged to be granted to platform-signed privileged apps
without being in the allowlist XML, so we should revert to the old
behavior.
The refactoring was done in the hope that we can have one step that
handles privileged permission granting. However upon retrospection, we
have to do this in two separate steps because the privapp permission
allowlist should always be enforced first.
This change reverts to the old behavior by looking at both the current
code and the R source code, then extracts the privapp permission
enforcement as a separate step that happens first, to be used by both
signature and the new internal permission protection.
Also simplified the check about privileged permission, because vendor
privileged permission is always a privileged permission, as made sure
in PermissionInfo.fixProtectionLevel().
In the mean time, added the missing privapp permission allowlist entry
for Settings and RESTART_WIFI_SUBSYSTEM for device to boot.
Fixes: 179309876
Test: manual
Change-Id: I93cfe7a4621fc5ac65229d42c7a8ebd825ae8ae5
When in button navigation mode with autoEnterPip enabled, we still need
to resume the top focuses activities when tapping on home.
Video: http://rcll/aaaaaabFQoRHlzixHdtY/fys1jBNOQATN62K4DltfHU
Bug: 179498534
Test: enter PiP in button navigation mode with autoEnterPip on,
see also the video
Change-Id: I896c2bfeb819969475ba549ffbd64344bc017bc2
(Permission will be migrated to a role in a follow-up).
Bug: 178644109
Test: atest CtsPermission2TestCases:android.permission2.cts.PrivappPermissionsTest#privappPermissionsNeedToBeWhitelisted -- --abi arm64-v8a
Change-Id: I491450d8748ac669a017547ffb8616e2544aa397
(cherry picked from commit 6fa6344e00)
- gcar_emu_x86_64 starts to crash after commit 1dafc38 is merged.
Bug: 179455284
Test: Build gcar_emu_x86_64 and check if it boots successfully.
Change-Id: I59dad57c846e3a83d71abb58fdd5e57019d99e75
Origional changes were in aosp/1546877. It has a merged-in referencing
ag/13319676, but ag/13319676 doesn't contain these changes. This CL is
to add the missing changes.
Bug: 177271291
Test: gts-tradefed run gts -m GtsAssistIntentTestCases
Change-Id: I22a3e6a3475263ec4e007e37412a269ca95c8bbe
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
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
Change-Id: Ifa14d24ee1873161e3986e8d0669fd47a7bcaa7a
Sandbox Display#getRealSize and WindowManager
bounds when letterbox or size compat mode are
applied to the configuration. Display uses
this field to provide the sandboxed display
size.
Test: atest WindowConfigurationTests
Test: atest FrameworksMockingCoreTests:android.view.DisplayTests
Test: atest WmTests:SizeCompatTests
Bug: 171386167
Change-Id: I6f78edcd9214b52ab0708e3892bc86ee05bb5b9a
Apps can't request this permission anyways so some apps started
misbehaving when forcing users to grant all permissions without caring
what they are.
Test: Boot
Fixes: 172844303
Bug: 158311343
Change-Id: Ia83ad5433ff3cdae57d901b3a9d781725124c6b9
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
