| commit | 16809b1ad7262ee95d647b7655c4adf8cdeb75ab | [log] [tgz] |
|---|---|---|
| author | Adrian Roos <roosa@google.com> | Fri Dec 05 18:47:12 2014 +0100 |
| committer | Adrian Roos <roosa@google.com> | Fri Dec 05 18:47:20 2014 +0100 |
| tree | 27e0c5f06561dedb086ce472a1aa9667560554c2 | |
| parent | 3f5fd1febae34976bdc3f03b44eaec99bbf9703b [diff] |
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