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.
Merge commit '794841710d11f59fd1736d1c889cc9b91f38f78e'
* commit '794841710d11f59fd1736d1c889cc9b91f38f78e':
Change EndCallBehavior while in UTS test mode.
Merge commit 'f010b5d26f1e1c93b93576995e76ffd63db2f96e' into eclair-plus-aosp
* commit 'f010b5d26f1e1c93b93576995e76ffd63db2f96e':
Change EndCallBehavior while in UTS test mode.
The minimum value varies from device to device, so this is useful for defining
the shortest and most efficient vibration. The VibratorService creates a Thread
when playing back vibration patterns, so this allows you to avoid thread creation
and associated scheduling delays by specifying a one-shot duration in the config
file.
When in UTS test mode this reverts the behavior
of the end key as it was in cupcake. When not in
UTS test mode the behavior is as before the change.
The UTS test mode is enabled when presist.sys.uts-test-mode is 1.
Bug: 2402366
Change-Id: I81359f3870a1e4da513f76c32aecdb7dfdf3bacf
- Added new PasswordEntryKeyboardView to internal/widgets. Widget supports:
- alpha mode with symbols (latin-1 only).
- a numeric keyboard
- IME emulation that applies keyboard input to arbitrary top-level view widget.
- Added new transparent assets to framework resources.
- Modified Keyguard and Keyguard layouts to use new PasswordEntryKeyboardView.
Shown whenever the secure lockscreen is (a) visible, or (b)
active but hidden due to a FLAG_SHOW_WHEN_LOCKED Activity.
Change-Id: I0e08a952904cc4728621953a42806edf26eb8e46
This allows the lockscreen to activate after the normal screen timeout while the
screen is on. Needed for dock apps, screen savers, etc.
Change-Id: I25c3579e4363c2b19d503fdbd45d2ff41cdd11bb
Signed-off-by: Mike Lockwood <lockwood@android.com>
This came down to a decision; if we want to show other information (owner id, current playing song, etc.)
as well as continue to have an easy way to silence the device, we need to have two unlock screens in these cases.
We simply don't have enough room on these screens to show anything but the unlock widget and a small bit of text.
This change *does not* affect pattern unlock, which will continue to be a single unlock screen.
Merge commit 'fe22c50410029eaf37f3e8e910a8c5fdd5769c70'
* commit 'fe22c50410029eaf37f3e8e910a8c5fdd5769c70':
Fix 2287263: Change carrier TextView to be 1 line and marquee if text is too long.
Merge commit 'f2be271d1dd84d09ee55041d61ac9b2b4ed4ba31' into eclair-plus-aosp
* commit 'f2be271d1dd84d09ee55041d61ac9b2b4ed4ba31':
Fix 2287263: Change carrier TextView to be 1 line and marquee if text is too long.
This is intended as a workaround for the long text lines introduced in https://android-git.corp.google.com/g/#change,38100.
Added explicit TextView.setColor() to workaround bug with TextView.setSelected().
