Strava live segments is an important feature for me, because it is really fun. I had an Edge 520 before and it worked fine, but sometimes it lost the segment. Edge 1030 never loses the segment but the comparative times in real time are not accurate at all. I cannot rely on it. For example, I was trying to beat my PB this morning in a 2 km climb. I started at full power and after 200 meters the 1030 said I was 11 seconds ahead. When I reached 500 meters it said I was 15 seconds behind (all of a sudden). I tried to cut the lead for a little while, but I couldn´t do it, so I gave up. At home, I have compared today's effort and my PB and there is no such difference. The two efforts are pretty even, with a minimum difference of 1 or 2 seconds between them until I gave up. This happens a lot. The gap showed by the 1030 is not accurate at all. Edge 520 is far more accurate. With the 520 you know the actual gap during the whole segment and you can rely on it. I don't know if the algorithm of the 1030 is different, but it works worse. Please, implement the same algorithm or method used in Edge 520 for Edge 1030. Thank you.
" Behaviour observed by many of you with inconsistent and jumping time gap might be caused actually not by your current ride but the ride which you're comparing to. I've found it while analysing my ride, see below an output from Strava Effort Comparsion:"
See post 32 above. I made several segments from my own data. I always record at 1 second intervals. Each of the segments jumped around, forwards and back again. This was sent to garmin 4 months ago but I guess they can't fix it.
I had strava premium but because it doesn't work properly on my 1030 I now refuse to pay for strava summit.
This is quite old discussion but seems that issue is still the same as over oune year ago.
Just a recap of the problem which is the gap between your actual effort and your PB (or any starred record you want to be compared with in the Live Segment). During the live segments there is a sort of fluctuation ot the gap between your ride and the record you are following. See attached as an example
I see that this issue is not based only for 1030 but to me it's a wong implementation of the feature not a device problem. I think that is a very interesting ad useful feature but it works at least at 40% of the potential, It isn't unusefull to have a number that at the finish line is very different from the reality. Yesterday for example I ride a 10 km live segment and I record my PR with -46 sec for a 46:00 minutes of elevation's ride. During the live segment I try to take o a look of my garmin 1030 live segment screen and I see this "wave" fluctuation of the gap. I see also that at the end of the segments I made a -46 sec, but during the live segments I never see such a good difference, only -15 sec or max - 30 sec
Garmin = take care of this thread, your software need to be at the quality that your user want to have,...
I am still having the same issues with segments. Am I the only person with this? Despite providing as much information as I could I haven't heard anything for a long time
I'm having this same issue with live segment times inaccurate and jumping around on my brand new Edge 530 so it isn't fixed yet. I'm surprised more people are not complaining.
I stopped using my 1030 over a year ago because of the live segments performance. I switched to wahoo and its simple but better for me. I did have a 820 before the 1030 and that simply showed green when ahead and red behind! it was so easy to understand and then they ruined that with a firmware update so its like the 1030. Garmin makes me so angry launching first to fix years later if at all. We are unpaid beta testers who have paid good money for substandard goods.
I think this started about 15 months ago. Both Shawn and Alan from garmin took an interest in the problem but it wasn't fixed by their engineers.
It isn't going to be fixed. There have been half a dozen people note the problem, do some fault finding but no fix. It obviously wasn't a simple fix from garmins side otherwise it would have been remedied.
As this doesn't affect many people (more likely not too many people have complained) garmins engineers will work on something else.
Garmin 1040 is due in about 7 months or so, so maybe the fix is the garmin tried and true... "too hard to fix buy our new garmin."
I don't really care any more as I have been refunded instead of a 4th 1030.
It's a shame really, I did like the 1030 more than any other of the previous 10 garmins I have owned but like all the rest it didn't work as it should.
