Mountain Bike Reviews Forum banner
Cancel
Create thread New Forums

Strava inaccuracies

Jump to Latest
81 - 95 of 95 Posts
#82 ·
Duffman1976 said:
It is NOT strava, it is the device you are recording with. Strava just takes your GPS recorded from your device and maps it. If your device gives strava garbage, garbage is coming out. I've noticed this a lot with guys using older phones with battery life that isn't what it used to be. They will have a bunch of straight line segments and times on segments magically way faster than any of their previous best times. Funny part is they still think their times are legit. Anyway, use a dedicated recording device like a Garmin and your recordings will be much more accurate.
Click to expand...
As referenced in the first post it was recording correctly with Trailforks.
And now it works correctly with Strava again.
 
#83 · (Edited)
Cleared2land said:
It's amusing to hear folks bash Strava for the problems that was generated by their phone. Some seem challenged to grasp this and continue to blame Strava. I hear it regularly from some that I ride with.
Click to expand...
Depends if you're talking about the app, which is itself recording the waypoints, or the cloud platform, which has a dithering algorithm to interpolate those waypoints when it draws overlay graphics onto maps. Strava has been known to have bugs in both.
 
#84 ·
Duffman1976 said:
It is NOT strava, it is the device you are recording with. Strava just takes your GPS recorded from your device and maps it. If your device gives strava garbage, garbage is coming out. I've noticed this a lot with guys using older phones with battery life that isn't what it used to be. They will have a bunch of straight line segments and times on segments magically way faster than any of their previous best times. Funny part is they still think their times are legit. Anyway, use a dedicated recording device like a Garmin and your recordings will be much more accurate.
Click to expand...
Did you even read the thread?

While your point is valid, it's not relevant here. People were satisfied with the results they got for awhile, then things went to **** with an update, and now a recent app update seems to have resolved the problems. So this case is pretty clearly caused by a problem with the app.
 
#85 ·
It's very clear that some posters don't do any tech trouble shooting.

1) The phone itself has not had any updates on its software whatsoever and has worked flawlessly with a specific app for months while on that current software.

2) The app in question pushes an update and the very next ride after that app update (and with the same phone on its same software) there is an immediate and major problem reported by 100s of users.

3) Strava acknowledges that there is in fact an issue with their latest update and says they are working hard on a fix.

4) A new Strava update is pushed out by the app designers and all of the reported problems are immediately fixed on all of the same phones with no change in their software version.








34,823) It's the phone's fault.:ROFLMAO:
 
#86 ·
Duffman1976 said:
It is NOT strava, it is the device you are recording with. Strava just takes your GPS recorded from your device and maps it. If your device gives strava garbage, garbage is coming out. I've noticed this a lot with guys using older phones with battery life that isn't what it used to be. They will have a bunch of straight line segments and times on segments magically way faster than any of their previous best times. Funny part is they still think their times are legit. Anyway, use a dedicated recording device like a Garmin and your recordings will be much more accurate.
Click to expand...
How do you explain my Samsung Galaxy S23 Ultra working fine for 5 months, then having a few weeks of quirks before another strava app update and then is started working fine again..... Perhaps read the entire thread before making a very wrong comment.
 
#87 ·
You guys should stop giving Duffman a hard time, he has a valid point imo and everyone is free to agree or disagree civilly.

Even if the device isn't specifically the problem it can be part of it. The updates to keep data from going wonky seem to be needed only for certain mobile devices and not dedicated gps's.
 
#88 ·
Sorry for offending anyone recording with a super duper ultra supreme deluxe android phone. All I'm saying is that if you want accurate times you should use a device that is dedicated for this use. Just think of all the tasks modern phones are doing simultaneously vs a cycling computer. I used to have these errors a lot, especially with when my phone got a couple years old and the battery was not working efficiently anymore. Switched to a garmin and all of my recordings have been flawless since. Sounds like the app update was also causing problems as well. I will say most of the errors were caused by iPhones and iWatch users, not android. So maybe there is something in these devices that pull resources away from GPS activity when preserving battery life. All of these factors are why I don't put much stock in Strava segment times anymore.
 
#91 ·
Duffman1976 said:
Sorry for offending anyone recording with a super duper ultra supreme deluxe android phone. All I'm saying is that if you want accurate times you should use a device that is dedicated for this use. Just think of all the tasks modern phones are doing simultaneously vs a cycling computer. I used to have these errors a lot, especially with when my phone got a couple years old and the battery was not working efficiently anymore. Switched to a garmin and all of my recordings have been flawless since. Sounds like the app update was also causing problems as well. I will say most of the errors were caused by iPhones and iWatch users, not android. So maybe there is something in these devices that pull resources away from GPS activity when preserving battery life. All of these factors are why I don't put much stock in Strava segment times anymore.
Click to expand...
still irrelevant to the thread
 
#92 ·
Duffman1976 said:
Sorry for offending anyone recording with a super duper ultra supreme deluxe android phone. All I'm saying is that if you want accurate times you should use a device that is dedicated for this use. Just think of all the tasks modern phones are doing simultaneously vs a cycling computer. I used to have these errors a lot, especially with when my phone got a couple years old and the battery was not working efficiently anymore. Switched to a garmin and all of my recordings have been flawless since. Sounds like the app update was also causing problems as well. I will say most of the errors were caused by iPhones and iWatch users, not android. So maybe there is something in these devices that pull resources away from GPS activity when preserving battery life. All of these factors are why I don't put much stock in Strava segment times anymore.
Click to expand...
I still get the feeling you did not read the thread before posting...... I ended up switching to a Garmin watch even though my phone strava app was fixed by strava.......
 
81 - 95 of 95 Posts
About this Discussion
94 Replies
39 Participants
Last post:
J.B. Weld
Mountain Bike Reviews Forum
posts
16M
members
534K
Since
1990
A forum community dedicated to Mountain Bike owners and enthusiasts. Come join the discussion about bike parts, components, deals, performance, modifications, classifieds, trails, troubleshooting, maintenance, and more!
Full Forum Listing
Explore Our Forums
General Discussion Downhill - Freeride California - Norcal Shocks and Suspension Passion