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
Bug: 389002332
Flag: android.hardware.biometrics.screen_off_unlock_udfps
Test: 1. Build pass
2. Check screen off unlcok is enabled on usudfps & udfps devices
3. Enable screen off unlock on usudfps devices by default
4. Disable screen off unlock on udfps devices by default
Change-Id: I81c419f51a808a5e51d9bb92f19553cdf9e9c2f8
Changing the height of the pane causes UI elements below it to shift
around. Allow it to grow when needed but do not shrink once it has
grown.
Test: atest TopologyScaleTest.kt
Flag: com.android.settings.flags.display_topology_pane_in_display_list
Bug: b/352650922
Change-Id: I1a3e0ab77b05c5a4337e3e8ab865a974eb1faeda
Add a mirror/extend built-in display switch. Make minor changes to
DisplayTopology.kt for consistency and correctness.
Kotlin requires the two preference key names are different since they
are in the same namespace, so fix the name in the existing
DisplayTopology.kt module.
Make DisplayTopologyPreference responsible, rather than the caller, for
setting its persistence property, since a wrong value may cause unusual
behavior.
The setOrder calls are necessary to prevent the new switch from
appearing below the Built-in display category when a display is
hot-plugged in after showing the UI. We set them on all top-level
preferences (not just the two we are fixing) for consistency.
Flag: com.android.settings.flags.display_topology_pane_in_display_list
Test: atest ExternalDisplayPreferenceFragmentTest.java
Bug: b/352648432
Bug: b/366056921
Change-Id: Ib0072dd75066758903cc48c2d1e7142e1d921f67
