F150Limitedfan

According to some EU folks, some managed to get updates done by also getting one previous 2.2 file, if someone could just look inside this license file and tell us what the heck its looking for...this guy was getting LST_ERR04, and he had this autoinstall


autoinstall.lst

Item1 = License
Open1 = SyncMyRide \ JL7T-14G424-BA_87970.tar.gz
Item2 = Maps (EU)
Open2 = SyncMyRide \ JL7T-14G421-BA.tar.gz

Options = Delay, AutoInstall

then added this to make it a full complete package: HB5T-14G421-BD

EcoBeast2.7L

I tried this on my iphone x but it says you have to plug in the phone, can you tell me how you got it to work?

F150Limitedfan

android doesnt need to be plugged in

hawkinsjohn1

Forgive me if my question is a repeat. I'd rather not scan through 512 pages of comments.

I have a '16 F150...updated Sync 3 first of last year so that I could use Android Auto. FYI...you MUST use the OEM USB cable for Android Auto to work. I tried a cable I bought from Amazon and it would not work. You don't need to use a cable with Sync3 though...just when you want to use Android Auto. Not sure why because the phone is still connected via Bluetooth. Gotta be the dumbest thing ever.

Now the question is, are people experiencing Android Auto (AA for short going forward) running inconsistently? Start my truck, wait a second, plugin my phone and sometimes AA works, sometimes it doesn't. On some days, it will work right off the bat but if I switch it to Google Maps, start a navigation and Google Maps speaks, the "prompt" volume can be controlled but then I can't turn the main volume up or down. I have to unplug my phone in order to restart AA then it all works perfectly of the rest of the day.

As soon as Waze is available via the next Sync3 update, I will completely abandon AA until all the bugs are worked out. Now are these bugs specific to Sync3 or the AA app provided by Google or maybe a little bit of both???

Makes no sense that it works 90% of the time.

Julywizard

Awesome. Does it have to be the same year as mine or can it be newer one?

planetix

It may be sensitive to the cable but it doesn't have to be OEM, I use a third party with mine just fine. I don't have the problems you have though a couple times here and there I have to re-connect to get AA working after first connect. This is my experience with AA in general though, not just via Sync. It's not quite a fully baked product. If Waze/Sync 3 integration is truly good (voice, Spotify integration - which is already a Sync app - even turn directions in the cluster) I will probably ditch it as well. Note like most other Sync apps it is likely you'll need to plug it in too.

AA itself didn't support wireless (wifi+BT) until very recently. Some aftermarket HU are coming (Pioneer has one) that support it but it's a slow rollout on Google's part.

New F150's with the wifi-access points could in theory be updated to use it, but anyone's guess when or if that will happen. Same for wireless Carplay btw.

htownholditdown

I mean, kind of, yeah. I understand it being newer technology that they didn't have for 2015 models, but I don't think it's fair to have to pay ~$1,400 just to update the screen that I already have to be compatible for Apple Car Play. That seems a little extreme. My buddy was able to do it in his Tacoma for about $200.

jm061

iTrader: (2)

Your infotainment equipment (SYNC2/MFT) is completely different hardware. Its not updating...it is component replacement. SYNC2/MFT will never support CarPlay (at least as a Ford function). This is a topic for another thread however and there are threads explaining the MFT-->SYNC3 process.

TexasRebel05

same year would be best.
Make darn sure the nav option is the same.

TIGERLURES