| e7d4775275efeca0caf7ec9106fa5b38057f2233 |
03-Mar-2018 |
Siarhei Vishniakou <svv@google.com> |
Rename a constant in VelocityTracker
Constant "SECONDS_PER_NANO" was incorrectly named.
Test: presubmit, no functional change was made
Change-Id: I9e7a70c078499cd22655a47f47c0fae8684511e7
elocityTracker.cpp
|
| 61da25aa581d2d7994b9d727b5e6f9419df68c8a |
16-Feb-2018 |
Siarhei Vishniakou <svv@google.com> |
Move SPECIAL_FUNCTION from .kcm to .idc files
Currently, the only use of device-specific .kcm files is to specify
SPECIAL_FUNCTION flag (meaning that this keyboard is only used to
perform system control functions and not for typing).
Instead of adding a special .kcm file, use .idc files with se
keyboard.specialFunction = 1 to achieve the same functionality. This
allows the removal of all device-specific .kcm files.
The .kcm functionality will remain in P (with a warning). The
functionality will be removed in Q.
Bug: 67718661
Test: tested the codepath on Android wear device via logging
Change-Id: I1b4572456fa42caae1282dd8d3557820671b3610
eyCharacterMap.cpp
eyboard.cpp
|
| 56c9ae1d334534c2f4c2857ea4b6d09feef50075 |
07-Nov-2017 |
Siarhei Vishniakou <svv@google.com> |
Fix resampling for multiple pointers
If more than one pointer is present and identical coordinates are
encountered for any pointer, the lastResample value will not be
invalidated (by clearing its bits). As a result, the same lastResample
value will be used to subsequently rewriteMessage any time in the
future. This can cause significant jumps in the pointer coordinates, and
is a bug. To further clarify, this bug has only to do with resampling
and nothing to do with both pointers having the same X or Y value.
This CL makes this logic to be per-pointer. As soon as non-identical
value is encountered and the timing conditions are such that the
resampled value is not needed to be used, the lastResample bit for that
pointer will be cleared, meaning that the value in lastResample for this
pointer is stale. This value will no longer be used anywhere.
When performing resampling, allow the process to happen on a per-pointer
basis. If one of the pointers has encountered events with identical
coordinates, then use the previously resampled value (do not resample
again), if that value is still valid (see above). Otherwise, the normal
resampling path will be taken. On the other pointers that do not have
identical coordinates, go through the normal path as well.
Bug: 68840121
Test: recorded a repro event with inputstudio and replayed it while
observing the screen. Saw that the coordinates jump before the fix,
and do not jump with the fix.
Change-Id: If43c323759de8f0184b76221d1ae599a75349ce9
nputTransport.cpp
|
| 2bc43cadc2cca889229b210f9938e815997d728b |
01-Feb-2018 |
Siarhei Vishniakou <svv@google.com> |
Use raw coordinates in VelocityTracker
Currently, VelocityTracker uses the "default" motionevent coordinates in
order to estimate the liftoff velocity of a pointer. When a view
receives a MotionEvent, the coordinates are getting adjusted relative to
the top left corner of the view. In a situation where a view itself is
moving while the user is interacting with the screen, and the view is
trying to estimate the fling velocity for a finger, this would cause
velocitytracker to use dynamic view coordinates. When these dynamically
adjusted coordinates are used in VelocityTracker, the resulting estimate
no longer accurately represents the liftoff velocity of a finger, since
the received data does not have a common origin.
Instead of using the offset-adjusted coordinates of a MotionEvent, use
the raw coordinates that are relative to the display itself and
independent of the view hierarchy.
Bug: 72263561
Test: m -j inputflinger_tests_InputReader_test
inputflinger_tests_InputDispatcher_test libinput_tests_InputChannel_test
libinput_tests_InputEvent_test
libinput_tests_InputPublisherAndConsumer_test
libinput_tests_VelocityTracker_test && adb push
out/target/product/$TARGET_PRODUCT/data/nativetest64/*
/data/nativetest64/
then run the tests on the device.
When "impulse" strategy is enabled, the velocitytracker test fails
because the flings need to be re-recorded.
Also manual fling in Google Maps (one and two finger), youtube, settings.
Change-Id: Id4d152dae00c2e6a342a71f5c89cbb5426c169ff
elocityTracker.cpp
|
| e63cbba080c9298a9b964f74d40fd2cb96873bb4 |
22-Jan-2018 |
Siarhei Vishniakou <svv@google.com> |
Revert back to lsq2 velocity strategy
Switch back to lsq2 while the bugreports for the impulse velocity
tracker strategy are investigated.
Bug: 72263561
Test: this is a revert
Change-Id: I6a2399d91f8c0225df8b90fb452a54aa42fe6894
elocityTracker.cpp
|
| 7e78b9e0b77b4ccbda27ef93ee683c186b050d82 |
12-Jan-2018 |
Siarhei Vishniakou <svv@google.com> |
Switch to impulse VelocityTracker strategy
Switch from lsq2 to impulse strategy for VelocityTracker.
Bug: 69069303
Test: flings in SystemUI and Google Maps with 1 and 2 fingers on both
Pixel 2 and Pixel 2 XL devices.
VelocityTracker_test currently fails 8 pre-recorded flings on Pixel, and
will be updated after this change has soaked in dogfood. The flings will
need to be re-recorded. Currently, in all 8 instances the reported
velocity is more than 20% smaller in magnitude than expected velocity.
m -j inputflinger_tests_InputReader_test
inputflinger_tests_InputDispatcher_test libinput_tests_InputChannel_test
libinput_tests_InputEvent_test
libinput_tests_InputPublisherAndConsumer_test
libinput_tests_VelocityTracker_test && adb push
out/target/product/$TARGET_PRODUCT/data/nativetest64/*
/data/nativetest64/
Then run test binaries on the device.
Change-Id: I952fdfdc4ecd21cdfa50ec388af7f98d1b0d8cbe
elocityTracker.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
nputTransport.cpp
ests/InputChannel_test.cpp
ests/InputPublisherAndConsumer_test.cpp
|
| b0fffdd1638cefdfdc1cdcab789ac203df08c237 |
11-Nov-2017 |
Siarhei Vishniakou <svv@google.com> |
Improve InputTransport test coverage
When sequence number is zero, then publicMotionEvent should return
BAD_VALUE. That check happens before the pointerCount check.
Therefore, this test does not currently fail due to a single
bad value of pointerCount, because it is also supplying an
invalid value for sequenceNumber. Use a valid sequenceNumber
value in this test, and add a separate test for bad value
of pointerCount.
Test: m -j libinput_tests_InputPublisherAndConsumer_test && adb push
out/target/product/$TARGET_PRODUCT/data/nativetest64/libinput_tests
/data/nativetest64
then run the binary on the target and check the output
Change-Id: I0d041870da81a1e7b95a1f83f822a0df15ee3a27
ests/InputPublisherAndConsumer_test.cpp
|
| 899c2aa1b8c7b576ddb7949ec4448956d7c5bc2c |
09-Nov-2017 |
Siarhei Vishniakou <svv@google.com> |
Revert to lsq2 VelocityTracker strategy
The impulse implementation causes high velocity
at liftoff on some hardware. Reverting back to lsq2
for now.
Bug: 35412046
Fixes: 69069303
Test: use Google Maps with 2 fingers with both strategies
Change-Id: I7138fa12468303aa3885f4731bbdacbf5c7ce3a8
elocityTracker.cpp
|
| 113254c931d280fb555b07baa4a65b07b2402024 |
03-Nov-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Switch to ImpulseVelocityTracker fling strategy."
|
| 635cb71a65d361ec107afeafcb49488f6812f7d1 |
02-Nov-2017 |
Siarhei Vishniakou <svv@google.com> |
Fix broken input tests
InputPublisherAndConsumer_test currently segfaults due to
null pointer dereference. This is because 0 is passed instead
of a valid pointer to an allocated int32_t. Also, enforce strict
compiler warnings, include signed comparisons.
Bug: 62033391
Test: m -j libinput_tests_InputEvent_test
libinput_tests_InputChannel_test
libinput_tests_InputPublisherAndConsumer_test
libinput_tests_InputTransport_test libinput_tests_VelocityTracker_test
&& adb push out/target/product/taimen/data/nativetest/libinput_tests/
/data/nativetest/
then run the above tests individually, for example
/data/nativetest/libinput_tests # ./InputPublisherAndConsumer_test
and others in a similar manner
Change-Id: Ia030cdbfa22d2bf7bdf6274a337b059ca3f9a6c3
ests/Android.bp
ests/InputEvent_test.cpp
ests/InputPublisherAndConsumer_test.cpp
|
| 13e4bdc8fc3c9cede83a1e99251235006226f67d |
02-Nov-2017 |
Siarhei Vishniakou <svv@google.com> |
Switch to ImpulseVelocityTracker fling strategy.
The current default VelocityTrackerStrategy is lsq2,
which is using second-order least squares fits to
calculate the fling velocity. However, that strategy
has a few shortcomings, which should be fixed by the
impulse strategy.
Bug: 64680775
Bug: 35412046
Test: /data/nativetest/libinput_tests/VelocityTracker_test
(test will be fixed after this CL ends by re-recording some of the
flings that fail due to the implementation change of the
impulse strategy)
Change-Id: Ib4d70bc3c88892f01d29bc1cb8f5802ace938d45
elocityTracker.cpp
|
| 973df98c8902496d2f69c9baee668816dc2619f0 |
12-Oct-2017 |
Chih-hung Hsieh <chh@google.com> |
Merge "Use -Werror in frameworks/native/libs" am: b6dabc8819 am: a1ff1045a0 am: de5c8a55e5
am: 1e6380e84d
Change-Id: I8510318912bdd097f73e21351cb0801289023442
|
| 1e6380e84dc0690caf99e5c4b635be1e4ad25df1 |
12-Oct-2017 |
Chih-hung Hsieh <chh@google.com> |
Merge "Use -Werror in frameworks/native/libs" am: b6dabc8819 am: a1ff1045a0
am: de5c8a55e5
Change-Id: I314de59ebb608645e2b9c70247af2e7511059ede
|
| a1ff1045a0b944974f5ac5a2080aadb5e83179cb |
12-Oct-2017 |
Chih-hung Hsieh <chh@google.com> |
Merge "Use -Werror in frameworks/native/libs"
am: b6dabc8819
Change-Id: Ie165a18da9b36942653062ac7529080851c8efc5
|
| 687a0d19345bb5fc669e594397370c76172362e1 |
06-Oct-2017 |
Chih-Hung Hsieh <chh@google.com> |
Use -Werror in frameworks/native/libs
* Suppress unused-variable and user-defined warnings.
* Keep sign-compare warnings to fix later.
Bug: 66996870
Test: build with WITH_TIDY=1
Change-Id: I6eee1532aa22c92ed19515ad5574734d1016d967
ests/Android.bp
|
| 219aec37372d9db514591126feb6f6ac7441442a |
05-Oct-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Different previous velocity calculation"
|
| 5d83f60f4df35d64854dd67893f7ab2ab3bbf5bc |
12-Sep-2017 |
Siarhei Vishniakou <svv@google.com> |
Enforce print format warnings in input subsystem.
Treat compiler warnings as errors. Switch to portable
print formatting of such types as uint64_t and size_t.
Bug: 64258224
Bug: 63412298
Test: m -j, interact with the phone using touch input,
check the logcat output.
Change-Id: I70a170b0b7d4ac979d997324741d0aeb2e2c458e
nputTransport.cpp
|
| 97b5e18ddf25d9f0e4eec85f0e0e80487d7fca14 |
01-Sep-2017 |
Siarhei Vishniakou <svv@google.com> |
Different previous velocity calculation
Instead of using the instantaneous velocity as the value for the
v[i-1], use the velocity equivalent of the energy accumulated so
far. This should act as a kind of a low-pass filter, and results
in lower velocity values than the current version of the algorithm.
Bug: 35412046
Test: native and CTS
1) /data/nativetest64/libinput_tests/VelocityTracker_test
This test currently fails, and we may need to modify the
expected velocity values to get it to pass with this version
of the algorithm
2) bit CtsViewTestCases:.VelocityTrackerTest
This test passes
Change-Id: I358cfd8161ec3d423a4f3126c9bcec6de1020490
elocityTracker.cpp
|
| d4b607ef71cf2d76206151ce321239cad40cdd68 |
13-Jun-2017 |
Siarhei Vishniakou <svv@google.com> |
Native test for VelocityTracker
Adding VelocityTracker native tests for checking
the velocity output for certain inputs. Adding two types of
test cases:
1) Generated manually. These are simple test cases like linear
motion, repeated coordinates, etc.
2) Generated by recording an actual fling. Used
to reproduce the swordfish fling bug referenced below.
3) Recorded flings on sailfish for additional tests.
Currently, the make target for the test is
libinput_tests_VelocityTracker_test.
Bug: 35412046
Test: adb shell /data/nativetest64/libinput_tests/VelocityTracker_test
Change-Id: I2f71100f8dc6216667b0698270a27c98cd401565
elocityTracker.cpp
ests/Android.bp
ests/VelocityTracker_test.cpp
|
| f187bb8421bd1bd795e15c66cc1d45169bdf9840 |
23-Aug-2017 |
Siarhei Vishniakou <svv@google.com> |
Fix resampling logic for duplicate events.
am: 086a02a25f
Change-Id: Idfbd41a7309e96bdd6caaa230a8a8124d1bbc4ba
|
| 086a02a25f4e24be436411d7cbe86307ae0a6ad7 |
12-Jun-2017 |
Siarhei Vishniakou <svv@google.com> |
Fix resampling logic for duplicate events.
When events with identical coordinates are
reported by the input driver, resampling can lead to
false change of direction due to extrapolation.
The added logic will compare the current event to the
previous event, and will use the previously resampled values
for the new event if the raw (as reported by the driver)
coordinates of the two events match.
This commit makes events with identical coordinates possible,
so it must be submitted together with the new impulse-based
VelocityTracker strategy commit. The currently used 2nd degree
polynomical unweighted least squares strategy cannot handle
consecutive events with identical coordinates.
Bug: 35412046
Test: Recorded bad scroll event on swordfish, and replayed
the event to reproduce this bug. To twitch is no longer observed.
Also tested common usecase scenarios on sailfish, no regressions observed.
Change-Id: Icb5cf6c76959f3514b8b94c09e38cc5434f31b23
(cherry picked from commit 0aeec07971d86c635412c672bd69d91f589a0cd9)
Merged-In: Icb5cf6c76959f3514b8b94c09e38cc5434f31b23
nputTransport.cpp
|
| 58854c2a55b3375dd1af8346f427c02eed78444c |
22-Aug-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Fix resampling logic for duplicate events."
|
| 4cd4009e811d3117d642607fc70485f26ce2bb63 |
15-Aug-2017 |
Siarhei Vishniakou <svv@google.com> |
Switch back to lsq2 VelocityTracker strategy.
The impulse VelocityTracker strategy is over-estimating
certain injected input events, used for SystemUI jank
performance tests. The current regression is caused by a combination of
improperly spaced input events and the high sensitivity of the new
strategy to that portion of the motion.
Bug: 64680775
Test: bit CtsViewTestCases:.VelocityTrackerTest
Change-Id: I4b387dcc4a13fe4295ee208490c49b2763a6bd19
elocityTracker.cpp
|
| 3992ea1b2d2c2844261aedd6eecc8be7e48b9b9a |
14-Aug-2017 |
gaoshang <gaoshang@xiaomi.com> |
Merge "use more correct case condition when consume input" am: 050861f957 am: d0198af634 am: ff99040d10
am: 75571fe9d5
Change-Id: I59da74e0e43b59e0ab559cb4a35653c98b530d02
|
| 75571fe9d54400636b1d5e2f04fd8838b34efc5e |
14-Aug-2017 |
gaoshang <gaoshang@xiaomi.com> |
Merge "use more correct case condition when consume input" am: 050861f957 am: d0198af634
am: ff99040d10
Change-Id: Ibae342909bc93ddeb7366a0da35f04938dd8846b
|
| d5338a5155c0aafaf8344fb99ae498b9e7337b6a |
12-Aug-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "New impulse-based VelocityTracker strategy."
|
| 7c870521ebb9d9bffee1b85f882b579671e97aaa |
08-Aug-2017 |
gaoshang <gaoshang@xiaomi.com> |
Merge "use more correct case condition when consume input" am: 050861f957 am: d0198af634
am: ff99040d10
Change-Id: I4e6c5ffe50057e51d47e29818c120d23fc59b890
|
| d0198af634f557f57d3c541eb00ca8d9a6460408 |
08-Aug-2017 |
gaoshang <gaoshang@xiaomi.com> |
Merge "use more correct case condition when consume input"
am: 050861f957
Change-Id: I8124f5403b5d6caf9582995c10664dee118021fe
|
| e3e11a77ccb2fc23c55a868df482fa738315cb0c |
08-Aug-2017 |
gaoshang <gaoshang@xiaomi.com> |
use more correct case condition when consume input
InputMessage::TYPE_MOTION instead of AINPUT_EVENT_TYPE_MOTION
Although these two values are the same
Test: input
Change-Id: Ic1478cf2a5ef1706844d89428ef3a7e999877bcc
Signed-off-by: gaoshang <gaoshang@xiaomi.com>
nputTransport.cpp
|
| 0aeec07971d86c635412c672bd69d91f589a0cd9 |
12-Jun-2017 |
Siarhei Vishniakou <svv@google.com> |
Fix resampling logic for duplicate events.
When events with identical coordinates are
reported by the input driver, resampling can lead to
false change of direction due to extrapolation.
The added logic will compare the current event to the
previous event, and will use the previously resampled values
for the new event if the raw (as reported by the driver)
coordinates of the two events match.
This commit makes events with identical coordinates possible,
so it must be submitted together with the new impulse-based
VelocityTracker strategy commit. The currently used 2nd degree
polynomical unweighted least squares strategy cannot handle
consecutive events with identical coordinates.
Bug: 35412046
Test: Recorded bad scroll event on swordfish, and replayed
the event to reproduce this bug. To twitch is no longer observed.
Also tested common usecase scenarios on sailfish, no regressions observed.
Change-Id: Icb5cf6c76959f3514b8b94c09e38cc5434f31b23
nputTransport.cpp
|
| 00a4ea970bab16ef5675e866cd856a0d9919f0c5 |
08-Jun-2017 |
Siarhei Vishniakou <svv@google.com> |
New impulse-based VelocityTracker strategy.
New velocity calculation strategy for VelocityTracker.
The strategy models the phone screen as a physical object
that gets pushed by the finger. Upon liftoff, the total
work done on the object (past 100ms of data and at most
20 most recent samples) is considered to be kinetic energy,
which gets converted into equivalent velocity.
Works well with "bad" data - unclean touch liftoff,
repeated coordinates. Time-shift invariant. Performance
otherwise similar to the current default strategy,
quadratic unweighted least squares.
Bug: 35412046
Test: Recorded bad scroll event on swordfish, this fixes the
fling in the wrong direction. Also tested common usecase
scenarios on sailfish, no regressions observed. Similar
velocity values to lsq2 strategy.
Change-Id: Ib439db0ce3b4fe84f59cf66683eae0b5df7776eb
elocityTracker.cpp
|
| 986678fc37edfee2b0d1a9120146a9310216c55a |
04-Aug-2017 |
Siarhei Vishniakou <svv@google.com> |
Merge "Faster unweighted 2nd degree least squares algo."
|
| 50010a893911f56cbe02c500df9c1d8858ee71e8 |
03-Aug-2017 |
Tarandeep Singh <tarandeep@google.com> |
Merge changes from topic '62033391' into oc-dr1-dev
am: 97d1c4f234
Change-Id: I33111bae2e009087d979b5f83b0d76a6ba9328c1
|
| 13c058fc180b1b1831ca52cc4a9c13d59ec67c34 |
03-Aug-2017 |
Tarandeep Singh <tarandeep@google.com> |
Merge changes from topic '62033391' into oc-dr1-dev am: 97d1c4f234
am: e6e2e1b431
Change-Id: I90d6d35abf452d61bc0a9dc0fe21848a483f6f9f
|
| 58641508af4e3d3f553ff7e73304866755cfbd5b |
31-Jul-2017 |
Tarandeep Singh <tarandeep@google.com> |
Add displayId in InputDispatcher, InputTransport
Bug: 62033391
Test: make StructLayout_test
make libinput_tests_InputEvent_test
make libinput_tests_InputPublisherAndConsumer_test
Run tests under /data/nativetest64/libinput_tests/
Change-Id: Id02cab83924d399eae0c1c233dc545fbb64945c2
nputTransport.cpp
ests/InputPublisherAndConsumer_test.cpp
ests/StructLayout_test.cpp
|
| ec2727e9835be89263ca1170ad62dbaba0980737 |
06-Jul-2017 |
Siarhei Vishniakou <svv@google.com> |
Convert String8 to std::string
String8 is deprecated.
Test: m -j and uncomment DEBUG flags
in VelocityTracker to view coordinates
in logcat.
Change-Id: I968685765f06418be73fbb8ad2747a1fe8ed324e
ndroid.bp
elocityTracker.cpp
|
| 7b9d189574fdf530df9c2e30e4fd799c9a25e6b4 |
06-Jul-2017 |
Siarhei Vishniakou <svv@google.com> |
Fix SIGABRT caused by integer sanitizer.
Test: m -j and use flings in settings menu.
Change-Id: I7c15c610ed2d74b128a2924c097fb7dc351ea5f4
elocityTracker.cpp
|
| 489d38e219a0f8ba35f9d4e1a9ebee0b4d62ca3e |
16-Jun-2017 |
Siarhei Vishniakou <svv@google.com> |
Faster unweighted 2nd degree least squares algo.
Speed up the default velocity computation that uses
unweighted second degree least squares approach.
Only calculate the linear coefficient, single loop
with O(n) complexity. About 2x speedup.
Test: dumped the original and the new values while
flinging settings. Observed nearly identical
velocity results (less than 0.1% difference).
Also ran CTS test:
tools/cts-tradefed run cts -t android.view.cts.VelocityTrackerTest -m
CtsViewTestCases --skip-system-status-check
com.android.compatibility.common.tradefed.targetprep.NetworkConnectivityChecker
Change-Id: I7ddbd85a092f44e8d4b5f109c386af5dd589d249
elocityTracker.cpp
|
| c1f060e6f3a299c51c10f35810a9670a526bba9a |
24-May-2017 |
gaoshang <gaoshang@xiaomi.com> |
Merge "Fix a anr bug caused by sendFinishedSignal logical error" am: 77bee3b429 am: 9d5bddcded
am: 251baedfaf
Change-Id: I34210fcd813c2118f0fa4814884b4adadacc415f
|
| 9090d4faae02e8e4dde45851d2969e7e62d40c9b |
17-May-2017 |
gaoshang <gaoshang@xiaomi.com> |
Fix a anr bug caused by sendFinishedSignal logical error
Because of eliminate multiple benign overflow conditions see:
https://android-review.googlesource.com/#/c/172237/
Changed the do while loop resulting in a logical difference.
When the chainIndex-- to 0, the loop is not run.
It is the most important cycle, it will push head seq to mSeqChains.
If not run, will lead to a batch of seq can not corrected finish.
Eventually leading to the occurrence of anr.
Signed-off-by: gaoshang <gaoshang@xiaomi.com>
Test: Input dispatche process
Bug: 38366215
Change-Id: I87e609dfcb00ac7b8e82c6de789df094e7c25efd
nputTransport.cpp
|
| 9e94788e8a8388eeb1113dc42c932ed42008de5d |
06-Mar-2017 |
Frank Barchard <fbarchard@google.com> |
InputDevice warning fixes and make warnigs into Error
use const char * for string literals in InputDevice
Remove unused variable in Keyboard
Bug: 35993509
Test: mm in frameworks/native/libs/input builds without the warning
Change-Id: I11242835eae855386c47e56d6c36e5a2f912a28f
ndroid.bp
nputDevice.cpp
eyboard.cpp
|
| 7ead73ed26403405bddd625c6ea0f009bff92939 |
28-Feb-2017 |
Jaekyun Seok <jaekyun@google.com> |
Treblize input device config file location
Treblization requires to locate partner-specific configs in its own
partition. So the input device config file could be located in
/odm/usr or /vendor/usr.
This CL is to support those locations for the config.
Test: building succeeded and tested on sailfish.
Bug: 35815587
Change-Id: Ib6ae230118c8dc45dc030b32eb59441c3a544535
nputDevice.cpp
|
| de98297153ff3e7cccf28a1e90e204d29c299158 |
01-Feb-2017 |
Evgenii Stepanov <eugenis@google.com> |
Disable integer sanitization on host.
Test: NFC until https://android-review.googlesource.com/#/c/329510
Change-Id: I0183556d5b945c689934664fe7f15caa18a0997d
ndroid.bp
|
| 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
nputTransport.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
nputTransport.cpp
|
| e390826e3871b68c6a282eef71d8f92bc7758378 |
08-Oct-2016 |
Elliott Hughes <enh@google.com> |
Rely on the platform -std default.
Bug: http://b/32019064
Test: builds
Change-Id: Ie2df259641889b3ce95648bd2be48d061108162c
ests/Android.bp
|
| c7dd2b905d83cbf7ee98792142a4d078e7cfbb39 |
26-Aug-2016 |
Dan Willemsen <dwillemsen@google.com> |
Convert libui to Android.bp
Along with the libinput tests, which depend on libui. For more
information on Soong, see build/soong/README.md
Change-Id: Id4fbeb114d03e37556dca59a2c9f5c9abb0a1825
Merged-In: Id4fbeb114d03e37556dca59a2c9f5c9abb0a1825
(cherry picked from commit 871dda3d6485617bf3a1ea6c8236071212234433)
ndroid.bp
ndroid.mk
ests/Android.bp
ests/Android.mk
|
| 2a001e8bfe0255242740df7d9674408820f13627 |
05-Aug-2016 |
Dan Willemsen <dwillemsen@google.com> |
resolve merge conflicts of 0783d5f to stage-aosp-master
Change-Id: I4fe9c0391d6d41bae5fbbb0df6e00e264e87649f
|
| 59e086f536e1dbbbfe9cb6a1826aaddef999d5ce |
26-Jul-2016 |
Dan Willemsen <dwillemsen@google.com> |
Start converting Android.mk to Android.bp
See build/soong/README.md for more information.
Merged-In: Ifbe9b0072a63b4467c72b3a52148a606e5365f78
Change-Id: Ifbe9b0072a63b4467c72b3a52148a606e5365f78
ndroid.bp
ndroid.mk
|
| ce244b87888fa2ba5e2414801159b70848ec9673 |
20-May-2016 |
Chih-hung Hsieh <chh@google.com> |
Merge "Fix misc-macro-parentheses warnings in test macros." am: 23d433c576
am: eb209a41f1
* commit 'eb209a41f14a30ceccbd52ee254181e36a8a318a':
Fix misc-macro-parentheses warnings in test macros.
Change-Id: Ia7f58971d3c828fa0bed800585cec3ca446ca655
|
| 4a186d4579655eec4122369d5bd39a8ce9ece054 |
20-May-2016 |
Chih-Hung Hsieh <chh@google.com> |
Fix misc-macro-parentheses warnings in test macros.
Bug: 28705665
Change-Id: I6e64ccdae5869b66a3caa09d8f32b2fcc9c1b2b9
ests/StructLayout_test.cpp
|
| 68a593e7fa07c947fef2c5de53c42e14ed630a8a |
28-Apr-2016 |
Chih-Hung Hsieh <chh@google.com> |
resolve merge conflicts of 168dc86 to nyc-dev-plus-aosp
Change-Id: I1554cec6ea880a87921f723bc96972cb8e1d3c5c
|
| e2347b7953f70232541bdc1b392230d6231aaeb9 |
26-Apr-2016 |
Chih-Hung Hsieh <chh@google.com> |
Fix google-explicit-constructor warnings.
Bug: 28341362
Change-Id: I0ce850de85e0de6a5472dd142f738856142db9ec
InputFlinger.cpp
|
| d57d9b900da83b1b5431d90e250f86c0047c618a |
19-Feb-2016 |
Ian Pedowitz <ijpedowitz@google.com> |
Revert "Revert "Fix warnings in servicemanager and KeyCharacterMap""
This reverts commit b480269b0f8e933fa6fc6bd4c9e1e504e1b51508.
Change-Id: If405c0786c5bdd02e3f2c3356d56a4200c6b9dfb
eyCharacterMap.cpp
|
| b480269b0f8e933fa6fc6bd4c9e1e504e1b51508 |
19-Feb-2016 |
Ian Pedowitz <ijpedowitz@google.com> |
Revert "Fix warnings in servicemanager and KeyCharacterMap"
This reverts commit d3b4c050f6bcdfd44bfb9c8ed885fd1c482c50bb.
Change-Id: I961f89d4446ac23f0e267c6541b504c4ec6b3af1
eyCharacterMap.cpp
|
| d3b4c050f6bcdfd44bfb9c8ed885fd1c482c50bb |
19-Feb-2016 |
Aurimas Liutikas <aurimas@google.com> |
Fix warnings in servicemanager and KeyCharacterMap
- Suppress unused parameter warnings.
- Remove a few unused parameters.
- Set the correct formatting for size_t log.
Bug: 26936282
Change-Id: I2e2acb15d1bc05c6ba09563a87d5baceebe7ebd9
eyCharacterMap.cpp
|
| 4c971c001f401d7742db326c8e5654693eb3687e |
21-Oct-2015 |
Michael Wright <michaelwr@google.com> |
Limit the number of keys read by KeyCharacterMaps.
Apps can send us a KCM containing a ridiculous key count, which will
cause us to crash when an allocation fails. Limit the key count so this
doesn't happen.
Bug: 24876135
Change-Id: I2bb4a5acabfc9184a867a406eef756c28c28f0ad
eyCharacterMap.cpp
|
| 0ee1b1ff1f454e72a5b2ef2fbe78f7b66eba8bd4 |
13-Oct-2015 |
Adam Lesinski <adamlesinski@google.com> |
am 5bba4236: am 76fc5f18: am 16b0ae10: Merge "add number constraint for samples per MotionEvent" into mnc-dr-dev
* commit '5bba4236a86bbf4537bc27810803b9b224b0840f':
add number constraint for samples per MotionEvent
|
| 16b0ae105e4e94ff09d1517b68f7c66f2022a19e |
13-Oct-2015 |
Adam Lesinski <adamlesinski@google.com> |
Merge "add number constraint for samples per MotionEvent" into mnc-dr-dev
|
| 552a8a5d8df32f659b8d11311a244cdc6d3b7733 |
07-Sep-2015 |
Flanker <i@flanker017.me> |
add number constraint for samples per MotionEvent
Bug:23905002
Change-Id: Ifd24802977c3dcdd1dbc5120a78aac41beae4603
Signed-off-by: Adam Lesinski <adamlesinski@google.com>
nput.cpp
|
| 3b9211608669eb5aafba65d35b4cfbec89755499 |
08-Oct-2015 |
Dmitry Torokhov <dtor@google.com> |
resolved conflicts for b9163905 to mnc-dr-dev-plus-aosp
Change-Id: I83afd79491533b1c7ae2aed50a927db175ba555f
|
| 2f3c3eb4e47d7cb6ef67e0fd2063e4b93e38e9ec |
08-Oct-2015 |
Puneet Kumar <puneetster@google.com> |
Merge "Allow defining replacement key events in keymap" into mnc-dr-dev
|
| d120254f5ec511f441e5d4e8942b16068294afad |
02-Oct-2015 |
Andrew de los Reyes <adlr@google.com> |
am c9b39239: am 6c51a07d: am de18f6c3: InputResampling: Don\'t extrapolate for very low frame rates.
* commit 'c9b392395f3eada767cf9d1dce1eb40930ca1b95':
InputResampling: Don't extrapolate for very low frame rates.
|
| de18f6c32add6fb22065807a00ddc88b363df527 |
02-Oct-2015 |
Andrew de los Reyes <adlr@google.com> |
InputResampling: Don't extrapolate for very low frame rates.
In very low framerate situations, extrapolation is generally going to
either cause no benefit or make a mistake. We can safely turn it off
with no user-visible negative impact.
BUG=https://buganizer.corp.google.com/u/0/issues/24550942
TEST=Scrolled very slowly and saw mispredictions on Angler. With change,
saw the log message that the mispredictions were suppressed.
Change-Id: Ic9747d3ff098d7918047ada2ed1c2d21282c65b0
nputTransport.cpp
|
| 115f93eeebf7f33b56ed090de70d6e8c733e5d88 |
18-Sep-2015 |
Dmitry Torokhov <dtor@google.com> |
Allow defining replacement key events in keymap
Currently keyboard maps allow to assign character sequences to key
events and allow specifying a so-called "fallback" key events that are
re-injected into input stream if target application indicates that it
was not able to handle the original key event. Unfortunately there is no
way to perform substitution before handing the event to applicationis.
This change adds a new keymap keyword "replace" that allows users query
"replacement" actions for key (if any), with the intent that such
replacement happens early in the event handling process.
Bug: 24504154
Change-Id: I3e6a2476c856524171df00ad22ff56f2018c1278
eyCharacterMap.cpp
eyboard.cpp
|
| 476398ab60f4f777b0d7c85986f0185350468d5d |
23-Sep-2015 |
Dan Austin <danielaustin@google.com> |
am 0830bb16: Merge "Enable integer overflow sanitization in libinput."
* commit '0830bb169717f920817e66afb18abe2c86d20161':
Enable integer overflow sanitization in libinput.
|
| 0ba3db9e91d683a75af244cccfa62c8778a4c62a |
23-Sep-2015 |
Dan Austin <danielaustin@google.com> |
am bffbd09f: Merge "Eliminate multiple benign overflow conditions."
* commit 'bffbd09f65d3bc594d844a185d75700e8b4789eb':
Eliminate multiple benign overflow conditions.
|
| 29b3555f344471de8e08ed00e5df4451aa953a8d |
22-Sep-2015 |
Dan Austin <danielaustin@google.com> |
Enable integer overflow sanitization in libinput.
Bug: 24171356
Change-Id: I1412b78171c60b0252560956a672f2d92a7011e6
ndroid.mk
|
| bffbd09f65d3bc594d844a185d75700e8b4789eb |
23-Sep-2015 |
Dan Austin <danielaustin@google.com> |
Merge "Eliminate multiple benign overflow conditions."
|
| c6a6c6de7c43198dc93f92f935ebc120de1050c8 |
23-Sep-2015 |
Dan Austin <danielaustin@google.com> |
am ad2a1592: Merge "Enable multiple benign overflow conditions."
* commit 'ad2a1592cf01a5393ad645fea81b6c36ee11f73e':
Enable multiple benign overflow conditions.
|
| fc6a2bff11e342acb3c098bc2be7557e0876efac |
23-Sep-2015 |
Dan Austin <danielaustin@google.com> |
am 146f31b6: Merge "Eliminate benign overflow condition triggered upon loop termination in Input.cpp"
* commit '146f31b6c44f557270779106e95c769783270fed':
Eliminate benign overflow condition triggered upon loop termination in Input.cpp
|
| ad2a1592cf01a5393ad645fea81b6c36ee11f73e |
23-Sep-2015 |
Dan Austin <danielaustin@google.com> |
Merge "Enable multiple benign overflow conditions."
|
| 1faef80170b71ee4162dc910bfe1aea9d7181e58 |
22-Sep-2015 |
Dan Austin <danielaustin@google.com> |
Eliminate multiple benign overflow conditions.
In InputTransport.cpp, there are multiple loops in which loop
termination occurs when the value becomes zero. These termination
conditions are all written value-- > 0, which, since value is
unsigned, result in an unsigned integer overflow when value is 0.
These loops were refactored to eliminate these conditions.
Bug: 24171356
Change-Id: Ie135c4306d1f2cef2778e295242305ed5139221a
nputTransport.cpp
|
| 389ddbad52b32beeee6d3f361145b7431bae3536 |
22-Sep-2015 |
Dan Austin <danielaustin@google.com> |
Enable multiple benign overflow conditions.
In VelocityTracker.cpp, there are multiple loops in which loop
termination occurs when the value becomes zero. These termination
conditions are all written value-- > 0, which, since value is
unsigned, result in an integer overflow condition when value is 0.
These loop were refactored to eliminate these conditions.
Bug: 24171356
Change-Id: Ie44940cfef8a122ee1aff59c021274ba39a368bf
elocityTracker.cpp
|
| c94fc45bc5c07724e63e4da5151cfea90bd87986 |
22-Sep-2015 |
Dan Austin <danielaustin@google.com> |
Eliminate benign overflow condition triggered upon loop termination in Input.cpp
In readFromParcel, a while loop is terminated when sampleCount = 0. The
decrement operation that was here would decrease sampleCount, an unsigned value,
below 0, triggering an unsigned integer overflow. The while loop was refactored
to eliminate this condition.
Bug: 24171356
Change-Id: I7669f54a41d11548b33e322b025431c6f6038952
nput.cpp
|
| c6ada3b169827f581cd61749c6056c4209ebb650 |
13-Aug-2015 |
Elliott Hughes <enh@google.com> |
am 6a846dd5: am 5f5a0e0f: Merge "Lose HAVE_ANDROID_OS from frameworks/native."
* commit '6a846dd51885df861f4e1e30fcca86b9dd2f4092':
Lose HAVE_ANDROID_OS from frameworks/native.
|
| 6071da7ef84c60645572654504813d492b8b21d5 |
13-Aug-2015 |
Elliott Hughes <enh@google.com> |
Lose HAVE_ANDROID_OS from frameworks/native.
Change-Id: I8e6af2a46a9d875192fc7957ada9b5f66d84bad6
nput.cpp
eyCharacterMap.cpp
|
| b03f103fd40d9028731a81e87a817a3e3bd07fa4 |
14-May-2015 |
Michael Wright <michaelwr@google.com> |
Fix input tests to work with new MotionEvent member
Change-Id: I0dde0f91f693903f26edc116b5dbcbf33bac2b93
ests/InputEvent_test.cpp
ests/InputPublisherAndConsumer_test.cpp
ests/StructLayout_test.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.
nput.cpp
nputTransport.cpp
|
| 70b41ef580644fd0fe6fa9b8ac7e4a745cfb6db3 |
14-May-2015 |
Michael Wright <michaelwr@google.com> |
Revert "Add new MotionEvent actions for button press and release."
This reverts commit 48a8a0e4322969e1551536d6183af3a1faa2240b.
nput.cpp
nputTransport.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
nput.cpp
nputTransport.cpp
|
| 063ff53d0b0a0d670ea0185e687526d8fd302820 |
08-Apr-2015 |
Tim Kilbourn <tkilbourn@google.com> |
Pass through availability of audio mic for input devices.
Bug: 15374820
Change-Id: Id2ca6da10165e3a887ebfbb18f663a3bf316ac79
nputDevice.cpp
|
| 94ba882df2aac6d0cf35b6ae445b95d247662e9d |
12-Sep-2014 |
Dan Albert <danalbert@google.com> |
am 4355c0c9: am e1e3d278: Merge "Clean cruft out of makefiles."
* commit '4355c0c98644c37f0511257403bbfb71b342e2df':
Clean cruft out of makefiles.
|
| 4355c0c98644c37f0511257403bbfb71b342e2df |
12-Sep-2014 |
Dan Albert <danalbert@google.com> |
am e1e3d278: Merge "Clean cruft out of makefiles."
* commit 'e1e3d278549eb6389eb0b5fa3f13a4ac079a55a2':
Clean cruft out of makefiles.
|
| b79dfe672138805b4f70183fd738d9af58591148 |
12-Sep-2014 |
Dan Albert <danalbert@google.com> |
Clean cruft out of makefiles.
Cleans up manual uses of stlport and bionic (and removes uses of private
bionic headers).
Change-Id: I157309d702e59152adfa3450939082248ae4c043
ests/Android.mk
|
| 62fbb16383d6d8268821f947e2c6d0828f7e2b41 |
18-Aug-2014 |
Michael Wright <michaelwr@google.com> |
Shelve InputFlinger for another release. DO NOT MERGE
Change-Id: I0f034a2b8b1d9192f61f5001799bd3aa4b3964c7
ndroid.mk
InputFlinger.cpp
|
| 63ff3a84ae5f60fc427aed4f63364b50695266d9 |
10-Jun-2014 |
Michael Wright <michaelwr@google.com> |
Fixup more potential issues / warnings in string formats
Change-Id: I323e44f950b2e758dc9ff4510b2e13ca870eb849
nputTransport.cpp
|
| d0a4a6234f3d97f5e7fb86b028d3ee79dd4e3fa6 |
10-Jun-2014 |
Michael Wright <michaelwr@google.com> |
Fix warning in logging string interpolation
Change-Id: I86623083f68664d31ea277958837a4c2985037b4
nputTransport.cpp
|
| db1972bd8e9b055f2df77d57ac55f1c02ebdd278 |
03-Jun-2014 |
Narayan Kamath <narayan@google.com> |
am 26063a91: am f1dd859b: Merge "x86_64: Align uint64_t/int64_t structure member to 8 bytes"
* commit '26063a9155ddd18d858cea7fac7c1ddf71e1bcb7':
x86_64: Align uint64_t/int64_t structure member to 8 bytes
|
| 26063a9155ddd18d858cea7fac7c1ddf71e1bcb7 |
03-Jun-2014 |
Narayan Kamath <narayan@google.com> |
am f1dd859b: Merge "x86_64: Align uint64_t/int64_t structure member to 8 bytes"
* commit 'f1dd859baa114995bcbcfb7119e939d0b4f45ed5':
x86_64: Align uint64_t/int64_t structure member to 8 bytes
|
| 83e0e425c61c4e03f61114a88f117db1553cd44c |
23-May-2014 |
Fengwei Yin <fengwei.yin@intel.com> |
x86_64: Align uint64_t/int64_t structure member to 8 bytes
To make sure the stature which pass between 32/64bit process have
same memory layout for 32/64bit.
Signed-off-by: Fengwei Yin <fengwei.yin@intel.com>
Co-Authored-by: Narayan Kamath <narayan@google.com> (Unit test only.)
Change-Id: I1bc2d12cce41ec0bc484adcaf968f274bec75c12
ests/Android.mk
ests/StructLayout_test.cpp
|
| f8c66b4bee9ab0203b83ea3a6df8f49fad443d88 |
16-May-2014 |
Narayan Kamath <narayan@google.com> |
am cfba3bf1: am c9fcaf37: Merge "Change InputMessage.motion.pointerSize to a uint32_t."
* commit 'cfba3bf1606dfdb1daf1be1c19176180660ae19d':
Change InputMessage.motion.pointerSize to a uint32_t.
|
| ed5fd384b7401fbb6143eb7107cbfe9af46116be |
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.
(cherry-picked from bc6001b026069714177526eb1120b0011d6f2a51)
Change-Id: I28e87050478920a54132efbbb8138076ebad1409
nputTransport.cpp
|
| b8290c2642ec7a0cb8a1703a7e1e8958a6a5f9f3 |
06-May-2014 |
Narayan Kamath <narayan@google.com> |
Fix InputEvent_test.
Axis 0 sets the MSB and Axis 63 sets the LSB, and not
the other way round like the test expects.
This was broken by commit 38dcdff3087f01 which moved this
code over to using BitSet.
Change-Id: I63a72abe7ce14720b0bf26e5f6d651bb42452f79
ests/InputEvent_test.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
nputTransport.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
nput.cpp
nputTransport.cpp
eyCharacterMap.cpp
eyLayoutMap.cpp
eyboard.cpp
|
| d0bd3911462f42487944dbaf85d87d569e2f9633 |
19-Mar-2014 |
Michael Wright <michaelwr@google.com> |
Generate ACTION_CANCEL on joystick disconnect. DO NOT MERGE
Bug: 11480300
Change-Id: I5a4096970c9e588d134f05dd0eb3a9c91c836b2f
nput.cpp
|
| 38dcdff3087f01ba02aabfc17b3ff6c549bb5707 |
19-Mar-2014 |
Michael Wright <michaelwr@google.com> |
Generate ACTION_CANCEL on joystick disconnect.
Bug: 11480300
Change-Id: I46706838eec0711c6bf345301e7b4ccbad83b063
nput.cpp
|
| 962a108856767d6f5c17cf2854b13fef0315f8ca |
18-Oct-2013 |
Michael Wright <michaelwr@google.com> |
Parse LED mappings in keylayout files. DO NOT MERGE
Change-Id: I2b34939cc0df256e6b872502ea93f2884b4c8334
eyLayoutMap.cpp
eyboard.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
nput.cpp
|
| ed4d28dd70448b13eb74a3166ec8d1c1a530e2d4 |
11-Feb-2014 |
Jeff Brown <jeffbrown@google.com> |
Add method to apply offset to PointerCoords. (DO NOT MERGE)
Change-Id: I3dc2ba22b026e5b8e1c3d90f7366ec09a59ce6b6
nput.cpp
|
| 2130192c78d872e2c605648e6eadde8ff655463d |
22-Oct-2013 |
Michael Wright <michaelwr@google.com> |
am 47f0b989: am 3223217a: Only consume touches up until the frame time
* commit '47f0b9894b78a76a1257e0f3299cbe5446035c09':
Only consume touches up until the frame time
|
| 3223217aed6dcfa55b5b952cd6be71f70e41ba63 |
21-Oct-2013 |
Michael Wright <michaelwr@google.com> |
Only consume touches up until the frame time
When resampling is disabled, it's currently possible to consume
touches after the current frame time. This breaks some guarantees and
could cause unexpected behaviors.
Change-Id: I99908a2cac2df9f795dd4a07188b4451213cf3e4
nputTransport.cpp
|
| 74bdd2e7ceabd3c9e74ccf7c2e6bd3dae27ca497 |
18-Oct-2013 |
Michael Wright <michaelwr@google.com> |
Parse LED mappings in keylayout files
Change-Id: I6bc3760341868015f054d9866e2616a312da94e0
eyLayoutMap.cpp
eyboard.cpp
|
| 218566c303c7b71d6991dce2dfdd8d718659c368 |
11-Oct-2013 |
Dave Burke <daveburke@google.com> |
am 06c964d9: am 9c0dfa09: Merge "Eliminate latency when resampling is disabled" into klp-dev
* commit '06c964d9b31ac81d3521f97427cdab77ee7d1cff':
Eliminate latency when resampling is disabled
|
| ad526f8505efe2ccd800e4665864b10bdae31e29 |
11-Oct-2013 |
Michael Wright <michaelwr@google.com> |
Eliminate latency when resampling is disabled
Since the latency was introduced to avoid egregious errors during
resampling, remove it when we aren't resampling.
Change-Id: Ia8e9a9afb1e16212fec81a8c9c661c598e1b0ebf
nputTransport.cpp
|
| 464febc44908fb4a8fca9e513ba8469750dde838 |
23-Aug-2013 |
Jeff Brown <jeffbrown@google.com> |
Remove input flinger stubs. (DO NOT MERGE)
Bug: 10446930
Change-Id: I4dd46f539cd2a2e324dfc83b45ba2787f7404a4a
ndroid.mk
InputFlinger.cpp
|
| 0415d63b1adf15f6546fea902c66f8bd508afbfc |
17-Jul-2013 |
Michael Wright <michaelwr@google.com> |
Add controller numbers for gamepads / joysticks
Change-Id: I5294aabbadb836a6a4c7ce76a670abcf50c1f885
nputDevice.cpp
|
| e5bb2a45e0861c7ed953373f86afe44f255f021c |
20-Jul-2013 |
Michael Wright <michaelwr@google.com> |
Merge "Add input device property for buttons under touchpads"
|
| 7556c37b1c1ddd82801bc9ea4cea1ade4d380a98 |
16-Jul-2013 |
Jeff Brown <jeffbrown@google.com> |
Merge "Completely remove skia dependency from libinput."
|
| 313eff7bb7e5eedbdbea805343451fd473241266 |
16-Jul-2013 |
Jeff Brown <jeffbrown@google.com> |
Completely remove skia dependency from libinput.
Including the tests...
Change-Id: I6ec8f1a5ae7e7514831d7e3b430b3b37b0841b92
ests/Android.mk
ests/InputEvent_test.cpp
|
| 174c26045c79c56acbd95f1644a72ca512c75134 |
16-Jul-2013 |
michaelwr <michaelwr@google.com> |
Merge "Add a keycode to switch audio tracks (2/2)"
|
| 5a2f68e5a5526ba80b5192776e2f0e349626777d |
16-Jul-2013 |
Jeff Brown <jeffbrown@google.com> |
Fix PDK build.
Quick hack to remove Skia dependency from libinput.
Change-Id: Ibaf2e312236f5e3f7251fa903ce381456a77467c
ndroid.mk
nput.cpp
|
| 40c9e0a3989222b4c27c88f54b6acf67b58a68cf |
15-Jul-2013 |
Jeff Brown <jeffbrown@google.com> |
Add skeleton of input flinger.
Change-Id: I7f25080e446d4d3d9de9b18fe432a09bc751e0d9
ndroid.mk
InputFlinger.cpp
|
| 8d06dcf9c663cccc44318c01c13f2b3ba0001b4c |
08-Jul-2013 |
Jaekyun Seok <jaekyun@google.com> |
Add a keycode to switch audio tracks (2/2)
A key to switch audio tracks is general on media devices like blu-ray.
Bug: 9728155
Change-Id: I13ebbc64321f3cf10370f9a605f3d94ea0d16d6d
nput.cpp
|
| 931fd6dee7891e94650353c09956ccf24b4dfff3 |
11-Jul-2013 |
Michael Wright <michaelwr@google.com> |
Add input device property for buttons under touchpads
Bug: 8990644
Change-Id: I6df5fb9e11199173d62523928082db428af55394
nputDevice.cpp
|
| 80b5cf9934b8f450d8c1145f0f937ff40829c81b |
02-Jul-2013 |
keunyoung <keunyoung@google.com> |
do not build libinput in PDK
- skia is not available in PDK, and it causes build break.
bug: 9528927
Change-Id: I89663e4a4bd52858506e3b52fbf8ca85d9992363
ndroid.mk
|
| 5912f95d26f77d2b6df13e1f2672e48e3f9b871c |
02-Jul-2013 |
Jeff Brown <jeffbrown@google.com> |
Move input library code from frameworks/base.
Change-Id: I4983db61b53e28479fc90d9211fafff68f7f49a6
ndroid.mk
nput.cpp
nputDevice.cpp
nputTransport.cpp
eyCharacterMap.cpp
eyLayoutMap.cpp
eyboard.cpp
elocityControl.cpp
elocityTracker.cpp
irtualKeyMap.cpp
ests/Android.mk
ests/InputChannel_test.cpp
ests/InputEvent_test.cpp
ests/InputPublisherAndConsumer_test.cpp
ests/TestHelpers.h
|