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.
09-09-2016 10:15
09-09-2016 10:15
@andruboine i can't speak for spotify, but the app that's playing the music should have no bearing on the question.
With 2 Bluetooth speakers, 2 bluetooth headphones, and a homemade Bluetooth adaptor for the car, ive never had a problem with volume or music control from the Blaze or Surge.
09-13-2016 06:22 - edited 09-13-2016 06:27
09-13-2016 06:22 - edited 09-13-2016 06:27
This explains why Fitbit devices aren't supported by me. I use the scale only because we have had it for a while and it is linked to myfitnesspal, which, by the way also will no longer be suppored. I am sure there are "good" technical reasons why Windows Phone and Fitbit are incomplete in the compatiblity arena but it is sad that this has remained an issue. But, nevertheless, I will be supporting Garmin from here on out. Fitbit was how I got into fitness tracking. I have given them a fair opportunity and even wanted the Blaze to be a worthy option. It has fallen behind others by a long shot.
09-13-2016 07:04
09-13-2016 07:04
09-13-2016 07:25
09-13-2016 07:25
My Blaze is abandoned... I'm using MS Band, which has GPS and talks with every phone and every OS...
09-13-2016 15:33
09-13-2016 15:33
The latest patch has broken the GPS connection with the phone. All worked fine until I updated the device yesterday. Restarting the device and the app does not fix the problem. The device is syncing with the phone but refuses to accept the GPS connection. Extremly annoying.
09-14-2016 05:50
09-14-2016 05:50
My Fitbit Blaze always seems to show 1bar on the watch and after the run the accuracy on the map is really wrong. Looks like this maybe an issue with some Android phones (I have marshmallow on Samsung s6) and people are having more success with apple. Surly this is just a bug that FitBit could fix in an update but the reply’s I seem to get are the usual. Think I will wait until the Sep update maybe randomly it will work after. If not I think I will have to purchase a cheap Garmin forerunner as my brothers one works perfectly.
09-15-2016 16:45
09-15-2016 16:45
New Blaze and new to Fitbit, had to return my beloved Basis Peak because of safety recall.
I like the phone quite a bit so far, but having issues with connected GPS accuracy. May be linked to some Android/Google app issue depending upon how Blaze is accessing GPS. I have a Nexus 5x running Android 7/Nougat. When I track distance using Google Fit app on that phone it is reliably and predictably wrong. It always under measures/reports distance. I walk 2 miles it says I walked 1.6/7. I use Endomondo on that same phone and it accurately reports distance.
My Blaze is closer to the Google Fit distances then the Endomondo. This distance inaccuracy of course leads to inacccuracies when reporting pace.
I think it might have to do with the agressive "Sleep/snooze" work Google has been doing in Android to extend battery life. Fitbit needs to make sure it is accessing the GPS hardware the same way that Endomondo does.
Is this something that Fitbit is aware of and working on? Is there any extra info I can supply to help with troubleshooting?
Thanks
09-15-2016 23:35
09-15-2016 23:35
09-20-2016 06:32
09-20-2016 06:32
I guessing this has been asked before but for the connected GPS function on Blaze. Can you try something like what Addias Micoach does, you can track your gps location with out any internet connection.
Then when you next sync with internet connection update the tracked information with the GPS information.
09-20-2016 06:48
09-20-2016 06:48
@anoyce wrote:
Yes I agree dies seem like the android os is trying to save energy and at the same time loosing gps accuracy. Can't belive that fitbit has not realised this and made a fix for this September update.. I have ended up getting a Garmin for running and it's great!
If it is a possible failing in the OS on some devices, I'm not sure what fitbit can do.
Not that anyone cares, but I did a run at weekend (first with the Blaze), partner followed me on her bike. I tracked it with the connected GPS and it gave exactly the same (correct) reading that my Charge HR used to give. It was also pretty much identical on my partners charge HR too.
My phone is a Sony Z5C, hers is a Vodafone Smart Ultra 6. Both work perfectly.
09-20-2016 09:58
09-20-2016 09:58
09-20-2016 19:43
09-20-2016 19:43
09-20-2016 20:44
09-20-2016 20:44
@docwatkins I'm not sure exactly what you mean by "piggyback", the Blaze and Charge 2 do connect to the phones GPS, but the tracker does the actual recording of the path taken.
Why the disclaimer that is 3-4 times longer then then the post. Are we not the intended receiver?
09-20-2016 21:00
09-20-2016 21:00
09-20-2016 21:21 - edited 09-20-2016 21:24
09-20-2016 21:21 - edited 09-20-2016 21:24
Considering that Fitbit says, do not respond through email and blocks my try...
Oh and a disclaimer at the end, that is seen after reading is as useful as putting a movie rating at the end of the movie.
09-21-2016 01:11
09-21-2016 01:11
Of cause, I used my phone GPS, but Blaze didn't count speeds and distance.
09-21-2016 01:46
09-21-2016 01:46
@FlavioCardoso wrote:My Blaze is abandoned... I'm using MS Band, which has GPS and talks with every phone and every OS...
And rarely lasts more than a few months before breaking. Also worth noting that MS have disbanded the band development team.
09-21-2016 03:17
09-21-2016 03:17
09-21-2016 06:35 - edited 09-21-2016 06:38
09-21-2016 06:35 - edited 09-21-2016 06:38
@akaserge your looking at the summary page, tap on one of the maps and you will have 6 pages of run detail to swipe through.
I suggest restarting the phone and blaze since it looks as if the GPS isn't correctly tracking your path.
09-21-2016 06:43
09-21-2016 06:43