Support our independent tech coverage. Chrome Unboxed is written by real people, for real people—not search algorithms. Join Chrome Unboxed Plus for just $2 a month to get an ad-free experience, access to our private Discord, and more. Learn more about membership here.
START FREE TRIAL (MONTHLY)START FREE TRIAL (ANNUAL)
As we talked about earlier this week, every brand-new platform goes through growing pains right out of the gate, and Googlebook OS is no exception. While we’ve already seen Google step up to acknowledge issues the washed-out OLED black levels on Intel-powered units, early adopters have surfaced a few other annoying day-to-day quirks across the first-generation group of devices.
Thankfully, the Googlebook engineering team is actively listening and working through the list. As spotted by GbookHub via responses from Mishaal Rahman on Reddit, Google has officially confirmed that fixes are underway for three specific pain points: Bluetooth audio lag and limited codec support, greyed-out Gboard Writing Tools, and a frustrating “Cast My Apps” loop when tethered to your phone.
Fixing Bluetooth audio delay and adding AAC codec support
One of the most ironic early hiccups on a Google-made desktop OS has been Bluetooth audio sync when using Google’s own Pixel Buds. Users across multiple machines have noticed a distinct audio-video delay when watching YouTube both in the browser and inside the Android app.
Making matters worse, Snapdragon-powered Googlebooks are currently locked to the basic SBC Bluetooth codec, leaving higher-bitrate options like AAC and LC3 off the table. According to Rahman, the product team is working on a two-pronged update that resolves the latency issue with specific earbuds and officially brings AAC codec support to Googlebooks in an upcoming release.
Unlocking greyed-out Gboard Writing Tools
Another weird inconsistency involves Gboard’s built-in AI Writing Tools. For a chunk of early owners, the Writing Tools icon remains stubbornly greyed out inside text fields in Gmail and Google Docs even after switching system languages to English, factory resetting, or leaving the laptop plugged in overnight to force background AI model downloads.
While a few users have managed to trigger the feature after a system update or fresh setup, Google confirmed it is actively testing a backend fix to make sure Writing Tools initialize reliably out of the box without requiring bizarre troubleshooting workarounds.
Resolving the “Cast My Apps” tethering loop
Finally, Google is tackling a bug that hits right at the heart of the cross-device “Better Together” experience. I’ve spent a lot of time praising how seamlessly Android 17’s Continue Activity and Cast My Apps features work over home or office Wi-Fi, letting you stream mobile apps directly onto your laptop screen.
However, if you take your Googlebook on the road and tether it to your phone’s mobile hotspot, Cast My Apps hits a wall. While the internet connection itself works fine, trying to launch an app stream over that same tethered connection gets stuck on the QR code setup screen or spins infinitely.
Google didn’t share an exact rollout date for these three patches just yet, as they are still working through testing. Still, seeing rapid, transparent communication around community feedback is an encouraging sign that the team is committed to smoothing out these rough edges fast. And the fledgling platform needs it.
SUBSCRIBE TO UPSTREAM
Get Chrome Unboxed delivered straight to your inbox
Upstream is our flagship, curated newsletter with the top stories, most click-worthy deals, giveaways, and trending articles from Chrome Unboxed sent directly to your inbox a few times a week. Join 31,000+ subscribers.

