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

  • Wolfpup - Tuesday, June 9, 2015 - link

    Out of curiosity, what's slow about the 521? It's main limitation is RAM I think, but then that mostly just means it has to load a bit more when switching programs.

    Of the mobile OSes right now I like iOS best (though obviously I like real Windows far, far better), but I pad $950 for my iPhone and when it broke replaced it with a Lumia 635, and...honestly it's nearly as good, for my use at least. The podcast program actually syncs with iTunes too, and there's nothing on Android that does that for real. (I've seen things CLAIM to, but they don't actually.)
  • mockyboy - Tuesday, June 9, 2015 - link

    Once I upgraded to Windows Phone 8.1, it became noticeably slower. Apps crashing, phone freezing, getting the resuming message for 20 seconds or so. And I don't have that much loaded on it.
  • testbug00 - Tuesday, June 9, 2015 - link

    oh, in that case, a 640 should be fine. The issue you're running into is most likely RAM.
  • testbug00 - Tuesday, June 9, 2015 - link

    Unless you're set on Windows Phone, going with a Moto X 2013 (http://www.amazon.com/Motorola-Moto-XT1058-16GB-Un... is probably the best option.
    Or, if you want/need SD card, get the newest Moto G. Make sure one of the ones with SD card slot, if Moto is still segmenting that.

    From WindowsPhoneLand, there isn't anything that technically has a faster SoC that isn't $300+ iirc. At least, not now.

    If you don't mind buying used, I would check out swappa.com, everything I've got off there has been great so far. hope it still is.
  • Harry_Wild - Thursday, June 18, 2015 - link

    I have an iPhone 6 and it is super fast and has tons of high quality apps too! I use currently the iPhone 6 and Lumia 735. Both are 4.7". I would recommend the iPhone 6 if you can afford it! But the Lumia 735 is pretty nice at the now low price of $200. I purchase it at $300.
  • jjj - Tuesday, June 9, 2015 - link

    It's weird how Metro makes the phones look bulky and crowded, the childish icy iOS rainbows are quite the opposite. Not that M$ should copy that, just the message.
    They also need to dump this kind of back shell. Nokia, iphone 5c, Xiaomi Redmi and many others turned this kind of shell into the definition of cheap and the way they implement it makes the phones bulkier too.
    As for this device ,too bad for the SoC , guess for a startup like Microsoft it's normal to not have the resources to make it's software run on A53.
  • StormyParis - Tuesday, June 9, 2015 - link

    that kind of back shell does make an additional case 'which 75% of smartphone users add) unnecessary. I think the Nokia should be compared to case-equipped iPhone et al, and then the bulk issue goes the other way. I'm not a Nokia customer, but I'd love to have a similar design on my Androids.
  • Callum S - Tuesday, June 9, 2015 - link

    Completely agree here. It's always been a massive benefit. They're normally thinner than even the most expensive phones with a case, that makes them feel cheap and fat anyway, or much better value and safer than using an alternative phone without one.

    Additionally, as someone who has very rarely used phone cases, I have always found phones with easily replaceable cases beneficial for both appearance when I have dropped and damage them (no walking around with cracked phone cases or backs like so many people with iPhones) and for when I want to pass them down to other family members. After a fresh install and a new $15 back shell it's essentially like a new phone for those who aren't too concerned.
  • damianrobertjones - Tuesday, June 9, 2015 - link

    Not bad at all really especially for people that don't care or ever need something faster.
  • GlobeGadget - Tuesday, June 9, 2015 - link

    My first smartphone was Nokia Lumia 800, it was a pretty great phone but it wasn't as great as the 3310 when it met the pavement... :(

Log in

Don't have an account? Sign up now