Google has recently announced a new project involving the integration of the Chrome OS operating system with the Linux kernel and frameworks utilized in the Android platform. This project is in its early stages and will require a significant amount of time before the updated system is ready for end users.
The first major step in this project was the incorporation of the new Floss Bluetooth stack into Chrome OS 122. This stack is based on the Bluetooth stack ‘fluoride’ used in Android. The changes will primarily impact system components of the platform and will not alter the user interface or the overall concept of Chrome OS.
Once Google completes this initiative, it aims to seamlessly transition the traditional Chrome OS to a new environment constructed with Android components. This integration with Android is anticipated to expedite the adoption of new technologies related to machine learning, simplify system maintenance, and enhance compatibility with various devices, including smartphones and accessories.
Currently, the architecture of Chrome OS closely resembles atomically updated Linux distributions. The system utilizes a patched Linux kernel, the UPSTART system manager, and the EBUILD/PORTAGE assembly tool from the Gentoo project. Despite its focus on web browsing and web applications, Chrome OS features a full-fledged multi-window interface with a desktop and taskbar. To run Linux and Android applications, virtual machines operate via the Crosvm hypervisor based on KVM.
By default, Chrome OS encrypts user data disk partitions using FSCRYPT. System partitions are mountable in read-only mode, verified by a digital signature, and updated atomically. Two root partitions are utilized for updating, with one serving as the working partition for installing updates while the other is switched to. Graphics rendering is achieved through the Freon stack, with plans underway to transition to using Wayland and the AURA window manager. The initial system texts are released under the Apache 2.0 open-source license.