commit 7baca0639f87ca7f383ffaa6ea133c3da2384126
author Biswarup Pal <biswarupp@google.com> Tue Nov 26 15:57:23 2024 +0000
committer Biswarup Pal <biswarupp@google.com> Wed Nov 27 09:02:45 2024 +0000
tree 34de54439a5866292dfe49609f4b4b3dc131fd2b
parent 2f9ad13079de5066918ffb8fe86147f25a5d6072

Don't rely on GLConsumer frame number in virtual camera

Sometimes the GLConsumer frame number is not set correctly
(depending on how one writes into the Surface) causing the virtual
camera render thread to get stuck. This change maintains an atomic
bool within the virtual camera service itself to check if the
first frame has been drawn.

Test: VdmHost + VdmClient
Test: CtsVirtualDevicesCameraTestCases
Bug: 381074653
Flag: EXEMPT minor bugfix
Change-Id: If108f4d8da4f52c9bea550d27f34c927d7622737