934fe8b2a5dbd090ab546555d0b80913904a2a5f
This is a small preparation to consolidate RemoteException handling out from InputConnectionWrapper. With this CL, InputConnectionWrapper no longer early-exits when a RemoteException is thrown but just falls through to IME tracing logic. By making this small change, the next CL [1] can split out RemoteException handling from InputConnectionWrapper as a pure refactoring. Anyway neither users nor developers can observe this change unless they are carefully checking IME tracing result when the IME target app is being killed. [1]: I0ea27e915a07699a4c124750266d84346fbd7bf6 Bug: 192412909 Test: atest CtsInputMethodTestCases:InputConnectionBlockingMethodTest Change-Id: I5c778a1097e7f05eeff27e7a72966f613076a801
Merge "Exempt default_input_method from BG-FGS-start restriction." into sc-dev am:
12ded20343 am: 0d2d7eb66f
…
Merge "Move tethering related hidden API flag file entries to packages/modules/Connectivity/Tethering" into sc-dev am:
8c37e55416 am: fbf590d3ea
…
Merge "Give Shell the NOTIFY_PENDING_SYSTEM_UPDATE permission" into sc-dev am:
69a0939764 am: 79f30197dd
…
…
…
…
Merge "Check the min menu size when exp. to normal bounds" into sc-dev am:
47aa9f156e am: 1de9c7bbe6
…
…
…
…
…
…
Merge "Update wallet tile secondary label when QAW cards fetching in flight." into sc-dev am:
ed6a76796f am: d11e405bfa
…
…
…
…
…
…
Merge "[Telephony] Add description about location permission" into sc-dev am:
fc3e38324f am: 395ffc40a7
…
…
…
…
…
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%