At least now I know it exists. Do you happen to know what the other utilities do? I see there are nav and non_nav Sync 3 partition table checks but those are the only other ones I know. I assumes the IFS update scripts update validations of approved native apps?

 

This looks like nav data stored on sync 3:

/fs/Nuance/Nav_Data/MD5_PerFile.txt
/fs/Nuance/Nav_Data/Nav_Data_** (** = regional letter codes like NA or EU)
/fs/Nuance/Nav_Data/Version.inf
/fs/mp/NAV/licence.key

So you think it's possible to simply overwrite this data and that these folders & files are contained in the latest JR3T-14G421-CB.tar.gz & JR3T-14G424-CB_88385.tar.gz?

Again, I'm not a programmer. I just want to figure this out since Ford won't provide owners with updates.

 

lol.

Found Sync 3 native ringtones here.

/fs/Nuance/Nuance/VCA/data/common/run/soundfiles/89500_Ringtone1.pcm

89501_Ringtone2.pcm
89502_Ringtone3.pcm

 

Nice list. Newer versions add various new errors as well.

Off the top of my head I can't remember them all, not much interesting though ... the partition check is really only to make sure you get the right system voice package. Everything else is the same nav vs non nav (outside of maps and nav voice of course). IFSs are a QNX way of packaging some read only files. The main IFS, QNX-IFS is the secondary bootloader (along with the MLO). So the update of it is part of the update of the core sync software. The various forks that delineate MY16/MY17 base versions as far as I can tell are patches for bugs likely related to Apple Carplay, so those are other utilities I believe.

/fs/Nuance is a voice image mount point. Anything here is from the voice image.

Indeed it works ... and you don't need 14G424-CB

It's a shame they don't release mass updates.

 

Ok, estimated guess number two.

I extracted JR3T-14G421-CB.tar.gz

There are two files contained in it: map_new.img & map_ext_new.img
I would rename them without the word 'new' and overwrite the following...

When connected to sync 3 you can go to /fs/images and see:
/fs/images/map.img
/fs/images/map_ext.img


Also, while I think this part doesn't apply for North America, I found that under /fs/sd/MAP there is version.imf and version.txt here. I suspect this is only for nav units that draw map resources from an externally mounted disc (sd card) and therefore licence data isn't that important for North American units or it is stored somewhere else which I can't see.

Does this sound right?

 

If anyone here wants to test this theory assume you can set a custom background (if you use the default ford-timeless theme) by overwriting this file while keeping the same file name.

/fs/mp/fordhmi/qml/themes/ford-timeless/images/day/view_background.png

/fs/mp/fordhmi/qml/themes/ford-timeless/images/night/view_background.png

 

Exactly. During install the _new gets dropped.


Eh good guess but not quite. The "sd" don't read into that meaning external. /fs/sd/MAP is where map.img and map_ext.img are mounted. Everything you see there is from those two images. So different regions will have different contents there. The images aren't APIM specific so any APIM with the same map version will have exact files in /fs/sd/MAP

 

Acool is your username Stang18 on other threads?

 

Nope but he's a pal

 

I see where these changes need to be made now, but the firewall is preventing access. I'm not even remotely knowledgeable when it comes to building my own NCM drivers on linux. I know you know more lol and we all know Ford monitors these websites... 'HI FORD' ... but do you have any hints of ways to explore getting around this firewall problem?