Adrian Roos 16809b1ad7 Fix race leading to spuriously disabled trust agents
If TrustManagerService is able to refresh the trust agents before
the Settings activity gets a chance to reenable the lock pattern,
the TrustManagerService won't see a secure credential and won't
load any agents. This was introduced when we switched to isSecure
instead of getKeyguardStoredPasswordQuality. The latter ignored
the lockPatternEnabled flag.

Bug: 18596036
Change-Id: I2734899f7684916fc84bc3a07edca29310887103
2014-12-05 18:47:20 +01:00
2014-08-24 13:07:11 -07:00
2014-08-22 12:24:00 -07:00
Description
No description provided
3.1 GiB
Languages
Java 89.8%
Kotlin 10.2%