Inconsistencies between App voice cues and final logged data

[BigJ]

I have been using a basic Fitbit Flex to track steps for about four years and it seems to work fine within its limitations.  I also use the Fitbit App (latest version) on my Samsung J320 to track my runs and use the voice cues to give me a bit of feedback during the runs.  I have noticed that the voice cue might say I have run 6 k's but the GPS data that I see when I finish will always be shorter.....this morning in just over 9 k's it was shorter by 300 metres.  I have been running the last couple of hundred metres looking at the phone so that if I am wanting to run a specified distance say 9 k's I will run till the display says 9.2 k to account for a small discrepancy and actually run a little further than the 9 k's (Yes, I know there is no built in delay in the tracking to allow me to get up to speed and I always turn the tracking on a while before I start to run to allow a GPS signal to be acquired).  As I run in public open spaces well away from high rise buildings dodgy bouncing signals are not really an issue. I am assuming that the voice cue information is linked to the GPS data acquisition system as when I have run a measured, signed course the voice cue has corresponded reasonably well with the signage allowing for the delay in data processing and formulating the voice cue message. Any thoughts?

[LanuzaFitbit]

Hello @BigJ! 

Thanks for bringing this up. I'd like to ask a few questions about your setup:

• What Android version are you on?
• What app version are you running?
• When did you first notice this happening?

Look forward to your reply.

[BigJ]

Hi Lanuza



I am using a Samsung J320 (2016) running Android 5.1.1 with Fitbit 2.75 (it
just updated overnight as when I posed the question I was on 2.74). I also
run the App off my SD card to save memory on the phone itself.



The discrepancies have been around for a while, hence my always running that
couple of extra hundred metres to make sure I get the distance I want but
having the 300 metre difference the other day was just too much!



Yesterday, voice cue said 6 k's so I looked at the phone and ran until the
display said 6.2 k's. The App says I did 6.17 k's and the Activity on the
web page has me down for 6.14 k's.



I am due to run tomorrow (just a short 5 k's as it will be about 25 degrees
C) so will also be interested if the new version of the App reacts the same.



Best Regards



BigJ

[LanuzaFitbit]

Hello @BigJ! 

Thanks for reaching back and answering those questions.

It could be because the Samsung J320 is not a supported device. I will be passing this details on to the rest of the team. The moment we receive some news I'll be sure to let everyone know.

Having said that, please do let me know how it goes with your run with the new app version.

Look forward to your reply.

[BigJ]

Hi Lanuza



I would think my phone not being supported would not be an issue as it seems
to synch with my Flex OK but you never know.



I have done two runs now with the new version (2.75) of the App.



Saturday I ran until the voice cue said 5.5 k and I used the App display to
reach 5.6 k. After I stopped and synched, the App said I had done 5.58 k
but the map/web data said I had done 5.39 k so about 200 metres difference
in about 5.5 ks.



Yesterday (Tuesday) I had some trouble as a Google app started butting in on
my phone towards the end of my run! I didn't really manage to get a voice
cue for 7.5 k's but ran until the App display said 7.6 k's. After synching
the App says 7.6 k's but the map says 7.44 k's. Interestingly when I looked
at the splits it says I ran the first Kilometre in 4'27" (never run that
fast in my life!) and the second in 6'16". I use 500 metre intervals for
the voice cues and I got a 500 metre cue followed about 30 seconds later
with a 1 kilometre cue! This sort of close cueing has happened a couple of
times before also.



Supposed to be running again in the morning so we will see what happens
then!



All very interesting.



Regards



BigJ

[LanuzaFitbit]

Hello @BigJ! 

Thanks for sharing all of that. I will be passing this information on to the rest of the team. This seems to be related to a known issue. As soon as I receive some news or updates on the matter I'll be sure to post about it and let everyone know.

Feel free to reach out with any further questions.

[BigJ]

Thanks Luanza



I look forward to hearing the outcome of the investigation



Regards



BigJ

[LanuzaFitbit]

Hey @BigJ.

Thanks for your understanding! At this time we do not have any updates on the matter but I'll be posting about in here when there is something.

Let me know if there are any questions.

[BigJ]

Hi Lazuna



Thanks for the update.



This may or not be related to the issue but now when I run the Fitbit app
and play music at the same time something cuts the volume down to nothing so
I get no music and no voice cues!



BigJ

[LanuzaFitbit]

Hello @BigJ.

Thanks for sharing that.

They might be realated. I'll be sure to bring it up.

Feel free to reach out if there is anything else I can help you with.

[BigJ]

Thanks Lanuza



I note that Fitbit App has updated again overnight so I will see what
tomorrows run brings!



Cheers



BigJ