Yesterday, I logged a 13 mile walk as a "run" using my 235. I logged it as a run, as there is no hike or walk activity selection. I used my footpod and Garmin ANT+ Chest strap, as these are far more accurate than the watch (they need to fix this). I recorded just shy of 13 miles and 31,000 steps, and was dual gps'ing with GPS and GLONAS. All was well and good until this morning when I looked at my connect sync and noticed that it claims 30 miles and doubled the calories. It appears to me that it is taking the total steps and adding them into the formula after already logging them in the activity. This is incorrect. I noticed that my assumed active calories was also roughly doubled. This seems like it can be easily addressed, and MUST be. Has anybody else noticed this. Also, why no "hike" or "walk" activities?
Add me to the list of 235 users having this problem. Does it go away when the connection between MFP and Garmin Connect is terminated? I'm planning to try that tomorrow, but am curious if anyone has already found it to be an interim fix.
No, in my experience, nothing you can do can fix it (even in the interim). It's severity changes, yesterday was almost spot on for me but other days it's out by quite a bit. Only Garmin can fix it.
Log a case with Garmin Support. The more cases logged for this issue the better.
Log a case with Garmin Support. The more cases logged for this issue the better.
Thanks. Will do. It's a shame, because the watch is working pretty well for me otherwise. So much so that I've barely worn my (soon to be sold) Apple Watch since Thanksgiving.
The interim fix is to turn off the HRM during your waking hours (easy to do). Calories in both GC and MFP are then based on steps and look MUCH more reasonable. Unless you have another reason to want the 24/7 HRM information this is a good compromise. I turn it back on when i go to sleep to get my daily RHR (which is when it's always lowest).
The added bonus is that battery drain goes from ~7-8% per day to 3-4%! Note i keep BT off as well, so no notifications. Basically, how many days i get between charges is determined by how much i run. Getting well over a week and 70-80km of GPS is pretty fantastic i must say!
In summary: calories in MPF look believable, i still get RHR, and i only need to charge after running ~80km (~7.5 hours for me).
Got it. Does that also fix the distance bug for steps? When I look at my activity breakdown under Steps for today, GC is showing 8.09 miles for 3,244 steps. The 8.09 is likely my total mileage for the day, as I had a 6.5 mile run (which appears to have been logged correctly).
Got it. Does that also fix the distance bug for steps? When I look at my activity breakdown under Steps for today, GC is showing 8.09 miles for 3,244 steps. The 8.09 is likely my total mileage for the day, as I had a 6.5 mile run (which appears to have been logged correctly).
Wow that's some impressive olympic-grade walking! :)
Unfortunately (probably) not. This is just to stop the watch using your HR to determine daily calories, given the HR sampling is so infrequent and the HRM can get stuck on some high-ish value for 1-2 hours (and giving you a stupid number of calories for it). It very commonly happens after an activity when your HR is up a bit anyway.
What you describe above seems to be a different bug. I don't have that problem fortunately.
Got it. Does that also fix the distance bug for steps? When I look at my activity breakdown under Steps for today, GC is showing 8.09 miles for 3,244 steps. The 8.09 is likely my total mileage for the day, as I had a 6.5 mile run (which appears to have been logged correctly).
I've had this happen several times and it seems to come and go. As of late, when it has occurred, I've also missed out on a chunk of logged step/HR data around the activity time (as in it doesn't show on GC).
You're right when this particular bug occurs, the distance and calories from the activity are added to the daily so you get a doubling up of both. The "lesser" version of the bug is not a complete doubling up of the distance/calories but a slight increase (or decrease sometimes) in the distance and calories from actual. Even the steps widget and the full steps page will show a discrepancy. You can see what I mean by doing a sync and then immediately looking at GC and comparing it with what your watch displays. The steps widget will be exactly (or +/- 2~5 kCal due to time delay) the same as the watch, while the full steps page would be off by a bit or a lot depending on how bad of a bug has occurred.
We are actively looking into the issue reported by many of you. If you are experiencing any other issues please report that to our Customer Service team. Have a good day and keep running.
We are actively looking into the issue reported by many of you. If you are experiencing any other issues please report that to our Customer Service team. Have a good day and keep running.
This is very exciting news! Thank you for following up directly on the forum for this. It is much appreciated.
We are actively looking into the issue reported by many of you. If you are experiencing any other issues please report that to our Customer Service team. Have a good day and keep running.
Just want to say, i really appreciate you posting a short note to let us know. If you need beta testers you know where to come find them! :)
Another happy active calorie double counting customer
Another new FR 235 user with step calories seemingly still counting towards your active calories, whilst you are earning calories from a run activity.
Surely Garmin would have thought about this so that when two things are happening at the same time (earning steps and running), you would not get active calories for both!
This is a deal breaker for me for this device.
I did a 5k run today, got back and the activity said 400 calories, but when I went to look at my active calories, I had earned another 400 from the steps, so 800 calories for 27 minutes exercise, arrrrrrrrrgh!
Anyone know how to fix this without disabling the features I bought this device for?
Any word from Garmin on a fix? I have raised a support ticket too
