Latest update news

Hopefully Telstra moves out of scheduling very soon!

Keep up the good work guys, we need more faster...

I didn't receive an update Notification on my Bell HD7 for the 73920 update,but when i plugged my phone to my PC and searched for updates on ZUNE it found the update and the installation went on perfectly

@Eric,just wondering if MS has started looking into the SMS bug on the HD7,because i started having this trouble on my HD7(from Bell) after updating to Nodo.

@ stevethenerd..

What good work, exactly?

Will the 7392 update as complicated as NODO with a wheres my update page and all that? Or because this is a security update will this be expedited?

Hi, I'm from Chile and I have a factory unlocked Omnia7 ... my

query is whether my location interfere with the upgrade?

and other questions are people who occupy chevronwp7updater is true that

damage the phone and not allow future updates?, if so

Microsoft will offer a solution?

PS: In next updates why not put them on the page to download and not wait?. might avoid problems of "I do not get even and blablabla"

kool new update is everyone getting it this week

This update needs to be added to the "Where's my phone update?" page. After NoDo is FINALLY delivered you guys should stop naming updates by month and just use the version #. That way you won't confuse people as to why the Feb and March update didn't come in either one of those months. As for the Focus problem, do you guys not work with your hardware partners to make sure you have at least ONE copy of each version of the phone they are making? If not, I hope you will do so (or something similar) in the future so you will have a better chance to find these problems before you release the update, not after.

@Eric Hautala ATT released feb/march updates on 4/19.  Wife bought focus on 4/21 (I bought mine in January).  Since 4/21 I have been asking why my wife's phone was not being updated and now, after nearly 2 weeks, you decide to post that "We’ve also been looking into reports from a small number of Samsung Focus owners on AT&T who haven’t received an update notification".  I have been telling you this on this blog since 4/21 but mysterisouly my posts keep getting deleted.  I have been telling support via twitter since 4/21, I have contacted Samsung support via twitter and email and no one has said anything other than it is someone else's fault (Thank you ATT as we all know you have never done anything against your customers!, or that you don't have any information try contacting Samsung or ATT (Thank you @Winphone Support), or the Windows Team Blog where many go to get information and updates about their Windows Phones since everyone else sems have their heads stuck up their rears and claim to not know what is going on.  Here, where we come to get "official" information, we get nothing!  I have been coming here for 2 weeks and not until today do I find out that you are looking into reports of this issue. Really???

I'm not receiving nothing on my LG Quantum (AT&T) i guess i'm going to have to unbrand again and see if anything happens

It worked soon as i debranded by LG Quantum! i've decided i'm just going to leave it debranded. :)

Regarding this statement... "... you’ll receive 7392 as a standalone download or bundled with a future update."

I think we should receive  the security for fraudulent certificates NOW not with some unknown future update leaving our phones in an unprotected state until the carrier decides to "allow" another update.

"How you get 7392 depends on your mobile operator". WRONG. WRONG. WRONG. WRONG. WRONG. WRONG. WRONG... Oh and did I mention WRONG?

Seriously Microsoft, which decade are you still working in?  a *SIMPLE* certificate fix should be delivered STRAIGHT TO THE PHONE (via Zune software). There is NO NEED WHAT SO EVER to involve the money-hungry-useless mobile operators for such a fix.

You guys *SERIOUSLY* DO NOT UNDERSTAND THIS PROCESS AT ALL. Sigh.

@Eric - Regarding ".. you'll receive 7392 as a standalone download or bundled with a future update", is there any way Microsoft can remove the carriers from the update process entirely? It may be just me, but delaying security updates sounds like a terrible idea. Delaying any update, for that matter, is bad PR for Microsoft (even if it's the carrier's decision).

I donèt wait for the notification on my phone,as soon as the bloggers blog about the release of an update i hunt it via ZUNE,i updated to Nodo when bell mobility was still testing the update and today i updated to the 7392.

N.B. i updated to Nodo using a walkaround process(not the Walshed way and not with a third party software),just disconnected from the internet when ZUNE was searching for updates and reestablished the connection when it found NoDo.

For the 7392 i updated normally and it went perfectly

100% agree to Glen Roberts, why do you still lick the mobile operators a**, they just slow down the whole process and the customers get pissed on wp7 (not the mobile operator)? Why you keep doing it wrong?

Anyway @microsoft, why an certificate update contains so many system changes? Why dont telling which bugs adressed by the update (instead of the certificate problem)?

@Mostsimon

there are reports chevron updater users get the 7392 update...i dont think this will be a problem in future, even if microsoft said this.

But anyway...at the moment microsoft said there will be no fix for the chevron updater users, you have to flash a stock rom.

Are you guys crazy or what? This is a security update and some may get it only bundled with a future update???

Oh boy, Microsoft, this thinking itself is mayor failure on your part! I am at Deutsche Telekom and finally recieved all updates last night, so I could not care about that right now. But I do. All the time I thought "Okay, it is their first WP7 update, they are still learning in that process etc bla bla" and I had high hopes things would get better with the next updates down the road.

