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
17s have 2.2 from the factory. 16s probably will never get the update ota because of the expectation of gaining carplay based on early marketing. It may end up available to download with plenty of disclaimers.
This is for all 8" sync3 trucks. 15s and early 16s (did early 16s have mft/sync2?) that have the 8" sync2 will never get these capabilities, but the confusing thing to some is that their software version is 3.x.
This is for all 8" sync3 trucks. 15s and early 16s (did early 16s have mft/sync2?) that have the 8" sync2 will never get these capabilities, but the confusing thing to some is that their software version is 3.x.
Last edited by stowaway; Apr 13, 2017 at 06:44 PM.
17s have 2.2 from the factory. 16s probably will never get the update ota because of the expectation of gaining carplay based on early marketing. It may end up available to download with plenty of disclaimers.
This is for all 8" sync3 trucks. 15s and early 16s (did early 16s have mft/sync2?) that have the 8" sync2 will never get these capabilities, but the confusing thing to some is that their software version is 3.x.
This is for all 8" sync3 trucks. 15s and early 16s (did early 16s have mft/sync2?) that have the 8" sync2 will never get these capabilities, but the confusing thing to some is that their software version is 3.x.
YEAH BABY!!! I figured it out and now at v2.2 and CarPlay is working!!!
So, in my 1st post I mentioned that after I installed File1 successfully I installed File2 and it would not start and I assumed I had to start over. I did instert File2 in a 2nd time and it did not run again and it made me think I needed to try again from the beginning.
So today when I tried it AGAIN it failed with the error "wrong version or no disk space". THEN IT HIT ME, maybe it was looking for File2 and BOOM in 5 minutes the install was completed and I popped in my USB module and had maps up on the 8 in touch screen.
I must have tried to install File1 20 times with 10 different flash drives, FAT32 and exFAT, Windows and Macbook.
Thanks for all the input, I hope this helps someone else.
So, in my 1st post I mentioned that after I installed File1 successfully I installed File2 and it would not start and I assumed I had to start over. I did instert File2 in a 2nd time and it did not run again and it made me think I needed to try again from the beginning.
So today when I tried it AGAIN it failed with the error "wrong version or no disk space". THEN IT HIT ME, maybe it was looking for File2 and BOOM in 5 minutes the install was completed and I popped in my USB module and had maps up on the 8 in touch screen.
I must have tried to install File1 20 times with 10 different flash drives, FAT32 and exFAT, Windows and Macbook.
Thanks for all the input, I hope this helps someone else.
Last edited by meterman87; Apr 13, 2017 at 09:34 PM.
YEAH BABY!!! I figured it out and now at v2.2 and CarPlay is working!!!
So, in my 1st post I mentioned that after I installed File1 successfully I installed File2 and it would not start and I assumed I had to start over. I did instert File2 in a 2nd time and it did not run again and it made me think I needed to try again from the beginning.
So today when I tried it AGAIN it failed with the error "wrong version or no disk space". THEN IT HIT ME, maybe it was looking for File2 and BOOM in 5 minutes the install was completed and I popped in my USB module and had maps up on the 8 in touch screen.
I must have tried to install File1 20 times with 10 different flash drives, FAT32 and exFAT, Windows and Macbook.
Thanks for all the input, I hope this helps someone else.
So, in my 1st post I mentioned that after I installed File1 successfully I installed File2 and it would not start and I assumed I had to start over. I did instert File2 in a 2nd time and it did not run again and it made me think I needed to try again from the beginning.
So today when I tried it AGAIN it failed with the error "wrong version or no disk space". THEN IT HIT ME, maybe it was looking for File2 and BOOM in 5 minutes the install was completed and I popped in my USB module and had maps up on the 8 in touch screen.
I must have tried to install File1 20 times with 10 different flash drives, FAT32 and exFAT, Windows and Macbook.
Thanks for all the input, I hope this helps someone else.
Regarding Ford's position on the matter, I can't imagine there are technical issues remaining with the update since so many people on this forum have updated using the current 2.2 version software. I doubt anyone at Ford is working to resolve this issue so don't hold your breath waiting. They will release the official update when it make business sense to do so. US auto sales are slowing which has to be partially to blame for Ford's delays.
a) Ford's network couldn't handle thousands of trucks trying to download a big update at once. Staged release would have helped, but not solved this.
b) There's a known issue with the built-in update logic. Those of us that updated with the flash drive, we had to do it in two phases. Imagine what happens when it updates partially and the owner drives out of range or has a glitch. It would overwhelm their support network (dealers customer service, etc.).
c) Licensing. Android (google)/Apple aren't charitable organizations. I honestly don't know how all the manufacturer licensing works, but it could be a factor.
d) Hardware. There might be a slight variation in the Sync hardware that poses a known problem. I find this the least likely, but still a possibility.
e) The update itself. We're doing it via USB. It might just be too big to work properly OTA. Corruption or local cache storage of it might just prevent it.
f) If E is true, then that would mean dealers could do it locally. And that might be a fight with ford dealers. Dealers would charge hourly, customers get mad, and service departments get bogged down updating a bunch of vehicles.
g) If G is true, then why not just let people download to USB sticks and update themselves? Well, frankly people are stupid.....
Being high level IT at a very large global company, I'll offer my hypothesis on this. Ford didn't release OTA because they simply weren't ready for it. Whether it infrastructure or planning, it's the most reasonable explanation. My guess is that one or more of the following were true.
a) Ford's network couldn't handle thousands of trucks trying to download a big update at once. Staged release would have helped, but not solved this.
b) There's a known issue with the built-in update logic. Those of us that updated with the flash drive, we had to do it in two phases. Imagine what happens when it updates partially and the owner drives out of range or has a glitch. It would overwhelm their support network (dealers customer service, etc.).
c) Licensing. Android (google)/Apple aren't charitable organizations. I honestly don't know how all the manufacturer licensing works, but it could be a factor.
d) Hardware. There might be a slight variation in the Sync hardware that poses a known problem. I find this the least likely, but still a possibility.
e) The update itself. We're doing it via USB. It might just be too big to work properly OTA. Corruption or local cache storage of it might just prevent it.
f) If E is true, then that would mean dealers could do it locally. And that might be a fight with ford dealers. Dealers would charge hourly, customers get mad, and service departments get bogged down updating a bunch of vehicles.
g) If G is true, then why not just let people download to USB sticks and update themselves? Well, frankly people are stupid.....
a) Ford's network couldn't handle thousands of trucks trying to download a big update at once. Staged release would have helped, but not solved this.
b) There's a known issue with the built-in update logic. Those of us that updated with the flash drive, we had to do it in two phases. Imagine what happens when it updates partially and the owner drives out of range or has a glitch. It would overwhelm their support network (dealers customer service, etc.).
c) Licensing. Android (google)/Apple aren't charitable organizations. I honestly don't know how all the manufacturer licensing works, but it could be a factor.
d) Hardware. There might be a slight variation in the Sync hardware that poses a known problem. I find this the least likely, but still a possibility.
e) The update itself. We're doing it via USB. It might just be too big to work properly OTA. Corruption or local cache storage of it might just prevent it.
f) If E is true, then that would mean dealers could do it locally. And that might be a fight with ford dealers. Dealers would charge hourly, customers get mad, and service departments get bogged down updating a bunch of vehicles.
g) If G is true, then why not just let people download to USB sticks and update themselves? Well, frankly people are stupid.....
Being high level IT at a very large global company, I'll offer my hypothesis on this. Ford didn't release OTA because they simply weren't ready for it. Whether it infrastructure or planning, it's the most reasonable explanation. My guess is that one or more of the following were true.
a) Ford's network couldn't handle thousands of trucks trying to download a big update at once. Staged release would have helped, but not solved this.
b) There's a known issue with the built-in update logic. Those of us that updated with the flash drive, we had to do it in two phases. Imagine what happens when it updates partially and the owner drives out of range or has a glitch. It would overwhelm their support network (dealers customer service, etc.).
c) Licensing. Android (google)/Apple aren't charitable organizations. I honestly don't know how all the manufacturer licensing works, but it could be a factor.
d) Hardware. There might be a slight variation in the Sync hardware that poses a known problem. I find this the least likely, but still a possibility.
e) The update itself. We're doing it via USB. It might just be too big to work properly OTA. Corruption or local cache storage of it might just prevent it.
f) If E is true, then that would mean dealers could do it locally. And that might be a fight with ford dealers. Dealers would charge hourly, customers get mad, and service departments get bogged down updating a bunch of vehicles.
g) If G is true, then why not just let people download to USB sticks and update themselves? Well, frankly people are stupid.....
a) Ford's network couldn't handle thousands of trucks trying to download a big update at once. Staged release would have helped, but not solved this.
b) There's a known issue with the built-in update logic. Those of us that updated with the flash drive, we had to do it in two phases. Imagine what happens when it updates partially and the owner drives out of range or has a glitch. It would overwhelm their support network (dealers customer service, etc.).
c) Licensing. Android (google)/Apple aren't charitable organizations. I honestly don't know how all the manufacturer licensing works, but it could be a factor.
d) Hardware. There might be a slight variation in the Sync hardware that poses a known problem. I find this the least likely, but still a possibility.
e) The update itself. We're doing it via USB. It might just be too big to work properly OTA. Corruption or local cache storage of it might just prevent it.
f) If E is true, then that would mean dealers could do it locally. And that might be a fight with ford dealers. Dealers would charge hourly, customers get mad, and service departments get bogged down updating a bunch of vehicles.
g) If G is true, then why not just let people download to USB sticks and update themselves? Well, frankly people are stupid.....





