The gnarly stuff where we keep track of the old input method
window as if it was still there was sitting around leaving things
in a stuck state. Now we clear this out at key points in the
window manager (freezing screen, user change), and the input
method manager service is less aggressive about asking the window
manager to do it.
Also fixed a problem that was causing flickers during some
wallpaper transitions -- when we are animating two things on
top of the wallpaper and one of them disappears, we need to
make sure the wallpaper target points to whatever the current
target should be (if any), not left pointing to the old target
that has gone away.
Change-Id: I2fb9600f569a5bd5e3528aaf24cde9340af56cb0
* commit '6490f42be703e17a1d3c49b4fccb49957c6511f2': (26 commits)
hide the correct text, and more text, on bounce
Improve PIN key layouts.
Obscure speech for PIN password keys when no headset plugged in.
Initial changes to allow dropping on delete target to remove widget.
hide multiuser selector when IME is up.
Block swipe up gesture if challenge non-interactive.
Properly disable challenge handle.
Disable disable back if using an alternate back icon.
Disable security handle when swiping into camera widget.
Import translations. DO NOT MERGE
Fix small issue with previous CL
Widget size policy, size callbacks
Don't show security method until we actually return from the camera
Fix whitespace problem and sync with prototype.
PUK support.
Fix build.
SIM PIN support.
Use clock's widget as the default keyguard widget
Add configurable em-dash separator for all concatenated keyguard strings
Cleaning up keyguard persistence threads when the pager is detached. (Bug 7460991)
...
- 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
* commit 'fc3d4dbd091ad91307bbba63892f2cee42f97f5f':
Keyguard sliding challenge - fix overeager touch interception
Addressing comments in 74bdd21629681528dbe7f3ea363d99c8514e026b.
Showing message when max attempts are hit in face unlock fixes b/7306168
Keyguard tablet/portrait fix for HUGE security views
Cancel camera launch on screen off.
Fix launcher flash during secure camera transition.
Updating isShowing during onResume()
Suppressing FUL after going to backup fixes b/7449820
Addressing comments for change c4842c11932ea4f60fe7ae09b0a59660207e1587
Adding a button for expanding the clock screen challenge.
Accessibility support for the lockscreen - phone.
Stripping dead API related to keyguard widgets
FUL being unsuppressed when screen turns off fixes b/7453702
Show the keyboard less aggressively.
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
