Sync 3 version number on2018 vehicles

[mvan231]

1 hour ago, Michael David said:

 

I re-read the FAQ and if you read it carefully it is clear that it is the Waze + AppLink combination that requires CarPlay to be disabled, not Waze itself, so although I could complain that the information was not clear I can not say it was wrong. My mistake.

 

I do not know if that functionality is in the Sync 3 system in my Transit chassis but I will find out the next time I try this. The chassis is 2018 but I am not sure that they upgraded the van chassis as quickly as the cars. The same phone and cable combination that worked in a 2018 Fusion did not work in my 2018 Transit but perhaps all of that will be taken care of by using CarPlay and not AppLink, so thank you for clarifying that for me.

 

I tried to do all of this with an iPad instead of an iPhone (the phone is my wife's and I really did not want to use it for navigation as she uses it for calls when we are on the road) but I did not have much luck with the iPad. It is not gps enabled so all location information is only an estimate based on internet usage and it does not offer CarPlay anyway.

CarPlay gets location and speed info from the vehicle. The transit could possibly need an update to the sync software to enable CarPlay. Is it not showing anything when you plug the device in?

[Multitask]

I use the Google Maps most of the time, if I see a lot of traffic, I switch to Waze to see what is up (although Google Maps seems to be learning info from Waze as they are both owned by Google)

 

If I switch back to Google Maps, I still get the Waze voice from time to time.... ( I laugh because I got it to the Voices from Sesame street....  C is for Careful... also for Cookie)

[Michael David]

12 hours ago, asteele said:

It would only work with a very recent Sync3 update (build 18093 from memory), and you would also need to disable CarPlay *AND* remove all memory of previously CarPlay used/known devices from Sync3 too, so that meant going into the CarPlay list of devices in Sync3 and deleting them all. Very odd that it would be so sensitive that disabling CarPlay would not be enough to make this work - you have to delete the known devices as well.

 

You would then connect your phone by cable to Sync3 and launch Waze on the phone.

If you were very lucky, a Waze icon would appear in Sync3 as an icon on the bottom menu - and you could possibly enjoy a SLOW version of Waze.

 

This is exactly what I have found when trying to use my wife's iPhone 8 Plus. If I remove the phone from the Sync 3 list of paired devices and start from scratch each time I usually (and only usually) get Waze to show up on the screen. I have been trying to understand what I was doing wrong as it was way too much trouble to go through that process every single time I restarted the RV to continue on a trip.

 

12 hours ago, asteele said:

I use Waze every day, but as an app within Android Auto - it's fast and brilliant.

 

This only works for me with my older (and no longer SIM-ed) Samsung S7 Edge. My new Samsung S10 Plus will not work at all and to even get it close to working I have to go through a process similar to what I used with my wife's iPhone - remove the device as a known bluetooth contact, open the Apps link under Android setup on the phone, clear the memory on both Android Auto and Waze, reboot the phone and then go through the pairing and usb connection. I then get the Android Auto screen, but often I also get a "phone not responding" message so it is all for naught. My S7, however, works without issue with Android Auto and I have begun to wonder if there might be some usb issue. The S7 is a usb-2 connection via a micro usb cable and the S10 is a usb-3 connection via a usb-c cable.

 

This is all on a Ford Transit 350 HD chassis which has a small RV built on it. The Transit is a 2018 model, but was produced late in 2017 (December) and that is why I wonder about the usb connection. I have tried my new phone on Ford cars, both 2018 and 2019, and it works properly with those Sync 3 systems. I only have trouble with the Sync 3 system in my RV. I have thought it might be some OS setting on the phone, but then I don't see why it works on the cars but not on the Transit chassis.

 

12 hours ago, asteele said:

My wife uses Waze every day as an app within Apple CarPay.

 

I am going to try this the next trip we take, which may be tomorrow if the weather is OK. I had thought that if this worked I might try getting a used iPad mini (with SIM card) to use with the Sync 3 system) but the iPads do not have CarPlay installed on them and Apple tells me I can not add it, so I guess that option is also out. Perhaps some older Android tablet has has a SIM card and hence is gps enabled.

 

12 hours ago, asteele said:

A feature of the Waze on CarPlay was that the reported speed on the Waze screen was inaccurate... you need build 19149 to address that - but if you dont yet have that build, still use Waze anyway - as it is brilliant.

 

According to Ford I am up to date, but I only have 18093 and 19149 is not available in the US (to the best of my knowledge). I have seen links to the later version on some of the forums, but I am reluctant to install a version of the software that is not currently available in the US.

 

12 hours ago, asteele said:

I hope this summary helps

 

It most certainly did help. Thank you very much. I still have this issue with the newer phones but the idea of using CarPlay to run Waze is a big help.

Edited July 23, 2019 by Michael David