But to be honest: this is BS!!! And this is not what you had promised at the start of WP7. I am disappointed and mad and I really lost the faith in you getting your sh*t together and make this whole update process more bearable to your paying customers.

This is laughable...

Hey Eric and/or microsoft.

I just want to ask a few questions maybe you can outline in a future post.

 So my main question is, Why must updates go through carriers? I mean, I would understand if these updates were coming OTA as was your original plan i presume but since we're pretty much downloading the update from zune servers (i may be wrong but), do carriers really have to get involved? I am asking this as a general question but also,

Couldnt you pull an amazon (when they released that cloud music service)? :P like release the updates officially in a way that cannot be influenced by carriers and when they complain, just apologise? but keep consumers happy?

p.s. i don't believe this is accurate www.microsoft.com/.../update-schedule-world.aspx  . the Australian part. not sure about the rest

@Eric : Are we ( Omnia 7 owners ) getting any update at all ? ( Pre-NoDo update ),

most of my friends are on Three or Orange and all of them have received teh Nodo update. What I dont understand is the fact that after updating almost everyones Omnia 7 we realized that there is a problem before we give this to T-Mobile customers

Can we get some details about whats wrong with the Omnia 7 update ?

I updated my Omnia 7 when officialy prompted by notification. All went well.

Now we are told there is a problem with this update and it has been suspended while a new version is readied. This leaves me and many other owners wondering what is wrong with it... some details would be good. Am i going to have problems with my phone now? Am i going to need to install this new version when it's ready? etc.. etc..

Worked for me: Updates arrived this morning (my carrier is Deutsche Telekom).

Updating my Optimus 7 device took around 5-7 minutes. Sure do love the fast update process. :D Thank you for this update.

I echo brianm76 about the Samsung Focus Rev1.4 calamity (to put it kindly). I'm still waiting and waiting.

I have been a loyal Windows smartphone user since Windows Mobile 2003. But my frustrations with this update process have me warming to Android.

@a688, I think that's actually a good idea.  As long as that numbering will be consistent across all devices (we know already that some devices have been getting specific pieced bundled with their updates, <Samsung, ahem>).  I was never a fan of giving updates a name or referring to them by a planned deployment month.  We don't see that with the desktop platforms.  So, yeah, count me in on your idea.

To @Glenn Roberts, I found your statement "You guys *SERIOUSLY* DO NOT UNDERSTAND THIS PROCESS AT ALL" to be really interesting.  It's their process, not yours.  So, how can you accuse them of not understanding the process.  You can say their process sucks...that's why we have opinions.  But how can you say they don't understand the process?  I think a more appropriate rant would be "You guys *SERIOUSLY* DO NOT LISTEN TO CUSTOMER EXPECTIONS VERY WELL".    If you read the myriad of posts on the other threads of the blog and of other WP7 websites I think you'll see that we all pretty much agree that, as customers, it made very little sense to hand so much control to the carriers, that carriers are purely a pipe for communication (as it should be).  The "bundling" caveat has to do with the fact that carriers CAN (and HAVE) choose to wait on one update but that they have to let the next one roll out.  Remember, the statement was made that updates are cumulative.  So, if carriers just rolled out NoDo they CAN hold off on the certificate update until the next update (presumably Mango).  Smart?  Nope.  But that's how it appears Microsoft struck the agreements with carriers to use WP7.  I'll remind you that a majority of the problems that have come up with devices were because OEMs made changes to their devices without engaging Microsoft properly ahead of time.  I think it's a HUGE foul that Samsung even HAD a version 1.4 device.  They effectively screwed customers by doing that.  I'd accuse the OEMs of not understanding the process before I'd blame Microsoft in this case.  Bottom line:  you have a case if you say Microsoft created a bad process, but I completely disagree with your argument they don't UNDERSTAND the process.

I sync'd up this morning, but the certificate update wasn't available yet (Focus, AT&T) for me.  Let's see what happens this evening.

@ Michael Stroh, Brian Seitz, Eric Hautala (aka Mr. Congeniality), Steve Ballmer OR EVEN Barack Obama… ANYONE OUT THERE!! You Microsoft, have pissed on your toes all over again!! If it’s not one thing, it’s something else.  I have seen this mess before with Windows Mobile… DÉJÀ VU!  Am I so stupid that I don’t comprehend your business strategy for WP7? I remember reading back in July of last year (I think) on your website about how renovated and improved your approach to developing WP7 was going to be, that you were going to orchestrate the whole process and leave pretty much nothing to the carriers (just to sale the final product) BUT now more than EVER, I realize that they were empty promises.  I ask, with so much talent and so many resources, why didn’t you select one exclusive OEM (Motorola, Nokia or HTC are my favorites) to design and develop a sleek, powerful and dependable smartphone that could be used across all carriers (with only two versions: one for GSM and one for CDMA networks)? (kind of the model being implemented by iPhone with AT&T and Verizon).  If you would have taken your time to further brain-storm your business strategy for WP7 and not rush yourselves into deploying a half-made OS only because you wanted to quickly start grabbing a slice of the smartphone-market-pie, we ALL wouldn’t be in this mess with 3-5 months late updates/patches, some OEM hardware related problems, incompatibility issues, etc.  I am telling you Microsoft, you are trying to bite more that you can actually chew.  Are you?

