Switch back to lsq2 VelocityTracker strategy.
The impulse VelocityTracker strategy is over-estimating
certain injected input events, used for SystemUI jank
performance tests. The current regression is caused by a combination of
improperly spaced input events and the high sensitivity of the new
strategy to that portion of the motion.
Bug: 64680775
Test: bit CtsViewTestCases:.VelocityTrackerTest
Change-Id: I4b387dcc4a13fe4295ee208490c49b2763a6bd19
diff --git a/libs/input/VelocityTracker.cpp b/libs/input/VelocityTracker.cpp
index cc74b9b..a914408 100644
--- a/libs/input/VelocityTracker.cpp
+++ b/libs/input/VelocityTracker.cpp
@@ -105,7 +105,7 @@
// this is the strategy that applications will actually use. Be very careful
// when adjusting the default strategy because it can dramatically affect
// (often in a bad way) the user experience.
-const char* VelocityTracker::DEFAULT_STRATEGY = "impulse";
+const char* VelocityTracker::DEFAULT_STRATEGY = "lsq2";
VelocityTracker::VelocityTracker(const char* strategy) :
mLastEventTime(0), mCurrentPointerIdBits(0), mActivePointerId(-1) {