Incorrect calculation of the remaining mileage if the route deviates!
Unfortunately, this bug has always existed in LM4... I've reported it several times already – and I've always received good advice on what to set where and how to fix the problem, but unfortunately, none of it helped!
The problem:
If the route traveled deviates from a planned route – e.g., due to a shortcut – and is then "returned to" again, there are no more navigation announcements after this deviation, and the remaining kilometers to the destination are calculated incorrectly!
These may even be more than less...
Attached are images and gpx-files of the planned and driven routes at the "shortcut" point, as well as the log file (although I couldn't find anything there).
If there is a setting that permanently resolves this behavior for all existing and future routes, please let me know what I need to set where and how. Otherwise, it's about time to finally fix this problem!
The same question 
If it helps, I'm attaching the config.
If it helps, I'm attaching the config.
Hi Oliver,
before we start investigating the issue, please install the latest beta version from https://bit.ly/lmVersionsTest and test the problem again. Then please let us know the results. Thanks.
Hi Oliver,
before we start investigating the issue, please install the latest beta version from https://bit.ly/lmVersionsTest and test the problem again. Then please let us know the results. Thanks.
Update made. Test as soon as the weather improves... I'll report back.
Update made. Test as soon as the weather improves... I'll report back.
Hi!
Today's route worked without any problems, with a deviation of less than 1 km. However, the direction remained the same – on the "problem route," the direction reversed when I left the specified route to take a shortcut...
So I can't say yet whether the problem is really solved.
However, the route is still identical at the beginning and end of the route. LM can't distinguish which direction I'm traveling until the route (outward and return) differs. I receive both navigation announcements and the display for the return journey when traveling there. It can't be right that I have to plan a separate route each time (separate for the outward and return journeys) just so that potentially identical routes are announced/displayed correctly?!
A new feature with this beta version is that at the end of the navigation – I've reached my destination (which is also announced and displayed correctly) – the navigation doesn't end automatically (although this is set in the configuration), and I have to do it manually.
Regards
Oliver
Hi!
Today's route worked without any problems, with a deviation of less than 1 km. However, the direction remained the same – on the "problem route," the direction reversed when I left the specified route to take a shortcut...
So I can't say yet whether the problem is really solved.
However, the route is still identical at the beginning and end of the route. LM can't distinguish which direction I'm traveling until the route (outward and return) differs. I receive both navigation announcements and the display for the return journey when traveling there. It can't be right that I have to plan a separate route each time (separate for the outward and return journeys) just so that potentially identical routes are announced/displayed correctly?!
A new feature with this beta version is that at the end of the navigation – I've reached my destination (which is also announced and displayed correctly) – the navigation doesn't end automatically (although this is set in the configuration), and I have to do it manually.
Regards
Oliver
Hi,
thanks for testing the new version and reporting the endo-of-navigation problem. We have simulated it. However, we are unable to simulate the issue with route reversion after recalculation... some more testing will be needed.
Hi,
thanks for testing the new version and reporting the endo-of-navigation problem. We have simulated it. However, we are unable to simulate the issue with route reversion after recalculation... some more testing will be needed.
This time, the deviation between the route driven and the planned route was greater than 5 km, and I had to make two detours due to diversions. LM4 continued navigating without any problems upon reaching the planned route. However, the direction remained the same each time! The reported error was/is apparently only relevant when the direction reverses – regardless of whether it was a 2 km or 5 km "shortcut/detour". I'll continue to monitor this.
Due to an update, I had to restart my phone – this time, navigation ended properly upon reaching the destination. Whether the update or the reboot fixed the error… it hasn't occurred again.
For now, the ticket can be closed – if the above-mentioned error occurs again, I'll report it again.
What's still the case, however, is that if the start and destination use the same route, LM apparently can't distinguish the direction, and the directions for the outward journey are for the return journey (so instead of "turn left," it says "turn right" – which would only be correct for the return journey). As soon as the route is different, the navigation directions are correct (although the display is always correct)!
This time, the deviation between the route driven and the planned route was greater than 5 km, and I had to make two detours due to diversions. LM4 continued navigating without any problems upon reaching the planned route. However, the direction remained the same each time! The reported error was/is apparently only relevant when the direction reverses – regardless of whether it was a 2 km or 5 km "shortcut/detour". I'll continue to monitor this.
Due to an update, I had to restart my phone – this time, navigation ended properly upon reaching the destination. Whether the update or the reboot fixed the error… it hasn't occurred again.
For now, the ticket can be closed – if the above-mentioned error occurs again, I'll report it again.
What's still the case, however, is that if the start and destination use the same route, LM apparently can't distinguish the direction, and the directions for the outward journey are for the return journey (so instead of "turn left," it says "turn right" – which would only be correct for the return journey). As soon as the route is different, the navigation directions are correct (although the display is always correct)!
Hi, could you please send
Hi, could you please send
Here's an example where the first KM for the outward and return journeys are identical.
The display is correct, but the navigation system's announcement for the outward journey is for way back
Here's an example where the first KM for the outward and return journeys are identical.
The display is correct, but the navigation system's announcement for the outward journey is for way back
Replies have been locked on this page!