tree 9036b290a6a6d8134088f2aa854d389cf9fa6fc9
parent 1466e4a4e77e97712b1ca85d03dd832e016e1775
author Yohei Yukawa <yukawa@google.com> 1549965660 -0800
committer Yohei Yukawa <yukawa@google.com> 1549965660 -0800

Log display IDs for both IME and IME-client in StartInputHistory

This is a follow up CL to a recent CL [1], which added a special
fallback mechanism for IMEs to be shown on the default display when
the target display doesn't have FLAG_CAN_SHOW_SYSTEM_DECORATIONS.

It turns out that this scenario will soon become more user-visible
once Bubble UI is enabled, because Bubble UI is built on top of
ActivityView, where the target Activity including any text input field
will be running on a virtual display, not on the default display,
while IMEs are expected to continue running on the default display.

To make it easier to diagnose this new scenario, this CL updates our
retrospective debugging mechanism called StartInputHistory [2].  With
this CL, InputMethodManagerService starts keeping track of both IME
display ID and IME client display ID for each StartInput so that we
can see them later into the StartInputHistory section of the
bugreport.

For Bubble UI scenario for instance, we would see a log like this:

  ... imeDisplayId=0 ... targetDisplayId=1 ...

There should be no user-visible behavior change.

 [1]: Iedd71e4ddf4983f90b02dd72e471e7fa8e838fbf
      ef1965bd6d6061cb54bce305a4b99e640db19ddc
 [2]: Icb29c4ef0703553ead8654d3255a554de6d1a9b4
      357b2f60e147d18af9c8399b346a9e63de1baaf3

Bug: 35079353
Bug: 114350902
Test: Manually verified with Bubble test app and run 'adb shell
      dumpsys input_method' to see that a virtual display ID is logged
      when typing on Bubble UI.
Change-Id: I6f40d86a03a7965d72af7e9a1b6466350b7dfab7