Hi Con,
Thanks for this clarification. So it seems I should have either signed onto Starbucks's WiFi or switched to offline before resuming.
I'll know for the next time.
It would great if the developers could somehow make the switch to off-line mode automatically when asked to resume an A to B route if there's no Internet rather than the routing just not working.
@Vincent-Curren said in Could Not Calculate Route (after stop):
Am I right to conclude that if I use the "stop navigate" function when I (for instance) go to a coffee shop, when I resume navigation, the app needs a good Internet connection to reload the route and it's not just pulling the route I want to resume from memory?
A quick test shows me that this is indeed the case. BUT if you switch to offline navigation in the settings, it WILL be able to calculate. Hence my suggestion the dev to try offline before pushing the message.
@Doug-Robinson said in Could Not Calculate Route (after stop):
based on the picture above, it appears you are doing an A to B route and not a pre-planned route with waypoints. I believe you do need Internet because it uses an online map and not the downloaded Here maps.
The app definitely uses the offline HERE maps for offline calculations. It does seem to have trouble to start an A to B route offline through the resume option though, if that destination was set during online use. I fail to see why. But if you close that option and search for the destination again, it has no problem calculating a A to B route offline. And a destination chosen in offline mode also works fine when resumed.
This quirk is good to know. I'll try resuming in offline mode next time I'm in this situation.
Thanks,
Vinnie