In a nutshell, think of VR mode as a special high-performance setting for your smartphone. As Google's VP of Engineer for Android Dave Burke puts it, a phone that meets certain criteria and conforms to "lots of rules" can declare itself "VR-ready." From there, apps like virtual reality games and YouTube can fire up VR mode to unlock extra power and, crucially, drive down the latency between the moment you move the phone mounted to your head and the moment you see your environment change on-screen. Too much latency means you don't get the sort of persistent, "I'm actually somewhere else" feeling as you spin around with a phone on your face.
We're told getting to this point required work on just about every level of Android N's software stack. When VR mode is on, it changes how Android interprets information coming from its sensors. Graphics have to be drawn differently too. Usually, Android uses a double graphics buffer where one set of images is drawn on the screen and then swapped with another set stored in memory. With VR mode on, though, apps can use a buffer where images are replaced much faster, on a scan line by scan line basis.
Oh, and curiously enough, Burke also mentioned in a blog post that developers would have access to an "exclusive CPU core for VR apps" -- we're still trying to figure out how that works. Still, it's hard to argue with results. To put things in perspective, Samsung and Oculus managed to get motion-to-photon latency to under 20 milliseconds with the Gear VR. Google's work seems to have matched that ultra-low latency: the Nexus 6P with VR mode inside Google Cardboard also comes in under that 20 millisecond bar, compared to the 100 millisecond latency without VR mode.
There's still a lot to dissect here, and we'll update this story as we learn more.
For all the latest news and updates from Google I/O 2016, follow along here.
