Originally we cache mFollowingTypingSwitchPreference in fragment so in
ToggleScreenMagnificationPreferenceFragmentForSetupWizard we can set the
preference visible to false to hide it. After creating MagnificationFeaturePreferenceController,
the MagnificationFollowTypingPreferenceController can extend it and
check isInSetupWizard internally then dicide whether to hide. Therefore,
we don't need to cache mFollowingTypingSwitchPreference in fragment
and let the fragment control the preference visibility anymore.
Bug: 340721852
Flag: NONE
Test: manually
atest MagnificationFollowTypingPreferenceControllerTest
atest ToggleScreenMagnificationPreferenceFragmentForSetupWizardTest
atest ToggleScreenMagnificationPreferenceFragmentTest
Change-Id: I44f7f0589b2df3d83a27139323fc68a0561f1cfa
Add a new abstract class MagnificationFeaturePreferenceController
that extends TogglePreferenceController, to wrap inSetupWizard
setter/getter. Then for magnification feature preference controllers
like alwaysOn or followTyping, they can just check isInSetupWizard to
decide whether hiding in setup wizard.
Besides, in ToggleScreenMagnificationPreferenceFragment we cache a flag
mInSetupWizard when fragment created, so we can pass the info to the
preferece controllers when creating them.
Bug: 340721852
Flag: NONE
Test: build pass
Change-Id: I05c59a766219862117d2a6ede775d68a4c3dedac
Adding minor touch ups, such as starting the
FingerprintEnrollConfirmation when enrollment has been completed.
Bug: 297082837
Test: atest
Change-Id: I7b3edebb141bdb3e4648f71527d45dc5a0185b60
The resulting search result takes the user to the modes aggregator page.
Flag: android.app.modes_ui
Bug: 332937523
Test: ZenModesListPreferenceControllerTest, manual with modes_ui on and off
Change-Id: I7372307cb995667f6f7234530a3140f5295ab06a
In PackageMonitor, it is no longer based on broadcast receivers to
listen package added/removed/... events. Therefore the verification
should be removed.
Bug: 340387113
Test: atest SettingsRoboTests:com.android.settings.accessibility.AccessibilitySettingsTest
Change-Id: I7b0d46add06c74f1b9bf1097f92dececa9b130de
This reverts commit 7f2fbc2e4c.
Reason for revert: voice activation is not going in V
Test: manual - on Special app access
Change-Id: Idfabfd48f45d2ace7de9f8498181f281ad0358a1
Merged-In: Idfabfd48f45d2ace7de9f8498181f281ad0358a1
To match the sorting order in
SubscriptionManagerService.getAvailableSubscriptionInfoList.
Fix: 340361264
Test: manual - on SIMs
Test: unit test
Change-Id: I06b6c61304f9e6c9515b5f989294417ac3f82a60
As strict mode is in place, the default strict_mode is now set to true. We are encourage teams to write tests in strict_mode to make tests Bivalent (able to run on device and devicelessly)
For more info on strict mode: go/roboStrictMode
Test: atest SettingsRoboTests
Bug: 334089788
Change-Id: I4381446dac381a34747043c564cf5288a2e16725
Save the preference for connected apps for backup and restore
Flag: android.app.admin.backup_connected_apps_settings
Bug: 175067666
Test: manual
Change-Id: Ic46fbd1ab82f551ecf89caf800e41d6afe48fc68
Revert submission 27392016-cherrypick-AppOpsController-AppOps-w48m53c1or
Reason for revert: <Potential culprit for b/341210811- verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.>
Reverted changes: /q/submissionid:27392016-cherrypick-AppOpsController-AppOps-w48m53c1or
Change-Id: Ib9813a48170f4ef38de9eee811c677ad75f5401e
