Galaxy Watch Battery Drain Hits Owners Across Multiple Models

Owners of multiple Samsung Galaxy Watch models are reporting a sudden drop in battery life, with screenshots pointing to Google Play Services as the app swallowing the charge. Figures shared by affected users range from roughly 30% of daily battery use to a screenshot that pegs Play Services at 99.97%, a level that would leave almost nothing for the rest of the watch. Neither Google nor Samsung has issued a public statement on the issue.

The reports, gathered on the r/GalaxyWatch subreddit and catalogued by Android Authority, span at least four watches: the Galaxy Watch 5 Pro, Watch 6, Watch 7, and Watch 8. The pattern of Play Services eating battery, sometimes starting after a recent system update and sometimes with no update at all, is what makes the case unusual. The two companies that could fix it fastest have not, so far, said a word.

What Watch Owners Are Seeing

Three screenshots carried in the same thread lay out the spread. One user shared a battery usage panel showing Play Services at 69.7% of the charge since the last top-up. A second user reported 30.9% taken by the same background process. A third posted a screen in which Play Services was credited with 99.97% of battery use, the kind of figure that should be impossible for a service that is supposed to be invisible.

Android Authority’s Kaitlyn Cimino flagged the thread and wrote that the screenshots are “definitely a cause for concern” given that Play Services, under normal conditions, should only nibble at daily battery. SammyGuru picked up the same reports and quoted a Galaxy Watch Ultra 2025 owner who said their watch had dropped from four days of always-off display endurance to barely two: “Play service is draining like crazy.” A separate Watch 7 owner told the site Play Services was accounting for “more than 10% of total battery usage,” a high figure for a service that is supposed to be invisible in the background.

Which Galaxy Watch Models Are Affected

User reports so far name four models and one variant, with the model list drawn from the threads Android Authority and gHacks catalogued in April 2026. The watches are spread across three generations, which suggests the common factor is the software stack rather than a single hardware revision.

The earliest signs of trouble, per Android Central, were posted on the Galaxy Watch subreddit shortly after the March 2026 security update for Samsung wearables, though several Watch 6 Classic owners also reported the drain without installing anything new. Android Central’s report noted that not every Watch 6 Classic is affected and that one Watch 6 Classic owner with a non-Samsung phone ran into the issue only after pairing, which hints at a server-side change rather than a single rogue firmware build.

The full set of models reported so far:

• Galaxy Watch 5 Pro
• Galaxy Watch 6 and Watch 6 Classic
• Galaxy Watch 7
• Galaxy Watch 8 and Watch 8 Classic
• Galaxy Watch Ultra 2025

Why Play Services Sits at the Center of the Stack

Google Play Services is the background layer that ties Wear OS apps to Google’s account, location, push notifications, and update services. Owners cannot uninstall it without breaking the watch’s connection to the phone, and that is the structural problem at the heart of this story. When a service that cannot be removed starts acting up, the only tools left are a cache clear, a restart, or a factory reset.

That placement is exactly what makes the reported figures sting. A regular app can be force-stopped or background-restricted, but Play Services is the plumbing. Several of the Reddit fixes in the original thread that touched off the coverage (a guide post on disabling individual app permissions for Play Services) have drawn replies warning that disabling the wrong permission leaves the watch unable to pair with the phone, which then forces a factory reset. The same thread documents one user whose Play Services hit 5% battery in 15 minutes after a single permission was disabled, a reminder that the only safe lever owners have is the one Samsung or Google has to pull from the other side.

Where the Two Companies Stand

Android Authority’s report says the outlet has reached out to Google for comment. Samsung has not been named in the request by Android Authority, and gHacks notes that neither company had issued an official statement as of April 14, 2026. SammyGuru’s write-up echoes the same silence. There is no published fix, no acknowledged regression, and no promised patch.

The pattern is not new for Samsung’s watches. Android Central’s piece reminds readers that the Galaxy Watch 7 had a similar, more severe episode during its debut year, when some users in South Korea watched the watch run down at roughly 10% per hour after setup. Other owners reported waking up to a watch with 30% to 40% remaining after a full overnight charge, and a Reddit thread surfaced users who said they were left with 8% after minimal use. Samsung resolved that one with a patch, but the rollout took time, and there is no equivalent patch in sight for the current reports.

