Display - qHD RGBW PenTile

Probably the most significant change (other than Tegra 2) between the X and X2 is of course the display. As we mentioned before, that has been upgraded from a 4.3” FWVGA (854 x 480) IPS LCD to a qHD (960 x 540) LCD with the same diagonal size. What’s special about the X2’s screen, however, is that it comes with an RGBW PenTile subpixel rendering layout. 

We’ve talked about the RGBG PenTile subpixel structure before in the context of devices which came with AMOLED or Super AMOLED displays. The chief complaint back then was that black text on webpages and UI elements didn’t always look super sharp. RGBW is a different layout with different purpose, and dare I say different results. 


A 100% crop of the AT homepage on the Droid X2's RGBW display

As its name implies, RGBW PenTile includes a fourth, white, subpixel. The idea here is that light throughput for the panel can be vastly increased by simply adding a subpixel with no color filter. That increase in throughput then can be exploited to either get equivalent visual brightness with less backlight power, or you can crank things up all the way and get extreme brightness for the same backlight power. That translates to power savings most of the time, and extremely bright whites other times when you need it. It actually does make a lot of sense, especially when you consider things like browsing webpages which is still largely black text on a white background. 

Left: Droid X2, Right: Droid X

On webpages, RGBW actually looks pretty good, with black text being nice and sharp on a white background. This is one place where RGBG just never could do a perfect job, but RGBW does. I actually have no problem with RGBW for black text on white backgrounds. 

Droid X:

Droid X2:

The only place you can still dramatically tell that this is PenTile is either by looking at regions that are solid green, or red. At green in particular, you can see a bit of that grain from the subpixel structure - green is most visible because visual acuity peaks in the green. Red is also sometimes also shows a bit of that telltale grain, but nothing too dramatic. Human visual acuity isn’t very good for blue, so that looks pretty homogeneous.

In our tests, the X2 results definitely show how much having that white subpixel can help. 

Display Brightness

Display Brightness

Display Contrast

Motorola has had a pretty steady track record for putting great displays in their devices, going all the way back to the original Motorola Droid which included an IPS display. It’s nice to see that they haven’t compromised with the X2 either. 

We’ve also been measuring display brightness and white point at 25% brightness increments on displays lately, and the X2 is no exception from this treatment. Alongside the Motorola Droid X, the X2 looks substantially bluer. Looking at the white point on the X2 it’s easy to see where that comes from. At 7500K it’s closer to sanity than the 8500K for Super AMOLED Plus, but still not quite perfect. 

Moving onto the brightness (white and black) graph, we can see something finally reminiscent of a LCD, showing steady contrast as black and white both climb in a nice linear fashion as we ramp up brightness. The Droid X2 stays pretty contrasty, moreso than we originally measured the Droid X as being, but still not quite chart topping. 

Viewing angles on the X2 seem subjectively better than the original X. You can see colors on the X fade off and turn strange at the extreme vertical angles and a bit as well at horizontal extreme angles. I don’t remember the X looking this bad, it could be that the device I borrowed has a worse panel than the original X we were sampled last year.

Outdoors the X2 seems pretty readable, no doubt thanks to having that white subpixel and extremely high brightness. Even in the extremely bright, direct Arizona sunlight the X2 seemed a bit more readable than other devices from recent memory. 

Again the real nice thing about the X2 display is that qHD resolution which makes it able to both have a bit more text smoothing on webpages, and also just look better. I was especially thankful for that extra resolution when using things like remote desktop and maps from the X2, as a result, things on similarly sized WVGA displays look cartoonishly huge.

 

Nameless Motoblur: Continued Camera: Better Video and Stills
Comments Locked

72 Comments

