MRA Community Forum

@Andrew said in Always says first exit at roundabout regardless of actual exit shown: I have a problem where the phone shows correct exit at roundabout but the AAuto screen always shows just a left or right turn for roundabouts. I see this also - Google pixel 8 MRA 4.1.2, Android Auto via Carpuride 702

I don't thimk it is simply a screen issue. For high contrast = readability in sunlight a proper choice of colors is much more important. A retired photographer recommended me, switch your color tables to greyscale and then choose for landscapes etc. and roads just the opposite colors. Michelin overlay colors are a good example.

@Bouke-Ent I am with you, some users have houndrets of route in several files and need only a few for the next vacation, week, whatever. But it is as it is, some prefer this, some not and MRA trust in their way, which is sometimes a bit different to usual common practices in computer based handling. So what, the advantages of MRA predominate up to now, even with some frustration coming up and unexpected reactions. Yeterday I am back home and made my standard test and I had a lot of problems with verbal announcements of the POIs with 335. Informations are announced by random. No preannouncement but confirmation. preannouncement of POI1 but confirmation „You reached no 1“ when I reached the Sp 2, nothing was called for WP 5. An i folow the roules for announcemts and before 4.3. it works on the same route. I am meanwhile also frustrated to write about this and stop here. Regard to your concern My solution for easy access to my routes I want to use next session I create a folder „AA routes for use“ which is by alphabetic order the first file on the screen. Those routes I need will be copied in this folder with the same name and the appendix -copy- they get automatically. The originals stays in their folder and when the session is over it is easy to delete only the copies.

@Corjan-Meijerink wil je svp nog kijken naar het te voet afleggen van de routes want daar is het probleem niet opgelost.

@Con-Hennekens het “probleem” waar ik in het openingsbericht tegenaan loop is nog niet opgelost helaas. De route maak ik in de OSM kaartlaag en dan zonder de navigatie te starten kan ik die zonder herberekening in de app volgen.

@Brian-McG Hi Brian, you didn't derail anything imho. Just pointing out a shortcoming you've encountered is fine and part of the discussion. Thanks for comment and I agree that any controller that works for the user is way better than a gloved finger and much more safe.

@Manzo91 said in Stuttering menu after 4.4.0 update ?: we need to use the 4.3.9 version until next update I am fine with that. Also I never had any battery drain issues while using the app in version 4.3.9, so version 4.4.0 is not really a must have for me.

I use Acapela for Android. Does the same. Available in the offical Play Store but not without costs. Although the costs are a fixed one time price per voice. A few Euro's

@Con-Hennekens Directly via speaker in the phone, there is no problem

@Jörgen das ist mir bekannt, es ging mir um das verschiedene Verhalten. Aber ich habe das öfters, das bei mir bei Ampeln am Rad gedreht wird. ‍

@Con-Hennekens Sad to hear that! This week we will research more

@Dikke-Wim geweldig!

@Jack-van-Tilburg, Kan de OSM community alvast beginnen met het in kaart brengen van de maan? Alvast bedankt! Let op de slider: dit is nog niet 1/3 van alle mogelijkheden

@Hans-van-de-Ven-MRA-Master Ja, dank je wel ............

@Guzzist I'm sure that the 1.2 export works good on an XT done it a lot of times

@paul69 thanks for showing. Mine looks similar, but without key

@Rob-Veerman not good

@Martin-Wilcke looks good and as designed!