History log of /frameworks/native/services/inputflinger/InputDispatcher.h
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
6d2ede118add6647d230f090d64a8c7cf49ebf05 01-Sep-2016 Chih-Hung Hsieh <chh@google.com> Fix google-explicit-constructor warnings in inputflinger.

* Add explicit keyword to conversion constructors.
Bug: 28341362
Test: build with WITH_TIDY=1

Change-Id: I8259317db74b177b6e62a0aa2ad21aead47f698e
/frameworks/native/services/inputflinger/InputDispatcher.h
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.h
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.h
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.h
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.h
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.h
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.h
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.h
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.h
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.h
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.h
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.h
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.h
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.h
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.h
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.h
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.h