This is fixed in the upcoming update

Forgot to add this was while usingCarplay.

That's the fun part of this issue, it's extremely device / environment / charger dependant We (as app) would not be performing as well if everyone had this issue. If everyone had this issue, it would have been easier to solve as well That said, a lot of my time lately has gone into improving the battery usage and the results are getting there. Yes, I know we've said that more often in the past year (but minor improvements were also already made).

Ok, thanks. I think that was a one-time thing.

Thanks. Let me play with it, and I will get back to you.

Is there any more help with this problem. With higher temperatures now it's making it almost unuseable.

@Con-Hennekens @Jörg-VMS-e.V. @Reinhard-32 Das Teilen aus einer App an eine andere App ist nicht immer fehlerfrei, das kann an so vielen fremden Dingen liegen was auch außerhalb der MRA liegt. Eine saubere App Übergabe aus der App ist nach meiner Erfahrung die Datei als GPX auf dem Handy zwischen speichern und dann aus MRA dann diese importieren. Das ist der beste Weg um Fehler zu vermeiden. Auch aus MRA über WhatsApp geteilte GPX Dateien an Freunde, bitte nicht direkt aus WhatsApp an die nächste App teilen besser erst aus WhatsApp diese Datei auf dem Handy speichern dann aus der z.B. BMW-CRA von dort importieren. So werden die Daten sauber erkannt und auch alles übernommen. VG ——- Sharing from one app to another app is not always error-free, this can be due to so many foreign things that are also outside the MRA. A clean app transfer from the app is according to my experience the file as GPX on the mobile phone between saving and then from MRA then import it. This is the best way to avoid mistakes. Also from MRA via WhatsApp shared GPX files to friends, please do not share directly from WhatsApp to the next app better first from WhatsApp save this file on the mobile phone then import from the e.g. BMW-CRA from there. In this way, the data is recognized cleanly and everything is taken over. VG

That's because I fixed it in that version

Thanks, I will check soon.

@Drabslab Long time no see, welcome back

@Corjan-Meijerink The OSM applies to both selection of OSM cards [image: 1747593096290-img_1266.png] [image: 1747593292407-img_1269.jpeg]

@CD130 Update 391 is on the way

@M-Schrijver ik heb dat gevoel maar of dat klopt weet ik niet. had vandaag op de terugweg geen zin in onduidelijke route lijn en heb even alternatieve app gebruikt naast mijn xt. hopelijk word dit opgelost want het is net als het volgen van witte track lijn erg lastig.

@Gary-Clark : Also the route with the 6 WP was wonderful to drive me Carplay, the symbol to skip WP was also available and could have been used. I'm thrilled with how good it looks. So have fun with it.

@white-mouse said in Latest release kills battery: conclusion; wireless charging is possible but using a cable is better. That is definitely correct! Charging wirelessly has a maximum of 15W, of which sometimes more than half gets lost due to incorrect placement, or distances created by cases and things like that. That is really no comparison to cabled charging. Even with cabled charging many things have influence, but then more hardware related. Cable quality, sustained charging protocols by your charger and phone etc.

Probleem is over enkele ogenblikken opgelost!