Some Google Pixel Watch owners are experiencing severe battery drain issues, with devices losing power in under 12 hours compared to the normal 24- to 48-hour lifespan, Mobil reported. The glitch impacts multiple generations of the smartwatch lineup, ranging from the Pixel Watch 2 onward.
Battery Life Drops Below 12 Hours Across Multiple Generations
Affected users report sudden power drops even when the wearable sits idle. In specific instances documented by Mobil, battery levels fell by up to 20 percent over a four-hour window. Turning off the always-on display feature fails to resolve the rapid drain for impacted owners. Industry evaluations point to a software defect rather than a hardware or physical battery failure as the root cause.
Google Confirms Knowledge of the Glitch
Google addressed the situation publicly within a Reddit discussion thread where users documented their device failures. The company confirmed it is aware of the bug affecting a small number of users and stated that engineers are actively working on a fix. However, Google has not disclosed the exact trigger behind the high power consumption, which specific hardware models are vulnerable, or a concrete timeline for releasing a patch.
Software Update Guarantee Looms Over Older Models
Adding complexity to the repair timeline, Google’s official software update guarantee for the Pixel Watch 2 expired in October. It remains unclear whether that expiration date will affect the rollout of a patch designed to fix the current power drain issue on older hardware variants.
Common Questions About the Pixel Watch Battery Glitch
Which Pixel Watch models are affected by the battery drain?
Reports cover multiple generations of the device, spanning from the Pixel Watch 2 up to the Pixel Watch 5, according to Mobil.
Does changing display settings fix the rapid power loss?
No, disabling the always-on display setting fails to make a noticeable difference for users experiencing the rapid battery depletion.
Has Google released a patch for the issue yet?
Google stated it is working on a solution for the bug, but the company has not announced when a fix will become available to the public.
Related reading