PLEASE solve the Omnia 7 issues.  It's a very popular phone

AND I hate to keep bringing iPhone to this conversation BUT the only thing I like about them is that we ALL know when someone has an iPhone, it’s the sense of brand identity that WP7 lacks of.  The only thing that is unique about WP7 is the UI (the best one out there) but I don’t get that “hey, you got a Windows Phone” when someone sees me using my phone, as opposed to iPhone users… they are never mistaken.  AND I know what you all business/marketing gurus are going to say, that Microsoft is trying to emulate Androids’ strategy so they can start biting bigger chunks off of the pie.  I guess I have to settle for that.

Glad to see it's March already.  My Surround is updating now.  We'll see if it was worth the "pain" once it completes.

When's the IE SSL update coming out?

People to MS: Tell us everything so we understand whats going on. MS to People: We have a new update that we are currently working on to deliver to you. People to MS: What the hell. Why ...bla bla bla. I think I get the dialog here. Here is my advice to MS, don't tell customers anything unless they are ready to deal with it. MS could have sneaked the update into your phone without knowing but they did what the customers wanted and they are being crewed for it. So... if the update doesn't affect the visual look & feel and behavior of the phone to the customer, just don't tell them. Heck, i get a lot of updates on my pc name "security patch" from MS from behind the scene fixes and none of us care (except for the IT admin and the hacker) . Why win phone 7 users care about backend fixes, maybe its because they are soar from the earlier update mess. I'm a customer and my advice, don't tell us about any update if its behind the scene fixes unless the update results in some visual evidence (UI updates, speed etc). Customers will always complain. That's what they do best even when you say "sorry, we screwed up".

Obviously, you either haven't learned from the debacle that was the pre-NoDo and NoDo updates, or you are working behind the scenes to fix carrier involvement with the update process.  If you keep insisting that Carriers be involved with ALL updates, including security updates, then you must put this information on the "Where's my Update" page you created.  How or why carriers should be involved with Security Updates to the OS is beyond me, and those that have raised their concerns in this discussion.

Please listen to the customer, and not the Carriers.  We are the most important folks.

Thank you for clarifying the Samsung Focus dual memory vendor aspect.  It's good to see information like this and avoids rants & speculation as to why some handsets receive the update and others didn't.

Off topic here, but if you guys want these phones to succeed, you need to split the division off and get the names Microsoft and Windows out of the mix.  Like Stringer Bell learned on the Wire, if your product name's reputation is unsalvageable, change it.  Very few people choose Windows and the name is getting in the way of your phones.  Look at the sales.  "Catastrophic" jumps out at me.    Everyone I've spoken to says their phone is way too important to be left in the hands of Microsoft b/c of the past issues with security, speed, constant problems...  Microsoft and Windows are not synonymous with cool, cutting edge or high quality, especially with the younger generation.  Time to give up the ghost or pay the price later on.

can some one shed some light on that please

www.winrumors.com/674000-windows-phone-7-devices-sold-analyst-causes-online-stir

Ive been a windows mobile user since 2002 and just upgraded my phone because I read that the update that included copy and paste had been added.... guess which phone I went for...omnia 7.. oh well never mind. I love the interface but do feel that some real basics have been overlooked.. like keeping the screen activated only when plugged into power (in a car etc.). my biggest problem is that most third party apps I have tried so far are no more than broken toys... I used to feel like an adult with my windows 6.5 device now I feel like a kid with a new toy! I'm sure this is a push by microsoft and developers to compete with with the 10000000 (cr)apps available on other other devices...

What i ment by that last statement was... be yourself.. dont worry about people saying "apple does this...android does this." keep up the good work I like microsoft products for what they are/were.. lead dont follow and all that stuff!

Thank you for providing more clarity on the update problem for Samsung Focus owners.  

To echo another request on this thread, in addition to providing more specifics as and when they are available, I'd ask that a row be added to the "Where's my phone update?" for the "small number of Samsung Focus owners" who have been impacted - though I'm certain that is already in the works for when MS has the information to be able to provide that update - right?

A little swamped this week, folks, but I'll try to jump in and answer questions as best I can.

@D-Burrs (et al): Nice to hear from you again. We won't be adding info about the Focus variant to the chart. Instead, we'll provide updates via the blog. And I want to underscore that just because it appears that a small number of phones are affected, it doesn't mean that Eric and his team are treating it any less seriously. I sat in their daily status meeting yesterday and can verify that they're working hard to get EVERYBODY's phones updated.

