SurfaceView: Synchronize initial destframe change from BBQ
Fixes a case where the SurfaceView is stuck with a wrong scale. Destination frame scales the buffer to the SurfaceView fixed size. Currently the initial destination frame is applied when the first buffer is acquired by BBQ. The transaction is sent via the BBQ apply token. Meanwhile if the client updates the SurfaceView fixed size, the SurfaceView will apply the transaction via the SCC apply token. This can cause destframe changes to be applied out of order causing the app to be stuck with the wrong scale. Bug: 195443440 Test: atest BLASTBufferQueueTest Test: repro steps from bug Change-Id: Ibf53a0efdebb87291d081e48633c373a98d347b1 Merged-In: Ibf53a0efdebb87291d081e48633c373a98d347b1
Loading
Please register or sign in to comment