How is the New 2.11 working? | Page 2 | Ford Explorer Forums

  • Register Today It's free!

How is the New 2.11 working?




Join the Elite Explorers for $20 each year or try it out for $5 a month.

Elite Explorer members see no advertisements, no banner ads, no double underlined links,.
Add an avatar, upload photo attachments, and more!
.





And that speaks for itself if you have been following their posts!

Yup, as I said before, if you are having problems - get it, if you are relatively problem free wait until the next oil change as its not gonna rock your world.
 






I got the new 2.11 update yesterday. Made the screens a bit more responsive, but as I was relatively problem free on 2.8, like jrmexplorer said, it isn't going to be any world-rocking change. Glad I got it, tho.

I WAS having problem with bluetooth noise, and when I took it in, the adviser said the TSB listed 2.11 as a bluetooth fix (I'd sure love to read the TSB). The first thing I did after getting the car back was to test it.

No change. Still the wind tunner effect. I will say that when I'm NOT talking, it is fairly quiet. Unfortunately, as soon as I start talking, the wind tunnel is back. Windows up, a/c off, freeway speeds. I recorded this on my voicemail, so I'm prepared to play it for anyone that cares to listen.

Can anyone confirm whether there is a known fix for this problem? I know I'm not the only one experiencing this.
 






I have a droid x and was hoping that text messaging would work, but it does not appear that is the case.

-Justin

I have a Droid X and I am able to get texts with no problem.

Have you upgraded your Droid to the latest operating system? Before I updated my Droid to Gingerbread, the texting did not work. Now it works great.
 






The speaker picks up as VA when you start talking. Is there really supposed to be no perceivable background noise at highway speed? I mean, I know it's a technologically advanced marvel, but are people expecting this thing to be as quiet when standing still and not running? I have wind tunnel noise when talking on the handset in my cars, even the '07 Camry. If I put it into bluetooth, it's still there even with the noise canceling adjustments in the system. It's a car that lets you make phone calls, not a noise-free sound studio. Are people just expecting too much?
 






I think some are, especially when you read some posts. And I not just talking about mic noise I particularly liked the one poster that was complaining about the wind buffering noise when the front windows are up and the backs are down. Gee I just crack the front and all gone. LOL
 






I have a Droid X and I am able to get texts with no problem.

Have you upgraded your Droid to the latest operating system? Before I updated my Droid to Gingerbread, the texting did not work. Now it works great.

Yup - got gingerbread and still no texts. I've tried pairing/unpairing, etc...

Maybe I need to do a factory reset on the phone....
 






Got the update installed yesterday (they also did the TSB for A-Pillar rattle, and replaced all 4 window moldings to reduce streaks). It is MUCH faster however I've already had 2 black screens. The difference this time is that after 30 seconds it reboot on it's own rather than me having to pull the fuse. But in less than 2 hours worth of driving having two black screen crashes is ridiculous in my opinion.
 






^ That ^ is ridiculous.

IMHO, without knowing the intricacies of what and how the system totally operates, it just looks to the layperson like this system just doesn't have enough memory available to control what it is controlling.
 






It's using flash lite for the GUI, which as a developer I can tell you is overly resource intensive. I wish they'd update to win7 for auto and rewrite the UI in silverlight.
 






I have a Droid X and I am able to get texts with no problem.

Have you upgraded your Droid to the latest operating system? Before I updated my Droid to Gingerbread, the texting did not work. Now it works great.

So I reset my phone to factory and now it /sort of/ works..... I can go to messaging in the phone menu and hit "download new" and it tells me there are no new messages, but then it immediately pops up with the message. The problem now is that the message says "unknown" for the sender - it doesn't send messages (for some reason, it creates a new message and then fails to hit "send" - I can go into the message app and see that it placed a new message in there and I can manually hit send - but that won't be too convenient). AND - it doesn't check/get notified when a new message arrives without me going to the messaging menu and downloading new ones....

urgh....
 






I also have a Droid X and it also works fine. Never had any problem between phone and MFT.
 







+1

My memory, with all of it's leaks and faults, seems to recall reading that the new release was going to be a major revision. Is 2.11 the new release or is there still something else in the works?
 






+1

My memory, with all of it's leaks and faults, seems to recall reading that the new release was going to be a major revision. Is 2.11 the new release or is there still something else in the works?

