Your Pixel Watch thinks you ran a marathon yesterday. You didn’t. You walked to the kitchen twice and sat through four meetings.

If your Fitbit app suddenly shows 25,000 steps for a day you spent mostly at a desk, you’re not alone. Google’s March 2026 firmware update for Pixel Watch 2 and Pixel Watch 3 has broken health tracking across the board. Step counts are roughly doubled, calorie burn estimates are wildly inflated, and SpO2 and skin temperature readings have disappeared entirely for many users.

This isn’t a minor calibration drift. It’s a full-on data meltdown.

What’s Happening

Starting March 18, Pixel Watch owners who installed the latest firmware update began flooding Reddit, Google’s support forums, and Fitbit community boards with reports. The problems fall into four categories:

Doubled step counts. Users are seeing step totals roughly 2x their actual movement. A normal 8,000-step day shows as 15,000-17,000. Some users report counts as high as 30,000 for sedentary days. The Fitbit app syncs these inflated numbers, which then cascade into incorrect distance, active minutes, and calorie calculations.

Inflated calorie burn. Because step counts feed into calorie estimates, daily calorie burn numbers are equally wrong. Users relying on Fitbit’s calorie data for nutrition tracking are getting numbers 500-1,000 calories above reality. If you’re eating back exercise calories based on your Pixel Watch data right now, stop.

Missing SpO2 readings. Blood oxygen monitoring has gone silent for many Pixel Watch 3 owners. The watch still prompts you to check SpO2, but readings either fail to complete or simply don’t appear in the Fitbit app. Pixel Watch 2 users are reporting similar issues, though less consistently.

Skin temperature data gone. The skin temperature tracking that Fitbit uses for sleep analysis and (on Pixel Watch 3) menstrual cycle predictions has stopped recording. Historical data appears intact, but new readings aren’t being logged.

Which Devices Are Affected

Based on user reports so far:

• Pixel Watch 3 — All four issues (steps, calories, SpO2, skin temp)
• Pixel Watch 2 — Step count doubling and calorie inflation confirmed; SpO2 and skin temp issues reported but less widespread
• Original Pixel Watch — Limited reports, but some users seeing step count inflation

The common thread is the March 2026 firmware update, which began rolling out on March 17. Not all users received the update on the same day, which is why reports started trickling in on the 18th and exploded by the 19th.

Why This Matters for Your Training

Bad data isn’t just annoying. It actively undermines your training if you’re making decisions based on it.

Nutrition tracking goes sideways. If you use Fitbit’s calorie estimates to guide how much you eat — and plenty of people do — you’re currently getting permission to eat 500+ extra calories per day. Over a week, that’s a pound of fat gain from trusting your watch.

Recovery signals disappear. SpO2 trends and skin temperature are genuinely useful for catching overtraining, illness onset, and sleep quality shifts. Losing both sensors simultaneously means flying blind on recovery. If you’ve been using these metrics as part of your training decisions, you’ll need a backup plan until Google fixes this. Our sleep tracking app roundup covers alternatives that can fill the gap.

Step-based goals become meaningless. If you’re doing 10,000-step challenges, tracking walking for weight loss, or using step counts as a baseline activity metric, your current data is fiction.

What Google Has Said

As of March 20, Google hasn’t issued a formal acknowledgment of the bug. A Fitbit community manager posted a generic “we’re aware of reports and investigating” response on the Fitbit Community Forums on March 19, but no timeline for a fix has been provided.

This is frustrating but unfortunately par for the course. Google’s track record on Pixel Watch firmware issues has been slow. The November 2025 battery drain bug took nearly three weeks to patch after widespread reports.

What You Can Do Right Now

There’s no user-side fix for the sensor issues. You can’t patch firmware yourself. But you can minimize the damage to your data and training:

1. Stop Trusting the Numbers

Obvious, but worth stating. Don’t make nutrition, training load, or recovery decisions based on your Pixel Watch data until this is resolved. If your watch says you burned 3,500 calories, you didn’t.

2. Use Your Phone as a Step Counter

Your phone’s built-in step counter (Google Fit, Samsung Health, or Apple Health if you carry an iPhone for some reason) uses its own accelerometer. It won’t double-count. Use phone step data as your baseline until the watch is fixed.

3. Cross-Reference with Another App