View All Comments

  • Hrel - Thursday, July 7, 2011 - link

    I'd like to see them add an attachable/detachable slide out keyboard. Then they could also add a gamepad for actual hand held gaming. And they'd get to make money selling more accesories. It's a win for everyone! The thing is so thin as it is it can stand to gain some thickness without being an issue AT ALL.
  • snoozemode - Thursday, July 7, 2011 - link

    what do you mean, u cant see the grainy pattern in blue color? i see it just as good as in green, download the engadget app and put the icon on the homescreen, tons of black spots in it where the white subpixels have closed. RGBW sucks, period.
  • bjacobson - Thursday, July 7, 2011 - link

    all these high powered phones but scrolling up and down with your finger on a webpage is still laggy as hell. ???
  • bplewis24 - Friday, July 8, 2011 - link

    They're displaying flash images...what do you expect?
  • JayQ330 - Thursday, September 1, 2011 - link

    you have to download a gpu rendering browser, its the reason the iphone & samsung galaxy s2 & even the s are able to scroll & zoom in & out so smooth, when you see checker board effect you know its gpu rendered where as the regular android browsers are constantly resizing & adjusting words & images in realtime. they should take a hint from samsungs browser.
  • NeoteriX - Thursday, July 7, 2011 - link

    If I was looking on my HTC Evo 3D, what text would I be searching for in the dmesg output to identify the camera initialization line?
  • Brian Klug - Thursday, July 7, 2011 - link

    Things like this:

    <4>[ 14.364959] __s5k3h1gx_probe
    <6>[ 14.365051] s5k3h1gx_vreg_enable camera vreg on
    <6>[ 14.365173] sensor_vreg_on camera vreg on
    <6>[ 14.365722] sensor_power_enable("gp4", 2850) == 0
    <6>[ 14.366180] sensor_power_enable("gp6", 2850) == 0

    ...

    <6>[ 14.463897] s5k3h1gx_probe successed! rc = 0
    <6>[ 14.464141] ov8810 s->node 1
    <6>[ 14.464324] s5k3h1gx: s5k3h1gx_sensor_probe: switch clk
    <6>[ 14.464416] Doing clk switch (s5k3h1gx)
    <6>[ 14.484527] [Camera] gpio_request(30, "s5k3h1gx")

    Note the part with OV8810 which is an omnivision 8 MP 1/3.2" sensor. Possibly the Sensation uses some parts Samsung, some parts OV.
  • YoPete525 - Thursday, July 7, 2011 - link

    Great review as always, but I still find it ironic how far software optimization has to come on Android in general. I realize the X2 is rendering 26%(?) more pixels, but for every time it appears to process actions more quickly than the X, there is an example of it falling behind, like when pulling up the menu with the hardware button, and loading Basemark from the app drawer. Also, if you were to load up one of the more scrolling-conscientious launchers from the market, like LauncherPro or Go Launcher, the homescreens would scroll essentially at the device's refresh rate without stutter. Same story with Opera Mobile vs. the stock browser.
  • NeoteriX - Thursday, July 7, 2011 - link

    As I thought when I first looked at the dsmeg output; looks like it's no dice -- where the sensor ID should be is only "sp3d":

    <6>[73834.064016] [CAM]sp3d_vreg_enable camera vreg on
    <6>[73834.064139] [Camera]Shooter_sp3d_vreg_on

    ...

    <6>[73837.130660] [CAM]sp3d_spi_open_init: 1697
    <6>[73837.130691] [CAM]sp3d_vreg_enable camera vreg on
    <6>[73837.130691] [Camera]Shooter_sp3d_vreg_on
    <6>[73837.132155] [CAM]sp3d: sp3d_sensor_probe: switch clk
    <6>[73837.163436] [CAM]sp3d_sensor_setting type:0 config:0

    Thoughts?

    BTW, for what it's worth, the HTC Evo 4G uses the OV8810 omnivision for its camera:

    <6>[690609.827789] [CAM]ov8810_resume
  • wpwoodjr - Thursday, July 7, 2011 - link

    The effective available RAM memory on the DX2 is about 70-80mb less than the DX, you can see this by looking at Settings...Applications...Running Services and adding up the used and free memory. I was all set to buy a DX2 until I saw this. Even in the store I could easily make the Moto launcher close and be forced to redraw with only a few programs open. My DX already runs out of memory, I didn't want more problems. Perhaps this memory is taken up by the graphics card?

    It would be great if you added some multi-tasking tests to your reviews that would stress memory.

Log in

Don't have an account? Sign up now