Update all versions of Ford Sync 3 to the latest Sync 3.4

Disclaimer: Links on this page pointing to Amazon, eBay and other sites may include affiliate code. If you click them and make a purchase, we may earn a small commission.

LokiWolf

Staff member
Moderator
Joined
Apr 2, 2016
Posts
3,971
Reaction score
2,837
Location
Richmond VA
I am on 20196. I noticed an improvement in general from 20021 to 20136. 20196 just fixed some icon glitches in SXM from what I can tell.


Sent from my iPhone using Tapatalk Pro
 

Highlightreel

Well-Known Member
Joined
May 10, 2019
Posts
84
Reaction score
45
Location
MN
Gumby, I tend to agree. I only notice the radio icon updates (which are nice) but other than that, nothing of note but it does seem to be just a bit off. Not totally crisp.

Also, switching from normal sync to android auto has got caught up for awhile and has delayed almost seems to have froze. I rebooted and shut off car so we'll see if that's gone next time.
 

Gumby

Full Access Members
Joined
Jun 5, 2019
Posts
496
Reaction score
238
Location
Beaumont, Alberta
Gumby, I tend to agree. I only notice the radio icon updates (which are nice) but other than that, nothing of note but it does seem to be just a bit off. Not totally crisp.

Also, switching from normal sync to android auto has got caught up for awhile and has delayed almost seems to have froze. I rebooted and shut off car so we'll see if that's gone next time.
I let my SXM subscription lapse so I don't really see any icon differences. FM Radio stations here don't seem to have icons and there are no stations in HD radio. I was running 20022 before so the FM radio interface is different and I like it. I also like the BT interface over the Carplay interface for music. *shrug*
 

mpc11

Well-Known Member
Joined
Dec 12, 2018
Posts
97
Reaction score
37
Location
MI
Hey DWs-TTEB, any chance you can check your region settings using forscan? I believe it's ACM-727-04-01, but I also see docs saying its FCIM-7A7-01-01.

Regardless, I tried this today, would be curious what others are seeing, as I'd love to find a solution to this. After these two attempts, I still get the "For your safety, some features have been disabled while your vehicle is in motion." message when trying to browse folders on a usb drive, by clicking on the new search button in the top right of the screen. Clicking that prior to 3.4 used to allow me to select folders, artists, albums, etc.

This afternoon I tried two different things to see if I could get the "browse USB media" functions back, so far to no avail. First, I reformatted my USB to exFAT. Second I upgrade to 3.4.20136. Still no work-e-y.
Ever find a fix for this? Updating from the latest stock 3.0 version to the newest 3.4 went smoothly, except I have this new, same issue with not being able to browse folders on my usb drive while driving when I could on 3.0. Getting the same for your safety message.

I also have a new seek issue when using usb. The steering wheel controls and the touch screen button works like it should: pressing seek once goes to the next song. Pressing the physical seek button on the dash/console, it jumps 2 songs at a time. Goes to next song for less than a second then goes to the following song and starts playing. Anyone else?

I've tried rebooting using power button & next button multiple times...
 

mpc11

Well-Known Member
Joined
Dec 12, 2018
Posts
97
Reaction score
37
Location
MI
Ever find a fix for this? Updating from the latest stock 3.0 version to the newest 3.4 went smoothly, except I have this new, same issue with not being able to browse folders on my usb drive while driving when I could on 3.0. Getting the same for your safety message.

I also have a new seek issue when using usb. The steering wheel controls and the touch screen button works like it should: pressing seek once goes to the next song. Pressing the physical seek button on the dash/console, it jumps 2 songs at a time. Goes to next song for less than a second then goes to the following song and starts playing. Anyone else?

I've tried rebooting using power button & next button multiple times...

Tried a few more things. Popped a cd in and seek acts the same. Steering wheel and touch screen seek forward go one track/song at a time but the dash button advances 2 songs on a single press. All three back seek buttons only go 1 track/song back at a time.

Listening to sirius, next button only goes 1 station at a time with the dash button.
 

LokiWolf

Staff member
Moderator
Joined
Apr 2, 2016
Posts
3,971
Reaction score
2,837
Location
Richmond VA
Tried a few more things. Popped a cd in and seek acts the same. Steering wheel and touch screen seek forward go one track/song at a time but the dash button advances 2 songs on a single press. All three back seek buttons only go 1 track/song back at a time.

Listening to sirius, next button only goes 1 station at a time with the dash button.

You have a physical button problem with the dash button.

Spray around the button with compressed air. If you have contact cleaner(non-lubricated), spray that. If not use Windex and make sure car is off, and no power. Spray around it. Move, wiggle, press the button many times. Wipe, then blow it out again. Test it.


Sent from my iPhone using Tapatalk Pro
 

mpc11

Well-Known Member
Joined
Dec 12, 2018
Posts
97
Reaction score
37
Location
MI
You have a physical button problem with the dash button.

Spray around the button with compressed air. If you have contact cleaner(non-lubricated), spray that. If not use Windex and make sure car is off, and no power. Spray around it. Move, wiggle, press the button many times. Wipe, then blow it out again. Test it.