@Imperial Dynamics: Omnia 7 updates are just about ready to roll again. More on that soon.

@Michael Stroh : Thanks for jumping in again, hope to see Omnia 7 Updated soon

@Michael Stroh and @Eric H,

I second the other commenter's words on taking the mobile operators out of the update process.  It only slows the updates down especially for something as important as this!

I just called my mobile carrier, Sprint, and they don't even have a date or idea when they'll push the security update.  It could be next week, a month, or even all the way until Mango.

So that inevitably means that because of Microsoft AND them I can't really browse the internet on my phone without second guessing if I'm setting myself up for risk.  

Please, please, please change the model and just push updates directly through the Zune software.  Get control of your platform already. Geezus

@Michael Stroh,i have just one Question which i'm really looking forward to get an answer,why are carriers so involved in the WP7 platform???

the more users don't have full control over their devices the more walk around tricks and hacks they will look for and develop and the more the credibility of the OS falls,if this keeps on,the 2015 MS dream of being the leading  Mobile OS will just be real in your minds.

Mobile phones are just like PC's and cars,when a customers pays for the phone its because he wants to do all he wishes to do with the phone especially knowing the phone and its OS have the potential,and its just too frustratiing not being able to exploit what belongs to you to the fullest.

the chevron and other hackers and local developers give wp7 what Microsoft doesn't want to give for one reason or the other,I encourage them for that

we don't need all the burocracy MS is offering us.no matter security updates you come up with,hackers and home brew developers wouldn't stop as long as you sell an OS with strings attached

Operators and consumers have never been friends and MS being operators friends imply breaking away from users

@eastern european hacker: Thanks for sharing. While I totally (but respectfully) disagree with your opinion on brands, I LOVE the Wire reference--it's only the best TV show ever created! Trivia: I lived and worked in Baltimore before moving to Seattle, and used to see the show's creator, David Simon, at my local coffee shop/ Some of the people shown in season 5 at the newspaper were also my real-life former colleagues. Anyway,waaaay off topic here. :-)

Its May!! For F*** sake can you stop saying you are delivering February and March updates???

@Kenny Rawlins, that question was actually answered a number of times in earlier threads.  I'll try to recap and paraphrase the best I can.  Essentially, the triune partnership between OEM, Microsoft and carriers is based on a set of minimum standards for the hardware and how they would work with each carrier's network.  The OEMs would submit their target hardware to Microsoft, who would then put them through their paces to make sure there weren't any issues at that point and the carriers would get a crack at it as well.  This also allowed for carriers to work in their own unique apps, capabilities.  When all the players agreed that the update meets the requirements the scheduling of rollout then gets established.  Carriers apparently believe there are enough issues with their networks that they should have a certain degree of control over when updates are deployed, to make sure that the user experience is intact and what carriers think their customers expect.  The understanding is that it's the carriers that customers will first go to if they have any problems with the phones....that's a fair assumption.

Now, having said that, this is where a growing percentage of customers are diametrically opposed to this configuration of the partnership.  I'm of the opinion that carriers have no business doing anything to the phones and that the entire testing process should be between OEM and Microsoft.  Carriers are simply a conduit for communication, and that's all they SHOULD be.  If the process between the OEMs and Microsoft is tight then any involvement by carriers is reduncant and, therefore, waste.  Sadly, some of the OEMs did some things to the hardware after Microsoft had approved their configurations.  So, as one might expect, a number of problems cropped up when updates that were known to work on the ORIGINAL hardware/firmware didn't work so well on the modified versions (e.g., 1.3 Focus versus the 1.4 Focus).  Then, when you add in the fact that, for example, AT&T insisted in adding completely useless features to the update as a precursor for releasing the update, you have the end result: horribly buggy and fragmented update processes.

Until Microsoft can re-negotiate the process rules with the OEMs and the carriers, we will find ourselves in this situation.  In my opinion -- and I've posted this numerous times on AT&T's site -- carriers should be prohibited from interfering in the update flow.  Period.  If OEMs have unique features because of the hardware/firmware they are designing, then they should flow those through Microsoft ONLY.  Microsoft should be the solitary funnel for all updates.  If carriers wish to add features they need to submit them to the Marketplace.  I haven't seen a valid argument for keeping the current process.  But that's my opinion.  I buy a piece of hardware because of what the OEM has designed and what Microsoft does with the OS.  I do NOT buy it for what the carrier can do with it.  They are like the cable company, that's all.... a pipeline.  Unfortunately, they think they are more necessary than that.  I believe Microsoft had little choice but to play their game if they wanted to get carriers to deploy WP7.  We have to hope that we can help build marketshare to a level that Microsoft can reassert it's strength in dictating terms to the carriers---not acquiescing to them.  Again, my opinion.

