GPS tracking android app

[LaAnTu]

Should probably read if someone else has posted this, but there is so many fault with Fitbit so i just post.

The tracking with GPS does not work very well. It seems it only start tracking the time elapsed when I reach "fat burn zone".

I have check this with other GPS tracking software running at the same time and Fitbit tracking is way off. Like walking up a mountain takes 30 minutes in real time, Fitbut tells u made it in 25 minutes.

[USAF-Larry]

@LaAnTu, can you provide a little more information on what is happening?  You didn't say which Fitbit tracker you are using, and you don't say how you are tracking the exercise.

[LaAnTu]

Hi,

I am using Charge 2.

The way I track the exercise is throught the Fitbit app: Exercise ---> Track

I seems the Fitbit app dont track the minutes spent e.g walking from the point you start the tracking until it ends, as a normal gps would do. I seems to me it only start tracking time when I reach "fat burn sone".

Something must be wrong either way when a normal gps, is in my case with a walking exercise up a little mountain, shows 22 minutes and the Fitbit tracker via the app shows 17 minutes. This is not a one time incident. Happens on all my exercises. Therefor I alwas run a gps tracker in the background to get the correct data. (beat my time etc.)

Also the same problem with distance, also every time.

2 days ago I went for a hike, gps shows 12km, and thats correct. Fitbit shows 9,44 km.

And I ask, do I use to different GPS? No, I use only my phone with Fitbit tracker and GPS logger in the background. So they both use the same GPS signal.

I believe there is a variable programmed into the Fitbit tracker that is affected by the state av the heart OR it is just not accurate enough.

But I am leaning towards the heartrate because the last 12km (GPS logger) hike vs. 9,44 (Fitbit tracker) there is 2,5 km missing. And I would guess this is because of some stops/slow walk and lowered heartrate.

[USAF-Larry]

@LaAnTu, there are several things here. The distance tracking has nothing to do with the "fat burn zone" unless you are using SmartTrack.  If you are using the Fitbit app to track the exercise, it starts measuring when it gets a connection to the GPS.  If you are using two different GPS trackers at the same time on the same phone, there will be conflicts in connections that will cause error.

Have you tried using the Exercise Mode on the Charge 2 for Walk, Hike, etc., instead of using the Fitbit App Track Exercise feature? If so, has the distance been more accurate?

[LaAnTu]

I have tried i directly from the Charge 2, but that was a while ago. I can try it next time for measure.

When it comes to running 2 gps logger at the same time there is no error.

The Fitbit measured same distance and time wrong before I ran another gps logger. And still does with both gps loggers running. But the strange thing here is that the other logger is perfectly correct, fitbit is not. 

If there is no link between heartrate and gps logging there must be software issue. And Fitbit has got loads of them, from heartbeat measure failure with puls rises rapidly to food logging glitches, custom food problems...

[LanuzaFitbit]

Hello @LaAnTu! Thanks for coming in to help @USAF-Larry! 

I'd like to mention that there is currently an issue we're working on that causes the GPS information from the Charge 2 to not be very accurate when using any exercise besides run. My suggestion in this case would be what @USAF-Larry mentioned, select the Run exercise directly from the Charge 2 and then make sure the connection with your mobile device is strong.

Let us know how it goes after trying this!