Sent from my iPhone using Tapatalk Pro
Thanks. Never had that issue on 3.0 and I'm pretty meticulous about keeping my cars clean, but tried compressed air and contact cleaner (was leery of Windex) with lots of moving and pressing. No luck.

Searched around then ended up posting on cyan labs community forum. Cyan labs replied pretty quickly saying known issue on certain vehicles. Didn't mention anything further though.

Maybe next update they will figure it out. Thanks for your reply.
 

LokiWolf

Staff member
Moderator
Joined
Apr 2, 2016
Posts
3,971
Reaction score
2,837
Location
Richmond VA
Thanks. Never had that issue on 3.0 and I'm pretty meticulous about keeping my cars clean, but tried compressed air and contact cleaner (was leery of Windex) with lots of moving and pressing. No luck.

Searched around then ended up posting on cyan labs community forum. Cyan labs replied pretty quickly saying known issue on certain vehicles. Didn't mention anything further though.

Maybe next update they will figure it out. Thanks for your reply.

Interesting! Not having that issue on either of my 2020’s on 20196.

Good to know it is known...I honestly never use the one on the dash other than to force a reboot. Had to test it last night on mine, just to see.


Sent from my iPhone using Tapatalk Pro
 

mpc11

Well-Known Member
Joined
Dec 12, 2018
Posts
97
Reaction score
37
Location
MI
Interesting! Not having that issue on either of my 2020’s on 20196.

Good to know it is known...I honestly never use the one on the dash other than to force a reboot. Had to test it last night on mine, just to see.


Sent from my iPhone using Tapatalk Pro
Thanks for checking! I updated 2-3 weeks ago, but just noticed it for the first time yesterday as I rarely use that button too. But I don't like things not working now that I know about it! lol.
 

5280tunage

Full Access Members
Joined
Sep 17, 2019
Posts
1,875
Reaction score
1,154
Location
colorado
Don't even get me started on the Android Auto issues right now with this version (20196) and current AA on Android 11. Now, if I shut off the car with the phone plugged in, using an AA app (i.e. Pandora or DI.FM), and subsequently get back in and start the car, the screen is blank. Completely blank, nothing works after the ford logo, until I unplug the phone. What crap. So I either have to keep the car on accessory power when I leave and get back in, or I have to unplug the phone when I get out, and plug it in after the head unit has booted successfully. Even if I plug it in real fast before the stereo boots up completely, it often has the same issue.

Also, many AA apps now require that I press play or launch them twice before they start working. What a mess.
 

LokiWolf

Staff member
Moderator
Joined
Apr 2, 2016
Posts
3,971
Reaction score
2,837
Location
Richmond VA
Don't even get me started on the Android Auto issues right now with this version (20196) and current AA on Android 11. Now, if I shut off the car with the phone plugged in, using an AA app (i.e. Pandora or DI.FM), and subsequently get back in and start the car, the screen is blank. Completely blank, nothing works after the ford logo, until I unplug the phone. What crap. So I either have to keep the car on accessory power when I leave and get back in, or I have to unplug the phone when I get out, and plug it in after the head unit has booted successfully. Even if I plug it in real fast before the stereo boots up completely, it often has the same issue.

Also, many AA apps now require that I press play or launch them twice before they start working. What a mess.

Just for clarity, these issues appear to have nothing to do with Sync 20196. There is actually supposedly a fix in 20196 to resolve a call issue in 11's AA with Sync. These issues are being reported on MANY head units from many manufacturers.

https://9to5google.com/2020/09/13/android-11-auto-issues/

https://support.google.com/androidauto/thread/2475001?hl=en

Have you Master Reset your Sync? Have you removed the phone in both BT, and AA and added it back? It sounds like you are doing wired AA, I haven't played with it, but supposedly 11's AA gives all phones Wireless AA? I personally don't have Android, so don't get a chance to play with it.
 

5280tunage

