@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

@Frank-51 Es hilft auch hier einiges an Infos zu lesen Link zum Handbuch

I was out again today using Android Auto and this time I completed my route without the phone overheating. It was just a degree or two F cooler than last time when my phone shut down. But this time, I changed the USB charging port I was using to one that was limited to 2 amps instead of using a fast-charging port. Along with keeping the phone display off, this was enough to keep my Pixel 6 Pro charged - in fact, it actually gained a little charge during the trip. The phone was still warm, but not nearly as hot as it was when I used the fast-charging port. So, one suggestion for fellow riders who are having an overheating issue is to avoid using a fast-charging port. Kind of obvious, I know, but it did not occur to me before today. Vinnie

Ik merk zelf ook nog wel eens issues. Wat mij ook opvalt is dat ik maar 1 van de 2 gesproken instructies krijg (instelling staat op 2) Moet ik wel zeggen, ik hou er met het plannen niet echt rekening mee. Ik heb er mee leren leven en kijk toch regelmatig op het scherm omdat die boven mijn tellers zit. Als ik met zijn tweeën rij kan ik er ook geen gebruik van maken omdat dan de intercom aanstaat.

We do not support all languages - something I wish to add soon!

@Con-Hennekens Thanks Con. In the end I used the trip's recommended app (Guibo), mainly because it was pre-supplied with maps, it used tracks and OSM, and so there was little to be gained by using MRA. Guibo doesn't cope well if you accidentally leave the track either - it's up to you to correct your navigation. And guess what - Guibo ran the battery dry after half a day just using a track. It's not just MRA that has battery problems! Luckily, I had anticipated this and took a power bank on holiday, as you do. Lastly, I can recommend the north Adriatica coast (Venice -> Istria / Poreč) as a lovely area to cycle. Ice cream, seafood, quiet roads and cycle tracks everywhere.

@ATLast There is a solution: Set a goal, like to choose a curve Track is created in the app Track save from V4.3.x possible Open route lab in the app Under Routes, search for the route track Edit route track Then "As route" spokes that generates WP on the route Route corresponds to the track Choose route now in the Navi App Start route and go Recommendation: WP automatically skips off WP skips at the top right of the display, press longer, then you keep the power and decide for yourself. WP for diversions simply press the next suitable longer and it fits again because until there is recalculated. VG Es gibt eine Lösung: Ziel festlegen, gerne kurvenreich wählen Track wird in der App erstellt Track speichern ab V4.3.x möglich Routenlabor in der App öffne Unter Routen den Routen-Track suchen Route-Track bearbeiten Dann „Als Route“ Speichen das erzeugt WP auf der Route Route entspricht dem Track Route jetzt in der Navi App wählen Route starten und los Empfelung: WP automatisch überspringt Aus WP überspringt am Display oben rechts länger drücken nutzen dann behält man die Macht und entscheidet selbst. WP bei Umleitungen einfach den nächst passenden länger drücken und schon passt es wieder weil bis dort neu berechnet wird. VG Info comparison: [image: 1727857074499-img_8512.jpeg] (A to B) choose from left to right 1.) = Route 2.-4.) = Track You should know that Info Abgleich: (A zu B) wähle von links nach rechts 1.) = Route 2.-4.) = Track Das sollte man wissen Beispiel Track aus 4.) Aus Kurvenreich. [image: 1727856535975-img_8510.png] Danach das Ergebnis [image: 1727856557184-img_8511.png]

@Marinus-van-Deudekom, Er staan nog wel een paar andere puntjes open bij HERE denk ik

@Jörgen Sorry @Jörgen that was meant to be for @Peter-Schiefer