This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Multiple Errors

I am unhappy with the quality of product I own.

My VO2 is a previous high and never drops, despite the fact I am significantly unfitter now.

When my sleep is recorded, the data on app can change from when it is first synced to when it is checked later in the day, recategorosing sleep.

The run data is significantly out. I ran today for 6.33km Which i recorded on another app using only mobile phone GPS. My garmin vivosmart 4 recorded it as 8.35km. I cross referred this to an online map and the rival app is correct.

Whats going wrong with my device or software?

  • VO2 max depends a lot on correct user settings on the device. Make sure that you got the correct pulse settings and described yourself as true as possible.

    Is the sleep data incorrect after it has been updated? If it is more correct after the update then it is good.

    I see now that Vivosmart 4 got no GPS so I've updated my answer and removed the GPS part. Are you using a connected GPS when you got 8.35 km or did you just use the step and step length? If it is the latter you must set the correct step length.

  • Thanks for taking the time to chat to me about this Andy.

    My height and weight are accurate, and I have never entered any pulse information before. I have now put in the max pulse measured from my last run and I guess I'll see if that jogs it tomorrow. I have no idea why I'd have to set this manually when I haven't before and when the device measures my pulse for me?

    The duration of sleep data is the same as a total, it's the classifications of sleep type. Ie, when it first syncs I have deep sleep recorded, when I check it later it has all been recategorised as either light or REM.

    My Vivosmart 4 is linked to my phones GPS and I've never set a stride length and nor do I know how to... Again, I'd expect the device just to log distance via the GPS when the step length isn't set.

    It's a shame because the device has worked accurately previously.