Here’s a new Windows Phone 7 update rumor that just popped up ahead of tomorrow’s CES Keynote courtesy of Paul Thurrot. Once again grab some salt before reading all this. First there’s the Windows Phone 7 NoDo update (which means No Donuts):
The first Windows Phone 7 software update, codenamed “NoDo,” will RTM in January, possibly this very week and in time for the CES keynote. But it won’t ship to users until early February, once the carriers sign off on it. This update will include the famed copy and paste functional addition, support for the Qualcomm 7×30 smart phone chipset, a CDMA location stack, and a number of software fixes.
So Microsoft is adding support for Qualcomm’s current mid-range SoC and not the MSM8255 or QSD8650A/B which are the logical successors of the QSD8250? This doesn’t’ really sound logical. Are OEMs going to start shipping devices with Adreno 205 GPUs (which is a lot more powerful than the current Adreno 200 found in the current devices) and start fragmenting the ecosystem ? CDMA location stack or CDMA “radio” stack ? Anyway, Microsoft already mentioned in October in the official FAQ (and latter took it down) that Windows Phone 7 supported CDMA, LTE, WiMAX and WP7 devices have already been spotted tested on Verizon’s network a couple of months ago.
While I’m not sure on the timing, the first major Windows Phone 7 update contains a piece called “Mango” internally; this will add Internet Explorer 9 with with the Trident 5 rendering engine, HTML 5 and Silverlight, and gesture support. This is the “75xx” code branch, which suggests that it could be called Windows Phone 7.5. (But probably won’t be … It actually calls itself Windows Phone 7.2 at this time.). Internally, this code branch is referred to as the “entertainment” branch, which suggests other, non-IE functionality as well.
I would really be pleasantly surprised if Microsoft was able to port the IE9 trident 5 engine and ship it in Windows Phone 7 only a couple of months after it’s desktop launch. The last I heard was that Microsoft wasn’t really planning on adding in-browser Silverlight support thought. BTW, what is “gesture support” ? Anyway, let’s all patiently wait and see….. oh and No Donuts sounds like #tdmp -> Pink –>
UPDATE: Charlie Kindle just posted the following:
BTW, a guy failed to bring donuts to a meeting after loosing a bet. The “nodo” codename had nothing to do with Android.
As you can see in this picture I shot, the internal MoJo builds were already at 7112 back in August :