Google shipped another ChromeOS 151 maintenance patch on August 26, just six days after the last one. If the first round of fixes cleaned up window stutter and stylus lag, this one goes after quieter bugs: a Bluetooth reconnect glitch, a memory leak on lower-RAM Chromebooks, and a couple of display and audio edge cases that only show up in specific setups.
What’s actually in the .57 build
According to Google’s Stable Channel announcement, four specific bugs got cleaned up in this build. Paired Bluetooth mice and keyboards were failing to reconnect right after opening the lid from an extended sleep, an intermittent handshake problem that’s now fixed. Background tabs on 4GB and 8GB Chromebooks were also hanging onto RAM they should have released during tab discarding, the memory-saving trick ChromeOS uses to keep things responsive when you have too many tabs open on limited hardware.
The other two fixes are narrower. Dragging a window between an external monitor and your Chromebook’s built-in display could stutter if the two screens run at different refresh rates, say a 60Hz laptop panel next to a 144Hz monitor, and that’s been smoothed out in the Aura compositor. There’s also a fix for a rare audio hang: unplugging a USB-C headphone or DAC mid-video could freeze playback entirely, which is exactly the kind of glitch that makes you think your Chromebook crashed when it’s really just ChromeOS’s audio routing getting confused.
Two patches in six days isn’t a bad sign
ChromeOS 151 reached Stable on August 13 carrying 18 CVE fixes, a Flex GPU cutoff, and a handful of Gemini and bookmark bar changes, and it’s been getting cleanup patches ever since. The first one landed August 20 for window freezes and stylus lag. This is the second, and neither one is a security release; both are pure bug fixes for regressions that only surfaced once the update reached a wide enough pool of hardware to expose them.
That’s actually a decent sign, not a bad one. A big platform update ships, edge cases show up in the field, and Google turns around fixes in about a week instead of waiting two months for the next milestone. The alternative, letting a Bluetooth reconnect bug or a memory leak ride until ChromeOS 152, would be worse for anyone who happens to hit it. None of this touches Chromebooks on the Long Term Support channel, since LTS-144 doesn’t include ChromeOS 151 at all.
What Chromebook owners should do
Open Settings, click About ChromeOS at the bottom of the sidebar, then Check for updates. Your Chromebook should pull down version 16733.57.0 and ask for a restart to finish installing. The rollout is staged, so it might take a day or two to reach every device even after Google flips the switch.
If you’re on a Chromebook with 4GB of RAM, this is a genuinely useful patch and not just a token bug fix: tab discard does more work on your machine than it does on an 8 or 16GB model, so a leak there hits you first. Anyone who relies on a Bluetooth mouse or keyboard, or regularly plugs a Chromebook into an external monitor, will notice the other two fixes as well. If Bluetooth trouble persists after updating, our Chromebook Bluetooth troubleshooting guide covers fixes that don’t depend on a ChromeOS patch, and our guide to updating ChromeOS manually has steps for when the download won’t start.
