The other part of the story is Samsung’s mobile Digital Natural Image engine, or mDNIe, profile set on the SGS2. Numerous people have noticed that under Display -> Background Effect, lurks a page with a sample image and three presets - Dynamic, Standard, and Movie.

On previous Galaxy S devices there was a box in the camera app marked ‘outdoor viewing’ which increased brightness and contrast. I always wondered how that worked, and the answer is through mDNIe profiles. Inside /system/etc/ are a bunch of files prefixed with ‘mdnie_tune’ and then some more text, for example ‘mdnie_tune_camera_outdoor_mode’ and ‘mdnie_tune_standard_mode’. Of course, these are how the various settings are defined, and there are a bunch of them.

Inside are settings which control sharpening, saturation, and other things which are governed by mDNIe. For example, the mdnie_tune_ui_standard_mode file looks like this:

//start
0x0001,0x0000,  //
0x002c,0x0fff,  //DNR bypass 0x003C
0x002d,0x1900,  //DNR bypass 0x0a08
0x002e,0x0000,  //DNR bypass 0x1010
0x002f,0x0fff,  //DNR bypass 0x0400
0x003A,0x000d,  //HDTR DE_off CS : de on = d , de off = 9
0x003B,0x0001,  //DE SHARPNESS(0~1023)  off
0x003C,0x0000,  //NOISE LEVEL
0x003F,0x001e,  //CS GAIN 30
0x0042,0x0030,  //DE TH (MAX DIFF)
0x0028,0x0000,  //Register Mask
//end

Movie and Standard just differ in CS (Chroma Saturation) Gain (from 30 to 50), and dynamic boosts that to 300 along with another field whose purpose I’m not certain of. I’m told by Francois that Dynamic also changes white point through mDNIe by clamping and thus results in some dynamic range being lost. Unfortunately there’s no - everything off - mode with no sharpening or chroma gain that makes colors less oversaturated out of the box, though if you have root obviously you can change and experiment with these. Now that we’ve mentioned it, all measurements I’ve done on the SGS2 were in the Standard mode.

Now what about brightness across the spectrum of user-selected intensity percentages?

Bright SAMOLED

It’s redundant to show black brightness since each device measures 0 nits due to black pixels not emitting any light, so AMOLED remains super contrasty, even if brightness is about the same with SAMOLED+ as it was with SAMOLED. Thankfully the curve is nice and linear.

Display Brightness

On the big display graph though, SAMOLED+ still isn’t as bright as the competition, though again having infinite contrast does make the display subjectively awesome indoors.

Outdoors SAMOLED+ is about the same as the previous generation. It isn’t very easy to see the display contents outside in direct sunlight, but then again what phone does look as good outside as it does inside? SAMOLED+ as mentioned earlier still leverages the optical bonding benefits (fewer reflections) that SAMOLED brought, so if you were pleased with view-ability there expect much of the same with this update.

The only major issue outdoors is something else entirely. I noticed pretty quickly with the Infuse 4G and Droid Charge that outside in my climate’s environment (~100+F outdoor temps, lots of sunlight) that the phones would clamp brightness to about 75% to prevent overheating. This is in part a measure to protect the display panel and of course other internal components. I set out to find out whether SGS2 implements the same thermal restrictions, and it does.

I broke out my contactless IR thermometer and went outside into the midday sun on my patio and set the phone down. Overheating and clamping down the display brightness doesn’t take long in this climate, about 5–10 minutes will do it. At around 115F (~45C) surface display temperature you’ll get clamped to 75% maximum until temperature drops down. I actually subjectively don’t think SGS2 is as prone to overheating as the Charge or Infuse.

Some other people have reported SGS2 crashing or encountering a thermal shutoff after a certain point, so I braved the heat and stayed outside even longer using the device until it hit well over 140F (60C) and still no system shutdown or overheating happened. That’s not to say it isn’t possible, as the SGS2 clearly does have thermal monitoring, for example the following lines from dmesg suggest some thermal monitoring going on, though I definitely crossed these boundaries to no ill effects:

<6>[    0.047638] thr_low: 83, thr_high: 98  warn_low: 97 c warn_high 106
<6>[    0.047715] tq0_signal_handle_init
<6>[    0.047751] tmu_initialize: te_temp = 0x00000048, low 8bit = 72, 
high 24 bit = 0
<6>[    0.047765] Compensated Threshold: 0x7d
<6>[    0.098087] Cooling: 82c  THD_TEMP:0x80:  TRIG_LEV0: 0x89     
TRIG_LEV1: 0x99 TRIG_LEV2: 0xa0

Back to the display, next up are viewing angles, which the SGS2 thankfully preserves from the previous generation. I tossed the SGS2, SGS4G, and Optimus 2X in the lightbox and took pictures at various extreme angles. I realize the Sensation is a comparison point people are interested in, unfortunately that went back a while ago.

Viewing angles are awesome on all three - the SGS4G’s SAMOLED display (left), SGS2’s SAMOLED+ (middle), and Optimus 2X’s IPS display (right).

