- space between digit and mnemonics
- better center the (left-aligned) text in its container
- nudge the enter arrow a little to the left in its
container
- add missing contentDescriptions for SIMPIN/PUK
Bug: 7427380
Change-Id: I0f5d9d1554a476c00591981028733ee6924bb729
If applicable, also announces that the user needs a headset when
displaying the PIN pad layout. Also fixes accessibility focus "falling
through" to the next Z-ordered view.
Bug: 7436382
Change-Id: Ic1db5320b2e47ff181c5902e9f7980fe3fe6756b
-> vertically resizable widgets behave are sized to fill
-> non-vertically resizable widgets use the small size all the time
-> providing size call-backs. ensuring that we don't send excessive /
incorrect size callbacks. These are expensive. Had to clean things
up to ensure we only send the truth, and not bounce around.
Change-Id: I8038de01096906526e2622c6f1cd24c171e3a4ec
This was causing problems because face unlock and the camera app are
competing for the camera.
The solution is to not show the security method until we get back to
keyguard.
Change-Id: I179548e4ee6aa0ab5dad545842ddeb14bc3b58e1
Also, if we have no widgets in lockscreen,
reinflate the default widget. If that fails,
inflate the built-in clock (KeyguardStatusView)
Change-Id: I2e90ab0893c993a755700e075e4a8ac5a685e0f2
Bug 7453429
Change the detection of sliding the security view to require crossing
the border between sections in the correct direction. This also
improves the feel of re-opening the slider.
Change-Id: I57797f926e017ea2cf41f7c48e0fe77ac0f78460
FUL is suppressed when first booted and unsuppressed when the user
leaves keyguard (by logging in or turning the screen off). However,
if the user managed to enter the phone without going through
keyguard (security set to none, or initial device setup), FUL was
not being unsuppressed and it would not show up the first time the
user tried to use it.
This fix only suppresses FUL on first boot if it is the selected
security method. Therefore, it is not suppressed the first time it
is used after setting it up.
Change-Id: I766bbce31ce3939de97661623fe3b8d3fa29c20d
Added a check in pattern and PIN to showed the face unlock max attempts
failure message if that had been reached. The max attempts can only
be true if face unlock is enabled so it doesn't need to also check if it's
enabled.
Change-Id: If8a26498961d79fa6a647abc923c72f0af407e61
Since the callback is unregistered in onPause(), KeyguardFaceUnlock
doesn't get onKeyguardVisibilityChanged() when it's paused. This means
that if the state changes while it's paused, then mIsShowing is incorrect
when it resumes. This is fixed by keeping track of the state in
KeyguardUpdateMonitor and checking it when onResume() is called.
Change-Id: I67aa1e091161a965e4347dc8c2ec5e7a1dd9d92e
Face Unlock would reappear when rotating a tablet after it had already
fallen back to the backup unlock method. This change suppresses Face
Unlock after going to the backup so it isn't seen again until the user
leaves and revisits keyguard.
This change also removes the exposeFallback() callback from Face
Unlock. It has been unnecessary for a long tiem since Face Unlock no
longer covers the backup. The Face Unlock service was therefore
making unnecesaary calls via the AIDL interface.
Note that the AIDL interface change broke obsolete keyguard stuff.
That is being deleted soon anyway, so code has just been commented out
of the obsolete files to make it compile.
Change-Id: Ia5c451cce1703b3bc03e27a35c6b38373e944d1b
