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)
Over the past couple of weeks with all five launch Googlebooks sitting here on my desk, I have been preaching patience for a brand-new desktop operating system finding its footing. However, a persistent, nagging software bug had recently crossed the line for me from slight annoyance to outright frustration. Across all Googlebook models, a constant window flickering issue inside Chrome and Chrome-derived PWAs was making it nearly impossible for me to get standard work done.
Other owners had begun documenting the exact same behavior in a recent r/Googlebook Reddit thread, so I knew it wasn’t just me. While some users initially wondered if the glitch was isolated to the HP Googlebook 14 or specific OLED panels, hands-on testing confirmed it was much broader. Every single Googlebook model I’ve used eventually exhibited this exact behavior.
Isolated to Chrome and PWAs
If there was a silver lining for anyone worried about a physical hardware defect, it was that this was clearly a browser rendering issue rather than a hardware display problem. The flickering never affected the entire OS desktop, the system shelf, or native Android apps. Instead, it was strictly confined to open Chrome browser windows and installed web apps like Gmail, Google Docs, or Google Calendar.
When the bug flared up, the active Chrome or PWA window rapidly flashed or briefly blanks out as if the viewport was refreshing itself mid-task. At its worst, those flickers happened multiple times per minute before suddenly quieting down for maybe 5-10 minutes at a time. There was no actual data loss or dropped input, but if you were scrolling through an article or tracking moving content on the screen, it completely broke your visual concentration.
The latest Googlebook build has quietly solved the issue
A quiet system update rolled out yesterday that brings Googlebooks to build 17.CL3B.260622.276.R5 and it appears to have finally squashed the rendering bug for good. After updating and putting the hardware through a full morning of heavy multitasking across multiple browser windows and PWAs, the obnoxious window flickering is completely gone for me on a couple different Googlebooks.
Early-adopter hardware platforms always go through growing pains, and dealing with visual glitches on a brand-new operating system is never fun. But with this latest patch clearing out the rendering pipeline, Chrome on Googlebook is finally feeling more like the smooth, seamless experience we hoped it would be from the get-go.
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.

