diff options
| author | 2021-10-14 10:57:37 +0000 | |
|---|---|---|
| committer | 2021-10-27 05:42:28 +0000 | |
| commit | b3307ee4952e372da4bfd57b71085c3a55ade5f0 (patch) | |
| tree | a62d48e7b9c8eb9b4c78ed336aa57f6968c8bab2 /libs/gui/BLASTBufferQueue.cpp | |
| parent | f367330f19ba02797ed82382ab10a5cd51e7db97 (diff) | |
Add logs to trace no window touched and cancel event
To clarify some unresponsive touch problems, we have to know if the
event has really sent from firmware and some window could be touched
or it's dropped because of cancel.
- Add the explicit log where we did not really find a touched window.
- Add input_cacnel event log to identify the reason.
Test: atest inputflinger_tests
Bug: 201647070
Bug: 200837970
Change-Id: I17b1de6c96ddc11d2ca2efd00e30e00847b98406
Diffstat (limited to 'libs/gui/BLASTBufferQueue.cpp')
0 files changed, 0 insertions, 0 deletions