Create an architecture for the homepage to enable card adding
and displaying.
Bug: 111676964
Test: robotests
Change-Id: I06efe3d16585060a8e99313586ae29bbde7fe3e8
- change the way that default home query the resolve activity to only
check for LAUNCHER activity.
Change-Id: Ib53154afe7951f4e2c7c3ab147be4c691113e0e7
Fixes: 112249115
Test: make RunSettingsRoboTests
- Instead of force refresh when user tap action button, we not wait
until state changes for each conditional cards.
Test: robotests
Change-Id: I2eca59a06b8cb332b7b99f017baefb3d5b53234b
Add a developer options settings switch to enable a virtual
HiFrequency panel mode to be able to test the SW stack with
display running at 50% faster than the default refresh
rate.
Bug: 111549030
Test: Enable HiFrequency mode and use systrace/adb to verity
Change-Id: Ibfd30ca1a14a146419233eaefa9b5095bf459adc
- confirm that StorageWizardFormatConfirm works well after
changing calling method from showAllowingStateLoss() to show().
Bug: 111150236
Test: manual
Change-Id: I0ad6c54aaa2572fc5798ede900e0a6d10d2fbd35
To make behavior consistent in the long run and refactor the code
into settingslib and call it from both Settings and SystemUI.
Bug: 110973964
Test: run testcase and do manual test - test case as below:
1. Testcase: packages/apps/Settings: -> ALL PASS
make RunSettingsRoboTests ROBOTEST_FILTER=SimStatusDialogControllerTest
2. Fake the service state's voice and data value,voice is out of service
and data is in-service,and then check service state and signal strength
at sim status page -> PASS
Change-Id: I4cc454b6b3d4242af4805e2878f9d46ce28649ad
- make sure that StorageWizardFormatProgress runs smoothly.
- confirm that mTask has the same object id when changing the screen
orientation.
Bug: 111151113
Test: manual
Change-Id: I730c1b0f08e8a20a1aafa668fb02cd5a09fdd70a
1. Use BluetoothDevice.ACCESS_* instead of CachedBluetoothDevice.ACCESS_*
2. Use BluetoothDevice.setPhonebookAccessPermission() directly.
3. Use BluetoothDevice.setMessageAccessPermission() directly.
4. Use BluetoothDevice.getPhonebookAccessPermission() directly.
5. Use BluetoothDevice.getMessageAccessPermission() directly.
6. Use BluetoothDevice.getSimAccessPermission() directly.
Bug: 112517004
Test: make -j42 RunSettingsRoboTests
Change-Id: Ibe6b207b891b9bd2b328a2e2c7264a9a78cb498f
Use ApplicationState to count number of apps using unrestricted_data.
Change-Id: I083ff50e3e516536c87afa71d786b22e83d9a498
Fixes: 69313992
Test: robotests
Activity null check is probably necessary when this logic is written in
fragment, now the logic is in a controller where all dependencies are
self contained, so we don't need to check activity null here.
Change-Id: Ifa32e0d6563c411f19bec07f176765a7c94c8a40
Fixes: 112289663
Test: robotests
Don't clear the text when reciever has been re-registered in
onResume(), where quickUpdate has been called.
Change-Id: Ie056dfb225a1bf6c224932b310a97499fc26e8f0
Fixes: 69312991
Test: RunSettingsRoboTests
It happens due to a race condition when the AutofillDeveloperSettingsObserver
is triggered by a settings change while the underlying preferences activity is
being finished.
Fixes: 113030661
Test: echo 'could not reproduce this issue'
Test: runtest --path \
packages/apps/Settings/tests/unit/src/com/android/settings/core/\
PreferenceControllerContractTest.java
Test: atest AutofillResetOptionsPreferenceControllerTest \
AutofillLoggingLevelPreferenceControllerTest
Change-Id: I761195df13ac10705b9ce6b0c7546ec66a85d3ef
Updates strings according to spec. Also ensures
that the emulation overlays are shown in the
order of their priority.
Bug: 112876936
Test: Open developer options, go to "display cutout", verify strings.
Change-Id: If2d05595d02a277896202ab2a6262c99508a3a17
- Use the title (not summary) of the preference in its warning dialogs
Test: manual
Bug: 112687996
Change-Id: Ia217e5252cf7a48450da853c0270093ffb57dca7
And switch to getId() instead of title when comparing 2 tiles. This is
more accurate and more efficient.
Bug: 77600770
Test: robotests
Change-Id: I587d90702d98956bf7b420529ac3280351ca4a10
Modify the WifiSliceCode to follow the pattern for
Slices that do not match existing UI components.
Test: robotests
Bug: 80263568
Change-Id: Id69e019608777282f4b64ff945e8c30c97aaf577
"None" doesn't make sense for work profiles because it makes
profile insecure even if primary user is secure. If the user
wants to get rid of separate challenge, it will be offered in
previous Settings page, "Use one lock", so this shouldn't cause
any confusion.
Test: atest tests/robotests/src/com/android/settings/password/ChooseLockGenericControllerTest.java
Test: manual, tried setting personal an work challenges from Settings and via Intent.
Bug: 33656033
Change-Id: I830b3e372c1fe200fc4e02d59e3c3805bac5f9bb
