Connected GPS not working on my Blaze

[dopplergaydar]

For the past few weeks my connected GPS has been getting worse and worse.  Finally, as of last week it seems to have bit the dust entirely.  It'll connect initially, but the GPS signal is weak.  It'll drop after a few seconds and will never come back up so I won't get accurate mileage or a map of my route.  For example yesterday I went on a bike ride and it didn't record my route or pace, just the duration and my heart rate.  I've spoken to Fitbit support and since my Blaze is JUST out of warranty (bought it on launch day) there's nothing they can do but offer me 25% off a new Fitbit, but I don't want a new Fitbit!  I just want mine to work.  I know tracking a workout on my phone will work and I'm guessing I'll just have to do this as a last resort, but I'd really prefer not to as I like having my phone secure in my pocket or my bike bag while I work out.

Any advice?

[mvan231]

What type of phone do you have?

I have had some similar issues but mine shows a good signal when I start my run but it loses the signal shortly after and it causes a bit of a headache because the map is all screwed up at the end. I actually have been tracking this many different ways and we have some other posters in a different thread.

https://community.fitbit.com/t5/Blaze/Connected-GPS-failure/m-p/1851605#M48732

I am still hoping that fitbit finds a way to resolve this even if the downside is higher battery usage of the device. It is totally ridiculous to have to use a separate app to track the workout or to have to unlock the phone to track it via GPS just because the watch / app can't work properly

[dopplergaydar]

Thanks for pointing me to that thread.  How frustrating!!  I have an iPhone 7+.  Looks like I'm not alone in my GPS woes :(.

[mvan231]

yeah it is a huge pain. Sounds like fitbit might be replacing my blaze but
it doesn't solve the issue from what I have read

[mvan231]

Thy are sending me a replacement I hope it fixes something with this. 

I ran ran today and had issues yet again despite opening the run activity on my blaze for around 5-10 minutes before I started running. 

[mzup87]

Yes I'm finding the same issues here too. I have a Samsung Galaxy S6 and I just started paying attention to my routes I've been running and one is just a straight line down the end of our driveway and it says "2.9 miles". While, yes I did go on a 2.9 mile run, it is not 2.9 miles to the end of our driveway lol. Another run tracked me mostly on a route that I run (it's usually a giant loop through several neighborhoods), but on the way back it must have lost the signal as it's just a straight line back to our house and not following the streets I actually took. This makes me feel like there's no way it's accurately telling me my pace or distance. I have a Surge as well and I've never had problems with the GPS tracking on that tracker. Honestly, if you care about GPS tracking being accurate, and you want longer battery life and a tracker that has a screen that's always on and is easily view-able in direct sunlight, I'd go with the Surge. It's a bit bulkier but in my opinion much more reliable. I'm pretty disappointed in the inaccuracy/connection issues (mine also has notification issues sometimes) the Blaze has. I have not yet contacted Fitbit support, and from what I've learned here, I'm not going to want them to just send me a new tracker... I don't think that's a good resolution to a problem that is clearly related to software. 

[mvan231]

I agree this is a software issue and not fixed by replacement hardware.
It's irritating to me that they won't just work out a software fix for
this. I wouldn't even care if it killed my blaze or my phone faster. There
is no point in using GPS if signal is always getting lost. Almost better
off not even using the GPS and just relying on steps * stride length at
that point.

Best of luck to you and hoping to have more info when I get my new tracker
or when Fitbit issues an update.

EDIT:

i found a fix for me! Wearing blaze and phone on same arm fixed my lost connection issues.  Give it a try

[Dj_rastakowski]

I went through 3 Surges.  GPS was great.  The bands are not replaceable and they basically fall apart and look like trash if you are an active person... Hmm.... 

I got a BLAZE a month ago, I have a Pixel, the GPS connection has never worked. I reaiet ro also using Strava, kind of defeats the purpose, and now have a pretty step counter called Blaze.  At least it keeps track of my sleep and steps.

The new Ionic may be better.  But it's 300 bucks, I just got the blaze with the discount from Fitbit based upon my continued deteriorating Surge.

I am frustrated, and not seeing light at the end of this tunnel yet even after trying just about everything.  I will continue to try, but not feeling great about things right now. 

Best of luck to you, and if any Pixel users have figured out how to have a reliable connection that does not require 30 minutes of button pushing every time you get on your bike, I am interested in hearing from you.

[nitro_39]

Unfortunately if you downloaded the newest ios app 11.0.2 or 3, it has caused issues with Fitbit.  Here is a fix.

Step 1: In Fitbit App > Account > Blaze > Close App

Step 2: Delete your Fitbit App

Step 3: On your I-Phone go to Settings > Bluetooth> Blaze > Forget this Device

Step 4: Reinstall the Fitbit App and follow Setup

Step 5: On Phone Check Settings > Privacy > Location Services > Fitbit > set to Always

You might want to save these instructions for future IOS updates....

Good luck

[mvan231]

does this truly fix the issue?

[nitro_39]

It fixed mine, hopefully you will have same result.

Sent from my iPhone

[Dj_rastakowski]

I am using pixel. Synching is not reliable at all.

[JasonAnder]

Starting this week, I've also had problems with my Blaze getting disconnected during connected GPS, crashing/rebooting while trying to launch connected GPS, and not syncing automatically, on my Pixel.  I called Fitbit support today and they said they are aware of an issue with the Android app and are working on it.  I've already tried uninstalling/reinstalling the Fitbit app and deleting the Blaze (classic) from the Bluetooth menu, but that hasn't helped solve the problem.

[AlejandraFitbit]

Hello all, I hope you are doing fine!

First of all, thanks for troubleshooting this issue by yourselves. If you are having problems with the connected GPS feature, I recommend taking a look at the My Blaze GPS is not working post and follow the instructions provided there.

I hope this helps, let me know the outcome. 

[JasonAnder]

AlejandraFitbit - Been there, done that - none of those tips helped.  Of course I already saw those tips before posting here and when contacting support and they acknowledged that there is a known problem with connected GPS and Android 8.0 Oreo.  I hope a fix is coming soon from Fitbit!

[mvan231]

Have you tried to wear phone and blaze on same arm?

[jenirving]

Hi, Has anyone had any luck when speaking to Fitbit. I’ve search the internet for weeks to find a solution but everyone seems to have the same issue - GPS. I wish I never bought the **ahem** thing

running it with an iPhone 6s

[mvan231]

you're having issues with connected GPS still? There was an update that
came out today for firmware of devices. Besides that, I had issues before
too when I was wearing fitbit on one arm and my phone (in an armband) on
the other. Are you in a similar setup?

[jenirving]

Yeah, I’ve tried everything factory re-set, disconnecting & re-connecting via blue tooth. I use it with my phone in a belt around my waist. Was working fine till I got latest OS. Haven’t had a firmware update today but did have 1 a few days ago 

[mvan231]

That is really odd... I haven't had any issues lately with mine. Only when
Blaze battery is low and it doesn't hold a strong connection. Other than
that, same arm for blaze and phone keeps the connection strong. Also,
turning wifi off has helped me in the past as well since the bluetooth and
wifi share the same antenna source (apparently).