arstechnica.com/.../microsoft-tries-luring-ios-devs-as-windows-phone-7-dev-interest-falters.ars - Microsoft tries luring iOS devs as Windows Phone 7 dev interest falters

I'm glad that Microsoft is definitely listening to the Developers feedback however please listen the consumers feedback as well. The problem here seems to be the deployment of the updates which seems to be [blocked?] by carriers and OEMs instead of a being a simultaneous worldwide release. Gotta move fast to tighten this process up for "Mango" and future updates.

WP Team - Can we expect another update for bug fixes after (7392)?

You guys got the date which was reported to be deployed on time (May 3). Now the problem is, Which phones will receive it and when? I had to unbrand my AT&T LG Quantum in order to receive 7392 right away.

FYI, I sync'd up my Focus and the certificate update still isn't showing up.  Oh, well.

Does anyone know if my AT&T HTC HD7s will come with the 7392 update ? By the time they get around releasing it F'ing Mango will be out!   Sorry, I realize I am venting since no one can tell me why AT&T has announced this phone a month ago and it still not here...

this is kool think about it :)

jozefkocur.blogspot.com/.../wp7-mango-update-concept.html

Has anyone noticed colors being distorted on surround after update? I have updated 2 Surrounds and both experience this I rolled one back and and the problem goes away updated again and it is back. It looks as if the screen is not 32 bit color.

Image should look like this

http://tinyurl.com/428fchw

and looks like this on the screen

http://tinyurl.com/44ghynp

With all these new issues cropping up, That's exactly why we need another update to fix bugs and tighten what we already have on our OS before unleashing Mango.

OK, so the presence of the 7392 update is just starting the whole "when will I get my update" nightmare all over again.  As usual, I've not been offered the update (Samsung Focus, AT&T), and I have no idea if it's because AT&T is once again "testing", or if it's rolling out slowly, or blah blah blah....

I really don't want to know all these nitty-gritty details of your update process.  I really just want it to work.  But since it's not, can you please add details of the 7392 update to the "Where's my update?" page so we have a clue as to what's going on and when/if we can expect to actually get the update??  PLEASE?

I'm well aware that 7392 doesn't offer NEW functionality.  But that doesn't make it any less irritating to know there's an update out there than I can't get, and to have no idea WHY I can't get it.

@TwiceBitten

That's a very good point.  Yes, give us a freaking chart because I'm pretty sure our carriers customer support would be the last to know anything anyways, and better to hear it from the horses mouth.

+! @Imperial Dynamics PLEASE solve the Omnia 7 issues.  It's a very popular phone

and the best! :) so MS please hurry up and get the updates out to it. the where's my phone update international page should show the different models as it currently says for optus - delivering update but I'm with optus and won't be getting the update till the omnia issue is fixed.

I have an unlocked T-mobile branded Omnia 7 in the UK. Still no pre-NoDo :(

@Dreamerbala, you are aware that a problem was discovered with the update for the Omnia, right?  That's why it's on hold.  The last report I saw was that a solution is very close.  Of course "very close" doesn't tell us if that means that Microsoft is very close but that the carrier will still demand time to test it, or if that means it's very close PERIOD so that it will begin rolling out immediately when done.

FYI, still nothing on the 7392 update on my Focus.  

I just finished finishing up on something I was finishing ;)  (Steve Martin)

after installing this update marketplace keeps giving me an error when I try to select install. I have two dates waiting, when i tap on update all, it gives me the error. "Can't that info..."

I'm also having issues with Marketplace on a Focus on 7390....not related to 7392....

Michael, do you have any info on this?

Yet more bad press coming soon......great!

its not because of updates, I dont have any updates on my Omnia7 and Marketplace is down since this morning - Its not just Market Place other applications that connect to microsoft to collect data like Project Emporia App is also down

i used the "unsupported method of forcing to 7390" but later on i got an update called "samsung update" am i good or still in deep s***

Marketplace is down,can't download anything including updates my bell HD7 is updated to 7392,anyone else having this issue?

@Scubadog2011 (via @Dreamerbala): I meant it's very close PERIOD.

re: Marketplace status. I just posted on that....but am now hearing some reports that the service is back to normal.

How about adding the status of 7392 update and all future updates to "Where's my phone update?" page?  You need to set and control expectations. Thank you!

This security update (7392) highlights what many customers and IT folks have been worried about. It is one thing (as in-execusable as it is) to delay an update that adds features, it's another to delay a security fix.

My IT folks in the company said that from the beginning, the update process with microsoft does not allow any security updates and it'll take MS months to release one minor security fix, that was one of the reasons they blocked WP7 from accessing company resources. Unlike WM6 or 5, the WP7 platform is closed (which is OK) but combine that with a slooooooooooooow moving microsoft, you end up with a disaster in the making.

Carriers (and MS incompetence) are now going to cause this security update to be delayed months, at least for some customers. Simply unacceptable. What happens when there is a more serious security problem? The process and microsoft are not prepared for that!

