A shadow of DPM is automatically added as system service by Robolectric infra. Since SupervisionManager is new, it doesn't have that.
We will consider changing Robolectric to do the same thing when SupervisionManager becomes more stable.
Flag: TEST_ONLY
Bug: 382034839
Test: atest ActionDisabledByAdminDialogHelperTest
Change-Id: I389938df10ce97c563511473b0aeaee52225f419
By moving these from onStart to onResume. Looks like a recent change to Settings broke this.
Bug: 391543900
Test: manual
Flag: EXEMPT Trivial bugfix
Change-Id: Ie9b8bd08e8513e7c6c2f1baeab4801af2fbe1cae
Test: manual go through SUW setup Pattern view, and make sure pattern
view do not shift in confirm step
Fixes: 324489595
Flag: EXEMPT bugfix/clean up layout issue
Change-Id: Ia5e6ef8a8c9ecf712f69bfde2bb631dc2605210d
UiAutomator is case sensitive. On AOSP builds, the "Erase all data"
string is displayed in all caps in the dialog box on trying to erase all
data and switch to ext4 mode. This is a workaround fix for the issue.
Bug: 390535191
Flag: EXEMPT bugfix
Test: Enable16kbTest on AOSP Pixel 8 targets
Change-Id: I119fe076eb3eb037a23f07af77b9ad4935cb4064
Bug: 367414968
Test: atest com.android.settings.accessibility
Flag: EXEMPT cleanup
NO_IFTTT= Change does not alter preference list
Change-Id: I64f5f7fba112b6fb5035b88f01c04d9ee309f2c0
- For experssive style, items split into 2 groups. Item "battery percentage" for a single group.
- For original style, reorder the items, sort item "battery percentage" at the last.
Bug: 349652542
Test: visual
Flag: com.android.settingslib.widget.theme.flags.is_expressive_design_enabled
Change-Id: I4a163d075ecd94a8079839dc0ad34dd993a7c725
Provide an interface to inject new Fingerprint Settings from
FeatureProvider.
Bug: 388488353
Flag: EXEMPT support interface, flag only used in impl part
Test: atest FingerprintSettingsFragmentTest
Change-Id: I9d82e3e0b50a7aa1ed65f34ff0272d2a1b5881a9
Root cause: there's a mismatch in how visibility is determined for
the AutoBrightnessPreferenceControllerForSetupWizard. The
getAvailabilityStatus method and the displayPreference method
(specifically the preference.setVisible call) use different
conditions for showing the preference.
Solution: To ensure consistency, I propose aligning these conditions
by incorporating an aconfig flag check in both places. This will
prevent unexpected behavior and make the logic clearer.
Bug: 389011125
Flag: com.android.settings.accessibility.add_brightness_settings_in_suw
Test: atest AutoBrightnessPreferenceControllerForSetupWizardTest
BrightnessLevelPreferenceControllerForSetupWizardTest
Change-Id: I004bfe8b1e039734356715c971f0bfbe56ffa9db
There is no mock for
FaceFeatureProvider.getEnrollActivityClassProvider() in aosp which
caused the null exception test failure.
Use FaceEnroll class name to lauch enroll activity directly to fix this
issue.
Bug: 388933801
Test: atest FaceSettingsEnrollButtonPreferenceControlleTest
Flag: com.android.settings.flags.biometrics_onboarding_education
Change-Id: Ibbbbe888f95c1ece0372ac31435ce6817cba45b5
