A to B route choice bug
-
When using a simple A to B route, several options are shown. Unfortunately whatever route is chosen the navigation always defaults to the first route shown!
-
@OGRIII
I'm assuming you mean the scenic route A->B?I just had a go, and it worked OK for me.
I tried Banbury -> Circencester, very cuvry, large height differences, and then selected the second route, which was via Burford rather than Stow-on-the-Wold.Are there any specific steps? Or maybe you could share some example start and end points (and the curvy/height options) that fail, and I'll give it another go
-
I suspect @OGRIII means that if you choose a curvy setting, that curvy setting should be the default for the next route (make the setting "sticky"). I can think of at least as many arguments against the idea, as in favor of it, and PLEASE don't make it a setting...
-
@richtea999 thanks for your help.
No I am talking about a simple route to a chosen destination - not a scenic route.
-
@Con-Hennekens thanks for your reply.
No I am talking about using the app to select an end location not a curvy or scenic route.
Usually at least three options to choose from are given in addition to the default route. Unfortunately if you select one of the options (using android auto) and drive off it defaults to the original route.
This does not happen using TomTom App or Google App only MRA seems to have this problem. -
@richtea999
Did you use your mobile phone only or were you connected to an Android Auto screen? I have noticed that Android Auto does not do exactly what the mobile app on its own does. If so I will have to try A to B route on my mobile phone only and see if that fixes the problem. -
@OGRIII said in A to B route choice bug:
@richtea999
Did you use your mobile phone only or were you connected to an Android Auto screen? I have noticed that Android Auto does not do exactly what the mobile app on its own does. If so I will have to try A to B route on my mobile phone only and see if that fixes the problem.Apols for the late reply.
On a PC, i.e web, and not via the app.
I've not tried Android Auto yet.
-
@richtea999
Txs for the reply. Although MRA is improving, at long last, it still does not work as well with Android Auto unlike TomTom phone app, which works seamlessly.
Cheers OGRIII -
On recalculation, the newest faster route is calculated.
Could be that a recalculation occurred and it immediately decided to take the other routeIt's a tradeoff between sticking to user choice and forcing back to a route you want anymore because the other is faster.
-
@Corjan-Meijerink Txs Corjan, but how do I make sure it fixes the route I choose, not the default fastest?
-
@OGRIII You can't
-
@OGRIII, To put it into perspective
: A single destination is considered as a request for the fastest (or shortest) route. Any calculation will generate just that. That's why the route can change big time when you deviate. It is by public request on this forum that this method was chosen.
@Corjan-Meijerink, I am very much in favor of how it works now, but @OGRIII has a point than when you chose a specific (non-default) one from the suggested options, it is a bit strange that it is thrown overboard at the first occasion. Maybe it is an option to start a track instead of a route when any of the non-default route options are chosen? Then it would stick to the track instead of going for the fastest recalculation. Just a thought...
-
@Con-Hennekens thanks for your reply.
I find it hard to believe that people requested to ignore the route options and to always use the default. What's the point of giving options if the system ignores them? As I said earlier the TomTom App offers alternative A to B routes. When you select a non default it takes you on that route. Furthermore as you ride the route it shows green faster alternatives en route that you can ignore or take.
This is clearly a bug in the MRA software!