Revert to lsq2 VelocityTracker strategy
The impulse implementation causes high velocity
at liftoff on some hardware. Reverting back to lsq2
for now.
Bug: 35412046
Fixes: 69069303
Test: use Google Maps with 2 fingers with both strategies
Change-Id: I7138fa12468303aa3885f4731bbdacbf5c7ce3a8
(cherry picked from commit 899c2aa1b8c7b576ddb7949ec4448956d7c5bc2c)
diff --git a/libs/input/VelocityTracker.cpp b/libs/input/VelocityTracker.cpp
index 57eee12..e54f147 100644
--- a/libs/input/VelocityTracker.cpp
+++ b/libs/input/VelocityTracker.cpp
@@ -107,7 +107,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) {
