Handle duplicate DOWN event
After unlocking the device, an immediate swipe down to reveal the
shade (a very common user journey) can sometimes just directly to the
QS shade variant, instead of showing the expected QQS shade with
notifications. I have been unable to find root cause at this point,
however, I am aware that multiple ACTION_DOWN events are issued in
this case with the same downTime.
To fix, detect this very specific scenario and ignore the touch.
Test: manual, follow steps in bug (swipe down after unlock)
(cherry picked from commit 2e8d3e5e0929587d7b99b5e50ed7a8c1ef839496)
(cherry picked from commit 83d700c5938615cd4daae9da8204ec7a3d540808)
1 file changed