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?
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
Karl
This actually happen to me yesterday as well. It's the first time after a few months of 235 use.
I'm pretty sure this is a problem on the Garmin Connect side and has nothing to do with the watch. At the very least hopefully it's something they can fix retroactively.
Garmin is aware of this issue and is currently investigating.
I heard this comment a couple weeks ago and got slightly optimistic. However, keep in mind I reported this issue IN LATE 2015, and still see no resolution. I have patiently waited almost three months and have not seen any improvement on this.
At this point, your words that you are "currently investigating" mean absolutely nothing to me. When exactly are you working on it? It is either a huge flaw that will take total redesign to fix or it is NOT being worked on and is hopelessly stuck in some cue behind other issues. You sell a bunch of us a seemingly great watch that is a one-of-a-kind, and uses groundbreaking technology. It's a dedicated running watch AND it's a total activity tracker. We absolutely love the idea, and we think that ~$300 is a super price for this, so we eagerly buy the watch. It has simply not measured up with anything except running, which I already had in my 910XT.
Let me just say - the watch is only as good as the reporting that comes from it. Even if the watch collects accurate data, that data has to be able to be read and interpreted clearly and accurately to be of any use. The Garmin Connect website is full of flaws. The individual step charts (if totaled) do not match the total steps reported elsewhere. The calorie counts are off between each other in several places. The number of calories burned and distance traveled while walking, given a very similar heart rate and pace, vary wildly from day to day. This doesn't even begin to touch the issue of the calorie doubling.
I'm so cranky about this!! Each and every day I check to see if there are updates to Garmin Connect or to the firmware. Each day I read forum posts for some hope out there. I guess I will just have to keep waiting indefinitely.
Garmin, I have been a loyal customer for years with many products, and you used to be better than this.
I agree. The "Garmin is currently investigating" or "our engineers are currently working on" is getting real old. I've been in contact with support about the 71/72 HR issue (among other issues) since the middle of December. I was told a fix was going to be released soon. Well. January 26th a fix for the 71/72 issue was released. For the VSHR. It fixed the problem and yet here we sit with our 235's watching our HR's go to 72 and the screen usually timing out before it fixes on our actually HR. It's frustrating to no end!
I agree. The "Garmin is currently investigating" or "our engineers are currently working on" is getting real old. I've been in contact with support about the 71/72 HR issue (among other issues) since the middle of December. I was told a fix was going to be released soon. Well. January 26th a fix for the 71/72 issue was released. For the VSHR. It fixed the problem and yet here we sit with our 235's watching our HR's go to 72 and the screen usually timing out before it fixes on our actually HR. It's frustrating to no end!
For peace of mind, I'm telling myself that it's taking long for the next firmware release because they are going to fix everything in one big release. Really, really hoping this is why it's taking so long for the next update. :D:D
(In reality, they are probably working on the Fenix 3 or next generation products)
I agree. The "Garmin is currently investigating" or "our engineers are currently working on" is getting real old. I've been in contact with support about the 71/72 HR issue (among other issues) since the middle of December. I was told a fix was going to be released soon. Well. January 26th a fix for the 71/72 issue was released. For the VSHR. It fixed the problem and yet here we sit with our 235's watching our HR's go to 72 and the screen usually timing out before it fixes on our actually HR. It's frustrating to no end!
Yes, I have that same 71/72 issue as well. And yes, it is very frustrating. Each morning, I know that the only way I can count on an accurate RHR is to hit the down arrow, squint to see the numbers, and then repeatedly hit the arrow until I feel it has reached its minimum. Half the time I fall asleep again before it sets, or I am too irritated to relax enough to get it to reach a true minimum. Why is it that the watch has to be active on the HR screen in order for this calculation to occur? If I don't do this, my RHR is something like 57 instead of the more normal 40-44.
So, I can't count on an accurate calorie count or an accurate RHR. These were two of the most important reasons I bought this watch instead of just using my trusty 910XT.
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).
Darren; Excuse my ignorance but do you require to turn this back on for runs or will it go on automatically? And has this still been working for you?
Is everyone still having the same issues? I know I am:)
Yesterday I walked 4,389 steps with no run. That yielded 1.98 miles and burned 66 calories. (2,217 steps/mile)
Today I walked 2,652 steps and did a 7.5 mile run. The walking steps yielded 2.90 miles and burned 88 calories. (914 steps/mile)
How can almost 2K less steps steps take me a mile more in distance?
Saturday I ran 17 miles. That day I also walked 4,470 steps (about the same as yesterday). That yielded (in addition to the run distance) another 15.04 miles and burned 1,015 calories. That one was crazy off. (30 steps/mile)
Friday I ran 10 miles. That day I walked 3,630 steps that yielded 2.37 miles and burned 660 calories. That one seems almost believable. (1,532 steps/mile)
Look how widely the steps/mile ratio varies.
So sad that I keep waiting in vain for some help. Resting heart rate varies way too much as well, even when I try to force it to track first thing in the morning.
So on Friday I decided to test the HR and Distance on the Forerunner 235 against my Edge 1000.
Whilst they were fairly close in data it was still sufficient variances for me to advise Garmin of what I believe is an issue. I started both devices at exactly the same time on two separate occasions and each occasion the results where the same. I was riding in a lightly forested area, both don't believe I lost GPS on either device, in particular the 235.
First - with HR strap connected only to the Edge and the 235 using the OHR the results where significantly different. The 235 which showed spikes in HR that just don't show on the Edge. From historic use of the Edge & the HR strap this is show an even increase and decrease in HR which would be expected (imho).
Secondly - the distances varied by 0.5 mile over a distance of 6 miles on lap 1 and also on a 5.5 miles on lap 2.
