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

Map orientation not track up (after 5.50) after every stop in riding

stona1
over 4 years ago

Hi,

I realized that after upgrading to 5.50 when I switch to data screen with map (not during navigation) map orientation is not set to track up.

To be precise on the beginning it is track up but until first stop. When after stop I began riding again it is loosing it track up map orientation. I found simple solution (but not convenient). If I switch to whatever other data screen and switch back to map then it is displayed correctly oriented track up but of course until next stop etc...

Does anyone else found this problem too?

BR
Arek

  • Former Member
    0 Former Member over 4 years ago

    For me this happend once or twice during navigation. I do the same thing as you: change screen and go back.

  • Former Member
    0 Former Member over 4 years ago

    For me this happend once or twice during navigation. I do the same thing as you: change screen and go back.

  • Former Member
    0 Former Member over 4 years ago

    For me this happend once or twice during navigation. I do the same thing as you: change screen and go back.

  • 0 over 4 years ago

    Could it be that you are commenting about the ForkSight map that the display automatically switches to when you come to a stop? That map is north-up.  When you start moving again, or if you press the back button while stopped, it will return to your normal riding screen.

    https://support.garmin.com/en-US/?faq=P01Lqy8vUY84LonexcjNE9

  • 0 over 4 years ago in reply to ewarnerusa

    Well it is possible but I can not check it. I can't fint option to turn on and off ForkSight. I'm on firmware 5.50. I was looking in every position in menu (I hope) and can not find nothing related to ForkSight. 

    I found on forum thread related to ForkSight on 830 and they pointing that it should be: "Under Profile->Mountain Biking menu "Forksight" is enabled or disabled" but I do not have this options on my 530.

  • 0 over 4 years ago in reply to stona1

    When I first got my 530 at Christmas '19 I didn't like the Forksight map popping up automatically and looked into ways to disable it.  It is possible you found my old thread when searching these forums for it!  I left it enabled though and I'm totally used to it now.  

    Here's my original thread, including screenshots of what the ForkSight map looks like, asking how to disable it with some responses provided.

    https://forums.garmin.com/sports-fitness/cycling/f/edge-530/209573/edge-530-display-auto-switches-to-a-map-i-don-t-think-i-like-this/984790#984790

    My 530 updated to FW 5.50 last night and I have not used it since.  We'll see if I notice similar map behavior.  

  • 0 over 4 years ago in reply to ewarnerusa

    I am almost sure that it is ForkSight. After changing some settings now my map is displayed correctly but I can not realise which one was responsible for it.

    Problem is that I still do not know how to turn on and turn off ForkSight. I have read your old thread and can not find information how to do this. I would like to write that on my device I have all the time enabled Starva segments - before and now - so in my situation it is not related. 

    Nowhere in my activity profiles there is nothing about ForkSight. 

  • 0 over 4 years ago in reply to stona1

    I rode yesterday in a new area and followed a route that I pushed to my device via trailforks. During the ride I noticed that that navigation map would keep changing to North-up display rather than track up. Toggling to a different screen and then back to map would return to track up. But this happened dozens of times. 

  • 0 over 4 years ago in reply to ewarnerusa

    happened also to me when navigation via TrailForks.

  • Former Member
    0 Former Member over 4 years ago

    Having the same issue, for now it has only happens when navigating Trailforks route, switching screens as others have mentioned resolves it momentarily