| 45308b1b3b1582d048845df2ee5301241e52a5cf |
|
19-Jun-2012 |
Jim Miller <jaggies@google.com> |
Fix 6667238: allow market apps to support ACTION_ASSIST
This change allows market apps and 3rd parties to supply an activity
that responds to ACTION_ASSIST (e.g. market apps).
It also adds a test app to respond to the ASSIST intent and force
the intent disambiguation dialog to appear.
Change-Id: I5a78863c6a9546d18c66275187d178f6a1c9ee17
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 20039ad17b94873ee40fdd61c3d1d1aa590010df |
|
16-Jun-2012 |
Jim Miller <jaggies@google.com> |
Fix 6665117: ACTION_ASSIST visual improvements
- add generic icon for search providers that don't supply one
- change alpha weighting factor for glow
- don't show ring background
Change-Id: I86c86dc2d623c25ec7b91e206fac8ad9cd60faac
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| de7a8ead2467a4a152a5a9b2416c8048f1b48bbb |
|
14-Jun-2012 |
Jeff Brown <jeffbrown@google.com> |
Add new ASSIST key and map it to the global assist intent.
Moved some duplicate code from SearchPanelView and LockScreen
over to SearchManager to avoid creating yet another copy of it
in PhoneWindowManager.
Bug: 6594275
Change-Id: Ib4ebcd6817639d17548952ab2ce7cb876c05777c
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 955a016922ea49f154d190b054a202559b41a4d3 |
|
12-Jun-2012 |
Jim Miller <jaggies@google.com> |
Fix 6613962: Update keyguard to use new GlowPadView UX design.
Change-Id: I4f1ef3107e5550f7df9dcb412943a84b66432b7d
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 3294b6b09b2f52cb44005720051c32c9c851fc9f |
|
01-Jun-2012 |
Jim Miller <jaggies@google.com> |
Fix 6592932: add means to replace assist icon from given package
This provides the means to replace the assist icon shown in keyguard and the
navigation gesture for assist. It's done by adding metadata called
"com.android.systemui.action_assist_icon" to the activity that handles
android.intent.action.ASSIST. It should point to a StateListDrawable
in that package with the required states. For example:
<meta-data android:name="com.android.systemui.action_assist_icon"
android:resource="@drawable/ic_android_systemui_action_assist" />
And then something like this in drawable/ic_android_systemui_action_assist.xml :
<selector xmlns:android="http://schemas.android.com/apk/res/android">
<item android:state_enabled="true"
android:state_active="false"
android:state_focused="false"
android:drawable="@drawable/ic_action_assist_normal" />
<item android:state_enabled="true"
android:state_active="true"
android:state_focused="false"
android:drawable="@drawable/ic_action_assist_activated" />
<item android:state_enabled="true"
android:state_active="false"
android:state_focused="true"
android:drawable="@drawable/ic_action_assist_focused" />
</selector>
Change-Id: Ibc29360e179fed68253ff06a07b1bb2b982d0dab
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 998bb765290066822ff8a3b378dadd71deb0ce73 |
|
21-May-2012 |
Jim Miller <jaggies@google.com> |
Fix6398209: reveal search when home button is long-pressed
This change add a feature to reveal the swipe to search interface
when the home key is pressed for longer than 50ms. It progressively
reveals the interface. It still requires a bit of tuning, but all
the basic parameters are in this CL.
Change-Id: I1d3a5bb7b912265eb41da68bc9313eee1af2e415
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 12e0c5ac1b837d85c78221108b0d70417199bbbb |
|
17-May-2012 |
Jim Miller <jaggies@google.com> |
Fix 6504124: Disable assist when ACTION_ASSIST is not available
Change-Id: I2218afa7954961309d8cf2f2be0aff10826b9243
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 8818edbe2f5bef9cf161ef57e9296ff302ad44f6 |
|
12-May-2012 |
Jim Miller <jaggies@google.com> |
Fix 6485058: remove OnTriggerListeners from Wave*Methods in cleanup
This fixes a rare crash that could happen when the device orientation
changes while the handle is held over a target. LockScreen.cleanUp()
was being called which set mCallback to null which then causes it
to crash in MultiWaveViewMethods.onTrigger().
The solution is to also remove OnTriggerListeners in LockScreen.cleanup().
Change-Id: I487c7c9dbbe40417e685b39f2e79b1c43b30fa00
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 4c351d62e7a09bcc29e7d0329bcdd947a302cf40 |
|
11-May-2012 |
Jim Miller <jaggies@google.com> |
Fix 6040870: Update MultiWaveView for new device
This change allows more flexibility in target placement in MultiWaveView.
It now supports a new way of specifying chevron drawables that allows
them to be moved in directions corresponding to more than the four basic
directions (right, up, left, down).
Chevron drawables can now be updated in an overlay.
This change also adds a place holder and makes a minor tweak to the layout
on 720dp devices where the navbar buttons weren't centered.
Change-Id: Icd319ec5f276870380e27737c873e78f599ff751
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| bffc3d1bd33eb2d8e00a9f8b6261d815db503311 |
|
08-May-2012 |
Eric Laurent <elaurent@google.com> |
Silent and Vibrate mode clean up
Clean up related to new Vibration policy.
The vibrate behavior is now only derived from:
- presence of a vibrator on the device
- current ringer mode selected: NORMAL, VIBRATE or SILENT
If no vibrator is present the ringer mode can only be NORMAL or SILENT.
The control of ringer mode via volume keys when volume keys control the "master"
stream type (RING on phones, MUSIC on tablets) is as follows:
If a vibrator is present:
VOL- and volume equals 1: NORMAL => VIBRATE
VOL- and volume equals 0 and not continuous press: VIBRATE => SILENT
VOL+ and in SILENT mode: SILENT => VIBRATE
VOL+ and in VIBRATE mode: VIBRATE => NORMAL, volume = 1
If no vibrator is present:
VOL- and volume equals 0 and not continuous press: NORMAL => SILENT
VOL+ and in SILENT mode: SILENT => NORMAL, volume = 0
VIBRATE_ON and VIBRATE_IN_SILENT settings are not stored/retreived any more.
AudioService checks and corrects ringer mode and stream volumes if necessary when reading from
DB at boot time.
Also:
Added dump for stream volumes in AudioService.
Added device names missing in AudioSystem for USB accessory and USB device.
Issue: 6036529
Issue: 6414950
Issue: 6448163
Change-Id: I77fb821ec63e4e566320cac2701b4ac466e86aef
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 0799440ab3ce50ffa6acb762cb7677abdffb3f74 |
|
02-May-2012 |
Jim Miller <jaggies@google.com> |
Fix 6414061: Add new ACTION_ASSIST intent.
Change-Id: I3d334f67723ac89f6001267e0f06ad76190b929f
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.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/LockScreen.java
|
| c00fd7ab302198635885c1e090b41e3d11adc8ea |
|
23-Mar-2012 |
Jim Miller <jaggies@google.com> |
Fix 6216452: Add search target to lock screen
Change-Id: I0784e844fb8e1f904f37d2572c6ddbd6c22e95d1
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.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/LockScreen.java
|
| 75e1ce63353efe93a56dba3fff8d9f9134475163 |
|
29-Feb-2012 |
Wu-cheng Li <wuchengli@google.com> |
Use SINGLE_TOP and CLEAR_TOP when starting camera from lock scren.
Add these flags so there is no need to press back key twice to
exit the camera if users slide to camera twice.
bug:6070281
Change-Id: Iadf6ab2798cf9381bc9dc761920f46b022fb6bb8
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 3868cee0b9306644b250d3cd78b1be7af70abf68 |
|
24-Jan-2012 |
Jim Miller <jaggies@google.com> |
Fix 5907237: dismiss keyguard after the camera app launches.
This fixes a bug where either the home screen or the last app run shows
briefly while we wait for the camera app to launch. Instead, we have
ActivityManager dismiss keyguard once the camera app is up and running.
Change-Id: I1c2986ad84024dce675216a76c19c937c3e2828d
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| b75783571b2b51357f97407903b2fda9534f91f9 |
|
08-Nov-2011 |
Wu-cheng Li <wuchengli@google.com> |
Change slide-to-camera intent to INTENT_ACTION_STILL_IMAGE_CAMERA.
ACTION_CAMERA_BUTTON is for camera hardware button. Change the
intent to INTENT_ACTION_STILL_IMAGE_CAMERA.
bug:5572158
Change-Id: I49ffbf50ecd4458065ee1c2d1fdab8d9e696a1a8
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| ebcd6bb1b9ac5f898621ba25c37f2e3ccd2ff33b |
|
22-Sep-2011 |
Adam Cohen <adamcohen@google.com> |
Fixing emergency dialer flicker on lock screen (issue 5314293)
Change-Id: Ia9bf4acb84923e200b89ee55fc53bc92877001cf
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| cd2bad41afdf7c112b66a436562d080f3b99af1b |
|
18-Aug-2011 |
Jim Miller <jaggies@google.com> |
Fix 5149726: Add slight delay to initial lock screen 'ping' animation.
This adds a slight delay before the first ping animation runs. The
idea is to ensure enough time for the display to come on and the user
to notice the animation.
Change-Id: I3d981f5d50efa14683bb08cf6a1430244ce67e55
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| be8d1cf1ac9fc514fb0cc2e8ef4a85beb0197fa0 |
|
05-Aug-2011 |
Jim Miller <jaggies@google.com> |
Fix 5045008: replace "ring/silence" target in LockScreen with camera app
This change replaces the ring/silence target with a camera target. It
is disabled and falls back to the old behavior when any device policy
disables the camera.
Updated with latest icons.
Change-Id: I2374eba08f85ff1d1b0bad2859efa30bb166fb60
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 6b05d58018c2806459c121e507c005639b74aee9 |
|
18-Jul-2011 |
Jim Miller <jaggies@google.com> |
Fix 5044158: Initial pass: add music transport controls to LockScreen
Refactored all lockscreen notifications to go through new KeyguardStatusViewManager.
This is required to intercept messages originally intended for separate TextViews that
are now shown in a single view when showing the transport control view.
Refactor EmergencyCallButton to be handled by common code in KeyguardStatusViewManager.
First pass at LockScreenWidgetCallback for LockScreen "widgets" to send events back to LockScreen.
First pass at LockScreenWidgetInterface, which will be required of Views that want to be rendered on
LockScreen.
Added place-holder TransportControlView until the real one is ready and integrated it into GridLayouts.
Ensured emergencyCallButton is in all views, even if not shown since some devices may lock the user
out if certain criteria isn't met (missing SIM, etc).
Refactored layouts and removed keyguard_screen_status*.xml since layouts are all over the map and
no longer make good use of a shared layout for this.
Minor tweak to MultiWaveView to fix layout issues when placed in GridLayout where the measurement
was being calculated improperly.
Moved EmergencyCallButton to bottom of view where we can.
Removed unused Alpha keyboards from tablet password unlock layouts.
Removed unused views (status2, emergencyCallText screenLocked) from layouts and made common views have common names.
Fixed bug with MultiWave layout in landscape where array was shown in wrong orientation.
Separated clock colors for phones/tablets since they're now different.
Converted remaining phone layouts to use GridLayout.
Start routing audiomanager events to lockscreen views.
Move emergency call button handling to KeyguardStatusViewManager.
Change-Id: I480b0346cfe19aad316fea0c0aaabf8862693636
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 1c8d207201150c29ac92c424e1320c715a64b5bc |
|
30-Jun-2011 |
Jim Miller <jaggies@google.com> |
Fix 4691563: Polish MultiWaveView experience in LockScreen and InCall screen
Better activation experience:
- Hold off on switching out targets until current animation has finished.
- Hide unselected targets when a target is selected.
Code simplification:
- Use explicit callback objects to handle animation updates instead of having MWV implement the interface.
- More compact chevron-loading code.
- Don't use animations for properties that need to change immediately.
Other minor timing tweaks.
Change-Id: I328533e8ab7b4c69c7ba51c8c55002765dcbbd46
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.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/LockScreen.java
|
| 7c1650d180e536ce6b5f2fa7423abbbe7dcb08cd |
|
14-Jun-2011 |
John Wang <johnwang@google.com> |
am aabe5f46: am 49572479: Update sim missing message in lock screen.
* commit 'aabe5f46846a45163be874dca2d19910ce38c232':
Update sim missing message in lock screen.
|
| 70832a3d77d90f09fb7ba27612c9cbec6a92abe6 |
|
14-Jun-2011 |
Jim Miller <jaggies@google.com> |
Some tuning for MultiWaveView animations and assets:
- allow individual chevrons to be specified for (top, bottom, left, right).
- move ring to pressed position (currently w/o animation)
- add top/bottom chevron handling and refactor code accordingly.
- constrain drag handle to the ring
Change-Id: I859b2d03d8f0397c68b87a8ee15df20d55c9552c
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 49572479a9cb479f2b323f011c1a9f8142ec1a46 |
|
14-Jun-2011 |
John Wang <johnwang@google.com> |
Update sim missing message in lock screen.
Update SIM missing message to include SIM corrupted situation.
bug:4392059
Change-Id: Icf2f8d801a2e2761a309442209118a6a71a4c633
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| b505074e8273887fbcd1e933738a42e770085fb8 |
|
09-Jun-2011 |
Jim Miller <jaggies@google.com> |
Add new MultiWaveView widget and integrate it into LockScreen
This adds a new multi-target widget to the framework and integrates
it into LockScreen.
Now with updated assets.
Change-Id: Ib41595b9e80a7be6d647f44c803a77f9e5bfeca9
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 5328bf0b2e62c2719daf9154edbe81fd819974a6 |
|
09-Jun-2011 |
John Wang <johnwang@google.com> |
Set emergency call text visibility.
Set emergency call text visibility based on
emergencyCallCapable config for sim missing
and networklock screens.
bug:4392059
Change-Id: Ibfe92405ada7b452927940295c090d88ecd79519
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 0f7b3f8ba5c2f0b8f96e072bd866c9fb374ebdeb |
|
31-May-2011 |
John Wang <johnwang@google.com> |
Add SIM PUK unlockscreen.
Puk unlockscreen is implemented as SimPukUnlockScreen.
Added config_enable_puk_unlock_screen to control the display of puk unlock screen.
Using config_voice_capable to control the display of emergency call button.
bug:4384956
Change-Id: I2b8256b4ecdf3d4f1e85c4e868fac1810cfd29be
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 1b365921e88b14857d8e0826e221c371d25f6cb2 |
|
10-Mar-2011 |
Jim Miller <jaggies@google.com> |
Fix 3201849: Enable hardware acceleration in LockScreen WaveView [DO NOT MERGE]
Change-Id: I07bbed7843857158cd2c1ffd9b184bde7fd5860d
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| a55c1280f9b674619368ee61e4fe6b8db64eb2ce |
|
17-Jan-2011 |
Jim Miller <jaggies@google.com> |
am 057d9f16: Merge "Fix 3342063: Correctly update StatusView when battery changes." into honeycomb
* commit '057d9f16f793c3796751913ad2eeb12582a7626b':
Fix 3342063: Correctly update StatusView when battery changes.
|
| fc5001a5926495182e49408391b84172fb8f7915 |
|
17-Jan-2011 |
Jim Miller <jaggies@google.com> |
Fix 3342063: Correctly update StatusView when battery changes.
LockScreen wasn't correctly updating StatusView when the battery
status changed. In addition, the messages aren't supposed to
"pop" when changed, so changed visibility state from GONE to INVISIBLE
when not in use.
Change-Id: Icacbf7e2275c77a28e7e0a9d1247abdbebadcd4f
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 3530ebe451fea39b159baa9b8c9f9cd851de42a3 |
|
17-Jan-2011 |
Jim Miller <jaggies@google.com> |
resolved conflicts for merge of 578e73da to honeycomb-plus-aosp
Change-Id: I334ae5382220a84881521885b6e3c3991fd8bbb0
|
| 8b886fab5496b0b1f5193f21855220176deddc37 |
|
14-Jan-2011 |
Jim Miller <jaggies@google.com> |
Fix 3106227: use WeakReferences for receivers in DigitalClock class
This works around a bug in the framework where LockScreen wouldn't
get GC'd under certain circumstances which would lead to an OOM
crash. It now uses WeakReferences for observers inside the
DigitalClock container class and unregisters them if the containing
DigitalClock goes away.
Also removed mLive variable which was unused and could potentially
leak the receivers.
Left mAttached for debugging so we can use it to determine if the
calls to onAttachToWindow() and onDetachFromWindow() are grossly
unbalanced which may be the root cause of the original problem.
Have cleanUp() explicitly clear unused references to make
tracing through hprof references easier.
Change-Id: I99a7e0c356001b05eab5aa729564553666febfea
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 3b4fcbc9f13bab6a2e9e5c37cc5e18fec7341c04 |
|
09-Jan-2011 |
Brett Chabot <brettchabot@android.com> |
Add ActivityManager#isRunningInTestHarness() public API.
Replaces use of ro.monkey system property. This new API is controlled by
ro.test_harness.
Bug 3329873
Change-Id: Idb5bbbd9ca691976ef842eec681be34c29915976
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| b450a65c1c833e40d8c85a7670ed64f8be34102b |
|
07-Jan-2011 |
Jim Miller <jaggies@google.com> |
Fix 3330653: Update lockscreen layouts to match latest mocks [DO NOT MERGE]
This change list:
- simplifies the UI design to reduce the number of
on-screen items by combining Alarm status with the date line.
- updates many of the layout files to match closer to the
final design.
- Simplifies the logic for showing Status1 info. It's now
more predictable and robust.
- updates the layout for tablets
- contains a modified alpha to work well with different backgrounds
(Tested: white, gray, and dark backgrounds)
- updates the tablet icons to something closer to the final size.
Manual merge from Change-Id: Ifb349dfa778e9c91b0649c8d95229607be5af8e5
Change-Id: Ia2a9a2d285102d0208b3a7fcead58d6454d116ae
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| eb9f7a01b0f501a535d872a957c1102ebb13d1c7 |
|
30-Oct-2010 |
Jeff Brown <jeffbrown@google.com> |
Fix policy issues when screen is off. (DO NOT MERGE)
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.
Bug: 3144874
Change-Id: Iebb91e10592b4ef2de4b1dd3a2e1e4254aacb697
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 0c91a8ee9321da4dee17f0aeffbc20b0c5bb0644 |
|
02-Nov-2010 |
Jim Miller <jaggies@google.com> |
Minor tweaks to lockscreen animation:
Remove transition delay to show home.
Add new constants to allow finer tuning of "success" animation.
Transition all items to transparent on successful unlock.
Change-Id: Id9f57b9bfc08be840d9282f987925617d2b42ea1
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.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/LockScreen.java
|
| 4139b5505c1e07c56900aa72dd91a01e6b740f5f |
|
08-Oct-2010 |
Jim Miller <jaggies@google.com> |
Fix 3061025: Extend wave lockscreen timeout while grabbed.
This fix extends the lockscreen timeout to 30s while the
handle is being held. As a precaution, it will still timeout
after 30s of not completing the lock. Once the handle is
released, the screen will go dark after 5s, which gives
it enough time to finish pending animations.
Change-Id: Ie89449b6b09de06ca8a88702cc85085b2556903c
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 3060421045d4d9e411797f91bb509824b03e33fb |
|
23-Sep-2010 |
Jim Miller <jaggies@google.com> |
Add new WaveView widget to framework and integrate into LockScreen.
This adds a new "Energy Wave" widget to the internal widgets and
integrates it into LockScreen.
ValueAnimator needed a slight modification since it expects to
be run inside of Activities with a Looper. Additionally, this adds
an API, removeAllUpdateListeners(), which is needed to properly
recycle ValueAnimator objects.
Some minor code cleanup and UI tweaks after review.
Changed delay timeout from 1.3s to 0.5s.
Change-Id: Ibcf015e61fa8ba79d62f2019f1b29ace7caa00c8
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 8171b5182f5f07d33c9dfdf2dd8f0f6ae9588039 |
|
05-Aug-2010 |
Jae Yong Sung <jysung@google.com> |
lock screen for xlarge
Change-Id: Iab9f53609bf24be774752a9960aaaa654d7a614f
/frameworks/base/policy/src/com/android/internal/policy/impl/LockScreen.java
|
| 83ea9e395e86ca2d12d822609ca2a8b35b78cca9 |
|
16-Jun-2010 |
Brett Chabot <brettchabot@android.com> |
am 685fcf36: am c95812e6: Merge "Move out all framework-tests classes." into gingerbread
Merge commit '685fcf364b84d5ac911ae9cbbc4fec99f36cbd48'
* commit '685fcf364b84d5ac911ae9cbbc4fec99f36cbd48':
Move out all framework-tests classes.
|
| 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/LockScreen.java
|