Fitbit Blaze randomly stops recording my runs / bike rides.

[Sergie_RSA]

I have had my Blaze for over a year now and in most cases things are great. However, over the past 1-2 months my runs (and bike rides) stop recording after a while (normally after more than 1km).

In all cases, I start off synched to my device and using GPS assist mode. Device (phone) remains with me (I successfully log the activity using RunKeeper) and always have good internet connectivity (I see some people in other forums have linked wifi/internet connectivity to GPS tracking issues).

In particular, my Saturday runs take place at the same place, same time every week. For the 1st 6 months of the year I had no problems...from mid June'ish, my issues started.

To the FitBit technical staff, what happens if the GPS is temporarily lost during an activity tracking ? Does it stop the activity or ignore logging until the GPS returns ?

Regards,

Serge

Moderator edit: format

[AlejandraFitbit]

It's great to welcome you @Sergie_RSA, thanks for troubleshooting this by yourself.

If you haven't do this so far, I recommend taking a look at the My Blaze GPS is not working post and follow the instructions provided there. After following those steps, test your tracker.

I hope this helps, let me know the outcome. 

[Sergie_RSA]

Hi Alejandra. I went through the provided instructions and could not find anything new to what I have tried.

My main concern is that is does connect and log the activity for some time...but it stops recording for an unknown reason.

Do you know what is suppose to happen if the phones GPS disconnects momentarily ?

[ashwooi]

That's exactly what happened to me mid June. At the same time the battery life dropped dramatically. This coincided with changing my phone from LG G4 to Samsung S8. Fitbit replaced the Blaze but it now won't connect to GPS at all.