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
Pre-grant START_ACTIVITIES_FROM_BACKGROUND to emergency app
The emergency app needs this permission to start foreground service
after sdk 31.
Fix: 172364084
Test: manual
Change-Id: I111dbda3418edf4fcf34aa26f39dc6ce662f2e5d
(cherry picked from commit fb001c98ee)
Update local variables and comments with Task terms.
No logical changes.
Bug: 157876447
Test: presubmit
Change-Id: Iffcd5ca8971fc8856775538c3eebcefef2cf4b24
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
The UserSystemPackageInstaller installs packages on new users
based on their configuration in an allowlist. An exception was
made for auto-generated RROs, which were instead installed based
on their overlay target package's configuration (thus avoiding
the need for manually allowlisting each such overlay).
This is now expanded to all static overlays (which should
include auto-generated RROs, according to the bug). That is:
Static overlays no longer need to be mentioned in the list,
but will instead be installed based on the listing for their
overlay target package.
Test: atest UserSystemPackageInstallerTest
Fixes: 172956245
Change-Id: I6b974bba20ee059a8f744092db7c3441580d327f
- It now overrides shell package itself
Bug: 177099512
Test: Check if shell package has all necessary permissions
Change-Id: I139b47fcb2992e42da020aaac8680ae8dd2efac0
Merged-In: I139b47fcb2992e42da020aaac8680ae8dd2efac0
(cherry picked from commit 2bd010b7e5)
... until it adds the first view
In R, we create WindowToken for every WindowContext creation.
In S, we only create WindowToken for the WindowContext which adding
a view.
This CL also provide the ability to attach an existing WindowToken
by overriding WindowManager.LayoutParams.mToken, and remove the
WindowContext created WindowToken after WindowContext destruction.
Bug: 159767464
Bug: 153369119
Test: atest WindowTokenTests WindowContextListenerControllerTests
Change-Id: Iefe0315461b452a84cecbff2d08ee04c1f34051d
Original CL got reverted because target aosp_arm64-userdebug was failing
to boot. Apparently, the right place to put the permission for launcher3
is in frameworks/base/data/etc/com.android.launcher3.xml, not
frameworks/base/data/etc/privapp-permissions-platform.xml (despite it
having an entry on the latter) because launcher3 lives in system_ext.
-- Original CL description
CellBroadcastReceiver, a mainline module signed with the networkstack,
needs it before showing emergency alerts to the user.
This is inline and ok with the rest of of the restrictions given that
STATUS_BAR that allows calls to StatusBarManager.collapsePanels() also
has "privileged" protection level.
Also adding permission to privapp-permissions-platform for Launcher3
because of b/177506944, despite it getting it via "recents" protection
level.
Bug: 177346942
Bug: 159105552
Test: atest PermissionPolicyTest
Test: Run DeviceBootTest for aosp_arm64-userdebug in forrest.
Change-Id: Ie3298c839003aeaca3cc84782e8846374beca5b8
Add new column definitions in the call log db to support storing the new
call composer elements in the call log. Also refactor addCall to use a
builder pattern, and add READ_VOICEMAIL for shell in order to support
new CTS tests
Test: atest CallLogTest
Bug: 174798736
Change-Id: I00e127510c382d9ff0ffc70f4c5ad7179ac7319a
After this change, the power button on the reference remote will function
as a power toggle for the HDMI-connected display (=TV) power state. The
device will then follow the TV power state.
Bug: 157402294
Test: N/A
Change-Id: I462f792f5aae8c47c876d3ea3dfea64fc1c551b5
CellBroadcastReceiver, a mainline module signed with the networkstack,
needs it before showing emergency alerts to the user.
This is inline and ok with the rest of of the restrictions given that
STATUS_BAR that allows calls to StatusBarManager.collapsePanels() also
has "privileged" protection level.
Also adding permission to privapp-permissions-platform for Launcher3
because of b/177506944, despite it getting it via "recents" protection
level.
Bug: 177346942
Bug: 159105552
Test: atest PermissionPolicyTest
Change-Id: If027c6824a58c8b9a917f9995e34bf8b306cab54
- It now overrides shell package itself
Bug: 177099512
Test: Check if shell package has all necessary permissions
Change-Id: I139b47fcb2992e42da020aaac8680ae8dd2efac0
