Sorry, I'm a bit confused. @Lenny-O, are you asking about the "start screen" that @Jörgen mentioned, which looks quite similar to the screen in planning mode? Or are you referring to the design while navigating, as shown in @Hubert-Thoring's post?

I have had a similar effect (but not with MyRoute) when having the phone at ~ 45° (not vertical, not horizontal). The direction to the center of the earth was changing, hesitating between to directions.

Da sehe ich ganz klar die MRA App als Verursacher. In allen anderen Apps funktioniert die Tastatur in allen Ansichten. Wie zb jetzt gerade wo ich diese Zeilen in Safari schreibe , mit großem Zoomfaktor. . Der Fehler existiert seit Version 26.01 und auch in der aktuellen 26.1

@Corjan-Meijerink, Indeed, the 1 second pause did seem to help, but it is just not enough, for my specific case I mean. You absolutely cannot introduce a longer pause everyone not having this problem My theory, not being held back by any knowledge, is that some AA devices simply do not honour the "wants priority" command, but listen to audio (voice) itself and decide (too late) to duck for themselves. the behavior differs depending on if you are listening to the car radio or to spotify. Yes, but that is quite logical. When playing spotify (or anything else) from your phone, the media channel is continuously open. The phone ducks spotify, and not AA.

I am pretty sure this is has been resolved! Update 5.0.1 will provide the solution. We will test it now internally and roll out a beta as soon as possible. Also trying to resolve the "disappearing keyboard" issue

If you contact support, they can solve this for you

MRA App V5-426 Samsung Galaxy S10e - Android 12 - default Samsung keyboard I have the disappearing keyboard problem, but not the map covering the menu list problem. When tapping on the text entry field the keyboard only shows for a fraction of a second and then disappears. The screen now displays the menu list, but with a map that only has the relocate to current location button, and that button does not function when pressed. The only way to get back to the normal functioning map with the appropriate buttons is to close and restart the app. Deleting and reinstalling the MRA App, rebooting the phone and installing and using the Google Gboard keyboard did not help. This problem does not occur when editing and adding a point to a route that is currently being navigated. In that situation the keyboard stays displayed and performs as expected.

@JP-d firstly have you tried routing with the option no tolls disabled, does it effect/prevent the issue occurring? it is only a guess on my part that this is the issue

@Andre-Trudeau as you said with another keyboard attached via the USB the Bluetooth keyboard when connecting and disconnecting has no affect and works as it should

Thanks a lot - So simple! Once again, I was unable to see beyond the edge of the screen...

Dank u ga ik testen

@Marinus-van-Deudekom I did and Thork is taking care of it Fabulous support on their part. I was just asking because I have the issue of MRA restarting on bluetooth keyboard connect/disconnect on multiple devices. No worries. I'll wait to get my replacement 865X and re-test. Cheers!

Hallo,ich klinke mich hier mal mit ein. Habe folgendes Problem.Ich starte eine Navigation und alles läuft wie es sollte auf dem AA Gerät.Unterbricht man die Tour und fährt dann weiter dann läuft die Karte mit aber man bekommt keine Abbiege Hinweise.Die Anzeigen auf der linken Displayhälfte sind eingefrohren.Auch ein Neustart der Route ist nicht mehr möglich.Hat das schon mal jemand gehabt.

@Peter-Zehentreiter I have set the MRA app to English, but the problem persists. In the meantime, I have checked the codes sent by WunderLINQ using a key press tester. Everything is correct here, including the long left press. Yesterday, I created a support ticket – I'm sure they will be able to help me. Thanks for the tips! Best regards, Peter

I expect a fix rather soon for that issue!

I had this and changing to the native android keyboard works, it needs attention though.

@white.mouse, een ticket maken is natuurlijk vooral zinvol als dit bij herhaling gebeurt. Elk incidentje melden lijkt me niet echt nodig, want je had het op dat moment al correct opgelost. Zorg dat je na zo'n incident kunt aangeven wat het tijdstip was (maak bijvoorbeeld een screenshot, met de telefoon tijd in beeld), en zorg dat je ook meteen een logfile opslaat (lang drukken op het versienummer onderaan je profiel pagina in de app. Ik weet niet precies, maar zo'n logfile heeft naar ik meen alleen gegevens van de laatste 24 uur of zo. Dat zijn zo'n beetje de belangrijkste gegevens om te melden bij het maken van een ticket, en support gaat daar geheid naar vragen.

@Corjan-Meijerink said in Error message 'Could not calculate route' when one is shown on the map #bug: From my side I can let you know that the issue is fixed. @Corjan-Meijerink That's great. Thanks for the quick response.