| 4f5d1511b9123c342ba96fbd335f77749fde00de |
|
21-Jun-2012 |
Craig Mautner <cmautner@google.com> |
Make sure onScreenTurnedOn is called at power on.
KeyguardViewMediator.onScreenTurnedOn is not called if the device is
booted into the power-on state. In this case mScreenOn remains false
and the lockscreen will always appear after outgoing calls. This fix
ensures that onScreenTurnedOn is called when the device is powered
up in the on state.
Fixes bug 6709173.
Change-Id: I7557d8f002307b9125bc53b13bc3cb4c5c9b2758
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| c55b393efd462490cd5e27fc373bceafdd25662e |
|
05-Jun-2012 |
Jean-Michel Trivi <jmtrivi@google.com> |
Configuration for lock and UI sound levels
Define two integers in the platform configuration to
define the sound level for lock/unlock sounds, and
UI sound effects.
Use the corresponding value in KeyguardViewMediator for the lock sounds.
Use the corresponding value in AudioService when playing sound effects.
Bug 6448481
Change-Id: Ie238f5eb1645e395412864d93447ac4049f7e54b
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| c458ce98ce42c00b98afe00670f822814f3da572 |
|
30-Apr-2012 |
Jeff Brown <jeffbrown@google.com> |
Add support for using the lid switch to turn off the screen.
Added a config option to allow the lid switch to turn off the
screen. This is a closer match to what a lid switch should be
doing.
Removed an old feature to bypass keyguard when keyboard is visible
because the way it was plumbed in made bad assumptions about
the meaning of the lid switch. Also, the last product we shipped
that had a physical keyboard turned this config option off.
So away it goes. We can bring it back someday if we really want it.
It's questionable how useful the feature is anyhow, since it only
works when the keyguard is unsecure and when the lid switch is
unlikely to be jostled in the user's pocket.
Fixed a bug where we would tell the power manager that the keyboard
was visible even if the lid switch did not control the keyboard.
This used to cause the power manager to try to set the keyboard
brightness, which doesn't work.
Bug: 6377115
Bug: 6406726
Change-Id: Ic84b71d09563d51c92cd1cf132fa8bdee6509103
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 6d5176638c2189595cede38fb92c3e7e8700e221 |
|
24-Apr-2012 |
Eric Laurent <elaurent@google.com> |
system and UI sounds volume policy
Implement a more consistent policy for system and UI sounds (key clicks, lock/unlock,
camera shutter, DTMF, low battery...):
- All system sounds are played over STREAM_SYSTEM stream type.
- The STREAM_SYSTEM volume that was previously fixed now tracks the volume of a "master"
stream type. This "master" stream type is STREAM_RING for phones and STREAM_MUSIC for
tablets which corresponds to the stream whose volume is modified by default by the volume
keys.
- The STREAM_SYSTEM volume ranges from -24dB to -6dB (-24dB to -12dB over headphones) when the
"master" stream volume ranges from its min to its max.
- DTMF tones are played over STREAM_DTMF that tracks the "master" stream volume in the same
manner with the following exception: when in call, DTMF stream tracks STREAM_VOICE_CALL volume.
- Camera shutter sound is played over STREAM_SYSTEM_ENFORCED stream that tracks the "master"
stream volume except in countries where regulation enforces this sound. In this case
its volume is fixed and cannot be muted.
- Low battery sound is played over STREAM_SYSTEM and therefore has a tunable volume and is
heard while in call.
Issue 6344620.
Issue 6069229.
Issue 6213100.
Change-Id: I53a237878ead596e706c5dbbb1420e62cde32bd7
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| ff5b158f69bf453cf1fdedd175a09482c65f2bf2 |
|
13-Apr-2012 |
Dianne Hackborn <hackbod@google.com> |
Keep activities stopped while the lock screen is up.
Tell the activity manager when the lock screen is shown, so it
can keep itself (mostly) in sleep mode during this time, having
the foreground actvities remain in their stopped state.
Change-Id: I71c86d3298f23a98014d7ae36fd540c9df9a64e6
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| e9bdb31ea1dc3c1c2b1833a4bf0031d85928a45b |
|
06-Apr-2012 |
Jeff Brown <jeffbrown@google.com> |
Merge "Refactor input system into its own service."
|
| 4532e6158474a263d9d26c2b42240bcf7ce9b172 |
|
05-Apr-2012 |
Jeff Brown <jeffbrown@google.com> |
Refactor input system into its own service.
Extracted the input system from the window manager service into
a new input manager service. This will make it easier to
offer new input-related features to applications.
Cleaned up the input manager service JNI layer somewhat to get rid
of all of the unnecessary checks for whether the input manager
had been initialized. Simplified the callback layer as well.
Change-Id: I3175d01307aed1420780d3c093d2694b41edf66e
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 52c489cd63cca0361f374f7cb392018fabfa8bcc |
|
28-Mar-2012 |
Amith Yamasani <yamasani@google.com> |
Lockscreen settings per user
Move all lockscreen related settings to LockSettingsService.
LockPatternUtils uses this through IPC instead of Secure settings.
Migrate old settings to new database managed by LockSettingsService.
Passwords and patterns are stored in a new per-user location, except
for the primary user, for backward compatibility.
KeyguardViewMediator and LockPatternKeyguardView listen for changes
to user and updates the lockscreen.
Settings provider will look for Lock settings in the LockSettings
service now for the entries that used to be stored in Settings.
Change-Id: I956cd5b95e2d9d45a6401af7e270e6a5aa2dcc98
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| b030476d193a423f6c1baf3053f66fc768c925e0 |
|
14-Mar-2012 |
Jim Miller <jaggies@google.com> |
Fix 6021938: Improved target support in lock screen
This adds the ability to enable or disable target icons based on the drawable
resource of the target.
It also fixes a bug where we'd show the camera while displaying
the PIN/PUK unlock screen or when it's disabled by DevicePolicyAdmin.
Minor simplification and cleanup KeyguardUpdateMonitor callbacks.
Change-Id: I33fad56a2203bc8b7bcd0300c20478711a56713a
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| a4edd151c5266a2c794c95444fed67d19740cee3 |
|
07-Jan-2012 |
Jim Miller <jaggies@google.com> |
Fix 4560303: Add setting to lock later when power button pressed
This adds a feature to delay locking the device when the power button
is pressed. This fixes a use case where the user wants to turn off
the display (e.g. to save power) but doesn't want to lock the device.
For the case of a secure device (user has a pin/password/pattern),
this will lock the device immediately or not based on the setting.
For the non-secure case, this always "locks" the device to provide easy
access to the camera while preventing unwanted input.
Change-Id: Ie328485c3f7559e26896d761cbf0e69d3f4df4e2
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 43150bfa9377ca7a5fe0e6bfcdc04fb5807501f7 |
|
09-Nov-2011 |
Jeff Brown <jeffbrown@google.com> |
Wake on volume key when in dock.
Bug: 5580373
Change-Id: I847fb10b48c2e5e26cabefea1d630793efc32131
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 9fa1ada318ad9be0b43951b9d3c107b4e0bf345c |
|
01-Nov-2011 |
Jim Miller <jaggies@google.com> |
Fix 5497305: Make sure we show SIM unlock when "None" is selected
Previously the code ignored SIM state when lockscreen was set to "None."
It now properly accounts for the SIM state when deciding to show.
Change-Id: I272348c1a21b57ac146910850ea3db3adef0227c
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 19fa262c52ddaf0e5ec200f4f7f21bda0d4b617b |
|
14-Oct-2011 |
Martijn Coenen <maco@google.com> |
Merge "Send ACTION_USER_PRESENT when provisioning is completed." into ics-mr0
|
| dba935659024a9ca83cb6bd3f1a9970e277f7658 |
|
06-Oct-2011 |
Daniel Sandler <dsandler@android.com> |
Break apart DISABLE_HOME and DISABLE_RECENT.
Additionally, start using setSystemUiVisibility() where
possible in the keyguard to allow activities and dialogs to
re-enable some of the navigation keys (notably: home but not
recents).
Finally, stop disabling MENU for activities atop the keyguard.
Bug: 5380495 // no home in driveabout, clock
Bug: 5396134 // able to show home/recent in keyguard
Change-Id: I04eb224554ee8cff79476b85148c4cda75bb0b62
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 24d7b5f22ac98392f8b2d2c94560173e44d1ca6c |
|
11-Oct-2011 |
Nick Pelly <npelly@google.com> |
Send ACTION_USER_PRESENT when provisioning is completed.
This is needed for application to know when the keyguard becomes
unlocked, because isKeyguardLocked() is typically true while
provisioning (setup wizard), but ACTION_USER_PRSENT was
not sent when it transitions to false after provisioning.
Bug: 5436867
Bug: 5430833
Change-Id: Icae13ff9cab84774a002a426eb9cb353fa1dc530
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 8cb751b05a590a191ab4887567503269a475bbd6 |
|
01-Oct-2011 |
Amith Yamasani <yamasani@google.com> |
Tie the lockscreen sounds with the ringer volume.
Actual volume is a ratio of the ringer volume and drops along with
but slower than the ringer volume, so that at lowest ringer volume,
the lockscreen sounds are still somewhat audible.
Don't start the sounds if the ringer is muted.
Bug: 5394473
Change-Id: Ifcf242b3198b4ec8f12334e26ec23ebf05a96b83
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| d5545bd0a9efa65a8f7436205dd88965bc60192b |
|
29-Sep-2011 |
Marco Nelissen <marcone@google.com> |
Use SoundPool instead of Ringtone.
The lock screen was using Ringtone for the lock/unlock sounds, which
meant two new MediaPlayers were created every time a sound needed to
be played. In addition, the Ringtone was assigned to a local variable,
which means it could go be garbage collected and finalized while it
was still playing.
For short sounds that need to be played repeatedly, SoundPool is a
better option anyway, so use that instead.
b/5382634
Change-Id: I8794cbb24604fa7c03032bd5e32ceab37a858054
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| a2f00da374cd0d9776bc6c4e1cf3c3def990270b |
|
27-Sep-2011 |
Jim Miller <jaggies@google.com> |
am b4f0a9f3: Merge "Fix 5326463: rework sim state handling in lockscreen" into ics-factoryrom
* commit 'b4f0a9f3894c1f039168ad672f4aa194999c7cdd':
Fix 5326463: rework sim state handling in lockscreen
|
| 3f5f83b54fad4c797f5dbd75f050e4980e839122 |
|
27-Sep-2011 |
Jim Miller <jaggies@google.com> |
Fix 5326463: rework sim state handling in lockscreen
Previously it was possible to get an inconsistent state because there
were two paths that updated the lock screen sim state. This reworks
the data flow to ensure the same path is always used to update the state.
KeyguardUpdateMonitor now correctly updates the entire state of the callee
whenever a new callback is registered.
In addition, KeyguardUpdateMonitor now caches the phone state in order
to avoid a round-trip binder call in updateEmergencyCallButtonState().
This avoids a condition that could make lockscreen unresponsive while
updating the emergency call button state.
KeyguardStatusViewManager also ensures the TransportControlView is
hidden when created to ensure we don't inappropriately update the carrier
line while waiting for the first callbacks to update the status lines.
Change-Id: I6b3975b703a7d90bac8d0fe29fbc0f1d9c5e0e7d
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| e47e8520fa48bd014287eda94ea39927de73d6bc |
|
21-Sep-2011 |
Dianne Hackborn <hackbod@google.com> |
Keyguard sound needs to hold wake lock.
We need to hold a wakelock while playing the keyguard lock sound,
so that it actually completes before the CPU goes to sleep.
Change-Id: I144c345383afeb911ea461b2eb17b31183b6d092
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 38e29a61d0c87fe3e391d24e2eb11dd1800d107d |
|
18-Sep-2011 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #5242779: Device not responding to touch on unlock screen
Rework how we decide when it is okay to turn on the screen by having
the policy call back to the power manager when it knows the lock screen
has been drawn.
Change-Id: Ie8f3f72111dcf7f168723e6dce24e0343b4afe5d
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 4519a02608b9e02a2c0dbc7dff37c21167db8f24 |
|
08-Sep-2011 |
Jeff Sharkey <jsharkey@android.com> |
Always disable() through SBMS; watch date.
Touching StatusBar.disable() directly can make the cached value over
in StatusBarManagerService stale. Instead, dispatch DISABLE_BACK
through setSystemUiVisibility() on tablets; it's unused on phones.
Also DISABLE_NOTIFICATION_TICKER when showing secure lockscreen, and
watch for TIME_CHANGED in DateView.
Bug: 5255469
Bug: 5242677
Change-Id: I4efaf9799b2f229f49d7024da5dafceacd5e08bb
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 054340d0a3f242efeaf898cca38625bdcb3b4b5a |
|
02-Sep-2011 |
Jeff Sharkey <jsharkey@android.com> |
Show statusbar clock based on lockscreen status.
Keep track of lockscreen clock visibility, and only hide statusbar
clock when one is provided by lockscreen. This fixes bug where widget
would hide all clocks.
Bug: 5242065
Change-Id: I48de98ecb956c7f22bd40b54d771c78c1a80c14c
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| e3646dd8d96fb9756c8a7a4757ad5277e3801aed |
|
01-Sep-2011 |
Mike Lockwood <lockwood@android.com> |
Show back button in status bar when in an activity in front of the lockscreen.
When the lockscreen is up we still enable the home and recent app buttons,
but the back button is only enabled if the lockscreen is not obscured by other activities
Fixes problem escaping from the DeskClock app when the screen is locked.
Bug: 5206013
Change-Id: I68c9e4513018f51e2ee4fc11254e42ecbef834e4
Signed-off-by: Mike Lockwood <lockwood@android.com>
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| f52c70b2ccf711f507723bc74a68ca8c3a12c57a |
|
31-Aug-2011 |
Jeff Sharkey <jsharkey@android.com> |
Disable clock in lockscreen; better flag logic.
When showing lockscreen, hide clock and navigation. Clean up logic
to be easier to understand.
Bug: 5112812
Change-Id: I20e3563aa36644db678c7839d47f01f223fe8d37
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 29aae6f36e565b8f2a99f2193597b964bb800ee8 |
|
19-Aug-2011 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #4279860: previous UI flashes before showing lock screen...
...(when turning display on after recently turning it off)
Also clean up when we decide to turn the screen on to improve that
transition. There are still problems here with turning it on
before the wallpaper gets dispayed.
Change-Id: I2bc56c12e5ad75a1ce5a0546f43a845bf0823e66
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 661cd52e0e1d527132eb1cae604d3e64da7ec0cb |
|
22-Aug-2011 |
Dianne Hackborn <hackbod@google.com> |
Add progress dialog for booting after an upgrade.
This introduces a new facility for code during the boot process
to display messages to the user through a progress dialog. This
is only for use when performing longer-than-usual post-upgrade
operations such as running dexopt on applications or upgrading
databases.
Change-Id: I0e78439ccec3850fb67872c22f235bf12a158dae
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 130453c2eb615bb8cc51a26afbd40822a72636c1 |
|
18-Aug-2011 |
Daniel Sandler <dsandler@google.com> |
Fix DISABLE_EXPAND in the tablet status bar.
The codepath that honored this flag had been routed around
when notification peeks were disabled. (The bug was allowing
notifications to be accessed from a secure lockscreen.)
Bug: 5173959
Change-Id: I35dee343ee4f0288530580054f8bb9f511ebe6af
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 8b08b88640e1f847d4890399f236b434b08921c0 |
|
12-Aug-2011 |
Daniel Sandler <dsandler@android.com> |
Properly disable status bar on secure lockscreens.
(Broken implementation appeared in change I967e455.)
Bug: 5158885
Change-Id: I0e22c269ff76d19bcdd5e51e1722e34fdc025dfa
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 74d188c91134a255005c392770ad80d8c44e3c0c |
|
10-Aug-2011 |
Daniel Sandler <dsandler@android.com> |
Initial support for notification panel access in keyguard.
The special touch target and fancy animations (see bug
5052059) aren't there yet; we'll probably need a different
flavor of DISABLE_EXPAND to specify that state. But this is
a start and should get the basic feature into testers'
hands.
Bug: 5052059
Change-Id: I967e4557e467d1762d6566643bb401eb84f94e92
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| f3447351f7571b5ab3c2a59832d9497bde4f6776 |
|
07-Aug-2011 |
Jim Miller <jaggies@google.com> |
Fix 5125978: remove lockscreen logspew
Change-Id: Iefa103e867e870dfe587271e0555404589d9e5b3
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 6179ea3196e9306d3f14361fe9ef14191b1edba6 |
|
28-Jun-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Adding accessibility support to the Status Bar.
1. Added content description to pretty much all animals
in the zoo including buttons in the navigation bar,
notifications and status icons for battery, signal,
data, etc.
2. Rectored to avoid ovelaying views since they block
touch exploratino. In general overlaying views
cause trouble for touch exploration and accessibility
in general.
3. Avoid sending accessibility events in case the user is
touching outside of the StatauBAr panels to avoid
confusion.
4. Added records to accessibility events in the places where
this would help the presentation. So the event comes from
a given "leaf" view and its predecessor is adding a record
to the event for itself to provide more cotext. It is up
to the accessiiblity service to choose how to present that.
bug:4686943
Change-Id: I1c1bd123d828fb10911bca92130e9a05c1f020b3
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 5f81f1bcd9cdb15411bd4bb036b75ee6e822b8bf |
|
14-Jul-2011 |
John Wang <johnwang@google.com> |
am 74c425d3: am 54b2a326: Merge "Show SIM blocked after 10 time puk wrong entries." into honeycomb-LTE
* commit '74c425d3e95ed0f47b1a5d447007886d01d7ff56':
Show SIM blocked after 10 time puk wrong entries.
|
| 98c3fcc7afe34966c3608ec9283794a177ed902b |
|
08-Jul-2011 |
John Wang <johnwang@google.com> |
Show SIM blocked after 10 time puk wrong entries.
After user enters 10 time wrong puk in puk unlock screen,
device need show the SIM permanently disabled message
is in lock screen.
bug:4905509
Change-Id: I06242834972b3f403cfe99a2edd8bae47d7ed474
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 1766974b02a1accf6b0b553e3e7239b7c8416199 |
|
16-Jun-2011 |
John Wang <johnwang@google.com> |
am 03cbb58e: am ff42c04d: Merge "Support SIM permanently disabled state." into honeycomb-LTE
* commit '03cbb58e2418dc22ae18a8648404382da4ee46e8':
Support SIM permanently disabled state.
|
| b0b24b3df50988d23f571b83d829fecc986ec497 |
|
11-Jun-2011 |
John Wang <johnwang@google.com> |
Support SIM permanently disabled state.
SIM card can get permanently disabled due to too many
PUK retries. The PERM_BLOCKED pin state of SIM application
represents this state.
This change decodes permanent disabled state and broadcasts it
via ICC_ABSENT intent with PERM_DISABLED reason. It also update
the lockscreen to show the prompt message.
bug:4392059
Change-Id: I5e60dd65f48f42aa2e54db4cdebf803d6e666b99
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 43a17654cf4bfe7f1ec22bd8b7b32daccdf27c09 |
|
07-Apr-2011 |
Joe Onorato <joeo@google.com> |
Remove the deprecated things from Config.java. These haven't been working since before 1.0.
Change-Id: Ic2e8fa68797ea9d486f4117f3d82c98233cdab1e
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 56194ebec6212e229f4ccdaa4b187166d20013ef |
|
03-Mar-2011 |
Jeff Brown <jeffbrown@google.com> |
Wake screen from external HID peripherals.
Added some plumbing to enable the policy to intercept motion
events when the screen is off to handle wakeup if needed.
Added a basic concept of an external device to limit the scope
of the wakeup policy to external devices only. The wakeup policy
for internal devices should be based on explicit rules such as
policy flags in key layout files.
Moved isTouchEvent to native.
Ensure the dispatcher sends the right event type to userActivity
for non-touch pointer events like HOVER_MOVE and SCROLL.
Bug: 3193114
Change-Id: I15dbd48a16810dfaf226ff7ad117d46908ca4f86
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| a924dc0db952fe32509435fdb8dc9c84a9e181f3 |
|
17-Feb-2011 |
Dianne Hackborn <hackbod@google.com> |
Start window manager refactoring.
Move all of the pieces into a new com.android.server.wm package.
Change-Id: I942b7bcfb84ee0f843f47d58e55ffc5a93c0da94
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 77274695a724eefe70c63a5d8bbdf77bd89b748b |
|
18-Jan-2011 |
Jim Miller <jaggies@google.com> |
Fix 3210299: Extend lock screen wake timeout to 10s
Change-Id: I9e4f8761a80271b97ff6411a41664642273baaef
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 3e8f5a2c1beb4b918856063880e05125946e4347 |
|
03-Dec-2010 |
Daniel Sandler <dsandler@google.com> |
Hide navigation buttons and clock on lockscreen.
(This introduces a StatusBarManager disable flag to ask the
status bar to hide just the clock, which might be useful in
other situations, such as clock/dock apps.)
Bug: 3130393
Change-Id: Ia08627508518e2ed3713ffbf856e4ec42952b3a8
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 2a98a4cbaaf3300036434dd1d44b891ea8a8c932 |
|
20-Nov-2010 |
Jim Miller <jaggies@google.com> |
Fix 3024522: Add "no lock screen" support to the framework.
This adds a new feature where LockScreen can be disabled to
allow the device to go straight to the home screen when
powered on.
Change-Id: I288e8d5359442c042ae7911340885877a864faff
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| b0418da0e7594a8c2164a46985c5f1993632e010 |
|
01-Nov-2010 |
Jeff Brown <jeffbrown@google.com> |
Add plumbing for volume mute key.
Full support for the volume mute key will be implemented in a
later change.
Bug: 2912307
Change-Id: I98c27d6360f159c8b7447e04b45f442eff87b38a
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 4d396052deb54399cbadbeb8abd873df6f3af342 |
|
30-Oct-2010 |
Jeff Brown <jeffbrown@google.com> |
Fix policy issues when screen is off.
Rewrote interceptKeyBeforeQueueing to make the handling more systematic.
Behavior should be identical except:
- We never pass keys to applications when the screen is off and the keyguard
is not showing (the proximity sensor turned off the screen).
Previously we passed all non-wake keys through in this case which
caused a bug on Crespo where the screen would come back on if a soft key
was held at the time of power off because the resulting key up event
would sneak in just before the keyguard was shown. It would then be
passed through to the dispatcher which would poke user activity and
wake up the screen.
- We propagate the key flags when broadcasting media keys which
ensures that recipients can tell when the key is canceled.
- We ignore endcall or power if canceled (shouldn't happen anyways).
Changed the input dispatcher to not poke user activity for canceled
events since they are synthetic and should not wake the device.
Changed the lock screen so that it does not poke the wake lock when the
grab handle is released. This fixes a bug where the screen would come
back on immediately if the power went off while the user was holding
one of the grab handles because the sliding tab would receive an up
event after screen turned off and release the grab handles.
Fixed a couple of issues where media keys were being handled inconsistently
or not at all, particularly in the case of the new PAUSE, PLAY
and RECORD keys.
Bug: 3144874
Change-Id: Ie630f5fb6f128cfdf94845f9428067045f42892c
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| a6face4d40280067c6c829c8c186fc47969e7b7b |
|
25-Oct-2010 |
Marco Nelissen <marcone@google.com> |
Plumb KEYCODE_MEDIA_PAUSE and KEYCODE_MEDIA_PLAY up through the framework.
b/2764237
Change-Id: I9a20974fa0b7527230258f7d0bf829a031673a9d
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| 385a753dead6ef15f2e30eae47f73e642b3ef7ed |
|
21-Oct-2010 |
Brad Fitzpatrick <bradfitz@android.com> |
resolved conflicts for merge of 368fdba4 to master
Change-Id: I42b7b433c86a71a5da5db67109f056a280077c9d
|
| 431bb2269532f2514861b908d5fafda8fa64da79 |
|
19-Oct-2010 |
Joe Onorato <joeo@google.com> |
Reduce logging.
Remember, the system and main logs are
- Shared resources
- Primarily for recording problems
- To be used only for large grained events during normal operation
Bug: 3104855
Change-Id: I136fbd101917dcbc8ebc3f96f276426b48bde7b7
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| bc4603b0b1f1242387655274e39649882ca391d1 |
|
31-Aug-2010 |
Jim Miller <jaggies@google.com> |
Fix 2579224: Add a separate timeout for lockscreen vs display
This change adds a second timeout to the SecuritySettings page
separate from the standard display timeout.
Change-Id: I41fe10e31688308f52695ad3ee30a4b0507112bd
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|
| be81f4f15dad6d690efcab1973d1e174ce3b001b |
|
15-Jun-2010 |
Brett Chabot <brettchabot@android.com> |
Move out all framework-tests classes.
Previously tests/framework-tests contained a quarantined set of test classes
that needed access to package-private framework api. Running these tests
normally would cause the dalvik verifier to throw errors.
runtest now has support for turning off the dalvik verifier for frameworks
tests, so move this tests into their recommended location, close to the source
being tested.
Also move policy source into a 'src' folder to accommodate the tests move.
Change-Id: I62f839da185a55bc553b653bf583fd99da438512
/frameworks/base/policy/src/com/android/internal/policy/impl/KeyguardViewMediator.java
|