Three things are stated plainly in the available coverage and worth pulling together:

• Multiple models are affected, from the Watch 5 Pro through the Watch Ultra 2025, with both updated and unupdated watches showing the same drain
• Reported usage figures run from 10% to 99.97%, with most reports clustered above 20%
• Neither Samsung nor Google has commented on the issue in the public reporting gathered so far

Workarounds Owners Are Swapping Online

No fix has been confirmed. The moves that keep coming up in the Reddit threads, and that gHacks and Android Central both pass along, are housekeeping steps, not patches. Owners are swapping three suggestions in roughly this order, starting with the least destructive.

The first is a Play Services cache clear from the watch’s settings menu, which several users say brought their daily figure back down to single digits. The second is a full watch restart, which Android Central notes “seemingly gets Play Services back to normal, though it might return.” The third is a factory reset, recommended only if the first two fail, and only after a backup, since the reset wipes paired devices and any on-watch data.

Two of those steps to try first:

• Clear the Play Services cache from the watch’s app settings, then monitor battery use for a day
• Restart the watch, which several users say brings the figure back to normal for a stretch before it climbs again

SammyGuru also notes that some owners report a brief improvement after disabling unused app permissions for Play Services, but the same advice is contested inside the Reddit thread, where multiple users warn that disabling the wrong permission breaks the phone pairing and forces a reset anyway. The safest first move is the cache clear; the most disruptive, the factory reset, is a last resort.

A Familiar Pattern for Samsung’s Watches

What makes the silence harder to read is the prior. The Galaxy Watch 7’s first-year battery bug burned through public trust, and the patch that fixed it took a long, public rollout. The current reports echo that episode in shape, not in scale, with owners noticing the drain, screenshotting it, and waiting. The difference is that the Watch 7 problem was tied to a freshly shipped watch; this round is hitting watches that were running fine, which points the finger at something the software stack received, whether the March security update, a Play Services component update, or a server-side change that nobody outside Google can confirm.

Until one of the two companies says something, owners are stuck swapping the same three workarounds and watching the same screenshots stack up. A fresh leak that points to three Samsung Galaxy Watch 9 models is already circulating as the company lines up its next generation, and the timing makes the silence on the current watches louder. Either Samsung or Google can close this out with a one-line update, and the longer neither does, the more owners learn to read their own battery stats as a forecast.

Frequently Asked Questions

Which Galaxy Watch models are affected by the battery drain?

User reports name the Galaxy Watch 5 Pro, Watch 6 and Watch 6 Classic, Watch 7, Watch 8 and Watch 8 Classic, and the Galaxy Watch Ultra 2025, per Android Authority, gHacks, and SammyGuru. The Watch 6 Classic 89% report documented by Android Central shows the issue is not tied to a single hardware generation.

Is Google or Samsung going to fix the battery drain?

Neither company has issued a public statement or promised a patch in the coverage gathered so far. Android Authority says it has reached out to Google for comment. The closest prior example is the Galaxy Watch 7’s first-year battery bug, which Samsung eventually patched, but there is no equivalent patch in sight for the current reports.

What can I do right now to stop the battery drain?

The moves that keep coming up in the Reddit threads are a Play Services cache clear from the watch’s app settings, a full watch restart, and, as a last resort, a factory reset. No fix has been confirmed by Samsung or Google, and no source guarantees any of these steps will hold.

Will a factory reset actually fix it?

gHacks lists a factory reset as the more aggressive of two housekeeping steps, after a cache clear, and notes it is not guaranteed. Several owners in the threads warn that a reset is the only option if a permission tweak breaks the phone pairing, which is why it sits at the bottom of the workaround list.

Is this related to the March 2026 security update?

Android Central says the earliest reports followed the March 2026 security update for Samsung wearables, but multiple owners also report the drain with no update installed. The most likely candidates, based on the available evidence, are a Play Services component update and a server-side change, but neither has been confirmed.