08-02-2023 11:38
08-02-2023 11:38
Every single time I go for a jog, I start a "Run" activity on my watch. The activity counts down and starts within a few seconds, so I begin my run. As I run, I check my watch, and the distance appears roughly correct.
However, when I complete my run and get home, the data on the map at the beginning of my run is completely inaccurate. The path starts 300 to 500m into my jog, showing an inaccurate start point, pace etc.
This makes it hard to interpret the data related to my pace, etc.
That being said, somehow, the total distance ran is correct. I compared my route to the walking directions in Google Maps. Even though the path shown in FitBit's Android App shows a starting point several hundred meters into my jog, thus showing a shorter line, the total distance ran that is reported matches the total route as recorded in Google Maps.
On top of this GPS inaccuracy, on my most recent run, the heart-rate reading was showing a flat, constant 74bpm for the first 2/3rds of my run, then jumped up to the accurate, fluctuating reading >100bpm.
As a note, I keep my phone in my pocket as I run as well. Though, I'm not sure if this is relevant. Sometimes I have left my phone at home, and I believe the issue was still present.
What could be causing this?
08-03-2023 01:06
08-03-2023 01:06
Start your run from the Exercise app on your watch not from exercise shortcuts. Shortcuts don't wait until GPS connects. When you start from the Exercise app you can hit run after you see that GPS connected.
08-03-2023 06:17
08-03-2023 06:17
I will try that on my next run, thank you!