Use asynchronous messages for input method events.
Improves the throughput of IME event handling by ensuring that
input events do not get serialized behind UI traversal and
drawing messages such as when the UI is animating.
Added support for creating an asynchronous Handler as part of a
HandlerCaller. It turns out we should be using an asynchronous
Handler not only in IME dispatch but also in accessibility and
wallpaper events where HandlerCaller is used. So fixed those
services to also use an asynchronous Handler.
Change-Id: I0b19140c9d5ca6ee300c1a150c48312fd55ed8eb
diff --git a/core/java/com/android/internal/os/HandlerCaller.java b/core/java/com/android/internal/os/HandlerCaller.java
index 84699dc..b442ff5 100644
--- a/core/java/com/android/internal/os/HandlerCaller.java
+++ b/core/java/com/android/internal/os/HandlerCaller.java
@@ -24,38 +24,32 @@
public class HandlerCaller {
public final Context mContext;
-
+
final Looper mMainLooper;
final Handler mH;
final Callback mCallback;
class MyHandler extends Handler {
- MyHandler(Looper looper) {
- super(looper);
+ MyHandler(Looper looper, boolean async) {
+ super(looper, null, async);
}
-
+
@Override
public void handleMessage(Message msg) {
mCallback.executeMessage(msg);
}
}
-
+
public interface Callback {
public void executeMessage(Message msg);
}
-
- public HandlerCaller(Context context, Callback callback) {
- mContext = context;
- mMainLooper = context.getMainLooper();
- mH = new MyHandler(mMainLooper);
- mCallback = callback;
- }
- public HandlerCaller(Context context, Looper looper, Callback callback) {
+ public HandlerCaller(Context context, Looper looper, Callback callback,
+ boolean asyncHandler) {
mContext = context;
- mMainLooper = looper;
- mH = new MyHandler(mMainLooper);
+ mMainLooper = looper != null ? looper : context.getMainLooper();
+ mH = new MyHandler(mMainLooper, asyncHandler);
mCallback = callback;
}