Could Not Calculate Route (after stop)

[Vincent Curren]

Did a quick check and didn't see any reports like this...

V 4.0.2 -203 running on Google Pixel 6, Android 13 Gold lifetime plan with navigation. Location permission turned on, Offline navigation off.

Ocean City, MD to Columbia, MD - my home address which I have saved as a favorite.

I set up the route from my current location in Ocean City using the navigate screen, selecting "home" from my favorites. It set up the route just fine - the route looked good and started out running just fine.

Started the trip and stopped for coffee outside of Salisbury, MD. Chose "Stop Navigation / Confirm" and went in for coffee. Ten minutes later, I was back in the car and selected "Navigate" under "Resume Navigation. I got a blank screen where the map should be. Waited a few minutes, still a blank screen. Exited the program and re-entered, still a blank screen. Tried in offline mode: no help (the map for Maryland is downloaded to the phone.) Exited the program, reboot the phone, entered the program, still the blank screen. I noticed that I had only one bar of 5g signal, so I left it on the blank screen, got back on the road, thinking maybe it would recover with a better signal. Nope: eventually the phone went into sleep mode.

45 minutes later, I stopped for fuel. Lots of signal now, 5 bars of 5g. I rebooted the phone, opened Navigation, and tried to set up a route from my current location to home. I got this dreaded screen:

I switched to Google Maps.

Anything I should be doing differently?

Thanks,

Vinnie

[RetiredWingMan]

@Vincent-Curren Did you download the maps for MD?

[Vincent Curren]

@Doug-Robinson: Yes, sure did. I have MRA installed on two Android phones, and this has happened once on the other phone too, so I wonder if there's some kind of bug, maybe related to wireless service coming and going,

Vinnie

[Con Hennekens]

@Vincent-Curren, The map you first see when you open the program is NOT the downloaded HERE map, but a OSM map that cannot be downloaded offline. If that map does not load, it is an indication that you have no (or a bad?) internet connection. Even with that blank map, you can select an offline route from the download folder, or resume the route you previously abandoned if you get that question. For an offline route to be able to calculate, you need to have set the toggle for offline navigation to enabled. You can enter the menu to do that even without leaving the resume question.

@Corjan-Meijerink: We have a nice auto-switch between online-offline during navigation. Can that be extended to the start of a route? It is a bit funny that the app throws this generic message (which does not mention the internet connection at all) while it is capable of starting the route offline. I feel it would be logical, in case of not being able to calculate a route online, that it should try that offline before it throws a message.

[Dave J 0]

@Con-Hennekens Totally agree that it would be logical for the start of navigation for the start of the route/resumption of route for the auto-offline to switch on when poor or no internet available. Had the same problem happen to me several times (more on my Android) and it is one aspect that continues to frustrate.

[Vincent Curren]

@Con-Hennekens Thanks for the quick response. 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?

If that understanding is correct, it seems that I shouldn't use the stop navigate function unless I'm sure I'm going to have a good internet when I want to resume.

However, there >was< very good Internet at my second stop (5 bars of 5G connectivity), when I tried to create a route home from my existing location at that second stop. That's when I got the error message I posted above. So I think there may also be something else going on as well.

Thanks,

Vinnie
Thanks,

Vinnie

[RetiredWingMan]

@Vincent-Curren 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.

[Con Hennekens]

@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.

[Vincent Curren]

@Doug-Robinson: Right; that's what I was doing. It was an A to B route. If I had known about this quirk, I could have logged onto the WiFi in Starbucks first and THEN resumed. Live and learn!

Thanks for your quick response, BTW. I've been away from the site for a few days so am just responding now.

Vinnie

@Vincent-Curren 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.

[Vincent Curren]

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