ChromeOS and Android represent two distinct and significant components of Google’s ecosystem puzzle, and the tech giant has been striving to enhance their interoperability. However, Google seems to be experimenting with running ChromeOS on Android for undisclosed reasons. While various theories may abound, here are all the pertinent details surrounding Google’s recent maneuver.
Android users may be familiar with the concept of using their devices as makeshift desktops by connecting peripherals like keyboards and mice. Nonetheless, ChromeOS has undergone significant improvements over the past decade, offering a far superior desktop experience compared to attempting to utilize Android as a desktop OS.
Dubbed Project Ferrochrome by Google, initial commits for this endeavor are already accessible on the Chromium Gerrit. Recently, Google showcased a demo of Ferrochrome to select companies during an event. Android expert Mishaal Rahman successfully compiled and ran a Ferrochrome build on a Pixel 7 Pro device.
Ferrochrome essentially constitutes a ChromeOS virtual machine (VM) constructed using the open-source variant of ChromeOS. According to Mishaal, it has the capability to operate on any Tensor-powered Pixel device utilizing Android’s Virtualization Framework. However, to execute the VM presently, one must be running a customized version of Android sourced from AOSP and Google’s VM launcher application.
As expected for a project in its nascent stages, much of the functionality appears to be non-operational. Nonetheless, it boasts quick boot times. Google’s documentation also hints at the potential to incorporate additional operating systems into the project in the future.
Is the Future of Chromebooks at Risk?
This move certainly raises eyebrows. Introducing a fully functional ChromeOS to Android devices poses the risk of rendering Chromebooks obsolete—perhaps that’s Google’s intent, or maybe not. While ChromeOS on Android may not match the comprehensiveness of ChromeOS on Chromebooks at present, it’s premature to speculate. However, if Google intends to provide a complete ChromeOS experience on Android, Chromebooks might indeed face an uncertain future, potentially joining the ranks of the Google Graveyard in due course.
Additionally, it prompts speculation about whether Ferrochrome plays a role in enhancing ChromeOS on ARM, particularly with the imminent arrival of Snapdragon X Elite CPUs. However, we’ll leave that to your imagination, as it’s still too early to make any definitive assertions.
What are your thoughts on the prospect of ChromeOS on Android? Let us know in the comments below.
0 Comments