l33

Like a tree in a park?

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

http://www.fordedgeforum.com/index.php?/topic/7332-inside-info-on-mft-development/page__view__findpost__p__58713

 

You can trust Waldo on this one. BTW - this doesn't mean that Ford isn't still paying Bsquare under the contract terms even if they decided to redo the software in house. Happens all the time.

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!

The report I saw said Bsquare was out and Ford was rewriting the software in house with lots of help from Microsoft and the new version would be backwards compatible with current hardware. Not sure about the OS upgrade though.

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.

Not sure I agree there. I am a systems admin for a video game company that is very frugal so I am use to having to make do. While i would have no problem using a 600mhz processor with 512 of ram in a server that handles 100's of users aday there is no way I would run a GUI on it. The overhead for that would be a killer in such a system. The slowness as reported by alot of sync users is due to that proc being over worked. Its not a stand alone video processor so all the work that gets done and is reported back to the end user (changing music tracks moving back and forth between modules) is coming from the CPU in addition to the processing work that the commands require. Hell a 1gig P4 would have been the better choice and cheaper.

 

Not saying that you are wrong in your post just a disagreement from the sharp edge of the sword.

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! :-)

I'm going back this Monday, they're going to give me a car instead of wasting my time waiting for a shuttle. I'll insist they look at the heat shield. If they don't then I'll go somewhere else. Thanks guys.

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.

So I took my vehicle in to update the sync and mentioned this problem. Neither were fixed. They couldn't update my sync and the mechanic made notes saying 'abs wiring harness was loose, rubbing against front cv boot. Harness put back in place, test drove, noise gone' so I'm like okay. Then i pull out of the parking lot and take a RIGHT and guess what, still there. Like honestly what do I have to do, fix it myself? I told the girl in service that it was the heat shield was flexing and she's like 'well that wouldn't be it at all' nothing but problems.

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!

I believe i have this problem as well. I thought it was just the slant in the road for a while but eventually decided to try driving on the wrong side of the road to test it and it tracked dead straight rather than pulling left. Also i hear chirping during right turns if I'm doing anything but a crawl. Does not occur in left turns at any speed.

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.

The main thing I seem to have taken notice of is that if you jump in the car, start it up

and immediately put it in gear and take off, you are likely to see something go wrong.

I tend to wait a few seconds for the system to boot up and I rarely have anything go wrong.

 

for what its worth!

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.

Thanks for the replies, but this is not the fuel pump (although I did notice that it is noisy, too). I am continuing to work with the dealer, and will post any findings if they're able to resolve it.

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.

It is a 2011 Edge SEL built in the time frame addressed by 21744. (It would be interesting to know what changed to establish the end date for 21744.)

 

21744 only deals only with the door locking issue and while the problem I had may be related, it is not addressed.

 

A failure of Intellegent Access to unlock the doors is a minor, but irritating problem. There are four ways to unlock the driver's door. On the other hand, there is only one way to start the Edge and if you have Intellegent Access and it fails, you are SOL.

 

All the electronics are really cool as long as they don't fail. When they fail.......................

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.

I was out shopping today in my Edge SEL. I stopped, shopped, and put some packages in the back using the keyless entry. I did some more shopping and returned to the vehicle, using keyless entry to unlock the doors. I put my foot on the brake, pressed start, and "No key found" (or words to that effect) was displayed in the left panel. I took the fob off my belt and set on my lap, "No key found". I put the fob in the little pocket (logo up) in the center console, "No key found". My wife moved her fob to my lap, "No key found". I performed the remote start procedure, the Edge started, but then when I touched the brake, "No key found."

 

I called the Ford 800 number. Can you say "endless (^&()*)(*) menus?" I called my dealer, no help. I called the 800 number back. All they will do is tow the car. They have no trouble-shooting steps.

 

I finally got out of the Edge, triggering the alarm (at least that works). I closed the door using the touch the bump method (keyless), I unlocked the door by (keyless) grabbing the door handle, I got it, put my foot on the brake, pressed the button, and the Edge started.

 

WHY???

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).

All in this thread - I have an update here:

http://www.fordedgeforum.com/index.php?/topic/6509-doors-not-unlocking-on-limited/

Ford have identified and are working on a fix to our issues. Special Service message 21744

:hyper:

Thought I'd drop an update on this because its been a while. At the beginning of Feb I had the latest updates applied to the car during its 8000km service. I was lucky and the car demonstrated its fault to the guy that wanted to move it into the service area which I thought was great because they've now seen it doing its little tricks.

The mechanics reprogrammed the APIM and the latest MyFord Touch updates were applied. A few hiccups but in the end they did a good job, none of these strange issues (ambient lighting mix ups, and Lincoln theme applied for example).

Since that day, remote entry was perfect. It was like when I got the car... I was so happy. We've had good an bad weather, much like we've had here in Canada since I took ownership of the car back in November. Temperatures low, lower and even lower :yup:

