ShelbyGT350 Posted January 1, 2018 Report Share Posted January 1, 2018 it's 2016 Edge Ti 3.5 AWD thanks no you can get part number without taking it out..what car do you have? GJ7Z-19A397-B Source: http://www.fordedgeforum.com/topic/20468-sync-3-2016-upgrade-to-carplay/?p=158979 Quote Link to comment Share on other sites More sharing options...
RonRN18 Posted January 2, 2018 Report Share Posted January 2, 2018 you could try taking the VIN and popping it in ford.owner.com and checking update there, wifi option is not reliable after 2.2 was released The site has a problem with making the update available. I just chatted with a representative that said it has been down for some time and no ETA for the site to allow users to download the v2.3 firmware. Quote Link to comment Share on other sites More sharing options...
ShelbyGT350 Posted January 2, 2018 Report Share Posted January 2, 2018 The site has a problem with making the update available. I just chatted with a representative that said it has been down for some time and no ETA for the site to allow users to download the v2.3 firmware. dont worry about the site, write down the part number and go to the nearest ford dealer parts department and order the part Quote Link to comment Share on other sites More sharing options...
ben senise Posted January 3, 2018 Report Share Posted January 3, 2018 I installed 3.0. Seems to work but I haven't spent any time with it. I noticed a slight difference in some of the icons but that's it so far. I'm mostly anxious to see if it stops Android Auto stop crashing. I moved from my Pixel XL to a Pixel 2 XL and it has still been crashing. It's a royal PITA when you're in busy traffic and the google maps navigation disappears. Interesting side note though; i tried installing with a USB 3 memory stick and it wouldn't go. I re-copied the files onto a USB 2 stick and it worked right away. Quote Link to comment Share on other sites More sharing options...
ShelbyGT350 Posted January 3, 2018 Report Share Posted January 3, 2018 Android Auto has never crashed since it was first launched in 2.2, Im 99% sure its a phone problem, try different phone..im on sony xperia, works flawlessly every time Quote Link to comment Share on other sites More sharing options...
punch-card Posted January 3, 2018 Report Share Posted January 3, 2018 (edited) I am running a Pixel XL on Project Fi, and have V3.0 on my sync, and I have not had crashes with AA, Waze restarts occasionally, but not AA itself. I use it daily from work. Edited January 3, 2018 by punch-card Quote Link to comment Share on other sites More sharing options...
ben senise Posted January 3, 2018 Report Share Posted January 3, 2018 Android Auto has never crashed since it was first launched in 2.2, Im 99% sure its a phone problem, try different phone..im on sony xperia, works flawlessly every time Thanks for your data point. My AA on Sync has been crashing since I started using it after installing v2.2. let's see what happens now that i've installed v3.0 I am running a Pixel XL on Project Fi, and have V3.0 on my sync, and I have not had crashes with AA, Waze restarts occasionally, but not AA itself. I use it daily from work. did you run AA on your Pixel on Sync v2.2? I've done various master resets on Sync and I've wiped my Pixel XL. Now I have a brand new Pixel 2 XL and having the same problem. Having changed phones, I'm less likely to think it's a phone problem. One thing I used to notice is that very often my bluetooth on Sync would turn off and the "button" on the display wouldn't slide over to the on position. Sometimes it would unfreeze after restarting the car and sometimes i had to do a reset. My guess is that this is related. I'm hoping that v3.0 will be better. we'll see. Quote Link to comment Share on other sites More sharing options...
ShelbyGT350 Posted January 3, 2018 Report Share Posted January 3, 2018 Thanks for your data point. My AA on Sync has been crashing since I started using it after installing v2.2. let's see what happens now that i've installed v3.0 did you run AA on your Pixel on Sync v2.2? I've done various master resets on Sync and I've wiped my Pixel XL. Now I have a brand new Pixel 2 XL and having the same problem. Having changed phones, I'm less likely to think it's a phone problem. One thing I used to notice is that very often my bluetooth on Sync would turn off and the "button" on the display wouldn't slide over to the on position. Sometimes it would unfreeze after restarting the car and sometimes i had to do a reset. My guess is that this is related. I'm hoping that v3.0 will be better. we'll see. sounds like the problem is on pixel series phones..try a different brand of phone Quote Link to comment Share on other sites More sharing options...
punch-card Posted January 4, 2018 Report Share Posted January 4, 2018 Thanks for your data point. My AA on Sync has been crashing since I started using it after installing v2.2. let's see what happens now that i've installed v3.0 did you run AA on your Pixel on Sync v2.2? I've done various master resets on Sync and I've wiped my Pixel XL. Now I have a brand new Pixel 2 XL and having the same problem. Having changed phones, I'm less likely to think it's a phone problem. One thing I used to notice is that very often my bluetooth on Sync would turn off and the "button" on the display wouldn't slide over to the on position. Sometimes it would unfreeze after restarting the car and sometimes i had to do a reset. My guess is that this is related. I'm hoping that v3.0 will be better. we'll see. Yes I ran it on V2.2 for about 4 months, I never had an issue. Do you have background apps running on your phone (aka facebook/twitter/...)? I have had issues in the past (not on pixel) where I quit using them on a phone. Quote Link to comment Share on other sites More sharing options...
RonRN18 Posted January 5, 2018 Report Share Posted January 5, 2018 The site has a problem with making the update available. I just chatted with a representative that said it has been down for some time and no ETA for the site to allow users to download the v2.3 firmware. Just FYI, I was finally able to download the new v2.3. A file that was 1.6 GB in size. I then formatted an 8 GB USB thumb-drive in exFAT format. I then unzipped the file "JL1T-14G381.zip" directly onto the thumb-drive. This created two files in the base directory and a subdirectory called "SyncMyRide" which had 7 gzipped files in it. I plugged the thumb-drive in my 2016 C-Max Energi and hit the start button. After a minute or two, I saw that it was updating the system. It restarted Sync a minute or two later. After yet another minute or two, it continued showing that the system was being updated. Finally, after about 15 minutes, the screen says that the update was complete and I could remove the USB device. I turned the car off and then restarted and verified I was now on v2.3. I did have issues trying to report the successful update. When completed, an XML file was placed in that "SyncMyRide" folder that Ford wanted me to upload. The website reported a failure in uploading the file, BUT oddly, it had successfully uploaded the file and now on the owner.ford.com website, it reports I have the latest Sync software. Quote Link to comment Share on other sites More sharing options...
ShelbyGT350 Posted January 6, 2018 Report Share Posted January 6, 2018 good good so it worked out! Quote Link to comment Share on other sites More sharing options...
wjbultema Posted January 6, 2018 Report Share Posted January 6, 2018 Does anyone have any information on when the Sync 3 update page will be fixed? I keep getting a "system error" message when I click on the request download button. Been like that for over 2 weeks. Want to update the Sync 3 in my F-150 XLT and I cannot get anything to download. Did a chat session a week ago with Ford Help and they said they were aware of this issue,that it affected all ford owners, and their IT people were working on the problem. Site is working again. Just downloaded V2.3 Quote Link to comment Share on other sites More sharing options...
ben senise Posted January 7, 2018 Report Share Posted January 7, 2018 Anyone with Android Auto want to try an experiment? I upgraded to v3.0 and had my Pixel 2 XL connected and running Android Auto. I had a few drives totalling a couple of hours and I did not have a crash. Ah-ha i thought, v3.0 fixed it! I usually set Sync's display mode to "night" because I like the dark look even during the day. I hadn't done that for the first two hours or so. I decided to do it and bang, within a few minutes, AA crashed. Plugged it in again and crash. So I set Sync's display mode back to "Auto" where it is by default and drove the remaining 20 minutes home with no crashes. The correlation here is really high. This would lead me to believe that somehow, the display mode is crashing AA. I will be doing a few hours driving on monday and will check it out again. If anyone here feels like living dangerously, put your sync's display mode on "Night" and see if your AA crashes and let us know. Quote Link to comment Share on other sites More sharing options...
ben senise Posted January 8, 2018 Report Share Posted January 8, 2018 Anyone with Android Auto want to try an experiment? I upgraded to v3.0 and had my Pixel 2 XL connected and running Android Auto. I had a few drives totalling a couple of hours and I did not have a crash. Ah-ha i thought, v3.0 fixed it! I usually set Sync's display mode to "night" because I like the dark look even during the day. I hadn't done that for the first two hours or so. I decided to do it and bang, within a few minutes, AA crashed. Plugged it in again and crash. So I set Sync's display mode back to "Auto" where it is by default and drove the remaining 20 minutes home with no crashes. The correlation here is really high. This would lead me to believe that somehow, the display mode is crashing AA. I will be doing a few hours driving on monday and will check it out again. If anyone here feels like living dangerously, put your sync's display mode on "Night" and see if your AA crashes and let us know. nevermind. i just drove for a while with sync's display setting to auto and my AA is crashing non-stop, every few minutes. it is effectively unuseable. i need to determine if it is the car or the phone. i need to find some kind of de-bugging method. open for suggestions if anyone has some. Quote Link to comment Share on other sites More sharing options...
NCEcoBoost Posted January 9, 2018 Report Share Posted January 9, 2018 Just FYI, I was finally able to download the new v2.3. A file that was 1.6 GB in size. I then formatted an 8 GB USB thumb-drive in exFAT format. I then unzipped the file "JL1T-14G381.zip" directly onto the thumb-drive. This created two files in the base directory and a subdirectory called "SyncMyRide" which had 7 gzipped files in it. I plugged the thumb-drive in my 2016 C-Max Energi and hit the start button. After a minute or two, I saw that it was updating the system. It restarted Sync a minute or two later. After yet another minute or two, it continued showing that the system was being updated. Finally, after about 15 minutes, the screen says that the update was complete and I could remove the USB device. I turned the car off and then restarted and verified I was now on v2.3. I did have issues trying to report the successful update. When completed, an XML file was placed in that "SyncMyRide" folder that Ford wanted me to upload. The website reported a failure in uploading the file, BUT oddly, it had successfully uploaded the file and now on the owner.ford.com website, it reports I have the latest Sync software. Thanks for the info. Glad SOMEONE has had success. I've done the same thing as you, FOUR TIMES (from mid-Nov to mid-Dec), and the system never did a thing. Turns out that Sync3 doesn't like USB3s, which is probably what my 16GB USB is. Talk about finicky! I'm headed to the dealer in a few weeks for my first service visit and am hoping they'll do it for me. Quote Link to comment Share on other sites More sharing options...
NCEcoBoost Posted January 9, 2018 Report Share Posted January 9, 2018 Well, after searching, I found the original packaging for my USB drive. It's a 2.0, not a 3.0. Hmmph...I guess I'll try one more time tomorrow. Maybe the January version will be better than the Nov/Dec versions. Quote Link to comment Share on other sites More sharing options...
NCEcoBoost Posted January 9, 2018 Report Share Posted January 9, 2018 Before I attempt the update again tomorrow, I thought I'd mention that the v.2.3 update that I just downloaded and unzipped is different from that reported above. I'm coming from v.2.2. My update is 2.16GB, not 1.6GB, and in addition to the two base files, there are 8 (not 7) unzipped files in the SyncMyRide folder. Could be that different vehicles get different updates or (eye roll), it might be that this is a how-shall-we-say "daily work-in-progress" by Ford. I'm chuckling now. Hope I'm not cussing tomorrow. Quote Link to comment Share on other sites More sharing options...
NCEcoBoost Posted January 10, 2018 Report Share Posted January 10, 2018 Don't ask, just don't ask. Said "indexing" when I put the USB in, then never did a blessed thing after that. Health Report didn't run either. When I pull up the FordPass app on the phone, it starts Android Auto instead. And then when I disable AA on the phone, FordPass indicates a system failure. This has gone from pathetic to worse. Quote Link to comment Share on other sites More sharing options...
NCEcoBoost Posted January 26, 2018 Report Share Posted January 26, 2018 FINALLY...SUCCESS! I upgraded to v.2.3 earlier today. Some observations: 1. The entire process took WAY longer than advertised by Ford and in this forum. About an hour, not including the report back to Ford. I guess this can vary by system&vehicle. 2. In my case, patience is the ultimate virtue. I did not know that the system was even updating for the first 10-15 minutes, since it never said so. I did see the USB light flashing, so I persisted. Then the screen finally announced "SYSTEM UPDATING" and I wanted to break out the champagne. 3. DO NOT ATTEMPT TO DO THIS WHILE DRIVING. In my case, I had to perform 2 ignition cycles DURING THE UPDATE, not including the final one. Heaven help you if you're on a freeway with lots of traffic at 60 mph. You're then screwed since it demands you do it within 2 minutes. Also, forget about reading a book while doing this. You have to quickly respond to requests and there are several. You need to stare at the screen the whole time. 4. While somewhat similar (in order of steps), my update was quite a bit different from the process on the owner.ford website and what anyone has said in here. 5. I had NO trouble reporting the update to Ford. 6. Based on this, the update to v.3.0 might take several days. I'd better plan on sleeping and eating in the car. Cheers! Quote Link to comment Share on other sites More sharing options...
ShelbyGT350 Posted January 27, 2018 Report Share Posted January 27, 2018 hey glad to hear it worked out!! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.