Hi,
I hope I've put this in the right place.
I've been using Strava for several years, but earlier this year got the Pixel Watch to make my tracking more accurate, to give heart rate etc. I use the Strava App on the watch and use it for both running and cycling.
Usually, it works well, but on fairly regular occaisions (maybe once a week), I notice that after the activity has uploaded to Strava, the last half mile or so is cut off. The run is still tracking when I get home, so its not a case of me accidentally hitting 'end' or anything like that.
Geographically, it always seems to cut off in the same sort of area - so I'm wondering if there's something interfering with the signal - but that doesn't really make sense to me as it doesn't happen every time, and normally the tracker wouldn't cut off the activity, it would just keep going until it found a new signal.
I don't know if this is a Strava issue, or a Google Pixel issue, but it's becoming frustrating and I wondered if anyone else had a similar problem.
Thanks
Yes, I'm doing it, but is boring. I also will not pay strava and I was planning to buy a new Sigma, but I give up this too because Sigma seems not interesting in solve this problem too.
I believe it is not a Sigma problem - there were changes on the Strava side and some other devices also have te same problem
I believe in that too, but Sigma should have interesting in solve it
I call back my temporary solution:
With SIGMA DATA CENTER on your PC, you can export your activitie at .TCX format and upload it manually on STRAVA.
Yes but that is not solution, Sigma is **bleep**y company and that is it
Yes, I know. This solution already was gave here
I made a test with a previous activity that was correctly imported and interpreted on STRAVA (the distance was accurate). I deleted it from STRAVA, exported it in .FIT format from SIGMA DATA CENTER, and re-imported it into STRAVA. However, the distance was no longer correct. I imported the same .FIT file into GARMIN CONNECT (the inventor of the .FIT format), and my activity was complete. The issue lies with a change in STRAVA."
Yes, I have heared about this allready. Are You tried this operation? How many time it spend and was it handy? You need PC for this. Therefore it comes like step back from tecnology century into the past. I want to say it is not user-friendly and it is not long term sollution. That's allready 3 month gone, but nothing is changed in this case. Regrettably.
Does this really work for you? I've tried this with the .tif file but still the same issue occurred. I will try with the .tcx file today but still it's a workaround I don't want to use. I've asked sigma for an update last week since it's over 3 months, this was their reply:
thank you for your message.
When we have found a solution in cooperation with STRAVA, so we will lunch an update and inform our customers.
Up to this point, we will ask you for patience.
We wish you a nice day.
just uploaded my afternoon ride as .tcx file to Strava and it works! So .fit files have the same issue but .tcx files seem to go well. I still hope STRAVA and Sigma will come up with a fix soon, it was way easier uploading my files via bluetooth to my mobile sigma app and then sync it to STRAVA.
I have a similar issue when syncing my Polar pacer pro to Strava. In mode 'race' time/distance is correct, but autherwise (when automatic pause on/off) strava interprets more pause times and hence time is shorter hence speed faster. I tried manual export/import with .fit file but that gives the same result. This problem started appearing somewhere last year, before I did not have this issue.
Hi,
with the .tcx file kilometers and moving time are correct. I lost elapse time and break time.
You can see my last activities on strava, all imported with .TCX file
my profile : christophe bacon, Sérignan du Comtât.
I have same problem with Sigma Rox 11. The .fit file always cuts off last few kilometers. On Sigma data center everything is OK, but when I export .fit file and upload it to Strava, last 4 or 5 km are being cut off. If I export .tcx file and upload it to Strava, there is no problem.
So problem is with reading .fit file. From Sigma app on phone it always share (I think) .fit file because every activity which is shared automaticaly is cut off. If I want to have exact data on Strava I have to do it manualy and upload .tcx file.
tcx file works ok only for distance. For example if you go and ride with someone and upload .fit file strava will show that you have rode with someone, if you upload .tcx file times are not correct and strava will not show that you have rode with someone. For every pause the difference between riders will bi greater for exatly pause time.
Perfect! This is important information. That's means the "cut-off" problem is on Strava end. Strava support should to know it.
Interesting, why this topic status is SOLVED?!
The problem is NOT SOLVED! Hey, Strava agents!
Nothing is SOLVED... Shame on you strava guys
Any update on this issue? Did one find a temporary (manual) solution yet?
Completely hopeless support. What's the point of paying for Strava if it can't even do the basics
I was done waiting for a solution. I have bought a Garmin, no more Sigma for me.
**bleep** Sigma and **bleep** Strava
Finally, the simplest solution is to not use either manual or automatic pauses. Disabling automatic pauses from the Sigma data center works correctly when done for each profile. Too bad for the average on the Sigma app. But Strava will be able to extract the riding time and calculate the riding speed.
Finally, the simplest solution is to not use either manual or automatic pauses. Disabling automatic pauses from the Sigma data center works correctly when done for each profile. Too bad for the average on the Sigma app. But Strava will be able to extract the riding time and calculate the riding speed.
I have still canceled my paid subscription for now.
