Skip to content

Commit

Permalink
Redundant waiting time of keyguard unlocking after reboot
Browse files Browse the repository at this point in the history
LOCKOUT_ATTEMPT_DEADLINE and LOCKOUT_ATTEMPT_TIMEOUT_MS
should be cleared for every successful screen unlock.

bug: 36535118

Change-Id: Ia0a95f04f7fbbe83f1ee059fa550ba67097ef48b
Signed-off-by: Huang, Yang <yang.huang@intel.com>
Signed-off-by: xyyx <xyyx@mail.ru>
  • Loading branch information
yang8621 authored and xlxfoxxlx committed Jun 29, 2017
1 parent 9b19e88 commit ca8b01e
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 0 deletions.
Expand Up @@ -166,6 +166,7 @@ private void onPasswordChecked(int userId, boolean matched, int timeoutMs,
if (matched) {
mLockPatternUtils.sanitizePassword();
mCallback.reportUnlockAttempt(userId, true, 0);
mLockPatternUtils.getLockoutAttemptDeadline(userId);
if (dismissKeyguard) {
mDismissing = true;
mCallback.dismiss(true);
Expand Down
Expand Up @@ -278,6 +278,7 @@ private void onPatternChecked(int userId, boolean matched, int timeoutMs,
if (matched) {
mLockPatternUtils.sanitizePassword();
mCallback.reportUnlockAttempt(userId, true, 0);
mLockPatternUtils.getLockoutAttemptDeadline(userId);
if (dismissKeyguard) {
mLockPatternView.setDisplayMode(LockPatternView.DisplayMode.Correct);
mCallback.dismiss(true);
Expand Down

0 comments on commit ca8b01e

Please sign in to comment.