The problems first surfaced in July, during the arrival of the Galaxy Watch 8 and Galaxy Watch 8 Classic (review). Android 16 QPR testers, particularly those using Pixel 8 and Pixel 9 models, reported failed pairing attempts with both watches. One of our frequent visitors also shared a similar experience.
The issue was believed to stem from a bug in the Galaxy Watch Manager on Google’s Pixel phones, not from the Galaxy Watch itself. Fortunately, it was addressed in a subsequent Android 16 beta update.
Pixel 10 and Galaxy Watch 8 Still Aren’t Pairing
Fast forward to the Pixel 10 launch, and the same problem appears to be affecting early adopters of Google’s latest flagship. Across Google Community, Samsung forums, and Reddit, many Pixel 10 and Pixel 10 Pro users have reported that their Galaxy Watch 8 (Classic) fails to connect or pair successfully. This suggests a major bug remains, even on stable Android 16 builds.
Some users also noted inconsistent syncing issues after pairing. Interestingly, the problem doesn’t seem isolated to the Galaxy Watch 8. Reports indicate similar bugs with the Galaxy Watch Ultra and Galaxy Watch 7 running the latest One UI 8 Watch software.
Suggested fixes, such as factory resetting the Pixel 10 or Galaxy Watch 8, have largely proven ineffective. Eventually, Google acknowledged the issue and confirmed they were investigating.
Google Play Update Fixes the Pairing Issue
A few days after responding to user concerns, Google released a Google Play Services system update last Friday. Several affected users have since confirmed that the update resolved the pairing failures.
If you haven’t updated yet, you can manually check and install the latest Google Play system update dated August 2025. A reboot is required to apply the changes.
How to Update Google Play Services on Pixel Devices:
1. Open Settings on your Pixel device.
2. Tap System, then select Software updates.
3. Tap Google Play system update.
4. Your device will check for the latest firmware.
5. Tap Restart if prompted to apply the update.
After installing the update, try pairing your Galaxy Watch with your Pixel 10 again to see if the issue has been resolved.
Do you own the latest Pixel 10 or an earlier model and have experienced pairing issues with your Galaxy Watch? Did the update fix it for you? Share your experience in the comments.
We mark partner links with this symbol. If you click on one of these links or buttons–or make a purchase through them–we may receive a small commission from the retailer. This doesn’t affect the price you pay, but it helps us keep nextpit free for everyone. Thanks for your support! Prices are based on the date of publication of this article and may be subject to change.
I sent my watch 8 classic back 2 days after I got it (about a week after the 8 launch). Wouldn’t pair with my 9 pro XL, which is on the latest QPR beta. Best answer I got was to wipe back to stock firmware and on some forums that didn’t even work. So I said screw it and sent it back and will just stay with my watch 5 classic a while.
The problem is I think Google & Samsung are locking down their systems similar to Apple and if you don’t have the same brand phone & watch, they won’t work correctly.
With Google announcing their are going to stop allowing side loading (unless an approved developer), it just sucks because I like to set my phone up how I WANT TO, not how some programmer thinks. I like to remove apps I don’t want/need, change setting in developer mode and so on.
I think that’s a better decision since many Samsung Health features wont still be accessible with a paired Pixel. And I agree on that, locking out the sideloading is a major disappointment for many Android users especially those who rely on alternative apps.
Yeah, on my watch 5 classic, I had to use "another samsung health monitor" app that had been modified to allow ALL of the health features to work.
But so far with the Watch UI8 firmware, he hasn’t been able to "break the code" to allow all the features to work on non Samsung phones.
It’s sad that the "lock down" is becoming the norm.
I chose Android back in 2010 because it could be rooted, side loading, modifying it to MY taste, not what a manufacture wanted.
But, I guess manufacturers, LIKE the lock down idea, it makes you slaves to THEIR ecosystem.