SurfaceFlinger: get nextPredictedPresentTime directly from frame timeline
ag/13715677 moved the call to check whether a frame is early or not before a transaction is applied. This created a bug in BufferStateLayer::nextPredictedPresentTime since it is checking the drawing state surface frame, which is not valid since the transaction is not applied yet. This CL is fixing this by pasing the vsync id itself, and getting the expected present time base on that vsync id. Change-Id: I0f95f2a3a2efff921964a6fb5f9b50e0fcc65a85 Test: launch an app and observe systraces Bug: 181978893
Loading
Please register or sign in to comment