summaryrefslogtreecommitdiffstats
path: root/init/init_parser.cpp
diff options
context:
space:
mode:
authorTodd Kjos <tkjos@google.com>2015-06-25 13:08:14 -0700
committerTodd Kjos <tkjos@google.com>2015-06-25 14:29:07 -0700
commit4cdce427f9ba0339ac7c58fdb4f56ac3630abf34 (patch)
tree43af6562c83416588e8b82fedb58c4e20d24cd80 /init/init_parser.cpp
parentc7ab1e81776876d226174248593c6d0f2a65892b (diff)
downloadsystem_core-4cdce427f9ba0339ac7c58fdb4f56ac3630abf34.zip
system_core-4cdce427f9ba0339ac7c58fdb4f56ac3630abf34.tar.gz
system_core-4cdce427f9ba0339ac7c58fdb4f56ac3630abf34.tar.bz2
Fix janky navbar ripples -- incorrect timerslack values
If a thread is created while the parent thread is "Background", then the default timerslack value gets set to the current timerslack value of the parent (40ms). The default value is used when transitioning to "Foreground" -- so the effect is that the timerslack value becomes 40ms regardless of foreground/background. This does occur intermittently for systemui when creating its render thread (pretty often on hammerhead and has been seen on shamu). If this occurs, then some systemui animations like navbar ripples can wait for up to 40ms to draw a frame when they intended to wait 3ms -- jank. This fix is to explicitly set the foreground timerslack to 50us. A consequence of setting timerslack behind the process' back is that any custom values for timerslack get lost whenever the thread has transition between fg/bg. See Bug: 19398120 Change-Id: Idc259717f62fa2255f8bafbbf88b68c0043f29cf
Diffstat (limited to 'init/init_parser.cpp')
0 files changed, 0 insertions, 0 deletions