One of the standout features on the SGS3 is the 4.8" HD SAMOLED display, which has an effective resolution of 1280x720. Like other Samsung devices, the name tells you almost everything you need to know: HD connotes 720p, S for Super means the stack is optically bonded with fewer air gaps (and thus fewer fresnel 4% back reflections), and the lack of Plus means it’s an RGBG PenTIle subpixel matrix.

First off, it’s clear to me that the SGS3 display is a substantial improvement on the Galaxy Nexus display, which was 4.65" diagonal and also 720p HD SAMOLED. The problems that I talked about in the Galaxy Nexus display are basically completely absent in the SGS3. There’s no longer any mura (luminance variance which looks like noise) or a weird purple cast in the greys, two things that are still present on the Galaxy Nexus. I suspect that moving to a larger display with the same resolution (and thus larger subpixels) might have helped mitigate some of the mura, and in addition this appears to be a completely new revision of the process with none of those problems.


Outdoor viewing angles are pretty darn good

I think it’s also worth discussing PenTile once more - specifically in the context of whether or not you can see the pixels. At this point, I don’t think we need to go over what it is in much detail, but that it uses two sets of two subpixel units to achieve higher effective resolution than an RGB stripe. There are two variants - RG, BW which I’ve seen in a few Motorola LCD displays (that are Samsung), and RG, BG, which is the more common variant that is in all the AMOLED panels without the “plus” suffix.

The implementations that I complained loudest about were really the Nexus One and Nexus S / Galaxy S, where AMOLED was still somewhat in its infancy, and RG, BG was both a way to increase subpixel lifetime before fading took place (according to Samsung), and achieve a higher logical resolution with fewer subpixels than an RGB stripe would require. For that reason, you can’t really just evaluate a display with some boolean is garbage / not garbage based on the presence of PenTile alone. In theory, if the logical two-pixel cell is itself smaller than human visual acuity, then you shouldn’t be able to see it, and seeing the pixels is what drove me crazy about those two phones.

I present the following graph, which has the angular subtense in arcminutes along the stripe (when a device is held portrait, this is the x direction) of one logical pixel. That is to say, two subpixels if we’re talking about an RGBG PenTIle display, or three for an RGB display. For reference, human visual acuity is most often cited as being around 1 arcminute for the human vision system corrected to 20/20, which isn’t perfect vision (20/15 or slightly better is). Anything below that should be indistinguishable at a distance of 12 inches (standard viewing distance).

Display Pixel Subtense

This is what I’m talking about when I say that in implementations such as the SGS3, even though PenTile is present, the logical pixel is still smaller than visual acuity, and the subpixels are half that. There’s still a case to be made for whether you can see fringing on black text on a white background to some extent, but personally I cannot see it.

So how is the display in other terms, such as brightness, color rendering, and viewing angles? For this I turned to the combination of my display colorimeter (still an i1D2), ColorHCFR, and Francois’s excellent Voodoo Screen Test Patterns.

When it comes to brightness, I found that oddly enough the T-Mobile and AT&T devices differed by a measurable and repeatable margin. Possibly these are from completely different batches, possibly there is some optimization done for the display brightness dynamic range to conserve battery - I’m not sure. Either way, it’s there, but the SGS3 is thankfully brighter than the Galaxy Nexus, though it still seems to be clamped to a fairly conservative number.

Brightness (White)

I measured blacks a few times and tried to see if I could get a reading on whether the SGS3 also has a slight DC bias (not fully off), but still couldn’t get anything. If it’s there, I haven’t noticed it yet.

In the Color HCFR testing, we can see that gamma looks very weird and nonlinear across the greys, going from around 2.4 down to 1.2, I have no idea what’s going on here. Color temp is thankfully a bit more controlled, at just under 7000K, and relatively flat.

I measured both devices after seeing that there was variance, and uploaded the color.chc files for both the AT&T and T-Mobile model for people with HCFR installed to check out. I’ve also made two galleries for the respective panels. I’ve heard really good things about the International SGS3 from Francois (supercurio), but haven’t measured it yet. I guess these initial numbers make me suspect that like SGS2 the USA variants have differences in the display rendering. I will say that over a range of brightnesses the SGS3 seems to have much less of the color shift compared to other AMOLEDs I’ve seen in the past.

Camera - Video Cellular, WiFi, GNSS, Sound
Comments Locked

107 Comments

View All Comments

  • Impulses - Wednesday, June 20, 2012 - link

    Did the CDMA variants get skipped because Anand usually reviews those (I think?) And he's been traveling or just luck of the draw? Is the review of the EVO LTE and other One variants still coming? Just curious really, I know sometimes battery life results vary wildly between GSM and CDMA versions of the same basic design, throw LTE in there and still-growing networks and it's something worth looking at.
  • alik - Wednesday, June 20, 2012 - link

    Visit http://samsunggalaxysiiicellphone.com/ to get best price and deals for Samsung Galaxy S III
  • Torrijos - Wednesday, June 20, 2012 - link

    In a recent article (HTC One X) you plotted a graph of the battery life (time) divided by the battery capacity (Watt-hours), it would be interesting to get it at each review or at least with reviews marking the arrival of a new version of an OS, in order to check whether their energy efficiency is going in the right direction.
  • falc0ne - Wednesday, June 20, 2012 - link

    Packed with all the latest technology but in a soap-bar shape. Galaxy SII looks much better.
    Someone said here shame doesn't have "pentaband support". You don't need that. What you need is that the phone you purchase to support the band of your operator. That's all. More than that, lately people usually purchase the phone straight from the operator
  • Zoomer - Sunday, June 24, 2012 - link

    That doesn't help if you switch operators often.
  • www.dasinu.ro - Wednesday, June 20, 2012 - link

    nice post...http://www.dasinu.ro
  • jjj - Wednesday, June 20, 2012 - link

    still a very poor selection for battery tests (just web and talk time,what are you testing dumbphones?) ,no storage perf tests,at this point i'm about to give up on hoping you guys can do better.
  • bmgoodman - Wednesday, June 20, 2012 - link

    Can you start doing some tests of Bluetooth, both for voice and music? With my Galaxy SII, I've almost quit using my car's integrated hands-free system. Five years in my car using a Sony Ericsson with the handsfree and I almost NEVER had a complaint. Now people are almost always asking me to call back later!
  • BabelHuber - Wednesday, June 20, 2012 - link

    I had the same problem regarding Bluetooth. My good old Nokia Symbian phones supported rSAP. Android, iOS and Windows Phone do not.

    That's why I bought the SGS2, it was the only Android phone supporting rSAP.

    In its wisdom, Samsung has removed the rSAP capability with ICS, though.

    Fortunately Android is an open system, so I could root it and install an rSAP app.

    This was a Sunday afternoon of work, though.

    The app is here: http://www.android-rsap.com/installation.html
  • Angry AtAndroid - Monday, June 25, 2012 - link

    Not Samsung removed it, but that big bully google. It is not supported by android.

    Complaints going on about this for YEARS. See the google code site.
    Issue 4402: rSAP / Sim access bluetooth profile
    1829 people starred this issue.

    http://code.google.com/p/android/issues/detail?can...

Log in

Don't have an account? Sign up now