The update process, the slow feature additions and the number of missing features (all 3 combined flaws) are turning away customers and I hope MS is listening. If updates have been coming faster or more frequent, if carriers have not been blocking the updates and delaying them for months or if WP7 has come out with a lot less missing features, people would not have been this upset. Also, the promises MS made (and are not fullfilling) are making this worse.

When the first iPhone came out, I saw the number of missing features and I said no way I'll buy it (Apple didn't say what feature will be added when so I said I'll buy it only when it has the features I want). With the WP7, we were promised many things and we are not getting them (more control from MS for updates, series of significant updates in few months, a SharePoint integration (which is only half implemented), a WiFi capability (which is until recently only half way implemented), an Exchange compatability (which is only half way implemented by not supporting many authentication protocols) and many other things that were promised but not fullfilled). I bought the phone because I trusted MS and I regret that decision now. If microsoft didn't make these promises, i would not have bought the phone and I would have waited until the platform is a little more mature.

Lol...  You guys should be pushing out features as well.  What's so damn hard to understand:  WP7 is basically a feature phone OS right now.  It's unusable for a ton of people who are forced to doublefist Android/iOS devices because it's missing even trivial features.  Feature updates, please.  Or as least a semi-tentative timetable when one will come out.  I can't wait until Mango to have a usable device.  I'll be forced to sell this thing in the next month or so.  It's a waste of a data plan at the moment.  Would have been better off just getting an iTouch.

Also, when will you or HTC address the borderline useless radio (poor reception/call quality) or speakers (can barely ehar them) on the HD7?

I have Samsung Omnia7 on T-Mobile UK and no update so far not even Pre NODO :(

Thanks, @Michael, it's the little details that can confuse or frustrate folks.  I hadn't seen anything defining specifically how you guys were working with the carrier---it could have been interpreted either way.  Of course, you won't be able to please everyone.  I think it creates a bit more confidence to know that the rework on the package is being done jointly so that when you announce it's ready that folks will be able to expect it to roll out without delay.

On another topic, I wonder if it might be possible to pin the MIX'11 thread to the top and encourage folks who want at least some idea what's coming later this year to look there first.  I think at least some of the angst about "when are we going to see these features added" might be stemmed.  While that was geared for developers, there's no mistaking that the bounty of things covered are also of great interest to users.  As more info is released about what will be in Mango perhaps it could be dropped in there, too--sort of a running feature/fix list.  Just a thought.

@Nater, I think I get nearly as frustrated as others, but there are certain things that I simply don't assume are "easy".  When you ask "what's so hard" I can't help but wonder if you understand the challenges.  Surely you've seen the issues already with what most would qualify as "small updates".  Also, did you really not know what WP7 was capable of versus not right out of the box before you purchased a device?  "Let the buyer beware" is as valid today as it ever was.  Nobody is asking you to wait until Mango to have a usable device.  The difference is that your definition of a "usable device" may be different from what others call it.  I knew the shortcomings going, because I researched the heck out of it.  Yes, there are certainly aspects that I found myself disappointed with (based on expectations), but I absolutely consider my Focus to be a usable device.  And I'm absolutely going to wait for Mango.  Based on what's been released so far, I'm sure that there will still be plenty of features missing after Mango, and I'll be in the crowd lobbying to get those things added.  But I'm not going to throw in the towel.  If you live & die by the features you're concerned with then it's in your best interest to move to another platform and maybe revisit the device when it matures more...perhaps with WP8.  But I think it's completely unfair to assume that WP7 is as easy to update as Android or iOS.  In fact, I'd guess that it's actually harder because they've designed so much integration in it AND designed it to be extremely easy for developers to write apps for.

@ScubaDog2011: I like your MIX suggestion. Let me see what I can do.

"The update process, the slow feature additions and the number of missing features (all 3 combined flaws) are turning away customers and I hope MS is listening. If updates have been coming faster or more frequent, if carriers have not been blocking the updates and delaying them for months or if WP7 has come out with a lot less missing features, people would not have been this upset. Also, the promises MS made (and are not fullfilling) are making this worse."-MalazNJ

Exactly!

Cool, glad I could contribute something constructive.  In the meantime, I sync'd up this evening and the 7392 update still hasn't made it's way to west Texas.  Here's hoping for tomorrow....and for the rest of the folks to get NoDo.  It definitely is a worthwhile update.

Okay, @Eric, @Mike, is the process different for this update than the "March" update?

If so, how?

If not, PLEASE update the "Where's My Update" page, and let's stem the tide of owners in angst.    Though the update has no user feature changes, most users are going to be VERY interested in when they can get this update which plugs security vulnerabilities.

Thanks.

Enjoy Windows Phone 7!

-e

Interesting to see that some of my fellow AT&T ‘Still Branded’ Focus users are getting the resent SSL Update v.7392, through Zune…While others are not, including moi…*****

Will patiently await ‘official update notification’ hopefully coming in the ‘very near future…’

Went through v.7004—>NoDov.7390 (also still branded, no Walshie, or other forced updating methods) without issues.

But as a former WM6.5 user and ‘heavy participating’ member @XDA…man it is tempting…lol :)

