When the device is lost or stolen, it's safer to
fall back to strong authentication (pin, pattern or
password). This disables fingerprint like we do with
trust agents.
Fixes bug 21620081
Change-Id: I7bbe54be3721b2f160b783daeb3acbe434705046
This fixes a bug where we were counting short PIN, patterns and
passwords as attempts. For devices with a device policy admin,
this would cause devices to get wiped after a short amount of
interaction with the UI.
Fixes bug 22844609
Change-Id: I7616b38d954f89d4a2cee23f9aec1b898041b1f2
KeyguardUpdateMonitor should not call cancel() when fingerprint
auth fails. The life cycle will continue until an actual error
occurs or the maximum number of retries is reached.
Fixes bug 22562277
Change-Id: I36291d025de9c049cc7f7924f692c8c21349bb7b
- remove the content description in Keyguard
- only show virtual views when pattern is in progress
- add a content description when the pattern is not in progress
Bug: 22646748
Change-Id: Id32a37c4c74c82b547cee8861b2856fa0a08c41c
- Add callback to inform SysUI when the screen has been unblocked
and turned on.
- Cleanup inconsistent messaging about device interactive/screen on
and off.
- Add callbacks to inform SysUI about screen states
- Implement a quick fade for the scrim after touch, wake, and unlock.
First, start with a black scrim on top of everything, and then fade
it out.
- Make sure we play the normal unlock animation when device is pulsing
- Override navigation bar animations for touch, wake and unlock: Fade
in the same manner as the scrim.
Bug: 22571198
Bug: 21855614
Change-Id: I8ff08d72cced1e0f03c78d71ff710d8a4f6b848c
We now keep the fingerprint running and switch to the bouncer when
the user successfully authenticated.
Bug: 21618072
Change-Id: If00061cb3914afd4d7a7d75964594484c792a890
- Add onFingerprintAcquired, so Keyguard can grab a wakelock to prevent
the device from sleeping.
- If we get a successful fingerprint, wake the device up, immediately
dismiss the keyguard and tell PWM that we kicked off our frame that
will represent the correct state.
- PWM then waits for this frame to be drawn, and then turns on the
screen, which results in unlocking directly to the previsouly
opened app.
Bug: 21855614
Change-Id: I5f43df17fa5e4e9c6a6392eef4a4590b07df4f96
Previously the fingerprint animation would not run
when we successfully unlocked with the fingerprint,
because we were checking for the wrong state.
Bug: 22483380
Change-Id: I8d3ec303a43323431b8866df29ddd6d668edc1ed
The default Material theme for presentations on external displays
has a white background. This changes keyguard to use a custom theme
since we want white lettering on black.
Fixes bug 22305037
Change-Id: Idc6aca2398be34c4603446983e5d276abcace001
When first authentication is failed, keyguard does not try authenticate again.
This modification makes to try again authentication
when it receives callback of authentication failure.
Bug: 22131472
Change-Id: I5bdfc8b120595bf3252ad6e7353ace7ff7fbbae0
The lockscreen was skipped when the security mode was
swipe, which is inconsistent with the normal bootup
behavior.
Bug: 21850021
Change-Id: I2c59b1428d489fad566097771ca449ba667f34d2
A message can now be shown on the keyguard bouncer
explaining why the bouncer is being shown.
Bug: 21618072
Change-Id: I25aea9cc242abbf6a133fb42cc4407f5c2f3f688
CarrierText wouldn't always update the text when airplane mode
changed, because it depended on the subscriptions to change to
know to update. Now have KeyguardUpdateMonitor listen to airplane
mode changes so that we update text when needed.
Bug: 21705446
Change-Id: I64e1194ebb055ad10acd96b33e22b95fe2454425
We no longer send fingerprintid to non-privileged apps. Though
Keyguard can get the permission, it does not currently use fingerprint
info, so remove the API call.
Fixes bug 21040383
Change-Id: I8a9461ed138c368afc75601fe6d4eadc9a8b91c5
Let the intent receiver of a camea launch intent declare a prewarm
service instead of sending broadcasts.
Bug: 21347653
Change-Id: I11e31aad4f788ad90eb46a661b819d3e808ddb51
KeyguardBouncer could have 0 as its content area size. Two transient
cases found: on device boot with a 0 sized StatusBarWindowView and
first time showing after user switching. Be defensive and protect
against the case.
Bug:21333202
Change-Id: I73eabf64c597ea3ae96ccfba1aecf702da8dfb23
