l33

Those that want the update... http://www.madison86.com/mft/mft.htm Now here's the cool thing. The packages are signed by a Ford certificate BUT that covers the code... Ford have included in some of the packages resource files which are SWF (Flash) files for the whole user interface. I believe (I know a bit about this stuff) that this is our hole. I have decompiled some of the flash and sure enough... well... my thoughts here are that I could modify an existing flash file to CALL another new flash file that I can deploy in the update alongside the others. This would allow us to put calls into the Sync system (through the new flash file) that aren't usually exposed. Now this is a big job ahead, but I do think its possible. Certainly enabling things that are only available on the Lincoln on the Ford is easy (I remember in the current version the sound menu was different - this could be easily changed in the Ford package). Anyhow, I'll take a look and see what I can do. Should be fun. Edit: The more I look into this the more wide open this seems to be... I'm sure the zips that contain the resource files and the cab files are not signed in any way which allows us to modify the resources in there (not the cabs or pks files though). If that turns out to be true, a simple change to the SWF file is the gate into the core. Before I'd flash my car though, I'd want to make sure I could reflash or change the SWF file. I'm going to be looking at the update process to see if you can force a package to run again (even when the car is fully up to date). Also I'll be looking at the Sync Apps installer to see what happens there. Maybe some way of just updating an SWF file from USB without running through a whole package update even... who knows. In this update there are a couple of SWF files that aren't used as far as I can tell. Look like test ones (such as GenericApp), there could be some interesting stuff in there. There is an opportunity here to do something cool I think without risking the rest of the system - for example, small modification to one of the existing SWFs to include a tiny button that launches a different SWF file ... our SWF file. That could potentially carry many things ;-) Now, of course, I could be wrong about all of the above! Second Edit: So I said I could be wrong. So shortly after the excitement, I have found something that might kill the plan. It appears that inside the cab file it names the payload in the resources folder... then the dreaded line: % s : Hash checking of files failed . This implies to me that they *do* in fact check the resource files and hash the whole package. If thats true thats a massive spanner in the works. Not going to give up though! I'm now moving my progress over to the Ford sync forum website as I think its more relevant there: http://fordsyncforum.com/index.php?/topic/542-frown-on-hack-posts/page__st__40

I can only say it would surprise me that Microsoft would do this. This is an area I have good knowledge of and unless someone can tell us some proper facts about whats going on its still just hearsay. Microsoft doing something for Ford inhouse would be extremely rare indeed. They would not want the support burden etc that would come with it which is why Microsoft Embedded is a channel business. They have partners that they want to take on this type of work. BSquare are a partner but not only that... they happen to run some of Microsofts licensing programmes for them too (they also happen to license Flash Lite for Adobe ;-)). This "rewrite" could easily be something I've suggested which is an upgrade from Auto 4 to Automotive 7. Remember that with 4, there was a very basic interface and this is why Ford/Bsquare chose to use Adobe Flash as their front end. With 7 that goes away as Microsoft implemented a Silverlight interface which is easily customizable... it should perform a lot better. The whole underlying platform changed between Auto 4 and Automotive 7. Its a significant improvement and could be described by non technical people as a "rewrite". My feeling is whats probably happening is development is still taking place with BSquare heavily involved, supported by a team of Microsoft folks from the Partner Solutions Team. Also note that development is now taking place at the "Ford Telematics Competency Center" not "BSquare". This is a dedicated team/office but is run by Bsquare using Fords money. Its basically means "Ford employees" but without them being on Ford payroll - many reasons for that. We have to wait and see I guess. I could be wrong but I don't think I am.... If I am I will happily admit it - I'm trying to give everyone some perspective here with background knowledge of things I can't talk about ;-). I am an unhappy MFT equipped Edge owner too so I'm with you all!

Certainly not something I have heard - I believe BSquare would have to acknowledged this in their recent financial results as investors wouldn't be happy about that (its a large revenue source for them). Also, they only signed a further deal with Ford back in Feb that runs to Dec 30th 2011. There are approximately 55 employees working there vs 35 last year (so 20 engineers were added) for 2011. Funny, the day after I posted my breakdown this comment by a user "Derodeo" shows up on another forum that is getting some views.... strange, its almost like a copy of what I wrote a day earlier! Copying my assessment? It almost uses the same language! : http://www.autoblog.com/2011/06/03/mulally-facing-pressure-to-fix-ford-fix-tech-and-quality-glitche/#aolc=A1DNoA Too funny.

Thanks for posting. I suffered this too in winter but its not happened for a couple of months now.

