Is there a recording limit on exercise?

[LorenPechtel]

I'm looking at what it recorded from yesterday's hike and things look very strange.  We were out there 8 hours and it seems to have given the recording fits.

1)  Attempting to drag the bar along the graphs is impossible--the browser seems to be incredibly lagged on something.

2)  At roughly the 5 hour point it shifts from a detailed chart to what looks like data points every 30 minutes.

3)  The elevation chart is seriously wrong.  We climbed, went through one dip and then climbed to our maximum elevation at about 2:30 into the hike.  The elevation chart accurately reflects this, but from that point on it has little to do with reality.  There is one peak, then it shows a straight-line decline to our objective--in reality we stayed at our high elevation until about 3:00 in, then did all the decline by 3:30.  (And stopped for lunch at about the 4:00 point--that should have caused a flat spot.)  The graph, however, shows a small but sharp decline there, followed by a straight line decline from that point until the end of the recording.  This was an out-and-back hike, the graph has to be symmetric!  (The end points aren't even the same elevation--a look at the topo map seems to show the final elevation being more accurate than the start.)  Note that the map of the path appears accurate, it shows no loss-of-data artifacts.

[RicardoFitbit]

Hi @LorenPechtel, it's nice to see you again participating here in the Community Forums.

I appreciate all the details that were shared in your post. To better assist you with this situation, can you please let me know if you're checking such information in the Fitbit app or Fitbit.com dashboard? If you're seeing such discrepancies in the app, which mobile device you're currently using to sync the information that's tracked with your Charge 2? When was the first time you noticed such discrepancies and this occurs every time you do an activity?

In the meantime I receive your answers, please restart your Charge 2 to refresh its performance.

Keep me posted and let me know if you have any additional questions. 

[LorenPechtel]

Dashboard.

I don't think there are any other cases in my history where I would expect to see the problem.  I have only one other hike in there that goes past 5 hours and that one is corrupt (your app apparently didn't like my phone running out of power.)

I have tentative plans for another long one Sunday, I'll see what happens.

[LorenPechtel]

More data (I did the reset after your last message):

My planned hike on the 11th got disrupted by life, I did it on the 18th and things are even worse.

On the dashboard it says 12.42 miles, 59'09" pace, the displayed map is accurate.  Attempting to display the details barfs.  My previous recording of an all-day hike also barfed but my phone went dead during it and I figured that was the culprit, but this time my phone did not go dead.  Accessing the activity log shows 36,294 steps for the hike--yet it recorded 47,968 steps for the day.  This makes no sense as I got up, ate breakfast and loaded my food and water into my pack, and then afterwards I ate dinner and went to bed--I would be surprised at 1,000 steps not on the trail.

Note that the 47,968 is very similar to what I got previously on virtually the same trail (this time I took a fork that basically ran parallel to the main trail for about 1/2 mile.) but I forgot to record the hike so there's no detail record to look at.

More accurate data from MapMyHike shows 17.21 miles, 42:49 pace.  The route I took is normally considered to be 17 1/2 miles.  I believe the errant Fitbit pace is from using the very inaccurate mileage combined with the accurate time.  My pace really was slow--this was the highest mountain in this part of the state, the climb is 4,640'.

[RicardoFitbit]

Thanks for your reply and update @LorenPechtel, sorry for the delay in responding.

I appreciate all the information and details that were shared in your post, I'm sorry to know that you're still experiencing difficulties, thanks for trying the restart process that was previously shared.

Fitbit devices calculate distance by multiplying your walking steps by your walking stride length and multiplying your running steps by your running stride length. We estimate your stride lengths using your height and sex. If your Fitbit device uses GPS and you track 1 or more runs using on-board or connected GPS, we evaluate that data to automatically update your running stride length. For best results, run at a comfortable pace for at least 10 minutes.

If you prefer to measure your walking and running stride lengths yourself and enter them manually, see How do I measure and adjust my stride length?

Note that when you're tracking an activity with GPS, Fitbit calculates your distance using GPS data rather than steps. If you begin moving before you get a GPS signal, the tracker will calculate distance using steps and stride length as described above until a GPS signal is found. 

Let me know if you have any additional questions.

[LorenPechtel]

I'm hiking--outside, other than one hike where my phone ran out of power it should have GPS.  Besides, the terrain is uneven, stride length doesn't mean much--the people who use step counting to estimate distance substantially overestimate the distance they went.  That's irrelevant, though, as the real issue is the messed up data it's recording--that is, if it even will display it at all rather than simply showing an error.

I don't know if you have any way to view this:  Corrupted hike but it shows the corrupted data.  The problem here that bothers me is the elevation--that's **not** right--it was an out-and-back, that graph should be symmetric.

And that's what happens when things work.  Even longer and I get this: Error page Admittedly, I have been known to refer to myself as half-sasquatch due to my big feet but your tracker doesn't know that.