26af8c197c17487ac0400a7a3310037e57eda2a0 |
|
05-Dec-2014 |
Filip Gruszczynski <gruszczy@google.com> |
am 26b18771: Merge "Private Window flag to disable touch events in WallpaperService." into lmp-sprout-dev * commit '26b187711fdf6224e14df465a58f30f510011b49': Private Window flag to disable touch events in WallpaperService.
|
b8c0694ae883b0e14beab97c947a7c121c64dda6 |
|
05-Dec-2014 |
Filip Gruszczynski <gruszczy@google.com> |
Private Window flag to disable touch events in WallpaperService. Change-Id: I18b46340f89cbea0b6daeb1efe9c31656f4e1a5d
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
c08eab81f30a3120ec0929d3508b4a78d498e1ff |
|
11-Nov-2014 |
Craig Mautner <cmautner@google.com> |
Show error dialogs over apps that dismiss keyguard Error dialogs absorb all input to ensure that they are not missed. This can cause the screen to lock up if they are not displayed but are still absorbing touches. This was what was happening when there was an error dialog up at the same time as a phone call came in as in b/17648830. This fix recognizes when an app is dismissing the keyguard and forces any error dialogs to be shown over such an app. This also removes the private flags from the input system as they are no longer needed. Fixes bug 17648830. Change-Id: I5c98b8265a1448b445fdb2f745fc78892f8656a4
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
a6863ad62296a5280504165a1fbc70523940a9c8 |
|
05-Sep-2014 |
Michael Wright <michaelwr@google.com> |
Merge "Allow for event dispatching when in non-interactive states." into lmp-dev
|
70af00abf73160235d4efe114fcf4753007a8ff3 |
|
04-Sep-2014 |
Michael Wright <michaelwr@google.com> |
Allow for event dispatching when in non-interactive states. We need to allow for event dispatching in non-interactive states so that we can enable a richer set of interactions when a device is dozing (i.e. is in a low power state with an Always-on-Display). Bug: 17167296 Change-Id: I8ae0f544a8106cb91ff38c2309b8b57cbe2f2c72
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
3818c9261ceaa3a700ff984fbcd245faeede38d7 |
|
02-Sep-2014 |
Michael Wright <michaelwr@google.com> |
Add support for SW_CAMERA_LENS_COVER. This allows for magic cover type accessories to launch the camera application. Bug: 16034563 Change-Id: I0a46ef885737d964a1482c99f41145053d559faf
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
858737d08d9a2db7ef230a17975cd4ded709c3c5 |
|
11-Apr-2014 |
Jeff Brown <jeffbrown@google.com> |
resolved conflicts for merge of 4e5c089e to master-lockscreen-dev Change-Id: I456ff6be1e39b65f3e0efeb7fb1924e71d11f6b1
|
037c33eae74bee2774897d969d48947f9abe254f |
|
09-Apr-2014 |
Jeff Brown <jeffbrown@google.com> |
Plumb display power state through display manager. Declare a new method, Display.getState() to retrieve the actual power state of a display. Improved documentation for Intent.ACTION_SCREEN_ON and Intent.ACTION_SCREEN_OFF to clarify what they really mean in terms of the interactive state of the device. Deprecated PowerManager.isScreenOn() and replaced it with PowerManager.isInteractive() with a more suggestive name and better documentation. Redirect display power state changes to go through the display manager first and only then head over to the power manager for legacy compatibility. Eliminated the bright here and woke here policy flags since they were unused. Simplified the input dispatch policy somewhat. Ensure that screen wake locks are respected up until the point when dozing really begins. Fixed a regression in DreamService where onDreamingStarted might be called before onWindowAttached. Bug: 13133142 Bug: 13472578 Bug: 13929355 Bug: 13760290 Change-Id: Iabef96921dd554ce3768fb18619cefc3230b5fb0
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
380ecb81db52a9d0197ca969951d07b91c20d2b9 |
|
14-Mar-2014 |
Jorim Jaggi <jjaggi@google.com> |
Make Keyguard a library and make StatusBar the new Keyguard. This change achieves a couple of things: - Let Keyguard be a library, so we can use it in SystemUI. - Introduce FLAG_KEYGUARD for windows and deprecate TYPE_KEYGUARD. Make all the TYPE_KEYGUARD behaviour dependant on the flag. - Implement a new KeyguardService in SystemUI, and bind that service from PhoneWindowManager. - Introduce BaseStatusBar.setKeyguardState and inflate KeyguardSimpleHostView there and use FLAG_KEYGUARD for the window, such that the status bar window essentially gets the Keyguard. Bug: 13635952 Change-Id: I059d80d8b9b9818a778ab685f4672ea2694def63
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
2687550272ba061448f5d5b914700dc335299ee7 |
|
31-Jan-2014 |
Jeff Brown <jeffbrown@google.com> |
Add a new "doze mode" based on Dream components. When a doze component has been specified in a config.xml resource overlay, the power manager will try to start a preconfigured dream whenever it would have otherwise gone to sleep and turned the screen off. The dream should render whatever it intends to show then call startDozing() to tell the power manager to put the display into a low power "doze" state and allow the application processor to be suspended. The dream may wake up periodically using the alarm manager or other features to update the contents of the display. Added several new config.xml resources related to dreams and dozing. In particular for dozing there are two new resources that pertain to decoupling auto-suspend mode and interactive mode from the display state. This is a requirement to enable the application processor and other components to be suspended while dozing. Most devices do not support these features today. Consolidated the power manager's NAPPING and DREAMING states into one to simplify the logic. The NAPPING state was mostly superfluous and simply indicated that the power manager should attempt to start a new dream. This state is now tracked in the mSandmanSummoned field. Added a new DOZING state which is analoguous to DREAMING. The normal state transition is now: AWAKE -> DREAMING -> DOZING -> ASLEEP. The PowerManager.goToSleep() method now enters the DOZING state instead of immediately going to sleep. While in the doze state, the screen remains on. However, we actually tell the rest of the system that the screen is off. This is somewhat unfortunate but much of the system makes inappropriate assumptions about what it means for the screen to be on or off. In particular, screen on is usually taken to indicate an interactive state where the user is present but that's not at all true for dozing (and is only sometimes true while dreaming). We will probably need to add some more precise externally visible states at some point. The DozeHardware interface encapsulates a generic microcontroller interface to allow a doze dream for off-loading rendering or other functions while dozing. If the device possesses an MCU HAL for dozing then it is exposed to the DreamService here. Removed a number of catch blocks in DreamService that caught Throwable and attempted to cause the dream to finish itself. We actually just want to let the process crash. Cleanup will happen automatically if needed. Catching these exceptions results in mysterious undefined behavior and broken dreams. Bug: 12494706 Change-Id: Ie78336b37dde7250d1ce65b3d367879e3bfb2b8b
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
9158825f9c41869689d6b1786d7c7aa8bdd524ce |
|
22-Nov-2013 |
Amith Yamasani <yamasani@google.com> |
Move some system services to separate directories Refactored the directory structure so that services can be optionally excluded. This is step 1. Will be followed by another change that makes it possible to remove services from the build. Change-Id: Ideacedfd34b5e213217ad3ff4ebb21c4a8e73f85
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|