Move timeout scheduling mechanism from KeyguardUpdateMonitor to
LockSettingsStrongAuth.
Move reporting about successful strong auth unlock from
KeyguardUpdateMonitor#reportSuccessfulStrongAuthUnlockAttempt()
to LockSettingsService#doVerifyCredential() - the latter also
covers work challenge strong auth unlocking.
Test: manual with all types of strong and non-strong auth, including work challenge
Bug: 29825955
Change-Id: I38e51b21e3a455b95e3c857e091fe07ee388c7f8
Test: Manually tested onDeviceUnlockLockout being called with an actual
TestAgentService implementation.
Notes:
- Active Trust Agents are no longer killed/unbinded from when a temporary
device lockout occurs. Instead, the onDeviceUnlockLockout callback of
the agent is called.
Change-Id: Ifa0984d1d7e5153568334d736e9ebd5a00ef1297
Bug: 34198873
Shows the clock without the date. Also stop
hiding the stack scroller in AoD.
Bug: 30876804
Test: manual
Change-Id: I5f2a8e39be7750493dd8dac83641ac0b96082d0e
When user fails an authentification in lockscreen many times,
"Try again in 30 seconds." is displayed and a 30 seconds
timer starts to count backwards.
This lets "Try again in 1 seconds" to be displayed for one second.
Bug: 31078006
Change-Id: I6c7de2b751582bb06a93e583b710f83201da1728
The fingerprint timeout tracking in KeyguardUpdateMonitor has been
extended with use of StrongAuthTracker.
Test: timeout will be CTS tested, testing of unlocking TBD
Bug: 29825955
Change-Id: I5cc49ef46631c412f2d1db88e68a308322b27027
Cleanup:
- Make sure all the state is nicely dumped.
- Remove some unused stuff.
- Fix a flicker when occluded -> unlocked
Bug: 32057734
Change-Id: Id87e26adccef740d608b325c2dc1f6db14dd4ec3
Fixes a bug where the keyguard message area would reorder clears
after a new message was set, leading to the bouncer prompt reason
not showing.
Change-Id: I33001300d9175c521809cd4fdae5158269245c00
Fixes: 32306174
Test: runtest -x $T/frameworks/base/packages/SystemUI/tests/src/com/android/keyguard/KeyguardMessageAreaTest.java
- Remove timinig out of messages. This is no longer
necessary because we do not show the owner and charging
info in that area anymore.
- Remove the "important" parameter, which was equivalent to
clearing the message if false.
Change-Id: I5fae5432724ad90a68f53f678f933c4a15dc6e9b
Fixes: 28270749
Test: manual; reboot device, swipe up, verify message doesn't disappear after 5s
- Move latency fake actions into a central location, LatencyTester
- Add latency test for screen turning on
Change-Id: I8aa3f475d56a4ee7a36b97bd6ece32e60c5851cd
- Make sure the latency also gets tracked on first unlocked in
which we cancel the AsyncTask.
- Also add it for pattern authentication
Change-Id: Ie1561264b0a3b75c09819ccc6d269e61e367e1be
This commit makes it harder for a users pocket to trigger an MDM
remote wipe, by setting the warning dialog to noncancelable.
With this change the pocket would first need to tap on OK before
being able to attempt to enter a PIN. This mirrors the existing
behaviour of both PIN and PUK warning dialogs.
Test: manual - enable an MDM set to trigger a wipe of the device/user
on unsucessful unlock attempts. Then incorrectly enter your PIN until
the warning dialog appears. The dialog should only be dismissable
by pressing the 'OK' button.
Change-Id: I4d86af555a5d8b226ceffa4711bd5e277db93f1e
Test: Unlock freshly booted non-FBE device, make sure the transition
is fast as well as the icons have the correct state
Change-Id: I6427427d16edeceb0f410be0b88de601a3dffdb4
Fixes: 31203310
