Skip to content
Commit 4559c9d3 authored by Tom Cherry's avatar Tom Cherry
Browse files

Track all published motion events in InputEventSender

"Received 'finished' signal for unknown seq number" messages occurred
before this CL when the mouse is captured due to the below sequence of
events.

1. ImeInputStage in the app uses InputEventSender to send these motion
events to the IME. These events can be batched and for batched motion
events, NativeInputEventSender::sendMotionEvent() only writes the
highest published sequence number to mPublishedSeqMap here.
2. InputConsumer::consumeSamples() consumes these events in the IME. It
takes care to create a SeqChain such that it can finish every
intermediate event.
3. The IME handles the events and calls
InputConsumer::sendFinishedSignal() which sends a finish event for
each of the events
4. The app receives these input messages from the IME and handles them in
NativeInputEventSender::notifyConsumerResponse. This function logs a
"Received 'finished' signal for unknown seq number" warning since it
only write the highest published sequence number in step 2) instead of
all of the batched signal numbers

This CL captures tracks published motion events, so that the log only
occurs for truly unexpected sequence numbers.

Bug: 268243026
Test: apps with mouse capture do not log this warning unnecessarily
Change-Id: I35b64679c7af92f00e2d2ba7651cec4ed9142f26
parent 2ef62884
Loading
Loading
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment