This change hides the "Send feedback" button when a target for
the intent is not found. This will ensure the button is not
visible in cases when clicking it would have done nothing.
Bug: 283239837
Flag: com.android.settings.flags.datetime_feedback
Test: Test: atest TimeFeedbackPreferenceControllerTest.java
Change-Id: I8bb18c313925a7dc7ac07a1fb4c2f9e2d98352db
This update already happened for ZenModeAllBypassingApps to use the new single binder call to get all packages bypassing DND. This change uses that method for bypassing apps as well as collecting the set of all apps with a nonzero number of channels.
Bug: 368623163
Bug: 394614704
Test: ZenModeAddBypassingAppsPreferenceControllerTest, manual to confirm correct behavior
Flag: android.app.nm_binder_perf_get_apps_with_channels
Change-Id: I72a1edcb07d18f5707591a5341d7a7338c23f42b
The Phone Number field in either the about or network details pages
should not be shown if the device does not have telephony
capabilities.
Bug: 392808943
Flag: EXEMPT bugfix
Test: atest PhoneNumberPreferenceControllerTest
Test: atest MobileNetworkPhoneNumberPreferenceControllerTest
Change-Id: I04f682cc829d5dc7879e6cdacdaebc55a3b6fd2c
The phone number is hidden to non-admin users, following the same
reasoning that exists for other telephony-specific fields like the
baseband IMEI.
Bug: 392808943
Flag: EXEMPT bugfix
Test: atest PhoneNumberPreferenceControllerTest
Test: atest MobileNetworkPhoneNumberPreferenceControllerTest
Change-Id: I4e612219d0c7439930e91b3e1d6e368a0dfd073e
- Currently Android only handles Satellite w/ entitlement for any notifications. Some carriers such as KDDI have no entitlement for satellite service, so this change is to add some strings to avoid any confuse to Android user on satellite service.
Flag: EXEMPT resource update
Fix: b/382387532
Test: Manual test
Test: atest pass
Change-Id: I835787c9e0fe29eeecec0470e9bd6b38939abd8c
In order to avoid sending a new topology to DisplayManager
unnecessarily, which could cause some disruptive visual effect, don't do
anything if the drag was both (a) brief and (b) did nto deviate from
start position.
Flag: com.android.settings.flags.display_topology_pane_in_display_list
Test: DisplayTopologyPanePreferenceTest
Test: manual - quickly drag as few pixels as possible and verify the block moved back after drag, with no scale change
Bug: b/352648432
Change-Id: I29ffb51c54c9dbac970149cffd86a8027f0a42f5
When a) there are two sinks in sharing b) there is at least one temp
bond device connected
Test: atest
Flag: com.android.settingslib.flags.enable_temporary_bond_devices_ui
Bug: 392004799
Change-Id: Id093b4c0b67bdc1db621e0241e79900abbd26c0f
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
Some changes made to the UI, i.e. presence or absence of items, based on
feedback. There is some ambiguity because we are not fully v2 yet, hence
this change.
When all external displays are attached after opening the fragment, we
now show no preference items, whereas before we showed the pane with
built-in display options.
If only one external display is attached, we skip the "display list"
version of the fragment, and instead show the pane and other v2 items in
the per-display fragment.
If 2 or more external displays are attached, we do not show the pane
after selecting a display, which makes the rotation/resolution items
easier to find. I tried to get scrollToPreference to work but could not,
and it could be a little disorienting anyway.
To help manage the growing number of setOrder calls, keep the order
values as well as other pref data in a single spot. This also reduces
the amount of boilerplate around constants needed and makes uniform how
multiple preferences are built.
Flag: com.android.settings.flags.display_topology_pane_in_display_list
Bug: b/366056922
Bug: b/394361999
Test: TODO
Change-Id: Iaa33f6d9220a1658a372c0432fe159a69dbb88a5
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
We need proper support or Exception throw for this scenario
Test: atest SettingsRoboTests
Bug: 394813533
Change-Id: I8b552f7b2bff166643bdaa492dceff23679116ff
