Unable to recalculate... and again and again.
-
Did some touring today with the 266 version
At this moment 14:30 27x is not available yet.I had some interesting experiences.
- The app was directing me on a parallel road which is closed for cars and motorcycle. (Roundtour based calculation)
- Avoiding this I went on the 80km road. But then the app started complaining: can not recalculate.
- Due to some lag in location on screen, I missed a turn. Here too, the app started with lots of 'cannot recalculate' messages . It did not adjust the route. On my gut feeling I did some turns in a vilage and was able to return to the route (without performing a u-turn). I had an A-B route created with very curvy...
- In all I found that once you stray from the created route the recalculation was off or non existing..
Grtz
Edwin@Edwin_M I had a similar experience with v266 on a straight A to B route. Went off route and it took a very long time to recalculate. I was getting voice instructions while the recalculate was in progress.
When I started the Ato B route I was given a choice of three routes. I chose one. After the recalculate a different route was planned.
-
Hello,
I can confirm such a phenomenon also with version 4.1.0-276.
On a trip from A to B that was calculated before the trip, I have to leave the route at short notice. This meant that no recalculation of the route was possible and displayed. When I reached the actual route again and continued on it, the route could be calculated again and the message disappeared. GPS signal was available and offline maps too, so a recalculation would have been possible. -
Hello,
I can confirm such a phenomenon also with version 4.1.0-276.
On a trip from A to B that was calculated before the trip, I have to leave the route at short notice. This meant that no recalculation of the route was possible and displayed. When I reached the actual route again and continued on it, the route could be calculated again and the message disappeared. GPS signal was available and offline maps too, so a recalculation would have been possible.@Marschel had this happen to me too yesterday. Exactly the same with being off route and receiving the 'can not calculate' banner until I was back on the planned route. More testing tomorrow.
-
I find that when following a curvy A to B route (track), if you deviate from the track, the app sometimes has a lot of trouble recalculating. This is with downloaded maps and offline operation. I also find that the app is overly aggressive (in my opinion) with trying to get you back on track. At times it will try to send you backwards rather than route you to the closest point on the track.
-
@RetiredWingMan
Hello,
In this case, my route from A to B was planned without any curves, just a straight route on the fastest route, because I wanted to get home through the city. -
Can people experiencing this problem regularly, check if they left home or work starting the app in wifi conditions, after which the phone switches to cell network when this problem occurs? I have seen this behaviour a lot on my previous phone. I am guessing that something goes wrong after switching between different networks. The internet-availability test in the app succeeds, but somehow the service cannot be reached. In my case this problem ONLY occurred while online navigating (even with downloaded maps, because the calculation in that case is still done online. A force close followed by a restart and resume fixes it (network conditions are re-initialised?).
Another thing I read not long ago, is that the DuckDuck Go app seems to block certain outgoing traffic. Is that something you use?
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
Can people experiencing this problem regularly, check if they left home or work starting the app in wifi conditions, after which the phone switches to cell network when this problem occurs? I have seen this behaviour a lot on my previous phone. I am guessing that something goes wrong after switching between different networks. The internet-availability test in the app succeeds, but somehow the service cannot be reached. In my case this problem ONLY occurred while online navigating (even with downloaded maps, because the calculation in that case is still done online. A force close followed by a restart and resume fixes it (network conditions are re-initialised?).
Another thing I read not long ago, is that the DuckDuck Go app seems to block certain outgoing traffic. Is that something you use?
@Con-Hennekens none of the above in my case
-
@Con-Hennekens
For me too, the phone was only online the whole time via phone data traffic. -
@Con-Hennekens None of the above for me too. Using 4.1.0-276 with Android 14 on Pixel 6 Pro. I was out on a route today and skipped Point 3 well in advance of reaching the point and was online at that time - tracklog. All going well until I decided to go past Point 4 to see what would happen. I am offline at this point (unlike the other day where the same problem happened) and the 'cannot calculate' starts - video of the problem.
Turning around and heading back to Point 4, the problem continues as I approach Point 4 until I am back on the planned route after Point 4 - video.
Note that in both videos whether heading away from or to Point 4, the distance and turn indications do not change also:
@Corjan-Meijerink, I have sent you the log file from my device just in case it helps.
-
Can people experiencing this problem regularly, check if they left home or work starting the app in wifi conditions, after which the phone switches to cell network when this problem occurs? I have seen this behaviour a lot on my previous phone. I am guessing that something goes wrong after switching between different networks. The internet-availability test in the app succeeds, but somehow the service cannot be reached. In my case this problem ONLY occurred while online navigating (even with downloaded maps, because the calculation in that case is still done online. A force close followed by a restart and resume fixes it (network conditions are re-initialised?).
Another thing I read not long ago, is that the DuckDuck Go app seems to block certain outgoing traffic. Is that something you use?
@Con-Hennekens my most recent was not from home so no wifi Internet and I was in offline mode.
-
Same Problem Yesterday. Start cury Road to Home, left the track and IT could Not recalculate.
Strange Route anyway.
Same days before, even 20m from original Route, No calculation. Everything was ok, Signal GPS etc.
Hardware
iPhone 12 pro (iOS 17.0.2)
Oukitel RT3 (Andr. 12)
Samsung Galaxy XCover 4 (Andr. 9 Pie)
Wireless CarPlay mit (Elebest C650)
Wired CarPlay (SEAT Arona - 2021)
For more information, click here -
What travelmode are you using when this occurs?
-
What travelmode are you using when this occurs?
@Corjan-Meijerink Motorcycle travel mode was selected on both occasions I have seen this. One for a route and one for an A to B.
-
What travelmode are you using when this occurs?
@Corjan-Meijerink same for me, motorcycle mode.
-
@Corjan-Meijerink same for me, motorcycle mode.
-
-
@Corjan-Meijerink
Hello Corjan,
I'll test it on the drive home tomorrow and report back. -
@Corjan-Meijerink
Hello Corjan, I set the travel mode to car and drove the same route again and left the route at the same point. I did this again at a second point. Both times the route was recalculated very quickly without the error message "Route calculation not possible". The error then occurred again when I changed the travel mode to motorcycle. -
@Corjan-Meijerink
Hello Corjan, I set the travel mode to car and drove the same route again and left the route at the same point. I did this again at a second point. Both times the route was recalculated very quickly without the error message "Route calculation not possible". The error then occurred again when I changed the travel mode to motorcycle.@Marschel Excellent feedback! I will release an updated beta in a bit (and announce so) which will solve the issue
-
@Corjan-Meijerink sorry I can not test before weekend.
