Surge Error on long runs - Wrong data shown on PC and bad TCX

[michov]

Hello,

When runs go longer than 14miles, I am experiencing these issue:

- Data on Fitbit Android App is 100% accurrate. But when checked at Fitbit in the PC, the last mile is innacurrate in the map. However the total distance, time, pace, etc of the run is correctly shown in the PC.

- For the same run, the TCX file exported from Fitbit over the PC it not readable by Runkeeper. Cannot read any data from it. If I compare this file with old files that loaded correctly, I cannot find obvious differences - I do see lots of decimal places in some coordinates on this latest file.

Any ideas on how to fix this is appreciated. I can make the TCX file available if needed.

More evidence of these issues below:

Image for Run from App showing correctly the last mile:

From the PC:

Any ideas? 

So far did not have reasons to move to Garmin, but this is a great excuse to retire my Surge.

Thanks,

[RobertoME]

Hello @michov, I've seen you are new around so let me give you a warm welcome. I've seen this issue twice, counting you.  Can you let me know how you are tracking your exercise. Are you using any of the exercise shortcuts of the Surge tracker or you are using MobileRun using your app? How often is happening this? Is the issue only present when you run for more than 14 miles?

Let me know this details and any other you feel pertinent and I will investigate further to find a solution or pointed you the right direction to fix this issue.

See you around and keep me posted how it goes.

[michov]

Hello,

Lets focus on the issue of not getting accurate map data in the PC in ftibit.com, while it is shown correctly in Fitbit Android App.

Are you using any of the exercise shortcuts of the Surge tracker or you are using MobileRun using your app? 

Answer: I use RUN shortcut to start my activitites. I do not use the app while running, but I do carry my phone with me.

How often is happening this?

Answer:  Short sruns under 8miles have no issue. A 13 mile run had not issue (no pauses durgin the run)

Is the issue only present when you run for more than 14 miles?

Answer: It happended on a 15mile and a 16imle run. Both had a couple of pauses durign the run. The wrong data on map happens always in the last complete mile of the run. For instance, if the run was 15..03 the error is in mile 14-15, not in 15-15.03. Or if the run was 16.09, the error in in mile 15-16, not in 16-1609 

Regarding the other issue I reported about TCX fiel not loading in Runkeeper, I found that Runkeeper web page has a problem and it not leeting TCX fiel load at the moment.

Thanks,

Jorge

[RobertoME]

Hello @michov, thank you for letting me know these details. I'm was reviewing with my teammates the issue you brought to my attention and its very odd to be honest with you. So as a test, can you try with a different GPS exercise to see if the persist? 

I saw in other threads a case where the numbers where not the same, we are not talking about the map; but the actual stats of the exercise, and apparently changing the exercise was a workaround to have the same information across both platforms. We can try this, at least to identify the source of the issue.

I tested the issue myself also to replicate the scenario, but I was not able to obtained the same results you depicted on your first post. Both maps, either on my app or my computer were the same with no big differences.

If even after try with other exercise the issue still continue to happen, my recommendation is to approach to our Customer support team. They have more tools to review your device history and can tell you what would be the next step.

Keep me posted If you have more questions.