Can Only Pause/Finish Track Exercise 30min Later

[KelvinNg]

Android 4.4.2

I usually run 20km at a pace of 7 min per km and I use the "Track Exercise" in android app. At the end of the exercise of 20km, the "pause" was not responding and it seems like it always stucked at about 15km. Scrolled to the right-hand side of the screen, I can see the map and the red color path and it was still moving from about 15km. It might take about another 30min for the red color path to reach 20km. Then I could pause/finish the exercise. It showed me the correct path and split except the very last km. In many cases I could sync back to Fitbit server but in few cases it could not.

I have been having this problem for the last few months and it was quite consistent. Cleared cache and reinstalled the app did not help.

[TarinFitbit]

Hi @KelvinNg is great to have you here on the Community and for bringing this information. Try to update your Fitbit app to the latest version by going to your Google Play store on your device, tap the menu button, tap My Apps and choose the Fitbit app and tap update. The last version was released yesterday. I will love to investigate this issue. So, could you share with me a screenshot?    

Let me know how it goes, I'll be aware! 

[KelvinNg]

This was a run before the app updates on 16 May 2016. Everything seemed correct except I had to wait 30 min before I could pause/finish the exercise. Of couse this would affect the "splits" in the last km and also total time.

Have updated the app now and will see how it goes. 

[TarinFitbit]

Thanks for the screenshot @KelvinNg and yeah test it and let me know if the issue persist. In the meantime I'll try to investigate more about this issue, because is the first time I hear about this. Lets hope this bug get fixed with the new update. 

Keep me posted! 

[KelvinNg]

After the app updates on 16 May 2016, it is even worse now. Went for my usual 20km run. As you can see from below snapshot, the blue dot shows the GPS position where I completed my run. The red path still at 13km location and it took 1 hr to "catch up" my run then I could click "finish". After 1 min or so then it crashed. This run was not able to sync back to fitbit.com. I ended having 2 entries in my app - 1 entry using "track exercise" in the app, and 1 entry was automatically detected.

[63hokie]

