Galaxy Watch Ultra 2 is glitching out on this health metric, but a fix is on the way

If you’re using a Galaxy Watch Ultra 2 to log running sessions, you may have noticed it isn’t displaying VO2 Max data for certain running activities. Well, you’re not alone. It seems the Galaxy Watch Ultra 2’s VO2 Max calculations are failing for “track running” sessions despite good GPS coverage, pace, and activity time.

According to a user report on the Samsung Community forums, the Galaxy Watch Ultra 2 is encountering an odd error when calculating VO2 Max. The user shared screenshots showing that their watch was not calculating or displaying VO2 Max readings after logging a track running session.

We translated the screenshot with Google Translate to see the error displayed in the Samsung Health app. Apparently, the app thinks the user did not run for at least 10 minutes at speeds of 4 km/h or more in an area with a good GPS signal. However, based on the data in the screenshots, the user ran for more than 10 minutes at speeds well above 4 km/h. The user also states that the GPS signal was not spotty.

Surprisingly, the Watch Ultra 2 is reportedly able to measure VO2 Max data for outdoor running sessions. The user shared screenshots of their outdoor running logs from the Samsung Health app, and their watch has calculated a VO2 Max value for those sessions.

If you’re also facing a similar issue with your Galaxy Watch Ultra 2, you can rest easy. A moderator has already responded to the user’s post, stating that Samsung developers have confirmed the issue. The company expects to resolve the glitch with a future software update. However, the moderator did not provide an estimated timeline for the update.