Sync 3 very laggy after upgrade from v2.2 to v3.0

Ford SYNC 3 Support Ford Update Support
, , , , ,
1

We noticed our Kuga recently upgraded from v2.2 to 3.0 over wifi automatically so I thought I would also update the maps via the Ford website. However when checking we werent on the latest release of v3.0 so I downloaded this from the ford website and installed it this morning making sure I uploaded the log file back to Ford.

The current issue is our system is very laggy now and from reading it seems to be caused when Sync 3 updates but you are using old map data. The car is currently running maps F6 so I logged onto the ford website to download the latest version now Sync 3 is up to date however the download link they provide is downloading a 46kb file which I believe is interrogator rather than maps.

https://iotazipbinaries.ford.com/ownerpackage/3018912408/Map_47451_Update.zip

Ford have confirmed this is a known issue and are working to resolve however the problem we face is Sync 3 is very laggy and almost unusable in its current state with the F6 maps installed. I was reading on another thread someone mentioned it works fine when leaving the USB stick inserted and I have found this to be the case however I was wondering if someone could take a look at the output after the most recent update to 3.0.23219 and see if anything else could be causing the issue?

I have tried a master reset with and without the USB stick installed but this makes no difference and the system is just painfully slow until the USB memory is inserted again.

SYNC Region: EU

Navigation Variant: Nav

Manufacturer Year: Pre MY20

Install Type: OEM

Old SYNC Version: 2.3

New SYNC Version: 3.0.23219

Do you have a error message, if so what is it?
No error message, just running very slow.

Update Method: Official Ford

Sync_LX19010Q_WF0AXXWPMAJL61883.xml (10.8 KB)

2

Also worth mentioning I was reading a thread from 2022 where someone had the same issues and a guy called F150 was super helpful and they managed to resolve the issue which made me think about making a new post.

3

This is installed on the APIM…
JL7T-14G424-BA JL7T-14G421-BA EU.4.15 (08.09.2016, F6.
JL7T-14G422-BA 6.5Gb Sync3 v2.3.16284 EU, Nav Data version: 420.
JL7T-14G421-BA 11.4Gb Sync3 v2.3.16284 EU.4.15 (08.09.2016, F6.1)
JR3T-14G391-AE 1.5Gb Sync3 v3.2.19056-Pre18.5
JR3T-14G423-AB 711Mb Sync3 v3.0.17024 1.1.1.1127 (EU-0010) (23.08.2016)
JR3T-14G381-AY 417Mb Sync3 v3.0.23219

The maps are way out of date as you say, which can cause issues like what you described above. Ford is no help here unless you were subscribed to their map update service.

The solution here is to update the maps on the APIM. Your APIM storage looks good so there shouldn’t be an issue with this.
<d2p1:PartitionHealth type=“/fs/images/” total=“55G” available=“20G”/>

You will want to follow the instructions in this guide:
Sync 3.0.20204/23219 with EU 2.21 (F11) or EU 2.22 (F12) or EU 2.23 (F13)/EU 2.24 (F14) Map Installation - Ford / Guides - CyanLabs Official Community

Since you already have Sync 3.0.23219 installed, you can skip to the NAV Package USB Preparation Instructions section and start there.

4

Thank you that makes sense, I thought Ford still provided map updates even if you weren’t subscribed.

Just checking you mentioned on that old thread the maps were so old they were not compatible and you could tell that from the letters at the start being different. Is that not the case here and could a map update potentially not resolve the issue?

Also are the maps provided on that guide you sent any different to the ones you would download from Ford?

5

All files are sourced from the Ford IVSU database and are authentic. No modifications are made to these files.

It is possible that the map update is not the answer and your APIM has other issues, however, this has resolved these symptoms in the past.

1 Like
6

Thanks I’ll download the files today and look to follow the guide.

One last question does the autolist.lst need to be changed from the one in the tutorial as I am running Sync 3.0.23219?

; SYNC3 Consumer Application Upgrade - Release 3.0.25 - Only for Nav/EU assemblies.

[SYNCGen3.0_3.0.20204_PRODUCT]
Item1 = HB5T-14G386-TJB_133301.TAR.GZ
Open1 = SyncMyRide\HB5T-14G386-TJB_133301.TAR.GZ
Item2 = JR3T-14G424-BH_1658336264000.TAR.GZ
Open2 = SyncMyRide\JR3T-14G424-BH_1658336264000.TAR.GZ
Item3 = JR3T-14G421-BH_1658243676000.TAR.GZ
Open3 = SyncMyRide\JR3T-14G421-BH_1658243676000.TAR.GZ
Options = AutoInstall
[SYNCGen3.0_3.0.20204]
Item1 = JR3T-14G421-BH_1658243676000.TAR.GZ
Open1 = SyncMyRide\JR3T-14G421-BH_1658243676000.TAR.GZ
Item2 = HB5T-14G386-TJB_133301.TAR.GZ
Open2 = SyncMyRide\HB5T-14G386-TJB_133301.TAR.GZ
Item3 = JR3T-14G422-BG_1658243770000.TAR.GZ
Open3 = SyncMyRide\JR3T-14G422-BG_1658243770000.TAR.GZ
Options = Delay,Include,Transaction
[SYNCGen3.0_ALL]
Item1 = GB5T-14G386-AC_1587495565000.TAR.GZ
Open1 = SyncMyRide\GB5T-14G386-AC_1587495565000.TAR.GZ
Options = Delay,Include,Transaction

Thanks, Sam.

7

You need to change the autoinstall.lst for the map installation and use the latest files for F14 shown in the guide.

8

I have downloaded those files it’s just changing the file that is confusing me. Would you mind if you get a second providing an example?

9

Use a text editor to reflect the new file names.

10

autoinstall.lst (919 Bytes)

Make sure you download and put all the files listed in the SyncMyRide folder on the USB.