Bug: 31002801
Test: make RunSettingsLibRoboTests
Adds an optional metadata field to specify the key used for an injected
preference.
Change-Id: I3426713783b58020849bc384334ad173061847e9
During grouping, tiles are sorted based on package name, and their own
priority value. However if the package is Settings itself, the ordering
is not changed.
Before sort: [pkg1, 100], [pgk2, 120], [pkg1, 130]
After sort: [pkg1, 1], [pkg1, 2], [pkg2,3]
This is necessary to make sure settings app have the overall control of
ordering of all dynamic tiles. When each app define their priority, they
don't have access to the global vision of what other settings are on
screen so it's possible different app define conflicting orderings.
Settings app is the only reasonable place to rank them properly.
Bug: 32827787
Test: RunSettingsLibRoboTests
Change-Id: I38de55530e61da9de7532ef6a7ee97ef89aca9d9
Add TtsSpans to the GMT offset string so that TalkBack knows to
read it out in a more natural way.
Retain the old keys with string types for compatibility with TV and
wear.
Test: m SettingsLibTests && \
adb install -r $OUT/data/app/SettingsLibTests/SettingsLibTests.apk && \
adb shell am instrument -w com.android.settingslib/android.support.test.runner.AndroidJUnitRunner
Bug: 30042703
Change-Id: I5629a0113404b32b606c1f03060f32868b59c6d2
- Move SettingsLibTests to tests/integ
- Create a new robotests directory for SettingsLib.
- Add test cases for CategoryManager#backwardCompatCleanupForCategory
Bug: 32382487
Test: make RunSettingsLibRoboTests
Change-Id: I7ef5921ce8c47a3e1e7209be1abc97ea549a2378
- AccessPointListener was not set on AccessPoint in one of the code
paths and as a result, the UI wasn't notified of changes to the
AccessPoint.
Test: Manually tested and verified that notification changes were
delivered to the UI. Also added unit test.
bug:31945554
Change-Id: I89affada5dead4edc4218f424eec6b7f4a4e26a7
Change two public functions in ZoneGetter to have the same logic,
now in both functions the display name is based on the locale.
Bug: 19764807
Test: make SettingsLibTests
Change-Id: Id818d4bdb8b1a24c039dd5a3ea57d8fc09970352
The testcases are mainly to test warningBytes and limitBytes
could follow the constraint that "warningBytes <= limitBytes"
Bug: 30560513
Test: make SettingsLibTests && \
adb install -r ${OUT}/data/app/SettingsLibTests/SettingsLibTests.apk && \
adb shell am instrument -w \
'com.android.settingslib/android.support.test.runner.AndroidJUnitRunner'
Change-Id: I5722b0fc41e366e2b77a4a20242a5c9a523636fb
- Jank on setupwizard's wifi screens caused by concurrent modification
of AccessPoint on Worker thread while the wifi list is being updated
in the Main/UI thread.
- Fix this problem by maintaining two separate lists, one that is
modified in the worker thread and not published to outside components,
while another list that gets published on the main thread. The
AccessPoint changes are computed on the worker thread and once thats
done, the changes are then copied over to the published APs on the
main thread.
Test: Connected to multiple APs through both suw & settings. Did not
notice the jank. Also added unit tests
bug:30704173
Change-Id: I78666608d39d3680b91980c1a7907d239dc82799
When open QS wifi panel while wifi was off was causing a crash from
wifi enabling while the WifiTracker was not in a scanning state.
Fix plus a test enclosed.
Bug: 19322090
Change-Id: Id863cdcbf4aa8d50822de3a200355dbaee74b488
Make SettingsLib capable of tracking which wifi networks are
available/saved and their state.
Also modify Quick Settings to use this code rather than having
its own logic.
Bug: 19180466
Change-Id: Iff9f9aed240d79323dba41496496e8076b9fa6f2
