Braxx

I was going to try this sync3 v3 update but I'm still a little confused. I'll gather up my questions and get more comfortable with it before modifying my files.
In the mean time I think I'll just update/reflash the bcm and pcm on my wifes 2018 EcoSport , things I'm more comfortable with.
Thanks for the help Acool
I'm sure I'll have more questions in the coming days when I attempt the Sync update.

Acool

Sending you a PM

JFM4

iTrader: (1)

Acool, I followed the instructions you wrote for using the Nav voice file to free up memory (thanks for that) before performing a successful clean install of V3.0 18025. Will the fact that I used Nav Voice from V2.2 affect anything in my 3.0.18025 install?

Edit: I have a MY16 Non-Nav, so am I using Nav voice anyway?

Acool

The Nav Voice is used to only temporarily free up space. Once you install the full clean V3.0, you are reinstalling the Non-Nav voice. The issue is it can't install updated Non-Nav voice over old Non-Nav voice because it runs out of space while extracting the new Non-Nav voice. Since Nav voice is smaller, it can unpack and install Non-Nav voice over the Nav voice you temporarily installed. If your 3.0 install was clean, then everything is back to normal.

The reason Nav voice is smaller is because there's also a much much larger voice_nav file on Nav APIMs that makes up the difference. So Nav APIMS have voice and voice_nav. We're just borrowing voice temporarily.

Airborne_Ape

Im not sharing the direct link because that is partly how the Mustang Sync 3 forum got a cease and desist letter from lawyers at Ford. It is not my fault Ford left their intellectual property on a public server, but Im not keen to potentially seeing this thread shut down by sharing those files.

If you happen to find any IVSU binary link for any of Fords files from their servers you can look at the URL and easily figure it out how to copy and paste in the file name in to download whatever you need. Literally just google the words: ivsu, ford, binary, link. You will not find the file in any update section or friendly user interface section like the Ford owner website.

Airborne_Ape

Not sure why this is happening. My Apple Watch series 3 can pair with non-Apple bluetooth speakers but not Sync 3. I tried out of curiosity because there are days I leave my phone behind.

partsman109

I just updated mine to v3 today...when I try to report the update to Ford it states upload unsuccessful.

Braxx

I format my usb to exFat because Ford Owner site says that is what it should be. I've read some say to use Fat32.
Should I continue to use exFat or is there a reason to use Fat32?

flyinghappy

Mine was exFat and worked just fine.

Acool

I've had better luck with FAT32. FAT32 is an extremely well supported and compatible standard. Its main limitation is file size, but no Sync software update has had files large enough to matter. Nav updates are a different story where large file sizes won't work with FAT32.

When I say I've had better luck, let me clarify: I've looked directly at read speeds on the APIM. The APIMs are for some reason very temperamental. Sometimes a USB will read well at 10-20mb/s. Other times it will drop to ~100k/s or even less. Sometimes a reboot fixes the issue. I've noticed these issues more when I have an exFAT formatted usb. When you hear about people posting that their APIM has been stuck at UPDATING SYSTEM SOFTWARE for the last hour+, it's probably because the APIM decided to read that USB stick at a 100k/s.