Bug: Daily Steps Distance not accurate

Go Home Garmin. You're Drunk

i wish it was acknowledged at least. instead total silence....

tbh i dont know where the bug is.. when i turn off BT, but leave whr on, this bug presents itself inside my watch, so im pretty sure there is more than 1 source of the problem....but for meits looking like a non server problem

as soon as whr is off, no bug anywhere though

Your watch is accruing steps while you cycle. Another user in the F3HR forum is seeing this also.


Steps which are accrued during an activity don't show up on your "steps" meter but they WILL be factored into your overall distance for that day. So for some reason your watch is accruing steps while you cycle.

The watch shouldn't be able to think you are walking/running while you are inside of a cycling app.



These watches are an absolute mess on the software side...

I have been using a VAHR for a week or so now and thought the same that the 'distance travelled' value was including the erroneous steps recorded whilst logging a cycling activity. What I've determined on studying this is that the device itself is reporting the distance correctly, i.e. ignoring the steps logged during the cycling activity. However the device syncs these erroneous steps to Connect and this adds the distance for these dodgy steps.

This has cleared up for me one of the discrepancies between the VAHR and Garmin Connect. This needs work as really the device shouldn't be logging thousands of steps when logging a non stepping activity in the first place, but if the device can overcome the inaccuracy then surely GC could employ the same theory?

How do you explain this one then?

Manual run activity... was not wearing watch during activity.

Manual run activity... was not wearing watch during activity.

Hard to 'explain' this one with the level of detail however, if I were to make a guess I'd say that you picked up the watch and put it on your wrist while getting ready and not at the moment of pressing start for your activity, then similar at the end of the activity, pressing stop prior to moving to where you took the watch off and put it down. 243 steps are easy to accrue, even if the watch is not on your wrist but being carried, it will still register movement and count steps.

As an experiment how about pressing start on the activity before picking the watch up next time, then after pressing stop, don't take a single step till you've sync'd it with connect and viewed the data to see what it says?

Hard to 'explain' this one with the level of detail however, if I were to make a guess I'd say that you picked up the watch and put it on your wrist while getting ready and not at the moment of pressing start for your activity, then similar at the end of the activity, pressing stop prior to moving to where you took the watch off and put it down. 243 steps are easy to accrue, even if the watch is not on your wrist but being carried, it will still register movement and count steps.

As an experiment how about pressing start on the activity before picking the watch up next time, then after pressing stop, don't take a single step till you've sync'd it with connect and viewed the data to see what it says?

The watch was not worn during the run. It was in my truck charging.

I guess all I'm looking for is Garmin to acknowledge that they have an issue with this. A simple "This is a known issue and we are working on it. Thanks for your feedback." would suffice. Ya know?

Dear Garmin,

Here is another one: .

Love,
Brad