Nokia Lumia 930 Reviewby Brett Howse on September 8, 2014 3:00 PM EST
- Posted in
- windows phone
The Lumia 930 packs a 5” 1920x1080 resolution AMOLED display into its chassis. As seems to be the norm for higher resolution AMOLED, the Lumia 930 uses a RGBG Pentile matrix. AMOLED seems to have a lot more issues with color reproduction than most LCD displays, but the recent showing from Samsung with the Galaxy S5 and especially the Galaxy S5 LTE-A model have proven that an accurate AMOLED display can be done. The question is if it was done in this case. As display quality is one thing that can still differentiate one device from another, it is an important point. No part of a smartphone is used more than the display.
The latest Lumia devices with the Nokia “Cyan” firmware offer more customization of display settings than ever before, with fully adjustable brightness, and the ability to adjust color temperature, tint, and saturation. This is a huge step forward, but the hope is that the display can be accurate out of the box as well.
Like the Lumia 630 we recently looked at, the Lumia 930 also supports Nokia’s ClearBlack technology for better outdoor viewing and better black levels due to a reduction in reflections in the display layers. In addition, the device has Corning Gorilla Glass 3, a high brightness mode for outdoor viewing, and a second enhancement for outdoor viewing which Nokia calls “Sunlight readability enhancements” and is a method of performing content-adaptive backlight control (CABC) to adjust the perceived brightness of an image, but rather than doing full-frame CABC which is the common method of doing this, Nokia’s implementation utilizes Assertive Display technology from Apical. Rather than perform the CABC on an entire image, Assertive Display performs the adjustment on a per-pixel level. This can dramatically increase the usability of a display in bright sunlight and it does so without necessarily using more display power. Below is a sample of the Lumia 930 with the feature both on and off.
Sunlight Readbility Off (upper picture) vs On (lower picture)
This photo is somewhat of a worst case scenario, with a very dark image outside under the full sun. The bottom image is with the Sunlight Readability Mode enabled, and you can see that more of the image is visible.
To test the display accuracy, we turn to Spectralcal’s CalMAN 5 software package with a custom workflow. We utilize the X-Rite i1Pro Spectrophotometer for color accuracy and saturation, and the X-Rite i1Display Pro for contrast ratios. As this is an AMOLED display, we generally ignore the contrast ratios and black levels since the black level of AMOLED is zero, meaning the contrast ratio for all AMOLED displays is infinite.
The maximum brightness is very good for an AMOLED device at around 400 nits. Other 1080p AMOLED displays include the Galaxy S5, which only comes in at 350 nits. The maximum output was achieved in the outdoor viewing mode, with normal brightness levels kept much lower. It is a good result for this type of display and certainly helps with the phone being able to be used outdoors.
Now we can start to see some issues with the Nokia’s implementation of this AMOLED display. White Point is pretty good at 6347. What is missing though is green, which starts to drop off almost immediately after 5 to 10% white level, and then continues to fall right up until 100%. This leads to a grayscale average dE2000 of 9.4777 with the upper scores causing most of the issues. The grayscale almost perfectly follows an inverse of the green levels in the overall image.
Saturation accuracy is also not fantastic, with a dE2000 average of 6.6579. It is not helped either with the grayscale being so far off, which really pulls this score up. But regardless of grayscale, the saturation sweeps show all of the colors are off.
Like the saturation sweeps, the Gretag Macbeth color checker also has a dE2000 average of over 6, which is not great. There is really nothing here to focus in on as being well done. Out of the box, there is clearly no effort put in to calibrate the display at the factory which is a shame because other competitors are putting this effort in.
As part of the Nokia firmware updates, we can finally adjust the individual aspects of the display now. Not only can brightness be adjusted on a slider, but color temperature can be adjusted from warm to cool, tint can be adjusted from green to purple, and color saturation can be adjusted from neutral to vivid. This allows us to compensate for the lack of green and try to get the display into a much more accurate mode. While not a true color management system, it is certainly better than no options, or just generic options like “cinema mode” or other such methods of changing the profile of the display.
I performed some adjustments of the tint in order to pull the green values up, and the results were much better. While the white point was increased to 7006, the green values averaged much closer to 100 with this adjustment. Grayscale was still not perfect at 4.03, but it was much better than the initial results of 9.477. Saturation accuracy improved dramatically to 3.6781, and the Gretag Macbeth came all the way down to 3.075 which is right in line with the upper boundary of what you would consider a good display.
The disappointing part is that the display wasn’t dialed in out of the box. Clearly with not much effort, Nokia could have made this display more accurate because a simple tint adjustment brought the numbers way lower.
Overall, the display is a mixed bag. 1080p on a 5” screen means 441 pixels per inch, which is good. The pentile RGBG subpixel layout does not appear to be an issue once the pixels per inch get high enough. Images are very sharp and crisp, and the larger size works well with Windows Phone and gives you access to more tiles on your home screen without having to scroll. I have always like AMOLED on Windows Phone, because the operating system lends itself well to high contrast and good black levels, with AMOLED displays really shining with their true blacks. Unfortunately the color accuracy is quite poor though, and while it can be adjusted, it is too bad that it does not get any sort of calibration at the factory like some of the other flagship devices now.
Post Your CommentPlease log in or sign up to comment.
View All Comments
pjcamp - Tuesday, September 9, 2014 - linkNot a dev. THE dev. Marcus Duarte himself claimed that users find two storage locations confusing.
How we've muddled along with multiple storage locations on laptops all these years must confuse HIM to no end.
Besides this is Linux. It is possible to make a single file system spanning multiple devices. There's no reason Android couldn't clear up the "confusion" that way.
tuxRoller - Tuesday, September 9, 2014 - linkThis ^
I guess they've never heard of lvm/MD/btrfs.
Alexvrb - Tuesday, September 9, 2014 - linkThat's not limited to Linux. I mean heck there's multiple approaches, some are completely software agnostic.
Anyway, MS tried something like that with Windows Phone 7. It creates another problem when the user wants to REMOVE the memory card any time they want (users are stupid, this was a common complaint with WP7 I kid you not, result was WP8 separating the two again). WP 8.1 has a better middle-ground solution. Keep the spaces seperate but make better (and easier) use of the memory card.
BMNify - Monday, September 8, 2014 - linkThen get Lumia 1520 or 1320 or 630 or soon to be released Lumia 830 and 730, loads of options for MicroSD fanatics.
jimbo2779 - Monday, September 8, 2014 - linkThe issue is that this is meant to be the flagship phone at a reasonable size, the 1520 and 1320 are too big for the majority of users, the 830 is running a far inferior SoC, less RAM, poorer quality screen and camera, everything lower is in the same boat as the 830 or even worse so really the lack of SD card support here is it's main disappointment.
I was looking forward to this phone so much only to find out it had no SD card support, any user of a Lumia (or other WP phone) with SD card support knows that it is so easy to use and allows for much more space than is available in a phone.
Would you rather have a phone with 32Gb or 96Gb? I know which I would prefer and I definitely would have bought a 930 outright to replace my 925 as this is an upgrade in every way but for some unknown reason they decided to make it the only phone in this years line-up without SD card support meaning it is a no go for me.
Reflex - Monday, September 8, 2014 - linkThe question is what feature would you drop in order to gain that MicroSD slot? Because the 930/Icon is packed very tightly, it has everything that is in the 1520, yet in a full inch smaller package. Furthermore, it is barely larger overall than most 4.5" phones, so they really packed it tight.
I am not willing to go with a larger phone. The features they did include are all very useful to me, I'd be pissed to lose, say, Qi charging, for a SD slot. I get that you want it all, but there are tradeoffs. Either you get the 930 with SD but without something else that takes up space, or you get it without SD support, or you get a larger phone that has all of it included (1520). The reason the 1520 exists is because there are some who are not willing to compromise. Quite frankly the 1520 is the phone you should be looking at, it was made with you in mind.
Also, the 520 has a SD slot not because its a high end feature but because it permits them to sell a phone with very little integrated storage, putting that part of the cost in the hands of the buyer.
Samus - Monday, September 8, 2014 - linkMost SD cards are slow, the controllers are slow, both add complexity and space to the PCB, most people rarely, if ever, use them, and most importantly, they drain the battery.
If I were designing a small phone, I wouldn't put in external storage, either. Phablets and Tablets, sure...but with everything (especially WP8) becoming cloud-centric now, I don't see the need for physical media in a phone.
ummduh - Monday, September 8, 2014 - linkThe cloud this, the cloud that, cloud, cloud, cloud cloud cloud.
Do none of you people ever go outside the city you live in? End up in the mountains? The woods? A back country road that just happens to not have a signal?
I spend sometimes weeks on job sites out in the middle of nowhere with no signal. No wifi, either, since, ya know, it's a job site.
The cloud is 100% useless in those situations. Yea it's a neat toy, and can be handy when you never ever lose service. And you're willing to pay more and more for less and less data service.
Otherwise, you need storage on the device. 16GB, 32GB doesn't cut it. An endless supply is 64-128GB mSD cards, however, does. After apps are installed, I can only put a couple GB of music on my phone before it's filled. And then I get nagged to death by low storage warnings.
The cloud can go screw itself.
Reflex - Monday, September 8, 2014 - linkAnd in your situation that makes sense. However that is an edge case and the market really isn't, nor should it be, tailored to edge cases. Also, as someone who has compared coverage between carriers, I strongly suggest Verizon which tends to work just about everywhere, even in the backwoods, at least in the northern half of the country.
ummduh - Monday, September 8, 2014 - linkSo, I should pay extra amounts of money, every month, to stream the same data over and over to my phone, instead of carrying said data on my phone to begin with, and not keep incurring ever increasingly exorbitant monthly fees? What sense does that make?
Pay to have the amount of data I'd need monthly (10GBish), over, and over, and over, and over.. etc. Or, $25 mSD?
It's not market tailoring, it's data fees extortion.