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
- 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
In certain cases when lockscreen is constructed in landscape and then
switches to portrait on the phone, it inflates new views for
KeyguardHostView. The old views never call onPause() in KeyguardFaceUnlockView
so it was still getting callbacks and starting Face Unlock multiple
times. By removing the callbacks in onDetachedFromWindow() there won't be
multiple instances of KeyguardFaceUnlockView receiving callbacks and
starting face unlock.
Change-Id: I00d770283e83be2f4b76e00340123789a8075091
Bug: 7473142
Provide hidden methods in AccountManager for querying accounts and
authenticating for a specific user. Lockscreen is running in the
system process. Allow only system process to access accounts across
users.
Also make sure to launch the lock settings screen on the just reset
user using startActivityAsUser()
Change-Id: Ifefc0039ba2b51396b8bd0268f36d5271a3d8676
Change the keyguard window to LAYOUT_IN_SCREEN | LAYOUT_INSET_DECOR
and make the ViewManagerHost fitSystemWindows. This eliminates the
need to resize the actual window and associated surfaces when the IME
comes and goes.
Force the widget pager to measure at the fullscreen size of the
keyguard, even if the IME is showing. This causes the widgets to clip
instead of resize, removing a few more moving parts that can be
distracting/affect performance.
Partially improves bug 7427586
Change-Id: I0d86d0ca8045f737fa97ca5d1e7f6a49f746b999
We can stop before the service connected message is processed, in which case
we should clear the message. Otherwise it can cause us to start up the UI
before the camera is open, causing a crash.
I was unable to reproduce this issue, but it theoretically will happen, and
the bug report shows all the symptoms of this series of events.
Change-Id: I60d295883b08ac58ccf0f3fc6d152b8b75fe9b18
-> If the challenge is showing and the page is swiped, instead of immediately
sliding down the security and expanding the small widget, we instead
quickly fade out the security and keep the widget+frame small until
the page settles and fades out.
Change-Id: I0f376dcd863744b977a1c5ccc7a46a5c6fdb891d
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
