Google maps issue... Fix #10

[jlferg0509]

Has anyone seen this? I've noticed over that past month that when I use Google Maps, on the driver dash, it shows the battery (estimated) range, BUT the destination range is always zero (0) miles. Now in Google maps, it shows the trip time, destination mileage, estimated arrival time and estimated soc.

Look at the attached photo and zoom in on the arrows.

Sponsored

 

[chrislittle]

Has anyone seen this? I've noticed over that past month that when I use Google Maps, on the driver dash, it shows the battery (estimated) range, BUT the destination range is always zero (0) miles. Now in Google maps, it shows the trip time, destination mileage, estimated arrival time and estimated soc.

Look at the attached photo and zoom in on the arrows.

Yes it's definitely some type of bug as I have the same issue

 

[B177y]

A couple other other threads about the same issue:

https://www.f150lightningforum.com/forum/threads/distance-to-destination-on-dash-0kms.34351/

https://www.f150lightningforum.com/...ce-to-destination-always-0.33968/#post-636357

 

[Calvin H-C]

Just did a road trip this past weekend and I noticed this as well.

 

[Jfennell55]

And in route preconditioning is not working because of that bug only works in ford nav

 

[RickLightning]

Uninstall Google Maps updates.
Turn off automatic updates.

 

[fhteagle]

Tried Google Maps 26.09.06.something yesterday. Still has the distance to waypoint 0 miles bug.

I have to go back to 25.03.01 to get a distance to waypoint on the DIC.

 

[Markip]

Google pixel had a android auto update and distance to destination started working properly again. It appears it was a Google maps update that caused it but an android auto update fixed the communication issue

 

[TaxmanHog]

Google pixel had a android auto update and distance to destination started working properly again. It appears it was a Google maps update that caused it but an android auto update fixed the communication issue

Wow, I wondered if the could have been the case, I submitted similar trouble reports for each app when this problem turned up, what version number of AA are you running?

This is what I'm running at the moment, where the defect is still a problem.

 

[Markip]

I went back to non Beata google maps that was not working for me before the up date and that version works with the new AA update also works now.

 

[TaxmanHog]

I went back to non Beata google maps that was not working for me before the up date and that version works with the new AA update also works now.

Awesome, I'm looking forward to the newer version 16.3.660834 coming to my corner if the interwebs.

 

[TaxmanHog]

Google pixel had a android auto update and distance to destination started working properly again. It appears it was a Google maps update that caused it but an android auto update fixed the communication issue

Awesome, I'm looking forward to the newer version 16.3.660834 coming to my corner if the interwebs.

Just got the latest version of Android Auto, I'll test in the morning.

 

[priceb]

I just got the Android Auto update, 16.3.660834. Combined with the Google Maps update I received earlier in the week, 26.10.01.877073638, everything is finally working correctly.

 

[Markip]

That is excellent news.

 

[Firn]

Look, I submitted the feedback on Friday. The fix just rolled out. I’m not saying there’s a direct correlation between my Bug Report and the Google Dev Team’s sudden productivity... but I’ll be accepting thank-you gifts in the form of Bourbon or 3D printer filament. You’re welcome, everyone.

Sponsored