According to a pair of reports from The Information (subscription required), Google has big ambitions for the inside of Android phones. The report says the search giant has sent a long list of requests to chip manufacturers for future SoC designs and that Google is even planning to build its own processors.

The report says that during discussions that happened this fall, "Google representatives put forward designs of chips it was interested in co-developing, including a phone’s main processor." The new chips are reportedly needed for future Android features that Google hopes to release "in the next few years." By designing its own chips, Google can make sure the right amount of horsepower gets assigned to all the right places and remove bottlenecks that would slow down these new features.

The report specifically calls out "virtual and augmented reality" as use cases for the new chips. Publicly, only Google Cardboard has surfaced from Google's VR initiative, but internally, it seems like the company is gearing up for a huge VR push. Some of Google's biggest names have left their posts on flagship products to go work on the virtual reality team: Jon Wiley, the lead designer of Google Search, and Alex Faaborg, the former lead designer for Firefox, Google Now, and Android Wear. An earlier report from The Wall Street Journal claimed Google was building a version of Android that would become a virtual reality operating system.

Now Google wants to design its own VR and AR chips, presumably to power this new Android virtual reality OS and experimental devices like Project Tango (which is currently powered by a chip from Movidius). Augmented reality in particular is extremely hard on a processor. Overlaying a 3D image onto a video feed or a transparent display means constantly measuring the space in front of the display in 3D and rendering and positioning the objects in that 3D space many times a second. You're running the CPU, GPU, cameras, and accelerometers at full blast the entire time.

For the camera's image processor, the report said Google is interested in camera tech that can "scan the environment and push images to Google’s cloud-based systems for analysis." Google would then “give you context back” about the image. Google has a picture-based version of this today with Google Goggles, which can identify logos, book covers, and other images. We presume this would happen continuously at something like 24FPS, rather than just on individual pictures. It also sounds a bit like Google's Word Lens, an augmented reality translation app that replaces foreign text with translated text, right in the video feed.

Google is also reportedly looking for an image processor design that can minimize the camera delay in between photos for a "video-like stream" of images.

One curious bullet point mentions "adding memory capacity inside the phone’s main processor so that the processor doesn’t need to reach into a separate memory chip to accomplish certain tasks." This is vague enough to fit the definition of cache, something every mobile processor already ships with.

The report says Google also requested "more powerful sensors so that the phone can collect more data on its surroundings." It mentions "improved sensor hubs," which presumably means Google wants to standardize or improve the "Android Sensor Hub" and always-on voice chip present in the Nexus 5X and 6P. Google is also looking to add "support for a wider range of sensors, including one that can measure distance," something that would be helpful for AR and VR.

Finally, the report mentioned that these talks originated "from Google’s efforts to find a manufacturer to make chips for an “enterprise connectivity device,” a plan that is still ongoing. That's vague enough to mean almost anything, but nonetheless interesting.

Google designing its own chips would mirror Apple's chip strategy, which the company has employed in the iPhone and iPad to great effect. Apple's control over hardware and software allowed it to move to a 64-bit platform before anyone else, and its chips can focus on performance gains that really matter for mobile software, like single core performance.

Qualcomm has a near monopoly on Android SoCs, but it is more marketing driven than performance driven and has been doing a disservice to the mobile space lately. It rushed to get 64-bit support out the door when it was beaten to the punch by Apple, which resulted in the very hot Snapdragon 810 SoC. Throttling and design issues meant the chip wasn't much of an upgrade over SoCs from the previous years, and Samsung and Apple leapfrogged Qualcomm in performance. Qualcomm's "more cores is better" strategy also isn't the best for mobile performance—a pure performance approach would value a small number of faster individual cores—but for customers in China, Qualcomm reportedly believes a phone with a million cores (Qualcomm is now up to eight) will sell better.

The Information goes on to speculate that this chip design will somehow help Android's fragmented update situation. Seeing how Android phones are already mostly Qualcomm-based, we think that adding another chip vendor (Google) would only complicate things further. The real solution for Android updates has already been figured out: define an abstraction layer in between the hardware and operating system, just like a PC BIOS. ARM has already done this for servers with SBSA specification, and Microsoft accomplished this with Windows RT (and successive versions of Windows on ARM).

The site also notes that Google has hired a senior product executive from Qualcomm along with several engineers from PA Semi, a chip firm that was acquired by Apple. Along with using off-the-shelf ARM designs as a starting point, it would seem Google has the expertise to pull off a chip design. It just needs a manufacturer to play ball.