Many contextual cards will be built as slices, so we need a controller
and a renderer for them.
Change-Id: I3816db09ba0181399810652fb18fbe11ce273267
Fixes: 115709730
Test: robotests
I made it visible by default by accident.
Test: Looked at Settings > Security & locations > Screen pinning
Change-Id: I8ff6dc72e292ba76550edaeeac4d53ef4bd39505
Fixes: 116109852
On the Settings > System -> Multiple users screen, ensures that the"Delete from this device" menu is always available, but is disabled and includes policy information when DISABLE_REMOVE_USER is set.
Change-Id: Ia6c6cfb360f35a6e447bf9d85d2472ac11dde1ac
Fix: 113807450
Test: m ROBOTEST_FILTER=UserSettingsTest -j40 RunSettingsRoboTests; CTS Verifier Device Owner Tests/Policy transparency test/Disallow remove user.
Take a snapshot of the currently available search results, and
verify that search results aren't accidentally removed.
We use 4 items to identify a search result:
- Title
- Data Key
- Slice Uri
We use Title & Key to identify the search result, since they should not change.
The Slice Uri is used to make sure we don't regress on Slice Availability.
Test: runtest --path packages/apps/Settings/tests/unit/src/com/android/settings/search/SettingsSearchResultRegressionTest.java
Change-Id: I22498229bbcd1e90c9e0a026af9df4367a98190a
When hearing aid device has been set active, we shouldn't invoke
1. a2dpProfile.setActiveDevice()
2. hfpProfile.setActiveDevice()
Change-Id: Ie13dea041dd98d0cb9d913e1f28574b300095db9
Fixes: 113625278
Test: RunSettingsRoboTests
- move the method from DataUsageList to DataUsageUtils where other
utility methods are.
Bug: 111751694
Test: make RunSettingsRoboTests
Change-Id: If7176cb4278d568f890a0c94437c4483bbd472f9
Some app icons are really small. This is technically a bug in app, but
not handling it well makes settings UI look strange.
So in addition to setting a max size app icon can use, we just set that
as a only supported size (min == max == 36dp)
Change-Id: I4b3a1b83ab67be469ac74e7d4bb382ae855624d0
Fixes: 115788294
Test: visual
This reverts commit 3029efc5f7.
Reason for revert:
To fix null pointer crash in Pairing dialog. Dialog maybe triggered by intent, in which LocalBluetoothManager couldn't have instance for BluetoothDevice and will return null. As a result, we need to depend on method in CachedBluetoothManager to handle it.
Bug: 115754654
Bug: 112735753
Change-Id: I1ebf1f1c2829cfb75e6c382df5acf785fe54a185
- change to use the new NetworkStats.Bucket instead of
NetworkStats.Entry when iterating through the detail data.
Bug: 111751694
Test: make RunSettingsRoboTests
Change-Id: I305cc384320e4a72531d80dd9a00a3034ab12837
Bug: 74763823
Test: Manually check; sending an Intent with package:// scheme works, if
originated from app of same cert.
Change-Id: I8206197c2147cc91ef72ad89f330320781428bb9
When the last custom card for a specific type is removed,
onContextualCardUpdated should receive the cardtype info so we can
remove it from main data set.
- Reverted onContextualCardUpdated method signature back to before
- Force ConditionContextualCardController to send an empty list if
everything is removed.
* Note: the update logic is pretty complicated to handle
add/update/remove all together. In the future we should consider
spliting the removal logic to simplify this area.
Change-Id: Ied688deb693ec33e0017be02cf5c743a754a6e61
Fixes: 115572494
Test: visual
After we switch secutiry from EAP to WPA, add button will become
disabled forever. Main reason is that we use view visibility to decide
which security type it is. In this case target view is visible while its
parent view is gone. So even though UI shows correctly however we still
think it is in EAP mode.
This CL check the mAccessPointSecurity directly instead of depending on
fragile view.
Fixes: 114689178
Test: RunSettingsRoboTests
Change-Id: I4284d25e6bf86ee7c5e7c0e17f0834c719d8d587
