Gps walks tracking starts half way.

[Skellibert]

Well not half way.
I have a charge2 and a samsung s5.
I was wanting to gps track my walk/runs, but today I noticed two things:
1. The walk starts with about 3 mins already on the clock, and
2. The tracking starts a good ummmmm 300m into my walk.

What am I doing wrong?
I start the tracking from the phone app, wait till it finds gps position, press the "play" button (looks like play on a music app), and start walking.
When I check the map later, the trail doesn't start till about 300m or so down the road.......

[Skellibert]

This very quickly dropped off the first page, and there are no comments.
Either no one else has had this, or the experts have no answer - or mayve it just hasn't been seen by the right people, so this is a 'bump' because I would really like to use this feature, but as it stands right now it looks like strava moght be the go from the comments in other threads.

[Skellibert]

So is there no solution for me?
Or have I written it so poorly that nobody inderstands it?

[CarlosMo]

Hi @Skellibert it is a pleasure to have you with us in the Fitbit community. 

As you mentioned, you are doing correctly the procedure to measure the walk with the GPS of your Samsung s5. 

In this case, I recommend you performing a restart of your Charge 2:

1. Plug the charging cable into the USB port on your computer or any UL-certified USB wall charger.
2. Clip the other end of the charging cable to the port on the back of the tracker. The pins on the charging cable must lock securely with the port.
3. Make sure the button on your tracker is aligned with the button opening on the charging cable. You’ll know the connection is secure when the tracker vibrates and you see a battery icon on your tracker’s display. Your Charge 2 will begin charging.
4. Press and hold the button on your tracker for four seconds. When you see the Fitbit logo and the tracker vibrates, this means the tracker has restarted.
5. Unplug your tracker from the charging cable.

Let me know how it goes. 

[Rich_Laue]

One more thing, after starting walk feature from the Charge 2, make sure the line to the right of the phone icon has diss peered.

[ChasPro716]

 Same behavior for me on Droid Turbo when starting from the Charge2 walk mode.

I don't think resetting the Charge2 will have any affect.

[Rich_Laue]

Restarting the phone usually allows my tracker to connect again make sure the Charge 2 shows a GPS connection before starting out. This is explained in the user manual  

[Debehehe]

I have this same problem, and have tried this reset and it doesn't help. I have also tried restarting the phone, uninstalling and reinstalling the Ap, nothing changes. Very frustrating! Additional problems:

1.it will no longer record a walk, I select walk but it continues to record it as a run - not a walk. Only way to record a walk it to start it from the Charge 2 rather than the phone ap.

2. When performing Sync Now and sync is completed, it says sync 4 mins ago, when it used to say "a moment ago"

Any help much appreciated!

[Rich_Laue]

Starting the walk from the app, as mentioned is when the user is not using the Charge 2. That said if mentioning the app, it would be Benoist to include what OS the app is on. As we know a walk recording as a run is an issue with the Android app, but some have reported it on iOS.

Are you using the app to record your walk @Debehehe  if so then your problem is not related. You simply want to make sure that the app has a GPS lock before heading out.

Normally if the app says synced 4 minutes ago, it means the last sync was 4 minutes ago and the recent sync failed What does it say on the web dashboard?

@Skellibert  are you waiting for the Charge 2 to show that it has a gos lock from the phone.

[Debehehe]

Thanks for your assistance @Rich_Laue. The app is on a Samsung S8, so Android OS, will check out that issue link for the walk problem.

I have been using this Charge 2 and Samsung phone to record my runs for over 12 months with no issue until recently and an earlier version of each for about 2 years before that. It is the problems raised by @Skellibert that are really frustrating. I can't compare my run performances when the app is starting with time already on the clock - and this number is gradually increasing each time I use it. Whether the starting point on the map being about 300m after my actual starting point is affecting my run statistics as well is hard to know.

Syncing is not failing - Web dashboard says "just now" when app says "4 minutes ago". This not really a problem - just thought it may be related and help point to a solution.

So guess these issues are all app related, perhaps I just have to hope they are fixed in the next update?