The hardware is not the problem when it comes to performance. I'm in a fortunate position that means I know a bit about both the hardware and software in MyFord Touch (plus I've done some other research too...). The processor used is specifically designed for what its being used for - its perfect in fact. If anyone is interested in the specs please see this datasheet: http://cache.freescale.com/files/dsp/doc/data_sheet/IMX51AEC.pdf?pspll=1 I would like to quote this section: "Powerful Graphics Acceleration—The i.MX51A processor has an integrated Graphics Processing Unit which includes an OpenGl 2.0 GPU that provides 27Mtri/sec, 166Mpix/s, and 664Mpix/s z-plane performance. Silicon version 2.0 of the i.MX51A device includes an independent OpenVG GPU operating at166Mpix/s." Now to most of you that won't mean much but lets keep it simple: MyFord Touch does not output "HD quality" images or video and therefore the demands on a graphics chipset is lower than this processors capabilities overall. The biggest issue that Ford face is a user interface that has been bolted onto a previous generation of Microsoft Auto. Adobe Flash Lite was designed to be used for Windows CE, it just happens to sit on top of Auto too as that is also built on top of Windows CE. Its actually a subset of CE. Fact: Adobe Flash on any embedded platform is not wonderful. Just check out the latest and greatest smartphones today (excluding the iPhone here becuase Apple just won't allow Flash on that device... read into that what you will). Not many of the latest devices even cope with Flash well and they are on the bleeding edge of technology. Ford can't use the bleeding edge of technology in the car. They need reliable (I know, there's a joke here somewhere), capable and proven technology before they put it into the car. They need something that withstands harsher temperatures than your phone and things like that. Adobe Flash (lite or not) will not cut it and it impacts the whole system today. I hear rumors of the PST (Microsoft Partner Solution Team) working with BSquare and Ford to iron out some of these problems but I don't think that there will be big progress until we move from Auto 4 to Windows Embedded Automotive 7. Think of it like moving from Windows Vista to Windows 7. Microsoft used to have 2 "different" Auto platforms (Auto 4.1 and Automotive 5.5). 5.5 wasn't an upgrade of 4 - it was different. With 7 they combined parts from both of them and built it on top of their latest embedded platform. I really hope that we see the fruits of the work going on right now soon. On Feb 6 2011 investment in the "Ford Telematics Competency Center" was doubled - this means we should see faster and better software from BSquare (the people that build MFT for Ford). Here's hoping! :-)

My dealer said that Ford engineering got back to them today - specifically in reference to me telling them about this thread. Engineering confirmed they have feedback from a Field Engineer detailing this. When they described it to me, it didn't sound exactly the same as above but close enough for me to believe it was the same issue. There is also a report of the brake hose rubbing something so they are going to check that too.

Get to another dealer buddy. I have to say the heat shield resolution is certainly strange because I could have sworn that it sounded like something to do with the wheel (sounds like it comes from left front... anyone else agree on that?). Just the way the noise is, that intermittant, squeeking/chirping whatever you want to call it... sounds like its related to wheel speed. Curious, when was everyones Edges built or when did you take delivery? I took delivery of my 2011 Limited AWD in October/November 2010 and I think I started hearing the noise in January.

Me too guys! Thanks for the solution, I'll take it back to the dealer next week!

WOW! Someone with exactly the same problem as me... mine chirps (if you call it that!) if I'm making a right turn too. I've had it since November and its been doing it for a few months now. Dealer said they couldn't find anything wrong with it but "continue to monitor" and they put a note into Fords Engineering department (apparently). I haven't noticed if the car is pulling but I'll really check that out tonight. I'm running the 20's on a Limited.

HAHAHA thats so funny - I found the same but never said anything.... I wondered if it was just coincidence but I'm glad there is someone else that thinks the same. Especially things go wrong if you try and play with USB after doing the above. Can't say I have the "rarely" part but I have had less problems by doing the above.

I mentioned something similar a while back (in January): http://www.fordedgeforum.com/index.php?/topic/6509-doors-not-unlocking-on-limited/page__view__findpost__p__52330 "Not sure if its related but when I first got the car, sometimes I could walk in my garage and the car would be "buzzing". It was an electrical extremely high pitched squeel but you could hear it clearly. If I started the car and turned it off again it would stop but I'm so convinced it was to do with the IA." Its not the fuel pump for sure as the car would not be running, not be unlocked and thats why I think its to do with IA.

I'm in the same boat guys - just know there will be a lot more of us now the new Explorer is out. God help Ford when they release the 2012 Focus which is supposed to also include MFT. They will be in big trouble once there are even more people with it - its a complete disaster. I'd love the boys from Top Gear in the UK to try it out, they would humiliate Ford after having it for a week. No way should we each spend 40k or more and have these issues - frankly its a joke but its being played on us.

My album art works good - I don't use Gracenote by the way because thats total junk. The biggest problem with the system in my opinion (apart from the bugs) is the user interface is just too slow. I hope that Ford upgrade MyFord Touch to Microsoft Auto 7 and replace the terrible Adobe Flash Lite interface with a Silverlight one.

The dealer told me specifically that you may have to use the key in the glovebox ignition so that sounds like they are talking about more than just the locking problem... they are probably related because its all about detecting the key is nearby.

If this is a 2011 Edge then check my posts about Ford identifying an issue with IA (finally!). One they have a fix ready then see if it solves your issue. The service message states that you might have to use your emergency key (YIKES - thankfully mine isn't that bad but it sounds like yours might be!). The Special Service message is nuumber 21744 (if you speak to your dealer they will be able to pull that up in OASIS).