Sync 3.3 Causing Problems

[Navyboy]

Hey guys,

So along with everyone else I’m sure, I for the message a week or so ago to update to sync 3.3 on my 2019.
Went though the process with a usb stick, put it in, it said updating, eventually rebooted and seemed like it was all good.

After playing with it for a few days, I now have the following problems that I didn’t have before the update.

1) wont connect to my house WiFi
2) all voice Nav doesn’t work, I press the voice button on the steering wheel, say “find an address” (or POI) it waits a second then just resumes music as if nothing happened
3) the voice system will regularly confuse my command and just start playing Sirius radio.

I’ve tried rebooting a few times, I’ve done the master reset, and tried to do the update again. Nothing seems to fix it.

Any suggestions before I call the dealer or the 1800 number they supplied?

Sponsored

 

[ResQ_Ranger]

As of 3 days ago I've got 0 audio. When I try to turn the radio on it continuously turns it on and off but no sound plays. No voice prompt when using the NAV system, no sound when I try to have it read texts, etc. I've tried some random fixes I found online like locking and unlocking the doors, remote starting the vehicle, the master reset you refer to, among other things and so far no luck. I'm out of good ideas at this point.

 

[Geoff]

As of 3 days ago I've got 0 audio. When I try to turn the radio on it continuously turns it on and off but no sound plays. No voice prompt when using the NAV system, no sound when I try to have it read texts, etc. I've tried some random fixes I found online like locking and unlocking the doors, remote starting the vehicle, the master reset you refer to, among other things and so far no luck. I'm out of good ideas at this point.

You may have a malfunctioning APIM. Your dealer can check for fault codes (or, if you have a ODB2 reader you could check for codes yourself).

 

[weasel1]

Rangers came with less than Sync 3.3? Huh. Mine (September build) already has 3.3.

 

[Geoff]

Rangers came with less than Sync 3.3? Huh. Mine (September build) already has 3.3.

Mine (Mar '19) came with Sync 3.3 but there was an update to a later 3.3 build number (19052 if memory serves).

 

[UofMEngineer]

Hey guys,

So along with everyone else I’m sure, I for the message a week or so ago to update to sync 3.3 on my 2019.
Went though the process with a usb stick, put it in, it said updating, eventually rebooted and seemed like it was all good.

After playing with it for a few days, I now have the following problems that I didn’t have before the update.

1) wont connect to my house WiFi
2) all voice Nav doesn’t work, I press the voice button on the steering wheel, say “find an address” (or POI) it waits a second then just resumes music as if nothing happened
3) the voice system will regularly confuse my command and just start playing Sirius radio.

I’ve tried rebooting a few times, I’ve done the master reset, and tried to do the update again. Nothing seems to fix it.

Any suggestions before I call the dealer or the 1800 number they supplied?

Sounds like you're missing some of the voice packages. Can you report back all of the items you see listed on the diagnostics IVSU Versions screen?

 

[weasel1]

Mine (Mar '19) came with Sync 3.3 but there was an update to a later 3.3 build number (19052 if memory serves).

Interesting. That's even the current build # I have. Makes me wonder if 3.4 is around the corner.

 

[CoastieN70]

I computer chatted with a Lass from Ford about SYNC 3.4 for the Ranger. She said the Official Line is that it's coming but there isn't a confirmed date as of yet. She said ALL 2020 Rangers are suppose to be shipped with 3.4 installed.
She also said that the SYNC update message on Ford Pass went to ALL Ford Pass Users not just to Ranger users as a global announcement.
We will wait...

 

[weasel1]

I just got a notice this morning on Ford pass that there is an update for Sync 3.
I was happy cuz I thought maybe it would fix my problems of late, where it's crashing, freezing and doing all sorts of crazy things, none of which Ford can find when they test it. no faults, no codes, nothing.
Anyways, they tell me they're working with Ford for a solution as I spend my time always resetting it.

This...I thought...would be the golden ticket to my troubles. A new update.
(As well a few days ago, I got the notification for the map updates. I have those downloaded, but not transferred to the truck yet.)

Nope. This is a Fail

I follow the link on my phone, it says use my desktop cuz I need to do it by USB. Fair enough.
I go to the Sync updates on my laptop, and it says I'm up to date and wont give me an option past that.

Ford really doesn't have a clue what they're doing.
Please stick to building vehicles, and farm out the computer work. You fail.

That sucks. I just noticed the notice (ha!) this morning. Was hoping for 3.4 . Bummer.

 

[Geoff]

Interesting. That's even the current build # I have. Makes me wonder if 3.4 is around the corner.

Yeah, it's around the corner....probably a corner many many blocks away.....

 

[Navyboy]

Sounds like you're missing some of the voice packages. Can you report back all of the items you see listed on the diagnostics IVSU Versions screen?

Not sure how to get to that screen. below is all the info on my About sync screen

Software version 3.3
Build 19052_product
ESN: U97100PN
Gracenote Version: 1.1.1.1332 (NA-0010)
Navigation Maps Version: NA 1 18

 

[UofMEngineer]

Not sure how to get to that screen. below is all the info on my About sync screen

Software version 3.3
Build 19052_product
ESN: U97100PN
Gracenote Version: 1.1.1.1332 (NA-0010)
Navigation Maps Version: NA 1 18

Press and hold seek forward on the panel and the steering wheel at the same time for ~10 seconds. Cancel the speaker walk around, then go to the APIM info, IVSU Versions, then it'll list what's installed.

 

[ResQ_Ranger]

You may have a malfunctioning APIM. Your dealer can check for fault codes (or, if you have a ODB2 reader you could check for codes yourself).

You were dead on with it being caused by the APIM. The service manager I picked it up from claims they did a hard reset on it that can only be done once and it is now working. He let me know that if it happens again that they will have to replace the module and he has been cleared to do so at no cost to me.

Sponsored