There are a few issues related to lens distortion on Samsung devices (immersive-web/webvr-polyfill#129, immersive-web/webvr-polyfill#133, immersive-web/webvr-polyfill#273, immersive-web/webvr-polyfill#272) due to newer Samsung devices decreasing resolution when the battery gets low, as well as manually setting the resolution. The dpdb only currently handles one resolution per device, and when not using max resolution, the distortion is incorrect. At the WebVR Authoring Workshop, we discussed some work arounds for this that'd provide the best possible experience for Samsung devices on browsers that do not support native WebVR.
We're working on getting a list of Samsung devices and potential resolutions, and with that, we can work on detecting the window width/height and see if the device is at max resolution. If not, we'd prompt the user to use the max resolution, similar to the 'please rotate your device' message. I think this is a fine constraint, as GearVR experiences also require full resolution.
There are a few issues related to lens distortion on Samsung devices (immersive-web/webvr-polyfill#129, immersive-web/webvr-polyfill#133, immersive-web/webvr-polyfill#273, immersive-web/webvr-polyfill#272) due to newer Samsung devices decreasing resolution when the battery gets low, as well as manually setting the resolution. The dpdb only currently handles one resolution per device, and when not using max resolution, the distortion is incorrect. At the WebVR Authoring Workshop, we discussed some work arounds for this that'd provide the best possible experience for Samsung devices on browsers that do not support native WebVR.
We're working on getting a list of Samsung devices and potential resolutions, and with that, we can work on detecting the
windowwidth/height and see if the device is at max resolution. If not, we'd prompt the user to use the max resolution, similar to the 'please rotate your device' message. I think this is a fine constraint, as GearVR experiences also require full resolution.