Bluetooth connection being lost during activity (RUN)

[GarethDPhillips]

I am having real problems with my Blaze in conjunction with my Android phone (specifically a Google Nexus 5x) when tracking an activity. Phone is runnig 7.1.2 but behaviour was the same on 7.1.1

I am using my Blaze to track my running, and I am finding that the Bluetooth connection keeps dropping during the run, despite being initially connected, which in turn causes the assisted GPS to stop tracking my run.

I have searched the community and there are various reports of this behavior, but no definitive solution. I am open to the possibility that this may be related to my Blaze and mobile model combination.

I have to say, the bluetooth connection to the Blaze doesnt seem amazing on my Nexus 5x as sometimes when I open the app, it can take a while for the connection to establish and for sync to start, even though I have it set to be always connected?  Bluetooth connections to my headpones, or car, or any other device are bullet proof. It just seems to be the Blaze that is flakey.

Specifically when starting a RUN activity (though any activity with assisted GPS would be the same), I often get the error that the Blaze cannot find the mobile. I restart my phone, and the Blaze, and it will connect. I can then start my run.

The main problem is that often (maybe 50% of the times I try) the bluetooth will crap out during the run, and I see a mobile with a red line through it at the top of the screen. This is really, really annoying, as I find that when I am done, the run stopped tracking at this point, so the data is all screwed up. Really destroying the usage of this device as a run tracker. 

The issue seems to only be with my Blaze, as Bluetooth is otherwise working perfectly. The phone pairs with my headphones when I am running without any issues, 100% reliable. I realise the Blaze isnt using classic bluetooth, and is instead using a low power bluetooth connection, and it seems to be this that is problematic on my Nexus 5x, and seemingly plenty of other Androids?

I have tried turning off WiFi, on the off chance that other radio interference is causing this. THe phone is on a strap on my arm, so plenty close to the watch, so its not a range issue. Its like the phone is just dropping the connection at times, but it never recovers. Once I see this icon on the screen saying connection is lost, it will not come back.

Is this a known issue? 

Is there any good advise?

I am contemplating running the Fitbit app during the run, and preventing the phone closing it, or going to sleep, in the hope this may persist the connection, but it is poor that I should have to find such workarounds

[mvan231]

Best of luck. It has solved my problem that's for sure.

[MikeMakeSuffer]

It seems to have worked thanks mate, will let you know how the following weeks go.

[mvan231]

Glad to hear it! It seems it was some issue with Bluetooth loosing
connection due to the water in our bodies that we are made of blocking the
signal. And for some reason once the connection drops it takes a long time
to reestablish. Not sure why exactly. But in any case, happy it helped and
happy running.
Cheers

[MikeMakeSuffer]

It has happened twice again during this week both on the same arm, any other tips? 

[mvan231]

That's pretty odd. Have you tried with wifi off?

I was told by support to reset my settings too

[Deano108]

I have a Moto G Play android phone.

I walk and run every day.

Usually whilst walking, I lose connection between my phone and blaze several times, normally it re-establishes the connection quite quickly.

Unfortunately, lately whilst running the connection is lost and remains lost, leaving me with inaccurate data as the GPS info is not present.

I can't seem to resolve this issue?

[Deano108]

I have a Moto G Play android phone.

I walk and run every day.

Usually whilst walking, I lose connection between my phone and blaze several times, normally it re-establishes the connection quite quickly.

Unfortunately, lately whilst running the connection is lost and remains lost, leaving me with inaccurate data as the GPS info is not present.

I can't seem to resolve this issue?

[mvan231]

Have you tried the previously mention items?

I found wearing Fitbit Blaze and phone on same arm helped my issues.

[astachowiak]

It looks like there are many problems with fitibit trackers not only blaze. The same apparently happens for charge 2. It looks like the connection between the phone and the watch is the problem and the watches are not able to continue tracking. Sometimes I get an activity on watch but GPS data stops in the middle. Sometimes the whole activity is stopped in the middle and I watch behaves as if it wasn't tracking anything at all. It's really unreliable. And there is no support.

[mvan231]

I had the same issues previously and it no doubt is not specific to the
blaze. It seems to be an issue (for me at least) with the bluetooth
connection having to go through my body and that is causing a blockage in
the connection (especially while running due to one arm extended out from
the body frontwards and the other backwards).

For me, the fix was to wear the fitbit tracker and my phone on the same arm.

[Ericgnome]

Hi, I had similar problems with Android Sony M8 and Blaze.

I have found that if I go to the Bluetooth settings, location menu, then click the "scanning" word in top right hand corner (I did not realise this was even a menu until I touched it!) then deselect Bluetooth scanning; then the blaze continues connected throughout my walks/runs.

Only had the Blaze since last week, and only used it a couple of days since trying this (and having tried a lot of the other things posted in this discussion) so fingers crossed.

Hope this is helpful. 

[marks1014]

Soooo frustrated!! 

I've had the Blaze since 6/16 and I use/pair it with Galaxy S6. Have had random connections dropped during the time I've had the Blaze. 

But, recently, since the firmware was "updated", every single run is way off with distances, crazy maps are being drawn up to show my runs in the app, losing connection almost exactly after 1 minute of activity. Every. Single. Time. 

I've tried everything being suggested in these forums. Nothing works. I'm officially now in the market for a new fitness watch, and unfortunately, Fitbit, you've lost a customer. What a piece of donkey excrement this has turned out to be! 

[mvan231]

This is a known issue by Fitbit and they are working on a fix. Until then,
they recommended for tracking using the app track feature. Super annoying
but it’s all we have to do at this point.

[marks1014]

I guess I'm not exactly sure what the app track feature is? I thought that's what I was trying to do? Log my runs while the fitbit app tracks distance, data and maps it out? 

[mvan231]

You’re right... sort of. But the app has a tracking feature to not use the
blaze for saving the GPS data of the run. Instead, it saves everything to
the phone. If you go into the exercise area or activity area of the app.
You’ll see a stopwatch button in the top right. That’s where you want to go

[marks1014]

Awesome! Thank you for your guidance 


Sent from my Verizon, Samsung Galaxy smartphone