Update: fixed in 2.2.51 UK search for: CT161JA (Dover ferry port), add to places LL651DR (Holyhead ferry port), add to places
Set: LL651DR as departure CT161JA as destination
Route Info: Routing mode: Fastest Road restrictions: Off Small Local Road, Other Road Route Setup: Set Off: Toll Road, Charge Road and Congestion Charge
No, it is not enough. And I know that it is very frustrating when others say "it is working for me", especially when it is the only answer. But Oldie also specified what he did.
And yes: it is crucial to know whether you are the only one or that others have that same issue.
And I say the same: The route is not found but the application does not crash for me.
You also mentioned above:
Routing mode: Fastest Road restrictions: Off Small Local Road, Other Road Route Setup: Set Off: Toll Road, Charge Road and Congestion Charge
I tried your settings and I tried every combination of your settings: still no crash.
I also tried the
As you encounter it on 2 devices I assume it is really a bug and "somewhere" in you settings and a setting which has not been mentioned yet, OR it is another application on both your devices that might interfere.
And 1 minute later I found what is happening. With your settings:
departure CT16 1JA
destination LL65 1DR
Menu -> Tools -> Calculate Route ==> No route found, but no crash either
Menu -> Route Info -> Itinerary (2nd tab) -> Calculate Route ==> CRASH
I guess the others also did the calculation from the Tools menu instead of the Route Info menu.
That I do understand. Not the crash, should it just not return "Route not found" as in Itinerary: Simulate. Instead of crashing/closing navigator free?
Happens every time when I do: Route info: Itinerary: Calculate route: CT16 1JA to LL65 1DR (UK) Not certain crash is crash? Looks like it. popup window: "Navigator is gestopt" (Navigator has stopped). Marshmallow 6.0.1 message? pressing OK: Navigator closes
When I use: Route info: Routing Points: Simulate: pop-up: Calculate Route pop-up Window: Warning: "Route not found" pressing OK does not close Navigator
Simulate catches: "Route not found", Calculate route does not. Samsung SM-T810 (gts210wifixx) 9.7 inches. Happens with Map renderer Software and Hardware What else can I provide? Test? I have time to test this.
I understand you can't replicate. Here this happens every time, is not random, every time in this situation. There must be away that you can get more information from my part: log, ... OSM UK date version 44-201606290. both are amoled
@Tomas: I myself occasionally encounter crashes when a new version is installed. These crashes no longer occur when I have rebooted my phone. Maybe this should be a standard remark in replies.
@Jan_Gruuthuuse: Have you already rebooted your phone after having installed the new navigator?
yes, standard practice power down and restart. Rebooting does not make a difference in this case. my opinion: is the way how the route not found is handled. Route Info: Routing points: simulate: route not found, app does not close Route Info: Itinerary: calculate: route not found not showing on screen, app closes. Have you tried: departure: CT16 1JA to destination: LL65 1DR (UK)
1. with starting point as per your screenshot it routes, but if you set departure before the roundabout then route is not found, even if I enable all road categories - in OSM it says Allowed access Customers, that may be the problem, it does not specify vehicles
2. crash I cannot reproduce and cannot comment on log extract, but log did continue, so I do not think that bold line is the cause - we have to wait for programers to look at it
I have no crash for the route from the screenshot. As with @tomas there is no route found starting before the roundabout (why not found?). Latest UK OSM maps, latest beta of Navigator, Galaxy Tab4 8.
@oldie: I have the issue with 2 different devices: - Samsung SL-G903F(s5neoltexx) Lollipop MR (5.1.1) - Galaxy Tab S2 - SM-T810, Marshmallow (6.0.1), ARMv7-A Booth with latest UK OSM maps, latest beta of Navigator. Navigator free should show the window "route not found" as it does when you simulate the route and not close all together. That the route is not found is another issue. It is like you're saying it works for me and @tomas and that's enough?
chattiewoman: "Edit: no I do it always from itinerary with function show route on map, as this recalculates too" This is grayed out here? update: this works only after calculate route.