Have viewed the Windows Phone Dev Blog BWatson, and feel quite refreshed that their is a 'huge common bond' to rectify the issues for those who chose to 'force pre_NoDo and NoDo updates...and the Windows Phone Dev Team...nice!

@ScubaDog2011, also still have not felt the v7392 update with my focus in NW USA area.....

@Michael, you have jumped in and have done nice communicative interim job....

I personally feel that Windows Phone will  keep improving with bug, stability, feature updates...I am in no hurry, and am completely enamored with the GUI, and integration of OS...:)

{Info obtained through reviewing various Window Phone 7 Blogs} *****

I'm in the UK and for my Omnia 7 2 days ago, no updates showing yet and I am still on 7004.0 but I am happy to wait for a bit.

@Michael Stroh - I would really like to know if I am going to have future issues because of this Omnia 7 problem. It is not fair to tell us that there was a problem with the original release of the update and then give no further info to customers who have already recieved this "problematic" update.

I have not forced the update in any way and am then told there was an issue leading to it being pulled. Can I please have some word on this? What was the problem and is it going to give me cause for concern?

can anyone help me here ive got a samsung omnia 7 i got the pre nodo update on my phone so my os version is 7.0.7008.0 i was stupid an forced the nodo update on my samsung omnia 7 but last week restored my phone to before i forced the nodo update i just wanna know whens the nodo update coming on the samsung omnia 7 an am i gonna have any difficulties getting it because what i done thank you

@ Michael Stroh Some news about Omnia7s? Mine from T-Mobile CZ(Deutsche Telekom ) still on 7.0.7004 :/

@Eric Sorry Eric, I got tired of all this drama. Between You all and AT&T, what a soap opera! Took my Sim Card and put it back into my HTC Tilt 2 where I have Bing Navigation, File Manager, Task Manager, and tethering! Put the Samsung Focus in the dresser drawer next to the Blackberry Curve! See Ya! Hope you do get it right!

Sorry Eric, I got tired of all this drama. Between You all and AT&T, what a soap opera! Took my Sim Card and put it back into my HTC Tilt 2 where I have Bing Navigation, File Manager, Task Manager, and tethering! Put the Samsung Focus in the dresser drawer next to the Blackberry Curve! See Ya! Hope you do get it right!

I think @MWA1955 works in the Department of Redundancy Department ;)    

Seriously, though, I think the kind of info the Omnia users are looking for is similar to what we eventually go on the Focus side.  In other words, what was the issue that showed up, causing the halt in deployment of NoDo and a rework of the package?  Was this another case of the OEM tweaking the firmware/hardware and not sharing that news with Microsoft?  If that's what it was customers can't really do much about that, but it definitely adds strength to the case for Microsoft having strict hardware standards---standards that OEMs had better stick to in the future, lest potential customers say, "No, thanks, you guys keep screwing up your hardware".  When we were finally told how Samsung slipped a mickey into the Focus I didn't have a burning desire to know what the change was, but was satisified to learn that Samsung didn't follow the rules and that had the consequences we observed.  I bet a similar "clearing of the air" would satisfy most Omnia users.   Just sayin'......

BTW, 7392 Deployment +3, still no update available. If the fact that @gahbmwm5 hasn't seen the update yet is any indication, I wonder if the rollout is east-to-west.....hmmmm.

I keep meaning to post this question and am finally remembering to do so.  Are there plans to expand the capabilities of the WP7 versions of Word, Excel (especially!) and Powerpoint?  I realize that WP7 was designed more for the consumer than the enterprise.  But the editing and formatting features of Excel in particular are extremely weak.  Only three colors for fonts or fills?  Seriously?  I use spreadsheets and charting a lot in my work and came to rely on the Windows Mobile Office capabilities.  It would be nice if the Office folks plan to ramp up the power of the WP7 versions.  Also, I was a bit surprised when I first got the Focus and discovered that I could only edit existing Powerpoint slides, not create any.  With copy & paste back, I really could use the ability to build slides on the go.

Never hurts to ask ;)

@ScubaDog2011,

You may be correct via v7032 SSL update roll out being geographically related...(US based). As I typically do a thorough review of all Window Phone 7 related blogs daily prior to posting up on any related blog, forum...As I see that you are located in SW and I'm in NW (USA)...seems that I recall those who did receive the update (all branded, unmodified AT&T focus users) were_are located in NE (USA)...Possibly...?

telstra is in scheduling state . it means that it is going to release update 7392 ?

@Freypal That's a very good question and one I'd like answered too.

STILL waiting to be offered 7392 (AT&T Focus in California), and STILL waiting for an explanation from Microsoft as to what's going on with this update.  Did you learn nothing from the whole NoDo experience?  Do you really believe that saying how/when we'll get it "depends on your mobile operator" is sufficient?

