Issues with GPS Accuracy on Blaze

[loungesong]

I thought I would throw one more Hail Mary before throwing out FitBit like my wife did years ago...

I use my Blaze with a Samsung S8+.  Before I go for a run I reset my phone and the Blaze like a good boy.

Then I turn off Wifi.

Then I start my Exercise, Run and hit the "Play" button.

Then I turn on my Plantronics bluetooth headphones and start a spotify playlist (which has previously been downloaded).  Then I start running!  I keep the phone in a waist strap

About 50% of the time at some point I get the dreaded phone with a slash through it and lose connection.  Sometimes I have to start the entire process over, other times it starts working by itself.  This was enough to make my wife switch to an Apple Watch...but I don't have an iPhone.  Plus I dragged at least 8 other people into the FitBit world...and want to continue competing against them.

The latest problem I've been having for the past week is completely inaccurate distances recorded.  I've been noticing my pace is way too slow.  I usually run a 9:30 pace but even downhill it's showing me a 13:00.  Sure enough I went for a run I know is 8 miles this morning but the FitBit showed 5.5 miles.  The map also represented this in the app.

I was able to exactly map one of the miles from the app on google maps...sure enough the app shows it as 1 mile, but in reality it's 1.22 miles. What gives?  This has been going on for a while now. (2 weeks at least).

I went on the chat and this is what the rep told me (important parts only):

"Me:could i have a problem with the stride length? I thougt it was using the GPS?
lpala:I am actually confirming that this is a general issue and that I will make sure is on our engineers hands.
lpala:We are aware of the problem and are working to resolve it as quickly as possible.
Me:really?
Me:is it a firmware issue?
lpala:According to my system, the firmware for your Blaze is updated already.
Me:can i downgrade?
Me:to one that works? i didn't really have this problem before
lpala:This issue just happened, it is not your tracker or phone, is something else, but as I said, I will report it to our system technicians.
Me:do they have an ETA for the fix?
lpala:Not that I have ans ETA. I will suggest you check back with us in the next 24 hours.
Me:is there somewhere i can check online for an update?
lpala:Your case will be handled internally with the technicians".

Am I crazy?  The response is so weird that I believe it, but with no more details...

I don't know why this is my 4th fitbit.  This stuff was normal when I was an early adopter but my $400 Garmin Forerunner from 13 years ago was always accurate and worked great...just not "social".

Am I just a glutton for punnishment or is this not a legit training watch?

Moderator edit: Clarified subject

[MarkMM]

---

@davibes wrote:

Doh! Smart watches, dumb buyers? I have 35 days to return mine. Think I should?

---

I can't really advise on that. Mine is still working good enough, so IDK what I'd do if it broke soon. With all the Versa complaints, I'd be tempted to try another Blaze. Maybe even a charge 2. I don't need the music option. If they allowed 2 Blazes on your account, I probably would have bought a backup by now. Seems like complaints have gotten way worse in the last year or so. Makes me wonder if they recycle returns deemed no problem found, and you're not actually getting a new one anymore? 

[davibes]

Well thanks. At 76 I'm a low level user j(40 miles walking per week) just IT smart enough to make use of a reliable timekeeper with added extras. I'll keep my fingers crossed. But you're right. They could do better. 

[MarkMM]

---

@davibes wrote:

Well thanks. At 76 I'm a low level user j(40 miles walking per week) just IT smart enough to make use of a reliable timekeeper with added extras. I'll keep my fingers crossed. But you're right. They could do better. 

---

Maybe you should look around more. Make your own thread seeking opinions. You have 35 days. I would think with steps being your main interest, you could probably find something newer AND cheaper to suit your needs. The Blaze isn't perfect even for steps. It's arm motion based. You can get steps just moving your arm while sitting. You could also be walking and not get steps if you're arm is not moving. 

[davibes]

Thanks. Sound advice. I shall follow it. Disappointing though. Prima facie it is an excellent product. 

[MarkMM]

---

@davibes wrote:

Thanks. Sound advice. I shall follow it. Disappointing though. Prima facie it is an excellent product. 

---

It's not that bad, just now over 2 years old, discontinued, and seemingly more than you need. You could very well be happy with it. Wouldn't hurt to get opinions while you have time to return it is all. 

[Rach1802]

Well I finally got an 'answer' to this ongoing problem after having my Blaze replaced and experienceing the same thing and a new problems of no syncing with the app - apparently my phone, the Samsun Galaxy A5 2017, isn't compatible! 

In all the issues I had with my Charge 2, the many times I contacted support for that and for the problems with my Blaze and no-one thought to tell me this?! It also never mentions on the website when you purchase that you need a specific phone, just that you need a recent version of Android, which I've always had. 

I'm trying to get my money back because there's no sign of them adding the A5 to the compatibile device list - it's bee out since 2014 - and my Blaze is basically useless now if it can't track runs or, as a result, my fitness level.

[SunsetRunner]

Same issue with the Fitbit blaze GPS data accurate but data in the app not. Done parkrun 3 times never has it matched the 5km on the Fitbit app. 

[SunsetRunner]

Having tracked a run using map my run which uses the same GPS data from my phone the fit bit app tracked at 6.24km and map my run using same data 6.43km so some 200m out. I also tracked in Strava which matches map my run which again used same GPS data. This is obviously an error in how Fitbit is interpreting the GPS data as the above person posted so not just the ionic but also blaze and likely all Fitbits. This needs fixing if Fitbit want to be considered a more serious fitness tool otherwise I will be switching to a more reliable tracker.

[SunsetRunner]

Ive been having the same issue. It either maps completely wrong, all over the place, or the milage is completely messed up. It says i only did 1.66 miles when i know it was 3. As u, i mapped it out. What is up with that? I also have the S8. My son switched to apple, and hasnt had any issues at all. About rdy to switch