- remove redundant signals that were causing keyguard to be rebuilt unnecessarily.
- add a check to ensure we only handle configuration changes if the view is actually showing
- only reconstruct view if screen is turning off or if the configuration changes.
Change-Id: Ia9c7830e370feed6af36cc139d4cd3c5ca0be4fd
This maps activity on the SlidingChallenge to the security
challenge view. Currently it calls onPause() on the SecurityView
if the view is on the move or is hidden.
Change-Id: Ide5f2200e45d8996fa91af06ac2059c3d125ea6f
Integrate changes from prototype app
* Add callbacks for bouncer state changes
* Dismiss the bouncer if focus leaves the challenge area
* Increase edge swipe region, treat this as a slop for
SlidingChallengeLayout's drag handle. (This allows edge swipes in
the drag handle area to still page widgets instead.)
Change-Id: I732de1a8d999a34c7cc8aa8ed99e24b597f3444c
This means the visual glitch is possible again, but reduced since
the layout transitions are disabled.
It's more important to bring back nav buttons for incoming calls
(for the secure, screen off case).
Bug: 7411356
Change-Id: I83005a77930ec7f70a613b3396f85ab1a5fdd96c
Also pull the Klondike telephone exchange letter strings out
into arrays.xml so we can override it for specific locales.
Change-Id: Idf79ff8bfd53e5a8277271cc85ac7a1784ae3b64
The IME wasn't coming up in password mode because the base class always
returned 'false' for needsInput().
Change-Id: Ia5bf508b3e08fa6980e83103322711857af74680
Added a keyguardVisibilityChanged callback to indicate when the
keyguard is covered by something (alarm, phone, etc). Face unlock
doesn't start if it's not visible and it restarts appropriately when
it gains visibility again. This mostly fixes b/7362774 and b/7376783,
but there's some jank when face unlock goes away (if it was interrupted
while running).
Change-Id: I7bdf8ef6af687acaa7152d8e61bfdcc1979259ff
The show() method was calling onScreenTurnedOn() which attempted
to update the entire state.
Instead, show() should just ensure the current security screen
is showing.
This was causing some mischief in Face Unlock because onResume() was
being called multiple times.
Change-Id: I39682a213b1cc4dcf8133907b643028e844d0f47
Keyguard now disables all navbar buttons when turning screen off
instead of only recents.
Navbar is told about screen off/on and disables the layout transition
animation on screen off - if the user quickly turns the screen back
on they do not see the end of the fade out animation.
Bug:7377776
Change-Id: I96a050d58c6c9ce8537f50408655006fadbfcd4f
Bug: 7368245
Log a warning if the system process calls unqualified sendBroadcast()
and other calls.
As a result of the logging above, found a few more method calls such as
bindService() that would benefit from being more explicit to avoid
future confusion and reduce the log warnings.
Change-Id: I17f15c8be9adf7becd456d6abbab606f19befdbf
Specifically, this adds the following functionality:
- portrait layout on phones
- new KeyguardViewStateManager
- new SlidingChallengeLayout
- some event wiring.
Change-Id: Ie4491416f591b6d4002d33e9803a764a8ae730f6
This merges the changes from the proto app into the framework.
Basic functionality tested on phone in portrait:
- Slide
- Pattern
- PIN
- Password (wonky)
- SIM PIN
Change-Id: I21b2c30cf05dc01ffb20948f41a044e7af1db25f
Not very clean, this has a special hack in the window manager to
redo layout when a dream window is shown. After MR1 we should clean
this up (and the various other special dream hacks).
Change-Id: Ic1a5a2b10a0a07b4a5dccdbf0736b614ec06dd4a
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
