Blaze phone not found for exercise

[AlacrityF174]

I have my phone in an arm band no more than 10" away from the Blaze on my wrist and the message I get is "phone not found".

All other apps are turned off and even wifi is turned off and still the watch will not connect to my phone. I have rebooted the phone and it then finds the phone only to lose connection again after a few minutes which messes up distance and mile splits which is very frustrating as I cannot use this data for any meaningful purpose.

I have tried using the standard bluetooth connection and the classic connection it makes no difference which or both connections are active.

Please help

[Rich_Laue]

Classic is only used for music control on non iOS devices. 

Do you have Fitbit notifications enabled or the Fitbit app loaded on memory, it does not need to be active. 

Also what type of phone are you inquiring help for? 

[AlacrityF174]

Duplicate post, deleted

[AlacrityF174]

Android S6, yes to notifications and App loaded. 

[AlacrityF174]

Still no change, runs are inaccurate and the tracker loses connectivity with phone multiple times during run. I can drive to Florida from Georgia using bluetooth all the way for music and maps and car never loses connection to phone, I use Bluetooth on motorbike helmet and can make calls and listen to music with no problems but my blaze can't stay connected to my phone for more than 5 minutes.

[AlacrityF174]

Any chance of an answer on this one? 

[h4A3DgM8B5sB]

I am in the same boat. I've tried everything including a NEW phone. My fitbit, if it connects at all, shows a low signal, then disconnects. This is with the fitbit just inches away from my phone. I give up.

[AlacrityF174]

Check out the Garmin VivoActive 3, had mine a month now and loving it, so much better than the Blaze, built in GPS looks better, more screen face options and the quality of information you get from Garmin far exceeds what Fitbit offers

[AuntBB]

I cannot believe FitBit support has not even commented on this issue you've posted. Ridiculous! This month, 9/2018, my Blaze started behaving like this. The Blaze initially connects to my s7 edge with a great signal veggie a run, walk or hike. Within seconds that drops to weak and then it disconnects starting "phone not found" as soon as I begin the workout. I've reset watch countless times, restarted my phone, checked all app settings. Nothing helps. I thought my Bluetooth headphones were interfering with the accuracy of the mileage recorded, but NEVER the GPS mapped route, or the connection to my phone. I'm rethinking all that....

I'm experiencing all these malfunctions now regardless of the BT or wired headphones I'm using. Seems everything has gone downhill even further since the last update to the phone app. Smh. No accurate millage, maps or data period!

[AuntBB]

Just wanted to note that my fitbit app is always open and I always sync immediately before a workout.

[Rich_Laue]

Considering that this conversation is where Fitbit users help each other out, and not where Fitbit employees necessarily hang out to offer assistance. Yes the moderators do help out, but they are not with the technical department, and will normally only be able to offer general help.

They do sometimes open a troubleshoiting  case for a user. However buy going to the support page a user who wants a response from Fitbit may open their own case by going to the Fitbit support page. Link is also found in the top right menu and under help on the web and Fitbit apps.

If your looking for a resoores from Fitbit, I suggest reaching out to them and opening a support ticket. 

[AlacrityF174]

My Fitbit died shortly after this,  could never get a straight answer out of them.  Decided to get a Garmin and couldn't be happier 

[AuntBB]

Thank you for the response, Rich. You're everywhere in these forms. That's great!  I spent hours, was extremely thorough and exhausted every troubleshooting approach I could. It seems something has changed, since the update to Android Oreo, Samsung's last Galaxy s7 edge software update and recent Fitbit App updates, that now requires me to have notifications set to "On" before I start a run or walk. I never use my Blaze watch to receive phone call, txt, or app notifications. Until now, I've never needed Blaze watch notifications turned "On" in order to connect to my galaxy S7 edge. Yes notifications enabled within the Fitbit App, but never necessary on Blaze. In fact, I've never used my watch for notifications. That seems to have changed and is now required for connected GPS function.

It worked today when I turned this "On".

It may have been a fluke, so I'll report tomorrow if torrential rain isn't falling all day. Today I noticed a crack around the small clear square in the middle of the HR sensor....This is just terrific. Disappointing! It's on it's lat leg I'm afraid. Ionic and versa reviews are disheartening. Ok losing faith in fitbit and if been loyal. Newest devices are making it hard to continue.