F13 latest maps NAV freezing while driving

Ford Discussion
, , ,
1

Hello everyone,

it has been a couple of months since I installed the F13 EU maps on my Fiesta ST 2020, and I’ve realised only recently since my friend has the same car but didn’t do the update that my position icon keeps stuttering and freezing many times during a trip, like complete 3/5 second freezes whilst his never freezes.

My question is, can it be an issue of the maps being heavier? or could it be related to the fact that the first time I tried to install them it didn’t go through and had to restart the whole process? Any tip or answer will be gladly appreciated since I don’t know what I have to do, if I have to format or if it’s normal this way, thanks

2

What build of Sync3 are you on?

3

Sync 3.4.23188, the latest one available at the moment for my vehicle

4

There is nothing newer. This was the last one Ford released.

5

Thanks for the reply! Yes indeed, so is it normal? Or maybe the latest maps version is too heavy for this sync and that’s why they didn’t officially let you download them yet?

I was wondering what I have to do, if I need to install an older maps version or if it’s just how it is with the latest maps.

Thank you again for the support.

6

Have you tried a master reset?
If the answer is not, try with that.
Then create, run and share the output for the interrogator log. (redact the VIN from the file’s name and content if you care about it)

7

Yes I tried it but the freezes still happen during navigation, but if it helps I can master reset again and try the interrogator

8

VIN:
Modello di APIM: LU5T-14G371-GKC
Tipo di APIM: Navigation
Capienza APIM: 64GB
APIM Spazio Libero: 9.0G
Versione 3.4.23188 (NU5T-14G381-AD)

15/03/2026 09:34:41 +00:00

Partition Type = Free / Total
/fs/sd/MAP/ = 976K / 1.2G
/fs/sd/MAP/ = 15M / 3.0G
/fs/sd/MAP/ = 14M / 2.4G
/fs/sd/MAP/ = 7.8M / 1.6G
/fs/sd/MAP/ = 17M / 2.4G
/fs/sd/MAP/ = 26M / 3.7G
/fs/sd/MAP/ = 312K / 41M
/fs/sd/MAP/ = 4.9M / 3.4G
/fs/sd/MAP/ = 27M / 3.4G
/fs/Nuance/ = 29M / 5.0G
/fs/Nuance/ = 30M / 5.2G
/fs/Nuance/ = 27M / 4.6G
/fs/Nuance/ = 38M / 3.9G
/fs/Nuance/ = 8.4M / 1.9G
/fs/Nuance/grace = 21M / 1003M
/fs/rwdata/ = 763M / 1.2G
/fs/rwdata/quip/ = 35M / 35M
/fs/rwdata/quip/ = 90M / 90M
/fs/mp/ = 84M / 1.4G
/fs/mp/resources = 332K / 72M
/fs/images/ = 9.0G / 54G

Installed Packages
1U5T-14G421-BAM
1U5T-14G421-BBM
1U5T-14G421-BCM
1U5T-14G421-BDM
1U5T-14G421-BEM
1U5T-14G421-BFM
1U5T-14G421-BGM
1U5T-14G421-BHM
1U5T-14G421-BJM
1U5T-14G658-AH
4U5T-14G422-BCM
4U5T-14G422-BAM
4U5T-14G422-BBM
1U5T-14G424-BP
4U5T-14G423-AC
5U5T-14G391-AT

4U5T-14G422-BDM

APIM AsBuilt
DE00: 886A059A50027C0440C2
DE01: 474D0B0AC08A0890A8B84E04
DE02: 0000010000
DE03: 00001D82310101
DE04: 190819082653
DE05: 80
DE06: 0B0533000000006428000056565D0061

is this everything needed?

9

The output seems ok. Does the about sync3 screen show the correct information for the maps?.

11

What do you mean with correct information?

I also tried to clear the rwdata but after doing another interrogation it still showed 763MB.

12

Is the information displayed in that screen correct?. The map version for instance…

13

IMG_20260316_123359
IMG_20260316_1233591920×388 255 KB

F13 yes, but it showed F13 as well before the update because it’s not officially the F14 maps

14

So we do not really know… Ok, here is what I think: you should not be experiencing lag, unless the hardware is going bad…

There’s something to try, but it will be a pain…

  • install F12 EU maps, the whole package.
  • see if the about sync3 screen changes (it should)
  • run the interrogator log to see how much free space the APIM has
  • if it does, use it for a while to see if you experience any lag
  • if no lag is present, reinstall the latest F13 package
  • confirm the information has updated in the about sync3 screen
  • run the interrogator log to see how much free space the APIM has
  • use it for a while, see if there are any lags

After all of this, we would get a better idea of what the issue is. Also, having only 9GB of free space is on the lower end… And maybe, just maybe, you have a corrupted/incomplete NAV installation…

Again, testing this will be a pain… Also, if the position lags (but the UI does not), maybe there’s something else at play that’s not related to either of these things…

1 Like