Another small thing about the SGS2’s SAMOLED+ is that I’ve noticed that high contrast images can be persistent for a few seconds. It isn’t burn-in, but a persistence that stays for a few seconds and can be very visible. For example, leaving the Android keyboard up (which is black, grey, and white) and dragging the shade down, a shadow of the keyboard remains visible until it fades after a few seconds. This persists even on other applications as well, and I can only hope doesn’t become something permanent if left up too long.

Wrapping up SAMOLED+ is difficult, because whether or not you like it over traditional LCD alternatives is ultimately a very subjective (and as I’ve learned in discussions, sensitive) matter. We’ve codified the differences between SAMOLED+ and previous generations, and other IPS displays, but really it’s impossible to communicate every subtle difference.

Personally, I prefer higher PPI IPS-LCD displays, though at 4.3“ SAMOLED+’s WVGA (800x480) isn’t a slouch, and the change from RGBG PenTile to an RGB stripe helps matters. Where WVGA starts to become a problem is at 4.5”. Scaling up area and increasing the diagonal size by 0.2“ doesn’t sound like a problem, but r^2 is a bitch, and at that size both the Android UI elements and subpixels look absurdly huge. Luckily, the international SGS2’s 4.3” is completely tolerable with WVGA.

MHL

Last but not least, the SGS2 supports HDMI out through USB MHL. For those that haven’t encountered the term before, MHL (Mobile High definition Link) is just a way of getting HDMI out through a low pin-count port alongside supplying power. So far, all MHL I’ve seen has worked over microUSB, but other interfaces possibly may support MHL in the future as well.

I had a Samsung MHL adapter laying around from a Samsung Infuse 4G, which has a microUSB port on the side for connecting to a charger, a full size HDMI port, and the microUSB connector which plugs into the host device. With all this connected, you can then get HDMI mirroring working, which does work on the SGS2.

I connected the SGS2 over HDMI up to an ASUS PA246Q and saw it negotiate a 1080i link and do HDMI mirroring flawlessly. Landscape is also supported, thankfully, and seems to work just like it should.

Super AMOLED+ Display Camera UI and Video Quality
Comments Locked

132 Comments

View All Comments

  • mbetter - Sunday, September 11, 2011 - link

    Nice looking phone but after my last Sprint Epic turned out to be such piece of crap, I'm not getting burned again.
  • jmcb - Sunday, September 11, 2011 - link

    Sadly....this happened to me from the old Win Mo days with the Omnia 1. I kept up with the GS 1 and now the GS2...and I give Samsung credit for whatever pros the phones have.

    But like with any phone manufacture...a bad experience can have a lasting effect. And for me it was something simple: build quality and reception. Both were bad with the Omnia 1 IMO. And ever since....I've been leery of Samsung phones.

    But...all n all the GS2 looks like more of a winner than the GS1.
  • warisz00r - Monday, September 12, 2011 - link

    Eh, your loss. (you and the poster you're replying to)
  • steven75 - Sunday, September 11, 2011 - link

    ...still doesn't have functioning GPS? Yikes!
  • WinProcs - Sunday, September 11, 2011 - link

    The GPS now works very well. It finds the satellites faster than any other smartphone I have tried including the iphone 4. Navigon is preloaded onto the phone (in Australia at least). The earlier version of Navigon had some problems on the Galaxy S. That appears to be fixed with the latest software version. The S2 has never had a problem with the GPS.

    I loaded Litening ROM and find that the phone is faster than original and battery life is much better too. I charge it every night but it is normally sitting at about 65-70% after an normal days use.

    I had an iphone and a Galaxy S before the S2. It is better than both of those.
  • ph00ny - Sunday, September 11, 2011 - link

    Are we reading the same article?

    "GPS works this time around, and works well. I took the SGS2 on a 7-hour long road trip with me and used its GPS continually with no issues."

    Every review since the release has made it a point to check this and mentioned it clearly since the SGS1 debacle.
  • Reikon - Monday, September 12, 2011 - link

    You missed the subject of the comment. He's talking about the original SGS, not the SGS2.
  • JMS3072 - Sunday, September 11, 2011 - link

    Does Hulu work using the Desktop user agent?
  • Astri - Sunday, September 11, 2011 - link

    Great review as always, but i was expecting to get more information about the famous color banding problem.
    Yes, the device is super etc etc, but its a pity to not be able to see everything on 24bit
  • supercurio - Sunday, September 11, 2011 - link

    Hi Astri.

    In some conditions yes on Galaxy S II you can perceive gradient banding or suboptimal dithering.
    The reason is not hardware at all, Super AMOLED+ controller and display work on higher bit-depth than 24bit, Gingerbread uses 32bit surfaces by default.

    You can see 3 situations with degraded gradients:
    - pre-dithered to 16bit or lower gradients or images
    - web browser (automatic 16bit dithering)
    - some games using 16bit without dithering instead of 32 on other phones.

    Every available mDNIe preset apply a sharpness filter between the GPU and the screen itself. Of course, it doesn't play well with the 3 type of content listed before.

    I reverse-engineered mDNIe controller registers to build a screen tuning app. Give a try to the dev snapshots: https://market.android.com/details?id=org.projectv... - root required.
    The current version is basic but I'll offer complete rendering configuration in the end.

    To avoid banding, use "Native" preset: as its named: no effect applied.

Log in

Don't have an account? Sign up now