Blaze stops tracking runs at 1km

[CeeChelle]

For the past couple of months at least once a week while using the run tracker feature it stops and returns to the home screen as if the run has been terminated/completed. 

I'm noticing this is after I've re-started my blaze because it wouldn't pair with my phone for the GPS or because the app has requested I reboot my phone for app notifications to be restored (presumably after an update). I don't run with long sleeves and I'm 100% certain it's not because a button is accidentally being pressed - I already thought of that and monitored. At the time it terminates the run it is always connected to my phone with the GPS turned on.

It's fairly frustrating but at this point I know it was a 1km that I've run and it means attempting to re-connect my phone whilst still running so I don't lose any pace or momentum. I was wondering if anyone else has had this issue and how they've solved it? I would quite like to go back to having complete run stats! 

Thanks in advance. 

[RunningFreak]

Hi @CeeChelle!

Make sure your Blaze is not paired with any other device. I would try the following:

1.) Sync your Blaze so you don’t risk losing data.

2.) Remove your Blaze from your Fitbit account.

3.) Set Up your Blaze as a new Fitbit Tracker, and then turn ‘All Day Sync’ to on.

Let me know if that was successful or not.

[CeeChelle]

Thanks @RunningFreak. 

Definitely isn't paired elsewhere, I'd thought of that but have no need for it to be with any other device.  

I'd tried everything but that before, not sure why I didn't think of it. Have done that so shall see what it does on my next scheduled run, which providing my knee behaves, should be tomorrow. 

Shall let you know 🙂

[RunningFreak]

Great! Looking forward to it!

[MikeS1971]

My friends Blaze starting doing something very similar last week. Except at 2.74 miles. Every time it gets to 2.74 miles, it stops the work out like you've manually stopped. 

2.72 miles, all was good. 

2.73 miles, still good.

2.74 miles, screen goes black, then it displays the time. 

No amount of resets have fixed it so far. 

[CeeChelle]

@RunningFreak - It didn't cut out at 1km, but it still stopped tracking at 4.71 km which is really annoying when you're on a 5km run, but usually run longer distances! Thanks for the tip though, we'll see if it does any better for the next couple of runs, but sadly I'm not confident at this stage 😞 

@MikeS1971 - Yup, looks like it might well end up being that way for me too as despite unpairing/pairing it's still doing it, albeit today it tracked for a bit longer! It's really frustrating! 

[RunningFreak]

I’m sorry to hear that your problem is not 100% resolved. At this point, I would highly suggest contacting Fitbit Support via Chat!

Let me know if this helps!

[CeeChelle]

@RunningFreak & @MikeS1971 Sorry it's been a while before I could update this! With customer support's help we tried a couple of things but unfortunately it looks to be the tracker itself and so they've replaced mine as it was under warranty still. Hasn't arrived yet but hopefully no more issues!

Thanks for your help and comments and I'd suggest if anyone else has this issue to just contact direct after trying multiple reboots, disconnecting and reconnecting etc. 

[LSD1979]

Hi ive been having the same issues with my blaze and so far is always at the 1k mark... how long did it take for them to sort out. I will have to email them. Ive tried everything like you but i run everyday so its driving me mad now... 

[MikeS1971]

My friends that I mentioned above never stopped doing it. She moved onto a Samsung. 

I used to have a big list of friends, family and co-workers that had FitBits. We'd all do competitions and try to out do one another. I don't think any of them have FitBits anymore. 

[LSD1979]

Oh its so annoying beacuse i really like it. I used to have a tom tom buy they just dont work for me and with fitbit it pushes you when all your friends are linked. Wish they would just sort out the niggling problems. If its more than one then it should be fixed with an update i would think. 

[CeeChelle]

Eventually they gave in and sent me a new one...it happens occasionally still but not every time. I just haven't gotten around to contacting again 😞

It's really irritating, I agree! Been hoping they fix it as it's clearly a software bug but no joy yet.

I found one way around it was to start the run from the app but it's not ideal and I hate doing it that way as then I don't get stats during, which I find really motivating!

My best advice is to email them and keep on and explain everything you've tried in detail - that's what I've done.

Now though I wonder if upgrading to the ionic will solve it...which is on my to do list but I am worried it'll have the same issues 😕

Bit of a wordy reply, But honestly the best advice I have is to contact them directly as my newer one doesn't do it nearly as much (still sucky I realise, sorry!)

[Tonys_cool]

I got mine for Christmas and I had the same issue during my first two runs. I tried turning off the notifications at each km and it seems to have solved the issue... I've only had the Fitbit for a week now, so time will tell if the issue is really fixed or not.

[LSD1979]

Hi... they offered me a replacement in the end... i did everything they suggested and still nothing.. even my new one cut off the other day at 4k... i think its because they use the gps from your phone as its not built in and it just randomly disconnects... to be honest it would be better if it was built in but as with everything its about money they make lots of different watches each with slight variations to sell more. Really the surge is probably better because now i have a samsung using the music is a pain as you have to reconnect its a joke.

Sent from Yahoo Mail on Android

[chriswoj]

I am experiencing a very similar problem, none of the solutions I found on fitbit community seems to help - yesterday my blaze stopped tracking after 4k of 10k run, few days ago it stopped just after 2k. I really like fitbit but I won't risk buying it again.

[LSD1979]

Contact fitbit they are extremely helpful they sent me out a replacemt after i had tried everything else.

Sent from Yahoo Mail on Android

[LSD1979]

I tried everything i had read about and contacted fitbit who asked me to try a few things which i did. As it continued the sent me out a replacement pebble. I found their customer services brilliant. 

[Tonys_cool]

Just turn off the notifications at each km, it will stop shutting off, had the same issue and permanently fixed it.

Sent from my iPhone

[LSD1979]

Shouldnt have to especially if your attempting to keep track of speed etc..but a good short term remedy until they fix or replace... 

[Mattblakey]

I have just had the same issue, this is the second time it has happened to me. Very frustrating!