Announced today at Google I/O 2016, VR team lead Clay Bavor revealed on stage that the company will be partnering with manufacturers to build Google-approved VR headsets based on an internally generated reference design. To boot, Google is also providing their new VR ecosystem with a handy Wiimote-style motion controller.

Unlike Samsung Gear VR, which features a separate IMU from the phone itself, Daydream-ready phones will supposedly already be suitable for low latency VR by providing sub-20 millisecond motion-to-photon latency natively. It’s unsure if the Google-approved headsets will provide any benefit outside of good ergonomics.

“There’s so many things you need to get right. It has to have great optics. I has to be comfortable. The materials need to feel good, and it needs to be really easy to put on and take off,” Bavor told the crowd.

See Also: Samsung, HTC, LG, and More Bringing ‘Daydream Ready’ VR Phones to Android

daydream controllerThe newly revealed controller, which looks eerily similar to the Oculus Rift remote, provides a touchpad and clickable buttons that allow you to scroll and swipe through apps, and is presumably for light gaming applications. Google maintains that the new Daydream controller houses ‘orientation sensors’, but doesn’t specify if the controller is entirely IMU-based.

The first headsets will be available starting fall 2016 from a number of yet unspecified manufacturing partners. Daydream-ready smartphones will be produced by Samsung, HTC, LG, Mi, Huawei, ZTE, Asus and Alcatel.

This story is breaking. Check back for more Google VR news shortly.

Newsletter graphic

This article may contain affiliate links. If you click an affiliate link and buy a product we may receive a small commission which helps support the publication. More information.


Scott Hayden
Well before the first modern XR products hit the market, Scott recognized the potential of the technology and set out to understand and document its growth. He has been professionally reporting on the space for nearly a decade as Editor at Road to VR, authoring more than 4,000 articles on the topic. Scott brings that seasoned insight to his reporting from major industry events across the globe.
  • Steve Biegun

    To clarify, the Google remote will have 3 degrees of freedom – roll, pitch, and yaw. Currently, it does not have positional tracking (6DOF.)

    • Jon

      How do you know that?

  • RSIlluminator

    I was hoping for one really good unified headset. It looks like now we’ll have a GearVR situation across all of the major manufacturers.

  • Orientation is NOT position. If they could do positional tracking for both (or either) the hands or HMD, I think they would have said so clearly. It sounds like they *might* have put better sensors in the phone itself, but I can’t help thinking that the GearVR will still be better because it uses two sets of sensors for error checking, doubling it’s chances of getting a good orientation track. Still, since neither are doing positional tracking, it’s still kind of a wash.

    Btw, the VicoVR people sent me an E-mail telling me they just launched. It’s kinda like a Bluetooth Kinect for cellphones. Full body tracking! Where is the story on that? That might be a viable solution to pull mobile out of the overwhelming shadow of PC VR. (currently LOVING my VIVE!)

    • MdM

      http://uploadvr.com/new-mobile-vr-positional-tracking-solution-coming-indiegogo/

      UploadVR had a story on VicoVR a couple days ago. However, even though I’m excited about what VicoVR claims they can do, I am VERY skeptical that they can get the latency down good enough for it to be tolerable. I suspect that Carmack tried something similar a while back and came to the conclusion that Bluetooth was not feasible to use to get the responsiveness required. He believes that inside-out positional tracking is the only solution for mobile and doesn’t bother talking about or exploring any outside-in solution.

      • Dmitry Morozov

        good point about VicoVR – but actual latency of VicoVR is suprisingly low, Bluetooth adds just 6.5ms, Currently Android rendering is an issue ~80ms, As Daydream promises to cut it to 20ms, it may become closer to Vive. And I bet Vive does not capture body cloud of human in real time )

        • MdM

          If this is true, I can’t wait! Any idea when VicoVR will have something available, and will this be a standalone product available to consumers? Correct me if I’m wrong, but the Vulkan API has already greatly improved the rendering latency on Android. No idea what the actual overall latency is, but it is certainly very responsive on my S7/GearVR. Good preemption support on the Snapdragon 820 to allow effective asynchronous timewarp helps a lot too. Of course, once VicoVR allows positional tracking, ATW won’t be as helpful.

    • TechnoHunter

      Totally Agree!