Remove database version 1~11 support since the format hasn't changed
in the past 7 years.
Bug: 135956699
Test: Manual
Change-Id: I367124471f16073bb47a31c094d161d36969acc1
In order to support system use-cases, such as when the user wants do
revoke SYSTEM_ALERT_WINDOW (SAW) permission via notification, we are
introducing a new intent, MANAGE_APP_OVERLAY_PERMISSION (notice the
"APP_"), that directs the user to the app-specific screen to toggle SAW
permission.
The intent can only be started if the caller has INTERNAL_SYSTEM_WINDOW
permission, which sysui and the system have. This is verified in CTS.
In this change we also update usage in NotificationGutsManager and
AlertWindowNotification.
Test: Builds
Test: atest TestManageOverlayPermissionIntents
(cts in one of the topic CLs)
Test: Let an app draw on top of other apps, via its notification go to
settings, verify that the screen for controlling such capability
for the app is dispayed.
Bug: 145198756
Bug: 135920175
Change-Id: Iba29e1eaee729268a4dec9561946f6ed74b36619
Move the Copy button to a new row of chips below the
(now larger) preview. Optionally, if a proximity-sharing
service is installed, show that chip as well.
Bug: 143229724
Fixes: 144290152
Test: atest SystemUITests frameworks/base/core/tests/coretests
Change-Id: I0d6457df85bc937f72ca97da6b4b84b634a90daf
It is no longer used anywhere in the framework. (It is sometimes used
by GPP, but that's fine; they don't use this constant.)
Bug: 135751498
Test: Still builds
Test: atest SettingsProviderTest
Change-Id: I52244fa096e70349165d435493cc758acc52ad68
It isn't used anywhere in the framework, except by incidentd - that
usage is also removed.
Any such setting is private to the verifier and not the business of
the framework.
Test: atest SettingsProviderTest
Test: Still builds
Bug: 135751498
Change-Id: Ia6424d8ce811560e4ba72ada003dc08475d5123e
This method accepts multiple flags and overrides the values of all flags
in the provided namespace atomically. If any listeners are registered
for that namespace it will also trigger a callback with all of the flags
that were changed (added, updated, or removed).
Test: atest FrameworksCoreTests:DeviceConfigTest
atest FrameworksCoreTests:SettingsProviderTest
atest SettingsProviderTest:DeviceConfigServiceTest
Bug: 136135417
Change-Id: I2e496a3807493750ba8891dd6390055c919b5f45
The keys are split according to whether they affect the system as a whole,
or simply the inner workings of the window manager.
Also encapsulates WindowManagerConstants properly and adds testing.
Bug: 139735771
Test: atest WindowManagerConstantsTest
Change-Id: I67c96a2bdd3140fe2ff9c6832d2d69f2e57115e2
Required to test ANR
Fixes: 144724475
Test: run cts -m CtsWindowManagerDeviceTestCases -t android.server.wm.AnrTests
Change-Id: I02ef51790a630c9cead7e66eca58d107d77e95db
This setting should be private to GPP, and there should be no reason
for any app to access it. And GPP is migrating away from this
relatively public setting, so it can't be relied upon.
Test: Builds
Bug: 135751498
Bug: 37119785
Change-Id: I839c2d67ae54b4df184ea7ee1c7aebee72c6e794
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.
This initial pass introduces the APIs needed to support a "legacy"
MediaProvider that will be used to migrate data between the old and
new UID. This legacy provider is implemented using the same code
as the modern provider, but hosted at the "media_legacy" authority.
Bug: 144247087
Test: atest --test-mapping packages/providers/MediaProvider
Change-Id: Ibc38a786799e138e9c3e31297c7066bab6843d89
