This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Strava Routes + Strava Live Segments works concurrently but turn-by-turn nav interferes with live segments when the turn-by-turn nav is chatty

Former Member over 5 years ago

I use the Strava Routes (under "Connect IQ" on my Edge 530) to navigate one of my strava routes plus I ride Strava Live Segments concurrently.

It works for about 75% of my non-negative gradient segments except if there is a lot of turn-by-turn navigation happening at the same time as the live-segment 'start' and live-segment 'end'.

Essentially, the "approaching" street XYZ display takes priority over showing the start and/or end of the live-segment. Instead, I see a little notification at the base of the Edge 530 showing a little flag icon and the name of the segment but it doesn't tell you when it starts and ends.

I can understand why Garmin would prioritize the turn-by-turn nav screen over the segment live tracking screen because generally speaking getting lost is a bigger problem than not PR'ing on a strava segment.

With that said, is there a Setting where you can tell the Edge 530 to prioritize the display of Strava Live Segments over turn-by-turn nav? The use case I'm thinking about is riding strava live-segments close to the start and end of my ride (and not getting interfered with by the turn-by-turn nav display) because I'm familiar with the general area close to home but the further I travel there is more of a need for turn-by-turn in unfamiliar areas. I guess I could stop following the route/course on the return home when I know my way but will that mess up with the logging of my ride? That also doesn't help with the segments at the start of my ride when I'll need the nav later in the ride. Perhaps, I'm over thinking it. Any suggestions/workarounds would be helpful.

thank you all!

0 Former Member over 5 years ago

Bump! Anyone, bueller? ;-)

0 Former Member over 4 years ago

Interesting to see that you actually got Live Segments to work while using navigation. Pretty much everywhere else, I'm reading that these features don't work concurrently. Is it because you do it via the Strava Routes IQ app, instead of the standard navigation functionality built-in to the device?

I recently bought a Wahoo Elemnt Roam, but am slightly disappointed by the usability of the turn-by-turn navigation on this device. I'm thinking of returning it, and getting the 530, because my main reason to have a bike computer is clear turn-by-turn instructions. However, I want Strava Segments to work concurrently (this is not a main priority, rather a nice-to-have, but it works fine on the Wahoo).

0 Former Member over 4 years ago in reply to Former Member

Hi Daniel, I’ve only ever used the Strava Routes IQ app for turn-by-turn nav + live segments. I doubt you’ll be able to get the concurrency working without using the Strava Routes IQ app.

Nonetheless, turn-by-turn nav with concurrent live segments works well on the 530 via the Strava Routes IQ app. My only gripe is how the 530 handles conflicts. More specifically, if a live segment starts at or near the same time as the next turn-by-turn nav instruction, the 530 will suppress the segment in favour of showing the navigation UI as if the segment didn’t happen. I understand why they implemented the algorithm this way because the vast majority of folks would prefer not to get lost as opposed to missing out on a segment. I turned off the “map” option on turn-by-turn on the 530 so it just reports nav text at the base of the screen but it still misses the segment. With all of this said, what I’m reporting is an edge case and only a problem for 1 or 2 of my main segments.

Daniel, I also have all my negative gradients segments working with this configuration thanks to https://www.doogal.co.uk/strava.php

I’m happy to help answer any additional questions you may have. I suggest you dump the Wahoo and pickup the 530 instead. It’s working well for me in the manner I’ve described above but I’m biased ;-)