+2
−0
Loading
Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more
Both setRelativeLayer and setLayer are used to set z order. The two will conflict if set on the same transaction for the same surface. SurfaceFlinger will just apply setRelativeLayer since it's second in the setClientState order. Instead, the code should only apply the transaction that was requested last. This change removes the setRelativeLayer flag if the setLayer flag is added and vice-versa. Fixes: 131834423 Test: Steps from bug Test: LayerTypeTransactionTest.SetLayerAndRelative Change-Id: Ib14aa5c666e74455e5ccb26a0fea94699bcc5771