History log of /frameworks/native/services/inputflinger/tests/InputReader_test.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
eaf7acd902d8c178570a51cc317a07bb8c19807e 09-Jan-2018 Siarhei Vishniakou <svv@google.com> Ensure deviceTimestamp is cleared

Add native test to ensure that deviceTimestamp field
is cleared.

Bug: 62940136
Test: m -j inputflinger_tests_InputReader_test
inputflinger_tests_InputDispatcher_test && adb push
out/target/product/$TARGET_PRODUCT/data/nativetest64/*
/data/nativetest64/
(adb shell mkdir /data/nativetest64 if needed)
on device: /data/nativetest64/inputflinger_tests # ./InputReader_test

Change-Id: Id70f07b143c22fc337fa94b264bc7fafa3f8d3fd
/frameworks/native/services/inputflinger/tests/InputReader_test.cpp
16f90693fdce4aec6ec7507628660e4f9564a201 27-Dec-2017 Siarhei Vishniakou <svv@google.com> Process EV_MSC MSC_TIMESTAMP in InputMapper

An evdev driver could report EV_MSC MSC_TIMESTAMP input event to relay
the number of microseconds since the last reset. This data could be
useful for keeping track of the specific kernel time of a particular
input_event. Propagate this data here to the InputDispatcher level,
but only for the MultiTouchInputMapper.

Bug: 62940136
Test: report MSC_TIMESTAMP in kernel driver on Pixel 2 XL device and
observe the data in the inputflinger layer using HeatMapDemo app.
Test: m -j inputflinger_tests_InputReader_test
inputflinger_tests_InputDispatcher_test && adb push
out/target/product/$TARGET_PRODUCT/data/nativetest64/*
/data/nativetest64/
then on device: /data/nativetest64/inputflinger_tests # ./InputReader_test

Change-Id: Id990ec46a380e7f367020863fd86e4bae6ce47e4
/frameworks/native/services/inputflinger/tests/InputReader_test.cpp
aa449c9c9905049938aba7d44bbcf84c539b58b3 13-Dec-2017 Michael Wright <michaelwr@google.com> Scale the pressure range's max value.

Since the pressure scale is configurable via a idc property, it isn't
guaranteed to always be [0, 1.0]. Unfortunately, we didn't scale the max
value of the MotionRange so we'd incorrectly return a max pressure of
1.0 for all devices, even when they might exceed that range.

Test: adb push \
$(gettop)/out/target/product/taimen/data/nativetest/inputflinger_tests/InputReader_test \
/data/nativetest/inputflinger_tests/InputReader_test &&
adb shell /data/nativetest/inputflinger_tests/InputReader_test

Change-Id: I7ef174941c4faa7d7efdaa3d69107740f58afd2a
/frameworks/native/services/inputflinger/tests/InputReader_test.cpp
f93fcf4c403fa4181536821680d495824a4290c5 23-Nov-2017 Siarhei Vishniakou <svv@google.com> Prefer std::string over String8

String8 is obsolete, only use std::string in the
input libraries now.

Bug: 64258224
Test: make
Change-Id: I958b6b281d969138f39cc26825c877a24bc4a853
/frameworks/native/services/inputflinger/tests/InputReader_test.cpp
fa5cf46ac7b84cc20bf29e5b8c298a84b407b1e3 05-Apr-2017 Santos Cordon <santoscordon@google.com> Add uniqueId to Virtual Display and pass through to inputflinger (2/2)

This CL adds:
1) Adds uniqueId (protected via system/sig permission) to virtual
displays.
2) Add support for N virtual display viewports into inputflinger.
3) Set the virtual display's viewports in inputflinger if it has the
uniqueId value set to non-null. (a) Moving the new viewport from java to
native inputflinger and (b) adding "uniqueId" value to viewports makes
up the great majority of this change.
4) From the inputflinger side, we also read in a new value from the
input device configuration files called 'touch.displayId'.
5) When touch.displayId and the virtual display's uniqueId match,
inputflinger links the two.

Test: Start VR and ensure that the virtual viewport shows up when running
'adb shell dump input". Run a VR app, and ensure that the virtual input
device is associated with the new virtual viewport.

Bug: 36051620
Change-Id: I662f09f863a3dc94c570e7e7f30b83888b3f514c
/frameworks/native/services/inputflinger/tests/InputReader_test.cpp
e54cb8574f9c44256c88c192ec28256fbd0b3006 22-Mar-2017 Siarhei Vishniakou <svv@google.com> Adding feature: input device disable/enable

This functionality will only be available for signed system
services. A disable call will cause a file descriptor to the input
device driver to be closed, which in turn may cause the input
device to switch into a low-power mode. An enable call will
reopen the input device.

Bug: 30143923
Test: CTS test - android.view.cts.InputDeviceEnabledTest
Native test - WhenEnabledChanges_SendsDeviceResetNotification,
WhenDeviceCreated_EnabledIsTrue. Also developed a custom apk
with signature permission that calls disable/enable on a
touchscreen device. Verified that touchscreen stops working
when disable is called and starts working again when
enable is called. Verified that the file
handle to the driver is closed and reopened. Verified that
the notification onInputDeviceChanged is received in the
app.

Change-Id: I99a7866cebff873dc1848e11a39045ed2eaec07c
/frameworks/native/services/inputflinger/tests/InputReader_test.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/tests/InputReader_test.cpp
fb7525847700ef8c328616727c747dc5e0ca8c4e 16-Dec-2016 Vladislav Kaznacheev <kaznacheev@google.com> Fix InputReader_test

Account for ACTION_BUTTON_PRESS/RELEASE events.

Bug: 33701392
Test: all tests in InputReader_test pass
Change-Id: I1b5279b24f7203a45242c96c84743e14dc06e7f8
/frameworks/native/services/inputflinger/tests/InputReader_test.cpp
6ca70efdaef8c07e91692101c7a3ae35dc1e0cbb 30-Apr-2016 Chih-Hung Hsieh <chh@google.com> Fix google-explicit-constructor warnings.

Bug: 28341362
Change-Id: I83bb2282249ecd4e39347b90f5fb53788e1fff5b
/frameworks/native/services/inputflinger/tests/InputReader_test.cpp
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/tests/InputReader_test.cpp
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/tests/InputReader_test.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/tests/InputReader_test.cpp
39efe3e5bf6282a4851e0eb3b938060c8f7790ae 17-Oct-2014 Narayan Kamath <narayan@google.com> Clean up unused parameter warnings.

Manual application of change 692018430f115343e36b0680acc659f2a731a5d7.

Change-Id: I100f838d70e591a13abb198dc420000ef114a429
(cherry picked from commit 97a3367a1b49b1761e3485765b2bd3f2293f9638)
/frameworks/native/services/inputflinger/tests/InputReader_test.cpp
71b16e81f9cbf2e288611f32c43ea7fb4a331fcf 10-Mar-2014 Jason Gerecke <killertofu@gmail.com> Support unique calibration per orientation

Updates the format of the calibration XML to store the Surface rotation
that a specific calibration applies to. Also updates the API to require
a rotation value for get/set, and has the native framework supply this
according to the current rotation whenever it changes.

Change-Id: If38563ceba27c9d8a75f9fd7928c8d7c9d187afb
/frameworks/native/services/inputflinger/tests/InputReader_test.cpp
489fda8d476f3fc10b0251263cc69528b736257b 08-Sep-2012 Jason Gerecke <killertofu@gmail.com> Add test for InputReader location calibration

This patch adds a test for the new native location calibration
code. The Java interface is not tested.

Change-Id: Id7496486f6b6e2ade12ada607b62d1594af488e8
/frameworks/native/services/inputflinger/tests/InputReader_test.cpp
12d6baa9b832f16a28f048ed5ffab75a76ed9c41 28-Jan-2014 Jason Gerecke <killertofu@gmail.com> Initialize mAffineTransform and update on modification

This patch causes the InputReader to update its mAffineTransform to reflect
the currently-set calibration on startup and whenever its value is changed
through the InputManagerService.

Change-Id: I4719122a28afa9833772040f0433780a84240b9d
/frameworks/native/services/inputflinger/tests/InputReader_test.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/tests/InputReader_test.cpp