10-07-2020 15:12
10-07-2020 15:12
I have been tracking my distance while running simultaneously on my phone and fitbit sense and I get about 6.5km on my sense, while my phone says 8km. For this reason my pace is way off as well. Upon double checking on google maps I found that my route was indeed 8km. What is causing this bug?
Also, the app says there was an elevation of 60m on my route, while my route is flat, with the exception of a bridge, which is tops 5m high.
10-07-2020 15:18
10-07-2020 15:18
Something tells me that we became the official beta testers of this company.
10-09-2020 07:11
10-09-2020 07:11
Unofficial beta testers, if it were official, we would get paid at least.
10-09-2020 07:12
10-09-2020 16:16
10-09-2020 16:16
I've had my Sense for 1 week and I noticed this problem too. I upgraded from the Versa and I also run on the NordicTrack iFit - both these devices were calibrated to show similar accurate data on pace, distance, elevation, floors, etc. Anticipating even better data, I upgraded to the Sense and now I am running a whole minute slower than last week and miles less - even though my Nordic Track iFit machine reports otherwise. Very disappointing to spend the money on an upgrade when I may just put my Versa back on. Would love to know if there is a fix for this.
12-02-2020 18:23
12-02-2020 18:23
I also have the issue too. I updated from charge 3 to sense. I used my phone (android) and my wife's iphone to track my run. From google maps and phones GPS, the distance should be 5 km, however, the sense showed only 4.6km. and I also noticed that not only the sense connected to GPS very slowly, nut also the time for first km was recorded much longer. I don't know if this is a defected unit or it is just a common issue. @Fitbit