)]}'
{
  "log": [
    {
      "commit": "fc434acf530cbde198c8936bf1bc09fad5861031",
      "tree": "2f22c6a51fe8cd66f106004d9b438f52c8eeccf2",
      "parents": [
        "99599940f68158aeef735d8763980d0dbd397b51"
      ],
      "author": {
        "name": "Siarhei Vishniakou",
        "email": "svv@google.com",
        "time": "Wed Jan 13 10:28:00 2021 -1000"
      },
      "committer": {
        "name": "Siarhei Vishniakou",
        "email": "svv@google.com",
        "time": "Fri Jan 29 18:48:01 2021 +0000"
      },
      "message": "Add inputEventId to SurfaceFrame\n\nSurfaceFrame will now be aware of the id of the input event that caused\nthe current frame.\n\nThe flow of input event id is inputflinger -\u003e app -\u003e surfaceflinger.\nHere, we are adding the \u0027inputEventId\u0027 parameter to the\n\u0027setFrameTimelineVsync\u0027 call. This call will now be responsible for\nsetting two pieces of information: the vsync id, and the input event id.\nSince it will no longer be limited to the vsync id, we rename this call\nto \"setFrameTimelineInfo\".\n\nOnce the inputEventId is stored in SurfaceFrame, we will add a binder\ncall to send the frame timing information to inputflinger (separate,\nfuture CL). This will allow input to reconstruct the entire sequence of\nevents (at what time was input event getting processed in system_server,\napp, and surfaceflinger) and will provide the ability to measure\nend-to-end touch latency.\n\nIn a separate change, we will also add ATRACE calls to allow manual /\nscript-based latency analysis for local debugging. We will now know\nwhich input event is being processed in surfaceflinger.\n\nBug: 169866723\nBug: 129481165\nDesign doc: https://docs.google.com/document/d/1G3bLaZYSmbe6AKcL-6ZChvrw_B_LXEz29Z6Ed9QoYXY/edit#\nTest: atest WMShellUnitTests SurfaceParcelable_test libgui_test IPC_test SurfaceFlinger_test\n\nChange-Id: If7e0eee82603b38b396b53ad7ced660973efcb50\nMerged-In: If7e0eee82603b38b396b53ad7ced660973efcb50\n"
    }
  ]
}