akirby

That was on the pre-2011s with Nav. The Nav had a 10 gb hard drive partition. You could only load it from an audio CD. With the 2011 you can only load songs to a mp3 player or a usb drive (from a computer - not from the vehicle).

Ford typically does cold testing in Yellowknife among other places. It is possible they didn't do enough testing but it's more likely that something changed late in the program or it's just a manufacturing tolerance issue.

That does meet the Ford spec (according to Amsoil) so it should be ok.

The bluetooth interface specs are not Microsoft technology. There is a bluetooth standard that all mfrs must adhere to and implement correctly for the interface to work. If either side doesn't implement the standard correctly then it won't work. The fact that some phones do work just fine with Sync generally proves that Ford implemented their interface correctly and the problem is on the cell phone.

This is what I've been trying to explain to people who insist on blaming Ford because the cell phone mfrs didn't implement their bluetooth interfaces correctly. Thanks for posting it.

But those interfaces only do stereo audio, right? It's a different ballgame when you start moving different types of data like phonebook contacts, playlists, photots, etc. The Bluetooth profiles for this advanced functionality is quite complicated and unfortunately Ford is on the bleeding edge here which just magnifies any Apple issues.

Only the ones who spout wild conspiracy theories and incorrectly accuse Ford of deception. xphile has issues just like you and overtheedge but he's not overreacting.

Definitely synthetic - it will flow better at those extremes. Ford synthetic 5W-20 should work fine. If you can find a 0-W20 that meets the Ford spec in the owner's manual that would probably work even better. FYI - the Ford factory oil is a synthetic blend which is better than regular dino oil.

I'd stop at step 1 but that's just me. The Edge's AWD system is not really meant for heavy off-roading. The Explorer would be a much better choice unless you're just going for looks.

I was trying not to post this but you leave me no choice...........

MKX - adaptive HIDs

The Edge Sport 3.7L is the same basic engine as the Mustang 3.7L V6 (it's just turned sideways in the Edge........)

Absolutely not. Where does Ford advertise that all these features work with your iPhone? For the 100th time (at least): FORD has absolutely no control over cell phones. They don't control how the cell phone mfr or service provider implement bluetooth. They never have and they never will. All Ford can do is provide the INDUSTRY STANDARD bluetooth profile interface and ask the cell phone companies to comply. Early on syncmyride.com actually did hands-on testing of cell phones to figure out what worked and what didn't and they published that to help customers. But think about how many different cell phones and OSes are on the market right now and how quickly new ones appear. It would be foolish to think Ford could do extensive testing on each and every new phone and new os version from every provider and keep it up to date. When you buy a bluetooth headset, does it list every single phone that it works with? Of course not. This is no different. You're just upset because your new toy doesn't work the way you assumed it would. Ford has to take the blame for the system locking up - no interfacing device should be allowed to cause that. But you can only blame Apple for the iphone not working with Sync the way you want. And I don't believe Ford ever advertised or implied that all features would work with an Iphone. I think you just assumed that (incorrectly). So no - there is absolutely no deception here. There is a phone incompatibility issue that Apple has to resolve and there is a sync problem that Ford is working on as we speak. You say it has to be software, but if it was software then a reload from scratch should fix it, at least temporarily. I think you'll see a fix within the next 2-3 weeks and it could be hardware or software or both.

Several Ford employees have already said that it won't work. The Nav software isn't installed unless you factory order the Nav and the SD card is tied to the software on a per vehicle basis. Anybody telling you it will work is just trying to get your money. So unless they can code the software to the SD card and load it they're feeding you BS (not the other way around).

It will. How much was it?

British slang.......it means "and there you have it".

Yes, they screwed up whether it was a last minute hardware or software change or lack of testing or (more likely) they chose to ship it with know bugs planning to fix it within a few weeks. But a class action lawsuit won't get it fixed any faster.

Maybe they didn't replace the pads correctly or used the wrong kind. I'd have it checked by a good mechanic just to be safe. They shouldn't be making noise when they're hot.

Believe it or not the Ford ESP program will do a free replacement as long as you have at least 3/32" tread.

Actually this program (if it is the Ford ESP tire and wheel coverage) WILL cover that type of damage. It's more like an insurance policy than a warranty. It's still priced way too high though.

Yeah....well HE started it!

Sync or MyTouch? They're different. There is no MySync option.

It's common on all vehicles from time to time. If this only occurs the first 2 or 3 times you use the brakes and then goes away then it's normal. If it starts after the first few times and continues then something is wrong. Have the pads and rotors checked. The pads could be work down and grinding into the rotor. Either way new pads and/or turned rotors should fix it.

No, I'd be telling the same story. Blame Ford for buggy software but don't blame Ford because certain cellphone mfrs haven't fully implemented Bluetooth. You're the only one who wants to accuse Ford of deceptive advertising which isn't true.

BTW - if you want to bash Ford then bash them for releasing the MyTouch software before it was ready. It's way too buggy and they released it too soon. That is 100% Ford's fault.