I6872c3ad135bc34348adafa76e08a3878f1b506f
"Add emergency call button to PUK'd lockscreen."
Bug: 2568732
I5ad8745443fc97225af9efb938e4640cfc29b5d7
"Restore text field used by sliding tab to give ringer
mode feedback."
Bug: 2587358
Change-Id: Ide3ad839aaf029930c0bf7ba4b9f6587efbd811d
Merge commit '7d8866f9ef026870d4735d6f2ede49525150e53e' into kraken
* commit '7d8866f9ef026870d4735d6f2ede49525150e53e':
Redo the look of the recent apps switcher.
This fixes a bug introduced in change 46594 that prevents showing
the tab unlock screen before PIN & password entry.
Change-Id: Ibd603921f6a22b603652c4751fa0f2f7d9129bb2
The emergency call button has been removed (since the user
can disable the keyguard, open the phone app, and enter the
emergency number there).
This change also restores a number of the informational &
help messages that were previously removed from the lock
screen.
Bug: 2421380
Change-Id: I4dda16be5d54c1e0ab4e26914c63d1f5b922cfe8
The emergency call button has been removed (since the user
can disable the keyguard, open the phone app, and enter the
emergency number there).
This change also restores a number of the informational &
help messages that were previously removed from the lock
screen.
(Requires I07bfc0f1c5b3f0e10b8cb72768848251439e19dd)
Bug: 2421380
Change-Id: I46a78c700427d769da6f7f2d3e9f419c2a921a61
do the long-press haptic feedback first, to avoid any slowdown
in the responsiveness of that.
Fixes http://b/2526697
Change-Id: I607063b67bdde92303ee112663b76d6e4e9a369b
The password unlock wasn't abiding by the 30s lockout rule.
This change adds the necessary logic and countdown timer to
disable text entry while in lockout mode. After 30s, text entry
is re-enabled until the next lockout count is reached.
Change-Id: I4d860565cad91cb88c36615b40d1837a5d97fe21
Added in I0e08a952904cc4728621953a42806edf26eb8e46, but
takes up too much room.
An undocumented system setting, "show_status_bar_lock", can
be set to 1 (e.g. in Spare Parts) to bring this back.
Bug: 2511090
Change-Id: I8869ac18c303a786eeb7f1a0c4ae08529b45d59c
This change removes the legacy notification of orientation and configuration changed events
from KeyguardUpdateMonitor and moves them into the individual activities. This was necessary
to guarantee order of events.
In addition, to minimize discrepencies due to notification lag, Keyguard screens (LockScreen,
PatternUnlock, etc.) are now responsible for handling onConfigurationChanged() notification and
forwarding them to LockPatternKeyguardView by a call to recreateMe() with the new configuration.
This also removes the hack that used to prevent drawing while the configuration was in flux.
Change-Id: I6b72e8c06cebb2c5c83e2debeb478e89b6f6f386
This is part 2 of the fix for bug 2364220 "Accessibility improvements for
ending calls".
This change updates the POWER key logic in interceptKeyTq() to check the
value of Settings.Secure.INCALL_POWER_BUTTON_BEHAVIOR, which allows the
user to specify that the Power button should hang up while in-call,
instead of just turning off the screen.
Bug: 2364220
Change-Id: If6d8e3155f7d60142ab6fd61f0a9db7f0b0d95ab
Now does lock screen and status bar management in the animation pass, to better
match actual changes on screen.
Change-Id: I9a68fcfa1968dfa71961bc164a6fda15b2cd7d47
Some devices have a qwerty layout without separate numeric keys. This makes PIN entry painful.
The workaround is to set an explicit numeric key listener when in numeric mode.
Previously, the battery percentage was only shown when the battery level
transitioned below the LOW_BATTERY_THRESHOLD (20%). This change makes it so it gets updated
whenever we get a battery status update where the level is below LOW_BATTERY_THRESHOLD.
Note: this only applies to the pattern unlock screen.
Added code to let us lazily re-create the unlock screen when the SIM
status changes. This fixes a bug where we sometimes show the Pattern/Password unlock
instead of the SIM PIN unlock due to an ordering issue with recent changes
to the telephony layer SIM update logic. It now correctly re-evaluates the SIM state
and updates the UI accordingly.
This makes the "Emergency call" button dual-purpose. If there's a call in progress,
the button will show "Return to call" and take them back to the call.
PasswordUnlockScreen was previously registering for multiple callbacks which *sometimes*
caused a memory leak because a reference stuck around in the callback list. I wasn't able to
track down the cause, but it looks like an interaction between switching between various lockscreen
modes and ordering of CONFIGURATION_CHANGED events.
I found one instance where the callback was being registered twice (fixed). However, I'm
still able to reproduce the bug but far less frequently.
As a workaround, I've added code to prevent adding additional callbacks and added logging to
detect when a callback is already registered.
Also fixed an instance where we'd recreate the password unlock screen in LockPatternKeyguardView.updateScreen()
so it should be quite a bit faster switching orientations now.
Renamed UnlockScreen.java to PatternUnlockScreen.java for consistency.