I was looking forward to the first post-NoDo update (whatever that ended up being) -- not for the contents of the update itself, but for validation that Microsoft had indeed learned from the NoDo mess and ironed-out all the testing, distribution, and communication issues that have so tainted the whole WP7 experience.  7392 is clearly demonstrating (to me, at least), that nothing's changed.

This whole update process is so fundamentally broken that it's hard for me to even understand why you bothered to release 7392 at all.  It just starts the "cycle of frustration" all over again...

****Sorry meant v7392 SSL update****

Chris W had a interesting post on his blog regarding the update:

What’s in your 7392 Windows Phone Update

May 42011

So, we’ve woken up to the “SSL” update this morning.  Only to see MSFT have included a few more fixes than just SSL cert updates.

How the update process works

Once you’ve got an update pending, Zune will download the appropriate CAB files to “patch” your device.

Now these cab files, they aren’t full files.  They’re differential updates, which are merged with the existing DLL’s on the phone.  They’re then re-signed with the certificate specified in the DSM  

There are two types of CAB files.  There are language packs, and software packs.  

diff-7.0.7390.0-7.0.7392.0-armv7-retail-microsoft.pks_3a3a18fff5252d787974a169b115f8b428c0566c.cab

diff-7.0.7390.0-7.0.7392.0-armv7-retail-microsoft.lang_0410.pks_664864f39e89201620c48f6e6393123af232ae82.cab

As the language pack name denotes “0410”, this is an Input locale, typically the language(s) installed and available to change in the Keyboard settings. technet.microsoft.com/.../dd744319(WS.10).aspx

So if you’ve got multiple INPUT languages available on your phone, Zune will download all the appropriate DIFF language updates.

I won’t go into how the MUI files work on Windows Phone unless people want me to

What’s in your update

Managed Assembly Updates (IL diff changes to come)

Microsoft.Phone.Interop

Microsoft.Phone.InteropServices

Microsoft.Phone.MediaExtended

Microsoft.Phone.Reactive

Microsoft.Phone

System.Observable

Microsoft.Device.Sensors

System.Device (location sensors)

Microsoft.Xna.Framework.Game

Microsoft.Xna.Framework.GamerServices

Microsoft.Xna.Framework.Graphics

Microsoft.Xna.Framework.Input.Touch

Microsoft.Xna.Framework

AvCore (Camera Operations)

Quartz.dll

[url]blog.walshie.me/what-s-in-your-7392-windows-phone-update[/url]

Darn.  All sync'd up and no place to go.  sigh.

7392 T+4.....Amtrak isn't here...neither is the update, LOL.  I wonder how far west it actually has made it.  Kind of a silly way to deploy software that's just going out over the internet.

STILL WAITING FOR THE "7392" UPDATE

@scuba..  i don't think it matters how far west it went.  these roll-outs are ridiculously slow/unpredictable and just plain horrible experience for the users.

i'm in the midwest.. still got nothing.

I am also still waiting for the Nodo update on my Omnia 7..... and waiting, and waiting, and waiting, and selling my phone and never buy again WP/

I convinced my girlfriend to buy a new HTC HD7 (which got Nodo btw), bought myself an Omnia 7 (no NoDo after all) and quite a lot of my friends are surprised by how fluid and quick WP7 is but I still can't recommend WP7 100% to them considering the whole mess w/ updates, new features and the process behind that "fiasco"... so where's Nodo for Samsung's Omnia 7 in Germany and where's 7392 for all other phones - considering it's a "security-related" update, it's quite a long time...

@Michael Stroh : Are we owners of Omnia 7s in danger of not recieving future updates? (es. mango) Because this nodo is taking a really long time now.

Thanks for the security update!

Now how about hardware encryption for Exchange Server syncing for corporate email:

windowsphone7community.uservoice.com/.../1231513-add-hardware-encryption-for-secure-exchange-server

PLEASE!!!

C'mon guys, throw us a bone here!  What's going on with 7392?  I know some people with the Focus on AT&T have received it, but many of us still have not.  So what's up?

Shall I assume you've found problems and have halted the distribution, as happened before?  Or maybe AT&T has decided they want to "test" some more?  Or maybe your oh-so-fragile update process is unhappy with a bit or two on my phone and won't offer it to me?  (And, for the record, I have an officially updated, branded Focus).  Or maybe that same delicate process is only allowing you to offer it to3 lucky people per day?  Or...

It's incredibly sad that you've once again demonstrated that you simply don't have a handle on and/or control of your own update process.... even for what is supposed to be a very small, critical security update.  Heaven help us if a truly severe bug ever gets found in WP7.

i have a focus on at&t an still did not get the "7392 update "

On the good news front, it looks like those of you who care about turn-by-turn voice nav will get it with Mango, and those who want voice-to-text will be satisfied as well when Mango comes out.

On the bad news front, still no certificate update.