07-02-2017 14:29 - edited 07-02-2017 14:29
07-02-2017 14:29 - edited 07-02-2017 14:29
Hello, the past two runs have uploaded corrupt data. I am not sure how to resolve this problem. Instead of showing a 7 mile run at an 8:25 pace, it is showing a 0 mile run at a 9 million minute pace. Here are some pictures :
07-04-2017 04:36
07-04-2017 04:36
@DuckStock A couple questions, since there are a number of places where this can go wrong. What type of tracker are you using -- Charge 2, Blaze, etc.? What type of phone do you have -- iOS or android?
Also, I noticed that this exercise was over 73 hours!!
Laurie | Maryland, USA
Sense 2, Luxe, Aria 2 | iOS | Mac OS
Take a look at the Fitbit help site for further assistance and information.
07-07-2017 14:26
07-07-2017 14:26
Hello LZeeW, thank you for the reply. I am using a fitbit surge 2. I am uploading directly to my macbook pro, so I am not using the phone as a port to the dashboard. Yes the improper hours are one of the problems, as well as the wrong distance, and the lack of mapped gps data. It is strange, because the watch has worked flawlessly for the past 6 months.
07-08-2017 03:59
07-08-2017 03:59
@DuckStock I apologize, I should have noticed that your map was the fitbit.com dashboard view, not the app view. The key is the elevation doesn't show on the app view.
Next, there is a Surge and there is a Charge 2, but there is no Surge 2. This is important because the Surge has built in GPS and the Charge 2 has connected GPS.
With the correct tracker information, I will try to move your post to the correct device forum. I don't think this is a fitbit.com dashboard problem.
Laurie | Maryland, USA
Sense 2, Luxe, Aria 2 | iOS | Mac OS
Take a look at the Fitbit help site for further assistance and information.
07-09-2017 10:09
07-09-2017 10:09
Okay sorry for the confusion, I am using the surge. I have solved the problem (for now) with a simple manual reset. Thank you for helping me out.
07-10-2017 11:11
07-10-2017 11:11
Welcome to the Community @DuckStock! Thanks for chiming in to help @LZeeW.
@DuckStock It's good to know that the restart helped your Surge to behave normally. Thanks for sharing that.
If something similar was to happen again, I'd like to ask you to please let us know right away.
If you have any questions, please feel free to reach out.