Tracker is not connecting with phone

[batporio]

Hi, I have a Blaze and a Google Pixel (android) phone. Before the recent update I would have no problem tracking bike exercise every day. Now when I start the exercise on the Blaze it can not connect to the phone. I have them side by side, Fitbit app open on the phone and connected to the Blaze but it just wont find it on the Blaze. Sometimes it would connect and I can start the exercise but very soon it will lose connection and when I stop and check it has tracked just a few minutes max. So far I have tried:

• Unpair - pair
• Clear app cache
• Turn classic Bluetooth on and off
• Restart Blaze phone etc., multiple times

Nothing has worked in terms of getting a stable connection for an exercise tracking between the phone and the Blaze. It all started after the update so I am pretty sure it has something to do with it. If anyone has had a similar issue and found a permanent fix please share. My hope is Fitbit are aware and will release new update to fix this as now this watch is completely useless for my needs.

Thanks!

Moderator edit: Subject for clarity

[PunzunLtd]

I'm having a similar problem with an LG G6 from T-Mobile.

Blaze firmware 17.8.401.3

Android OS v7.0, security patch level 2017-10-01, kernel 3.18.31

Since Friday, my Blaze/app interaction has had the following symptoms:

• Multiple yanks on the app to get it to start syncing
• App starts syncing then stops within 2-3 seconds
• On Walk exercise when GPS is fine on phone and Fitbit app is open, Blaze cycles between "Let's go!" and "Phone not found" repeatedly
• On starting to walk, Blaze reports disconnection from phone almost immediately
• GPS track shows just the starting point
• When Blaze does stay connected to phone during a Walk, it loses 10-15% of distance (i.e., walking a known distance of 200m shows 150-160m on tracker)
• Syncs, when they do start, sometimes take several minutes or time out entirely

All of these symptoms started on Friday. I don't know whether it was the latest Android update or Fitbit App update that caused them.

Remediation:

• Restarted phone
• Restarted tracker
• Uninstalled and re-installed app on phone
• Recycled Bluetooth on phone
• Confirmed Bluetooth is working fine on phone with another device
• Tried all 4 combinations of All-Day Tracking and Stay Connected

Note that the tracker works fine on its own, and when not connected to the App records correct distances (I assume because it knows my stride and isn't relying on spotty GPS data).

It seems that I can get about 12-15 months out of a Fitbit device before something breaks. Any chance this can get fixed or that the cycle of software problems can end?

[PunzunLtd]

I'm happy to report that Blaze update 17.8.402.1 seems to have fixed this issue for me.

That said, there's still an odd symptom. The Blaze seems to measure distance inconsistently. I took a walk this morning that my Blaze reported as 4.88 km but Google Maps (and prior experience) reports as 5.3 km. I live in Chicago, where streets are known distances apart. Major streets are consistently 800 meters apart in some places, so when I walk 800 meters and my blaze reports 740, I know there's a problem.

[AlejandraFitbit]

A warm welcome to the Community @batporio and @PunzunLtd it's great to see you around and to hear that the firmware update worked for you.

Thanks for troubleshooting this issue by yourselves. Keep in mind that in order to successfully connect your phone with your tracker, it needs to be compatible. Please check our list of compatible mobile devices to confirm that your phones are there.

If they are, I recommend checking that your trackers are updated, take a look at the My Blaze GPS is not working post and follow the instructions provided there, also verify that your stride length information is updated.

I hope this helps, let me know the outcome.