We bought a Galaxy Watch to go with the Samsung phone we already had. Pairing the two couldn't possibly be a problem, right? How charmingly naive of us.
What the ads promise
The Galaxy Watch runs Wear OS, Google's "open" watch platform, with Samsung's own touches on top. In theory that means any Wear OS app installs and any Android phone pairs and works. A lovely theory!
A Samsung watch, a Samsung phone, and still: Nope!!
Our everyday phone is a Samsung Galaxy S10. Yes, the very one from our post on what should happen when software updates end. It runs LineageOS and gets Android's monthly security fixes from the community. For years it has done everything we expect from a phone, without a single complaint.
The Galaxy Watch can measure blood pressure on the wrist with its optical sensors. Technically very impressive! To get a reading at all, though, it needs a paired phone running Samsung Health Monitor. And that app turns out to require not just a Samsung Galaxy phone, but also Samsung's own operating system, based on Android 12 or newer. So on LineageOS, Samsung Health Monitor simply can't be installed! Our S10 was built by Samsung, sold by Samsung and still has the Samsung logo on the back. But because security forced us to install a different operating system, its maker no longer considers it worthy of pairing with a Samsung watch. WTF!?
"Just put the original Samsung software back," you say. Nice try. To install LineageOS in the first place, the phone has to be unlocked, and the moment it is, Samsung blows a tiny fuse inside it: the Knox warranty bit. It's a physical, one-time switch. No reinstall of Samsung's software resets it, no factory reset, no amount of clever hacking. From that moment on, Samsung's health apps, Samsung Pay and friends permanently refuse to run on that phone. So our S10 isn't merely locked out while it runs LineageOS. It has been excommunicated for good, because the only current system with security updates for a discontinued S10 has to come from somewhere else!
A smartwatch on the wrist and a phone in the pocket, and still no working setup. Two devices from the very same maker aren't allowed to talk to each other. And why, exactly? Thanks, Samsung, for this very considerate service!
In the end, the watch turns a fully working phone into needless e-waste. If you want the whole Galaxy Watch, you need a current Samsung phone. So the older one is forced into a drawer or the bin. How many tonnes of e-waste could easily be avoided with a more customer-friendly software strategy, without forced obsolescence? But longer use and less e-waste don't improve a manufacturer's balance sheet.
In our view, buyers should decide for themselves when a product is no longer useful. Without any pressure from manufacturers or platform owners!
Two questions before you buy
If you're shopping for a smartwatch, ask yourself: a) Does it work fully without the maker's phone app? b) Does it work with any phone, even one running a community system? The answers matter as much as the spec sheet. Hardly any big-brand watch answers both the way its users would want. So it's better to spot the trade-offs early. In a later post we'll look at alternative smartwatches that do a lot of things differently.
Back to blog