Ok, got it.

I had the persistent test menu on so missed that phase.

Gone into test menu via speaker walkaround.

 

 

 

Sent from my SM-G965F using Tapatalk

 

 

 

 

13 minutes ago, Stoney871 said:

Ok, got it.
I had the persistent test menu on so missed that phase.
Gone into test menu via spesker walkaround.




Sent from my SM-G965F using Tapatalk
 

Perfect, thanks.

You have F8 maps, but a newer Nav voice than mine. Although there is also a newer one still now, hopefully we'll both be offered that with the F9 map.

Have you been offered the 3.4 20136 update on the Ford site yet? I'm tempted to update mine from 3.3 using the official update currently rolling out on the Edges.

Checked updates yesterday and nothing available yet.

Sent from my SM-G965F using Tapatalk

Sent from my SM-G965F using Tapatalk

Has there been an OTA update to sync 3.3 but without an version update. I'm on 19052, and yesterday when first starting the car the info screen did not come on as normal then when total black as if a reboot.  Now in mobile apps I have a new icon "App Catalogue" when it's list all available apps.

As for the Hazard Spot Warning people are getting , it was turned off in my menu, now turned on and will see what happens.

1 minute ago, Mark-UK said:

Has there been an OTA update to sync 3.3 but without an version update. I'm on 19052, and yesterday when first starting the car the info screen did not come on as normal then when total black as if a reboot.  Now in mobile apps I have a new icon "App Catalogue" when it's list all available apps.

As for the Hazard Spot Warning people are getting , it was turned off in my menu, now turned on and will see what happens.

19052 is the same version they've been using for the first year of production of the Mk4.

Perhaps something to do with the fordpass app updated, or some other service getting updated.

28 minutes ago, Mark-UK said:

Has there been an OTA update to sync 3.3 but without an version update. I'm on 19052, and yesterday when first starting the car the info screen did not come on as normal then when total black as if a reboot.  Now in mobile apps I have a new icon "App Catalogue" when it's list all available apps.

As for the Hazard Spot Warning people are getting , it was turned off in my menu, now turned on and will see what happens.

I’m on 3.3 19052 but no sign of hazard warning button?

am I missing something? 
 

(apart from F7 maps update 😡)

1 hour ago, alexp999 said:

Perfect, thanks.

You have F8 maps, but a newer Nav voice than mine. Although there is also a newer one still now, hopefully we'll both be offered that with the F9 map.

Have you been offered the 3.4 20136 update on the Ford site yet? I'm tempted to update mine from 3.3 using the official update currently rolling out on the Edges.

Do you forsee F9 being imminent?

Just now, Andyr55 said:

Do you forsee F9 being imminent?

Yea sort of. But imminent could be anytime in the next few months. They seem to be doing the 3.4 update first. 
 

But in the US the 3.4 update then triggers the map update. So I’d expect the same here eventually. 
 

I only know of the Edge getting 3.4 in Europe at the moment. 

14 minutes ago, Andyr55 said:

I’m on 3.3 19052 but no sign of hazard warning button?

am I missing something? 
 

(apart from F7 maps update 😡)

I may be talking about the wrong thing, in fact a little research and I'm sure I'm getting confused. As I now think it was on before and some how got turned off.

 

 

3 hours ago, alexp999 said:

I'm tempted to update mine from 3.3 using the official update currently rolling out on the Edges.

I can't see why that shouldn't work. If you decide to take the plunge let us know how it goes!. I've just pulled the update using a Nov 2019 Edge VIN and its exactly the same.

As you say the files aren't unique to model's. The files extracted from this update have exactly the same file names and md5 hashes as those pulled directly from the Ford binaries CDN using the Cyanlabs and .ru boards download references.

You never know , I might get brave enough before you...

4 hours ago, ianincheshire said:

I can't see why that shouldn't work. If you decide to take the plunge let us know how it goes!. I've just pulled the update using a Nov 2019 Edge VIN and its exactly the same.

As you say the files aren't unique to model's. The files extracted from this update have exactly the same file names and md5 hashes as those pulled directly from the Ford binaries CDN using the Cyanlabs and .ru boards download references.

You never know , I might get brave enough before you...

Just done mine this evening.

Looks like the older AD package for the DAB logos is incompatible. Otherwise works great. I've manually upgraded them to AE, same as Clive had from factory.

Thanks for that Alex.

I'll download the AE version  of the dab logos and add that to the install.

I' think I'll then give that a go tomorrow.

About how long did the update take ?

1 minute ago, ianincheshire said:

