I believe I am having a similar issues with my speed sensor. When mountain biking without the speed sensor the distance always fell short due to all the twists and turns. For years that problem was resolved by use of a speed sensor. I do the same trails…
I don't know why OWS app records so far short distances, that's surely something wrong on its algorithm, report it to beta team... If you want to do a test, use run or walking app instead and you will see that diseases will be fine.
The short answer is no. You can see the distance that is left on the segment, but not the distance travelled along the segment.
On the 1040 this would be the "Distance to Next"
yes the tracking seems to much more inline with reality. Does anyone know how to get the distance corrected - I get about 10% short on any know course everytime
The only cadence sensors I know are the footpods and HRM-Run. As it happens, I use both!
The footpod takes priority for cadence if both are connected to the watch.
I've also set the footpod for pace (a must) and distance (YMMV, but my GPS distance is consistently…
In order for you to see the calibration option. You would need to record a distance of atleast 1.5 miles on the watch. The treadmill will most likely be reading a lot higher at this point if the distance is reported short on the watch. If the distance…
I have an F6+ Pro. GPS settings: GPS+Glonass, 1 sec, no 3D speed or distance.
when I run with friends, especially trails, my distance is always short...but my elevation is the same as theirs. I know my distance is short because the runs are runs I have…
or are these false alerts because the algorhythm thinks i am riding on the other (nearly) roads? sometimes i ride on forbidden sections (bike is not allowed for a short distance) or there is cyclepath next to the main road but i prefer the main one.