Then, all of a sudden yesterday it started happening again. And again today. Grrrrrr so frustrating! I've called the dealership and they are contacting Ford engineering to see what they say. Like I've said before, the car knows you are there because you can attempt to lock the doors using the raised bump on the handle and the lights flash in acceptance. The unlock will not work however on either drivers or passengers side.

Update - just had a call from the dealer! Ford posted this Special Service Message this weekend!

Special Service Message 21744

Ford have identified there is an issue with 2011 Super Duty, Edge and MKX's with the Intelligent Access system.

They are advising the dealers to do nothing right now (but tell owners to use the key :shades:) until they have a fix. The message describes exactly what I see - an intermittent issue,

I'm so glad that this is now taken seriously and Ford will fix this annoying thing!!!! :hyper:

I am having the same issue, sort of. Sometimes, when I touch the inside of the door handle, the car will lock and unlock in rapid succession several times, but then ultimately not let me in. I have to keep trying the key fob, open up a back door, and just keep messing with it until it lets me in. I even had the key inside the car the other day, shut the door (did not lock it), and the car locked me out when I tried to get back in! I had to punch in my code to get it to unlock one of the back doors so I could grab my purse with the key in it! This is so frustrating and I'm scared to take it in to the dealership because it sure seems like Ford has NO fixes for any of these (very common) problems!!

My problems got more common until yesterday when I had the latest updates applied to the car. Since then I've not had the problem happen but that doesn't mean its gone away... I'll update once I've had a few days use and see if there is any changes.

Was it working and now has stopped? Stupid question, but do you realize the button on the outside is ONLY for locking and for unlocking you touch the inside of the door handle? The reason I ask this is for my FX35, the button on the handle did both and it took me a bit to learn the difference.

See here:

http://www.fordedgeforum.com/index.php?/topic/6509-doors-not-unlocking-on-limited/

Well when it is on fire grab the Marshmallows and take pictures for us.

Some days I wish mine would catch on fire - I'd get more enjoyment out of the marshmallows

I would try a new battery in the fob...just for grins

But I cannot see how that would help if the car recognises the keyfob being nearby (as the lock function works).

So here's the latest thought.... *what if* the car thinks we are already sat in it. That would explain the behaviour possibly?

Surely thats a security "feature" so that you couldn't get someone trying to enter the car at the stop light or something? I need to do some more testing but I have a feeling that this is the problem...

I lock my car every time using the door handle, I might start locking it with the keyfob and see if the problem goes away - I'm just looking for reproduction steps. Halbran - how do you lock yours? I find that this happens more commonly when I have remote started the car using the 1) lock button 2) remote start button twice.

I'm going to the dealer soon for my 8000km service (and will get the Sync updates applied). If this doesn't work I'll have the IA unit replaced (its located inside and above the glovebox).

Interested in the feedback but Halbran I have exactly the same symptoms as you. Ford need to know about this - has anyone called them out on it yet?

Must just be me then... it seems to be getting worse!

I've had the same problem, or something very close to it, a couple of times. It's as if the system isn't picking up the key even if I'm pressed right up against the door. Has only happened when it's particularly cold out and there may have been some ice on the door and lock area. I've then had to use the keycode pad to get inside. Possibly a feature that didn't get enough cold weather testing...

Mine did it again yesterday and I even filmed it on my mobile phone camera. I show that it recognises the key because when I hit lock you can hear the door locks trying to lock the car again. I went around to the passenger door and that wouldn't let me in either... Went back around to the driver door and after standing outside for a couple of minutes suddenly it let me in! Miracle! It then happened later on in the day too - same thing, in the end I just hit unlock on the keyfob.

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.

After all of these incidents, I'm really sure it is not my key (because it is happy to lock the car even when its locked...), it is not the door handle because the passenger side does the same (and thats hardly ever been used) so that leaves me believing that there is something fundamentally wrong with either my IA system or the system in general if others are seeing this too.

Anyone else suffering? Hope Ford visit this site and keep their eye on this thread because it could develop.

Did it again for me two days ago... always happens when I'm in a rush though so I can't try out scenarios (and its damn cold in Canada and I want to get in to get warm!). The car was running using remote start this time and I was the only person anywhere near it. I found the door would respond to the lock (the bump on the outside of the handle) but not the unlock (the inside of the handle). So what I mean by that is if I pressed the outside of the handle you could hear the car try and lock even though it was already locked and I think the hazard lights flash too. So I know the car could detect the key.

Hands were clean, door handle was clean on both sides. Since that time its been working fine again... its so frustrating!

Glad it seems to have worked itself out and hope it stays that way.

Was anyone else near the car with key 2? I found mine wont open the driver door if my wife is standing near the car with her key in her pocket... its a bit strange. I went through a phase where mine was really playing up - maybe I'm just putting two and two together? I tried cleaning the handle all over (and under!) but only managed to get it to work if I got my key out and put it right near the door.

We should all keep our eye out for this and see if we can find a way of reproducing the issue... without leaving the keys a long way from the car ;-)