New Beta! (v4.0.6)

[Con Hennekens]

@Arno-0 and @Dave-J-0, no what I meant is if this happens after having started the route from an active wifi connection, after you switch to an active gsm data connection. You know, when you start a route at home still connected to wifi, and your phone switches to gsm data when you leave your driveway. I am suspecting the app still tries to use DNS servers from the connection it started on. Or something similar.

[Arno 0]

@Con-Hennekens That could maybe be the cause of this problem. I use the phone only for navigation on my motorbike and I think that WiFi was switched off when I left home in the morning. At work, I remember, I turned it on to update the maps and think it was still active when I went home in the afternoon. I will test again what happens when WiFi is not active at all next week.

[Arno 0]

Today, I tested again the same route to and from the Office. I took care that I only used my mobile connection to both start and drive the route. The test was successful and I did not encounter any problems with constantly switching between online and offline modes and route calculations etc. So it seems important to not use different internet connections for starting and driving your routes.

[Con Hennekens]

@Arno-0, Thank you! I know it is asking a lot, but it would be great to see if this is really structural. So if you have the chance, repeat the test a few times, to deduct if it is really only happening when you started the route on wifi. I am doing the same thing, and it certainly looks that way.

[Marinus van Deudekom]

@Con-Hennekens I've done the same thing. When starting a route being connected to my home WiFi network the same problems occur.
Your explanation could be the cause of the problem. When starting a route in gsm mode no problems. It seems to me that the problem only occurs when starting an A to B route and not with a planned trip
I' ve posted a couple times with the same problem
Hope the team can find a solution

[Arno 0]

@Marinus-van-Deudekom I only checked it for planned routes and not for A-B routing. You say "it seems to me" but did you really test it or is it only a thought?

[Con Hennekens]

@Marinus-van-Deudekom said in New Beta! (v4.0.6):

It seems to me that the problem only occurs when starting an A to B route and not with a planned trip

Well, I am experiencing this with planned routes too. Direct routes I have not tried So it definitely is not limited to direct routes.

[Marinus van Deudekom]

@Arno-0 with a planned route I didn’t have the problem. With A B routes I had problems. Since You and @Con-Hennekens both had the problems with a planned route we’re Back to square one with thinking it has something to do with starting with WiFi connections.
Still hoping for a fix by thé team

[Arno 0]

@Marinus-van-Deudekom I will test next week with an A-B route. Start the route with a WiFi connection and then see what happens when I’m driving the rout using my mobile connection.

[Con Hennekens]

@Marinus-van-Deudekom, I don't see why we are back to square one. If a problem arises when switching networks, why would that only affect direct-routes or only multi-waypoints routes? In both cases, in online mode, data traffic will be generated by the app. So we are definitely not back to square one

[Con Hennekens]

@Arno-0 said in New Beta! (v4.0.6):

@Marinus-van-Deudekom I will test next week with an A-B route. Start the route with a WiFi connection and then see what happens when I’m driving the rout using my mobile connection.

If you do that, and nothing happens, try a detour, forcing the app to recalculate. Do that on online mode of course. Thank for your cooperation.

[Marinus van Deudekom]

@Con-Hennekens what I meant was that we’re Closer to vinding the sollution

[Marinus van Deudekom]

@Con-Hennekens tried that but that wasn’t thé answer. Will keep on trying