MRA Community Forum

@M.-Schrijver said in First point is often ignored: If you draw a straight line from your postion to (way)point 1 and a straight line from your to the postion where the route is picked up. As far as I know the decision is not made on distance of straight lines, but on distance over the road, probably measured in time and not in meters, if that's the parameter used in planning. @Herman-Veldhuizen said in First point is often ignored: I am more worried about others which have to explain for ever why point 2 is considered the nearest point in my first scenario. The only correct answer will always be point 1. I watched the movie just now and see what you mean. It does seem funny that WP1 is skipped in this particular situation. I would however not worry about it at all. If you want to start at WP1, just unselect "nearest point" or long-press WP1 once navigating. There could be multiple reasons for what happens. Maybe a one-way road to WP1 or a speed limit that makes WP2 quicker despite that it seems to be further away. This feature certainly prevents MANY "why does it keep sending me back to WP1" questions, so let it go. It is really not worth the fuzz in my opinion.

Tomtom pakt route op bij het punt wat ik in het screenshot heb aangegeven. Dat is het dichtstbijzijnde punt. Bij MRA wordt de route niet bij het dichtstbijzijnde routepunt opgepakt. Dat zijn 2 hele verschillende dingen

A good route in your navigation device depends a good planned route. Just like Marinus said. How it is planned is the first suspect. Can you share the route as a public route. We all can look at it and maybe tell you what went wrong.

Als je bij de planning er al rekening mee kan houden, is het een kwestie van wat meer vormingspunten plaatsen en dan kan je het gewoon op snelwegen toestaan laten staan.

There is an Autozoom in Android Auto. I can clearly see this on my screen. But how it works? I don't know. It looks random. My setting is "Both" (speed and directions/crossings). Biggest complain. The crossing with a white arrow shows up in the screen only 120-140 meters before you arrive at the crossing. Too late. The blue line and position indicator are looking good. Did not see any strange things. Smooth graphics. Good job. There is still a clear delay in real position and position on screen. Combine this with the issue of the Auto zoom and you can understand there is an issue. What i noticed about the delay in the position indicator compared to other navigation apps. Other navigation apps are more on par with the real position. But when you take a wrong turn it takes those other apps a longer time before they noticed you took a wrong turn. It seems all navigation apps have the same issues but those other apps do a more aggresive correction to keep it the indicator better on par with your real position.

Hi @Greenham [image: 1751202667139-4319fcfd-792e-45b3-b623-21f237e4bf05-image.png]

@Adrian-Avram, That's a pity, but kind of what I was expecting Thanks for testing!

@Corjan-Meijerink yes, because the phone's processor is so fast and I don't have a laptop. But when I'm planning with my friend on his laptop it's really handy having the waypoints to the left all the time. Especially now I'm having the issue with scrolling through the waypoints. [image: 1751145612411-1000092724.jpg]

I'd have to second that. I went out for a short run yesterday 56miles/90km with the App running on a Motorola Edge Neo 40 with a wired connection to my Africa Twin screen. No issues including a stop for Icecream. That said I did a 900 mile trip through Scotland the previous week with the same setup and version 4.3.9 and that was also trouble free.

Jetzt noch einmal getestet … Fahrmodus = Auto (1) geht direkte Route A zu B [image: 1751125640613-img_2084.png] (3) geht nicht, da kommt die Fehlermeldung bei dem Track Kurvenreich über diese lange Strecke ! [image: 1751125649862-img_2085.jpeg]

Hi @Paul-Johnson-5 All the above posts give good advice, it is just the nature of having multiple different devices that there are going to be inconsistencies in the routes due to the different routing algorithms/profiles that are used to calculate the routes. All you can do is try to constrain the routes to be as similar as possible by adding lots of points One trick I use to help identify if there is going to be an issue is in the name of the route I add  the total mileage that I believe the route should be, the mileage MRA has calculated with the Here routing. When friends load the route to their Garmin or TomTom if there is a big difference in mileage calculated then it implies it is a poorly constrained route & the navigation systems have a serious divergence somewhere in the route It is not a perfect solution & it won't catch the small deviations but it can serve as a warning something is amiss

Hi @Simon-q The issue with waypoint names is as @Marinus van Deudekom says, it is a Garmin thing the XT specifically renames points in a seemingly completely random way, it even can change the location by small amounts each time you rename the point ! I don't believe it is to do with the position of the points but more to do with the Garmin/Here database for the road names not matching or somehow conflicting with your name of the point. The Garmin tries helpfully to "correct" what it thinks is an error but is in fact deleting/corrupting hours of your work The only way round it I know of is to check the points after they are loaded to the Garmin & rename the ones that have changed back to the name you original chose. Transfering via Basecamp or such does not help, the names are changed as they are loaded onto the device

Hi @Stephane-30 I had a similar issue last year where I could not select/change the voice option, it was stuck with a nasally american accent I could see lots of other voice accent options but none of them could be selected & would stick, it always reverted to the american accent In the end to resolve the issue I had to completely uninstall the google TTS voice & reset it all up again from scratch

@Marinus-van-Deudekom Bedankt voor je reactie.

Thank you all for the help. I often take multi day rides with numerous routes fairly close together. I still think being able to join routes where you want to rather than at just the end or the beginning would be very useful.

Leuk te lezen, Ik heb een Active 4 Pro en die gaat mee in de camper of de cabrio. Net bijna 3.000km met de app o de tablet in de cabrio weggepoetst Het ging overal super! [image: 1751138677425-20250607_091403_web.jpg]