Add InputConnection app and service dump

This change dumps information through IME tracing for the getter methods
exposed by the InputConnection interface. The dump is done through the
ImeTracing interface and is triggered by events in the wrapper classes
used to handle InputConnection implementations corresponding to:
 - different apps
 - InputMethodService
The new data is available under inputConnectionCall in the clients
output proto.

Bug: 154348613
Test: flash a device
      start IME tracing by calling "adb shell ime tracing start"
      end IME tracing by calling "adb shell ime tracing stop"
      pull generated trace files and visualize in Winscope
      or start tracing directly through ADB Connect and visualize traces
Change-Id: Iabd6af1b858803030848a0ef5e7dd9ecfc562716

1 files changed, 2 insertions, 1 deletions

diff --git a/core/java/android/inputmethodservice/AbstractInputMethodService.java b/core/java/android/inputmethodservice/AbstractInputMethodService.java
index 7cf0b10031ac..3cd13a212a4b 100644
--- a/core/java/android/inputmethodservice/AbstractInputMethodService.java
+++ b/core/java/android/inputmethodservice/AbstractInputMethodService.java
@@ -199,10 +199,11 @@ public abstract class AbstractInputMethodService extends Service
      * Dumps the internal state of IME to a protocol buffer output stream.
      *
      * @param proto ProtoOutputStream to dump data to.
+     * @param icProto {@link InputConnection} call data in proto format.
      * @hide
      */
     @SuppressWarnings("HiddenAbstractMethod")
-    public abstract void dumpProtoInternal(ProtoOutputStream proto);
+    public abstract void dumpProtoInternal(ProtoOutputStream proto, ProtoOutputStream icProto);
 
     /**
      * Implement this to handle {@link android.os.Binder#dump Binder.dump()}