At this year’s Mobile World Congress (MWC), Google introduced a slew of updates across the Android ecosystem, bringing enhancements to apps such as Fitbit, Google Docs, Google Maps, and Google Messages. However, a significant revelation followed after the initial Android announcements – the introduction of a revolutionary “hybrid OS interface” for Wear OS. This game-changing feature, designed to dramatically enhance battery life, has already made its debut on the recently released OnePlus Watch 2.
Understanding the Hybrid OS Interface: A Dual-Chipset Architecture
Explained by Google, many Wear OS smartwatches incorporate two chipsets within them. The primary component is a powerful applications processor (AP), like the Qualcomm Snapdragon W5 Gen 1 in the Pixel Watch 2 and OnePlus Watch 2. Accompanying this is a low-power co-processor microcontroller unit (MCU), such as the Bestechnic BES2700 in the OnePlus Watch 2, running a real-time operating system (RTOS).
The dual-chipset architecture aims to optimize battery life by offloading less complex tasks to the energy-efficient MCU, allowing the main AP to remain in a low-power state. While the concept is promising, the challenge lies in efficiently delegating workloads between two distinct chipsets with different operating systems. The solution to this challenge is Wear OS’s new hybrid OS interface.
The Functionality of Wear’s Hybrid OS Interface
Wear’s hybrid OS interface employs APIs that facilitate seamless communication between the operating system and the RTOS on the secondary chipset. These APIs are categorized into Display, Health Services, and Notifications. The Display APIs enable the MCU to handle certain display rendering tasks, such as rendering watch faces built on the Watch Face Format. Health Services APIs allow features like precise workout tracking and health data monitoring to be offloaded to the MCU. The Notifications APIs handle the processing of bridged notifications, syncing notifications from the phone to the MCU.
The OnePlus Watch 2 utilizes Wear OS’s hybrid OS interface to deliver exceptional battery life of up to 100 hours in its default “Smart Mode.” The MCU is actively engaged during notification interactions and when using most watch faces, seamlessly transitioning to the AP when launching apps or accessing specific functionalities. This ensures impressive battery life without compromising fundamental watch functionality.
Prospects for Other Wear OS Smartwatches
The key question arising from this breakthrough is whether the hybrid OS interface will extend to other Wear OS smartwatches, particularly Google’s Pixel Watch 2. According to Björn Kilburn, VP of Wear OS and Android Health at Google, the adoption of these improvements depends on each OEM’s underlying watch architecture and power strategy. While specifics regarding the Pixel Watch 2 remain undisclosed, it’s plausible that more OEMs will at least integrate the notification hybrid interface.
The hybrid OS interface signifies a paradigm shift for Wear OS, promising enhanced battery life and a more efficient utilization of dual-chipset architectures. Despite uncertainties about broader adoption, the Wear OS team assures users of additional power improvements in Wear OS 4, keeping the focus on delivering trustworthy battery life.