app_Settings

Go to file

Rubin Xu 359a6b5c06 Do not set separate challenge flag before clearing lock

This step is redundant since clearLock() would set the flag internally anyway.
In fact setting the flag before calling clearLock() is wrong since it will
lead LockSettingsService.setLockCredential() to think that the target profile
does not have a unified challenge, causing it to use an incorrect existing
credential for password change, leading to untrusted credential change.

Bug: 77892111
Test: Create profile; set separate empty work challenge; observe no crash
Change-Id: I4d76b20706a796654f9389f31ae8c46d51d7adac

2018-04-11 11:43:18 +01:00

res

Merge "Add new string for audio switcher" into pi-dev

2018-04-10 04:24:16 +00:00

src/com/android/settings

Do not set separate challenge flag before clearing lock

2018-04-11 11:43:18 +01:00

tests

Fix robotest failure for ChartDataUsagePreferenceTest.

2018-04-09 18:12:46 -07:00

Android.mk

Updates to match prebuilts drop