Earlier quoted context omitted.
That's not accurate. The human eye uses primarily green to detect resolution. Red and blue are used for color. I wish I could find it, but there was an online example, where someone took a picture, divided it into the three channels, then pixelated (mosaic) one channel at a time and recombined it. When he did green you saw it right away. With red it took some pixelation before you could see it. And with blue it took…
"Your eyes suck at blue": http://nfggames.com/games/ntsc/visual.shtm
Nexus One display and subpixel pattern
21–28 of 28 posts
Re: Nexus One display and subpixel pattern
#22I consumed this article with much enthusiasm. It was filled with information and still very easy to read. My immediate thought though: I wonder how much battery-time you would gain by making the device monochrome (black/green) when you just intend to use it to, say, call or perhaps even read something. Maybe a mode like this already exists in Android? I don't have a Nexus one, so... :) Heck, if it doesn't exist, then…
I still want to see some real numbers on energy consumption between a 100% white and 100% black (but still powered) AMOLED. As the first two letters stand for active matrix, there's still a control voltage going through each pixel when it's at RGB000, so the difference may not be as great as it's often made out to be.
Basically, it looks like AMOLED uses 3x the power of an LCD for an all-white screen, and about 1/10 the power of an LCD for an almost all-black screen. The LCD power stays the same, the AMOLED power varies by 20-30x.
Re: Nexus One display and subpixel pattern
#23I consumed this article with much enthusiasm. It was filled with information and still very easy to read. My immediate thought though: I wonder how much battery-time you would gain by making the device monochrome (black/green) when you just intend to use it to, say, call or perhaps even read something. Maybe a mode like this already exists in Android? I don't have a Nexus one, so... :) Heck, if it doesn't exist, then…
I still want to see some real numbers on energy consumption between a 100% white and 100% black (but still powered) AMOLED. As the first two letters stand for active matrix, there's still a control voltage going through each pixel when it's at RGB000, so the difference may not be as great as it's often made out to be.
When on but screen powered down (normal "waiting for a call" mode) I measured 2 ma, average, with occasional blips much higher (to 400 ma, measured with a Fluke 87 in MIN/MAX mode).
When powered "off" the phone takes 60 uA - I attribute this to keeping an internal RTC active, possibly keeping some sort of pseudo-static RAM active - but those are just guesses.
The battery voltage measured 4.1
I did these current measurements by wedging in two thin pieces of copper tape with an insulator in between, placed between the + battery terminal and the phone's + input.
The phone indicated "4 bars" and Edge service (not 3G) when I made these measurements.
Re: Nexus One display and subpixel pattern
#24800 horizontal pixels, but half of them can contain no red and the other half can contain no blue. Someone should cue the lawyers from the dithered LCD lawsuits. They will have a field day with this.
The trick this screen uses isn't even exactly new. JPG compression has done something very similar for ages (http://en.wikipedia.org/wiki/YCbCr and http://en.wikipedia.org/wiki/JPEG#JPEG_codec_example). Digital cameras also use that trick.
Re: Nexus One display and subpixel pattern
#25Earlier quoted context omitted.
I still want to see some real numbers on energy consumption between a 100% white and 100% black (but still powered) AMOLED. As the first two letters stand for active matrix, there's still a control voltage going through each pixel when it's at RGB000, so the difference may not be as great as it's often made out to be.
I put an ammeter on my Nexus One and measured 160 ma in black screen, and about 450 ma in white screen (with a "flashlight" application). When on but screen powered down (normal "waiting for a call" mode) I measured 2 ma, average, with occasional blips much higher (to 400 ma, measured with a Fluke 87 in MIN/MAX mode). When powered "off" the phone takes 60 uA - I attribute this to keeping an internal RTC active, possi…
Re: Nexus One display and subpixel pattern
#26I have heard that OLED screens are extremely difficult to read in daylight/direct sunlight, can anyone confirm or deny this? I think this would be a problem in on a phone in some places.
1) It's winter in New York City. Even outside there's not a lot of really bright sunlight.
2) The N1 has a feature (which I like) whereby, with a light sensor, it adjusts the brightness of the screen to compensate for ambient light automatically. Or: readable in light, not blinding at night.
Re: Nexus One display and subpixel pattern
#27Very interesting! This may explain the un-Googley-ness of the Android interface. I was racking my brain to figure out why the interface didn't have a blue, Gmail mobile /web app look and feel.
Re: Nexus One display and subpixel pattern
#28That's actually pretty interesting. I wonder if it was hard to do a subpixel rendering system for fonts (like ClearType)? I don't have a Nexus One so maybe the pixel density is high enough that they don't need to render fonts like that.
Actually, it does make it hard. To do subpixel smoothing correctly, you need to be able to keep the total amount of color the same -- so if you want to move a part of the glyph right one, you'd light up a red from the next pixel right and turn off blue on the last pixel in your line on the left. This becomes both much harder and less useful when not all pixels have all colors. But you are right on the other point --…
Since the display rotates, normal desktop sub-pixel rendering algorithms won't work anyway.