Indicated Speed Error on Waze

[TicTocTach]

So a few weeks ago, I noticed that the speed shown on the Waze app was way high compared to my speedometer - it had been spot on until I noticed the error, but has been a little over 14% high ever since. Running Waze in any other vehicle shows the speed to be spot on again, so it seems to be either a Sync 3 thing or a CarPlay thing.

IMG_2354 by clair_davis, on Flickr

IMG_2352 by clair_davis, on Flickr

In the photos (professional driver, closed course, etc.), I have the cruise set @ 70, but Waze says 80. I just updated Sync 3 to the latest version for 2018+nav, but nothing changed with regard to the error.

Anybody else noticing this type of error?

Thanks,

Clair

Sponsored

 

[Dusten]

when you run waze stand alone, is the issue still there?

 

[eddison]

It is a known issue with Sync 3. A newer release/update is said to fix or at least improve it.

 

[TicTocTach]

when you run waze stand alone, is the issue still there?

This I can't verify - I haven't checked it unplugged or unconnected from CarPlay since I noticed the problem a few weeks ago. I'll check it on the drive tomorrow. That said, I can't say why it popped up at all, either. I had problems with Waze working with CarPlay at all early on and had to drive disconnected for it to work, but an update with Waze fixed that. I wonder if that might still be related to what is going on, and I haven't checked on the Waze forums yet, either.

It is a known issue with Sync 3. A newer release/update is said to fix or at least improve it.

I just updated Sync 3 to 18093 yesterday - no change. Previous version was 17276, and I'm not aware of any other Sync updates since I bought the car in May '18. I'll keep an eye out for the next update and see how that does now that I've got a handle on the process.

 

[Cathul]

Current build version of SYNC3 is 19149, at least in Europe. Users are reporting that this version solves the error.

 

[TicTocTach]

Current build version of SYNC3 is 19149, at least in Europe. Users are reporting that this version solves the error.

For 2018 or 2019 cars? 18093 is what downloads from the Ford website for 2018 cars. I understand that 2019's run on Sync 3.3, and the two versions will stay separate.

 

[eddison]

For 2018 or 2019 cars? 18093 is what downloads from the Ford website for 2018 cars. I understand that 2019's run on Sync 3.3, and the two versions will stay separate.

2018's. I would assume the 19149 build will be released in the US soon since it's out in the EU.

 

[Cathul]

Yes, it's for cars up to 2018 (3.0_Production with build number 19149). After that they already have 3.2 at least, if not already on 3.3.

 

[TicTocTach]

Confirmed on the drive in that Waze reports correctly on its own... hopefully the new update will be out here soon.

 

[Dusten]

That pretty much settles that there is some comms error for waze through car play

 

[kirk533]

I don't think it's just Waze. I have the same thing happen with any GPS based speed app when usb is connected. Don't even need to have CarPlay active.

 

[TicTocTach]

I don't think it's just Waze. I have the same thing happen with any GPS based speed app when usb is connected. Don't even need to have CarPlay active.

Interesting... I haven’t tried any other nav or gps-dependent apps to see. I don’t mess with the Ford nav, I wonder if it also suffers?

 

[StangTime]

Interesting... I haven’t tried any other nav or gps-dependent apps to see. I don’t mess with the Ford nav, I wonder if it also suffers?

Ford NAV will indicate only the speed limit for the street you are driving on. Having current speed on the map is redundant.

 

[FreedomPenguin]

Mine worked perfectly til a month or two ago, instead of being 65 in 65, its like 80 in a 65, and its completely inaccurate, it USED to be accurate, but now way off. Its Waze itself, my phone. has to be, because it just shows it wrong

 

[TicTocTach]

Mine worked perfectly til a month or two ago, instead of being 65 in 65, its like 80 in a 65, and its completely inaccurate, it USED to be accurate, but now way off. Its Waze itself, my phone. has to be, because it just shows it wrong

So are you not running Waze through Carplay / Sync? Your experience is exactly like mine, down to the timing.

Sponsored