diff options
| author | 2024-08-05 21:46:25 -0700 | |
|---|---|---|
| committer | 2024-08-05 21:46:25 -0700 | |
| commit | 931b02f0f4516e68b793b0e389fcaf9a0a08ee69 (patch) | |
| tree | 92734cf7a17e0b4599dfb1ee2b9325280721122f /libs/androidfw/StringPool.cpp | |
| parent | 9f94e49dc786cce615264cc093d88788022ea490 (diff) | |
Remove UMS#mUserStates lock from IMM#getInputMethodList()
With this CL the following methods
* InputMethodManager#getInputMethodList()
* InputMethodManager#getInputMethodListAsUser()
* InputMethodManagerInternal#getInputMethodListAsUser()
stop acquiring
synchronized (UserManagerService#mUserStates)
internally.
The idea is that we already have all the relevant user lifecycle
events. Thus it would make more sense to have our own canonical user
storage lock/unlock state in UserData rather than always calling into
UserManagerInternal#isUserUnlockingOrUnlocked(userId),
which internally acquires mUserStates lock in UserManagerService.
This CL should generally make IMMS operations more predictable
regarding whether a user storage is considered to be still locked or
already unlocked. Other than that, the semantics should remain
unchanged.
Bug: 329703038
Bug: 343601565
Bug: 354323416
Test: presubmit
Flag: EXEMPT refactor
Change-Id: I8a83910d770754eef4b81a542d4f21ffc8efe296
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions