"This November we introduced Windows 10 to phones including brand new features such as Continuum and Universal Windows Apps with the introduction of the Lumia 950 and 950 XL. The Windows 10 Mobile upgrade will begin rolling out early next year to select existing Windows 8 and 8.1 phones."
It's not made explicitly clear why the update has been delayed, as the OS is already available on Microsoft's recently launched Lumia 950 and 950 XL. From my experience with the beta/developer releases of the OS that Microsoft has made available, it's entirely possible that they still need to work on ironing out bugs and improving performance. Many reviews of the new Lumia phones have a similar sentiment, and with many of the older Lumia devices running less capable hardware from Qualcomm's Snapdragon 400 series than the 950 and 950 XL, it wouldn't be such a bad thing to have the update delayed to ensure it doesn't cripple performance on those phones.
At this time it's also not known how many devices will receive the update to Windows 10 Mobile. Microsoft has stated that phones will need 8GB of NAND, but it's not clear if there are other hardware requirements. Given that the Lumia 550 just launched with Snapdragon 210 and runs Windows 10 Mobile, I would hope that Microsoft plans to update a significant number of existing devices.
Microsoft kicks off 2016 with a problematic Windows 10 Mobile build 10586.63 launch
Microsoft has promised that Windows Insiders get Windows 10 builds faster in 2016, and it's Windows 10 Mobile users who get the first release of the new year. It's a few weeks since the release of build 10586.36 and now build 10586.63 is available for those on the Fast Ring.
You might expect from the relatively small jump in version numbers that this is something of a minor update -- and you'd be right. But despite the somewhat trifling nature of the changes, this release is noteworthy for a fluffed launch.
A problem with the update staging meant that some Insiders were able to detect the update before it was fully deployed. Gabe Aul -- in a series of tweets that could serve as an argument in favor of increasing the character limit on Twitter -- explained that there had been a problem with the rollout which had since been rectified:
No comments:
Post a Comment