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
The new test checks whether the item is available when the
SubscriptionUtil.isSimHardwareVisible() method returns true, i.e. if
the config_show_sim_info boolean flag is true on non-test runtime.
The default visibility status for all tests is defined in the test
setup() method, as this will also simplify the addition of new checks
later on.
Bug: 392808943
Flag: EXEMPT test only
Test: atest MobileNetworkPhoneNumberPreferenceControllerTest
Change-Id: Icedef190a8140fd8164dd8035ae93735a666b9f0
The tests check whether the item is available based on the result of
the SubscriptionUtil.isSimHardwareVisible() method, which is the one
allowing to check the value of the config_show_sim_info boolean flag
on non-test runtime.
Bug: 392808943
Flag: EXEMPT test only
Test: atest PhoneNumberPreferenceControllerTest
Change-Id: I2d1361ecef8a9c1083b4fd6fd4462c7815574827
If the user credentials dialog displays multiple elements (e.g. if the
certificate is used by a wifi configuration), the content size exceedes
the available space.
Currently, the alias text view is the only element which declares a
`layout_weight`. The LinearLayout failes to distribute the space
correctly, pushing it beyond the bounds.
Bug: 287533409
Flag: EXEMPT bugfix
Test: manual
Change-Id: Ieff1b3011080dabf823c7689a3781c6e52b9791d
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
