I also experience the problem described. But has never bothered me personally, because I have my smartphone on the handlebars.
From tomorrow I’m on the road with new or different smartphone, let’s see how it behaves with it.
Das beschriebene Problem tritt bei mir auch auf. Hat mich persönlich aber nie gestört, weil ich mein Smartphone am Lenker habe.
Ab morgen bin ich mit neuem bzw. anderem Smartphone unterwegs, mal schauen wie es sich damit verhält.
Automatic rerouting is set. The navigation is okay, only the spoken text doesn’t fit. Look at the example. If I drive along the red arrow, it says, in 100m to the right, then in 200m to the right, in 300m to the right, etc. But it doesn’t say: “please turn around”. Only when I turn back are the announcements okay again.
As a reminder: I carry the smartphone in my jacket pocket and cannot see the display, only hear the announcement via bluetooth in the helmet.
Es ist automatisches rerouting eingestellt. Das Navigieren ist in ordnung, nur der gesprochene Text passt nicht. Schaue auf das beispiel. Wenn ich am roten Pfeil entlang fahre, heißt es, in 100m rechts, dann in 200m rechts, in 300 m rechts usw. Aber es sagt nicht: “bitte wenden”. Erst wenn ich umkehre, sind die Ansagen wieder in Ordnung.
Zur Erinnerung: Ich trage das Smartphone in der Jackentasche und kann das Display nicht sehen, sondern nur die Ansage über bluetooth im Helm hören.
If you drive along the red arrow, than a rerouting would happen.
After new route is calculated, the announcement would be:
“In 100m turn right”.
But this announcement only fits, if you drive in the green direction.
If you continue driving in the red direction then another recalculation happens:
Then the resulting announcement would be:
“In 200m turn right”.
And so on, until eventually a new route towards the red direction would be found.
Thanks for the information, now it seems more clear what could happen.
The (re)routing requests contain also the location’s heading (coming from GPS).
Navigation gets the (re)routing response and auto-announces the 1st instruction.
Navigation continues. If user keeps being off route then more reroutings happen.
A Yes or No does not mean you have to answer any question or have a talk to you phone.
It means, or you do indeed have a turn maneuver now, or you ignore and simply continue. Roger ?
By the way…as in the video by the block method. I found the result VERY usefull …you do not ?
Do these belong together? Yes definitely. Optimise both or none.
Both optimization adjustments are so desirable.
No turn instructions for the reverse direction if the distance indication is still increasing.
Avoid the large flow of then irrelevant instructions by quickly enforcing an alternative.
Not convinced ? Diversion Güglingen.
Here app: The passage through Pfaffenhofen is blocked. However, not in osm.
If so, Kurviger recalculation would respond more alertly to this.
The motorcyclist keeps driving and so clearly does not want to turn back.
Video now including sound. Listen, don’t watch, phone in backpack. Usefull ?
This quickly becomes a very annoying TTS nuisance.
Now you don’t get misleading voice guidence any more, when riding away from route.
But you may still get many “recalculating route” messages in a row.
This doesn’t seem to prevent graphhopper Kurviger (online) from calculating a route in the opposite direction of current heading.
Here is a simple route example
If you keep heading away from route (as in screenshot) you get one “recalculating route” message after the other.