summaryrefslogtreecommitdiff
path: root/libs/jpegrecoverymap/jpegencoderhelper.cpp
diff options
context:
space:
mode:
author Siarhei Vishniakou <svv@google.com> 2023-01-05 17:20:00 -0800
committer Siarhei Vishniakou <svv@google.com> 2023-01-05 17:20:00 -0800
commit0839bd636585de782a2c22b9f44164fb74db3534 (patch)
treec2e940c586f5043b1cb31b45469c7e60a8ae6bea /libs/jpegrecoverymap/jpegencoderhelper.cpp
parent990ff7ba368f3d24ba6ac25321e326c82f13d620 (diff)
Provide prediction time from the application
After further discussion with the graphics team, it turns out that the Choreographer isn't the best way to compute the prediction time. There may be some strategy that would use the Choreographer, like looking at the last vsync and trying to guess when the next drawing will occur. However, for now, let's just provide this time from the application and experiment with it. If we do need the Choreographer, we should be able to get this data from libgui here in the native layer, so we don't need the java to set this time, anyways. Bug: 167946763 Test: atest libinput_tests inputflinger_tests Change-Id: I496a9c184745d4cec085b880f913983cc2be9e3f
Diffstat (limited to 'libs/jpegrecoverymap/jpegencoderhelper.cpp')
0 files changed, 0 insertions, 0 deletions