Nokia Lumia 900 Review - Windows Phone with LTE
by Brian Klug on April 3, 2012 9:00 PM ESTPerformance
Performance on Windows Phone 7.5 at the moment tops out at almost the same place for virtually every handset. As I touched on before, the platform is still a Qualcomm-only party, and the name of the game is single core 45nm Snapdragon with Adreno 205 at the high end in the form of either MSM8x55, or for the Lumia 900 APQ8055 at 1.4 GHz.
I’ve already penned some thoughts on WP7’s current chassis spec, and in the future the specification will open up with the Tango update (which we’ve seen in the Lumia 610) to a lower-end configuration with MSM7x30 or MSM7x27A. Eventually Windows Phone will move onto dual core SoCs and possibly more vendors, but when and how that happens remains to be seen. The driving factors will undoubtably be both performance, but also improvements to things around the edges like 1080p video encode, decode, and power gains from a 28nm process geometry.
For now however let’s focus on the Lumia 900, which again is 1.4 GHz APQ8055 with 512 MB of LPDDR2. Benchmarking WP7.5 still is a pretty basic thing, since platform consistency somewhat obviates the need for many of the other big cross-platform benchmarks (this will change with Windows 8, however). For now that means our testing is limited primarily to assessing javascript performance with sunspider, browsermark, and WP Bench.
At this point all the most modern WP7 devices are still shipping with essentially the same SoC - 1.4 GHz 45nm MSM8x55/APQ8055. For comparison, the initial launch devices were 65nm QSD8x50 at 1 GHz. With the Tango update performance differences will start to be more of a thing for consumers to care about as it becomes possible to select a phone with a lower end SoC that still runs the Windows Phone UI at a decent clip (like the Lumia 610 we’ve handled). As a result, it isn't surprising at all to see the WP7.5 devices with the same exact SoC all clumped together and performing basically the same. In addition, though the WP7.5 IE JavaScript engine (Chakra) is a huge improvement upon the WP7 JScript engine, it still lags behind the competition on Android and iOS.
128 Comments
View All Comments
Beerfloat - Thursday, April 5, 2012 - link
Yup, I guess there's always a next best thing around the corner in the tech industry. Krait is pretty cool. But then, A15 bundled with a fast SGX or Mali GPU will be cooler still. Tegra 3 does have the benefit of the low power 5th core, plus, for right or for wrong, Nvidia always seems to bring the little extra member benefits.tipoo - Thursday, April 5, 2012 - link
True, but the Krait version of the One X isn't that far away, compared to A15 and all that. The Krait One S is already shipping. And Nvidia's fifth core doesn't help it against Kraits battery life, look at the One S with Krait, it gets significantly higher life (to be fair, some will be the screen, but still). Tegra Zone optimizations apart, Krait is nearly uniformly better.jed22281 - Sunday, April 8, 2012 - link
typical moronic response.ecuador - Wednesday, April 4, 2012 - link
If more people got their hands on the N9's it would not be a dead OS. Even people with the latest iphones are amazed when they try out the N9, something I have never seen with, say, an Android phone.That's why I complain about tech sites not trying to give the N9 the chance that Nokia did not want it to have - it is (was?) by far the most promising mobile OS (not to mention the most open).
jed22281 - Sunday, April 8, 2012 - link
Maemo6x (meego-harmattan) used by the N9 is far from being the most open.Tizen & WebOS are far more open, even Android is arguably....
If it had been given time to evolve into real MeeGo* it would've been w/o question.
There's MeeGo derivatives floating about still (MeR + Nemo/Plasma etc)
But they're more underdeveloped than they would've been, had resources not been dropped hugely in the past 14mth.
*which would've completed by July 12' at the latest w/the 1st x86 phone, after the 3rd Harmattan ph started reaching shelves.
jed22281 - Sunday, April 8, 2012 - link
typical moronic response.Tujan - Wednesday, April 4, 2012 - link
Excellent article about a cell phone from anandtech.com !...
With the exception of memory bandwidth this is certainly a great little computer radio phone.
....
"Waiting is never easy" <- catchy. !
Origin32 - Wednesday, April 4, 2012 - link
And of course half of the comments are about Android phones being slow. Yes, the UI is less smooth than iOS of WP. But I really don't care about that and I can't be the only one. In my humble opinion functionality is king, and whether my homescreen renders at 20fps or 60 doesn't really matter. Android has some great features that I am yet to see in iOS or WP. Having borrowed an iPhone for a couple hours I already found it to be incredibly constraining and the lack of a back or menu button annoyed the crap out of me. As for WP, I played around with a Lumia 800 for a while but all the sidescrolling in the homescreen and in apps was very confusing. It made the display feel too narrow.Plus, I bet you'll all be glad we have quadcore smartphones when they've become so fast you can ditch your laptop, but of course most of you never even considered that :)
valhar2000 - Wednesday, April 4, 2012 - link
People around here keep talking about the superior feature set of Android. What are these features that other phone OSs don't have?Beerfloat - Wednesday, April 4, 2012 - link
Well, HD screens for one. Grown up DPI-independent rendering for another. A choice of different form factor devices to suit various usage patterns and budgets. Multiple software stores, an enormous amount of apps, close integration with Google services (if so desired), wonderful customizability, the most straightforward interaction with other devices like PCs (it's just an USB disk drive, plus it talks CIFS).But oh well.