Connected GPS vs Mobile Run - Difference?

[IsmeneP]

Folks, I have recently started using mobile run with my FitBit Charge HR.

What exactly is the difference between Mobile Run and Connected GPS?

Is it that with Mobile Run I 'initiate' the exercise mode from the mobile phone, and it tracks the Fitbit device and uses the data from both devices?

While Connected GPS I 'initiate' the exercise from the FitBit Blaze and it tracks the mobile phone and uses the data from both devices?

thank you in advance.

Moderator Edit: Title for Clarity

[ErickFitbit]

@bbarrera@EmersonFitbit@SunsetRunner As a point of clarification, on Android, you won't see any indication that the Fitbit App is using your phone's GPS as @bbarrera's screenshot suggests you will on iPhone. I can only speak to Android at this time. When @EmersonFitbit gets a chance I'm sure he will share what his experience is with iPhone.

[bbarrera]

@ErickFitbit appreciate the comment, still leaves the curious among us wondering if you can confirm that some Fitbit app or process is running in the background on Android? I don't see any advantage or disadvantage to either "yes" or "no" replies -- this detail is off in the weeds and really a don't care from my point of view -- as I stated earlier, if an Apple Watch app needs the companion phone app then iOS magically starts it in the background and I don't know or care about it (and it sounds like Blaze works the same way).

The Blaze has a lot of interesting features on its own -- size vs Surge, looks vs Surge, user interaction, color display, replaceable watchbands, Connected GPS, additional features if upgrading from One/Zip/Flex, etc.

Again, just curious. I don't know a lot about Android however just like iOS the basic approach is for your app to register with the LocationManager, give it a callback, and when new GPS location(s) are available Android/iOS calls your app to do whatever it wants with the new GPS data.

[bjanow]

My GPS is working on android but I'm not seeing any maps after or during my run/bike ride. How do I get to see the maps?

[MikeF]

Sync your Blaze with the app or your computer after the exercise is done and the appropriate exercise record should show up in the app/dashboard with the map attached.

[bjanow]

Thanks, that's what I thought too. It's just not showing up. My Google Maps works, my Strava works but I'm seeing nothing for any map. Distance is fine but something is just not syncing with my GPS I guess.

edit: Under auto-recognize is says, "GPS will not be turned on" How do I enable it then? Under some help screens it says "Use the MobileRun feature in the Fitbit app to track GPS activities with only your mobile phone." I don't have that in the Fitbit app either.

[MikeF]

That's correct, if you're using SmartTrack then it won't even attempt to use your phone GPS. You need to use the Walk or Run exercise shortcuts to get GPS working with the Blaze. I haven't tried it yet, my phone died, but the Blaze looks like it tells you pretty clearly when it's accessing the GPS data.

If you haven't tried that, I guess that's why you're not getting a map. Sorry, I just assumed you'd already got that far.

[Aredhel]

I got my Blaze 2 days ago and connected GPS was an utter fail on 2 short runs over 3.3km each. The fitbit app was running on my mobile, I got a connection to the phone after a couple of tries and started both activities from the Blaze and got 2.66km distance measured for an average speed of 6'19'' instead of the actual 4'30'' (measured in parallel with MS Band 2, best average speed and best split, thanks for nothing fitibit).

If the app runs on the phone, how come that runtastic gets it right and the fitibit app doesn't?

I'm going to test some more but my patience with devices not living up to their expectations has grown short. There's a good chance I'll return this thing.

[MuzDownUnder]

@Aredhel @ErickFitbit I have noticed an error with the Blaze->Fitbit app commuication. I have a Samsung S7 (the same thing happen on the S5) and starting the walk from the Blaze will not automatically activate the GPS on the phone even though it will say "Connected - Lets Go" on the watch. If you start the walk from the Fitbit app it will start the GPS and you get an accurate distance measurement. When the GPS doesn't start it would seem that the Blaze & App are working out the distance from the cell network which is pretty inaccurate and from other discussions would seem to be +-10%.

To test this theory I set the location to GPS only on the phone and the Blaze gave me a single red bar of the connected signal strength and didn't record any track. So I got no map on the App after as usual.

Even manually turning on the GPS using another app will not help as is seems that the Blaze->Fitbit app are not using it and you still get the same errors.

I have contacted Fitbit about this and after many weeks of canned replies they have finally admitted they are looking into it. So hopefully and update will be forthcoming.

[CMichelle]

@MuzDownUnder  Thanks so much for the info - the difference has been driving me nuts!  I have mapped out 2 or 3 different walks - one using Endomondo and one using the Walk Exercise function on my Blaze with Connected GPS and it is off every time by around 25%! I haven't tried the MobileRun yet in the Fitbit app but I will for my next walk.  However, an interesting note today - I just got back from my first bike ride with my Blaze and with Connected GPS, Bike Exercise Function, it was spot on to the Endomondo app!  I couldn't have been more shocked after all the issues I've had with walks.  Fingers crossed they have fixed some glitch and we will be closer from now on!  I have a Galaxy S6 Edge, by the way.

[SunsetRunner]

Interestingly @MuzDownUnder I too have an S7 and my Blaze is more than happy to connect to it.

