@Makro said in Spoken waypoints prevent spoken route directions: ...Besides, people should have the freedom to set route points as they like, and not have to force themselves to use the software in a way the algorithms can handle... Sorry to say this: If you buy a Garmin, you need to lern how it will work. If you buy additionally a TomTom, you need to get familiar also with its algorithm. And they are different! Why the behaviour with MyRoute-App could be different?

@Donovan-Smith that is a long A-B route, just shy of 600 miles it seems to be doing the right thing in avoiding the tolls I put similar start - end points in google maps & selected avoid tolls & the 2 systems seem to track pretty well a few small differences, the main one being how to route round the tool on the A63 at the Aire Port des Landes, only about 35 miles into the trip If you select the TomTom & Openstreetmap route algorithms you will see they also take slightly different paths but in general they are all doing similar things Remember to return the route algorithm setting to Here before you navigate

@steve-spake Your XT is on and connected to your phone? You should see that "D" icon in the top of both your screens, XT and phone.

It's always avoided

@Adrian-Avram, that could be useful info, however it contradicts @dbrooke experience... Maybe more AA/CP users can test if the fact that tracking is enabled has influence on the crashes.

@Corjan-Meijerink thank you very much for investigation. Unfortunately I did not have the same Idea to look into. I only checked the file on PC by XML reader. If it will happen again, I will inform here again... Have a good night, sleep well

I have had the same issue as well. I think it is caused by my Sync3 AA/CP headend. I have not heard it with my direct connected helmet headset.

@Con-Hennekens said in Stability problems after 4.4.0 update: but if you want to solve anything, you need to look at other possible culprits too. There are many... In my case, its MRA. This has already been decided, and now I am waiting for the next update, maybe it will fix things ...

@Arron-Watkins, you do not need to download routes for navigation. Just open your routes from the routes menu in the app. If you do what @Rob-Verhoeff said, you can even do that while offline (after an initial sync of course).

iOS 18.6. I phone 13. I haven’t tried the volume up first before connecting but from memory that would probably mean the volume is the same level for sound being treated as a music source. On my bike I can set diff volume levels for different applications via my blue tooth intercom

With your knowledge, you can figure out why this happens. But put yourself in the shoes of a person who is happy that he/she can get the route on his screen and starts riding. What do you think what happens when this person get this problem?

...and sometimes - if you search by postal address for the starting point - it will be placed in map not exactly on the road. Check in deepest zoom level and move it a bit away from home or hotel etc.

@Bouke-Ent, I must admit that despite my rich experience with MRA, I usually do A2B routes with gMaps. It has unparalleled traffic info, and does not have the full tool set when you don't need it

just go replay from support. it can be that driving navigate route as track is giving problems when it is behind. there advice is to use only route if this happens and look if it then is ok. i will try that. for me this options saves a lot of time to make route precise on here map. but if this works it is for me ok.

@Hans-Mester is dit de route die je bedoelt? https://www.myrouteapp.com/en/social/route/11904118?mode=share Deze route is ruim 3400km lang en bevat diverse overtochten met een ferry. Ik kan mij voorstellen dat MRA daar moeite mee heeft om de route van te berekenen. Waarom knip je die niet op in dagtochten?

@abowen if your in dynamic mode & set "zoom correction" to negative two, then that is as far out as the auto zoom will go on my phone which is quite a large long screen, that gives me about 15 miles, sunbury-on-thames to bagshot (M3 jct 1 - jct 3) which is way more than I need 15 miles is about 15 minutes ahead & i don't need to plan that far enough in advance [image: 1755110838464-62cd3974-7c9a-4f98-86b4-d1f99f73adab-image.png] Like @Rainer-Treichel I normally use a zoom correction setting of -0.6 that shows me about five miles ahead which is more than adequate "the app won't zoom out far enough" how far are you expecting!? the compass icon tells you what mode your in, the red arrow in the picture above shows a triangle symbol within a circle - this is dynamic mode & the triangle is pointing north in this case your position/location icon wil be to the bottom third of your screen, in my case this is the pink triangle/arrow in "top down heading up" mode your position/location icon wil be to the bottom third of your screen like this & your position/location icon will always point to the top of your screen [image: 1755112039831-c6ac6ff6-faad-4371-a465-73d8f6ecd4d0-image.png] the compass needle will always be pointing to the north/south, the needles angle/orientation will vary depending on your heading, the needles angle/orientation will vary so it always points to the north/south in "top down north up" mode your position/location icon wil be to the in the centre of your screen & your position/location icon will rotate as your heading changes the compass needle will always be pointing to the top of your screen, north is up & up is the top of the screen [image: 1755112260247-37c3d45a-0ec0-40f3-bf1b-d4d94be9df14-image.png] as far as I am aware auto zoom should definitely not be functioning in the "top down heading up" mode in this mode according to the documentation the zoom should only be set by the magnification keys + & - no auto zooming should be occuring & the map should stay at the fixed zoom level you have chosen with the + & - keys If things are zooming when your in "top down heading up" mode then something definitely seems wrong

@Con-Hennekens routs are designed well. In the beginning I had problems with shaping point placement. I have everything dialed in pretty well now. The ride i took on Sunday after the re-download, for some reason wouldn't even keep me on the "designed route" just kept trying to bring me another way.

@Marinus-van-Deudekom, we know of course that there are (quite a few) restrictions by Apple and Google, but @Achim-Kaluza complaint about crashes, not about missing features. @Achim-Kaluza, nevertheless AA/CP are quite complex protocols, many things can go wrong outside of the MRA app. @Rainer-Treichel tip about trying a cable for testing purposes is certainly not a bad one. If you have a tankbag or something, it is quite easy to do. Of crashes do not occur while using a cable, we can rule out the origin of the problem being in the MRA app. Complaining in the forum is not making things better. Did you submit a supportticket already? That could be helpful in solving the issue.

@HighPeakRider I have seen odd behaviours at the end of a trip & messages that there are problems with the log. Fortunately I have not lost any as I navigate in offline mode all logs have still been in the upload que My feeling is that the log problem is secondary to an issue of the navigation failing at the end of the trip & crashing the app. I think the root problem may be to do with the introduction of the stop navigation switch at the end of journey. The log issue never used to happen.