When maybeCreateKeyguardLocked was called from methods other than
show(), the requestFocus() call on the new KeyguardHostView was
never made.
At boot time the screen on notification was not propagated to
KeyguardViewManager because the showListener callback was null.
This passes on the notification but does not make the callback
if it is null.
Bug: 7299119 fixed.
Change-Id: Iaf058954473dc63fe4864ab1f435db4463b1110e
- set the Configuration's layout direction in ViewRootImpl instead of PhoneWindow$DecorView
- then remove unecessary API on ListPopupWindow for passing the layout direction
Change-Id: Ia2c6e4aa8cb82aed9b088bc3b8004ea0a1ded1f3
does not show if you press on power button when the "low battery" dialog is showing up
Always put the global actions dialog in the keyguard dialog layer (above
the keyguard). I don't see any reason to have it change layers based
on whether the keyguard is showing.
Change-Id: I1bd3600af9f115d662d2a4783f835e234db1b7f0
This addresses crashes caused by an upcoming change to crash
when missing layout_width and layout_height attributes are missing.
Change-Id: I71044b4623d04cab41f4aee6a7a5c01b67b0d2a5
The refactoring broke my fix for 7222226. We need to stop Face Unlock without
any messaging delay when the window is detached to avoid it starting with an
invalid window, or stopping right after it restarts.
Change-Id: Iea23989ec2ab3ad7d1a57e2d1fb85163a6396024
This fixes a bug where the forgot pattern button wasn't working because
the logic for face unlock was interfering with determining the proper
backup to use.
The fix:
- adds a new state to SecurityMode so we have an initial condition
we can check for.
- passes the current mode to SecurityModel.getBackupSecurityMode() so
it relies on the current state.
- prevents face unlock from invoking callbacks that change state
once we're no longer showing face unlock.
Fixes bug 7346989
Change-Id: I4e64515efbbad712f11c820e690b458f352bf46c
Add Keyguard to list of windows that can't be hidden by keyguard.
Don't assign Configuration to window until layout has had a chance
to compare it to window's existing Configuration.
Bug: 7094175
Change-Id: I99a9fd4af9a31871fe130db7b6bdf49bd51a6092
-> Recovery button should only appear if account present
-> Recovery button should appear at bottom
-> Account view should have emergency call button
-> Account view should not show the clock / status area
Change-Id: Id12e8219f3fc6ecb14e82c5ec6ea4b3e28ed772d
-> Dealt with this NPE, and guarded against all related NPEs (which probably
can't happen, but given the stakes of a system crash, this is safer).
Change-Id: I3c207839ae0279033b6f3dad791d710b19415439
Now that we have a single stage unlock, there's no need for the transition. This
was causing unnecessary flickering to happen in views where we add the security view
just after inflation, which triggers the animation.
Fixes bug 7343632
Change-Id: I5bb8e37df66e4d96f00719e318424d46bf0e2e5a
-> When an unimportant message is set, we need to clear the security string
so that battery / owner info takes precedence at that point.
Change-Id: I3f86b0c2cc8fb2fb0023fce77a7725d8ada96d9e
Fix a bug where ordering during inflation caused us not to set a
keyguard callback early enough to properly modify window flags. Add a
gross hack to work around this for now.
Fix status layouts to scale a bit more gracefully in the presence of
an IME.
Fix password layouts to scale more gracefully in the presence of an
IME
Bug 7343312
Bug 7341795
Bug 7342963
Bug 7343089
Change-Id: Ifb2c06defef11e8f7f9d0e09855632ed491bb31c
Now that there isn't a swipe before launching face unlock, face unlock
needs to be suppressed during a phone call. If it isn't it will popup
on top of the phone call screen.
Change-Id: Id6c4165bf4df606ebf396c151f1c80603d5abca3
The code really shouldn't select the page until after the view has been
removed and had a chance to measure itself. The fix is to post a message
to select the correct widget page.
Bug 7334209
Change-Id: I5c2d59b00b3c502893da6000154ce6cdc79ecc1c
When we defer making the screen visible (waiting for the lock screen
to be ready) the screen may actually be on but covered by a black
surface. We need to make sure to ignore any touches on the screen
during this time until the black surface is about to be removed.
Bug: 7318962
Change-Id: I50eb7dcf05295cd276925625240996c4b80c5fe2
This change integrates the finalized tablet layouts for keyguard. It supports
both 7" and 10" tablets and makes some minor tweaks on phones.
Bug 7094419
Change-Id: I7b683382974de509e8045210544ea959db82e72d
1. If the global gesture to enable accessibility is enabled there should
be a haptic or auditory feedback after the global actions dialog pops up
as a result of a long press on power. On devices with no vibrator an
attempt to vibrate was performed evne if not hardware support exists
As a result no sound was played because the it was assumed a haptic
feedback was provided.
bug:7324903
Change-Id: Ic76db232d761a2899c1ca5f59ca55ff15ae575dd
