b72c9ad721e5ff5b9d5a45ca4ba2608940815388 |
|
12-Apr-2016 |
Jorim Jaggi <jjaggi@google.com> |
No input for windows in minimized docked stack Also make them unfocusable, and don't focus the docked stack when tapping into it in that state. Bug: 27972642 Change-Id: Ic24ff9a5f39f596fe4a2f50567566d4400f9c125
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
0d50d8660dac35f7eceb5d74756de0417095b427 |
|
30-Mar-2016 |
Vladislav Kaznacheev <kaznacheev@google.com> |
Add wallpaper input consumer to WindowManagerService This is an input consumer similar to the one used when hiding the navbar, but placed above wallpapers. It might be useful for processing touch events over "desktop" in freeform MW mode. Re-landing I9d6d28a624f750ad48fc39f9b149dd1f989cceba after fixing build. Bug:26688904 Change-Id: I89fdabd9c72cdd4a1d7ca626c33ddc99ddea97f9
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
2769e7ebe9d9c5b7f1d10b21b32787b98522339f |
|
31-Mar-2016 |
Vladislav Kaznacheev <kaznacheev@google.com> |
Revert "Add wallpaper input consumer to WindowManagerService" This reverts commit 6013a558262d149023b32ab175c9b885b6c5b81d. Change-Id: I2711afe2e97a8b9a4bd94193202cb83113b3bd7e
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
6013a558262d149023b32ab175c9b885b6c5b81d |
|
30-Mar-2016 |
Vladislav Kaznacheev <kaznacheev@google.com> |
Add wallpaper input consumer to WindowManagerService This is an input consumer similar to the one used when hiding the navbar, but placed above wallpapers. It might be useful for processing touch events over "desktop" in freeform MW mode. Bug:26688904 Change-Id: I9d6d28a624f750ad48fc39f9b149dd1f989cceba
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
e89eeac54766633e482b51c15e99d2d93843ce26 |
|
12-Mar-2016 |
Wale Ogunwale <ogunwale@google.com> |
Added input freeze reason string. To help debug b/27576902 Bug: 27576902 Change-Id: Ic3d2bb25842593efb11e195a1bbe19bed3bf7067
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
0bd180d8880b3d1b9677f154c034a2af840b4796 |
|
08-Dec-2015 |
Filip Gruszczynski <gruszczy@google.com> |
Improve debugging setup for window manager package. This moves debug flags to a dedicated class and also provides a mechanism to either have fine grained tags or one common tag for easier grepping the logcat. This mimicks the approach in activity manager package. Change-Id: Ie8c08b9a3d8b182335ee5547ee05d21b5933db6b
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
b15758ab7a6481717d0d29612e870d7241061c31 |
|
17-Nov-2015 |
Chong Zhang <chz@google.com> |
Support scrolling for non-resizeable tasks in side-by-side mode Display toast when a non-resizeable task is put into side-by-side mode. Scroll the task upon a two-finger scroll gesture. bug: 25433902 Change-Id: I69967056a564cfe7773afb80aa7e7ea7167a791a
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
053c8e4ef4a8cbc89506b661dd6ef51a301a895c |
|
16-Nov-2015 |
Wale Ogunwale <ogunwale@google.com> |
Crop window input region to stack bounds. Prevents the input region of a window from extending outside the stack bounds. For example, if you have a non-sizeable activity in docked mode you don't want the app getting touchs when you tap on the side occupied by the other app. Bug: 25710884 Change-Id: I044b4e87448fbd3eb51822e6d71e8ed8d06f55ec
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
1fcbab6ae5c99acab70eacc015d194e2c6ddd4e2 |
|
04-Nov-2015 |
Jorim Jaggi <jjaggi@google.com> |
Implement divider UX interactions - Update visuals to spec - Divider lifts when touching - Implement basic version of snap points and animations - Implement touch conflict behavior: If touched around 48x48dp area around the handle, the divider handles all these touches. If touched outside of the black background divider, touch goes directly to underlying window. If touch on the black background divider, touch is considered slippery and thus the window in which the touch trace moves gets the touches. Change-Id: I0307c191ae032672c4b73d439c23cf9833d3fce6
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
9cac3b4d4629f10423e293a77f3c2184ba867817 |
|
30-Oct-2015 |
Filip Gruszczynski <gruszczy@google.com> |
Fix bug preventing resizing of freeform apps. Also move the calculation of the touchable region to WindowState, since it calls many methods from there. Change-Id: I7f799277f4ed8a62b1ac8240f2b21d31a095a693
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
f8a2a632023ef0bafa9c7d5a343cf84d10dbd241 |
|
28-Oct-2015 |
Filip Gruszczynski <gruszczy@google.com> |
Fix touching outside of popup not dismissing it. We only included the exact popup window area for intercepting touches that would dismiss the popup. We need to intercept the parent area, so we use the task or stack associated with the window to determine which touch events to intercept and use as dismiss. This doesn't affect which touch events will be delivered to the window. Bug: 25329650 Change-Id: Ie248ec67bb5328fd67b470f556cf206ce888514c
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
3ddc5d60967a5daa2ebf0ede98b71093bb8cc4ae |
|
24-Sep-2015 |
Filip Gruszczynski <gruszczy@google.com> |
Resizing docked stack by dragging dock divider. Change-Id: Icc9df00446780f8cd81df4654ace07f33346e901
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
61b009e0591df4fcaf5c57c6ce598044263d952f |
|
17-Sep-2015 |
Wale Ogunwale <ogunwale@google.com> |
Don't crop home activity windows to stack bounds. We crop windows to their stack bounds when the docked stack exists. We don't want to do this for the home activity since the docked stack isn't visible when the home activity is visible. Change-Id: Ibb3157dabbb6c979358ddc2098a01c6ddf6540e8
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
3b2658011819cfe1bed61763bb666bde6e919f79 |
|
16-Sep-2015 |
Wale Ogunwale <ogunwale@google.com> |
Use stack bounds to determine input bounds for window. We were previously using the task bounds to determine the input bounds for the window. This doesn't work for the case where the docked stack is next to a non-resizeable activity/task. In this case the task is still fullscreen, but the window surface is cropped to the stack size which isn't fullscreen since the docked stack is up. By using the stack bounds the input region matches what is displayed on screen. Change-Id: Ia4d2b3a7a050eff38d651e511f5822c4428e137d
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
8e89b31a62fb9ec5ad33908c5e8e9c7ab2fd949f |
|
10-Sep-2015 |
Chong Zhang <chz@google.com> |
Move window moving and resizing handling to WindowManager - add a startMoving API to initiate a window move from app, once the move starts WindowManager will take over the event handling. - detect touch events along window's outside border and start a resize if necessary Change-Id: Ic7e8baba34e0aa27a43173e044ffb46e93e219e0
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
f932e56bd8abd737e471e841f175c787c4f20826 |
|
20-Aug-2015 |
Skuhne <skuhne@google.com> |
Adding a touchable area around a task To allow task/window resizing through decors drawn outside the task bounds (e.g. shadows) on the free form desktop. Bug: 23324672 Change-Id: Iaf88ec658e235aa74317a0f33d25fee83f959ac3
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
e8069dcfcff15e060fc397b9ed5ea8b915b1cfa7 |
|
18-Aug-2015 |
Wale Ogunwale <ogunwale@google.com> |
Moved window manager wallpaper control into separate class Change-Id: Ia3c12065678992614667dc210d4611a1250ca22b
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
e4a0c5722b1d8db95dfc842d716452dbbf02c86d |
|
30-Jun-2015 |
Wale Ogunwale <ogunwale@google.com> |
Allow stacks to hold tasks on various sizes. Tasks are now resizeable just like stacks. Adjusting the size of a stack will also adjust the size of all it's containing tasks. This model allows us to be more flexible in using stacks as workspaces (like you would have in a desktop environment) and tasks as the resizeable windows within the workspace. Also added "adb shell dumpsys window visible-apps" for getting the list of visible app windows. Bug: 22068114 Bug: 19182363 Change-Id: I5bf77063252a5abae4e327f6fc42e607091749f9
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
f83e824216435e45f36a3587e269888f791b2a01 |
|
20-May-2015 |
Selim Cinek <cinek@google.com> |
Fixed that touches where incorrectly consumed when fullscreen The fake window that was added when View.SYSTEM_UI_FULL_SCREEN was set consumed all touches, even those going to the SystemUI and not just those of windows below. The input consumer is now correctly positioned in the window order to only capture the right touches. Clicks to the volume panel and the heads up now correctly go to the right place instead of just unhiding the SystemUI bars. Bug: 21089476 Change-Id: Ib53dfc0b33b70084ca607d0f044db30b6e6c91d6
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
a6ab5c4efbbf438693fa976b54ac84c033109df0 |
|
24-Apr-2015 |
Wale Ogunwale <ogunwale@google.com> |
Cleaned-up unused session argument. Change-Id: Iff9d0df5f1643c581767a41a1ba4b1d43e5b45d8
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
40832ac39502d7c4226b00c1d14f895ff449c613 |
|
15-Apr-2015 |
Michael Wright <michaelwr@google.com> |
am 6fb80b70: am 99e23088: am 150e0e87: Merge "fix return value scale of notifyANR()" * commit '6fb80b704e7808e4e7cd15f6ccade1e4b6406b56': fix return value scale of notifyANR()
|
def340d45e8795128aab98d9d3cc36bcac58710e |
|
15-Apr-2015 |
baik.han <baik.han@lge.com> |
fix return value scale of notifyANR() fix return value scale of notifyANR() from milliseconds to nanoseconds when windowState is not null This prevent unintended frequent method calls of notifyANR() in a very short time. Change-Id: Icc1f363b3ed3538821a42c080809567473bfb833 Signed-off-by: Baik Han <baik.han@lge.com>
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
165be0c70d128f0ece876d54e1c7e95ef04c6960 |
|
28-Jan-2015 |
Craig Mautner <cmautner@google.com> |
Remove TYPE_UNIVERSE_BACKGROUND from system An experiment that is over and has been occupying space. Fixes bug 18088522 item #7 Change-Id: Ib0fcaa24243ed9b0581143e1d5114c1fd2b0aa6e
/frameworks/base/services/core/java/com/android/server/wm/InputMonitor.java
|
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
|