Strava differences between devices - autopause issue perhap?
Discussion
The last couple of MTB rides with a mate we've noticed that our respective strava distances are very different - both times his recorded 20-25% more distance (roughly 8 vs 10km and 17 vs 21km).
I would expect some difference due to limitations of phone GPS accuracy, but that's a huge difference.
Digging a bit deeper into the stats his has also recorded a much longer 'moving time' even though our elapsed times are about the same (as you would expect), and mine seems to have failed to record quite a few segments (especially higher speed downhill segments).
Wondering if it might be dropping GPS signal and auto-pausing itself because it thinks it isn't moving, then re-initialising the GPS and unpausing in a different place either without counting the distance in between, or losing a lot of distance and not registering the segment because the straight line between points is too far off it? But there aren't any obvious huge straight line leaps on the logged map, so it would have to be a series of smaller dropouts.
Anyone found similar issues and found a solution?
I'm not much of a strava junkie at all, but its a bit pointless if its only logging 3/4 of my ride and missing the best parts.
I would expect some difference due to limitations of phone GPS accuracy, but that's a huge difference.
Digging a bit deeper into the stats his has also recorded a much longer 'moving time' even though our elapsed times are about the same (as you would expect), and mine seems to have failed to record quite a few segments (especially higher speed downhill segments).
Wondering if it might be dropping GPS signal and auto-pausing itself because it thinks it isn't moving, then re-initialising the GPS and unpausing in a different place either without counting the distance in between, or losing a lot of distance and not registering the segment because the straight line between points is too far off it? But there aren't any obvious huge straight line leaps on the logged map, so it would have to be a series of smaller dropouts.
Anyone found similar issues and found a solution?
I'm not much of a strava junkie at all, but its a bit pointless if its only logging 3/4 of my ride and missing the best parts.
I would imagine by using the Strava app on the phone to record the track then the extra processing, guesstimates or whatever it does with the GPS data is invisible as you do not have access to that raw data. Perhaps recording the track using another app or device and uploading the GPX to a mapping site like plotaroute would reveal something maybe.
My phone is generally very consistent to itself at least and friends will often differ in distance and elevation (although not 20%).
Strava segment matching and time calculation is certainly strange. Looking at the top 10 times for a popular offroad segment in Surrey Hills the other day everybody was in the order of 80-90mph average speed.
My phone is generally very consistent to itself at least and friends will often differ in distance and elevation (although not 20%).
Strava segment matching and time calculation is certainly strange. Looking at the top 10 times for a popular offroad segment in Surrey Hills the other day everybody was in the order of 80-90mph average speed.
Hello!
Most obvious possible cause is that you and your buddies phones are on different data networks. This, as well as dropouts that phones usually get, could account for a far chunk of the disparity.
Strava via a phone is, in general, more of a 'best efforts' system than one that garners real accuracy. I use a Bryton Rider15 GPS Computer, and it's far, far more accurate than Strava ever was over the same routes that I use.
Initially, I used Strava as a backup, and found that it's results were very conservative compared to the computer.
Most obvious possible cause is that you and your buddies phones are on different data networks. This, as well as dropouts that phones usually get, could account for a far chunk of the disparity.
Strava via a phone is, in general, more of a 'best efforts' system than one that garners real accuracy. I use a Bryton Rider15 GPS Computer, and it's far, far more accurate than Strava ever was over the same routes that I use.
Initially, I used Strava as a backup, and found that it's results were very conservative compared to the computer.
STiG911 said:
Hello!
Most obvious possible cause is that you and your buddies phones are on different data networks. This, as well as dropouts that phones usually get, could account for a far chunk of the disparity.
Strava via a phone is, in general, more of a 'best efforts' system than one that garners real accuracy. I use a Bryton Rider15 GPS Computer, and it's far, far more accurate than Strava ever was over the same routes that I use.
Initially, I used Strava as a backup, and found that it's results were very conservative compared to the computer.
^ This.Most obvious possible cause is that you and your buddies phones are on different data networks. This, as well as dropouts that phones usually get, could account for a far chunk of the disparity.
Strava via a phone is, in general, more of a 'best efforts' system than one that garners real accuracy. I use a Bryton Rider15 GPS Computer, and it's far, far more accurate than Strava ever was over the same routes that I use.
Initially, I used Strava as a backup, and found that it's results were very conservative compared to the computer.
I use a Garmin on my bike and it is slaved to a Garmin sensor on the back wheel, as well as satelites. It defaults to the wheel sensor when it can't get a good GPS fix. If I try recording just on my phone it is very different; when we ride in a group there is one guy who late brakes at stops and is away at a right old pace as soon as the lights change - when I asked him why it was because he wanted his bike up to speed as soon as possible so when the auto stop/start activated it didn't effect his average pace. I have a benchmark run and ride that I do every couple of months as a time trial to gauge fitness - a good GPS watch might be a good investment?
I often record my MTB ride on two Garmin devices , my VivoActiv4 watch and an Edge 820., and occassionally a Garmin Instinct watch if the VA4 is flat Over a 6 mile ride which usually has a lot of tree cover the Edge820 is usually upto 1/3rd of a mile shorter distance than the VA4, Trails recorded on the Instinct suffer from poor elevation tracking by a significant margin so I avoid using it . All are set to the same GPS (Galileo) settings and both are checked for GP lock in the open before recording is started. I suspect different GPS chipsets/firmware is responsible for the differences but its hard to spot an visible differences between the track except on the odd occasion when there appears to have been GPS issues and the tracks have visibly deviated from the path taken. II originally noticed plain GPS option produced the lowest trail track accuracy followed by GLOSNASS with Galileo being the most accurate though I've not bothered changing back to see if that alters much (between GLOSNASS/Galileo)
Gassing Station | Pedal Powered | Top of Page | What's New | My Stuff