@Marinus-van-Deudekom, er wordt niks omgerekend, de route zal als track worden gestart in de app.

@Con-Hennekens said: Correct, that has been deprecated, since nowadays routes NOT being created on the HERE map are automatically navigated as track. A message tells that while starting the route. So there is still a check, but it is handled differently. Great, thanks. So what's the process, if any for getting the documentation sorted out? PS There are a number of differences between the documentation and the actual app in the Functional section. Seems that keeping the documentation up to date is not a priority!

I've read this whole thread about 3 times now, because I was trying to understand what the problem is, and it took me a while. As far as I know, this is how maps have always worked, digital or analogue. Take a paper map, that has north marked on it, place a compass on top of it and start rotating. The compass North will obviously not coincide with the north of the map while you look at it and from your perspective the map's north will always be up as you hold it and look at it. So how can the camera map view setting that is called North up can possible have any other meaning? That being said I agree that the suggestions people made in previous posts about the UI can only help and by that I mean having the cardinal points being shown on the compass wheel or having the traveling direction written on top or below, in typical fashion, NNW, SSE and so on.

start tracklog en tracklog automatisch pauzeren staan uit. Controleer track navigatie op fouten staat uit. De overigen staan aan.

@Stevedo-6-0 Let me refraise that. The systems used on car navigation are mostly app that require regular updates for the map material. That's flaw number one. Then the map material used is more then often wrong regarding speed limits. It mostly a system te be used for A2B routes. Never intended to be used like we use MRA. If you compaire those app to Google maps you'll soon find out that those apps are indeed crap. An app like MRA is build for navigating and all those others apps are not. The topic is about Here maps updates. Altough there's plenty to say about the updates froim Here they most certainly are a lot better then maps updaste poorly or even worse never.

@Bruno-7, Bij een route werkt er logica mbt het al of niet automatisch overslaan van een routepunt. Je zult dus altijd naar een routepunt herleidt worden (hetzij het gemiste, hetzij een volgend routepunt). Bij tracknavigatie wordt je op een min of meer logisch wijze teruggeleid naar de track. Dat kan ook ergens tussen routepunten in zijn in dat geval. Dat lijkt gunstig, maar is het zeker niet altijd. Mede omdat sommige gebruikers dit vergelijken met hoe een zumo of tomtom werkt. De MRA app heeft helaas geen "track awareness", dus die blijft je soms wat langer terugsturen naar een punt waar je niet meer naartoe wilt, ook al zit je weer op de track. Om echt verschil te ervaren, moet je het gewoon proberen denk ik

A few weeks ago I rode a route that I have done many times. on this occasion the NN did exactly as you describe here. tried to send me off and back on the motorway at almost every junction. I had 1 start point 400m away from my house and the next shaping point was located at the end of the motorway section. I did not need anymore as I know the route, it was a means of getting to the twisty toads and these two points were circa 50miles (80KM) apart. only reason I had the two initial points was to give me a rough arrival time. route as track I sent the log files to the devs, did not get an explanation, which I wasn't really looking for, the answer I received was, they would use the findings from the log files to help with updates. which was my intention when I sent the log files. curiouser and curiouser

We take all feedback serious but please, create a support ticket. Then we have an official way to communicate. Obviously audio is critical.

Allen bedankt voor de diverse zienswijze op mijn vraagstuk. Laat de ontwikkelaars adhv onze opmerkingen maar iets van maken (of niet).

Danke für den Link, Jörgen. Den Beitrag von Corjan kannte ich noch nicht, werde ihn jetzt "beobachten". .....und hoffe, dass das Problem bis zum Beginn meiner Bulgarien-Tour am 16.8. erledigt ist...

@Brian-McG, what issues. Explanation of how things works is hardly an issue. Not adhering to them could be an issue though

Is there any progress or solution available? 2 weeks ago I got a response to my ticket in the support section that a new version will be available in a week. So another week went by, my ticket was closed and the problem still persists. Any chance to downgrade to 5.0 on IOS?

Ich würde kaufen, aber kein Abo nehmen. Ich brauche das zu wenig, deswegen warte ich auf ein Angebot. Das kriege ich, dauernd, aber nur für das Abo und nicht für Lifetime

@Mike-wiruth, I think you enabled some messy track to be visible on the map? Try this: On your phone, in the main map, press the map-style button. [image: a010dd02-e51d-44ad-bc59-e3caa487c7a2-image.jpeg] Then tap the second menu option: "Routes visible on map" [image: c36bc9cb-48ae-4d30-b144-351ba252e19b-image.jpeg] If any routes are listed here, delete them by the X on the right Or click the bin symbol to delete them all at once. [image: 8c62710a-5ac2-47a8-9601-1687bea86bb9-image.jpeg]

@Pierre-c would you possibly be able to share a route where you consistently get the added time & could you check if the distance is the same at the start of the navigation as is calculated on the web planner? I agree with what @nick-carthew is saying & this is how things should work MRA does behave as such most of the time but occasionally it has glitches or edge cases so it would be good/helpful if someone could check your route

That´s why pictures help.

AA and ACP are an extra layer of complexity but they are certainly not the cause of most problems.