tree e6b2e929b2c9b8aa873916e4fc36d26eb3676de0
parent d4384a5ff2c9621e2f89f20454c71914f88677d0
author Yohei Yukawa <yukawa@google.com> 1658789757 +0900
committer Yohei Yukawa <yukawa@google.com> 1658789757 +0900

Simplify IMMS#getEnabledInputMethodSubtypeList() a bit

This is a follow up CL to my previous CL [1], which let query APIs
defined in InputMethodManager support background users.

Basically UserHandle.getCallingUserId() never returns a pseudo user ID
such as UserHandle#USER_CURRENT.  Hence there is no need to use
InputMethodUtils.resolveUserId there.

There should be no developer observable behavior change.

 [1]: I192a0f5a1375170d17a4c08af94f23966dbaea8b
      7f8ee4b9ddd31ad36a12c5278b27990dc76011cc

Bug: 122164939
Bug: 234882948
Test: make -j CtsInputMethod1  \
                CtsInputMethod2  \
                CtsInputMethodServiceDeviceTests  \
                CtsInputMethodServiceEventProvider  \
                CtsInputMethodServiceHostTestCases  \
                EditTextApp  &&
        atest CtsInputMethodServiceHostTestCases
Change-Id: I85da7d819b6fba01fce1e5df1347534febf9aa53