@Brian-McG this is great thanks Brian. I removed all the NSO attributes from the tags (editor tool issue) and that cleared up the waypoints naming and description issues for me as well (thanks to you), but when I click to see tracklogs (I assume this is where it would be?) the track did not get imported. Based on what I understand of MRA workflow, what I am trying to achieve now is uploading the file with the track and waypoints into one route. Convert the track into a route. That gives me the shapoing points I need plus the primary waypoints for stops and photo opportunities. I would be fine uploading them as two separate files but I can't upload the waypoints into an existing route correct? [image: 1765057094402-screenshot-2025-12-06-at-4.35.47-pm-resized.jpg] If I try to import the file as a Route-Track, then the waypoints don't appear importing that way. I'm not sure why there are two different import methods. I do have some gpx files that have waypoints, routes and tracks all in the same file. [image: 1765057313796-screenshot-2025-12-06-at-4.40.43-pm-resized.jpg] Next I tried to just import the tracks by itself, convert it to a route and see if I could find a way to import those Primary 9 waypoints into this new route created from the track. No deal. It looks like you can only do an import into a new route and you can't select the location where the imported file will go to (subfolder).

@Gijs-Jonker with this solution it seems to work on active 2

501 433 gives on samsung active 2 and samsung S8 no solution. I think both android 9. on my main navigation phone ulefone x10 with android 11 it works ok. did use setting in map layers and virtual display and it seems to fix it for active 2

I understand now. And a quick test did show the waypoint name, plus the audio. And I was able to skip a waypoint. So, I think all my issues/concerns are addressed! I'm no longer afraid to use Via points Thanks again for the quick feedback. No Garmin XT2 for me - now I just have to decide on the right phone and mount

Hi, I noticed littel problem today with the Barbuttons, I think this is also based on a ESP32 and sents normal keyboard characters. Here is a little tool the check sents caharcters: https://jaxeadv.com/barbuttons/keypress-tester/

Newer Android Phone can have an option for leaving the battery on 80% under use. This also means that the power from the powersupply only is used by phone. The battery will disconnected so to speak. https://allthings.how/how-to-limit-your-androids-charging-to-80/ I use this option for a while now and i'm very pleased with the results. My phone is mounted on the bike in open air. The phone stays cool even in the hottest moments of the year. On colder moments (spring/fall), the phone is just cold in my hands.

Probably because the routing settings aren't available - most likely because you've selected "motor" as transport mode. The routes you load are maybe created for "car" and have routing settings.

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

@Con-Hennekens merci d'avoir pris le temps

Thanks Corjan, It is indeed fixed now

I must have missed this one 2 weeks ago. I have a Pixel 8 Pro and the app works really well. Have you tried to clear cache and data for the MRA app on the Android settings?

@Robert-Laudensack said in Annoying "Can't calculate route": there is one or the other thing which was clearly designed being in front of a Computer screen and not sitting on an MotorCycle I know @Corjan-Meijerink to be developing MRA in bed, in a hot tub, a hotel room and more places, but hopefully not while riding his bike. Believe me: he is a fanatic biker... in Navigation mode being able to Navigate must remain the priority I have no doubt that exactly that is the case. Once again, it would be helpful if we could see the pop-up on which you base your claims. Please add a screenshot. I prefer the old calculated rout to be shown Me too, there is a setting for that, which shows a white line indicating the original route. Also you can disable recalculation if you want to. Forgive me, but it almost looks like we are not talking about the same app...

@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. ‍

Yep - can confirm, it’s working now in portrait mode! Landscape is still an issue, but that’s caused by the keyboard that covers far too much space. However, as mentioned, I don’t care.

@Ad-l mooi! En anders kijk gerust eens naar die instellingen die ik deelde. Op een bepaald moment worden dit soort toestellen te oud inderdaad

@Stephan-21 said in Indicated route duration: @Corjan-Meijerink it had been a while, but is this something that is on the roadmap of improvement for MRA? Not sure about other users, but for me this really prphibits the use of the trip generator, becausr it is not a 5 minute difference, but 30 minutes to 45 for Some cases (the longen the route, the greater the difference) Hi Stephan, I usually don’t see such large differences, except in cases where the app starts the route with traffic checks enabled or detects a road closure on my originally planned route. Under normal conditions, the differences are about 15 minutes max.

@Corjan-Meijerink said in Centering issue: Interesting issue! Haven't seen it myself but will definitely keep an eye out. If you lock the screen while navigating (using the feature in our app, simply open the menu while navigating and it's right there) the orientation will remain fixed! Yeah I seen that lock feature, I suggested it some time ago against raindrops but forgot to use it for locking the orientation The loss of focus happens mostly after breaks and me using the phone for other stuff returning to navigation after. I am on a Oukitel WP22 as my primary Navi device and my Samsung A54 which I use as my normal phone and Navi Backup and , not Android Auto (I use that in my car). I nearly only use the dynamic mode. tapping the Compass does not solve the issue - it ried that serveral time, only quit MRA and restart solves the issue. I'll try to do a screen shot next time, but you know during a 400km day trip I am enough stressed about solving the issue instead of proper documenting it: