summaryrefslogtreecommitdiff
path: root/libs/androidfw/StringPool.cpp
diff options
context:
space:
mode:
author Yohei Yukawa <yukawa@google.com> 2024-07-17 13:38:51 -0700
committer Yohei Yukawa <yukawa@google.com> 2024-07-17 13:38:51 -0700
commit1c1954f6207b3cd46f9c6525ebb996dfde563126 (patch)
treec824b185a9a763b203362071d90b3a542681b61e /libs/androidfw/StringPool.cpp
parent81c8ae9d01628182ba57c6d2d0f7cf1b58a879da (diff)
Run IMMS#onUnlockUser() also for background users
As part of our on-going effort to address the remaining dependency on InputMethodManagerService#mCurrentUserId, this CL updates the behavior of InputMethodManagerService#onUnlockUser() so that it calls * IMMS#postInputMethodSettingUpdatedLocked() * IMMS#updateInputMethodsFromSettingsLocked() not only for the current user but also for background users, even for phones/tablets/TVs/wearables. This was not possible until when we update the above two methods to take userId [1]. With this CL, we would start initializing IME-related settings (e.g. secure settings) more eagerly for background users. But other than that, user observable behavior should remain unchanged. [1]: I9d4615e6da979204c21555e040a687163c1460ab e08e5c4a76ea32db05af858ebcfd9d88dc943f8c Bug: 350386877 Test: presubmit Flag: android.view.inputmethod.concurrent_input_methods Change-Id: Iecbca2696d4e2fd56a434f2e3a95d14976978e06
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions