Sync 3 version number on2018 vehicles

[Michael David]

I found out, much to my surprise, that different vehicles seem to have different versions of Sync 3 installed, even if on the same year vehicle. I had assumed that any 2018 or 2019 Ford vehicle with Sync 3 would have the same version number or, if not, that there would be updates available to bring them all to the same version number. Since the Sync 3 software only involves interfacing with external devices (I think) I don't see why different vehicles would have different versions. However I found that the Sync 3 system on my 2018 Transit (which is the chassis for a small RV) will not link to my Samsung S10 Plus while the 2018 Fusion at the dealer's lot had not problem with the same phone. Apparently they are different versions and builds.

 

Given that, I was wondering what build numbers people had on their 2018 Ford vehicles. I am trying to find out how far out of "current" my Transit is. I have installed the latest update for it, given what is available on the Ford web page, but I don't know how out of current it is. My version is 3.0 and my build number is18093.

 

 

[Multitask]

18093 would be the highest that the Ford site will give you... there are later versions out there, that I would call beta ... 

 

I'm currently running 19119 that I downloaded from somewhere, but it's not a 'in public' version

 

It took Ford about a year to go from the 17xxx to the 18xxx, so maybe sometime this year they will do 19xxx

[Michael David]

If all of the Sync 3 versions are the same build number, then I don't see why they act differently. I am not questioning what you are saying - I'm sure you are right - it is just that I would have thought that they would all act identically if they were at the same software level. I guess it could be the hardware on the system and any related firmware associated with that hardware.

 

I am just trying to make sense out of why my S10+ works on a 2018 Fusion but not on a 2018 Transit when they both are running Sync 3 with the same version. But then it would not be the first time that I was left puzzled. ?

 

Thanks for the response.

 

 

[asteele]

You are right, they should both work the same.

 

You could try a factory reset on the problem vehicle, and do make sure you have the same cable in both too - as many a Sync3 user has been unstuck by a cable that charged OK but didn't otherwise work correctly. There are some settings about enabling/disabling CarPlay and Android Auto too.

 

From memory there was a hardware change on the USB port interface module - so some older models couldn't use Apple CarPlay unless they paid for a USB port upgrade.  I don't recall this being an issue for Android Auto users - but I could be wrong.

 

 

[Michael David]

For a couple of days I spent hours trying different approaches to try to get the phone working with Sync 3. One of those involved doing a Master Reset on the Sync 3 system, another involved clearing the data from the Android Auto app and others involved trying pretty much every usb-c cable I had. I uninstalled and reinstalled Android Auto and Waze. I shut down and restarted the phone. None of that worked. I then spent an hour making sure the Android Auto settings on my S10 Plus were the same as those on the S7 Edge, but that did not help either.

 

The one really annoying thing (well, all of this is annoying but the one thing that is most annoying) is that one of the dozen + times I tried this I actually got the Android Auto screen to show up on the Sync 3 system, but it then shut itself down after about 1 or 2 seconds, so the phone was taking to the system, but I was never able to recreate the connection again in spite of trying repeatedly.

 

When I tried the new phone on the Ford and Chevrolet cars I used the same cables and they all worked, so it was not the cables themselves. I told myself that I gave up on getting the Sync 3 system to work with the new phone, and just use the old phone until Ford released a new update to the system (if they ever do), but will probably try a couple of other things. Perhaps reset both Sync 3 and phone at the same time. Perhaps remove all of the devices from the Sync 3 system. I no longer expect any of this to work, but there is still the glimmer of hope that something will work.

[mvan231]

