History log of /frameworks/native/services/inputflinger/EventHub.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
0faaa0bd7aa5dadea7c365fbb1f186da6eb097ef 24-Sep-2015 Dmitry Torokhov <dtor@google.com> Inputflinger: hook up key event replacement processing

Add handling of "replacement" key events in InputReader and EventHub by
consulting device's character key map (if exists) for presence of
replacement key code for given get code and meta state combination,
before passing it to InputDispatcher.

This enables defining special keys, such as ESC, on keyboards lacking
enough physical keys, via combination of normal keys and modifiers, for
example AltR + 1 => ESC.

Bug: 24504154

Change-Id: I7e36104808bedcf724436c1fbb63d37c35cca8af
/frameworks/native/services/inputflinger/EventHub.cpp
842500e146cdc0036b2a1a3e2acc7626d005128b 14-Mar-2015 Michael Wright <michaelwr@google.com> Fuse stylus and touch screen data.

TODO: Ensure we dispatch new pressure and button data when stylus
is stationary.

Change-Id: I10a665a9b81ff4b9acd01bf72f0fc2e0c2abc203
/frameworks/native/services/inputflinger/EventHub.cpp
063ff53d0b0a0d670ea0185e687526d8fd302820 08-Apr-2015 Tim Kilbourn <tkilbourn@google.com> Pass through availability of audio mic for input devices.

Bug: 15374820
Change-Id: Id2ca6da10165e3a887ebfbb18f663a3bf316ac79
/frameworks/native/services/inputflinger/EventHub.cpp
3447df165f53d76791221531b769801741cfe04a 26-Mar-2015 Tim Kilbourn <tkilbourn@google.com> Use EPOLLWAKEUP properly.

We were trying to use it only when it wasn't supported.

Bug: 19937342
Change-Id: Id35aef9ad84f101f7ada2eb87fb91e5c5e2b3357
/frameworks/native/services/inputflinger/EventHub.cpp
5ea47f7a3222357c4b16500ad66ce493d017ebb2 10-Jan-2015 Elliott Hughes <enh@google.com> We have POSIX clocks, and we don't need to ask for the openssl headers.

This code doesn't need to run on the Mac, and the BoringSSL transition
will be easier without references to external/openssl.

Change-Id: I14ea11fa2911af0f4e95e69636e6a2c26126cbe0
/frameworks/native/services/inputflinger/EventHub.cpp
6183eb72ec16ef36a31a9d92ad4268247a906ef0 17-Nov-2014 Bernhard Rosenkränzer <Bernhard.Rosenkranzer@linaro.org> Remove comparisons that can't be true

keyBitmask and ledBitmask are arrays, "!their address" always evaluates to
false. clang complains about this.

Change-Id: I6aed45a203b0eeaad2093dbdebea03a2c2fc1a3d
Signed-off-by: Bernhard Rosenkränzer <Bernhard.Rosenkranzer@linaro.org>
/frameworks/native/services/inputflinger/EventHub.cpp
677d87ec50b9e8cdf88c61be07ad8c6d7f68f9dd 17-Jun-2014 Dan Albert <danalbert@google.com> Use openssl's SHA1 instead of bionic's.

Bionic is removing its SHA1.

Change-Id: I7d15986ebac9e0f0eb7ff93457780bd90a4f1d4f
/frameworks/native/services/inputflinger/EventHub.cpp
5aa26b274595f12e98abaad364cf9e3061b2dfe7 10-Jun-2014 Mark Salyzyn <salyzyn@google.com> inputflinger: 64-bit compile issues

Change-Id: I9861f96a8234d5f57b664baead7a465771b63bd5
/frameworks/native/services/inputflinger/EventHub.cpp
0516ed85c880733e906821a291e95223d9d34878 02-Apr-2014 Michael Wright <michaelwr@google.com> Misc. buttons aren't gamepad keys.

BUTTON_[1-9] are intended to be misc. buttons so the kernel will
assign them to non-gamepad devices. As such, we shouldn't treat them
as belonging to gamepads at all.

Bug: 13432364
Change-Id: Ida52ec45dadb53df1a9d36ac3ab212a2d2b56359
/frameworks/native/services/inputflinger/EventHub.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/EventHub.cpp
42f2c6a92ca54ff77003ac174e0771351fbe537c 12-Mar-2014 Michael Wright <michaelwr@google.com> Controllers must have buttons and a movement mechanism.

Some devices have joystick axes or DPad keys, but no gamepad buttons (or vice
versa). We shouldn't count these as gamepads since games can't really be
expected to work with this setup in the general case. Instead, require that a
device has a movement mechanism (joystick axes or DPad buttons), as well as at
least one gamepad button before considering it a controller.

Bug: 13432364
Change-Id: I64372e69d29c775094e2b1faa89714da8c29e2be
/frameworks/native/services/inputflinger/EventHub.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/EventHub.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/EventHub.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/EventHub.cpp