by abulhussain
Everything that can go wrong with Windows Phone 7 update does
[Via Ars Technica]
It’s amazing. Given the importance that Microsoft’s smartphone platform should have—not to mention the uphill struggle it faces against the iPhone and Android juggernauts—one would have thought that the company would make sure that delivery of the first patch was rock solid and reliable.
After all, robust, universal patching is one of the big advantages of Microsoft’s platform over Google’s Android. Microsoft’s locked down hardware requirements, in conjunction with its centralized patch distribution and offical (albeit carefully-worded) statements to say that all devices would be “eligible” for updates, should have given Microsoft an almost Apple-like patch process: uniform availability, regardless of carrier, regardless of OEM, regardless of model. And because every phone is running the same software, well, it should all just work, shouldn’t it?
[More]
So, phones are getting bricked during the update process. If I were Microsoft, I’m hoping it is just a few handsets. But, as Apple saw with ‘Antennagate’ all it takes is a few to create a real firestorm of bad publicity.
Updates may not be finishing requiring rebooting without the update. This looks it might be due to the lack of strong connection between hardware and software, in that certain firmware versions of the phones work and other versions do not.
And get the process to find out if they can get their phone to work again.
Those unfortunates with apparent firmware corruption can try forcing the phone into download mode (turn off the handset, then turn it on while holding the camera button and the volume down button, and keep all three buttons pressed for 10-15 seconds; then choose the “format” option).
That is obvious. To find out which firmware someone has, they must do this:
Figuring out which firmware version you have is a somewhat awkward procedure. From the phone’s dialer, type ##634#, then press the call button. This will start up Samsung’s Diagnosis application (it will also create an icon for it in the phone’s programs list, so that you can go back to it in future without using the dialer).
In the Diagnosis application, type *#1234#. This will show a screen of detailed version information. It’s the first three version numbers (for “PDA”, “Phone”, and “CSC”) that are relevant here. If the firmware versions are older (JIx, JJx) then the update probably won’t work; if they’re newer (JKx) it probably will. But there are no guarantees.
Very user friendly. If the phone is bricked, it can only be replaced at the wireless carrier. I’d imagine the cost of the bricked phones comes out of Microsoft’s pocket. If it comes out of the carriers, I’d imagine they will be very hesitant about selling the phone in the future. If the handset maker gets dinged, they might not want to make many more in the future.
Where is the robust QA/QC that Microsoft was supposed to provide that is not seen in the Android world, supposedly?
In addition, it may be that some phone carriers are blocking/delaying the update entirely. So, even if the phone has not problems, the owner’s can’t update without the carrier’s permission. Perhaps in this case, that is a good thing.
As the article states, this was not supposed to happen. Microsoft’s tight specifications was supposed to prevent problems across dfferent carriers using phones made by different handset companies.
Looks like that expectation was wrong. Compare this to Apple which makes both the software and hardware, with two versions of the handsets. It disctates updates, without the carrier interfering. It can easily check out its updates on a very few models.
In the alternate world of MS, who is responsible for making sure the thing works? The handset guys can see if it works. If there are problems, they have to wait until the software company fixes it. Of course, Ms is then dealing with what, 4-5 different versions of handsets from multiple makers on multiple networks.
Why in the world would anyone buy a phone that gets bricked on its first update? This means someone somewhere screwed up. Even if they fix it, as an owenr, I’d be worried about the future. When the cut-and-paste update comes along, what’s going to happen?
Jobs made sure that nothing would be put on the iPhone if there was any chance it made the phone unusable. People will get by without apps if the phone works. It does not seem MS has the same dedication to detail.
They have a mobile phone that gets bricked. They have no tablet strategy. Perhaps MS should just admit that it has a kick-ass gaming system and divest itself of anything else.
Like this:
Be the first to like this post.