The same thing happened to me 2 days ago... same exact behavior, first I displayed the screen as yours, you could no longer see the cursor position, then after closing the app several times, the cursor came back, but the position was wrong, it was hundreds of meters behind, in all this the voice directions were correct... maybe it is the case that the developers take a look at this post, I would not want it to be a problem of the new update... I always have the phone near the CarPlay on the handlebars, I doubt there were any disconnections... and the phone signal was constant...

@Fred-Gilbert, You placed your topic in the APP section, does that mean that you were planning in the in-app planner? I think you would be doing yourself a favor to do these kinds of changes on the web-planner in the browser on a large screen. There you can set a transparency to the route line, which makes it easier to see loops. As far as I know there is no single other planner dat replaces waypoints when you change direction. Intelligence is to avoid placing waypoints on one-way lanes in the planning phase (yes, that is not always possible, I know). I know from experience that navigating a reversed route is really no problem, if correctly reviewed.

Not so long ago I had a similar problem. The final solution was restarting my phone. After that no problem any-more! It was not MRA this time that caused the problem but just my phone.

I don't doubt that it's complicated. I also didn't mean to "blame", should it have come across like this, stating that Google Maps doesn't show this phenomenon, but rather point out that it is possible to somehow avoid this problem (i.e., there's hope). I do, however, wonder why (for my setup at least) the severity/frequency of the spinning has increased to a level where it occurs at practically every stop. Something must have changed.

Thanks I guess

@Corjan-Meijerink It is the Android 13 (Go edition). The app will install, but will not start up. On my primary phone using the standard Android Version 13 everything works great with the new MRA update. Something about the "Go Edition" does not seem compatible. Just curious if anyone else has reported this quirk. Thanks

@Fred-Gilbert Suggestion: Check your location settings. They may have been accidentally disabled for the app?

@Javi-Cabrerizo I recommend resetting your Pixel 9 to factory settings and setting everything up again. The MRA app runs perfectly on my Pixel 9.

@Con-Hennekens I do use Intercom on my bike but I repeat: the same Problem exist with my carradio (Bluetooth Connection) and with a jabra Bluetooth headphone.

...a gpx file can contain: a track with dedicated trackpoints list itema route with min 2 dedicated routepoints list itemseveral Points of Interest (waypoints) But the general structure in MRA is, to load (by a gpx file) a route into the folder structure for route a track into the folder structure for tracks You can't mix them up! If the gpx file contains both (route and track), you need to upload it twice - one time the route into route folder structure, second time the track into track folder structure. The internal upload logic of MRA picks the needed information automatically out of the gpx file. But for tracks, only 2 of the trackpoints (start- and endpoint) will be made visibly on the map. For routes, all the existing routepoints will be made visible on the map (max 200). In MRA you can open the route and add to display additionally one or more tracks. But this isn't possible in the App (for navigation).

@Con-Hennekens I am using MRA for years and 85'000km. I don't want to turn of recalculation, because I need that feature. its hard to make screenshots when you are on a trip, also this situations add a lot of stress and "fighting the system" is enough distraction I'll try to make notes next time.

@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 merci d'avoir pris le temps

Thanks Corjan, It is indeed fixed now