Weird data in strava (shorter time)

[Efejota]

I am testing Tour, Endurance and Ultra modes to check with S9B. Today I made a long walk using endurance mode. In Suunto app distance and timing fits perfectly. However, Strava counts only like a third of my timing, as if I had been resting while, in fact, I walked without any interruption. As I had not used these modes before, I wondered whether this is an expected behavior or not or even a bug in the latest firmware.

[isazi]

@efejota what happens if you mark the activity as a race in Strava?

[Efejota]

@isazi You are a genius. It creates a problem, though, forcing me to change hiking to running. By the way, the same happened with another activity where I was trying the new Tour mode.

Hoy does it happen that way?

[isazi]

@efejota because Strava thinks that you are not moving fast enough and cuts the time.

[Efejota]

@isazi Amazing. I am not good enough for Strava . It seems strange though. I move slower when mountaineering and it counts it properly. But not in endurance or tour move. Why?

[isazi]

@efejota I don’t know, Strava is a bit peculiar for those things

[stromdiddily]

@isazi everyone else seems to have this worked out except for Suunto. I don’t think it’s a strava problem…

[isazi]

@stromdiddily from what I read Strava interprets the scarcity of points of those mode with less points as lack, or very slow, movement.

[Brad_Olwin]

@efejota This is Strava’s problem not interpreting space between GPS points. The only way to get this to work is to mark as a race. I typically use Endurance mode for 100k to 100 mile races and Ultra mode if my 100 mile races have a 48h cut off. Otherwise, there is no real reason to use these modes. There is no bug in the software as this issue is known for sometime. For example, TrainingPeaks interprets the data appropriately. Since Strava is basically lies about times as it removes non-moving time this is the consequence.

[cosme.costa]

There is a small trick (credits to: @Dimitrios-Kanellopoulos ), if you do a small pause with the watch then Strava will count correctly the time. This works for running and trail running for sure and I think the same for hiking and walking. The pause can be one second, like push twice the upper button.

Strava sucks quite a lot on this, in my last race it cut nearly two minutes, and it was only from two small steep trails where was impossible to run and I had to walk. In my area we do not have very high hills/mountains, but we have a lot of them, so it is easy to get 700/800 m ascent in twentyish trail runs but with 3 to 5 uphills, all of them quite steep, here Strava never gets the correct timing if you do not do the trick or mark the activity as a race. Besides, in my opinion Strava’s threshold to consider you are not moving is quite off.

[Efejota]

Thanks for all the information. It seems a Strava problem, maybe because it was aimed towards running/cycling?

@Brad_Olwin I was trying the other modes as to understand how would the S9B perform if I was to spend like two or three consecutive days in the mountains hiking without charging. For one day activity, performance mode is brilliant.