RestrictedSettingsFragment is deprecated and no longer supported. To be
compatible with catalyst, change the super class to
RestrictedDashboardFragment.
Bug: 372733639
Test: atest NetworkProviderSettingsTest, manual tests with user restrictions
Flag: EXEMPT N/A
Change-Id: I02b08363dadd5739a1d348f099d439b9f82ffb18
- Use one Controller to manage preferences related to battery Optimization Mode.
- Move optimization mode & preferences status update logic from Fragment to Controller.
Bug: 373544647
Test: atest AdvancedPowerUsageDetailTest PowerBackgroundUsageDetailTest BatteryOptimizationModePreferenceControllerTest BackgroundUsageAllowabilityPreferenceControllerTest
Flag: EXEMPT for simple fix
Change-Id: I2b1fed837fb4904e4118ab51c1d0cda36c0f6198
This reverts commit 2545f06558.
Reason for revert: DroidMonitor created revert due to b/374650528.Will be verified through ABTD for standard investigation.
Change-Id: Ifa3f061b7954dc2b5780b768fefb9358c597fdc0
Test was failing because it was not setting the EXTRA_LOW_POWER_WARNING_ACKNOWLEDGED setting.
Change-Id: Id9e95c0240908dafbaa791e7f4f4b9ded9d39d9b
Test: atest BatterySaverScheduleRadioButtonsControllerTest
Bug: 370883745
Fix: 370883745
Flag: EXEMPT for simple bug fix
These are unnecessary now that shortcut enabling is done via
A11yManager#enableShortcutsForTargets which handles enabling
a shortcut-required service if necessary, controlled by the
rolled out a11yQsShortcut flag.
These also cause a race condition conflict when attempting to toggle a
service that does not require a warning, causing it to disable the
service immediately after enabling.
Bug: 324653372
Flag: android.view.accessibility.a11y_qs_shortcut
Test: Toggle a shortcut-required service that does not require
a warning; service is started correctly.
Test: Repeat for a service that does require a warning
Change-Id: Iff44d87faf8a5d2eb9b6643dd582c2b697ad0b5d
- Add a flag for the migration
- Add the skeleton of the screen
Test: atest LocationScreenTest
Bug: 368360458
Flag: com.android.settings.flags.catalyst_location_settings
Change-Id: Id8b7d748210d1cacf99e3d61236706029b862289
- Add a flag for the migration
- Add the skeleton of the screen
Test: atest BluetoothDashboardScreenTest
Bug: 372774767
Flag: com.android.settings.flags.catalyst_bluetooth_switchbar_screen
Change-Id: I48e446532d3e839ae55880095a496e3ac4790c81
- Add a flag for the migration
- Add the skeleton of the screen
Test: atest MobileNetworkListScreenTest
Bug: 368355368
Flag: com.android.settings.flags.catalyst_mobile_network_list
Change-Id: I9d5d57b78d8f2c7d2bc6fd02e402fcdaf5b97bdf
This fixes an issue where this page was presenting an inaccurate
preference list count to TalkBack because it was including this empty
preference.
(Uses the same flag as other fixes for this same bug, even though the
flag name doesn't make sense here.)
Test: atest EditShortcutsPreferenceFragmentTest
Test: Confirm preference invisible when editing a single feature,
opened from the Settings app
Test: Confirm preference invisible when editing a single feature,
opened from the FAB Drag-to-Edit
Test: Confirm preference still visible when editing multiple features,
opened from the FAB Drag-to-Edit
Test: Confirm TalkBack announces correct item counts in both cases,
including when editing Magnification which has an "advanced"
preference that gets replaced with the triple-tap shortcut.
Bug: 318607873
Flag: com.android.settings.accessibility.toggle_feature_fragment_collection_info
Change-Id: I2e1eb7f66022c1a47d1f96a914294fd8da25549c
1. support non-flow version isEnabled
2. support send announment
Bug: 372385781
Test: Function works w/o build break
Flag: EXEMPT feature flag protected on override project
Change-Id: I2867edf9e9b9cc9190888e257a203acd7877ab3b
