Flags are enabled already. The flag disabled tests should be
removed.
Fix: 395131189
Test: atest CellularSecurityNotificationsPreferenceControllerTest
Flag: EXEMPT test fix
Change-Id: I40d5c56956b714ba563cb545807deb1dee9e8d8a
Replace Autoclick sliderbar with an alert dialog
and radio group to match the new UI requirement.
Screenshot:
- Click area column:
go/screenshot-5AfdF7FGghsdiXk
- Alert dialog:
go/screenshot-4dgtojcc6lvjtyy
Bug: 390460480
Test: ToggleAutoclickCustomSeekbarControllerTest
Flag: com.android.server.accessibility.enable_autoclick_indicator
Change-Id: Ic79f8833e69dde8d8eb3e945e5acd551d2ee9ff5
In onBlockTouchUp, if DisplayTopology.rearrange happened to revert the
change made by the drag so that it matched the before-drag layout, the
blocks would not be moved, so the block would be in the dragged position
but not the normalized position.
This will happen when rearrange has a bug or is otherwise optimizing the
layout, which is dependent on the implementation of rearrange.
The test field mTimesReceivedSameTopology has been replaced with one
that represents an observable positive operation:
mTimesRefreshedBlocks, the validation of which has been added to some
existing tests.
Flag: com.android.settings.flags.display_topology_pane_in_display_list
Test: move display so that rearrange reverts the change, then exit and re-enter the external display fragment, and verify it matches the state when left
Test: DisplayTopologyPreferenceTest
Bug: b/394361999
Bug: b/394355269
Change-Id: Ic3028747d283db77f144831352b7687fe2706391
Bug: 394999568
Test: manual - Go to Screen lock settings page and check the title
Flag: com.android.settings.flags.biometrics_onboarding_education
Change-Id: I51352a43297e226cd1a72bd9edfe1211f02a4191
Add a scrolling category title in mouse settings page to match
the new design.
Mock: go/al-peripherals-ux page 3.
Screenshot: go/screenshot-8mtcgnjkabci8qt
Bug: 383555305
Bug: 384795606
Test: Local DUT with aconfig flags enabled
Flag: com.android.hardware.input.mouse_scrolling_acceleration
Change-Id: I3aa734a9e588c41dc9d48c40d779544074654a0a
We need proper support or Exception throw for this scenario
Test: atest SettingsRoboTests
Bug: 394813533
Change-Id: I8b552f7b2bff166643bdaa492dceff23679116ff
The Hotspot & Tethering feature allows sharing the current primary
data connection of the device with others using either a Wi-Fi hotspot
or USB/Bluetooth/Ethernet tethering.
The primary data connection is typically a mobile data connection on a
phone, but that is not the case on other form factors, e.g. in the
desktop experience, where sharing your Ethernet connection via Wi-Fi
(i.e. Ethernet is the 'upstream' technology instead of
cellular/mobile) may be a much more common usecase.
Given that devices can support Hotspot & Tethering without supporting
Telephony, there should be no explicit reference to a "mobile data
connection", as it is not accurate.
Bug: 393312760
Test: Manual check
Flag: EXEMPT strings only change
Change-Id: If71134deca4610a2304630f331e3a4fe62f0bc63
