Fix setFrameRate() cts test problems
Problem 1: We weren't reparenting our test surface to null each time
before releasing the surface. So when test 2 would start, the surface
from test 1 was still on screen, influencing the system's frame rate
decision and breaking the test.
Problem 2: Bad bit math to convert from ARGB to RGBA. This didn't
actually cause any problems with the test, but caused the onscreen
results to look broken.
Bug: 149052739
Test: cts-tradefed run commandAndExit cts-dev --module CtsGraphicsTestCases --test android.graphics.cts.SetFrameRateTest
Change-Id: I53df211d9ab7608c50d81dc69ce6c2e2d280209f
2 files changed