It previously did some of the logic of dismiss() itself:
checking to see if the KG is secure, and if not, proceeding
to call keyguardDone() to actually hide everything. But now
that we have the "bouncer" authentication UI, the WM should
let the keyguard challenge the user to see if even a secure
keyguard should be dismissed. (Insecure keyguards should
behave exactly has they did before.)
Unless, of course, the KVM is in a "dismissable" state, in
which case it's safe to call keyguardDone() directly. (This
can happen if the user has *already* authenticated and we're
ending up in this codepath in response.)
Bug: 7458531
Change-Id: I9571acf19f9bcc16bba7a826f916da7be8ca9c33
Many media files and source code files were marked as executable in Git.
Remove those.
Also a shell script and python script were not marked as executable.
Change-Id: Ieb51bafb46c895a21d2e83696f5a901ba752b2c5
Wait for activity to launch before dismissing the keyguard.
Otherwise we see launcher/last activity waiting for the
picker to start up.
Also remove camera transition workaround obviated by:
Iefee62061962625b622ff2cf9a307d9429c2ad54
Bug:7482560
Change-Id: I554ddffb7981488fa8a81933842b0c7730e775f3
Teach KeyguardSecurityViewFlipper about layout_maxWidth/Height. Give
maxes to security views. Fix some IME layout weirdness in
SlidingChallengeLayout by adding more weirdness.
Change-Id: I8047d32302aad44844de06d54b150586b0861dab
This fixes a bug where the emergency call button doesn't reflect the current
state.
Fixes bug 7482869
Change-Id: I7de2100f10a078943cb92c13d638c72e99c7a643
Previously wake keys were filtered differently depending on whether
a keyguard was showing. If the user disables the keyguard then
no filtering was applied, which means that the volume key may
wake your device while in your pocket.
This change ensures that we use the same policy consistently
regardless of whether keyguard is showing. The behavior is
otherwise the same.
Removed the "Locked" suffix on a method that was actually
being called without a lock held and which in fact does not
require it.
Bug: 7481025
Change-Id: I704c71ca009bc5437f349f858b9de7c77ea73e4b
Have the widget view and the user switcher stay fixed when IME insets
are applied. This keeps more stability in the layouts as the IME comes
and goes.
Change-Id: I5ac62c3da6ec618280f89e87993837b3e4941ec9
1. If the lockscreen has more than one widet, the left and right widget
pages are partially on the screen and visible. Therefore they may
take accessibility focus so the user will hear a prompt that he is
on the partially visible widget page but will not be able to interact
with it - confusing. This change makes partially shown windget frames
not important for accessibility.
bug:7454355
Change-Id: I475b21e215474a4421acaec485cde64dc4e2aee5
- Disallowing taps/interaction outside of the viewport (Bug 7459448)
- Fixing regression in incorrect pivot for Camera page
- Fixing issue where the bouncer was both scaling and shrinking widget pages.
Change-Id: Iefee62061962625b622ff2cf9a307d9429c2ad54
