02-22-2016 09:42 - edited 02-22-2016 10:26
02-22-2016 09:42 - edited 02-22-2016 10:26
Hey all!
I've been seeing a ton of great conversation about Connected GPS- the technology that will allow you to see your maps, as well as pace/distance using your phone's GPS. Ahead of launch of the device, I'd like to provide a bit more information about Connected GPS in comparison to our built-in GPS technology (found in Surge) or our existing GPS functionality in relation to other devices! The following is an in-depth look at Connected GPS, and and opening of the floor for questions! Are you ready? Let's do it!
Connected GPS is a new part of the Fitbit ecosystem! Using Connected GPS, Blaze connects with your phone's native GPS capabilities to plot routes and activity stats screen as the pace and duration.
The necessary components for initiating a Connected GPS exercise are:
To initiate a Connected GPS exercise, open the appropriate exercise (exercises that offer GPS connectivity on the Blaze will have a gear icon on the tile). Once you select the exercise type, you'll see that your Blaze will begin to look for your phone's GPS services. Once the device establishes a connection, you'll be notified that you're ready to go. You can always bypass the connection if you'd like, much like on Surge.
GPS is built-in on the Fitbit Surge, meaning that you could initiate a GPS activity without your phone in proximity. The MobileRun process works a bit differently; you'll have to open the Fitbit app and select Track Exercise > Stopwatch Icon > Start.
Phone Not Found: Users may see the following error state if their tracker is unable to connect to their phone. If this happens, please ensure the following: phone is within range, your app is open, phone is charged up, Bluetooth enabled and bonded, and Internet connection is present.
Check Fitbit App: If you come across this error, there may be a bit of action required. Please ensure that your app is open, you are logged into your account, and that location services are enabled.
Location services are required for Connected GPS to function properly. Please ensure that location services are enables, and set to "Always" if applicable.
Permissions are requested upon setup of the tracker. Users who intend to use the Connected GPS feature should accept the permission requests. If you switch phones during the life of your Blaze, you'll be prompted to run through all of these permission requests again before being able to successfully use Connected GPS.
08-01-2016 08:21
08-01-2016 08:21
My GPS problems occur when in heavily exposed areas, walking by the three line(sometomes), and on heavily clouded days.
My recently replaced phone seems to be not as accurate as the previous, but it is this way also in MMF, google, and waze.
08-01-2016 12:59
08-01-2016 12:59
@Danianya81 @HollyF @OleMarius
Check this post and other topics. This is an on going problem that fitbit seems to be unable or unwilling to fix. Pretty disappointing.
https://community.fitbit.com/t5/Blaze/Miles-are-off-with-blaze/m-p/1436070#M22240
08-01-2016 18:30
08-01-2016 18:30
08-05-2016 10:57 - edited 08-05-2016 10:59
08-05-2016 10:57 - edited 08-05-2016 10:59
Since the Blaze is useless with pair GPS on the mather of distance i was thinking of doing a test this time. I compared the actuel GPS distance data from google map log and took my previus runs and made an average stride lenght to see if the distance would give me more acurate lenght.
As seen on the photo under i undid the automatic stride lengt option.
I then had a run as seen under. But tho, still same problem. it has 5,95 km over the actuel lenght.
WTF fitbit do suck.
08-06-2016 15:16
08-06-2016 15:16
08-06-2016 15:23
08-06-2016 15:23
08-06-2016 21:51
08-06-2016 21:51
If i take the same walk with MMR, Fitbit, Surge, Blaze with connected GPS, and Charity Miles.. How come i get 5 different distances reported?
08-06-2016 22:53
08-06-2016 22:53
Sense, Charge 5, Inspire 2; iOS and Android
08-06-2016 23:02
08-06-2016 23:02
Exactly @Julia_G, there are other factors also involved, since i can take the same walk 3 days a row and MMR will give 3 different numbers..
Just pointing out that without milatary grade equipment the measurements won't be spot on everytime.
08-06-2016 23:21
08-06-2016 23:21
08-06-2016 23:32
08-06-2016 23:32
I'm not sure at what point a fix is at, but it is not just a simple fix..
First the problem has to be identified, this so of be easy if it affected everyone, it doesnt.
The affected hardware needs to be udentified, is it the Blaze or the phone.
A fix has to be found and tested.
Unaffected units must also be tested, it might fix affected units and mess up unaffected units.
This is only what i can ascertain without knowing Fitbit's protocol.
08-06-2016 23:47
08-06-2016 23:47
08-07-2016
04:56
- last edited on
08-27-2024
12:38
by
MarreFitbit
08-07-2016
04:56
- last edited on
08-27-2024
12:38
by
MarreFitbit
Hello all, I hope you are doing fine! Thanks for the screenshots and all the information provided. If you are having problems with your map information. I recommend checking if your Fitbit apps are updated by following @MarreFitbit's instructions (iOS) and my steps (Android).
Also, our connected GPS feature works with your phone to deliver real-time activity stats like distance and pace during outdoor workouts. After a workout, you can see the details in your exercise history on your dashboard. Connected GPS requires a GPS-enabled mobile device. For instructions on how to track an exercise with connected GPS, see http://fitbit.link/1Pjdqk0.
Note that connected GPS is only available with compatible iOS and Android devices. Windows mobile devices are not supported.
See you around!
08-10-2016 00:42
08-10-2016 00:42
Why aren't Windows devices supported? There are 3 major phone OS', of which one is Windows. Imagine how many more users you could have if you didn't neglect a major OS.
08-10-2016 00:50
08-11-2016 10:00
08-11-2016 10:00
Did a new run with the automatic gps stride option.
THis time the blaze with my phones gps show an error of 7,39 km off. 7390m!
08-13-2016 19:36
08-13-2016 19:36
08-13-2016 20:23
08-13-2016 20:23
@docwatkins what error message are you receiving?
08-13-2016 23:19
08-13-2016 23:19
08-14-2016 04:04
08-14-2016 04:04