Update motion prediction offset.
The Jetpack motionprediction library calculates a prediction target based on the minimum display refresh rate (16~18 ms). UX feedback suggests that we should cap this at 3~4 stylus frames, which therefore requires a -4 ms offset (1 frame). Clients of the framework MotionPredictor can control the prediction time directly and can access predictions further into the future by providing a larger value. Bug: 288354672 Test: predictions are visible in the motionprediction test app Change-Id: I3a489b59b8b2050c64dd31b2a0f75c2238cb432d
This commit is contained in:
parent
9c9700c239
commit
fb55fbb7ec
1 changed files with 1 additions and 1 deletions
|
@ -636,7 +636,7 @@
|
|||
|
||||
<!-- Enable the system motion prediction model. -->
|
||||
<bool name="config_enableMotionPrediction">true</bool>
|
||||
<integer name="config_motionPredictionOffsetNanos">20000000</integer> <!-- 20 ms -->
|
||||
<integer name="config_motionPredictionOffsetNanos">-4000000</integer> <!-- -4 ms -->
|
||||
|
||||
<!-- Whether to reset Battery Stats on unplug when the battery level is high. -->
|
||||
<bool name="config_batteryStatsResetOnUnplugHighBatteryLevel">false</bool>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue