Camera Architecture & Still Image Analysis

Samsung's real potential has yet to be realized as a highly vertically integrated silicon and device house. The Galaxy S 4 for example still relied on a Qualcomm SoC with a Sony sensor for the rear facing camera. While the GS5 continues to leverage Qualcomm's silicon, Samsung did transition to its own sensor for the rear camera module as well as the front facing camera.

The front facing camera remains 1080p, despite competitors like HTC moving to 5MP. The front camera uses a 16:9 sensor with 1.12µm pixels shooting at 1080p.

Samsung Galaxy S 5 Camera
  GS5
Front Camera 2MP
Front Camera - Sensor S5K8B1YX
(1.12µm, 1/7.3")
Front Camera - Capture Resolution 1920 x 1080
Front Camera - Aspect Ratio 16:9
Front Camera - Focal Length 1.2mm
Front Camera - Max Aperture f/2.4
Rear Camera 16MP
Rear Camera - Sensor S5K2P2XX
(1.12µm, 1/2.6")
Rear Camera - Capture Resolution 5312 x 2988
Rear Camera - Aspect Ratio 16:9
Rear Camera - Focal Length 4.8mm
Rear Camera - Max Aperture f/2.2

The rear camera is the interesting one as it uses Samsung's own 16MP 16:9 sensor. This makes the GS5 and M7/M8 the only two modern shooters we have with 16:9 rear facing sensors. The GS5 unfortunately doesn't move to larger pixels, remaining at 1.12µm. To somewhat improve low light performance, Samsung is using its own ISOCELL technology to reduce crosstalk between pixels by introducing additional barriers between individual pixels. The video below does a decent job at summarizing what we know about ISOCELL:

Unlike Apple and HTC, there's no dual-color flash on the GS5 - just a single LED unit.

As always we turn to a collection of controlled test shots and live scenes to evaluate the GS5's camera quality.

Spatial Resolution

We'll start by measuring the rear facing camera's ability to resolve fine details by shooting at an ISO12233 test target. For now we'll be looking at horizontal and vertical resolution using the sagittal and tangential lines in the upper right of the center of the test chart:


ISO12233 captured by Galaxy S 5

The gallery below has links to the original chart captures for all of the phones compared in this review:


The GS4 already did well in this test, easily resolving the entire length of sagittal lines. The GS5 maintains slightly more detail past the 18 mark (units of line pairs per image height). The iPhone 5c and 5s do reasonably well here but can't resolve detail as well at the very left edge of the crop. Google's Nexus 5 has similar struggles, although nothing is anywhere near as bad as HTC's M8. Here we see the real limits of HTC's 4MP UltraPixel sensor as there's serious aliasing around the 12 mark. Sony's Xperia Z1s running in its native 20MP mode on the other hand is the clear winner here.

You can see full 1:1 resolution crops in the gallery below:


The story is unchanged if we look at the tangential crops as well. The GS4 and GS5 remain among the upper contenders in this space, losing out only to Sony's Z1s. Interestingly enough the GS5's image appears to be softer than what the GS4 produced. We'll have to spend some more time with Samsung's ISOCELL sensor to really get a feel for the images it produces.

Outdoor Scenes (Day & Night)

We grabbed test shots from four different locations using the GS5 and its immediate competitors. I've included all of the originals in the galleries below, but let's take a look at crops from a couple of them first.

I'll start with a low light test shot as that's one of the more challenging environments for such a sensor with such tiny pixels. Here we'll be able to see just how much ISOCELL buys us:


The GS5 shot this scene at 1/15s, ISO 2000. The GS4, by comparison, kept the shutter speed the same but ran at ISO 1000. The GS5 is naturally brighter as a result, but without substantially more noise. The image is relatively usable. Toggling picture stabilization (the new word for night mode on the GS5) trades off noise for exposure length, although Samsung obscures the latter in its exif data. When shooting without a tripod, longer exposure times aren't desirable (particularly without OIS).

The GS5's low light performance obviously pales in comparison to devices with larger pixels like the M8 and especially the iPhone 5s. There's an obvious tradeoff here. Samsung delivers clearly better spatial resolution (as seen from our ISO12233 test shots), while HTC on the other hand offers better low light performance. Apple finds itself in the middle of the two with the iPhone 5s. The Xperia Z1s does give us a good example of what you can get from oversampling as we're shooting in the 8MP superior auto mode here.


Moving to the opposite end of the spectrum, this daylight shot gives us an example of where the M8 clearly loses out to the GS5. You lose all details in the tree, and there's quite a bit of noise in the sky on the M8. The GS5 however delivers a substantially better shot.

Lab Scene

The next set of shots use a light controlled lab setup. Here we are immune to natural variances of sunlight and can do some true apples to apples comparisons.


The GS4 and GS5 are pretty close to one another in our scaled/cropped shot. There are some differences in color handling and dynamic range between the two devices. I actually find that there's some loss in detail in the paintbrush on the GS5 compared to the GS4. I've seen a number of situations where aggressive noise reduction on the GS5 seems to mangle detail and deliver a very oil painting like effect, although that's an extreme that we're not seeing here.


The GS5 once again defaults to 1/15s at ISO 2000, compared to the same exposure time but ISO 1000 on the GS4. Here we really see what Samsung's sensor can do as the resulting image goes from unusable on the GS4 to passable on the GS5. The final image isn't particularly great by any means but it's at least usable. If you're looking for ultimate low light winners here there really are only two: the 5s and the M8.

HDR

The GS5 has a very fast and usable HDR mode. You can toggle the mode on directly from the default camera UI (tap the icon on the left side of the display) and you get effectively instant HDR captures:


The GS5's HDR captures do a good job of retaining detail in the shadows while bringing in detail in the highlights.

Introduction & Hardware Capture Latency
Comments Locked

296 Comments

View All Comments

  • Saltank - Wednesday, April 9, 2014 - link

    Not a single word about actually making phone calls? No call quality / HD Voice stuff? I was awestruck by how awesome my iPhone 5 handles regular non-HDVoice calls, and the GS3 was good, too, but my old HTC One was subpar.

    Also, how come camera comparisons don't take WP's in to account? No Lumia 1020/1520/930?
  • Lightstorm66 - Wednesday, April 9, 2014 - link

    I thought Anandt ech knew that the Samsung Browser is faster than chrome and achieves in the Galaxy S5 even better results than the iphone 5s in sunspider.

    Galaxy S5: 385,8 ms
    iphone 5s: 414,7 ms
  • ryanmt - Wednesday, April 9, 2014 - link

    The LG G2 is the unsung camera hero here. It outperforms it all. Why are only the HTC M8 and 5S called out for their good low light performance when the G2 is actually (subjectively) better?
  • echo9251 - Wednesday, April 9, 2014 - link

    There should be more talk about the lack of a 64MB option. I have a 64MB HTC One (M7) and enjoy never having to worry about running out of storage for apps, etc. Losing half my storage is a big disincentive to "upgrading" to a new phone.
  • Brian Z - Wednesday, April 9, 2014 - link

    Well they did include a micro SD card that supports up to 128gb.

    I am not going to make the case that having more storage considering the outrageous prices of the these devices. But at a point it gets a ridiculous. People complain loud OMG no external storage. No buy. Then they make 32gb device with expandable storage. People still complain
  • Streamlined - Thursday, April 17, 2014 - link

    Uh, because SD cards are dog slow compared to storage on the motherboard. SD CARDS SUCK and that is why HTC includes larger storage options. Just another reason the M8 is the best Android phone money can buy.
  • Myrandex - Wednesday, April 9, 2014 - link

    I'm disappointed no Nokia's showed up in the camera tests. I've love to see how this lined up with my Lumia 920, particularly in the low light tests. My wife's 1020 is a beast too.
  • Souka - Wednesday, April 9, 2014 - link

    Here's a another way to test durability and take apart a S5

    https://www.youtube.com/watch?v=newNF1UsOcw
  • dlang1234 - Wednesday, April 9, 2014 - link

    What I'm most impressed by, is how well the LG G2 is performing at these benchmarks against much newer phones. I have had my G2 for a while now, and it is an awesome phone.. so much so that these phones look more like side grades than upgrades even though, I mean it was released September 12, 2013 and now almost 6 months later, the epic increases of speed in mobile seems to be subsiding some.
  • chrcoluk - Wednesday, April 9, 2014 - link

    agreed.

    I own a S3 and a galaxy ace.

    The galaxy ace has cyanogen mod 7.2 installed on it.
    The S3 has touchwiz based on android 4.3

    In terms of hardware spec the S3 is many multiples more powerful than the ace.

    However many basic functions are much snappier on the ace, in particurly using it as a phone, bringing up the call log, scrolling the call log, making calls, answering calls, opening contacts, all these functions much faster on the ace. The ace also wakes up immediatly whilst the S3 has wake lag, the ace has much longer lasting battery even tho it has a weaker battery. However the ace does suck when it comes to using it for the internet/gaming most 3rd party apps as thats where its hw spec hits it, but its limitations are mostly down to its lack of ram. IT seems to always have more spare cpu cycles than the S£ as the S3 is bogged down by touchwiz.

    So why havent I got the S3 on AOSP. google edition etc? the problem is the contacts/dialer app on AOSP sucks really bad, its aweful. Especially with the default white background. Samsung have at least maintained a half decent UI design in their dialer/contacts the problem is its mega laggy. But sadly UI design wins over performance. CM7.2 has the best ever dialer/contacts I have seen on a android phone but new phones cannot use CM7.2.

    I have recently decided to start using the ace as my main phone (its easier to use out and about also due to its smaller size) and primarily use the S3 as a portable computing device. That way I can stick AOSP on the S3 and not worry about the crappy contacts app.

    Do samsung deliberatly make their interface laggy? not sure, its certianly possible tho as they want to give a people a reason to upgrade to the next phone every year.

    Also notice how every new software update increases the fotn size as well, to give people a reason to want the higher DPI. The relative font size looks equal on my ace vs the S3 even tho the S3 has a way higher resolution.

Log in

Don't have an account? Sign up now