New issue
Advanced search Search tips

Issue 670104 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug
Proj-VR
Proj-XR
Proj-XR-VR



Sign in to add a comment

Re-enable Cardboard once Daydream platform support is fixed.

Project Member Reported by mthiesse@chromium.org, Nov 30 2016

Issue description

Daydream bug is here: b/33052570

Once that bug is resolved, we can re-enable cardboard support.
 
Labels: Proj-VR-Daydream
Hi, mthiesse,
I'm not quite understand what is "the DON flow is broken when called from Chrome for users with their headset set to Cardboard.", especially what is DON flow.
I try to run WebVR sample in cardboard mode successfully, so what is the broke scene?
Thx

If you're on a Dayream-ready device and you set your viewer type to Cardboard, then visit a webVR page, when the page calls requestPresent you get taken to the DON (device ON) flow which tells you to put your phone into the viewer, and pair your controller. Seeing as you have a Cardboard device, there is no controller to pair, so you get stuck in the DON flow.

b/33052570 (which unfortunately can't be made publicly visible) details why Daydream fails to detect Chrome as a Cardboard-compatible app (it's because ChromeTabbedActivity isn't exported). Once Daydream detects Chrome as a Cardboard-compatible app, then we should get a different DON flow that doesn't require controller pairing, and returns to chrome rendering in stereo as expected.
(Note that I also verified this is still broken)

Comment 5 by bshe@chromium.org, Jan 10 2017

Cardboard should have re-enabled on Canary a few days ago. we find a workaround. This should only track the process of b/33052570. After it fixed, we can remove the workaround.
Labels: Proj-VR-Cardboard
Summary: Re-enable Cardboard once Daydream platform support is fixed. (was: Re-enable Carboard once Daydream platform support is fixed.)
Status: WontFix (was: Available)
Closing as obsolete, tracking the removal of the workaround in  issue 683302 .

Sign in to add a comment