Should avoid spying on Android classes due to potential test pollution: https://robolectric.org/best-practices/
Bug: 315399487
Test: atest SettingsRoboTests:com.android.settings.homepage.contextualcards.slices --iterations 20
Change-Id: Ia52baf52bf43d3a3959dc0234fbfc5b4a4575dac
Network & internet is shown at the very beginning when activity
embedding is enabled.
Fix: 311604902
Test: manual - with TestDPC
Change-Id: Ic27455e34a9ba4b48b8e72fd30d5b8d9e4be7194
- Fetch foreground service info through new api from UidBatteryConsumer.
- Record fgs & bg usage time separately, combine them till ui display.
Bug: 315255868
Test: make RunSettingsRoboTests ROBOTEST_FILTER="com.android.settings.fuelgauge.*"
Change-Id: Ic19844db7908a6ae6522c7a72972f44f94dcfca4
What the clients send over is the tab based on user, but the correct tab
(position) wise needs to figured out.
Bug: 314371622
Test: manual
Change-Id: Ib6ebefb898b1c5678c14157333dc2b2ebc198ed8
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
