Auto-Pause Speed too high for MTB

Use auto pause when stopped.

For mountainbiking (slow speeds, riding under trees…) there is imho one solution:
use a speedsensor 
and…

JRat1 said:

Use auto pause when stopped.

Same for me. When I am riding in steep uphill (15-20% grade), auto pause (with "when stopped" option) do not restart. 5 km/h is a too high low value for personnalisation. I changed to 2.5 km/h on my old edge 1000 and it works like expected. So its possible.

Yep.  I use a speed sensor and set auto pause to 5kph, but basically don't use auto pause on the mtb.  I want the whole effort; riding, hike-a-bike, stopping for a minute to catch my breath, etc. to be accumulated so only use manual pause when appropriate, which in my case is virtually never. 

thanks all, speed sensor seems to be the best solution

I'd like to second a lower speed value for restart AND autostop. My wife and I both have an Edge830 and now both have an Edge1040. We use the 1040 mainly for MTB/Gravel tours with navigation. We both have an speed sensor on all bikes. On the 830 especially my wife was annoyed when going steep stony trails where she falls back at 3 km/h and the 830 paused. Auto pause was set to "when stopped", but also when stop speed was set to "0.0 km/h", which was possible on the 830 with a mountain bike profile. It didn't help and sure I've checked that the speed sensor was connected. :-(
Saturday we did a MTB tour with our new 1040 (FW14.20) and the same annoying behaviour was there and my wife was really "pissed". Speed sensor was connect, auto pause was set to "when stopped", but when my wife was still slowly climbing up, the 1040 did "auto pause". That's not okay. Even more problematic is the fact, that the 1040 will NOT restart, because the lowest speed is "10 km/h", which my wife will NEVER reach on part with more the 18% ascent. 
So we really would like to see the possibility of having a functional "when stopped" and i.e. if the 1040 has a delay of 2 sec, then "when stopped" should mean "the bike is NOT moving for at least 2 secs". And second, a start speed speed that goes as low as "1 km/h", as everybody is free to choose a higher value. :-)
And please: We don't buy a high end bike computer to be forced to "manually" start and stop the device hundred of times during a long tour.
Thanks in advance for any help!

IDK what algorithm the device uses to determined "When Stopped," but the device needs some means of determining when you're stopped.  It senses distance by counting wheel rotations or by GPS.  GPS has position noise/drift so always shows you moving around when stationary, so it has to have some threshold below which it says you're stopped, if your speed is slow and the drift is in the opposite direction, it can say you're stopped when you're not.   With a wheel sensor,  it has to wait some specific time before seeing the next rotation to day you're stopped.  That too is a speed threshold.  My suggestion is not to use auto pause when mountain biking.

Thanks for your answer. 
But that should be solvedable on an high end device like 1040. So if "when stopped" could wrongly be trigged if one goes with "3 km/h" then Garmin should fairly offer something like "when stopped for 3 sec"! 
And as I said, people don't buy an flagship bike computer and then are forced to stop and start manually. That's not okay as you will forget it often.
No, the solution should be an automatic solution satisfying all customers. Only if a solution would negatively impact the majority of other users would make a compromise okay.