Pixel fails to re-enter presentation mode in Daydream viewer |
|||||||
Issue descriptionChrome Version: Chrome Beta 57.0.2987.97 OS: Android 7.1.1 Test device: Pixel Device's state should be clear (restart chrome before running repro steps). Issue is reproduced with the Chrome Beta and the most recent VrCore version 1.3.148407064 from the Play Store. Reproduction steps: The easiest way to reproduce is not to use Daydream viewer, just controller, however I was able to reproduce it inside the viewer. 1. Access https://webvr.info/samples/03-vr-presentation.html on the test device 2. Tap "Enter VR" button and wait until Daydream setup flow is started. 3. when asked to hold the home button on the Daydream controller, do so => Web page content is rendered in binocular view, which is expected 4. Press cross in the left upper corner to exit presentation mode and press "Enter VR" button immediately after that Expected result: Presentation should be started, web page content should be rendered in binocular view. Actual result: DON flow screen appears, but after calibrating controller it still shows DON screen ("You can recenter your screen and controller ..."). Presentation is not started. There are some race conditions depending on the timeouts, so if the issue is not reproduced from the first time, please repeat step 4 (usually 2-3 repeats)
,
Mar 9 2017
Can you try to wait ~5s before re-enter VR mode? I think it was by design, the fix seems not in 1.3 release.
,
Mar 9 2017
Even if it's by design it's still an issue. After DON flow is completed user expects to see the web page content. It may take some time until user realizes that something went wrong and he needs to remove device from headset, close "binocular view", tap "Enter VR" button and complete DON flow again. Or if it's by design, then user should see the screen saying "Please remove device from the headset" instead of meaningless "You can recenter your screen and controller later ..."
,
Mar 10 2017
This should have been solved by b/33052570 I think we just need a GVR deps roll. Assigning to bshe as he's done this in the past.
,
Mar 11 2017
FYI, there are a couple other bugs that depend on the same roll. For this specific issue, would we depend on a specific Google VR Services version or just have better behavior if the newer version is present?
,
Mar 13 2017
No, I think they maintained backwards compatibility with older VR services versions. We should get better behaviour if the newer version is present, and the current behaviour if it's not.
,
Jun 6 2017
,
Jul 25 2017
,
Aug 30 2017
gvr has rolled a couple of times since then and this is no longer reproducible on TOT. mark it as fixed
,
Oct 6 2017
Verified in Chrome Dev 63.0.3233.3
,
Jul 4
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by bsheedy@chromium.org
, Mar 9 2017