@ValléeDesFées great!

@Jörgen : ja wollte nur sicher gehen das der Garmin Kollege die gleich Route daraus bekommt …

@Con-Hennekens said in In app route/track multiple options/alternatives not working: It's structural. It seems like you're right. Of the four different options, only the first two are different. Options two, three, and four are always exactly the same as each other! You old sleuth...

@Jörgen Agreed - long press for a log works on iPhone, but on iPad it doesn't.

@Calibos, Running the app in Android versions 9 and newer should be no problem. But iirc there has been identified a certain graphical chipset that is not compatible with the rendering engine used in the SDK. I don't have details however. I am very curious where you found older versions of the Android app though.

@Corjan-Meijerink, Great! (as always) Can you disclose what this feature is going to look like?

@Rob-Verhoeff Ok, thanks.

The map issue I reported earlier that always leads to a crash in Car Mode showing CarPlay and phone screenshots: [image: 1711089147266-img_0262.png] [image: 1711089170710-img_0263.png] Whilst the position and track are correct, the turn directions are completely wrong and have been stuck on the first 2 turns from starting the trip about 1 mile earlier having done 2 further turns to be on the current road/position. And in Motorcycle Mode for Car Play and phone all is correct: [image: 1711089215770-img_0264.png] [image: 1711089229603-img_0265.png]

@Herko-ter-Horst But all of this is easily solvable. Let the developer give us a table of words/phrases that need to be translated. Croatian/Bosnian: Left = Lijevo Right = Desno In = Nakon ...and so on. Then, regardless of the selected language on the phone, or whether it is supported as main, if there is a translation, it will be pronounced correctly. After all, we are talking about approximately a few dozen phrases, if that many.

I have the same problem on my Samsung Tab A6. Reinstalling the app does unfortunately not help.

Vandaag ook een wit scherm momentje gehad rondom de laatste stap om een route te starten op m’n iPhone 15. Geforceerd afsluiten verhielp het niet… De app leek traag te werken… van binnen begon al zachtjes een ongeduldig stemmetje tegen me te praten en toen bedacht ik mij ineens dat de wifi wel eens het probleem kon zijn. Net buiten de achtertuin heb ik nog 2 streepjes wifi signaal op m’n iPhone, maar qua data werkt het daar vaker niet dan wel… De oplossing was dus simpel: wifi uit en via 5G werd het scherm weer keurig gevuld met de kaart. Denk dat dit los staat van de witte scherm problemen die momenteel voorbij komen op Android, maar wilde het toch even delen.

Goedemiddag, Ik wil graag melden dat ook na de installatie van de nieuwe versie 4.1.0 - 286, ik nog steeds een zwart scherm ervaar op mijn telefoon op de plek waar normaal de kaart zou moeten verschijnen. Alle andere functies van MRA werken perfect. Mijn telefoon is een Huawei P20 Lite met het Android besturingssysteem. Ik heb het logbestand doorgemaild naar CorJan. Mochten jullie meer informatie nodig hebben, laat het me dan alsjeblieft weten. Ik hoop dat jullie in staat zijn om dit probleem op te lossen. Bedankt voor jullie inzet en ga vooral zo door.

@Peter-Schiefer said in Navigatie in de file in vergelijking met Apple kaarten: Hallo Con, meintest Du mich oder Rob. Ich habe nichts von Waze geschrieben You are right, I meant to reply to @Rob-de-Weijze indeed. Waze was just meant as an example (of A2B navigation). @Rob-Verhoeff said in Navigatie in de file in vergelijking met Apple kaarten: I mainly use the apps for what they're good at: MRA for driving routes and Waze for time-critical navigation. I think many people do it like that

@Corjan-Meijerink afterwards 286 On mobile via tracklogs , edit, tick on the route, add moment

@Jeremy-Palmer said in Round in a Loop.: So to go via a WPT (which is the reason WPTs are plotted), I’m guessing I have to be sure it’s on the correct side of the road. Is that correct? I am not sure if you would be unable to "hit" a waypoint if it is on the other side of a splitted road. But what I do know is that you want to check the WPs after you planned a route, to ensure that no loops are draw while navigating. You want to avoid that mess... @Jeremy-Palmer said in Round in a Loop.: You have to stop, take gloves off, etc, etc. Skipping a WP is done by tap and hold the top right icon in your navigation screen (only when actually navigating a multi WP route). It is wise to: have a phone-screen that accepts gloved fingers have gloves that mimic fingertips (these are quite common nowadays) In my gloves I have stitched a few ups and downs of stainless steel threads on the fingertips. That works beautifully

@Gos-Kuus fijn om te horen! Die instellingen werken inderdaad (nog) niet in CarPlay. Omdat CarPlay zo anders is qua vormgeving willen we nog kijken wat we wel en niet daar kunnen overnemen.

@Jörgen said in Unable to recalculate... and again and again.: Same Problem Yesterday. Start cury Road to Home, left the track and IT could Not recalculate. [image: 1709975036251-screenshot_20240308-155402.png] Strange Route anyway. Same days before, even 20m from original Route, No calculation. Everything was ok, Signal GPS etc. [image: 1709974965827-screenshot_20240302-145902.png] zoets had ik vaak als ik vanuit thuis met wifi wegreed, door bijv 5 min eerder je wifi uit te zetten op je telefoon en dus met data gebruik van je abonnement weg te rijden heb ik dit probleem niet meer gehad.

@Peter-Schiefer, what you are forgetting is that scenic routes take a lot more waypoints to define the route unambiguously then highway travel from Köln to Bordeaux. Especially if you want to make the route equal over all maps.