Exploring What’s Left Of Google’s VR Dreams

You’re likely familiar with Google’s Cardboard, and the legions of cheap virtual reality headsets it spawned. By sticking a smartphone to the wearer’s head, all these headsets needed were some basic optics to provide a surprisingly effective VR experience. You may even know about Google Daydream initiative that came a few years later, which not only improved the basic Cardboard design but brought with it new software features such as VR-specific improvements to the Android operating system and a version of the Play Store dedicated to 3D games and applications.

But unless you’re a true Google devotee, what you may not know is that the search giant partnered with Lenovo to produce a stand-alone Daydream headset called the Mirage Solo in 2018. A full year before the Oculus Quest hit the market, the $399 device combined the guts of a smartphone with a 2560×1440 display running at 75 Hz, a pair of cameras in the front that let it see the world around the user in three dimensions, and a gyroscopic handheld controller to provide an immersive VR experience without having to be tethered to a computer. In addition to the standard consumer version, there was even a “Business Edition” of the headset specifically marketed to schools, offices, and hospitals as a way to deliver VR content without having to invest in any additional infrastructure.

So why isn’t the Mirage Solo better known? Because in classic fashion, just a few years after it was released, Google decided they were no longer interested in virtual reality and shuttered the entire Daydream program. The software components it introduced were stripped out of Android, the 3D Play Store was taken down, and the back-end mechanisms necessary to register new headsets were turned off. Almost overnight, the Mirage Solo became a stereoscopic paperweight.

Or at least that was the official story, anyway. I recently came across a Lenovo Mirage Solo at a thrift store for $25, and despite my initial Internet searches strongly indicating that it would probably be worthless, it seemed worth the gamble to find out for myself.

Continue reading “Exploring What’s Left Of Google’s VR Dreams” →

Ping Pong Ball Improves The Google Daydream Controller

[Matteo] has just released a new installment of his Google Daydream VR controller hack, which we first covered last year (when he got it working with iOS). This time around he’s managed to forge a half Daydream, half PlayStation Move controller hybrid.

The original controller only managed a mere 3 DOF (Degrees of Freedom) using the internal accelerometer; although this conveyed rotational motion around the 3 axis, transitional information was completely lacking. [Matteo] resolves this by forming a simple positional marker out of a white LED enclosed in a standard ping pong ball; He tracks this setup using an iSight camera.

To gel everything together, he adds motion tracking to his already extensively developed software stack, which enables him to unshackle the Daydream controller from Android. He deciphers the Bluetooth packets and streams the sensory information straight to a web browser over a webSocket connection.

sf-stack

The results are quite impressive and the tracking is smooth. Not only does this add to the final goal of hacking his way towards a platform independent VR motion controller, he aptly gets some inspiration from Sony, extends Google’s hardware and even manages to use Apple’s webcam along the way. How’s that for carving passages between the walled gardens of consumer electronics?

Continue reading “Ping Pong Ball Improves The Google Daydream Controller” →

Hacking Google Daydream To Work With IOS

The Google Daydream is a VR headset with a controller, and according to the folks at Google, “It’s not currently compatible with iOS and won’t be for several years probably.” OK.

This inspired [Matteo Pisani] to get to work on the protocol that it uses to speak with Android phones. Cutting to the chase, he got it working in several days.

There really wasn’t all that much to it. The controller sends data over Bluetooth, and [Matteo] noticed an “unknown” device on the network. Looking inside the data that it sent, it changed when he moved the controller. Not so unknown now! The rest of the work consisted of writing applications to test hypotheses, waving the controller around, and finding out if he was right. Read up if you’re interested in implementing this yourself.

We love protocol hacks here. From running quadcopters on your own remotes, to simply trying to turn on a lightbulb, it’s getting more and more important that we understand the various languages that our devices speak.