Googlebooks After 1 Week: Reviewers Hit Flaky Phone Links and Slow File Transfers

Google's new $899-and-up Googlebook laptops have now been in reviewers' hands for about a week. The early verdicts agree that much of the hardware is good. The software, and especially the link between laptop and phone, is where reviewers keep running into problems.

The Verge's Dominic Preston put it most bluntly after a week with two Googlebooks: "Phone connectivity is flaky, app casting is awkward, and file-sharing seems to be flat-out broken." Google has already started pushing fixes. Here is what reviewers reported, what Google says is coming, and how to decide whether to buy now or wait.

Based on Google's Googlebook launch post and community update, plus hands-on reports from The Verge, 9to5Google and BGR, checked October 13, 2026. We have not tested a Googlebook. Every problem below is attributed to the reviewer who reported it.

What a Googlebook is, and what it costs

In its September 21 launch post, Google calls Googlebook "a new category of laptops". It runs on the Android technology stack with desktop foundations taken from ChromeOS. The first models come from Acer, ASUS, Dell, HP and Lenovo, starting at $899.

Google says the laptops reached shelves on October 4 in the US and October 5 in Canada, the UK, Ireland, France, Germany and Australia. Each one comes with 12 months of Google AI Pro, and Google promises "regular feature drops and updates for up to 10 years".

The selling point is phone integration. Google says you can resume phone tasks with Continue On, browse your phone's files in the Files app, and stream phone apps into a laptop window with Cast My Apps.

The Verge: flaky pairing and "entirely broken" file transfer

Preston tested the Asus and HP models for his piece, "Android is the best and worst thing about Googlebooks". He reported that getting either laptop fully paired with a phone took toggled settings on both devices, "multiple restarts, and the occasional prayer". Moving to a new Wi-Fi network broke the link again.

His other reported problems:

• File transfer: browsing phone storage from the laptop took minutes, and opening or moving a single 5MB photo took minutes more. He called it "completely unusable", though he noted that Quick Share moved the same files in seconds.
• Phone recognition: his laptops ignored his Pixel 11 Pro Fold for days before one finally connected.
• Continue On and notifications: Continue On triggered inconsistently. WhatsApp notifications did not come through, and he could only get notifications for one of his two Gmail accounts at a time.
• Apps: Chrome lacked profile switching, split view and custom search shortcuts. He also could not install Bluesky or Okta from the Play Store on either laptop.

His conclusion: "I certainly wouldn't buy a Googlebook as they are right now".

9to5Google and BGR: rough edges, no deal-breakers

Abner Li's Googlebook OS review at 9to5Google covered the Acer Googlebook 14 (Intel) and HP Googlebook 14 (Snapdragon). He reported that pages reloaded on the 16GB models, that Chrome Settings opened full screen over other windows, and that new Chrome windows would not take typing until he clicked the address bar. He also noted that cross-device features can take a while to appear after setup, that Samsung phones were not supported on day one, and that Linux app support was missing.

Even so, Li wrote that "There are no fatal flaws for the general user", and that he does not think the OS has problems "that can't be remedied in future updates." He found the Snapdragon HP ran a bit more smoothly than the Intel Acer.

Christian de Looper's BGR review of the $1,300 Asus Googlebook 14 did not report pairing problems and described the phone integration as "pretty intelligent". His concerns were app compatibility on Intel chips ("plenty of apps won't work as well") and battery life he called "little more than adequate". He advised buyers worried about app compatibility to look at a Qualcomm-based model, which he said Dell and HP offer.

The catch: one week is a small sample

These are early impressions from three reviewers using three of the five launch models (Acer, Asus and HP), and their experiences differ. BGR did not report pairing trouble, while The Verge's problems varied by phone and by laptop. Your results may depend on your phone, your Wi-Fi network and whether your model uses Intel or Snapdragon.

Google's October 10 update, covered below, does not mention file-transfer speed, so it is unclear whether its fixes address the file-transfer problem The Verge described. The 10-year update promise is Google's commitment, and the reviewers have only one week of experience to judge it against.

Should you wait? What Google says is coming

On October 10, Google posted an update in its Googlebook Community forum. It said a Google Play services update rolling out "over the next few days" reduces the steps needed to set up cross-device services. Google said the update also helps with timing issues where the setup QR code stays on screen.

The same post said Better Together features (Continue On, Cast My Apps, Quick Access and Notification Sync) are arriving on Samsung phones running One UI 9.0 (Android 17). It lists the requirements: an Android 17 phone, the same personal Google Account on both devices, and both Bluetooth and Wi-Fi switched on. It also says hotel, cafe, office and guest Wi-Fi often use "client isolation", which blocks the direct connection, so Google suggests testing on a home network.

On October 12, Google also announced a Linux terminal preview for Googlebook, with Linux GUI app support listed on its roadmap.

Based on what reviewers and Google have said, here is our suggested checklist:

• If phone integration is the reason you want one, waiting a few weeks looks sensible. Most of The Verge's complaints involve the phone link, and Google's fixes are only now arriving.
• Check your phone first. Google says Better Together needs Android 17. On Samsung, that means One UI 9.0.
• Audit your apps. List the apps you rely on and search for them in the Play Store. Preston found the "Made for desktop" label meant the most.
• Consider Snapdragon over Intel. BGR recommended it for app compatibility, and 9to5Google found its Snapdragon model smoother.
• Mind the memory. 9to5Google saw page reloads on 16GB units. Our 16GB vs 32GB laptop RAM guide explains the trade-off.

Frequently asked questions

Are Googlebooks the same as Chromebooks?

No. Google describes Googlebook as a new category built on Android with desktop foundations from ChromeOS. Reviewers say Android apps and phone features are central to it.

Does a Googlebook work with Samsung phones?

Not at launch, according to 9to5Google. In its October 10 update, Google said Better Together features are arriving on Samsung phones running One UI 9.0 (Android 17) over the following days.

How much does a Googlebook cost?

Google says prices start at $899. BGR reviewed the Asus Googlebook 14 at $1,300, and The Verge's Preston wrote about the limits of Android apps "on a $1,000 laptop".

Googlebooks are a big bet for Google, and the first week shows both the potential and the gaps. If you are not in a hurry, watching how quickly Google's promised fixes arrive costs you nothing.