The new update is out for Sync 3 (just make sure to remove the space between the http: and the rest of the link

 

http: //az696501.vo.msecnd.net/owner-package/12555428801312641808/SYNC3_2938367228_Update.zip

 

On 7/13/2019 at 8:19 PM, Multitask said:

18093 would be the highest that the Ford site will give you... there are later versions out there, that I would call beta ... 

 

I'm currently running 19119 that I downloaded from somewhere, but it's not a 'in public' version

 

It took Ford about a year to go from the 17xxx to the 18xxx, so maybe sometime this year they will do 19xxx

 

Edited July 17, 2019 by mvan231

[mvan231]

7 hours ago, Michael David said:

For a couple of days I spent hours trying different approaches to try to get the phone working with Sync 3. One of those involved doing a Master Reset on the Sync 3 system, another involved clearing the data from the Android Auto app and others involved trying pretty much every usb-c cable I had. I uninstalled and reinstalled Android Auto and Waze. I shut down and restarted the phone. None of that worked. I then spent an hour making sure the Android Auto settings on my S10 Plus were the same as those on the S7 Edge, but that did not help either.

 

The one really annoying thing (well, all of this is annoying but the one thing that is most annoying) is that one of the dozen + times I tried this I actually got the Android Auto screen to show up on the Sync 3 system, but it then shut itself down after about 1 or 2 seconds, so the phone was taking to the system, but I was never able to recreate the connection again in spite of trying repeatedly.

 

When I tried the new phone on the Ford and Chevrolet cars I used the same cables and they all worked, so it was not the cables themselves. I told myself that I gave up on getting the Sync 3 system to work with the new phone, and just use the old phone until Ford released a new update to the system (if they ever do), but will probably try a couple of other things. Perhaps reset both Sync 3 and phone at the same time. Perhaps remove all of the devices from the Sync 3 system. I no longer expect any of this to work, but there is still the glimmer of hope that something will work.

 

You're running a 2018/2019 vehicle? Strange that it isn't working. I have a 2016 Edge, but I had to update the USB module to be CarPlay compliant, but now it works like a dream

[Multitask]

On 7/13/2019 at 5:19 PM, Multitask said:

18093 would be the highest that the Ford site will give you... there are later versions out there, that I would call beta ... 

 

I'm currently running 19119 that I downloaded from somewhere, but it's not a 'in public' version

 

It took Ford about a year to go from the 17xxx to the 18xxx, so maybe sometime this year they will do 19xxx

 

I see that a 19149 is out there.... hmmm

 

EDIT: Ah, it's EU only

Edited July 18, 2019 by Multitask

[Michael David]

15 hours ago, mvan231 said:

The new update is out for Sync 3 (just make sure to remove the space between the http: and the rest of the link

 

http: //az696501.vo.msecnd.net/owner-package/12555428801312641808/SYNC3_2938367228_Update.zip

 

 

 

That link does not take me to a download. Instead I get this. If you have the actual zip file that I can download from dropbox or some other location I will give it a try.

 

When I log onto the Ford website and ask about updates I get this message: You do not have a download available at this time.

 

[Michael David]

15 hours ago, mvan231 said:

 

You're running a 2018/2019 vehicle? Strange that it isn't working. I have a 2016 Edge, but I had to update the USB module to be CarPlay compliant, but now it works like a dream

 

I will check with Ford about doing that. Perhaps it is the hardware and not the software, although the usb-c stuff should be backward compatible and I am using Android Auto, not Apple stuff. Still, it can't hurt to check.

 

[Michael David]

Update:

 

I found the link on the other forum thread and that link worked. I have downloaded the zip file and will take a look at it.

 

Thanks.

 

[asteele]

"That link does not take me to a download. Instead I get this..."

 

 

that is because you didn't remove the space after http: , so the URL you entered wasn't valid.

The poster did tell you to remove the space within their message; but it would be easy to gloss over and then make this mistake.

 

Try again with the space removed!

[mvan231]

27 minutes ago, asteele said:

"That link does not take me to a download. Instead I get this..."

 

 

that is because you didn't remove the space after http: , so the URL you entered wasn't valid.

The poster did tell you to remove the space within their message; but it would be easy to gloss over and then make this mistake.

 

Try again with the space removed!

 

Spot on! I also am told by the Ford site that there are no downloads available for me at this time

[Michael David]

2 hours ago, asteele said:

"That link does not take me to a download. Instead I get this..."

 

 

that is because you didn't remove the space after http: , so the URL you entered wasn't valid.

The poster did tell you to remove the space within their message; but it would be easy to gloss over and then make this mistake.

 

Try again with the space removed!

 

Absolutely correct. I guess that falls under the category of "Oops".

 

Got it. I wonder if the European update differs from the US update and, if so, what the differences would be. Does anyone know? And is there any reason to think that a European update would somehow not work in the US? Or does it just provide additional language interfaces?

 

[bbf2530]

3 hours ago, Michael David said:

Update:

 

I found the link on the other forum thread and that link worked. I have downloaded the zip file and will take a look at it.

 

Thanks.

 

 

Hi Michael.  Can you post a link-to-the-link on the other forum thread you mentioned?

 

Thank you.

[mikemullin6]

20 hours ago, mvan231 said:

The new update is out for Sync 3 (just make sure to remove the space between the http: and the rest of the link

 

http: //az696501.vo.msecnd.net/owner-package/12555428801312641808/SYNC3_2938367228_Update.zip

 

 

 

20 hours ago, mvan231 said:

The new update is out for Sync 3 (just make sure to remove the space between the http: and the rest of the link

 

http: //az696501.vo.msecnd.net/owner-package/12555428801312641808/SYNC3_2938367228_Update.zip

 

list files says this is only for NAV/EU vehicles.  Do you have access to the NAV/NA and non-NAV/NA versions?

 

 

 

[mikemullin6]

list files says this is only for NAV/EU vehicles.  Do you have access to the NAV/NA and non-NAV/NA versions?

[mvan231]

4 minutes ago, mikemullin6 said:

list files says this is only for NAV/EU vehicles.  Do you have access to the NAV/NA and non-NAV/NA versions?

 

for Sync 3 with NAV
https: //ivsubinaries.azureedge.net/owner-package/7932338036273117425/SYNC3_2807667713_Update.zip

for Sync 3 without / non NAV
https: //ivsubinaries.azureedge.net/owner-package/14815755102569714493/SYNC3_2807668185_Update.zip

 

 

Edit:

Looks like this still has only been released for EU. I don't know what the differences are between EU and NA releases to be honest. I don't believe there should be any major differences.

Edited July 18, 2019 by mvan231

[mikemullin6]

To MICHAEL DAVID

 

can you post the link to the working NAV/NA SYNC 3 update?

also, non-NAV/NA version

 

thanks

[Michael David]

1 hour ago, mikemullin6 said:

To MICHAEL DAVID

 

can you post the link to the working NAV/NA SYNC 3 update?

also, non-NAV/NA version

 

thanks

 

Sure. The last post (as of now) here. 

[asteele]

Some differences between the EU and NA versions are to do with the voice commands and how the map works.

 

I installed a NA version on my Australian vehicle some years ago and broke voice commands from being able to control navigation...  I learned that Australia needs the EU version!

 

I read elsewhere that the only file we should install is the -AR one, and by only installing that you don't accidentally upgrade/replace anything other than the core OS itself.... so you would need to edit the autoinstall file.

 

[Multitask]

2 hours ago, asteele said:

Some differences between the EU and NA versions are to do with the voice commands and how the map works.

 

I installed a NA version on my Australian vehicle some years ago and broke voice commands from being able to control navigation...  I learned that Australia needs the EU version!

 

I read elsewhere that the only file we should install is the -AR one, and by only installing that you don't accidentally upgrade/replace anything other than the core OS itself.... so you would need to edit the autoinstall file.

 

 

The Bolded part is interesting.... I'll have to look into that.... the file listed above for non-nav has a huge file in there....  the AE file is almost 1.7gig

[asteele]

Being in Australia, where we use the EU build, I took the plunge and installed everything that came with build 19149, and it works great... took about 15 mins from start to finish.

 

Always use a modern USB drive for best copy speed - old slower drives that have been rattling in a desk drawer for a few years will make any update take a long time... and when it's copying the files of the USB you don't get any messages - so there is no clue it is doing anything unless your USB has an activity flight flashing away during the copy. Only after the copy has completed do you get a message "system update in progress" - but many users pull the USB out during the copy not knowing that anything is even happening.

 

 

I was on build 18093 previously.

Gracenote didn't change in version as a fyi... it's still v1.1.1.1127(EU-0010)

 

 

Sync3 appears to be snappier in response, but who knows if it really is.

After running obvious tests with voice commands and navigation I also tested Android Auto - which also seems snappier - but is it really?

I haven't tested CarPlay - but will install on wifes vehicle tonight and will see if she stops complaining about the incorrect Waze speed.

 

 

Non-EU users will probably break voice commands/navigation if they install all the files together (since that is what I broke at my end when I installed a NA version 2 years ago) - but I wanted to share my success in Australia in cast it helps.  Everything at your own risk of course!   Good luck!

 

 

[mvan231]

I'll confirm that the speed shown in Waze is fixed for CarPlay in this version. I don't really know about native voice or nav (don't have nav) commands since I haven't used either in my Edge. I wouldn't use the nav if I had it anyways due to other services like Waze having more up to date maps.

[Michael David]

16 hours ago, asteele said:

I read elsewhere that the only file we should install is the -AR one, and by only installing that you don't accidentally upgrade/replace anything other than the core OS itself.... so you would need to edit the autoinstall file.

 

Excuse my ignorance, but what AR file? None of the files in the un-zipped SyncMyRide folder have AR in the name.

 

My understanding is that I was supposed to download the update, unzip it (I work on a Mac and the instructions told me to use Stuffit for that part), and then copy 2 files (autoinstall.lst and DONTINDX.MSA) and one folder (SyncMyRide) to the root of a memory stick formatted as ExFAT. Then to use that as the update mechanism for Sync 3. I did that, I got the updating message and then, about 15 minutes later, I got the complete message. But there is no AR file anywhere on the usb stick.

 

There are AB, TCB, THA, AAB, AM, CD and CB tar files. The update gave me version 18093.