In short: Developer Skylar Taylor-Barrick has managed to get Googlebook OS running on Apple Silicon Macs using a virtual machine that supports GPU acceleration and a working Chrome browser. The project, called gbos-vm, allows Mac users to try out Google’s Android-based laptop operating system without having to buy a Googlebook. However, it remains an experiment with bugs and security limitations that make it unsuitable for everyday use.
Graphics support is a central part of the work. Googlebook OS uses Vulkan, while Apple’s graphics system uses Metal. The project connects the two graphics APIs so that the virtual machine can use the Mac’s GPU instead of relying on the CPU to render the interface.
This required more than just translating graphics commands. Android shares graphics buffers between OpenGL ES and Vulkan using a Linux mechanism that macOS does not support. Taylor-Barrick’s project instead uses POSIX shared memory and then imports those buffers into Metal and MoltenVK, the layer that translates Vulkan calls for Apple’s graphics system.
The two platforms also arrange texture data differently. Metal requires texture lines to be padded to 16-byte boundaries. Android doesn’t. The project adds this padding on the Mac side so that the guest OS can process the textures as usual.
These changes give the VM hardware accelerated graphics, but not full compatibility. Some WebGL content renders incorrectly because Chrome expects a Vulkan extension, which MoltenVK does not provide. The display is also limited to 60 frames per second as the project’s QEMU build does not provide a refresh rate setting.
I have Googlebook OS running on my MacBook Pro
by u/moon-w0man on Googlebook
The installation begins with a Dell Googlebook recovery image. A script downloads it from Google’s servers, modifies the hardware-specific parts and starts the operating system via QEMU. Users need an Apple Silicon Mac with at least 16GB of RAM, about 60GB of free storage, and Apple’s Xcode command-line tools.
Other requirements include Homebrew and a Java Development Kit (JDK), as well as an Android SDK that includes the Native Development Kit (NDK), build tools, and a platform that supports API Level 34 or higher. The Android emulator is optional and provides simulated Bluetooth functionality. Users can also run a separate script to check whether the required dependencies are installed before starting the process.
The recovery image was created for the Googlebook hardware, not the virtual devices provided by the Mac’s virtual machine. To address this discrepancy, the project rebuilds the manufacturer partition using components from Google’s Cuttlefish virtual device project. The system partitions remain unchanged.
This approach gets the operating system up and running, but also removes some of the protections available on a physical Googlebook. The VM has no secure hardware element, so software implementations take over functions that would otherwise rely on hardware-based security.
Therefore, the encryption keys lack the same hardware protection. The modified manufacturer partition also lacks verified boot, although the other partitions retain their original verification.
For this reason, Taylor-Barrick recommends using the VM for development and experimentation rather than everyday computing work. A successful installation does not mean that the virtual machine has the same security properties as the hardware for which the operating system was designed.
Bluetooth support is limited to a simulated radio device; pairing with physical devices is not possible. Audio was inconsistent, while copying data from the guest, right-click functionality, and longer sessions were not thoroughly tested.
Because of these issues, gbos-vm is best suited for people who want to try out Googlebook OS and can tolerate an unfinished installation. The script automates much of the installation, but the developer tools, memory requirements, and unresolved compatibility issues make the process more burdensome than installing a traditional desktop application.
The project still offers working access to the platform on existing Apple hardware. Chrome is running and the user interface benefits from GPU acceleration. That’s enough for developers and enthusiasts to explore the operating system – as long as they keep in mind its incomplete hardware support and weaker security measures.
