Camera Architecture

Due to the more closed nature of Windows Phone, I can’t do much poking around to find detailed information on the cameras in the Lumia 640. The information that I have been able to collect is organized in the chart below. The main omission is the sensor manufacturer, which I would suspect is Omnivison or Toshiba, but I can’t say for sure exactly what it is.

Microsoft Lumia 640 Cameras
Front Camera - Resolution 0.9MP (1280x720)
Front Camera - Focal Length 1.5mm (30mm eff)
Front Camera - Aperture F/2.4
Rear Camera - Resolution 8MP (3264x2448)
Rear Camera - Sensor Size 1/4", 1.12µm pixels
Rear Camera - Focal Length 3.0mm (28mm eff)
Rear Camera - Aperture F/2.0

On paper, the Lumia 640’s camera hardware is better than a lot of other devices at this price point. I recently reviewed the 2015 Moto E, and on paper the Lumia 640 has higher resolution cameras with larger sensors on the front and back, and the front camera has a significantly wider aperture. While the specifications of the camera sensor and lens aperture hardly tell the whole story when it comes to image quality, they definitely put the Lumia 640 in a better position when it comes to sharpness and low light performance.

Camera Focus Latency (Shooting ISO 12233 Target)

Camera Shot Latency (Shooting ISO 12233 Target)

The focus time on the Lumia 640 sits right in the middle of our comparison results. It’s slightly faster than many other devices that don’t have PDAF or laser based autofocus, but it’s not as fast as phones like the Nexus 6, and not near as fast as the iPhone 6 and Galaxy S6 with their PDAF. Shot latency is also right around the middle, and while there is a tiny bit of a delay between shots, I never felt like I was kept waiting for an unreasonable time when trying to take several photos quickly.

Camera UX

A device’s camera application has a big impact on the user’s experience when taking photos or shooting video. If the camera preview is cropped or badly scaled then it’s difficult for the user to gauge what their photos will look like. A high resolution preview and an accurate aspect ratio are necessary to frame and compose photos properly. For quite some time I’ve heard great praise for the Lumia camera application interface and the manual controls that it offers, so I was excited to have a chance to try it in depth.

Upon first opening the Lumia Camera app, I felt like the interface was fairly organized and well laid out. It was immediately obvious that tapping the right-facing arrow in the menu at the top would reveal more controls, and that hitting the gear in the upper right would show me options. Having a button to instantly record video is also very handy. The camera preview would definitely be improved if it were higher resolution, but this is mostly a limitation of the ISP so there's not much that can be done.

Once I started trying to use the manual controls I was very happy that the app uses what is basically a dial interface to make adjustments. It reminds me a lot of the control dials on a real camera, which is a good design decision, as anyone interested in these controls probably has prior experience with photography.

Unfortunately, I very quickly ran into a number of issues with the manual controls on the Lumia 640. The first problem was that I seemingly could only adjust one option at a time. While this is a common limitation of smartphone camera interfaces, it was very annoying because you had to continually move your thumb between the control wheel and the menu at the top. This is a much less ergonomic and more time consuming method of adjustment than something like ASUS’s camera interface where the menu for selecting each control and the menu for performing adjustments are beside each other.

After asking people who were more familiar with Windows Phone, I was told that you can pull outwards on the shutter button to bring up every control at once. I have two issues with this gesture. The first is that it’s not obvious at all. The only way I was able to find it was because I was told by another person, and that alone is a pretty massive design failure. My other issue is that it doesn’t directly solve my problem. I want the settings and the menu for adjusting them to be adjacent, not a giant menu of controls covering up the camera preview.

The fact that you wouldn’t be able to see the changes you’re making reflected in the preview because it’s covered by semi-opaque menus would be a big issue if it weren’t for an even bigger problem with the Lumia Camera application. The biggest issue of all is that camera preview does not change to reflect adjustments to ISO and shutter speed. At first, I had assumed my device was suffering from a bug, but after doing some troubleshooting I asked our editor Brett Howse to confirm that his Windows Phones behaved the same way. When he confirmed that they did I really didn’t know what to say. Having manual camera controls that aren’t reflected in the camera preview makes them essentially unusable. While changes to white balance, brightness, and focus do show up in the preview, your adjustments to ISO and shutter speed do not. This means that you have no visual idea of what the exposure of your photo is going to be.

