In original implementation, DashboardFragment.onResume calls
AbstractPreferenceController.updateState to refresh preference. While
after Catalyst migration, it requires explicit update when external
dependency is changed.
Bug: 397798327
Flag: com.android.settings.flags.catalyst_lockscreen_from_display_settings
Test: adb shell settings put secure lock_screen_show_notifications/lock_screen_allow_private_notifications
Change-Id: I1c16d7df62cdb1cb53d365f2636aa1dc0a424839
Added `display_color_mode` listener to Colors preference. As a result,
it becomes reactive and updates its color mode value summary.
Flag: EXEMPT minor change
Bug: 397659800
Test: changed color mode using `adb` commands and verify that Colors
summary reacts and print correct color mode
Change-Id: I963768e3dbb43b547ec53e6445b2791ec0f57cff
1. Refactor Color Mode by moving color summary functionality to the ColorModeUtils
class.
2. Migrated `ColorModeUtils` from Java to Kotlin.
3. Changed ColorModePreferenceControllerTest according to changes
Bug: 390644464
Flag: EXEMPT refactoring
Test: atest com.android.settings.display
Test: atest -c packages/apps/Settings/tests/robotests/src/com/android/settings/display/colors/ColorModePreferenceControllerTest.kt
Test: atest -c packages/apps/Settings/tests/unit/src/com/android/settings/display/ColorModePreferenceFragmentTest.java
Change-Id: I55ac6129b93e4e35bd58f0313215b711ce954c0a
Into SettingsSpaEnvironment.
Bug: 386013400
Flag: com.android.settingslib.widget.theme.flags.is_expressive_design_enabled
Test: visual - expressive can enabled for spa in Settings
Change-Id: I5225948c733a57855168a3e633fc4fbd4dd6f89a
This suggested change is automatically generated based on group
memberships and affiliations.
Please approve this change and vote the highest CR. This will keep the OWNERs
file tidy. We ask that you do not ignore this change and approve it
unless you know a reason the OWNER should remain. It can always be
reverted if needed.
If this change is in error, vote the lowest CR value (i.e. reject the CL)
and the bot will abandon it.
See the owner's recent review activity for context:
https://android-review.googlesource.com/q/zhangjerry@google.com
To report an issue, file a bug in the Infra>Codereview component.
Change-Id: Icfd162bf283cf74e3270d97a8ac15dcb2dfb34d3
Add autoclick shortcut to search index when
enable_autoclick_indicator flag is enabled.
Hide it when the flag is off.
Bug: 397719419
Test: atest ToggleAutoclickPreferenceFragmentTest
Flag: com.android.server.accessibility.enable_autoclick_indicator
Change-Id: Ib6d25067d024ff0dbea64d17d38fc544c615db97
Update onCreateView in AccessibilityShortcutPreferenceFragmen
so it only create a new shortcutPreference when no existing
shortcut preference is found.
Bug: 397719419
Test: Manually verified on test devices
Flag: com.android.server.accessibility.enable_autoclick_indicator
Change-Id: Ic4747240cfd3d48fd97c61fd0b15d44f6ba5cf0a
Refresh the preference every time the listener is added, not only for
the first callback registration. This is needed because when switching
fragments, the callback is unregistered by
ConnectedDeviceGroupController, so no updates are received in the child
fragments. This is handled differently by other device updaters.
UsbConnectionBroadcastReceiver invokes onReceive() in register() to
force a refresh. BluetoothDeviceUpdater requires the caller
to do a force refresh explicitly. This CL goes with the latter pattern.
Flag: com.android.settings.flags.display_topology_pane_in_display_list
Test: open CD settings fragment, remove all displays, then go back to CD entry fragment
Bug: b/398042811
Change-Id: Id139f227b1d59bde0174538b29b46fdd21ec0d24
