Select a language to translate this page!
Powered by Microsoft® Translator
Some late-breaking update news I wanted to quickly pass along. Today we began scheduling the 7390 and 7392 updates for Omnia 7 devices on Orange. Thanks again for your patience, everybody.
I mentioned Wednesday that we’re scheduling the 7392 update for HTC Surround models on AT&T and that other models would follow. Today, one did: the LG Quantum, which is also scheduling now. We’ll be updating the Where’s my phone update? table shortly to reflect these two changes.
Have a great weekend.
Happy days! Thanks for some great Friday news!
Great news for Orange users. Now here's hoping that Mango is a little more smooth.
@Michael Stroh,Since from what i know the update strategy for windows phone is not going to change,i mean the the carriers involvement (testing,scheduling and delivering) which is completely independent of Microsoft,Can we expect a smoother and faster delivery of the mango update?Or are some of us going to receive mango in 2012? I really need to know,so i know when to start expecting mango on my phone
Thanks for the prompt information and well done to the technical guys.
A suggestion...the "Where's my phone update" is not really for one's phone, but rather for one's carrier. For example, AT&T has 3 or 4 WP7 models to chose from but not all models are receiving the same update(s). Due to the fact that there aren't that many WP7 models out there across all US carriers, why can't this "Where's my phone update" page be more specific??? I think something like this would help cut back on the confusion 10 fold!
When I look at this page, I see that my carrier is "delivering" both the 7008 and 7390 update when in actuality, it's not delivering both updates to ALL their phones. I have the Samsung Focus rev1.4 and I can't get either update. So you can see how misleading this can be.
How long does scheduling usually take?
@comeradealex,its not suppose to take more than 10days
Has the nodo 16 bit banding problem/issue been fixed or will this update result in banding issues which were first of all, not present before update and second of all, provide a stark difference in screen visuals compared to pre-nodo. To speak plainly when weighing copy and paste and some extra security issues against 16 banding I think the visual problem outweighs the benefits and so most likely won't update until its fixed or just use registry fix as shown on xda.
@hawk - it used to list the specific devices for the carriers (in the US, at least) but I am thinking (and hoping) that this means that going forward that the mango update will be released per carrier not device
I hope this is only a nodo sympton, i truly do - that the updates are coming in so slowly. I already have Nodo on my Omnia but it just pains me to see that its not fully rolled out yet. Please have it fixed by mango.
While I hope I'm wrong, I don't anticipate the update process being any better when Mango is released. I speak specifically regarding at&t phones. It is, however, better than some Android updates but not near as good as iOS
I do appreciate this blog, but get frustrated, like others, at the lack of details. I would venture to guess that the readers and posters on this blog are not your normal phone users and would appreciate some more technical information at least every now and then.
Oh look my Samsung Focus is not being updated. Dead last. I HATE this phone. WORST choice I made was selling my iPhone for this piece of junk. The screen is beautiful and it is really a good phone, but all of that is completely worthless to me when I cannot even update my phone normally. It is dead to me. I should have waited and got a Verizon WP7 or something, or just got an iPhone 4.
Thanks for getting the updates out guys. I'm a UK customer on Orange and was wondering in what time frame they will be delivered? As of now my phone and zune still say that no update is available.
@leobeo84 Scheduling is up to 10 Days
Stage 2: Scheduling
Microsoft is scheduling the update for delivery. This phase typically lasts 10 business days or less.
@cM xB. Ah yes, slight fail on my reading there. Thanks very much for the reply.
I heard a new Firmware-Update for Omnia 7 is planned. Is that right?
Everyone might as well get used to this if you choose to go with this platform. As long as the carriers are involved (especially ATT in the US) you should assume any updates will take several months to get to you. That has been the track record with the last 3 updates (4 if you count the Focus with the alternate memory manufacturer). MS will continue to provide minimal or just enough information to pacify some and the carriers will contiue blocking or as they call it "testing" the update. If they are truly testing then why does it take months to test these minor updates? MS you will never gain the traction you need to compete if you continue on this path. I love my phone but these update delays and the lack of openess and response particularly on this site is pathetic. If the update issues aren't enough then you add in the issue with there not even being 1 update delivered for many customers like myself who have a Samsung Focus with the memory manufacturer variant and you have yourself an epic fail. It took MS nearly 2 weeks to acknowledge there was an issue with these phones once I reported it and I am certain I was not the first to report it. To this date ATT and Samsung have no idea what you are talking about when you ask them for an update. Go ask ATT right now on their Twitter alias if you don't want to call them @ATTCustomerCare and you will get the standard "we have no information to share at this time". Seems their support staff has been coached to not even respond to questions about updates and when they will be ready or they are completely clueless...MS is not sharing with us the full story here either which makes them 100% complicit. Since the OS is from MS regardless of carrier or manufacturer the update issues are MS fault. Once these update issues are finally resolved it will be time for "Mango" to be released. If these issues are not worked out and "Mango" is not delivered to each phone in a timely manner there will be people jumping ship and since there are not very many customers to jump ship in the first place this will be a disaster for MS. Once again, Windows Phone leadership you would no longer have jobs if you worked somehwere else. You are arrogant now but if you don't get "Mango" out smoothly let's see if you still have the same attitude.
I think you all need to relax. This is not the iphone, there are several different phones on many different networks. I myself have an LG Quantum on AT&T. Compare this to Android. 2.3 (Gingerbread) was released in February of 2011, almost all phones are still waiting for that update and most phones will never receive it. Even look at 2.2 (Froyo) and how long that took to reach end users, and how many phones will never receive that update. I think you should be patient, and thankful that MS is pushing these updates (7008, 7390, 7392) to all WP7 phones. I realize that waiting is difficult, but complaining and making accusations and idle threats against MS is clearly not the answer. Where will that get you?
And by the way, I "debranded" my phone and got the 7392 update on May 5th.
@Brianm - I would love to know what company is 100% open with their customers as I can't think of a single one and is timely in everything they do.
Android sure isn't except the nexus which is what apple is ( hardware and software) hell sone people can't download certain apps and android developers have issues with developing apps because of the fragmentation
Apple controls the hardware and software But now with the Verizon update there has been a lot of problems but they too do not disclose everything...the whole iPhone being left in a bar and they had no idea it was gone....right
Sony took two weeks before they advised their customers about a breech and then said no cards were compromised and then came out and said they were.
Businesses are run the same way your government is - you are on a need to know basis and you will get what they want you to know.
Business answers to their shareholders if all business was honest about everything to their consumers they would be lucky to ever get a product out
@krush you,reason why i hate capitalism
if we keep on comparing WP to the down side of its competitors and trying to feel better about our platform we wouldn't be helping it progress,sure we shouldn't also spend all the time singing how aweful we think it is,all i'm trying to say is that theres a great possibility of overcoming these barriers and thats what microsoft needs to be looking forward to.
the thing is Microsoft thinks there's just one way to,via carriers which according to me is wrong because i see better channels which don't involve carriers
rofl march update pushed out in june...
yea much faster than with a android device
can only hope that mango deliver dont took so long or one of the main plus points on wp7 is totally senseless
@Kenny - until the phone starts selling they can't make the terms and since they don't control the hardware it makes it more difficult -I hope though with all the negative press they got on nodo that mango will be much smoother, if it's not it's going to be avstruggle for the platform to gain ground
@krush you,the carrier route is slowing down the update process and turning away customers,thus slowing down the sales of the phone,at the same time carriers themselve are not pputting much effort in WP,because they are also waiting for it to start selling whereas Microsoft is counting 100% on the carriers to push the device to the market.so now who brings forth WP to the market??
i have what i think are solutions to help this situation,but no point revealing them
The issue with the rev 1.4 Focus is almost certainly due to *defective hardware*.
A different version of the memory chip or even a different chip manufacturer would merely have introduced different timings or sequence requirements during flashing and it would not have taken this long to modify the update to take this into account.
There is a bug in the actual hardware and Microsoft/Samsung are trying desperatly to find a work-around. I expect a recall.
@Krush who cares about other companies. I bought a Windows Phone. The OS came from MS, the updates came from MS, yet the carriers are calling the shots. As a customer who spent his own money for the phone and pays what many consider to be ridiculous monthly charges for data and phone service from a carrier, I believe I am entitled to information related to already released updates. If you have the time to come on here and try to invalidate and argue every point that someone makes about this horrible customer experience from MS, the carriers and the manufacturers so far that is your right. Don't think for one second I won't come right back at you as nothing any of these companies can do or has done will ever change my perception. There are only 2 words to describe this process...CLUSTER F***K!
@ jvanderburgh007 Who's making threats...let alone idle ones??? It is an absolute certainty, not a threat, that people, including myself, will drop this platform if these things are not worked out. I don't think anyone has said anything on these comments on any post that I would classify as a threat, idle or otherwise. People need to vent and people should be letting companies they do business with how they feel about their products and services. If that makes you a little wet in the eye sockets then that is what you deal with. Don't expect others to start pooping rainbows because they will " eventually" get an update for their phone. We all have expectactions and MS along with the carriers and manufacturers have all let us down so far. Same as I told @Krush, if you don't like a comment and want to voice your opinion on it that's your choice and your right. However you should expect the same.
The Skype integration in the latest webOS is pretty sick,if webOS had 4.3" screens and no slide out keyboard just a touch screen I should have quit WP.Now I'm hoping for 2 things from WP,one is a front facing camera on the next WP and the second is a good Skype integration or a great Skype app,in both cases having video chat capabilities.If by March 2012(thats when my WP contract ends) these two a still missing then I'll say goodbye to WP and come when it will be more mature (2015
I am not really technical in this area, but a simple question about the problem with the Focus - it looks like Samsung did not have any problem at the time of manufacturing the device with the alternate memory, they could install the whole operating system without much problem, but now they are all having this great difficulty with this seemingly small updates because of the alternate memory. I just can't understand this issue with my common sense ( not real technical know how).
Would appreciate anyone explanation , if there really is one, which i highly doubt.
@Drankurn, how do you figure Samsung had alternate memory at the beginning? Version 1.3 was the spec that Microsoft saw and approved for compatibility. I've not seen any indication that there were variations on the device until 1.4 came along.
BTW, let's say, for the sake of argument, they did have alternate memory across the 1.3 version devices. I'd argue that the way the OEMs put the OS on the devices is likely a bit different than the Zune Update method we users have to follow. So, it could very well be that the mass install process used by OEMs works with no issues but that the Zune update process is more flawed. I don't find that difficult to believe at all.
@ScubaDog2011 I was not talking about variations in v1.3, I am saying that when they started producing v1.4 that they seem to not have encountered any problems installing the operating system, and now it's apparently causing problems with updates, and according to MS it's very complex problem that it's taking months to find a solution.
I would think that MS knows a lot about different hardware components in the products that use their operating system e.g. PCs, WMobile, etc. that I am having really hard time believing that just a different memory module would cause such a big problem.
As I said ... the flash NAND in the rev1.4 phones has a *hardware defect* and Microsoft is trying to figure out some sort of work-around. They could be successfull but it is unlikely.
Wait and see...
@jvanderburgh0 - So tired of this line of reasoning. Having multiple OEMs on multiple carriers doesn't mean anything. What matters is how Microsoft decides to approach it. Us early adopters bought in, in part, because Microsoft released statements about providing consistent updates and pointed to the facts that they had laid out hardware requirements for all OEMs to follow. In short, Microsoft made statements which made WP7's update ecosystem more like iOS's rather than Android's.
Now, yes, it's come to light that some OEMs - I'm looking at YOU, Samsung - decided to deviate, slightly, from Microsoft's requirements. But that, alone, shouldn't be a stumbling block. That, alone, should not allow carriers to own, and control, the entire update ecosystem.
I said it several times during the NoDo nonsense, and I'll say it again.
Updates should go like this:
- OEM delivers firmware updates to Microsoft for all of their WP7 models.
- Microsoft appends firmware updates to WP7 OS updates.
- Microsoft delivers updates through NEW Zune software.
-- (In the case that OEMs need firmware updates but there is no corresponding WP7 OS update, Microsoft would ALSO push those through Zune software).
Now, that takes care of the major OS updates and OEM firmware. But there's also the carrier integration. However, let's be honest here: Carrier integration in WP7 is really nothing more than advanced app development. So you have a team of folks at Microsoft who work with the carriers to ensure proper integration, then the carriers deploy their updates through Windows Marketplace.
There's ZERO reason, other than laziness on Microsoft's part, for the carriers to be middlemen for the updates. That makes the updates more like Android and I purposely went to WP7 from iOS to stay AWAY from the dismal Android update issues (because Microsoft stated that wasn't how it was going to be done).
But it's clear to me, now, that Microsoft has no intentions of really supporting this platform as well as they stated. If they did have those intentions, they would have already built a new version of the outdated, clunky, Zune software from the ground up specifically for Windows Phone, allowing us to have better connectivity with our phones, including user backups, local sync, and update delivery.
Whatever, it doesn't matter. I'm very disappointed in this platform, disappointed in Microsoft's inability to back up their statements (so it's hard to believe them, or be enthused, regarding Mango statements), disappointed in the app building process, disappointed in the update system.. so on and so forth. And, clearly, I'm not the only one. comScore tells the tale; Month-to-month, Microsoft keeps losing overall marketshare in the mobile space (Nov '10: 9.0% marketshare; Apr '11 (latest report): 6.7% marketshare - a staggering 2.3% DROP since the release of WP7, with no sign of the drop leveling off).
I'm with Drankurn. I have a rev 1.4 Focus and the operating system runs perfectly fine on it. I also do not understand why there is such a problem with the updates when the core operating system runs fine on the "Alternate Memory". Obviously they didn't install an alternate operating system on my phone since Microsoft didn't even seem to know about the alternate version of the phone.
I just wish I could get a real answer from either Samsung or Microsoft. I have the rev1.4 Focus and not really concerned with the current updates, 7008, 7390 and 7392. What I'm concerned about is the Mango update. Will the rev1.4 get this update or not???
I bought the phone on 6/1 and I have until 6/30 to return the phone. If I can't get an answer by then, I'll return this Focus and get the new HTC HD7S phone or I'll go Andriod and get the Infuse.
If you can return it, pressure AT&T to give you a rev1.3 Focus. Personally, I will never buy another Samsung.
No one is listening to me when I tell them that there is a hardware issue with rev1.4 related to either reading or writing the alternate NAND chip.
Microsoft could, of course, tell me I'm wrong right here, right now on this forum and put everyone's mind at ease...
@Captiosus, I'm pretty much in full agreement with you there, but I don't think I believe the relationship with the carriers is about laziness on Microsoft's part. The conventional wisdom, which I subscribe to in this case, is that since Microsoft was SOOOooooo late to the party they had to forge some pretty horrible (from our perspective) agreements with carriers in order to get any kind of saturation in the market. In other words, they were not playing from a position of power getting WP7 out there. i think two things will change this, though. With all the news flooding us about Mango today, I believe Mango will even the bar, perhaps raise it in some areas (depending on what consumers find desireable). The other thing is Nokia. Establishing Mango + Nokia starts to move the power back to Microsoft, in my opinion. This may mean (I hope) that starting in 2012 Microsoft can forge better agreements w/carriers and put them in their place. That NEEDS to happen, as far as I'm concerned.
@jburch, I keep going back to my earlier post. It may be that the way the OS is flashed onto the devices at the OEM is different from the way the UPDATE process works. I can understand how it could be different enough that it chokes during update. Think about it this way: at the OEM you're dumping a fresh OS with no concern about previous data or settings. There's no backup needed, no moving of data to temporary areas, nothing like that. It's a straightforward dump onto the machine. The update process, in contrast, has to do a LOT of different things to preserve what you had. Think of what your desktop computer goes through when you do an in-place upgrade from one version of Windows to another. I have run into, on occasion, instances where the in-place upgrade didn't quite work, forcing me to just do a wipe & load. I lost everything, of course, but at least I was running the new OS. So, I'm saying that I can understand why they might be having difficulty. Particularly if the NAND in 1.4 truly has a flaw in it.
@ScubaDog2011 I believe you have assessed the situation correctly. MS was not in a power position and had to probably make some awful awful deals to get carriers to sign up with them. More market saturation, gaining access to new markets, the Nokia deal and Mango coming in the fall hopefully will strengthen MS's position.
If the 1.4 can't handle updates then by now they should have arranged an exchange program for them. We are theoretically within 4-6 months away from Mango and if my phone can't install very small updates, there is no way it is going to handle Mango.
I like some of the others really don't care about the updates that have passed me by so far. But nobody will be able to convince me that I will be able to install Mango if I can't install these small updates.
I find myself checking these blogs everyday just to find out if I am ever going to get the phone that I paid for and that I am locked into a 2 year contract for. It is beyond frustrating.
Market saturation is not going to change any of the carrier partnership situation.if Microsoft letdown carriers in the long run,carriers can still still inhibit the growth of windows phone,especially in the US and Canada were there're no unbranded devices being sold.Microsoft provides the phones and OS but the carriers provide the network.So Microsoft can only plead with carriers to ensure a smoother update process,but will still have to go through carriers.And remember each carrier network has a way it is established and a way it operates so you should never expect to have the updates delivered at the same time.in a few words,when WP gains market share you customers will be the ones to pressurize your carriers so they deliver WP updates more efficiently.
What you rely on to take you to the top,is what you are the most afraid to lose,because is what can bring you down
@jbirch...exactly my point and what the carriers, manufacturers and Microsoft have failed to realize...we the consumers are locked into 2 yr contracts and all we're asking for is the truth. I don't see why either Samsung or Microsoft or both can't give us a direct answer.
What's even more frustrating is that via CNET, they have a very nice technical article on Mango and guess what kind of phone they're using for their demos, you got it, a Focus. I'm guessing it's a rev1.3 Focus!
Hey Microsoft...are you guys paying any attention here? Can't you tell that you have some very unhappy customers and all we want is a straight up answer? I personally could care less about the 7008 or 7390 or 7392 updates...I want to know if my phone is a lemmon and if I should return it while I still can. Will the rev1.4 receive the Mango update?
Ok no news again today on the Samsung Focus...not surprised. Looks like my thoughts on the timing of feb/march updates for the Focus with the memory variant taking until at least mid-july may in fact be true. Oh, and you know there is another US holiday coming up for which I am certain those "working" on this issue will find themselves taking yet another undeserved 3 day weekend. MS / ATT / Samsung I hope that you prove me wrong and get this update prior to the holiday but I have a strong feeling it will not happen. I see @FuchiStar's point when they said that the 1.4 firmware rev. is not going to be updatable and MS / Samsung / ATT may be looking for a way out replacing every phone they sold with this issue. The only problem I see with this theory is that ATT could not have sold that many of these phones when the total number of phones sold is not even that great based on what ATT has publicly stated more or less. MS you better start coming up with some answers. This has gone on long enough. You may find yourselves in legal trouble if these issues are not resolved. Your arrogance will blind you into believing this won't happen but it would be wise not to tempt those that you have impacted by this mismanagement.
I have a OrangeFR/Omnia7
i am still stuck to the 7008, zune tell me that I am up to date ............
does someone with OrangeFR/Omnia7 is still stuck to this update or does it come from my own phone ?
does someone received any update notification ?
@RaxX : I've OrangeFR and Omnia 7 too, I check for updates every day but zune tell me I've the last update available ... Someone says that scheduling step lasts 10 days or less so I guess we'll have the update friday or early
I have a OrangeFR/Omnia7 too
i am still stuck to the 7008, i check the update everyday but zune alwyas tell me that I am up to date ........
i was wondering when i can get the update notification....:(
i got the update notification today....my phone is being updated to 7392 now.....:D
Got the updates laste night on my Omnia 7... Happy days!
Orange UK Omnia 7 - I've got it. Hurrah!
Prompted when i plugged into Zune this evening. Updated fine - However i still have the bad 18.104.22.168 bootloader :(
However I can now get into download mode by pressing camera, volume up and power on. Woop.
hi for all
my omnia 7 cant get my phone into download mode
I do not turn
my phone hang to logo samsung omnia
Does anyone know how I can solve this problem