commit 1fb18917380f77e4e8832a0aa496701a507bae69
author Siarhei Vishniakou <svv@google.com> Tue Mar 08 10:31:39 2022 -0800
committer Siarhei Vishniakou <svv@google.com> Wed Mar 30 21:58:01 2022 +0000
tree a5c789d554f7254c488a6583a1b91a70ec651927
parent a3eab26a641c071b714a6cf578be7c7ae5b8c8d3

Log event information when event is dropped

To help debug cases where the windows and displays are misconfigured,
let's check where the touch is trying to go when the events are dropped.

Bug: 220241282
Test: atest inputflinger_tests
Change-Id: I0f678a91954a4ba2a5c6e9aca8d9200e0f368271
(cherry picked from commit 84296558f573761ecad9c858d27917f4624e7663)

services/inputflinger/dispatcher/InputDispatcher.cpp

diff --git a/services/inputflinger/dispatcher/InputDispatcher.cpp b/services/inputflinger/dispatcher/InputDispatcher.cpp
index c8a3ccf..6bab349 100644
--- a/services/inputflinger/dispatcher/InputDispatcher.cpp
+++ b/services/inputflinger/dispatcher/InputDispatcher.cpp
@@ -2350,8 +2350,8 @@
                                         *touchedWindow.windowHandle->getInfo()) ||
                                  (touchedWindow.targetFlags & InputTarget::FLAG_FOREGROUND) != 0;
                      })) {
-        ALOGI("Dropping event because there is no touched window on display %d to receive it.",
-              displayId);
+        ALOGI("Dropping event because there is no touched window on display %d to receive it: %s",
+              displayId, entry.getDescription().c_str());
         injectionResult = InputEventInjectionResult::FAILED;
         goto Failed;
     }