After Firmware Update for XXL, "Plan Route" Mode Defaults to "Address"

[shthompson]

As long as I've had this device, when I tap "Plan Route" it brings up a menus of choices: Home, Favorites, Address, etc.

Now that I've installed the new update, when I tap "Plan Route" it takes me directly into the address option, and I have to hit "Back" to get to the other options in the route planning menu. Is there any way to alter this new default behavior?

 

[Andy_P]

That's a new one on me.
A lot of people are getting confused by the new "Favourite destinations" screen that you can opt to see when you select "Navigate to..." on the Go models, but that's not available on my XL.

Are you really seeing the normal "Navigate to Address" page with City Centre / Street and House number / Postcode / Crossing or intersection options straight away?

I'm running the latest build on my XL LIVE IQ and the 'Navigate to...' works just as it always has.

 

[Andy_P]

Or is it THIS small issue?
Any way for "Navigate To" to go where it used to go?

 

[shthompson]

Or is it THIS small issue?
Any way for "Navigate To" to go where it used to go?

That description looks familiar. I'll see if setting the state resolves the issue the next time I'm in the car.

 

[canderson]

-1 here.
My 720 and 740 both take me to the normal screen when I hit "Navigate to" or "Prepare route A>B". I have the usual options available.

 

[dhn]

With my 540 last night after the app update I first selected Prepare Route. The next screen did ask to confirm the country (Canada) before moving to the normal screen to complete the destination information.

Next Navigate to.... and the next screen was the normal screen.

 

[canderson]

Mine asked me to confirm "Colorado" the first time, but that's normal after the firmware update that we all received.

 

[shthompson]

Or is it THIS small issue?
Any way for "Navigate To" to go where it used to go?

This resolved the "issue." This is my first firmware update since I've owned it. I bought it refurbished from a third party. So I wasn't aware until now that this is standard behavior after a firmware update.

 

[canderson]

It didn't used to be 'normal' after a firmware update, but it seems to be so with this latest one.