Still Image Performance

Now that we’ve gotten the basics of the Lumia 640’s camera system and camera software out of the way, we can move on to evaluating the actual image quality. The most relevant phone to compare to will be Motorola’s Moto E, which sells for around the same price but sports only a 5MP rear-facing camera.

The first photo comparison is the standard daylight test scene that I use. The branches of the trees in the frame are a good test of spatial resolution, while the various different textures can be examined to see how the phone handles noise reduction and maintains detail during processing.

'

With ample lighting, the Lumia 640 performs very well considering its price. I do find that the Lumia 640’s white balance tends just a tiny bit too far toward yellow in this case, and colors are a bit undersaturated, but the overall image quality is pretty good. When you compare it to the Moto E, it’s clear that the Lumia 640 is much sharper across the entire frame, and ends up maintaining much more detail. A good example is the brick texture of the red building on the left, which is maintained in the Lumia 640’s shot but completely scrubbed away in the Moto E’s photo.

As for comparisons to other 8MP smartphones, the Lumia 640 tends to fall behind when it comes to sharpness. The Nexus 5 with its larger sensor ends up capturing the tiny interlocking branches of the trees with much more sharpness, and maintains the black bars of the furthest gate on the left which have become a grey unresolved area in the Lumia 640’s photo. This doesn’t mean that the Lumia 640 performs poorly relative to its price. On the contrary, its performance in daylight is extremely good for a $129 device.

While even the most inexpensive devices can now produce usable photos when there's good lighting available, low light photos tend to be where devices stumble. To see how the Lumia 640 performs in low light, I've taken photos of the same scene as above but at night. With the sun having set, the only sources of light in the frame are a handful of lamps on buildings and along the red brick road.

In the low light scene, the Lumia 640 actually performs better than I had expected. I would say it actually outperforms the Nexus 5. While it doesn't show as much in the scene as the Nexus 5 due to its exposure, and not near as much as the iPhone 5s, it has very fine noise and good sharpness in the areas that are exposed. The Nexus 5 by comparison shows a small bit of the sky and the leaves of the first tree, but the entire image suffers from distracting chroma noise which ruins much of the detail. I certainly didn't expect this from a 1/4" sensor without OIS, and much of it is thanks to Microsoft's superb image processing. My one complaint is that there's a lot of flare from all of the light sources in the scene, and the lamp on the right is particularly distracting because of it.

As far as smartphones in the $100-150 range go, the Lumia 640 definitely has the best camera I've seen to date. The Moto E simply can't compete with its smaller 5MP sensor, and Microsoft's high quality image processing ends up producing photos that are better than the 13MP ZenFone 2 in many ways, which goes to show how a device's image processing is just as important to image quality as the actual sensor itself.

Video Performance

The other side of a phone's camera quality is how it performs when taking video. Taking videos is also arguably a more intensive test of a device's camera system than taking still photos, as device's image signal processor has only a short time to process images. There's also no way for devices with OIS to use it to enable long exposure times, as the exposure time for each frame can't be any more than 42ms, and usually less.

The Lumia 640 can capture 1080p video at 24, 25, and 30fps. For this test I opted for the 30fps mode, as the higher frame rate comes with less motion blur. The Lumia 640 encodes its 1080p30 video with an average bitrate of 17.6Mbps using the H.264 Main profile.

Video footage from the Lumia 640 ended up being quite decent. The bitrate is just as high as high end smartphones, and the footage isn't really any blurrier or noisier than what you'd get from something like the iPhone 6 at the same resolution and frame rate. My one complaint is that Microsoft's EIS doesn't seem quite as effective as the EIS that I've seen on other smartphones, and as a result the footage is a bit shakier. There are also some fairly dramatic changes in exposure and white balance when changing the target of the shot, and in certain circumstances such as when the camera is being pointed at red flowers it actually ends up making the video look too cold. However, the overall video quality is very good, and is miles ahead of other inexpensive devices that I've looked at recently like the ZenFone 2 and the Moto E.

Camera Architecture and UX Battery Life and Charge Time
Comments Locked

130 Comments

View All Comments

  • GlynG - Thursday, June 11, 2015 - link

    Agreed. I've recently got a 640, my first windows phone, and the scroll speed is slow. Why can't they have an option to adjust it as the user wishes? First thing I do on getting a new computer is to adjust the scroll stopped to max and I'd do the same here if I could.
  • Margalus - Thursday, June 11, 2015 - link

    this scroll speed issue is not an issue with windows phone, it's an issue with the specific phone. My HTC One M8 scrolls just as fast as android, or as slow. Depending on you swipe or flick.
  • Michael Bay - Tuesday, June 9, 2015 - link

    I wish more WP phones had sensorcore thing. My 730`s pedometer is really quite handy.
  • cheshirster - Thursday, July 30, 2015 - link

    640 has it
    630 too
  • BMNify - Tuesday, June 9, 2015 - link

    The Matte Black Lumia 640 looks and feels much better.
  • MrSpadge - Tuesday, June 9, 2015 - link

    About the camera app: Brandon, if you change either ISO or shutter speed the software is adjusting the other one to get you a picture as good as it can. If you want to over- or underexpose the image, there's a separate setting for that.

    Honestly I don't know why anyone short of a professional photographer with a huge DSLR in a special situation would want to set ISO and shutter speed manually and try endless times to get just the right exposure. A live preview of the real captured image would help with that, but on a mobile screen outdoors that preview may not be very representative of how it looks like on a normal computer screen anyway.
  • Brandon Chester - Tuesday, June 9, 2015 - link

    If you adjust both the preview doesn't change. The manual mode is poorly designed.
  • MrSpadge - Wednesday, June 10, 2015 - link

    I know, that's what you said in the article. However, my point was that one should use the exposure adjustment, optionally together with either ISO or shutter speed. This takes better care of pretty much anything you could want from manually changing ISO and shutter speed. Except for images which are pretty much only black or only white.. but those could be better produced with Photoshop than a camera.
  • tanyet - Wednesday, June 10, 2015 - link

    Hardly. The manual mode is one of the best things about Lumia's and get copied often. You're not really seeing a good representation of the image until you get it on a pc anyway.
  • bman212121 - Saturday, June 13, 2015 - link

    Actually it's a PEBKAC issue. The manual mode is identical to that of an SLR. There is no "preview" in view finder because it's not really possible to preview what adjustments the shutter speed has on an image in real time. Using 100 iso with 1/20 of a shutter speed vs 800 iso with 1/160 shutter will give the same exposure but provide much different images especially if you have a moving subject. I suspect all you are looking for is a way to tell if the exposure is correct or not. On an SLR there is usually a grid in the bottom of the OVF with +- 3 stops and a little arrow that will tell you if you are over or under exposed. This is represented by the EV (labeled brightness) number in the upper right corner. As MrSpadge said you can simply look at that number and use it to determine the correct exposure which is most cases it should read 0. That should be a much more precise value than trying to eyeball the brightness from a pseudo preview on screen.

Log in

Don't have an account? Sign up now