Google Find Hub Googlebooks removal: what's really broken
No removal of Find Hub from Googlebooks is documented in current reporting. Two unrelated Google developments have been tangled together under similar names: a Wear OS Find Hub update, reported by Heise two months ago, and a Google Books preview-search failure, reported by WinBuzzer earlier this year. Only one of those stories involves anything actually broken.
Three names, three different products. Find Hub is Google's Find My Device system, now extended to Wear OS. Googlebooks is an unreleased line of Android-based laptops Google has previewed for a fall launch. Google Books is the long-running book-search and preview service, and it's the one with a real, user-reported problem: in-book search stopped working for preview-enabled titles, and Google hasn't said why.
Why is Find Hub missing on Googlebooks?
It isn't missing from either product. Heise's report describes a Google Play Services update that touched both Find Hub and Googlebooks, not a removal from either one. Version 26.32 of Play Services rolled out on August 17, 2026, and included a Find Hub (Find My Device) update for Wear OS alongside new setup-wizard references for Googlebooks (Heise, two months ago).
The Find Hub update adds a "Find People" app to Wear OS watches, letting users share their location with contacts in real time, according to Google's support documentation cited in the report (Heise, two months ago). Heise's report does not specify which watch models received it, so whether an individual owner has access remains unclear.
On the Googlebooks side, the same update added copy telling users they'll be able to "learn about the multi-device feature suite" during setup and discover features that work alongside an Android phone (Heise, two months ago). That tracks with what Google said when it first detailed the laptops in May 2026, when it framed Googlebooks around tighter integration with Android phones (Heise, two months ago).
Googlebooks is the Android-based laptop category Heise reported as expected "in the fall." The supplied reporting doesn't confirm whether the devices have actually reached retail as of now, so treat that timeline as Google's stated target rather than a confirmed ship date.
What Google Books users are actually reporting
Google Books splits titles into three access levels: full view for public-domain works, snippet view showing short excerpts, and preview view displaying select full pages (WinBuzzer, earlier this year). The reported failure is specific to that third category.
WinBuzzer reported in late January that search stopped returning results for preview-enabled titles, even as the preview pages themselves kept loading normally. The outage reportedly began a few days before the report published. One user quoted in the piece described searching a word "while staring at a page that has that word" and getting zero results, despite the search box still appearing functional (WinBuzzer, earlier this year).
A reader can still find a passage by paging through a book manually. They reportedly just can't search their way there anymore, which matters for anyone trying to track down a specific line in a long book rather than browse one page at a time.
WinBuzzer's report describes the failure as covering both search and optical character recognition, but it doesn't test the two separately. There's no way, from this reporting, to tell whether the OCR layer broke or the search index itself failed; "search and OCR" is the outlet's characterization of what users experienced, not two independently confirmed diagnoses.
Google hasn't issued a support update, changelog entry, or public statement addressing the issue, according to WinBuzzer, and nothing in available sources suggests that's changed. Whether the problem is global or regional, whether it hits every preview-enabled title or only some, and whether it's deliberate or an unresolved bug are all open questions.
Anyone can check their own access without much effort: open a preview-enabled book with an uncommon word in it and search for that word. A zero-result match against a term visible on the page reproduces what WinBuzzer described. That only confirms the problem on one account and browser, though; it says nothing about how widespread the issue is, since no broader measurement has been reported.
The search function mattered for more than convenience. Courts previously found that Google's scanning of copyrighted books to build a searchable index could qualify as fair use, on the reasoning that a discovery tool serves a different purpose than reproducing a book for reading (WinBuzzer, earlier this year). Nothing in the reporting connects the current outage to that legal history. It's background on why in-book search existed, not an explanation for why it stopped.
What still works, and what doesn't
Manual, page-by-page browsing of preview-enabled books reportedly still works, since the pages themselves keep loading. That's navigation, not search, and it won't help locate an unfamiliar passage buried deep in a long book.
A browser's own "find on page" tool might help once a specific page is already open, but only if Google Books renders that page as selectable text rather than an image. Neither outcome has been confirmed in available reporting, so it should not be treated as a dependable substitute until text rendering is confirmed one way or the other.
A web search for an exact phrase, a library catalog, or a publisher's own site can help identify which book or page contains a passage. None of those restore Google Books' own search function. They're ways to find the source elsewhere, not a fix for what broke.
What to do now
Heise's report does not describe a removal from either Find Hub or Googlebooks. It describes a Play Services update and new setup references, nothing more. Because the report doesn't specify which Wear OS watches got the Find People app, an individual owner's access to that feature remains unclear rather than confirmed missing. Treat the Googlebooks fall timeline as a plan to watch, not a date to shop against.
For Google Books, don't rely on in-preview search to track down a time-sensitive quotation while the issue WinBuzzer reported remains unaddressed. Test a title relevant to the work at hand before trusting it, save screenshots or page numbers while manual browsing still works, and fall back on a library database or a publisher's own search tool for anything that needs to be cited reliably. Nothing in current reporting indicates when, or whether, Google plans to restore the feature.
Comments
Be the first, drop a comment!