Full Access Members
Joined
Sep 17, 2019
Posts
1,875
Reaction score
1,154
Location
colorado
Yup, done master resets more than once, removed the phone from BT etc. and yes, it's wired. While 11 supports wireless AA, the Expedition doesn't yet (or at least its not on any of the compatible lists yet.

And I get it, AA is buggy and lots of reported issues, but the issue of for example the screen being completely blank and NOTHING working after a vehicle restart was happening prior to Android 11, and only happened once I upgraded to 20196. Prior versions didn't experience that issue. Call issues, yes, but not that issue. So it's a mix of things for sure.
 

Astro

Member
Joined
Apr 11, 2018
Posts
5
Reaction score
4
Location
Texas
New to this thread but I've read a decent amount. I have a 2018 Platinum and until today I was on the stock 17200something build, but Ford prompted an update in my app so I downloaded and installed 19205 successfully directly from their site. I see the Cyanlabs site and am familiar with what to do, but am nervous going to some of the more recent builds as I'm seeing things like bluetooth or USB issues. It looks like 20196 fixed some of that. I'm just wondering if there's any other 18 Expedition owners that have upgraded to 20196 and it works fine. Trying to avoid how my wife's Toyota entune system was when it locked up repeatedly as the Ford works flawlessly currently.
 

Lou Hamilton

Full Access Members
Joined
Nov 28, 2019
Posts
939
Reaction score
640
Location
Maryland
Anyone else get a maps update notification?

Wondering what it is.

I am on 3.4 19274.


Sent from my iPhone using Tapatalk
 

LokiWolf

Staff member
Moderator
Joined
Apr 2, 2016
Posts
3,971
Reaction score
2,837
Location
Richmond VA
Anyone else get a maps update notification?

Wondering what it is.

I am on 3.4 19274.


Sent from my iPhone using Tapatalk

Lou it is the Map Data update reminder. Ford puts the message out periodically, just cause. It does not mean there was actually a new data release. Most current Map Data out there is still 1-19. I haven’t seen anymore recent.

I actually downloaded the files after the notification this week, since Ford doesn’t tell you what you are going to be downloading. It was 1-19. I checked the Data files.

As far as 3.4 there is a newer revision. 20196 is the newest, Ford is pushing 20136 seems to be the version most 2020’s built recently are coming with.


Sent from my iPhone using Tapatalk Pro
 

LokiWolf

Staff member
Moderator
Joined
Apr 2, 2016
Posts
3,971
Reaction score
2,837
Location
Richmond VA
New to this thread but I've read a decent amount. I have a 2018 Platinum and until today I was on the stock 17200something build, but Ford prompted an update in my app so I downloaded and installed 19205 successfully directly from their site. I see the Cyanlabs site and am familiar with what to do, but am nervous going to some of the more recent builds as I'm seeing things like bluetooth or USB issues. It looks like 20196 fixed some of that. I'm just wondering if there's any other 18 Expedition owners that have upgraded to 20196 and it works fine. Trying to avoid how my wife's Toyota entune system was when it locked up repeatedly as the Ford works flawlessly currently.

19205 is a 3.0 build number, not 3.4.

20196 is a 3.4 build number. Different revision all together.

I was running 3.4 on a 2016 Edge and 17 Expedition before I traded them with no issues.

Ford will never take your 2018 to 3.4 officially. 3.0 19205 is as far as it will go doing updates from Ford.

If you use CyanLabs installer though you can go to 3.4 20196 and the newest Maps.




Sent from my iPhone using Tapatalk Pro
 

Lou Hamilton

Full Access Members
Joined
Nov 28, 2019
Posts
939
Reaction score
640
Location
Maryland
Lou it is the Map Data update reminder. Ford puts the message out periodically, just cause. It does not mean there was actually a new data release. Most current Map Data out there is still 1-19. I haven’t seen anymore recent.

I actually downloaded the files after the notification this week, since Ford doesn’t tell you what you are going to be downloading. It was 1-19. I checked the Data files.

As far as 3.4 there is a newer revision. 20196 is the newest, Ford is pushing 20136 seems to be the version most 2020’s built recently are coming with.


Sent from my iPhone using Tapatalk Pro

My map data is NA 1 18.

So, I guess I will update it. Then again, I may go through the effort to update my whole build to 20196.

I think my previous hesitation has been that it was a more complicated update since I was on 19274. Is that still the case — something about downgrading, rebuilding something, then installing fresh? I thought I read I would lose my custom settings (not ForScan, but anything I changed in the Settings menu. Is that still the case?)


Sent from my iPad using Tapatalk
 

mcb345

Full Access Members
Joined
Oct 11, 2020
Posts
210
Reaction score
81
Location
Nashville, TN
I haven’t read through all the pages of this post but can someone share where I can download 20196 to a USB? I typed in my VIN and Ford obviously doesn’t offer that dow load to me since I’m on sync 3.0.

also, is this a wise download for a 2019 model or am I barking up the wrong tree?
 

Tomurphjr

Active Member
Joined
Jun 15, 2012
Posts
28
Reaction score
2
Location
Newport News, VA
Thanks all, enjoyed reading this thread. Download the app to my pc and did the update. I kept reading the need for 2 or 3 usb sticks. For me, all I needed was one, but everything went as smooth as possible with my stick and one set of files dumped to it.
 
Last edited:

Gumby

Full Access Members
Joined
Jun 5, 2019
Posts
496
Reaction score
238
Location
Beaumont, Alberta
I haven’t read through all the pages of this post but can someone share where I can download 20196 to a USB? I typed in my VIN and Ford obviously doesn’t offer that dow load to me since I’m on sync 3.0.

also, is this a wise download for a 2019 model or am I barking up the wrong tree?
Go to the first page of this thread and the link to CYAN LABS is there. I have a 2018 which was sporting Sync 3.0. I did the full reformat and updated with the most recent version and maps. It took about 45 mins or so but it was fine. I have updated the system (not the maps) twice since and no issues.

For me 20196 fixed the "BAD USB CABLE" message too. Even though the cable was fine and worked every time.
 
Top