Daydream headset msg displayed when phone is set up for Cardboard only |
||||||||
Issue descriptionChrome Version: 57.0.2987.38 OS: Android 7.1.2 Device: Pixel XL What steps will reproduce the problem? (1) Setup phone to have Cardboard as the default VR device. (Daydream app is not installed) (2) Go to https://mrdoob.github.io/brokenmantra/?webvr (3) Click the "Enter VR" button. What is the expected result? binocular view mode starts for cardboard What happens instead? Binocular view starts, but content is frozen. After 1 sec, a screen is displayed telling the user to "Remove your phone from your Daydream headset". See screenshot "daydream_msg.png". Wehn checking the settings in binocular mode, it shows the "default/cardboard device" see screenshot "settings.png"
,
Feb 23 2017
harrr, wrong issue.
,
Feb 27 2017
+m58 given it is p1
,
Feb 28 2017
There are two issues: 1. There is a crash in the renderer which triggers exit VR (the remove phone from your Daydream headset screen). 2. The exit VR screen shouldn't say Daydream headset while using a Cardboard viewer. For 1, I will investigate if it is because of VR or other reasons. For 2, I have filed a bug to ask for Cardboard specific exit VR screen. Before that exist, it is probably OK to use the Daydream exit VR screen for now. (the alternative is to show 2D content, which is even less desired). If we really want to make this smooth, we could also consider implement our own exit VR screen. But this might be an overkill at this stage. To summarize, my opinion is to focus on the first crash and keep the exit VR screen the same whenever Chrome about to show non binocular view.
,
Mar 1 2017
This is not a chrome issue. It looks like the site didn't start VR rendering after pressing "enter VR" button, so the canvas was never fullscreened. And we have logic to check if canvas is fullscreen after enter VR presentation. If the canvas didn't fullscreen after a timeout, we just force exit VR. So you see the exit VR screen. I have contacted the author of the site. I will just mark this as external dependency for now.
,
Mar 1 2017
It is not a chrome issue and it currently only affect the above mentioned site (which requires turn on webvr flag to reproduce). So p2 is probably more appropriate.
,
Mar 13 2017
,
Nov 21 2017
,
May 30 2018
no actionable thing to do on Chrome side. So mark as close.
,
Jul 4
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by meganlindsay@chromium.org
, Feb 9 2017Owner: bshe@chromium.org
Status: Assigned (was: Untriaged)