)]}'
{
  "commit": "4cdce427f9ba0339ac7c58fdb4f56ac3630abf34",
  "tree": "43af6562c83416588e8b82fedb58c4e20d24cd80",
  "parents": [
    "c7ab1e81776876d226174248593c6d0f2a65892b"
  ],
  "author": {
    "name": "Todd Kjos",
    "email": "tkjos@google.com",
    "time": "Thu Jun 25 13:08:14 2015 -0700"
  },
  "committer": {
    "name": "Todd Kjos",
    "email": "tkjos@google.com",
    "time": "Thu Jun 25 14:29:07 2015 -0700"
  },
  "message": "Fix janky navbar ripples -- incorrect timerslack values\n\nIf a thread is created while the parent thread is \"Background\",\nthen the default timerslack value gets set to the current\ntimerslack value of the parent (40ms). The default value is\nused when transitioning to \"Foreground\" -- so the effect is that\nthe timerslack value becomes 40ms regardless of foreground/background.\n\nThis does occur intermittently for systemui when creating its\nrender thread (pretty often on hammerhead and has been seen on\nshamu). If this occurs, then some systemui animations like navbar\nripples can wait for up to 40ms to draw a frame when they intended\nto wait 3ms -- jank.\n\nThis fix is to explicitly set the foreground timerslack to 50us.\n\nA consequence of setting timerslack behind the process\u0027 back is\nthat any custom values for timerslack get lost whenever the thread\nhas transition between fg/bg.\n\nSee Bug: 19398120\n\nChange-Id: Idc259717f62fa2255f8bafbbf88b68c0043f29cf\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a7ff85ed7cf6cd035d8c557df1b330e73e38e3b6",
      "old_mode": 33188,
      "old_path": "libcutils/sched_policy.c",
      "new_id": "1ffe872a7facd5c7004908d31e162b3a8b3a5c0b",
      "new_mode": 33188,
      "new_path": "libcutils/sched_policy.c"
    }
  ]
}