01-31-2024 16:31
01-31-2024 16:31
I had purposely not upgraded to the latest version for a long time because my versa 2 was accurately recording my HR for my runs but one day Google somehow forced an upgrade on me and now my HR while running is measuring a good 20+ bpm too high. To top it off it also can’t perform a simple division calculation accurately. My average pace which should just be duration divided by distance is wrong. How can you mess that up? 56 min/6.56 mi = 8.53 min/mile not 10.09min/mi. Also I know my avg HR was not 161, it was 138 according to my Polar monitor. The super annoying thing is that it was all working pretty well until they forced that update on me sometime after I linked my google account. So lame.
02-10-2024 12:15
02-10-2024 12:15
Yes I agree! Fitbit has no interest to address any problems. I’m checking into Garmin and Apple. I’m tired of no resolution to all their issues.