@Tore-Teigene Jeg vet ikke om det hjelper, men prøv å tømme appens hurtigminne. Jeg hadde også noen merkelige problemer her om dagen, og de ble alle løst med det. Ik weet niet of het helpt, maar probeer eens het cache geheugen van de app leeg te maken. IK had laatst ook wat vreemde problemen en die zijn daarmee allemaal opgelost.

Google 'helpfully' tries to save app data and restore it on a re-install. If you have some poor data (say something that's not compatible across new versions) uninstalling & reinstalling doesn't always solve the problem. Try clearing the MRA app data rather than uninstalling it. You can do that with a long press -> press the 'i' for App Information -> Storage -> Clear data -> Delete. Then restart the app. With your fingers crossed.

Also good to take into account: follow the line does not work offline. So in the mountains it's no use

"problem" is solved by lowering the tilt value thank you

@Rakesh-Rao Its a known error/bug/flaw and I have nothing to add at Corjans post. I believe there is a update coming that might offer some improvements. One advice I can give you, try to use a cable instead of a wireless charger. A cable can reach higher watts then a wireless charger (depends on the phone and charger and other components).

@Mangelschots My personal experience: it happens sometimes, not all the time. When it does happen, I have noticed that the phone display is stuck too, and the AA screen is reflecting what the phone has. To get going again, I turn the AA screen off, reboot the phone (just closing the MRA app isn't enough) then restart MRA and turn on the AA display. I suppose that clearing memory and cache without rebooting may be enough but, given that I am stopped on the side of the road when trying to fix this, I just do the reboot. Vinnie

@henry-van-den-belt ik vermoed dat dit een gegenereerde scenic (bochtige) route is? Dan is de waarschuwing omdat HERE niet zeker weet of je hier kan rijden. Je kan deze waarschuwing uitzetten onder de navigatie instellingen > functioneel.

@Con-Hennekens Tatsächlich gefunden, danke!

Similar to what I uncounted on my Android device? https://forum.myrouteapp.com/topic/7875/no-map

@Mart-van-Walderveen Je bent goed bezig Mart. Ik heb ook dezelfde weg gevolgd als jij maar kwam, voor mij, gelukkig al eerder tot de conclusie dat MRA veel gebruiksvriendelijker is EN een stuk beter, meer 2024, stabieler. Zeker nu de web interface ook nog een serieuze update krijgt gaat het helemaal goed komen. Is alles nu perfect, helaas nog niet maar het gaat goedkomen. Wanneer ook het serieuze stroomprobleem alsgevolg van de Here kaarten kan worden opgelost is het tijd geworden om mijn XT te verruilen voor een serieus goede smartphone met hele goede afleesbaarheid, dan heb ik het minimaal over een Samsung S23 Ultra of beter (die heeft al een scherm van 1650 nits) Tot die tijd blijf ik lekker positief mee testen in de Beta omgeving om onze Devs van positieve feedback te voorzien

@LE-DIZES-Freddy ik heb nu na de update hetzelfde probleem in de auto. Ik begin aan een bugje te denken.

@Thomas-Neumeyer, see my reply here: https://forum.myrouteapp.com/post/55811 Please don't double post, thank you.

@Cookie-On-Tour said in Position on map and other pleasant things...: Then I set to avoid gravel roads, a nice message appears, that the route could not avoid the route into the gravel road, so far so good. However, while on the gravel road the message about the route violation pops up repeatedly. This is somehow unnecessary. The first message about route violation is okay and I accept, but while on the gravel road, I know I am on the gravel road, and I know that the route could not be done without using the gravel road. The annoying thing is that after a few hundred meters the violation warning comes again... and again... and again - yes, it is a long gravel road and plenty warning messages to click away during the ride. Question, I just found a setting where the (I) Information says "search for route violations" - is this setting just to turn off the displayed warning for a violation like gravel roads, or will the app start to route via gravel roads, if I try to avoid them in general?

Probeerde je 's avonds laat te plannen? Dan komt het misschien omdat er dan geen boten varen?

@Jörgen said in Zoom Apple CarPlay: @Oliver-a Not correct, there is a zoom function. Tap on the icon with the 4 arrows and then you get a + and - for zoom in / out. The thing is, that zoom won’t stick. When you exit the overview and go back to navigation the zoom level resets. https://forum.myrouteapp.com/topic/7747/making-carplay-zooming-more-effective?_=1728422286469 https://forum.myrouteapp.com/topic/8081/carplay-unit-zoom-love-mra-but-this-drives-me-nuts?_=1728422348886

@infoevertkuiken-nl Ik maakte gisteren precies hetzelfde mee. Had een mooie lange route gefabriceerd en bij de eerste 100 meter ging het al anders dan verwacht. Hij begon al aan de terugweg terwijl ik net op weg was. Ik wist de route wel uit mijn hoofd en reed verder in de hoop dat MRA het wel op zou pikken verderop, maar helaas. Opnieuw opgestart en uiteindelijk werkte het wel. Maar ik heb nog niet vaak meegemaakt dat het allemaal werkt zoals ik het zou verwachten. Te veel opties misschien? En daardoor te veel kans op onverwachte wendingen?

@Adventurer86276 said in Statement regarding battery usage: despite the thread here talking about HERE being the culprit, Scenic did not have this problem. HERE offers multiple developer platforms. Scenic was probably using an older one. The old MRA "previous" app also did not suffer from powerdrain, despite using HERE maps. HERE's own current WeGo app though, suffers from the same powerdrain, and is built upon the same SDK as the Navigation Next app. So, it is not simply by choice of the map-provider, but of the SDKs they offer to developers.

We had a great ride in Asturias and Galicia. Wore out a set of tires!! My issues with the navigation and roundabouts was similar to yours I think. Certainly a minority of the time. I am not certain I can come up with the exact locations but I will see what I can do. What I did notice was the number of the exit to take did not match the graphic at times. The graphic was pretty much always correct. So, like you say, it may be a matter of counting/not counting some smaller paths that may, or may not, have been considered exits. I found it more of an issue on the bike than in the car as I rely more on the audible instructions on the bike. In the car I had a good look at the graphic as I approached the roundabouts so I had a picture of where to go. Overall, I was happy with the way the app performed. The issues I encountered are certainly not enough for me to give up on it.

@Peter-kinver In that case, will be improved in the upcoming update