GPS Stopped Tracking/App Unresponsive

[M.F.]

Hello.  Just wanted to make you guys aware of a couple of bugs.

I've never used the GPS part of the app before, so for fun over the past 3 days I've been using the GPS to track my bicycle rides.  I took basically the same route every day, and the odometer on my bike was between 25.6-25.9 kms on those days.

The first 2/3 my ride is through densely wooded/ravine/trail areas, and the last 1/3 is through suburban streets with houses/parks (no high-rise buildings).  I'm very impressed with how accurate the GPS is in the wooded/ravine areas.  However, I found two issues with the app at the conclusion of all 3 of my rides.

The first issue is that the GPS stopped tracking my route during the rides.

April 18th - "Run" mode - GPS stopped at 16.71 kms

April 19th - "Hike" mode - GPS stopped at 17.30 kms

April 20th - "Walk" mode - GPS stopped at 16.30 kms

The second issue is that the app was unresponsive at the conclusion of my rides.  The "Pause" button would not work, so I couldn't "Finish" the rides.  And the back arrow button on my phone would not work either.  However, the stopwatch clock was still running and the voice cues button was still working.

I restarted my phone on all 3 occasions, and that got the app to work again.  However on the 20th when I restarted the app, the GPS drew a straight line on the map from where it stopped tracking me to my finishing point, totalling 21.27 kms.  And then when I clicked on the "Track Your Exercise" button on the Dashboard, the app crashed.  On the 18th and 19th, the GPS did not draw a line and the app did not crash.

Samsung Core

Android Version 4.4.2

Fitbit App

Version 2.22

Charge HR

Firmware Version 122

And I voted for adding Cycing to the GPS part of the app in your Feature Requests board.  So hopefully you guys will be working on that at some point!

Take care.

[RobertoME]

Hello @M.F., welcome aboard to our community and thank you for sharing the glitches you have found using the Mobile Run feature on your mobile device. Certainly I will be sharing this with the teammates to investigate further and also thank you for your participation in our feature request board. The product team looks forward to reading and incorporating users suggestions into future versions of Fitbit trackers and apps. 

Regard the issue with the GPS, I'm pretty sure you already updated your Fitbit app to the most recent version 2.24. which improved stability and address and fix some bugs. If you haven't please visit the Google Play store and update the app. If the issue still persist in some occasions after an update is require to log out from your Fitbit account and restart your mobile device. Once the phone has restarted go back to your Fitbit app and log in again. 

Some recommendations that may come handy are:

1. Make sure your phone can track your activity when you're out of Wi-Fi range. This is usually achieved by making sure Cellular Data is turned on.
2. Make sure GPS can continue tracking while your phone is locked.
3. Make sure your phone can identify your location.This is usually achieved by enabling Location Services within your privacy settings.

Hope this issue still not persist and keep me posted how it goes. 

[Grimbeard]

Resurrecting this thread as I'm having the same problem. The app has twice failed to allow me to "Finish" at the end of a walk, although the timer was still running, and the app was unresponsive to any commands. Only a force-stop through Android app manager could exit it. Re-starting the app after force-stop opened it with the (incomplete) distance and​ the timer where it left off, and restored control allowing me to "Finish". On both occasions the GPS track stopped after approximately 2 hours, in open ground with very good GPS signal.

P.S. I am on the latest update of the app.