Bug: 309545085
Flag: ACONFIG com.android.window.flags.predictive_back_system_animations DISABLED
Test: atest BackAnimationPreferenceControllerTest; Manual, i.e. building and verifying correct behaviour for different flag configurations
Change-Id: I3f478dc23bbfeb1f13cae64f3d04b3210841731d
Bug: 313775893
Test: Trigger the intent with action "android.settings.REQUEST_MEDIA_ROUTING_CONTROL" and package name in the data uri
Change-Id: If65ea61a058b465dc44836eff9c7d3fb25425ec4
Test: Verified test crashed without fix, and passed with fix
Test: atest FingerprintSettingsFragmentTest
Fixes: 315164185
Change-Id: I1d8ab32eef8578a6d35831aef46275a9732e497c
This commit continues the work to make all special app access
permissions ECM restrictable. Some implementation notes:
1. The FilterTouchesSwitchPreference and AppSwitchPrefernce components
are replaced with RestrictedSwitchPreference. afaict this is a
superset - it still filters out obscured touches and shows the app
icon.
2. I'm treating this as mostly a refactoring, and so do not have a
feature flag around most of the changes. Enabling ECM for them /is/
behind the feature flag in RestrictedLockUtilsInternal.
3. app_ops_permissions_details.xml is currently only used by
UsageAccessDetails.
Bug: 297372999
Test: Manually tested on device. Automated tests to follow
Change-Id: I65fe7ec099582de19192a77ad2e41c1558761502
1. Update Notification Listener and A11y settings to call
RestrictedLockUtilsInternal rather than checking appOp themselves
2. Rename ecm related methods to include Ecm rather than AppOp -
implementation details are being moved to permissions module and may
change.
Bug: 297372999
Test: Manually tested on device. Automaated tests to follow
Change-Id: Ie3e16b502993b21a7e34eab0d661f98814b3cfd5
This is the first in a series of changes to wire up all app settings to
be ECM restrictable. We introduce a new method in
RestrictedLockUtilsInternal which determines whether or not a setting is
restricted based on a passed in key. It currently duplicates the current
implementation, but will eventually be replaced by a call to permissions
mainline.
The settings under SpaPrivileged are then updated to have a new
BlockedByEcm which is decided by the RestrictedLockUtilsInternal call.
Bug: 297372999
Test: Manually tested on device. Automaated tests to follow
Change-Id: Ic295bdb41270b0f18f2ba3dffdffc062d532cabe
This includes below changes based on the updated UX mocks:
- Add one more loading screen in setup flow
- Update feature intro text on Setup page
- To swap order of bullets on the setup intro screen
- Update "Private Space" to "private space" in setup flow screens
go/ss/7pVGBSPqezDek47.png
go/ss/ADLX8aXAAGgYQHD.png
go/ss/tYtrGypBgRuXM9V.png
go/ss/3zZfij6JDpudwYR.png
go/ss/BFtWegFZyTueQoT.png
Recording link - b/313654776#comment5
Bug: 313654776, 313882412, 313655290
Test: Verify title and text is same as UX flow
Change-Id: I6a985c4fd6ecbe8ddd11e36bf76a2a9cc8427ef5
Bug: b/307632045
Test: Pair a watch with companion app > Settings > Apps > Special app access > enter "Change Media Output" > Find the companion app > Ensure the special app access is Allowed > ensure companion app is able to call remote media routing APIs > come back to the settings > revoke the access > ensure that now companion app is NOT able to call the remote media routing APIs.
Change-Id: I35487660365ef05f3b998e8ecf13aaed7ba844a9
