@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

@ATLast said in Route displayed white on white at change of direction: For this post for example: https://forum.myrouteapp.com/topic/7806/recalculation-of-the-route-does-not-point-to-final-destination?_=1727629803997 only a member of the development team can answer because only they know how the program works. And they didn't. There was no guessing in that threat (not by me anyway). I think you got an accurate answer, devs know that so why should they step in? Usually when I am guessing I will say so, and even then it is usually an educated guess. If I was incorrect, I am man enough to admit it and I learned something new. You should be more open to forum members, you might learn something.

@Peter-Schiefer, they ARE looking into competitors, but that does not mean they will be making a clone of them. I will not go any further in this senseless discussion with you. I suggest you move on to Scenic.

@Tom-Grzelinski said in 2024 Alpine trip - MRA problems, observations and suggestions…: I cannot see anywhere in the App to switch on/off seasonal closures. Is that an App setting, or just a HERE map setting on the route planner? The seasonal closures is a "planner only" setting. You will find it in the app too, but only in the planner (route options). If you feel you are wrongly lead around a road because of false seasonal closures, you can only switch off "traffic aware route calculation". That should do the trick. Please tell me where I can change miles to km in the App interface. The setting for units is in Menu - Profile icon - Distance notation (or similar wording, just under privacy settings). If you are not on the latest public, you might need to update

@Makro said in Route calculated via blocked road: But I could say the same about offline maps in general I don't completely agree with you. Data such as road closures is temporary or short-lived. Roads — especially the roads that we (motorcyclists) enjoy riding on — don't change that often. I'm not talking about new residential areas popping up like mushrooms. But we don't want to be seen there anyway

@Nick-Carthew Once again thank you I've also watched a few videos and I'm getting the hang of it all i.e route v,s track etc

I have found a solution for this if anyone else is having the same issue. I downloaded my route to my iphone (GPX 1.1)and then opened it with MRA on the phone and the skipped waypoints remained in place. It seems if you use the sync option it does not recognise skipped waypoints.[image: 1727076039534-whatsapp-image-2024-09-23-at-08.20.04_83243d72.jpg]

Hi, as I wrote it is tested with a iPhone and compared with the other Navi App in the Apple Universe. In this framework the power consumption is very high. In the Android Universe it's might be different but that not the point for this post. It doesn't make sense to optimize a iPhone for a single App. It should work out of the box on a similar level. As a toureguide I don't have time to fiddle arround with the navi. It must function reliably.