Replace the existing usages of now-deprecated API
WindowManager.getDefaultDisplay() with WindowMetrics or
Context.getDisplay() in frameworks/base.
Bug: 128338354
Test: Build, auto test
Change-Id: I02d38a022c5e0e6e9d699f03d35b65d6c8126da9
This adds extra metrics per each frame to capture:
* Maximum number of triangles to render.
* Fill and blend rate in kpixels
* Maximum number of device calls to render.
* Maximum number of UI controls.
This also capture results in two mode, first mode without extra load
and second mode with extra 2 threads that load CPU and emulate heavy
app/game.
Test: Locally
Bug: 13553231
Bug: 1347063273
Change-Id: I87491634fa38bd5e04d47d62154a0da8e467213f
(cherry picked from commit f3dae277aa990dcb99d5a0bab1f9ccc141b9e4d9)
This switches SurfaceView performance measurement to hardware canvas
type. Sloweness of this sub-test is caused by CPU blit operation. This
type is not highest priority for ARC++ and hardware rendering has more
sense to check.
Bug: 116859584
Test: Manually, FPS is 60 for caroline, which is expected.
Change-Id: Ic683c040e6089b878772e902f7a975898848b364
(cherry picked from commit 10da79663169f5d59a50d1a24b53d89f9844977a)
(cherry picked from commit 198a8d4c3b879d54681515367e13347cd258672a)
This collect first set of metrics, related to game performance. In this
test post buffer time, ready time and latency time is collected.
See GraphicBufferMetrics.java for explanation.
Test: Manually on different devices.
Bug: 116859584
Change-Id: I85eae038363860287b796c593b5192f74231cb72
(cherry picked from commit 20045a43bcf8c8bbbbbb677b4f5d49ebe4ab63f6)
