Pausing track recording due to slow speed
I see that this question has officially been "answered," but I have an "edge case" to report that I don't understand based on the above discussion (along with some comments in related threads). During my mountain bike ride today at a particularly hilly and rocky park, I noticed that during many of the long, steep climbs, Locus appeared to stop recording (the moving/ride timer didn't advance -- it was paused). This seemed to happen when my speed dropped below about 2.5 mph (~4km/hr). I use a Garmin ANT+ hub-mounted speed sensor on my front wheel. In my Mountain Bike Profile, there's a check mark next to the "Speed" item under "Sensor," and not under "GPS." For this ride, I had "Record only when moving" checked/selected. If I recall correctly from another threadposting, the threshold for defining "stopped" was described by a Locus representative as being only .9 km/hr.
Years ago, I may have been able to sustain a greater speed during climbs of this type, but at 64 years old, that ain't happening -- these are already near-maximal heart rate events for me! In fact, one way I can sometimes tolerate climbing such steep/difficult trails is to intentionally slow down in an attempt to manage my heart rate (i.e., avoid "blowing up"). On days like today, this may mean climbing at only 1 or 1.5 mph. With a hub speed sensor, though, I should still be generating a positive (>0 mph) speed, and even 1 mph is ~1.6 km/hr, greater than the stated "stopped" threshold of 0.9 km/hr.
So, why is the timer pausing when, despite the relatively low value, there's a non-zero current speed coming from my hub sensor greater than the "stopped" threshold (I fully understand why a higher threshold speed must be used when depending on GPS speed for "pauses")? With the timer paused, I'm curious to know whether I'm missing some other data like "Energy" (kcals burned)?
For now, I've unchecked "Record only when moving" to evaluate how this affects things during my next ride. I suspect, however, that this will seem like a poor work-around as it will reduce the validity of comparing my average data from one ride to another due to variable stop time. Thanks for any clarification or advice that you can provide.