Pixel Watch 2 gets a new chip and significant battery improvement
One of the big challenges with wearables is that they have to be small. Now that is generally not difficult to achieve in terms of material, but it is in terms of battery: it is quite small, making it difficult to get energy from it for many days. Pixel Watch, for example, struggles with this, but successor Pixel Watch 2 seems to get a significant battery improvement.
Pixel Watch 2
We expect the Pixel Watch 2 to be announced this year, alongside the Pixel 8 and Pixel 8 Pro. That is set to happen in the fall, but just as there were quite a few leaks around the Pixel 8 Pro recently, the first rumors about Pixel Watch 2 are also trickling in via 9to5Google. This time they revolve around the processor and the battery.
That processor would be a Qualcomm Snapdragon chipset from the W5 range. It is unknown whether Google opts for the ready-to-use Snapdragon W5+ Gen 1 that has been announced, and whether it specifically opts for that latest processor at all. However, there would in any case be a different chip than in its predecessor. No more Exynos 9110, but probably the 4nm processor with 4 A53 cores at 1.7 GHz (with dual Adreno 702 GPUs of 1 GHz) from Qualcomm.
Related articles
Processor
It is therefore not a Tensor chip from Google itself, nor a chip from Samsung. Still, you don’t have to read too much into it: it just might be the best choice for the new wearable. In addition, the battery would therefore be significantly improved to “more than a day” instead of a day, as Google Pixel Watch insists. In addition, it would have the same health sensors as Fitbit Sense 2, including a stress tracker and an option to measure the temperature of your skin.
It remains to be seen what colors Pixel Watch 2 will come in, when it will be released and what it will cost, in addition to many other specifications missing. So just through the summer, then we can see what Google has in store for our wrists in the fall.
What would you like in the new Pixel Watch 2? Leave it now in the comments.