If you have a secondary tracker (Garmin, Whoop, Oura, even a $20 Mi Band), now’s the time to wear it. Our Garmin Q1 2026 update review covers what Garmin’s latest firmware actually got right, if you’re looking for a reliable alternative to lean on.

4. Manually Log Key Metrics

For SpO2, a $25 fingertip pulse oximeter from any pharmacy is more accurate than any wrist-based sensor anyway. For skin temperature, you’re mostly out of luck on manual tracking, but if you’re using it for menstrual cycle predictions, consider temporarily switching to a dedicated app like Flo or Natural Cycles.

5. Don’t Factory Reset Your Watch

Some forum posts suggest factory resetting as a fix. Based on current reports, it doesn’t help and you’ll lose on-device settings. The problem is in the firmware, not your configuration.

6. Report the Issue to Google

The more reports Google receives through official channels, the faster this gets prioritized. File feedback directly through the Fitbit app: Settings → Help & Feedback → Send Feedback. Include specific examples (screenshot your inflated step counts).

The Bigger Fitbit-on-Pixel Problem

This update disaster highlights an ongoing issue with Google’s Fitbit integration into Pixel hardware. Since Google absorbed Fitbit, the health tracking stack has been in a perpetual state of transition. The Fitbit app still feels like a separate product bolted onto Pixel hardware, and firmware updates seem to break the connection between sensor hardware and software interpretation more often than they should.

We saw hints of this direction when Google announced the new Fitbit AI health coach earlier this year. Lots of flashy AI features, but the foundation (accurate sensor data) keeps cracking. An AI coach that analyzes garbage data gives you garbage advice.

For context on how wearable regulation might eventually address accuracy standards, the FDA’s evolving wearable rules are worth understanding. Right now, fitness wearables operate in a gray area where “close enough” accuracy is the norm, and there’s no regulatory consequence when a firmware update tanks your step count.

Should You Switch Watches?

If this is a one-time firmware bug that Google patches within a week or two, no. Every wearable manufacturer ships bad updates occasionally. Garmin had its own Q1 update issues (though nothing this severe). Apple Watch has had its share of sensor bugs after watchOS updates too.

But if you’re seeing a pattern — and with Pixel Watch, the pattern is getting hard to ignore. It’s worth asking whether Google’s wearable division has the software discipline to be trusted with your health data long-term.

If accuracy is your top priority, Garmin and Apple Watch have more mature sensor fusion pipelines. They still make mistakes, but they’ve had more years to stabilize. Whoop is another option if you’re primarily interested in recovery and strain tracking — our Whoop 5 review breaks down what that ecosystem actually delivers.

If you’re locked into the Fitbit app for its community features, challenges, or long-term health history, your best option is to wait for the patch and accept that your March data will have a gap. You can always delete the obviously incorrect days from your Fitbit history once accurate tracking resumes.

What to Watch For

Here’s how you’ll know when this is actually fixed:

• Google issues a firmware update specifically referencing step count accuracy and sensor data. Generic “stability improvements” updates may or may not address these issues.
• Your daily step count drops back to realistic numbers without you changing behavior. If you normally hit 8,000-10,000 steps and your watch suddenly shows that again instead of 18,000, the fix landed.
• SpO2 readings complete successfully. Open the Fitbit app, run a manual SpO2 check. If it completes and logs a result, that sensor is back online.
• Skin temperature shows new data points. Check the temperature graph in the Fitbit app. If new readings appear after the update, it’s working.

We’ll update this post when Google releases a fix. Until then, treat your Pixel Watch health data as decorative, not functional.

The Bottom Line

Google’s March 2026 firmware update has broken fundamental health tracking on Pixel Watch 2 and 3. Step counts are doubled, calorie estimates are inflated by hundreds of calories, and SpO2 and skin temperature sensors have gone dark. Google hasn’t committed to a fix timeline.

If you depend on your Pixel Watch for training decisions, nutrition tracking, or recovery monitoring, switch to backup methods now. Don’t wait for the fix. Don’t eat back the calories your watch is inventing. And don’t factory reset. It won’t help.

Your watch is lying to you. Plan accordingly.

---

Based on user reports from March 18-20, 2026, across Reddit, Google support forums, and Fitbit community boards. We’re testing on Pixel Watch 3 and Pixel Watch 2 units in-house. We’ll update this post as Google responds.