Google has sparked confusion amongst builders and customers after labeling the Put on OS 6.1 replace as a “new launch.” For reference, the replace was initially launched again in 2025; nonetheless, the corporate’s newest paperwork say in any other case. This transfer has not solely created confusion however has additionally raised questions relating to replace monitoring.
Google’s newest documentation marks the Put on OS 6.1 replace as a “new launch”
The Put on OS 6.1 replace was first launched again in December 2025, following the sooner rollout of Put on OS 6 in July alongside Samsung’s Galaxy Watch 8 collection. It later reached Pixel Watches in October. Regardless of this timeline, the latest developer documentation now labels Put on OS 6.1 as a brand new launch. This transfer creates uncertainty about whether or not this can be a re-release or just a labeling mistake.
Reviews initially advised that the replace was tied to Android 16 QPR2. Nonetheless, this interpretation seems inaccurate. The confusion possible stems from a “New” tag within the documentation somewhat than an precise recent rollout. Additional, the official changelog doesn’t clearly point out the sooner December launch. This makes it much more tough for builders to trace updates precisely.
Customers are confused about whether or not it’s a re-release or not
Furthermore, the documentation mentions a number of enhancements that differ from what was initially related to the Put on OS 6.1 replace. One key addition is location-based time zone detection, which permits units to robotically alter time based mostly on bodily location, even with out community connectivity.
Different updates deal with supervised accounts and kids’s smartwatch experiences. These embody a “commencement” characteristic that transitions customers from supervised to straightforward accounts as soon as they attain the suitable age.
Regardless of the listed enhancements, no new construct labeled particularly as a recent Put on OS 6.1 launch has appeared on units. Present Pixel Watch builds already embody a few of these options, suggesting that the documentation could have blended particulars from totally different updates. Google is but to launch a press release on the mix-up and make clear what precisely went mistaken with the documentation.
