diff options
author | Ruben Brunk <rubenbrunk@google.com> | 2017-10-03 15:39:41 -0700 |
---|---|---|
committer | Ruben Brunk <rubenbrunk@google.com> | 2017-10-05 04:47:58 -0700 |
commit | d675f51c72c230d701c14c7f953d38c3e9f1eb1c (patch) | |
tree | 7f413c4b9bac9215ab529d629d5d44ee22328ef7 /rs/java/android/renderscript/ProgramRaster.java | |
parent | c765c2c448b7c38e6fb72c96fc31f4a568433404 (diff) |
Change recovery logic for services bound by VrManagerService.
- On AIO VR devices (where live VR services are required to render
anything), reconnect to the VrListenerService and VR compositor service
indefinitely and never leave VR + persistent mode.
- On smartphone VR devices, do not reconnect if the VrListenerService
dies for any reason, instead immediately leave VR + persistent mode. If
the VR compositor dies, reconnect a limited number of times. The
expectation is that the VrListenerService process will detect the
compositor crashes separately (via a shared service binding), and chose
to either attempt to fall back to a previous render path or simply
propagate the crash and leave VR mode entirely.
- Update dumpsys logging to include lifecycle events from the
VrListenerService and VR compositor service.
Bug: 66967700
Test: Manual test with VrCore APK by logging when the VR services are
connected and killing each VrCore process from ADB shell.
e.g.:
- Repeatedly kill the VrCore main process.
- Repeatedly kill the VrCore compositor process.
- Repeatedly kill both processes.
Change-Id: I8952b872b39102a601f66bc6624fc0ad92ca0f30
Diffstat (limited to 'rs/java/android/renderscript/ProgramRaster.java')
0 files changed, 0 insertions, 0 deletions