View Poll Results: How many of you have utilized the SYNC3 update?
Upgraded
627
69.05%
Choosing to wait for Ford
281
30.95%
Voters: 908. You may not vote on this poll
Current SYNC 3 and CarPlay/Android Auto Information
#4311
Just Another Member
On the plus side I have learned a lot: how to find and understand my current SYNC configuration in OASIS/PTS, how to read the product, version and build number from the .lst file, learned how these download packages are put together and what each of the files does (for non-nav), learned how to control the order of install/execution of each of the data files. I just can't get it working perfectly like I had it with build 17194.
But I can live without Gracenote and with that annoying wifi popup for a while I guess...
Last edited by Theocoog; 10-25-2017 at 08:46 PM.
#4312
It's my first day
Originally Posted by Sam Kohrs
Forgive me if this is already answered in here. I have searched and have not been able to find the answer. I have a 2016 F-150 Lariat I just bought new from the dealer last month and it came with Sync 3 Version 2.0 on it. I just ordered the new USB hub (HC3Z-19A387-B) and should be getting it any day now. Does anyone know if I need to update my software to version 2.2 to use CarPlay? The Ford Owner's website says it is up to date, but all the posts I am reading talk about needing version 2.2. Will it work with 2.0 or should I download an update somewhere. Thanks for your input.
#4313
Senior Member
iTrader: (14)
Yep. Made sure USB and Bluetooth devices were removed/deleted and did a master master reset each time. Even pulled the Sync fuse and let it sit for 1/2 hour a couple of times. Seriously, I have spent a lot of time on this.
On the plus side I have learned a lot: how to find and understand my current SYNC configuration in OASIS/PTS, how to read the product, version and build number from the .lst file, learned how these download packages are put together and what each of the files does (for non-nav), learned how to control the order of install/execution of each of the data files. I just can't get it working perfectly like I had it with build 17194.
But I can live without Gracenote and with that annoying wifi popup for a while I guess...
On the plus side I have learned a lot: how to find and understand my current SYNC configuration in OASIS/PTS, how to read the product, version and build number from the .lst file, learned how these download packages are put together and what each of the files does (for non-nav), learned how to control the order of install/execution of each of the data files. I just can't get it working perfectly like I had it with build 17194.
But I can live without Gracenote and with that annoying wifi popup for a while I guess...
OASIS on the other hand anyone can buy a subscription to it.
#4314
It's my first day
Build 17276 got rid of the wifi pop up for me. While build 17194 caused it. I think it was my install method and not the update itself.
17276 is the first update where I did both a master reset before and after the update to clear any residual cache. After the install I also force reset the APIM twice with ForScan.
Forced module reset is not the same as a master reset.
I know people first hand who installed 17194 and also ended up with the wifi pop up prompts. Simply installing 17276 over top of that did not eliminate the wifi prompts for them and those people used my file on my usb key (Im away for
work and left my usb drive with a friend). They did not reset the APIM with ForScan and whether they did a master reset or not is questionable.
So I think it comes down to the process you undertake to load an update and not the actual package itself.
17276 is the first update where I did both a master reset before and after the update to clear any residual cache. After the install I also force reset the APIM twice with ForScan.
Forced module reset is not the same as a master reset.
I know people first hand who installed 17194 and also ended up with the wifi pop up prompts. Simply installing 17276 over top of that did not eliminate the wifi prompts for them and those people used my file on my usb key (Im away for
work and left my usb drive with a friend). They did not reset the APIM with ForScan and whether they did a master reset or not is questionable.
So I think it comes down to the process you undertake to load an update and not the actual package itself.
#4315
It's my first day
now the only prompt I receive when I turn on the truck is a little message for sync connect which says: “the NSA is spying on your passengers please let them be aware, if they denounce real time vehicle tracking, kick them outâ€.
#4316
Just Another Member
Build 17276 got rid of the wifi pop up for me. While build 17194 caused it. I think it was my install method and not the update itself.
17276 is the first update where I did both a master reset before and after the update to clear any residual cache. After the install I also force reset the APIM twice with ForScan.
Forced module reset is not the same as a master reset.
I know people first hand who installed 17194 and also ended up with the wifi pop up prompts. Simply installing 17276 over top of that did not eliminate the wifi prompts for them and those people used my file on my usb key (Im away for
work and left my usb drive with a friend). They did not reset the APIM with ForScan and whether they did a master reset or not is questionable.
So I think it comes down to the process you undertake to load an update and not the actual package itself.
17276 is the first update where I did both a master reset before and after the update to clear any residual cache. After the install I also force reset the APIM twice with ForScan.
Forced module reset is not the same as a master reset.
I know people first hand who installed 17194 and also ended up with the wifi pop up prompts. Simply installing 17276 over top of that did not eliminate the wifi prompts for them and those people used my file on my usb key (Im away for
work and left my usb drive with a friend). They did not reset the APIM with ForScan and whether they did a master reset or not is questionable.
So I think it comes down to the process you undertake to load an update and not the actual package itself.
My dealer said they'd reload 2.2 for $100, but if they use the USB method they'll fail too - I tried reloading 2.2 using factory OEM files. No luck. And so the APIM reset looks more appealing now.
What would be sweet is if the experts on this created a master "how-to", sort of like how Livnitup had his Forscan tutorial.
#4318
Just Another Member
Please let us know how that goes. Good luck! I'll do the same, tomorrow if I get the time.
#4320
Senior Member
Android Auto being much snappier is what I seen mentioned most often, not sure what else. I'm on 2.2 though.