It's a remarkable achievement of software engineering that the new features introduced in Oculus Go works so seamlessly with legacy apps. I also respect that they're all conservative with their application, with the clock governor treating the set clock levels as a baseline, and making FFR & 72Hz completely optional.
That being said, I would love to have the option to override any settings that can be set in the SDK using system properties. I frequently set the cpuLevel & gpuLevel to essentially overclock an app, or set textureWidth & textureHeight to run a game at display limited resolution. The ff. properties would be great to have for Go:
foveationLevel [0,3] - set any level of foveation in an app
cpuLevel & gpuLevel [-1] - allows the clock governor to set levels below the provided ones for the CPU & GPU, respectively
displayMode [1,2] - sets the display's refresh rate to 60Hz & 72hz, respectively
S7 Exynos Nougat. 2017 Gear VR. Public test channel.
Thanks to Chris Pruett and John Carmack, the oculus.debug.* properties needed to change most of these settings has been revealed: - foveation level: foveation.level[0-3] (huh, that one was right on the money) - cpu & gpuLevel: since there is a property to disable the governor (adaclocks.force 0), I suspect simply setting both clock levels to 0 well let the governor scale to those levels. - chromatic aberration (CA) correction: forceChroma[-1,0,1] (-1 let's the app decide)
The only property missing is the one to set display mode at 60 or 72. Could I get clarification on this?
S7 Exynos Nougat. 2017 Gear VR. Public test channel.
Could you ask the Oculus mobile team if there's an adb system property to set the display mode to 72Hz, the same way you can set CA correction on or off?
S7 Exynos Nougat. 2017 Gear VR. Public test channel.
