Earlier this week, Google confirmed what we’ve suspected for a long time: the Google Pixel Watch is coming later this fall. And while we learned some details, the reveal was more of a teaser than a full-blown announcement. Some of that was to be expected, and of course, the next few months will be full of speculation about what the final form of the Pixel Watch will be. But one thing Google has to get right is the chip inside.
It’s clear, from the Pixel Watch’s design to the company’s massive undertaking in retooling Wear OS, that Google is trying to make an Android flagship smartwatch that can give the Apple Watch a run for its money. The thing is, Wear OS’s sluggish evolution wasn’t all on Google. For a number of years, Wear OS was stymied by a lack of capable processors.
Most Wear OS watches run on a Qualcomm Snapdragon Wear chip. A few run on proprietary chips, but those are an exception to the rule. At a time when Samsung and Apple were rolling out advanced smartwatch features left and right on increasingly powerful SoCs, Qualcomm understandably put more of its effort into its mobile chips than its wearable ones. That left Wear OS without a processor that could keep up. The watches were laggy, downloading apps on the wrist could be tedious, and sometimes it felt like the watch was fighting against you.
There are many reasons why Wear OS struggled to gain a foothold, but there are two major factors that led it to where it is today: infrequently updated software and this chip problem. Fixing either was going to be a bumpy ride, but at the very least, Wear OS 3 is a concerted effort on the software front. The hardware issue is a little more concerning because up until now, Wear OS watches have primarily depended on Qualcomm’s chips. And unfortunately, Qualcomm didn’t deliver.
There was hope when the Snapdragon Wear 4100 platform was announced as it used newer (though still outdated) process technology that would enable faster performance and more modern features. But then it took over a year for a handful of watches to actually use it, and the total experience still wasn’t dramatically improved.
To be blunt, the Snapdragon Wear 3100 and 4100 platforms are not going to cut it for the Pixel Watch. It was telling when Samsung opted to use its own Exynos W920 SoC over the Snapdragon Wear 4100 platform for the Galaxy Watch 4 lineup — the very first Wear OS 3 watches. Whatever Qualcomm had available, it simply was never going to outmatch Samsung’s own tech.
And when Google and Fossil started explaining how upgrades to Wear OS 3 might work, it became clear that the 3100 wouldn’t cut it either. Fossil revealed that none of its 3100-powered smartwatches would receive the upgrade to the new unified platform, counter to what many believed. When Google announced which existing Wear OS watches would be eligible for an upgrade to Wear OS 3, it not only excluded all 3100-powered watches — it also included the ominous message with others that “in some limited cases, the user experience may be impacted.”
The kicker was when a few months after the Wear OS 3 reveal, Qualcomm announced in July 2021 that it was getting its ducks in a row to develop a new 5100 platform within the next year. Which should mean the 5100 is almost ready unless it got delayed.
This leaves us with a big question. What exactly is going to power the Pixel Watch? And will it be able to run Wear OS 3 the way Google envisions?
Perhaps Google will license Samsung’s Exynos W920. Samsung has declined to comment on whether that’s a possibility multiple times. (Understandably so.) Another recent rumor is that the Pixel Watch will feature Samsung’s last-gen wearable chip, the Exynos 9110. Or given Qualcomm’s sudden desire to hustle on a new wearable chip, perhaps the Pixel will be one of the first watches powered by the 5100 platform. Or, maybe Google will adapt its Tensor chip for the Pixel Watch. We asked Google to comment about the Pixel Watch’s processor, but it declined to comment.
All of these scenarios are hard to predict. Wear OS 3 ran well on the Galaxy Watch 4 — except when it came to battery life with the always-on display. You can’t say the Pixel Watch would suffer the same, even if it has the same chip. It’s going to run a refreshed version of the Wear OS 3 UI and likely won’t use the exact same components. Leaks already suggest that the battery sizes are different. The watch running on the older Exynos 9110 might be potentially disappointing, but not the end of the world either. The Samsung Galaxy Watch 3 ran Tizen quite smoothly — and Wear OS 3 is at least part Tizen. As for battery life, the Galaxy Watch 3 wasn’t anything to write home about but it was, at least in my experience, better than its successor.
Opting for a Tensor chip would be intriguing — partly because we wouldn’t know what to expect but also because Google wouldn’t be limited by a third party. As for a Qualcomm 5100 chip, it’s hard to be hopeful based on the past.
That said, Qualcomm could surprise everybody, and I find it hard to imagine that Google would suffer a subpar chip when it’s been actively and continuously laying the groundwork for the Pixel Watch for over two years. That would be flopping when it counts most.
What it can’t afford are laggy performance and abysmal battery life
Obviously, we won’t know what the chip will be until Google confirms it later this year. But one thing’s for sure — Wear OS 3 can’t repeat the mistakes of the past. It’s not the end of the world if the Pixel Watch doesn’t come with FDA-cleared EKGs, body temperature sensors, and every experimental health feature under the sun. (We asked Google about this too, but it again declined to comment.) Those can always come later. What it can’t afford are laggy performance and abysmal battery life.
The only way to judge Google’s success (or failure) will be to test the Pixel Watch ourselves. But knowing what’s powering it would at least give an idea of what to expect.