Samsung Galaxy phone won't connect to Chromebook? Fix it
A Samsung Galaxy phone can meet every obvious requirement, Bluetooth enabled, signed into the same Google Account, Wi-Fi connected, and still refuse to show up as an option under ChromeOS's Connected devices setup. If a Samsung Galaxy phone won't connect to Chromebook despite checking those boxes, a sensible first check is to update both devices before assuming it's a deeper Bluetooth or account problem.
A phone can fail to show up in a few different ways, and each one points to a different fix. It might not appear under Connected devices at all, a Chromebook Phone Hub connection issue at the enrollment level. It might appear but be missing one feature, like app streaming or phone unlock, which is closer to Samsung Phone Hub not working for a specific task than a broken connection. Or it might have worked fine before and stopped after an update. The sections below are organized around those three situations.
How to connect a Samsung Galaxy phone to a Chromebook: check versions first
A sensible first check is to update both devices: Settings > About ChromeOS > Check for updates on the Chromebook, and Settings > Software update > Download and install on the Galaxy phone. Either one can trigger a restart or ask for free storage, so leave a few minutes rather than expecting an instant finish.
Google's Phone Hub setup documentation requires ChromeOS M89 or later and Android 5.1 or later, according to a breakdown of Google's requirements from Position Is Everything earlier this month. That same source cites a separate, older baseline from Google's broader phone-connection documentation: ChromeOS 71 and Android 6 for features like texting, photo syncing, and Chromebook unlock. Both numbers come from a third-party summary rather than a direct read of Google's live support pages, so confirm them against the actual device rather than treating them as settled.
Updating doesn't guarantee a fix. At least two posters in a Google Chromebook Community thread reported no change after updating to ChromeOS 124 Stable, including the owner of a Chromebook Plus device. One of those same posters saw Phone Hub fail around an update cycle, and on that Chromebook, the Connected devices page showed a "Device Sync" status flagged in red next to a sync date weeks old. That status is worth checking on a stuck setup, even though a single report doesn't prove the update caused the failure.
If the phone shows up after updating both devices, finish setup as normal. If it doesn't, the next step is confirming whether it's actually missing or just mis-set-up.
Confirm whether the Galaxy phone is actually missing from Connected devices
Galaxy phones not connecting to Chromebooks has turned up in community threads and device reports from 2022 through 2024, on Pixel, ASUS, Acer, Lenovo, and Samsung hardware alike. Chrome Unboxed documented the symptom on a Galaxy Z Fold 3 in 2022. That spread shows the issue recurs across brands and years. It doesn't establish how often it happens to any one person, and no source here confirms an exact cause, though the pattern points toward a breakdown in the device-sync enrollment Phone Hub depends on.
Go to Settings > Connected devices > Set up and see whether the Galaxy phone appears as an option at all. If it's listed there, check the Device Sync status and last-sync date from the section above.
Meeting the basic conditions doesn't guarantee a listing. One poster running ChromeOS 126 and Android 12 confirmed Bluetooth on both devices, matching Wi-Fi, the same Google Account, and working Quick Share, and still got a "no available devices" message in a Google Chromebook Community thread from late 2024. The Galaxy Z Fold 3 case above hit the identical symptom despite being properly registered to the account. Shared Wi-Fi shows up in both reports as a condition the posters already had in place, not as a documented Phone Hub requirement, so treat it as a troubleshooting variable rather than a fix on its own.
Working Bluetooth or Quick Share does not prove that Phone Hub enrollment succeeded. A functioning Samsung Galaxy Chromebook Bluetooth connection only confirms the hardware pairing is fine; it says nothing about whether the sync layer behind Connected devices has actually gone through.
If the phone doesn't appear at all, the CryptAuth workaround further down is the next thing worth trying. If it appears but one specific feature isn't working, the connection itself is probably fine.
When the phone is listed but a feature still won't work
A phone can appear under Connected devices while a particular Phone Hub feature remains unavailable. App streaming is the clearest case: Google's current app-streaming support list names Pixel 4a and later on Android 13 or later, the Nothing Phone (1) and (2), and the Xiaomi 12T, 12T Pro, 13, and 13 Pro on Android 13 or later, according to Google's documentation as compiled by Position Is Everything. Samsung isn't on that list, so a Galaxy phone isn't confirmed as eligible for app streaming regardless of software version or connection status.
Smart Lock, the feature that unlocks a Chromebook using a nearby phone, carries its own separate requirements: the same Google Account on both devices, an internet connection on the Chromebook, and on the phone, Android L-MR1 or later, the screen unlocked, Bluetooth on, and a screen lock configured. If phone unlock isn't working, check that list before assuming the Connected devices enrollment itself is broken.
Quick Share deserves the same scrutiny. The cited Samsung instructions apply specifically to the Galaxy Chromebook Plus and don't establish identical Quick Share behavior on other Chromebook and Galaxy combinations, so confirm the actual settings on the hardware in use rather than assuming it should match.
The CryptAuth dialer sequence: an old, unsupported last resort
This isn't Google-documented troubleshooting. It's a sequence that circulated in community threads starting in 2022 and resurfaced two years later, with mixed outcomes and no confirmation it still works on current Galaxy software.
If the phone's built-in dialer doesn't trigger a response, install the Google Phone app first; one report found the code failed in Samsung's own dialer. Enter *#*#2884936#*#* into the dialer. Community posts describe this as forcing CryptAuth enrollment, and a toast notification reading "Forcing CryptAuth enrollment" is the only confirmation anything happened on the phone. On the Chromebook, open chrome://proximity-auth and select Enroll, then Sync. Return to Settings > Connected devices > Set up and check again, since the toast message appearing on the phone isn't the same as the phone showing up afterward.
Outcomes have been inconsistent. One poster reported the sequence restored a Galaxy S24 Plus connection to a Lenovo Duet 5. Another running the same steps on a Galaxy S22 saw no change at all.
A separate poster in the April 2024 thread suggested updating to ChromeOS 124 Beta and enabling the #allow-cross-device-feature-suite flag alongside reinstalling Cross-Device Services, a chain of steps that worked for some commenters and not others. A different poster, in the December 2024 thread, enabled just the flag, couldn't locate Cross-Device Services as an app on either device, and rolled the change back after the dialer sequence failed to help. Neither account is a reason to chase the flag as a fix, and anyone who enables it should reset it to default regardless of outcome.
One unverified community suggestion is to sign out of old, unused devices under Google Account device management first, as a way to clear stale entries. Nothing in the available reports confirms it actually affects enrollment.
What to do now
Update both devices first, then check Settings > Connected devices directly rather than treating working Bluetooth or Quick Share as proof the connection is fine.
If the phone appears, troubleshoot the individual feature, app streaming and Smart Lock especially, instead of repeating enrollment steps that already worked.
If it doesn't appear, the CryptAuth dialer sequence is worth trying once, without switching to the Beta channel and without leaving any flags changed afterward. The sources reviewed here do not confirm a universal fix for every device combination.
If nothing helps, send feedback directly from the Chromebook with Alt + Shift + I, and include the Chromebook model, Galaxy model, ChromeOS version, Android version, and the exact message shown on the Connected devices page. Chromebook Community responders have pointed users toward this step, noting that the logs it generates are what help engineers look into sync issues that still have no publicly documented fix (Google Chromebook Community; Google Chromebook Community).
Comments
Be the first, drop a comment!