MRA Community Forum

Bluetooth inderdaad. Today All worked fine again.

Welcome @robert-elliot-0 You have found a great source of information to help plan your travels. MyRouteApp is a brilliant platform and there are some great tutorials and available in the Support area and on YouTube. Enjoy.

That is a cool conclusion @steve-jarrell Tread didn't mess up the 1.2 (which I always use on my XT1)? So, could you say, that it will work on the XT2 exactly the same?

Ik denk dat dat wel moet lukken, maar als je het echt zeker wilt weten kan je je licht eens opsteken op het bmwgsforum, genoeg mensen die je zo een panklaar antwoord kunnen geven.(of even de zoekfunctie gebruiken)

@Bouke-Ent said: it would be strange that a developer would use 2 differant SDK's If you read again, you'll notice that that is not what I said i do not believe it is a design choice. i believe it is a good developer choice. Of course, it's the developer that decides what to design. So I see no difference.

@travellexxie : das ist die beste Lösung und entspricht fast einem klassischen Navi und funktioniert einwandfrei.!! Das Netz im Ausland wird zwar hoch gelobt aber es gibt doch viele Löcher im Netz gerade in den Bergen … also gut das MRA 100% Offline kann.

@Ian-Teasdale said: I have to agree that the font size of some elements is way too small. I use AA on a Honda NT1100 and with the new version, quickly glancing at the screen makes reading the speed and distance to next manoeuvre easy – no issues there. I also don’t face any difficulties with the distance to the subsequent manoeuvre but it seems others do. However, the distance to the next waypoint is too small. I have to lean forward quite a bit to read it which I think makes this unsafe. I like this new feature, but it’s current implementation is far from ideal. Similarly with the altitude. These are good and worthwhile features to have and we know about the issues with screen “real estate” and competing demands for clarity and more features, but having them when they can’t be read easily or safely strikes me as being an area for development. The exit number on the roundabout symbol is currently just too small to be of any use. [image: 1781009760560-screendump-2026-06-09-12_17_13.png] Yes, I agree with you there. The key information regarding the next turn needs to be easy and clear to read. To achieve this, the font size in that area needs to be increased. On a mobile phone, the distance to the next turn—and the roundabout exit number you mentioned—are far too small. I’m just concerned that the MyRoute team won’t make any changes based on the feedback of only a few users. The majority seems satisfied with the current setup; at least, that’s my impression based on previous comments from some users.

Thank you all for your replies! I do not use satellite mode to navigate, but I do enjoy creating routes using the various maps available in MRA. Satellite map is definitely one of them. MRA is a great program, and it is not a big deal, but it does occasionally bother me (just a little ).

@D-Griffin said: Is there something I'm missing? Did you miss or missinterpreted a navigation instruction near wp4 by anny chance? If not, then perhaps place some extra wp's! Off topic: Is there even the slightest bit of satisfaction in riding more than 80 km with nothing but straight roads the entire way?

The Chigee never sends the signals to apps about the wonder wheel movement, so neither MRA nor any other app can react to you twisting the wheel. I’m not sure about Android Auto, but that’s how CarPlay works. It only communicates to the apps which buttons you’ve pressed/touched on the CarPlay screen itself. The Chigee uses the wheel to move the selection box to the button you want to “press”, then nudging the wheel “touches” the highlighted button. All MRA sees is that you “touched” that onscreen button. It never sees that you rotated the wheel.

I did some further play. Manually Start WP6 - End WP7 - ok Start WP7 - End WP8 - ok Start WP8 - End WP9 - ok Start WP9 - End WP10 - ok Start WP9 - End WP11 - Not ok, error It seems that the distance from the current location doesn't matter—only the length of the detour. The detour must therefore be longer than 30 km.

The road block was visible in the map, the route info said there was a route violation due to the road block and the app kept telling me about the roadblock. The thing it did not do was not plan a route through the roadblock or provide an alternative.

the logs: go to your avatar in the app, scroll down and press long on the version number

You’re right though, but I didn’t meant it as complaint.

Stuur een ticket naar de service en misschien dat zij je kunnen helpen

To be honest, I’ve never geven it any thought at all. I know it’s like that. Maybe it can be altérée when the webplanner gets its major overhaal this yeat

@Nick-Carthew You're very welcome. Here's the link to my second post regarding the gpx 1.1 and 1.2 file formats that I mentioned above. I tried to add it to my first post but I guess I waited too long to edit it! Steve

@KevN1k-0 If you plan your routes using the mobile app you will definitely be using the planning map from HERE.