07-01-2017 06:22
07-01-2017 06:22
Hi everyone,
I've been using my Blaze for 3 weeks now and have been running with it 4-5 times per week. I always bring my phone with me on my runs and have been using the connected GPS through the Fitbit app to track them as well as my Nike NRC app that I have been using for years. I've noticed inaccuracies in the measurement of pace and distance when comparing these 2 apps. NRC will track a pace of 6'48'' (mins/km) and Fitbit measure 6'15".
It doesn't appear to measure distance accurately either because I start both apps at the same times and the Fitbit app advises me of finishing each KM faster than NRC. I can tell you right away that the NRC is not perfect but I've measured it out in the past to be fairly accurate, which means the Fitbit app is WAY off. I have the most up to date app and firmware so this is not the problem. If that be the case, then what is going on? Cause I'm starting to second guess whether I made the right purchase or not, as tracking my runs was my primary purchase for wanting this device.
Sincerely frustrated,
Sabrina
07-02-2017 12:00
07-02-2017 12:00
My fit bit doesn't record accurate distance either.I have a garmin so know most of the mileage for the routes i take.Ive tried automatically setting the distance and manually putting in stride length both are totally wrong.Garmin will record 4 miles fitbit 1.5 miles any suggestions.
07-02-2017 14:20
07-02-2017 14:20
@Rayvicjord67 what mode are you using with the Blaze? Unlesz you are using the GPS your tracker can not measure distance. This is the same with thw Garmon.
07-04-2017 06:03
07-04-2017 06:03
07-04-2017 07:20
07-04-2017 07:20
If you are not using connected GPS, it could be that your stride length needs to be set up within the app
07-09-2017 05:10
07-09-2017 05:10
Welcome to the Community @SabrinaSettimia and @Rayvicjord67. @Rich_Laue and @RonWH thanks for stopping by.
If you are having inconveniences with your GPS and the information recorded by it, I recommend following the instructions provided in the My Blaze GPS is not working. Also, if you are going for a run and want a map you can use this feature but keep in mind that you can also use SmartTrack to register your exercises.
Catch you later.
07-09-2017 07:58
07-09-2017 07:58
Hi @AlejandraFitbit,
Thanks for taking the time to reply. The only problem is your suggested solution not only doesn't solve my problem, it has nothing to do with it. I have a iPhone 7 Plus, which is a fitbit compatible device, and it connects to the phone just fine. The problem is that the GPS is not accurate, not that it won't connect. There was another fitbit representative that had responded to someone else, with a charge 2, acknowledging that it was a legitimate problem and telling the charge 2 owner to update their firmware. My firmware is up-to-date and I still have inaccurate GPS tracking.
I'm sorry if I misunderstand, but is fitbit now under the impression that this is not a legitimate issue anymore?
Additionally, the "SmartTrack" does not work with my runs,which from what I have read is a known issue.
I hope this information is enough additional information to get your help.
Thank you,
Sabrina
07-19-2017 06:20
07-19-2017 06:20
I would love to know the solution to this problem as well. My Surge was far more accurate than the Blaze. I have been doing the same route for years, so I know the distance. I have connected my fitbit blaze gps with my phone and started my mapmyrun app at the same time this morning, the course shows up on the fitbit app and mapmyrun and it is the same, fitbit says I did 2.67 miles and the actual and mapmyrun says 3.05. That is a huge difference.
Sincerely frustrated too,
Hope
07-19-2017 11:20
07-19-2017 11:20
In order to use the GPS tracking you have to have your phone, is that correct? I had a garmin and am now using the blaze and I attempted my first run a couple weeks ago with the GPS setting to 'On' and it said something like my phone was too far away. I never had to carry my phone with my garmin. I've been using it in the off position but the distance and my pace are off. I run the same 3 mile route and yesterday it told me I was at 2.7 miles and that my average pace was 11:44. The ladies I run with all have garmins so we all were very close in distance/pace prior and theirs read 3 miles and a 10:18 pace. Huge difference.
07-23-2017 06:54
07-23-2017 06:54
For most accurate measurements your supposed to have your phone with you and track your run through your app. The garmin has it's own built-in gps but the blaze functions off of connected gps through your phone.
I've been running tracking on both the blaze and the fitbit app, not matter what I use it's inaccurate. On top of that it looks like @Fitbit doesnMt seem to want to acctually address this issue. I'm slowly starting to really regret buying this item and wishin I just bought the garmin vivoactive HR. I don't see the point of spendingover $200 for something because it hass the added gps function only fornit not to work.
I'm still holding out hope however because I really like the blaze and I want to badly not to be disappointed in this product.
05-04-2018 08:58
05-04-2018 08:58
05-04-2018 10:07
05-04-2018 10:07
What Fitbit does tell us that when running and using the GPS the users strife will be automatically calculated. Fitbit advises to use the gps mode for several runs so that the auto stride detection will be accurate.
I have not found any place .or have had it confirmed/denied that GPS is used for distance in walk or hike. The mods have all simply not responded to my queries.
As for the Blaze and run with GPS Fitbit says the distance comes from GPS.
Now I just need to find the posts
05-04-2018 11:57
05-04-2018 11:57