This morning I walked a near 2km loop 3 times to see what differences I would see between just steps/connected gps/track. Details recorded are below (I'll include screen shot from dashboard later but for the moment I'm using an iPad mini)

Connected : 2138 steps 1.97km 19.08mins 145calories
Track : 1881 steps 1.94km 19.10mins 142 calories
Steps : 2236 steps n/a distance 21.20 mins 164 calories

So for me, the mobile track seems the errant recorder of steps, though distance is pretty consistent between the two. Unfortunately, for an auto detected activity the simple walk didn't register any distance.

[Rich_Laue]

When using the auto walk detection the Blaze or any of the other trackers will not display miles, sorry.

[SunsetRunner]

Yes thanks @Rich_Laue, I was aware but just trying to be complete in explanation for any others who might be reading.

[tjsplace21]

I sent my blaze back after about 2 weeks of inaccurate reading while walking. Its been about a half mile off compared to my map my run or walk on my iphone. Another friend compared his fitbit to I think a Nike app and he was three quarters of a mile off his run. I just got the vivoactive and used it 2 days and so far its accurate. The only negative is the watch is dim when inside but outside the screen is bright.

[hawkyou]

---

@MikeF wrote:

It's not an error, I just have a different opinion on how it works. I've no idea if I'm right, but then neither do you. We'll have to wait and see. 🙂

---

It's an error.  The app is still running.

[longhall7]

All- I have done several runs and tests with connected GPS, and this is what I have found.  When this is initiated, and you go for a run, an accurate map of your run is created by the app.  HOWEVER, your pace and distance is not accurately displayed during or after the run.  During the run, it seems that the watch is calculating distance and pace by counting your steps and stride.  I have tested this by riding my bike slowly with connected GPS on run mode.  Because my arms aren't moving while doing this, the watch will say that I have not gone anywhere (distance remains 0.0 miles).  I will then end the run and the map on the fitbit app will show my 1.5 mile route that I just took.  I can't understand this.  Conversely, if I start a connected GPS run and simply run in place for a few minutes, the watch will calculate and show that I have run a certain distance, when actually, I have been running in place.  This is because I have been moving my arms while running in place.  The map on the app will show that I have gone nowhere.  I took my GPS connected Blaze for a run this morning and also used a Garmin GPS device.  The results were off by about .13 miles per mile! 

Somehow, even when connected GPS is running on the Blaze, it doesn't seem to be caluculating distance and pace from the GPS on the phone.  Instead it seems to be calculating from stride and steps.  Has anybody else done similar tests?

[IsmeneP]

It is ridiculous that FITBIT does not provide an official clarification of how exactly the connected GPS works.  

Does it, or does it not use the distance as calculated by the phone GPS?

Does it just use the phone GPS to show the track you travelled on the map?

Is the distance calculated by Blaze with connected GPS any different from the distance calculated without connect GPS?

Although I am not bothered too much with the exact distance, or the accuracy of the HR measurement compared to a chest strap... And although I love the looks of the Blaze, I have to say that the lack of clarity from Fitbit regarding connected GPS, and the fact that only some of the smart notifications are shown on the Blaze (SMS but not emails or FB messages), plus the fact that special characters (from SMSs or contact names) are not properly displayed on the Blaze made me decide to switch from Fitbit to Garmin.  

As of sometime next week I will be using the Vivoactive HR.  I will of course do a parallel run of the VAHR with the Blaze and with an app on my phone .... And I will provide my final Blaze findings here ..... 

[IsmeneP]

So, the DISTANCE on the BLaze with connected GPS is calculated how?  

Using the number of steps times the  length of the stride (i.e. I have to calibrate my stride)

or the distance calculated through the GPS?

Tests from many Blaze users, including myself are not conclusive, can you please explain this? 

thank you. 

[AZPete]

According to the Help article, http://help.fitbit.com/articles/en_US/Help_article/1983/l=en_US&p=blaze&fs=Search&pn=1

HOW DOES BLAZE TRACK MY EXERCISE?

With multisport mode you can see real-time stats on your wrist during the workout and a summary in your exercise history. If you use a GPS-enabled mobile device, you can record GPS data such as distance, pace, and route while using multisport.

[IsmeneP]

Thank you , I know all that.  If it uses GPS to track distance, why is the distance calculated by the connected GPS different from the distance calculated by the apps that have on my phone? If I use 2 or 3 apps on my phone to track my exercise, all calculate the same distance.  But the Blaze with connected GPS calculates a different distance.  I am talking about the distance I see as total distance on my exercise screen of the watch, as well as the distance I see on the Fitbit app on my device (after I have completed the run).

Fitbit Developpers, please explain this to me ....

[longhall7]

Again- I think everyone should do a test in their car or bike to see that GPS connect is not calculating the RUNS by GPS.  It's being calculated through steps taken.

However connected GPS during BIKE activity (distance/pace) does seem to be calculated by GPS on the phone.

Very strange.  I had them send me another unit to see if there was a defect, but both acted exactly the same.

Not sure what the point of connect GPS during a run would be if it's not calculating from GPS!?