diff options
| author | 2024-04-25 10:43:25 -0700 | |
|---|---|---|
| committer | 2024-04-25 15:01:27 -0700 | |
| commit | 079fc8361ddd112b4a7dc3d6c6f26e1703bc3e9b (patch) | |
| tree | 085bd7d29ad211e8603d818f894d1b080aab7db9 /libs/androidfw/StringPool.cpp | |
| parent | dbf2dd623ba4754145067329e42d44892acf226a (diff) | |
Don't let two close frames to interrupt intermittency
Fixes: 336840867
There is a common case where two frames follow quickly during
intermittent updates. This CL requires that at least three
frames take less than 100ms before intermittency is not considered.
Also, some same-frame movement results in 0 overall motion.
For example, a setFrame() call that moves content will follow-on
with an offsetTopAndBottom() that moves it back. Now, the
previous frame's position is tracked and compared instead
of only flagging the motion.
Test: new test, existing tests
Change-Id: Ia2c9dbc5485b0af34b4f4aa5f3a1dda4cb8552f7
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions