Camera UX

For the most part, the OnePlus One has a generally standard camera system for 2014 smartphones. With a 6P lens system, F/2.0 aperture, and Sony IMX214 camera sensor, the OnePlus One has a relatively standard camera system for today's smartphones. The focal length is similar to most smartphones on the market at a relatively wide 3.8mm length, which makes it equivalent to a 28mm focal length when accounting for the crop factor of the sensor. The front facing camera has an OmniVision OV5648 sensor, which is a 5MP, 1.4 micron, 1/4 inch sensor, with an F/2.0 aperture at 2.67mm focal length. This means that the field of view is similar to the rear-facing camera at about 29mm accounting for the crop factor.

While the camera hardware is relatively standard, the camera interface is definitely a unique take, and is the first time that I've been able to use Cyanogen's camera UI. In general, this UI feels like a mix of the old Google Camera, along with an immense amount of complication and not much explanation. For example, in the settings there's an ISO selection menu. While this is nothing to talk about normally, there's a setting called "Auto (HJR)". The only way for me to learn about this setting is by searching for it on Google, which explains that it favors higher ISOs to reduce the effects of shaky hands. As of the latest 44S update, this crashes the camera any time I try to take a photo in low light. To further explain the point, there are plenty of options in the video size setting, but a huge number of them are completely unexplained. While one might easily guess what 4K UHD or HD 1080p is, I find it difficult to believe that 4k DCI, CIF, or QCIF are self-explanatory. Interestingly enough, turning RAW capture on or off also has an effect on the maximum shutter speed, something that isn't actually detailed anywhere.

While an unfamiliar UI is not really a massive issue, there are some fundamental flaws with how the UI works. One of the most obvious flaws is the aspect ratio of the preview, which is 16:9, when output images can have a 4:3 aspect ratio. This makes it impossible to accurately frame an image. In order to do the ISO chart test, it was necessary to use Google Camera to frame the chart before switching back to the Cyanogen camera.

In addition to all of this, the scene selection UI doesn't have much thought put into it. All filters and all scene modes are integrated into a single menu, which is navigated by swiping up and down on the preview. This wouldn't really be an issue but when there are 31 options to swipe through this really gets to be a bit much to handle. There is a list option that can be found by going through the menus though, which is a bit better at organizing information. Unfortunately, most of the scene options are a bit nonsensical. The "night" modes don't actually change anything (ISO and shutter speed seem to be identical), and pretty much everything else is unclear on what it does. The one interesting mode is the slow shutter mode, which sets ISO to 100 and allows the exposure time to go as high as 8 seconds for high-quality photos on a tripod. This is also broken as of the 44S update, which causes the camera to crash until the phone is rebooted. I suspect that OnePlus is better off exposing full manual controls instead of trying to cover every possible edge case with a large number of scene modes that may or may not change anything. There's also no way to get a grid to try and frame images properly.

Speaking of ISO and shutter speed values, while the camera UI was mostly responsive in previous versions, around the 38R OTA I saw a dramatic shift in the auto exposure algorithm as it went from a maximum of 4500 ISO and around 1/11 second shutter speed to 4100 ISO and 1/6 second shutter speed. This has effectively made it impossible to use the camera at night, as there is no OIS present to reduce the effects of even slight hand shake. Overall, all of these issues make the OnePlus One quite frustrating to use as a camera.

Aside from these niggles with the camera application that can generally be resolved by using Google Camera, another area of evaluation is shot to shot latency, along with focus latency. To this end, the device was tested by pointing the camera at the ISO chart with strong lighting to be able to reach base ISO and timing how long the camera took to focus on an object along with how quickly the device could take a photo.

Camera Focus Latency (Shooting ISO 12233 Target)

Camera Shot Latency (Shooting ISO 12233 Target)

The OnePlus One does do surprisingly well in our focus test, setting a rather respectable focus latency around the same speed as the competition. On the other hand, the default capture speed is really quite long, although this is really mostly due to the RAW capture as turning off RAW capture dramatically speeds up response time in the camera to a much more respectable ~750 ms.

Battery Life and Charge Time Still Image Performance
Comments Locked

148 Comments

View All Comments

  • Harry_Wild - Thursday, November 20, 2014 - link

    I saw many interviews were Android App developers were ask what personal phone they are using responded shyly - "iPhone #*". So, that explains many things here!
  • grayson_carr - Thursday, November 20, 2014 - link

    I am an iOS developer and my current phone of choice is the Nexus 5.
  • Conficio - Friday, November 21, 2014 - link

    Care to link to at least three of these "interviews"
  • coburn_c - Wednesday, November 19, 2014 - link

    Why do your custom screen and battery tests never line up with gsmarena? Their screen results always have different white brightness levels then yours, and their battery tests are always more in line with synthetic scores than yours. They put the contrast of this things screen at 800:1 and the battery life below the G3.
  • 2kfire - Wednesday, November 19, 2014 - link

    Re: battery, GSMArena uses 50% instead of a fixed luminance.
  • Cinnabuns - Wednesday, November 19, 2014 - link

    Just to add to what 2kfire pointed out, the author states:

    "200 nits on a phone can be as low as 50% and as high as 90%, so setting a standardized brightness percentage would not be an effective method of controlling for display brightness."

    I would not trust GSMArena's battery tests as they do not understand how to perform a controlled test.
  • coburn_c - Thursday, November 20, 2014 - link

    Their test was in-line with what the synthetic said here and in line with the common sense of less throttling and less software optimization don't make for more battery life.
  • Master_Sigma - Wednesday, November 19, 2014 - link

    Very pleased to see Anandtech coming around to reviewing this phone. While I disagree with the opinion that too many options are a negative, especially given the target audience for this device, I pretty much agree with the assessment of the hardware and software.
  • FreakTM - Wednesday, November 19, 2014 - link

    I think the opinion was more towards the fact that the options were causing some sacrifice on the user-friendliness of the experience, which I think is a fair opinion. Many options, good; many options presented in a confusing way, bad.
  • mrex - Wednesday, November 26, 2014 - link

    Better to have options than not having them. You dont need to use them if you dont want to, but if they dont exist at all, you could only dream about them... the phone is very user friendly, imo.

Log in

Don't have an account? Sign up now