diff options
| author | 2025-02-07 12:33:04 +0000 | |
|---|---|---|
| committer | 2025-02-07 12:33:04 +0000 | |
| commit | 7757972fb5eee0af170c76c0cfa9d8b9df1b8761 (patch) | |
| tree | 0cf49655d67691e7b8e681231322d6cfd74e2160 /libs/androidfw/misc.cpp | |
| parent | 76f60eea22f9f3a6ff2d9bfc0a199ce1daa8f6ea (diff) | |
InputEventConsistencyVerifier: only check actual trackball events
The trackball event verification code hasn't been changed since 2011.
Since then, we've introduced InputDevice.SOURCE_MOUSE_RELATIVE (with
SOURCE_CLASS_TRACKBALL), which uses some different action types than
actual trackballs. This was causing the verifier to report problems
whenever a captured mouse emitted any action other than DOWN, MOVE, or
UP, meaning that valid BUTTON_PRESS, BUTTON_RELEASE, and SCROLL events
were causing errors to appear in logcat.
To avoid this, only apply the trackball validation logic to actual
trackballs.
Test: capture the mouse with a test app, click the buttons and scroll,
and check that no "Invalid action" messages appear under the
InputEventConsistencyVerifier log tag
Bug: 394541626
Flag: EXEMPT bug fix
Change-Id: I2ab57d9680817d396d01e720c36b80c6fe3320f0
Diffstat (limited to 'libs/androidfw/misc.cpp')
0 files changed, 0 insertions, 0 deletions