Galaxy Watch Ultra 2's VO2 Max Metric Glitch: A Fix is Coming
A recent issue has been reported by users of the Galaxy Watch Ultra 2, where the device is failing to display VO2 Max data for certain running activities, specifically "track running" sessions. Despite good GPS coverage, pace, and activity time, the watch is not calculating or displaying VO2 Max readings for these sessions.
According to a user report on the Samsung Community forums, the issue is caused by an error in the watch's VO2 Max calculations. The user shared screenshots showing that the watch is not calculating VO2 Max readings after logging a track running session, with the error message stating that 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, the user's data shows that they ran for more than 10 minutes at speeds well above 4 km/h, and the GPS signal was not spotty.
Interestingly, the watch is able to measure VO2 Max data for outdoor running sessions, as evidenced by the user's screenshots of their outdoor running logs from the Samsung Health app. A moderator has responded to the user's post, stating that Samsung developers have confirmed the issue and are working on a fix, which will be released in a future software update. However, no estimated timeline for the update has been provided.
