| 1eb587b9df9b326e62eaace24b3245d46e60a467 |
|
03-May-2017 |
Kevin Schoedel <kpschoedel@google.com> |
Switch touch input device on hover events.
On a phone in a Mirage headset, two touch nubs are in continuous
contact with the screen while in VR. In order to pass virtual
touchpad events to embedded 2D content that is confined to the
physical display (e.g. permission dialogues), allow a hover event
(as generated for the user's controller pointer) to initiate a
new event.
Bug: 36686408
Test: manual on device
Change-Id: I868472721599843b183b2615aac8e6cd87a58e8e
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| e71f055d52817ceea7634314d57d49d03172a7d4 |
|
22-Mar-2017 |
Evan Rosky <erosky@google.com> |
Fully strip META state during event rewrite
Bug: 36288555
Test: Logged keys coming into PhoneWindowManager to verify that
meta state is stripped.
Change-Id: If51210517845464de185997f7c71a3888ee6af56
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| 78f97b3263053c388080a738b56499139517c3b6 |
|
16-Dec-2016 |
Vladislav Kaznacheev <kaznacheev@google.com> |
Support pointer capture in InputReader
When pointer capture is enabled, the pointer icon is hidden,
the pointer location is not changing, and CursorInputMapper
generates "captured" events with relative offsets instead of
absolute positions.
Captured events have their source set to a newly introduced
SOURCE_MOUSE_RELATIVE (of SOURCE_CLASS_TRACKBALL).
Test: InputReader_test --gtest_filter=
CursorInputMapperTest.Process_PointerCapture
Bug: 30897034
Change-Id: Id30cb8e7edac56ab813e22a834cc44ab263d1003
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| e5c943a7bf0081d9006b8e45a125808e91a905af |
|
18-Jan-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Remove window obscurement information from ACTION_OUTSIDE events."
|
| 3b1061044beec08306f6159fbc0dc5a8b7896dbc |
|
16-Jan-2017 |
Michael Wright <michaelwr@google.com> |
Remove window obscurement information from ACTION_OUTSIDE events.
If ACTION_OUTSIDE_EVENTS contain information about whether the touch is
obscured, then a pattern of invisible, untouchable, unfocusable
SYSTEM_ALERT_WINDOWS can be placed across the screen to determine
approximate locations of touch events without the user knowing.
Bug: 31097064
Test: cts-tradefed run commandAndExit cts-dev -m CtsSecurityTestCases -t android.security.cts.MotionEventTest
Change-Id: Iea968ce23e018acf95116896a1ba4c065885b760
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| 7823e124e00576e20e47ec717cbe8bc89f0f2bf2 |
|
29-Sep-2016 |
Mark Salyzyn <salyzyn@google.com> |
Replace cutils/log.h and rationalize log/log.h and android/log.h
- cutils/log.h treat as deprecated and lead by example
- android/log.h to be used instead of log/log.h if possible
- add system includes that are assumed as side effects
- define LOG_TAG first
Test: compile
Bug: 31289077
Bug: 30465923
Change-Id: I8d99b24c333578c9b5aa9f2a01324bd0bba268dd
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| a5e161b1207ef447a51e99856097d69d4a6111e1 |
|
29-Sep-2016 |
Mark Salyzyn <salyzyn@google.com> |
Replace cutils/log.h and rationalize log/log.h and android/log.h
- cutils/log.h treat as deprecated and lead by example
- android/log.h to be used instead of log/log.h if required
- add system includes that are assumed as side effects of log.h
- modules that use SLOG should use SLOG for all logging (installd)
- define LOG_TAG first
- remove logging infrastructure if not used
Test: build
Bug: 31289077
Change-Id: Iea147a0104c7ab7f12451304131d6500f42141e7
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| 455f288a7db0e94be6a5c5277c8f09eb1b1ffd13 |
|
18-Apr-2016 |
Michael Wright <michaelwr@google.com> |
Merge "Add new MotionEvent flag for partially obscured windows." into mnc-dev am: 58dc18a am: ab4b3c3 am: 2352674
am: c846278
* commit 'c846278141c94385a2c931a1df80ed3ffcc8e7c2':
Add new MotionEvent flag for partially obscured windows.
Change-Id: Ia0940c0440b94922fde7a93ef5d95df59aed3c3e
|
| cdcd8f2b25a4bf32bb7506fc98ba541d274c9a31 |
|
23-Mar-2016 |
Michael Wright <michaelwr@google.com> |
Add new MotionEvent flag for partially obscured windows.
Due to more complex window layouts resulting in lots of overlapping
windows, the policy around FLAG_WINDOW_IS_OBSCURED has changed to
only be set when the point at which the window was touched is
obscured. Unfortunately, this doesn't prevent tapjacking attacks that
overlay the dialog's text, making a potentially dangerous operation
seem innocuous. To avoid this on particularly sensitive dialogs,
introduce a new flag that really does tell you when your window is
being even partially overlapped.
We aren't exposing this as API since we plan on making the original
flag more robust. This is really a workaround for system dialogs
since we generally know their layout and screen position, and that
they're unlikely to be overlapped by other applications.
Bug: 26677796
Change-Id: I9e336afe90f262ba22015876769a9c510048fd47
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| c29d0845f5db1a1ad4847fe2d8f3cf9a83390ab4 |
|
03-Feb-2016 |
Dan Albert <danalbert@google.com> |
Merge "Clean up warnings in inputflinger." am: f3606ef25f am: ca5ad095f4
am: 82d47db481
* commit '82d47db4815ab8b49f4c399ba16d2af12926cfe1':
Clean up warnings in inputflinger.
|
| 1bd2fc059c73c91f64d86b0eee59eda6ba888354 |
|
03-Feb-2016 |
Dan Albert <danalbert@google.com> |
Clean up warnings in inputflinger.
Bug: http://b/26936282
Change-Id: Ie1fb281425c3b8c4b3e6e88dc5722d51b77ee093
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| fa1706afaf12b48fe0ab6d4b061b614bf901b173 |
|
03-Dec-2015 |
Jun Mukai <mukai@google.com> |
Add relative-x/y axis for mouse devices.
Used by Ie21e521f3e5c581f976dc0feb5d84bfa48b046cd.
Bug: 5452473
Change-Id: I4189eb4d93f50c2865b7a325727be5ceebcc71f8
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| fa13dcf39f09534ab8e95aec6f15a61a7f500b4c |
|
12-Jun-2015 |
Michael Wright <michaelwr@google.com> |
Send cancelation events to monitors when injection fails.
Bug: 20649729
Change-Id: I46cd14ac1f040d404c0b1581b38fa07a944e5fb9
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| 3a9817228928a8db68c34afe547c9ba18169af5b |
|
10-Jun-2015 |
Michael Wright <michaelwr@google.com> |
Only log dropped input when disabled for the first event.
Bug: 19851495
Change-Id: I8cb8076723c1ca1732c3bc37f283d8eb48b7bee0
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| 7b159c9a4f589da7fdab7c16f3aefea25e0e7e4f |
|
14-May-2015 |
Michael Wright <michaelwr@google.com> |
Revert "Revert "Add new MotionEvent actions for button press and release.""
This reverts commit 70b41ef580644fd0fe6fa9b8ac7e4a745cfb6db3.
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| 70b41ef580644fd0fe6fa9b8ac7e4a745cfb6db3 |
|
14-May-2015 |
Michael Wright <michaelwr@google.com> |
Revert "Add new MotionEvent actions for button press and release."
This reverts commit 48a8a0e4322969e1551536d6183af3a1faa2240b.
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| 48a8a0e4322969e1551536d6183af3a1faa2240b |
|
11-May-2015 |
Michael Wright <michaelwr@google.com> |
Add new MotionEvent actions for button press and release.
Introduce ACTION_BUTTON_PRESS and ACTION_BUTTON_RELEASE as actions to
signal a button press or release. If these actions happen
simulanteously with a DOWN or UP event then they're explicitly
ordered to happen after the DOWN or preceding the UP in order to send
them to the most recently targeted view.
Also, introduce new stylus button constants that differ from the
constants we use for mouse buttons.
Bug: 20704355
Change-Id: Ib960a5004db5429ad2fc8db020704773e2978327
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| 106547c1e33453b7e20b7b387087092d36aa6a72 |
|
24-Dec-2014 |
Narayan Kamath <narayan@google.com> |
am 033f7e8e: Merge "InputDispatcher: Optimize count()"
* commit '033f7e8e35ac76404fe823a67e07ba7c42bc357c':
InputDispatcher: Optimize count()
|
| 65dbe971b1bcefdaa353662f7bde5ea327544113 |
|
18-Nov-2014 |
Jon McCaffrey <jmccaffrey@nvidia.com> |
InputDispatcher: Optimize count()
Count items as they are added and removed rather than iterating over the
entire list to count them.
Increases performance slightly, particularly when tracing is turned on,
which causes count to be queried more often, and when the number of
items in the queues grow large. This can happen due to applications not
responding, for example.
Change-Id: I0f11f7edd46089612af910cdfabfeb3ee685d7d9
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| 0c17a2b2ea5c7bd4f6c9bd426e67c40022e3d84c |
|
11-Nov-2014 |
Craig Mautner <cmautner@google.com> |
Stop consuming input on error dialogs.
This code is no longer necessary and was preventing input from
reaching their desired windows. See bug 17648830.
Change-Id: Ib1c026ece70e6fa98343340b89af4199d6d0ffca
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| ffb497743831ae4857b674629b58ea3c46d01431 |
|
11-Oct-2014 |
Jeff Brown <jeffbrown@google.com> |
Improve ANR diagnostics.
Print more details about the exact reason that an ANR has occurred.
Also start checking that the window actually has a registered
input connection that is not in a broken state. These windows
are supposed to be cleaned up by the window manager promptly
as if the app had crashed but the pattern of ANRs we are observing
suggests that broken windows might be sticking around longer than
they should.
Bug: 17721767
Change-Id: Ie2803a3fa9642381ecadc198fec15e1b70d93c20
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| 2e732956adffbdf37374115d52646ddae9498a96 |
|
24-Sep-2014 |
Michael Wright <michaelwr@google.com> |
Only mark repeated keys as PASS_TO_USER if the original key was.
Bug: 17629695
Change-Id: Ic569aba4149c6cc321c2cf8aede7c5e8a1196234
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| 78f2444aaf09ba05c7b7e79d85f1e7efafa9fa94 |
|
07-Aug-2014 |
Michael Wright <michaelwr@google.com> |
Revert "Revert "Add system accelerators for BACK and HOME.""
This reverts commit d671f98a27f547ebcddff8dc962fe895549355e2.
Change-Id: Ibec48f81653bd2f755fc59a241fa7836baf53233
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| d671f98a27f547ebcddff8dc962fe895549355e2 |
|
07-Aug-2014 |
Michael Wright <michaelwr@google.com> |
Revert "Add system accelerators for BACK and HOME."
This reverts commit 278b525d25b852554015ec4f92862f9297b502fd.
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| 278b525d25b852554015ec4f92862f9297b502fd |
|
05-Aug-2014 |
Michael Wright <michaelwr@google.com> |
Add system accelerators for BACK and HOME.
Meta+Backspace -> BACK
Meta+Enter -> HOME
Bug: 14066931
Change-Id: Iff1d027300fa9911626785944a6d8efe4f62235e
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| bc6001b026069714177526eb1120b0011d6f2a51 |
|
02-May-2014 |
Narayan Kamath <narayan@google.com> |
Change InputMessage.motion.pointerSize to a uint32_t.
This ensures it's the same size in both 32 and 64 bit
processes and also brings it in line with struct
MotionEntry.
Change-Id: I66bb8b8d8664763e7dcbd489686051f563d5e1dc
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| 872db4f11e407accccba9d37c335ef7e3597eba4 |
|
23-Apr-2014 |
Michael Wright <michaelwr@google.com> |
Move key attribute information out of native.
Native doesn't ever actually care about the attributes of keys, so
move all of it up into the managed layer and move all of the key
names down so they're defined once.
Change-Id: Ic8ded13ce050b2b98744735ff50d11e8d882d7d5
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| dc5992e48ca88d882313d206f8174efcc5e01455 |
|
11-Apr-2014 |
Jeff Brown <jeffbrown@google.com> |
Plumb display power state through display manager.
Eliminated the bright here and woke here policy flags since they
were unused. Simplified the input dispatch policy somewhat.
Bug: 13133142
Change-Id: I74b4dc866c44c46ed43006a48a857f0da4c07cc9
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| 37764c71a0ac79142f90bb112b6cabffb940b955 |
|
27-Mar-2014 |
Narayan Kamath <narayan@google.com> |
Cherry pick parts of f5df700e6ce.
This is logically a part of the merge conflict resolution for
22d07464 to master. These files moved across git repositories.
Change-Id: Id95bfa0bf503295f2c02a201f4bec5243d169ec4
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| 41d2f80739700a56fd6a670923a2966add8dae61 |
|
18-Mar-2014 |
Mark Salyzyn <salyzyn@google.com> |
inputflinger: 64 bit compile issues
Change-Id: I73c37eb19b28d987ff13632a999e71d6c96cc3e0
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| 38dcdff3087f01ba02aabfc17b3ff6c549bb5707 |
|
19-Mar-2014 |
Michael Wright <michaelwr@google.com> |
Generate ACTION_CANCEL on joystick disconnect.
Bug: 11480300
Change-Id: I46706838eec0711c6bf345301e7b4ccbad83b063
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| f086ddbb97e59bd4a0c27745f6e6cc9832a2d4f8 |
|
11-Feb-2014 |
Jeff Brown <jeffbrown@google.com> |
Add support for injecting events into ActivityContainers.
Enhanced the input system to support concurrent dispatch of touch
events on multiple displays which is required for this to work.
Add method to apply offset to PointerCoords.
Change-Id: I55fe4a9a8785ae5a2d3341d214fa3c5107f3963a
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| d02c5b6aace05d9fd938e2d03705ac4f60f8da19 |
|
11-Feb-2014 |
Michael Wright <michaelwr@google.com> |
Move inputservice over to frameworks/native
Add all of the underlying input system pieces, minux PointerController and
SpriteController, to inputflinger. This is in preparation for moving input to
its own process and the addition of the input HAL.
Try 2.
Change-Id: I5f571fe86eb570885ae994e1f0552fb558930346
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| 1b1fe314c4e74ef85afe4dacd7ba1e87e6862aa3 |
|
11-Feb-2014 |
Michael Wright <michaelwr@google.com> |
Revert "Move inputservice over to frameworks/native"
This reverts commit 2dceb67f1f32bd2ec589c4ac3d83da0b8dbe4a5c.
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|
| 2dceb67f1f32bd2ec589c4ac3d83da0b8dbe4a5c |
|
10-Feb-2014 |
Michael Wright <michaelwr@google.com> |
Move inputservice over to frameworks/native
Add all of the underlying input system pieces, minux PointerController and
SpriteController, to inputflinger. This is in preparation for moving input to
its own process and the addition of the input HAL.
Change-Id: I1419a740b38756bd0d54fef5f5ca337e6815b1b0
/frameworks/native/services/inputflinger/InputDispatcher.cpp
|