Thanks for that Alex.

I'll download the AE version  of the dab logos and add that to the install.

I' think I'll then give that a go tomorrow.

About how long did the update take ?

Took about 20-30 mins. 

Just a bit too long to do it with engine off then as sync will shutdown in 30 mins.

BTW did you upload the xml log file after the update ?

Just now, ianincheshire said:

Just a bit too long to do it with Ignition off then as sync will shutdown in 30 mins.

BTW did you upload the xml log file after the update ?

No, have kept the xml and will upload it when it’s officially available for my car. Have turned off WiFi so it doesn’t report in for now. 

1 hour ago, alexp999 said:

Just done mine this evening.

Looks like the older AD package for the DAB logos is incompatible. Otherwise works great. I've manually upgraded them to AE, same as Clive had from factory.

Great info Alex. I’m about to update mine too. Got the AE DAB file downloaded and put it in the SyncMyRide folder. Edited the autoinstall.lst file to look like this. Do you think I should be good to go?

3 minutes ago, colinmcg71 said:

Great info Alex. I’m about to update mine too. Got the AE DAB file downloaded and put it in the SyncMyRide folder. Edited the autoinstall.lst file to look like this. Do you think I should be good to go?

Looks good to me. 

3 minutes ago, alexp999 said:

Looks good to me. 

Excellent, thank you. 
 

Did you master reset afterwards? 

Just now, colinmcg71 said:

Excellent, thank you. 
 

Did you master reset afterwards? 

Nope. Just locked it and left for 20 mins after install, to let it do it’s “maintenance”. 

Update went fine. Only issue I’ve noticed is that the ST splash screen on shutdown has gone and has been replaced by the Ford logo. Maybe it’ll return after a few startup shutdown cycles.

2 hours ago, colinmcg71 said:

Update went fine. Only issue I’ve noticed is that the ST splash screen on shutdown has gone and has been replaced by the Ford logo. Maybe it’ll return after a few startup shutdown cycles.

Colin,

This forscan thread https://forscan.org/forum/viewtopic.php?f=16&t=6676&sid=303da946ab937a62e9d571a0ff8d5340&start=10 might help

The relevant para is

Quote

Do you update the SYNC with 3.4 version ...

In this version , the default theme must be changed to "classic" no more timeless.
With this setting , you should have the ST logo at the start and also a the end splash screen.

7D0-03-01: xxxx 00xx xxxx - Ford Classics theme ( default for 3.4 version )
7D0-03-01: xxxx 01xx xxxx - Ford Timeless (default before 3.4 versions )

Seems like vn3.4 is processing the themes settings slightly differently.

Obviously you'll need Forscan and an adapter if you wish to change it

The ST logo shows up fine on mine when you unlock the car, haven't noticed anything about shutdown, I usually just get out and let it turn itself off. When should I be looking?

This update when it rolls out if intended for Sync 3.3 cars wouldn't require any APIM changes, unless Ford just don't care about logos changing, lol. I guess the one people see most is the boot up one.

EDIT:

Just looked up a 2020 Focus ST with Sync 3.4 from factory and it has 7D0-03-01: xxxx 01xx xxxx, the same as mine, so I don't think it's that.

Quote

This update when it rolls out if intended for Sync 3.3 cars wouldn't require any APIM changes, unless Ford just don't care about logos changing,

Probably they never tested it with an ST!

From that Forscan thread it's just the shutdown logo that's affected.

Clive has an ST with 3.4 installed from the factory doesn't he ?, it would be interesting to see if he has the same problem.

Another interesting comment on his IVSU Versions , he only seems to have maps 421-BAE? . I thought there were 8 map IVSUs for Europe.

BAE is EU Common, BBE is EU Ext, BCE is EU_North_UK , I would have thought that at least those 3 would be installed on a UK car ?

Maybe the bezel diags only shows the primary map IVSU

 

Just now, ianincheshire said:

From that Forscan thread it's just the shutdown logo that's affected.

Clive has an ST with 3.4 installed from the factory doesn't he ?, it would be interesting to see if he has the same problem.

Another interesting comment on his IVSU Versions , he only seems to have maps 421-BAE? . I thought there were 8 map IVSUs for Europe.

BAE is EU Common, BBE is EU Ext, BCE is EU_North_UK , I would have thought that at least those 3 would be installed on a UK car ?

Maybe the bezel diags only shows the primary map IVSU

 

Yeah that menu only shows the first BA* map file. Mine is the same, yet the XML shows all 8 mount points for the map.