My feeling is that Ford is still working hard on this but releasing stability fixes for the major issues users are having and will then focus on the little glitches.

Just my $0.02.
 






My feeling is that Ford is still working hard on this but releasing stability fixes for the major issues users are having and will then focus on the little glitches.

Just my $0.02.

If they weren't, they will be after the feedback they get on 2.11 ... they made it twice as fast, therefore it crashes twice as much ;) I think MFT is one of those projects that they need to cut the losses on, take the hardware, ditch the entire interface code, and start from scratch. Whatever company they contracted for the development clearly failed on this project.
 






If they weren't, they will be after the feedback they get on 2.11 ... they made it twice as fast, therefore it crashes twice as much ;) I think MFT is one of those projects that they need to cut the losses on, take the hardware, ditch the entire interface code, and start from scratch. Whatever company they contracted for the development clearly failed on this project.

Not likely. Then they'd have to go through a whole customer QA cycle again. A large part of Ford's problem is that they don't know how and with what, customers are using their system. There are lots of use cases out there.
 






Not likely. Then they'd have to go through a whole customer QA cycle again. A large part of Ford's problem is that they don't know how and with what, customers are using their system. There are lots of use cases out there.

You're saying because they would have to go through a QA cycle they couldn't start from the ground up? I'm pretty sure that Microsoft, Apple, every other large software developer w/ a huge install base has done this in the past. Most of the issues are seen during a 1 hour commute. Pick a limited install base for testing (possibly some from the boards here) and let them pick it apart. They obviously failed their previous QA attempts, so why would a new QA session be unfeasible?
 






My recent favorite example of how they missed the "How it is used" target is the only two potential hard buttons on the center section of the Sony system: Sound and Source. You give me two bars which look like buttons but aren't (they are touch sensitive above them) and them you give one of them up for sound controls???? How often do they think I tweak my treble and bass? And the Source button is the 4th choice for controlling that function (MFT screen, right dash screen, voice) I never use the Source button as I don't know where it will take me (USB? Sirius? Sirius 3? etc.).
 






The speaker picks up as VA when you start talking. Is there really supposed to be no perceivable background noise at highway speed? I mean, I know it's a technologically advanced marvel, but are people expecting this thing to be as quiet when standing still and not running? I have wind tunnel noise when talking on the handset in my cars, even the '07 Camry. If I put it into bluetooth, it's still there even with the noise canceling adjustments in the system. It's a car that lets you make phone calls, not a noise-free sound studio. Are people just expecting too much?

The answer from me is, no, I don't think THIS person is expecting too much. I've owned a couple cars with built-in BT, and my wife has an '09 Flex. None of which is as bad as the Explorer BT system. The last car of mine, a Mercedes, most people didn't even know I was driving at freeway speeds.

Now, I know the interior of a Benz is quieter than the Explorer. I'm not saying I can't live with ANY road noise. It just shouldn't rise to the level where people are asking me whether I have my windows down, or for me to call them when I'm not in the car. Many of these calls are for business, and business calls need to be handled.
 



Join the Elite Explorers for $20 each year or try it out for $5 a month.

Elite Explorer members see no advertisements, no banner ads, no double underlined links,.
Add an avatar, upload photo attachments, and more!
.





You're saying because they would have to go through a QA cycle they couldn't start from the ground up? I'm pretty sure that Microsoft, Apple, every other large software developer w/ a huge install base has done this in the past. Most of the issues are seen during a 1 hour commute. Pick a limited install base for testing (possibly some from the boards here) and let them pick it apart. They obviously failed their previous QA attempts, so why would a new QA session be unfeasible?

It happens, but a complete rewrite of code takes up a lot of time, and yes, a lot more QA. They have live users, and they want to resolve those issues before they even dream of rewriting the code from the ground up. Think back to when MS and Apple did it; first results weren't pretty (still have nightmares about that Windows 3.11). Both MS and Apple had reasons to rewrite beyond bugs in their code though - they had to move the platform. I don't think Ford has that same need.

They've been swatting bugs and (perhaps this is an assumption) dealing with customer use cases/hardware they didn't expect or test on. (All that being said, I'd certainly not be against them getting rid of flash components)
 






Back
Top