I wasn’t near as impressed with the Lumia Camera application as I had expected to be based on what I had heard about how camera-centric Lumia devices are. While the interface for auto mode is fine, it’s basically impossible to mess that up unless you're trying to. The manual controls aren’t implemented in a very obvious and accessible manner, and the most important ones require you to just pray that the exposure meter is accurate, which ruins the entire concept of having full control over how your photos turn out.

Display Camera Performance
Comments Locked

130 Comments

View All Comments

  • lolstebbo - Tuesday, June 9, 2015 - link

    "Since this Lumia 640 is locked to Cricket Wireless, I'm unable to also test it on LTE, which is unfortunate."

    Why would the 640 being locked to Cricket prevent you from testing it on LTE?
  • Brandon Chester - Tuesday, June 9, 2015 - link

    Because I'm Canadian.
  • milkod2001 - Tuesday, June 9, 2015 - link

    MS has less then 5% mobile market share...

    What will break this curse?

    1) another crappy low end phone? - NO

    2) high end Samsung / Apple like specs phone with better camera, mSD+rem. battery? - YES
    (MS needs to make killer phone people will talk about and think about getting )

    3) fixing missing apps -YES
    (MS as giant software company can not make the same in house apps as most popular Android / iOS apps? Or just pay developers to make the same apps for Windows Phone? How pathetic is that?)
  • colguy1 - Tuesday, June 9, 2015 - link

    Don't you think MS has not attempted to do that? Back in 2013 MS created a very beautiful Youtube app. I used it for a week in my Windows Phone. But Google made sure that it was removed from the windows phone store. Well known Windows Phone developer Rudy Huyn created an amazing client app for SnapChat. But when SnapChat removed all 3rd party apps, it removed this app too. This SnapChat app was miles better than the first party apps in iOS and Android. The developer requested many times to work with him to whitelist the app and get it in the Windows Phone store. But no response from the SnapChat. MS created a Pebble app and demoed it to the Pebble guy.. Little bit of google search will tell you what happened next.. It is not just entirely MS fault for the lack of apps.
  • jakoh - Thursday, June 11, 2015 - link

    I can say to for no 3, the new cross compiling feature in windows 10 which will allow Java or Objective C to be compiled for Windows will help.
  • Harry_Wild - Thursday, June 18, 2015 - link

    Microsoft needs to get out of the U.S. carrier exclusivity agreement with their high end models. Many people now go with unlock international models that live in the U.S. Total bizarre that Microsoft's home market; they screw the consumer in flavor of the carrier!
  • mockyboy - Tuesday, June 9, 2015 - link

    I need a new non-contract phone and have been considering an Iphone. I have a Lumia 521 right now and even as a casual phone user it's gotten way too slow.

    The thing is whether the Iphone is worth the 5x higher price than the 640. I can get the 640 and an Ipad Mini for around 420 and still save $200. And I work from home, so honestly I'm really not a heavy phone user. The 640 seems like it would be fine for everyday needs, and the few apps I want I can get a Ipad Mini for.
  • StormyParis - Tuesday, June 9, 2015 - link

    Frankly, I'd get a Moto E or G instead. Here's Anand's Moto E conclusion: http://www.anandtech.com/show/9129/the-moto-e-2015...
  • mockyboy - Tuesday, June 9, 2015 - link

    I hadn't considered those, thanks. Although for some reason I've been avoiding Android. I have no idea why. Maybe because I heard bad things about their low end phones, but based on that review I guess that's changed.
  • Callum S - Tuesday, June 9, 2015 - link

    Either that or get a Lumia 640 and Surface 3 with accessories for about the same price as an iPhone by itself. I do however seem to be addicted to OneNote though :-)

    Understand completely in regards to not being a heavy phone user. It doesn't matter how powerful they get, for actually getting stuff done, there is no comparison to using either a mouse and keyboard or a stylus (for diagrams and notes). Until of course phones are at stage where they can be docked and or properly utilise other input methods like the notebooks and tablets can today.

Log in

Don't have an account? Sign up now