Separate VR DFM install logic from Consent Flow
Currently GvrConsentHelper also ensures that the VR DFM is or gets installed if needed. However, the permissions API bypasses this flow. In order to enable the Permissions API logic by default, this logic needs to be separated out. This mimics the pattern of the ArCoreInstallHelper; however, there is an outstanding bug which blocks installing VrCore at this time. That will be addressed in a separate, future, change. Also drops the FPS timer in gvr_scheduler_delegate down to DVLOG(2), as it's rate of logging proved a bit difficult to debug during development. Fixed: 1043223 Change-Id: I2475403b4df62fa2b9db0ca15642be2ff7d6b4ea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036643 Auto-Submit: Alexander Cooper <alcooper@chromium.org> Reviewed-by:Klaus Weidner <klausw@chromium.org> Commit-Queue: Klaus Weidner <klausw@chromium.org> Commit-Queue: Alexander Cooper <alcooper@chromium.org> Cr-Commit-Position: refs/heads/master@{#738046}
Showing
Please register or sign in to comment