Not yet... Ford started using the 2017 Sync 3 units in the 2016 Ford F-150's starting with trucks built in July 2016... which is why they have the 2.0 update. Still waiting impatiently for the update for the Sync 3 units that were used in all the 2016 vehicles.

Still curious if anything is different hardware wise.

-
Aug 1 2016 3465 - 2016 F150/Edge/MKX Vehicles – SYNC 3 Software Version Differences Starting 3rd Quarter 2016

Some 2016 F150, Edge and MKX vehicles with SYNC 3 built beginning 3rd quarter 2016 may have 2.0 software that might present the customers with some new characteristics such as: a different display background, different sounding SYNC 3 voice prompts, or maybe equipped with Android Auto. This is an intentional change and no module should be condemned because of these differences. Flashing a module to a different software level due to this difference is not available at this time nor is it supported. Refer to the Owners Guide for the vehicle in question to understand the proper operation and functionality of the SYNC 3 system features. The SYNC version can be found in the Settings menu under General then About if needed for comparison of a like module. Also, the SYNC version can be confirmed via OASIS.

 

USB port module will be different. That's what previous 2016 trucks need for carplay.

there's already some other threads covering this topic.

 

Ford.com shows that for CarPlay, but Android Auto doesn't required new hardware

Ford.com only states software upgrade for Android Auto

 

It will require a new USB hub of sorts for Car Play (apple uses a special chip for security authentication of car play)... Android auto will work with existing hardware.

 

Well aware on Car Play... I wasn't talking about Car Play... I was referring to the actual internals of the APIM. There is a reason why it is taking a while for a software update that is already available lol.

 

Thanks for these posts. And thanks Livnit for confirming these are working on our trucks But I need some clarification .... what do you mean on/off status will be (or will not be) remembered with key off/on ? Are you saying they will stay (or not stay) enabled to be able to be on together ? Or something else ? I would like to set it so my fog lights are able to be on with my HBs.... and not have to worry about changing the program each time.

Also, for those of us new to this still, how long does it take for changes like these that are confirmed to be available and working to be updates by Forscan and become "plain English" / PIDs ? Still a bit un-trusting of myself to be changing the actual code lines......

 

What I meant by "remembered" is this: Say you have the switch in Auto and you have Lights on w/high beam & fogs and you turn off the vehicle. When you turn it back on it "remembers" your last setting and high beams & fogs will be on again. This isn't saying you can't then just turn them off when you get in the second time, just that it remembers your last setting.

When these new changes are found I email the developers with the things found and then at their discretion, they will send a new test build that will have these new features in the plain English area. Sometimes they are very quick with this and other times it takes longer. I try to send them a few new things found in a group so I'm not bugging them with every little thing found unless it's something significant.

Edit: Don't be afraid of the manual editing, it's easy and we're here to help if you run into problems. So long as you backup your modules like I discuss in post #1 in this thread, you'll have a quick & simple way to revert anything you do. By the way, this module backup should be done even if you only want to do the plain English method

 

Backing up all of the modules was the 1st thing I did, as advised in your first post !

Depending on our weekend and work.... I may try to set aside some time to play with the code "non-plain English" segments and see what I can do. I appreciate the assistance and support as I'm sure I will come up with questions simply by second guessing myself.

 

I prefer putting in the code. it comes in handy to see thing especially if doing ore the one address as 7D0-01-01 I like to see what changed and keep a running log of what I did on paper in case it crashes and I have to redo it all.

 

Agreed. I try to do it all manually and write down the OEM and modified entries on paper. It has worked flawlessly so far!