Same issue.  Samsung S3 with 4.4.2, latest version of Fitbit app (2.25 5/2516).  Did 6.5 mile walk/jog.  Checked periodicly to see if red line was keeping up, it appeared to be doing fairly well (didn't check last 3 miles).  At the end the red line was approx. 1/2 mile behind.  Watched it slowly catch up.  When it had recovered about half that distance, the finish button appeared.  After hitting finish, the screen went all green, then all white, then the phone locked up.  No trace of the exercise afterwards.  An interesting point is that the beginning and end of the route were along the same street.  The outward portion was inaccurate in that it was maybe 50 ft offline and jumped around,  The finish I watched was accurate and very smooth.  If I had to guess, it seems that the frequency of GPS queries was grossly different.  The updating I watched at the end  was very slow, very small increments.  Althought I don't see why large increments at the beginning would affect the accuracy.   I'll pay more attention to later portions of the route next time to see when it starts falling behind.  Thanks for anything you can do.

[63hokie]

Did 5.6 miles last night.  i will jog 1/4 to 1/2 mile and then walk for ~50 yds, result is about 15 - 16 minute miles.  While jogging the cell phone is in my pocket with the screen locked.  Each time i dropped to a walk I checked the tracking map.  Until 3 miles, the screen would quickly update to catch up to my current position.   At 3 miles, there was a noticable lag, the red line lacked about a 1/4 of an inch.  By 4 miles it was pretty useless, it couldn't keep up with my walking pace.  After 4 miles i just walked, and left the screen on so I could watch it.  It kept dropping further back and took 15-20 minutes to catch up when I stopped.  Unlike the previous run, the red line track was very smooth for the entire route.  After the red GPS line caught up I was able to finish the exercise and it shows on my cell phone, but not on the windows 10 app, no pace, no heart rate.  In its current state, the app is pretty useless for any but the shortest exercises.

[TarinFitbit]

Hey guys @63hokie @KelvinNg @SunsetRunner! Thanks for sharing this important information, this is very interesting and I'm investigating this issue to find a solution for you. In the meantime, try this:

1. Clear the Fitbit app Browser Cache by logging out from Fitbit app > Phone settings > Fitbit app > Clear Cache > Clear Data > Close the app > Log back into the Fitbit app

2. A friend of mine had this issue in the past, when he was running too many apps in the background. Like using MobileRun and Spotify at the same time. 

I will let you know any updates. 

[KelvinNg]

Cleared the data already. Went for a 7km run (mixed of run, walk, climb, exercise at the same location) for 1 1/2 hr. I could click 'finish' the app and everything worked perfect this time round. However, as far as my memory is correct, in the past I only encountered problem for longer run say more than 10km but never for a short run.

Fyi, I don't have MobileRun or other fitness apps. But if Fitbit app fails me again, I may give others a try. I have Spotify but hardly use it.

[63hokie]

Cleared the cache & data for fitbit and cardio trainer.  Did same 5.6 mile route with the same results.  The behavior on the 2 runs was very consistent.  Started out well, but by 4 miles, the red GPS line couldn't keep up with me walking.  Will monitor Play Store for app updates.  Otherwise I'll have to stick with cardio trainer for anything over 3 miles.  Let me know if you want me to try something.  Thanks.

[KelvinNg]

Updated the app on 1 Jun. Went for my usual 20km run. The same usual issue came back. The app was still at 15km and it took another hour before I could 'finish' the app. And as usual it crashed.

[TarinFitbit]

Hey guys @KelvinNg @63hokie! Sorry for the delay, but I was trying to find a solution for this issue with my friend @ErickFitbit. 

So, could you please take a look on this:

1. Make sure you have WiFi or cell data turned on.  

2. GPS is configured to allowing tracking even when the phone is locked.

3. Finally, locations services is configured to allow MobileRuns.

In addition, we would like to know the following:
2) What make/model handset are you using?
3) What OS version are you running? (You can use this tool to find out: http://whatismyandroidversion.com/)

Thanks for all your help! 

[63hokie]

OK,

1.  Data is definitly on.

2.  Don't see any setting to enable or disable this.  When I unlock the phone and it updates the screen, it has the correct route.  It has obviously been receiving gps data while locked.  Also Cardio Trianer works quite well.

3.  Again, don't see any way to do this.  But, again, MobileRun is obviously receiving gps data. Just that Its ability to process it deterorates over time, at a quite repeatable rate.  Wondering if it has a memory leak.

Samsung S3

Android version 4.4.2

[KelvinNg]

Went for usual 20km and the same usual problem again!

1. Generally my battery saver app will turn off data as soon as screen is off. However, for this troubleshooting, I made sure that the data is ON for the whole run.

2. I don't think I have any app settings to turn OFF GPS while screen is OFF. In other words, my GPS is always ON.

3. The google location setting for Fitbit app is set to "High accuracy".

I don't think it has anything to do with the GPS because Fitbit app correctly tracks my position ALWAYS but just that it "lags" behind.

LG G2 

Android 4.4.2

[KelvinNg]

Used the latest app update on 14 June 2016. Went for same 20km run and same problem.

Installed MobileRun app. Went for another usual 20km run. Used both Fitbit and MobileRun apps. Guess what!

- MobileRun app - it was just perfect!

- Fitbit app - I could click 'finish' after 1 min or so. Not bad though! BUT.... after I synced with Fitbit Charge HR, I ended up having 2 concurrent exercises. The other 1 was from the automatically recognized exerciese. After 1 hour or so, when I checked my 2 concurrent exercises again, the first 1 was gone. To sum up, the Fitbit app failed me again.

If Fitbit app works for me, I would just perfer to stick to 1 app instead of having an additoinal 1.