Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 4cd4009e authored by Siarhei Vishniakou's avatar Siarhei Vishniakou
Browse files

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
parent 6b3e769b

libs/input/VelocityTracker.cpp

+1 −1
Original line number Diff line number Diff line
@@ -105,7 +105,7 @@ static std::string matrixToString(const float* a, uint32_t m, uint32_t n, bool r 
// 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) {