Googlebook is sold as the laptop that works naturally with an Android phone, but its most useful cross-device features have a narrower launch window than the marketing suggests. Google requires a compatible phone running Android 17 or later, and Samsung phones are not supported at launch even when they already have Android 17.
Google says support for Android 17-capable Samsung devices will roll out over the coming weeks. That makes this a temporary compatibility gap, not evidence of a permanent split between Googlebook and Galaxy phones. It is still a reason to check the feature on your own devices before buying a laptop around the promise of tight phone integration.
Which Googlebook phone features are affected?
Google groups the integration under its Better Together pitch. The official Googlebook pages describe four particularly useful functions:
- Continue On: resume a supported phone task on the laptop, either in the installed app, in a browser, or through app streaming.
- Cast My Apps: open and interact with a limited number of phone apps on the Googlebook screen.
- Quick Access: browse, copy, attach and manage files stored on the phone from the Googlebook Files app.
- Notification Sync: view, dismiss and, for supported messaging apps, reply to phone notifications from the laptop.
Google’s product page places a small but important condition on these features: setup is required and the phone must run Android 17 or above. Google’s help pages add further requirements, including the same Google Account, Bluetooth, Wi-Fi and cross-device services on both devices. File access, app casting and task continuity also expect the devices to be on the same Wi-Fi network.
This is a different question from whether Android apps run well on the laptop itself. Our Googlebook adaptive app checklist covers resizable windows, keyboard input and other app-level issues. Here, the problem is the link between the laptop and the phone.
Why Android 17 is not enough for Samsung yet
The version requirement is necessary, but it is not sufficient at launch. Reports from Ars Technica, Android Police and 9to5Google agree that Better Together is not yet enabled for Samsung devices. A Google representative said support would roll out across Android 17-supported Samsung devices “over the coming weeks.” Google did not give a precise device list or completion date in that statement.
The practical distinction matters. A Galaxy phone can report Android 17 and still fail the compatibility check because the Samsung-specific rollout has not reached it. Reinstalling apps or resetting either device cannot force a server-side or system-level availability change.
Pixel phones are the safest launch-day match because Google controls both sides of the integration. Other Android brands also need Android 17, and availability should be verified rather than inferred from the version number alone.
Five checks before buying or troubleshooting
- Check the phone’s Android version. Open Settings, About phone, then Android version. Android 16 and earlier do not meet Google’s documented requirement. A promised future update is not the same as current compatibility.
- Check the brand rollout separately. If the phone is a Galaxy model, confirm that Better Together support is live for that device, software build and region. Android 17 by itself does not prove that the Samsung rollout has arrived.
- Verify the connection prerequisites. Use the same Google Account on both devices, enable Bluetooth and Wi-Fi, connect them to the same Wi-Fi network, and update Google apps. Then open Connected devices, Connection preferences and Cross-device services on the Googlebook.
- Enable only the services you need. Under Continue activity, check the separate controls for Tasks, Apps, Files & media and Notifications. Notification Sync is off by default, and Google lets you disable individual apps. Remote file access can also delete a phone file by moving it to the phone’s trash, so this is not a harmless display-only permission.
- Test during the return window. Resume one supported task, open one non-sensitive app, copy a small file and reply to a test notification. A successful device pairing does not prove that every Better Together component works.
If Better Together still does not appear
Start with the boring checks because they define the supported path. Confirm Android 17 or later, install pending system and Google app updates, restart both devices, and verify that both use the same account and local network. On the Googlebook, return to Cross-device services and check each Continue activity toggle instead of assuming one master switch enables everything.
Do not test Cast My Apps with a banking, password or streaming app first. Google warns that some apps showing sensitive information or copyright-protected content are unavailable for casting. A refusal from one such app does not prove that the entire connection is broken.
If a Samsung phone is fully updated but the controls remain unavailable, preserve the exact phone model, Android build and Googlebook software version, then wait for the compatibility rollout or contact Google support. A factory reset is disproportionate here: it removes data without changing whether Google and Samsung have enabled the feature for that build.
What actually changes
Googlebook’s phone integration is useful, but at launch it is a compatibility matrix rather than a universal Android feature. Buyers have to verify the OS version, phone brand, staged rollout and per-feature permissions. For Samsung owners, the sensible position is neither panic nor blind trust: treat Better Together as pending until the menus appear and a real task, app, file and notification test succeeds.
The broader lesson is less flattering for Google’s marketing. An Android-based laptop can still depend on a new platform release and manufacturer-specific enablement for its headline ecosystem features. The laptop may work perfectly as a standalone machine, but that is not the same product promise.
In brief
- Googlebook Better Together requires a compatible phone running Android 17 or later.
- Samsung phones are not supported at launch, even when they already run Android 17.
- Google says support for eligible Samsung devices will roll out over the coming weeks.
- Continue On, Cast My Apps, phone file access and Notification Sync each have separate requirements and controls.
- Verify the feature on your exact phone before buying a Googlebook for cross-device integration.
Sources
- Google: Googlebook product page and Better Together requirements, checked October 7, 2026
- Googlebook Help: Access your phone’s files on Googlebook, checked October 7, 2026
- Googlebook Help: Continue tasks from your phone on Googlebook, checked October 7, 2026
- Googlebook Help: Share phone apps with Cast My Apps, checked October 7, 2026
- Googlebook Help: Sync phone notifications with Googlebook, checked October 7, 2026
- Ars Technica: Googlebook Better Together does not support Samsung at launch, published October 6, 2026
- Android Police: Googlebook’s phone integration misses Samsung at launch, published October 7, 2026
- 9to5Google: Samsung support for Googlebook integration is delayed, published October 6, 2026