All taps under max double tap timeout are quick taps

When tapping rapidly on the overview button on a recents grid device
(like tablets), users might tap very quickly that would have triggered a
elasped time under the min double tap time (40ms) which would cause the
button to not be a quick tap. Removing the check allows all taps under
the max double tap timeout to be a quick tap. Then quickly tapping the
overview button would not confuse alt-tab with resume same task
functionality.

Test: manual
Change-Id: I9161fd5b68c299dc794e538a4fd9021ae98c7e94
Fixes: 36886408

1 files changed, 1 insertions, 2 deletions

diff --git a/packages/SystemUI/src/com/android/systemui/recents/RecentsImpl.java b/packages/SystemUI/src/com/android/systemui/recents/RecentsImpl.java
index 53a9eae17f41..2b812a5f7ac3 100644
--- a/packages/SystemUI/src/com/android/systemui/recents/RecentsImpl.java
+++ b/packages/SystemUI/src/com/android/systemui/recents/RecentsImpl.java
@@ -331,8 +331,7 @@ public class RecentsImpl implements ActivityOptions.OnAnimationFinishedListener
                 RecentsActivityLaunchState launchState = config.getLaunchState();
                 if (!launchState.launchedWithAltTab) {
                     // Has the user tapped quickly?
-                    boolean isQuickTap = ViewConfiguration.getDoubleTapMinTime() < elapsedTime &&
-                            elapsedTime < ViewConfiguration.getDoubleTapTimeout();
+                    boolean isQuickTap = elapsedTime < ViewConfiguration.getDoubleTapTimeout();
                     if (Recents.getConfiguration().isGridEnabled) {
                         if (isQuickTap) {
                             EventBus.getDefault().post(new LaunchNextTaskRequestEvent());