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


View All Comments

  • WinterCharm - Tuesday, June 9, 2015 - link

    That's a really nice phone for the price! :D

    Great look and design, too!
  • JohanAnandtech - Tuesday, June 9, 2015 - link

    That kind of performance is going to get frustrating pretty quickly. Simply using some kind of navigation will quickly show the limits of using an A7 core. Reply
  • Wolfpup - Tuesday, June 9, 2015 - link

    On Android an A9 is dirt slow, while it's not bad running real Windows, much less Windows Phone.

    I've got a 520 and a 635, and the A7 isn't an issue in the 635 at least not for the stuff most people do (certainly including navigation software). This 640 looks like an awesome extension...2x the RAM and a larger screen. Naturally it's coming out not long after I bought a spare 635 lol
  • jospoortvliet - Thursday, June 11, 2015 - link

    As the review makes clear - Windows Phone lost its advantages in terms of performance... Reply
  • jakoh - Thursday, June 11, 2015 - link

    The review compares the 640 to a bunch of high spec'd android and IOS, it doesnt show that WP can run smoothly even on crappy specs. Reply
  • leexgx - Thursday, June 11, 2015 - link

    i do agree i got a nokia 820 seems to work well
    But the Main problem with windows phones is lack of ram some times background tabs are deep suspended and take to long to restore i ignore any windows phone with 512mb of ram but would recommend 2GB as a minimum
  • darkich - Friday, June 12, 2015 - link

    You clearly didn't even read the article.

    The author was specifically comparing this to low end Motorola moto E performance wise.

    And he stated for several times that the whole OS and browser feel really slow in comparison.
  • SirPerro - Monday, June 15, 2015 - link

    "I mentioned in my Moto E review that for a long time I recommended that users who wanted a cheaper smartphone go with Windows Phone over Android, because at the time the options on Android were janky, slow, and offered a poor experience. I can’t make that recommendation anymore, because the app gap is still here, while the experience gap in favor of Windows Phone is gone."

    Article is loud and clear
  • Murloc - Tuesday, June 9, 2015 - link

    not really, I have a 635 and the experience is fluid. Reply
  • testbug00 - Tuesday, June 9, 2015 - link

    Really? L520 running quite smoothly through everything I throw at it (web browsing, some music playing, few notes in OneNote) andf it's a dual core A7 chipset (SD200).


Log in

Don't have an account? Sign up now