Gear Fit 2 Missing Parts of Run

Colin1970

New member
Sep 25, 2017
2
0
0
Recently, my Gear Fit has suddenly stopped recording part of the first kilometre of my runs. I run at about 4:30 per km but recently my GF has started recording that I complete the first km in somewhere between 5:45 and 7:30; thereafter it then seems to record distances correctly for the rest of the run; the S Health app shows the route correctly, but records a speed of zero for period of time, meaning that having completed somewhere around 6.5km, only 5.7km (for example) is recorded as completed. This only seems to have started happening in the last few weeks.

Any ideas on what is wrong and how to correct it?

It sounds as though it's not locking on to the GPS signal for a long time. This can relate to weather and other obstructions, but still it doesn't seem very likely that it would take that long. I've heard it suggested that if you start within range of your phone and then move out of range when starting the run, it may not realize that it's on its own instead of using the phone's GPS. But I don't think I've seen that issue on mine.

I've had a problem a few times where it would not lock on at all for the entire run (showing 0 miles and 0 calories, which seems odd considering it should have measured steps and heart rate even without the GPS). As if something was stuck. And once it got into that mode it didn't seem to ever work, even on the next run, but after rebooting the band everything was fine again.
 
Last edited by a moderator:
Re: Gear Fit 2 not recording runs

Recently, my Gear Fit has suddenly stopped recording part of the first kilometre of my runs. I run at about 4:30 per km but recently my GF has started recording that I complete the first km in somewhere between 5:45 and 7:30; thereafter it then seems to record distances correctly for the rest of the run; the S Health app shows the route correctly, but records a speed of zero for period of time, meaning that having completed somewhere around 6.5km, only 5.7km (for example) is recorded as completed. This only seems to have started happening in the last few weeks.

Any ideas on what is wrong and how to correct it?

Having run recently without listening to music, it appears that the problem may be something to do with me trying to record a run while listening to music.

Anyone got any ideas?
 

Trending Posts

Forum statistics

Threads
956,347
Messages
6,967,720
Members
3,163,517
Latest member
NameRingtone