yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] terryhau:
just a bit of extra info

http://www.engadget.com/2011/02/27/nexus-s-2-3-3-update-adjusts-screens-color-temperature-we-go-e/

Poll shows

2607 like the new colors.

727 do not like the new colors.
[Nexus S Android Development] supercurio:
Yes but I think the poll accuracy is affected by the article's photo,

The camera white balance used favor 2.3.3 color rendition.

On the color accuracy topic, the photo is not representative of what you see on the actual screen.

It allows however to calculate differently:

581 (14.9%) "looking good"

170 + 82 + 142 = 394 not happy with the update. "No, my screen looks terrible." + "No, mine's plagued with other bugs here." + "No, everything's gone wrong!"
[Nexus S Android Development] terryhau:
The poll asks people how they think it looks on their device, not in the picture.

But i agree, polls are inaccurate.

I haven't actually seen the 2.3.3 color profile on my own device because none of the custom kernels here use it. And i don't want to use a stock kernel (cm7 user).

When you update your kernel, will it use the new profile by default?
[Nexus S Android Development] supercurio:
Yeah, this poll cannot be accurate as the poll answers are for different questions, mixing color changes and general update modifications.

This poll is invalid by design ^^

You cannot add apples and oranges.

Until we manage to get nice colors from the new driver & gamma table, I'll publish mine with the old solution + the Voodoo color profile applied from the app.

But in this thread yes I'll publish a special kernel running the new code. But with the ability to customize it.

The goal is to let people try adjustments and share them :)
[Nexus S Android Development] mhaedo:
When the 2.3.3 update was released a few days ago, my immediate reaction was positive. I noticed how dramatically better the greys looked. Colors looked more accurate. I viewed the change as positive. I was quite vocal about how this was a fix, not a problem.

http://xdaforums.com/showpost.php?p=11632473&postcount=7

http://xdaforums.com/showpost.php?p=11631763&postcount=56

http://xdaforums.com/showpost.php?p=11630603&postcount=49

http://xdaforums.com/showpost.php?p=11629424&postcount=41

http://xdaforums.com/showpost.php?p=11628604&postcount=30

http://xdaforums.com/showpost.php?p=11618865&postcount=448

http://xdaforums.com/showpost.php?p=11618733&postcount=446

Unfortuntately, after nearly three full days of use I must take back every single one of the above posts. My screen looks terrible. The colors ARE more accurate. The greys ARE much better. However, overall my screen looks like it has jaundice. Everything listed in post #49 referenced above (ie. the dialer) does look dramatically better. However, my whites are terrible. They are not "yellow" per se, but they look like they have a slight yellow tinge like a subtle parchament effect. And honestly, I think since I knew this was an intended fix I convinced myself to like it. I figured the yellow was just my imagination because it was overly blue before, and yellow is the opposite of blue. If I look at my Facebook widget, GMail app, or Market app objectively three days later I can honestly say the yellow is real, and it is quite gross. When compared directly to my girlfriend's myTouch 4G the change is even more apparent. It's not that her whites are overly blue...mine really do have a subtle yellow tinge. And although stock and voodoo are both a bit oversaturated, the new 2.3.3 cover profile does appear undersaturated or "washed out."

Last night I reverted to voodoo color and WOW, it was a breath of fresh air. The colors are not as accurate. However, I don't care. The jaundice is gone, and my screen is vibrant again. If I must accept a tradeoff, I'll take the vibrant oversaturated colors over the sickly jaundice update colors. And this is coming from someone who initially viewed the change as overwhelmingly positive. I suppose subtle differences in sAMOLED manufacturing and each person's own perception of color make each person's preference different. Some people's screens may not have the yellow mine does. However after almost three days of trying to like the new profile, and then a VERY throrough comparison of stock 2.3.2, voodoo, and 2.3.3 ...I'll stick with voodoo. I just can't take the LED jaundice.

Thanks for your hard work supercurio. I'm really looking forward to the calibration tools.
[Nexus S Android Development] supercurio:
You know @mhaedo, if it a screen looks terrible (in some situations) it's always because the color rendition is not accurate.

Despite each screen physical/technical limitations.

People will tell you "it's washed out because it's calibrated" => wrong.

There is nothing more beautiful − objectively − than a accurately color calibrated screen.

I mean, with a calibrated screen you just forget it because everything is how it should be.

Because it becomes neutral, you don't see the screen anymore, only the images displayed on it.

Thanks for your report!
[Nexus S Android Development] mhaedo:
Well greys are definitely more accurate and look great. However I suppose you are right. As a whole, it is not accurate. I just purchased your voodoo donate market app to support the development. Thanks again.
[Nexus S Android Development] kenvan19:
I tend to disagree that people forget about a color calibrated screen. Actually, I know it to be completely false. Most best buy locations have a color calibrated TV display where they have two TVs side by side; one calibrated and one not. If you ask people which TV looks better 99 out of 100 people will tell you the overly blue saturated TV is clearly more bright and has deeper blacks. Those people are wrong. That is exactly what is going on here and its exactly why Samsung and others do this to displays. I'm all for giving people the choice when it comes to their screens but I'm also for not letting people perpetuate a falsehood; I've looked closely at my screen and my wife's, looked at every "horriblely" yellow tinted screen people have posted pictures of and I stand by my statement that there us nothing wrong. People are just used to horribly tuned screens.
[Nexus S Android Development] supercurio:
There is calibration and calibration.

Often, the name calibration is used for reddish screen tones and dull colors.

It should only describe a rendering scientifically accurate that fit the intended target color space.

Most times: sRGB color space.

However, I fully agree on the temperature. 6500K, which is the natural sRGB white point is fine compared to natural colors in exterior, but it's rarely the best choice for screens except for people working on imaging only.

I don't think either it's the absolute best choice for a mobile display.

- Cooler (more blue) temperature look better inside especially: more.. white :D

- We are used to blueish screens. As a consequence 65000 looks strange to most of us.
[Nexus S Android Development] Nutsonfire:
Polls don't mean a lot, if there are different screen versions, it's possible that the update works great on some screens and not on others.. It's possible that the people answering the Engadget poll have in majority devices with the same screen for which the update worked great.

The Google forums posts say exactly the opposite, 90%+ not happy and only a few happy.

In my opinion it is not possible to think that the colors on the screen of my phone look correct. The screen colors look like something you find on a cheap LCD or an old LCD screen with worn out back light that gives no more contrast.

Anyhow with Supercurio's kernel the issues is temporarily fixed.

Thanks for the hard work!
[Nexus S Android Development] supercurio:
You're welcome.

It's barely a choice, I would prefer selling my Nexus S than using it with 2.3.3 colors :p

Voodoo color profile V1 currently is app is far from perfect however. I gave it a 5 or 10 rating only.

− Began porting latest Voodoo color code and code documentation in 2.3.3
[Nexus S Android Development] MadFerIt2011:
Look, I'll agree that an overtly "blue" tinted screen is not good, both for colour accuracy and the life of your SAMOLED screen.

But, I do not for a minute believe the current 2.3.3 colour profile is anywhere close to "calibrated" or "accurate". It's not. Some are experiencing extreme yellow tint and washout. Also as supercurio's Voodoo colour profile has demonstrated the "purple tint" issue can be eliminated without introducing a yellow tint.

And I will repeat this over and over again until I can't type. NOT all SAMOLED screens are the same as supercurio pointed out. There are displays out there more negatively impacted by the 2.3.3 driver update.
[Nexus S Android Development] MadFerIt2011:
You rock! :D

I agree about selling the NS due to 2.3.3. I never intended to unlock my bootloader and mess with the kernel.. But here we are, and thankfully you did the amazing work of helping us out.

And I agree there's room to improve (and I will leave that to the master), there is still too much blue tint on my screen, even if the purple tint has been eliminated. I can imagine obtaining a 6500 temperature on this phone, and not the yellow tinted mess Google provided.
[Nexus S Android Development] ogdobber:
based on the downloads of my kernels...people running 2.3.3 prefer "2.3.2 w/voodoo colors" 2:1 over stock "2.3.3 colors"

thanks for your attention
[Nexus S Android Development] kenvan19:
You are entitled to your opinion but I will just say this: I have not seen a single picture of a screen that possesses this "yellow tint" that does not look normal to me. You're right though, SuperCurio fixed the purple tint without normalizing the colors, however his fix (this isn't meant as a slight to SuperCurio as I am a great believer in his work and his skill as a developer) didn't actually make the screen look natural. I still hold to my belief that what most people are claiming is a bug is really just a result of the fact that manufacturers have been using this type of over-blue saturation for years and that most people's eyes have become accustomed to it not to mention the fact that our eyes are easily tricked into seeing bright blue as brighter white.
[Nexus S Android Development] supercurio:
kenvan19, you need to see how a professionally calibrated screen look like ;)
[Nexus S Android Development] kenvan19:
I used to calibrate screens professionally. I calibrated all the screens in my home, my parents home and my wife's parents home. I have quite a lot of experience with the subject, actually, and I'd really appreciate not being talked down to about it.
[Nexus S Android Development] smelian:
Great news keep the good work man

I'm getting ready for Donation cheer
[Nexus S Android Development] supercurio:
Ah okay sorry. I'll be interested by your collaboration then with the upcoming release, especially if you still have calibration hardware !
[Nexus S Android Development] blackerwater:
@supercurio is it possible that we could get just the color fix without ext4 support? I'm not a big fan of converting my file system .

Sent from my Nexus S
[Nexus S Android Development] supercurio:
Without Ext4 support on Nexus S: what you ask is impossible ;)
[Nexus S Android Development] blackerwater:
Well not all the file system is ext4 right?

Sent from my Nexus S
[Nexus S Android Development] supercurio:
YAFFS and Ext4 natively. No conversion like Galaxy S lagfixes. Sorry: off topic.
[Nexus S Android Development] blackerwater:
Right Thanks :-)

Sent from my Nexus S
[Nexus S Android Development] supercurio:
Alright!

Uploaded the first calibration kernel based on 2.3.3 !

Nexus-S-Voodoo-color-with-calibration-tools-latest.img

What you can do with it:

Change the gamma table

adb pull /sys/class/misc/voodoo_color/gamma_table gamma_table.txt
edit gamma_table.txt
adb push gamma_table.txt /sys/class/misc/voodoo_color/gamma_table

Send direct brightness and gamma points commands to the panel

Write this as a text file:

185,184,252
22,11,31
118,110,79
174,174,161
181,185,166
194,197,185

First line: Red,Green,Blue gains for the hardware brightness levels

Lines 1-5: Red,Green,Blue gains for gamma points 0,1,2,3,4

Also named: v1 v19 v43 v87 v171 because it's the reference level they affect.

Then:

adb push points.txt /sys/class/misc/voodoo_color/apply_custom_brightness_gammas

Enjoy! And please share your results.

Notes:

you will also get plenty of details with dmesg output.

at boot and without manual customization, the color rendering is the exact same as 2.3.3

Upcoming.

- ability to switch from the previous (like Galaxy S) gamma initialization sequence.

- ability to tweak R G B multipliers.
[Nexus S Android Development] jlevy73:
Wow, that was quick. Will try it out now
[Nexus S Android Development] mingkee:
How can I install this .img file? Sorry for my ignorance.

Mine's contrast gets badly degraded. Winamp widget looks light gray more than original (dark gray).
[Nexus S Android Development] supercurio:
The current version is for developers only.

It will require a lot of work before having perfect color profiles, a bit less for "better" color profile.

The current kernel is a tool for developers to build such profiles.

Source pushed on github: https://github.com/project-voodoo/linux_samsung/commit/3b2e52a0b2777b38bf27f642c38d293b86038e43
[Nexus S Android Development] ogdobber:
aaaaaahhhhhhhh shhhhiii!!!!! went up to the mountains and only brought my chrome notebook. monday night when i get home is going to be a late one. Can't wait to try
[Nexus S Android Development] kenvan19:
How are the colors? I only have my Cr-48 until later so I won't be able to fastboot it until then.
[Nexus S Android Development] CB620:
I saw your kernel in another forum. How are they in comparison to netarchy?
[Nexus S Android Development] j.bruha:
If I could add my $.02 to the mix on the screen, I'd love to do so here.

I have gone through a total of 6 Nexus S's between me and my girlfriend and 2 of the ones we swapped out were due to the original yellow tinted screen that was reported when it came out. I finally settled on a Nexus S that had a nice and consistent screen with excellent whites and my girlfriend settled on one with only a minor yellow tint that didn't bother her in the least.

Last night, I manually updated my Nexus S to 2.3.3 after hearing about this color issue and reading through some info here about it (with a picture posted for testing purposes). I had my girlfriend's Nexus S right next to me and I performed the update in the same room with the same lighting conditions on the same brightness setting to be as accurate as possible when comparing the two.

After the update, it is immediately apparent that my screen looks terribly pale and washed out compared to how it looked prior to the update. When compared next to my girlfriend's Nexus S (with the slight yellow tint that I didn't like), my screen makes hers look absolutely beautiful.

I tested with the image posted in that thread, and while the poster is correct in that I could make out all the darker detail, I was able to just as well without the grey filter before the update and it looked much nicer.

As it has been posted here, Google was right about the blacks being represented as much darker than before, but the whites are definitely just wrong overall. It is noticeable on any screen that is using any colors other than a solid black, which is most of the time.

While I do like the very, very minor changes that were included in this update, I wish more than anything that I could revert back to 2.3.2 to get my beautiful screen back.
[Nexus S Android Development] irishrally:
When I pushed the points file with the numbers you listed I didn't see any change. Are those the default 2.3.3 settings?

Love the boot animation by the way ;)
[Nexus S Android Development] supercurio:
That's a very interesting and useful info.

It means almost every Nexus S screen is different, and can have tint in unexpected ways.

Looks like the update works better with his screen than yours.

Sucks for you, but great for me (for testing ! ;))

The actual kernel here don't change colors.

But it allow you to change colors totally via sysfs controls.
[Nexus S Android Development] KnightMAREcrow:
What is the boot animation and is this off the voodoo-image that was in the original post?
[Nexus S Android Development] supercurio:
There is no special boot animation.. however, there is a new kernel version !

Changes:

Voodoo color: add RGB multipliers via sysfs controls

Voodoo color: save RGB mulplier original calculated values and make them readable via sysfs controls

Download:

http://dl.project-voodoo.org/nexus-s-kernels/Nexus-S-Voodoo-color-with-calibration-tools-latest.img

WARNING

It is possible than displaying very high brightness images with sliders at maximum can damage your screen by

- over-heating

- rapid screen burn-in

It may also stress a lot of your battery

I don't have exact screen specs but I'm pretty sure it can be driven off-specs by this brand new developer tool.
[Nexus S Android Development] irishrally:
Thanks for your response. I'll try the new one
[Nexus S Android Development] jlevy73:
Everything looks good, except the white still freaks me out :) It's got a yellowish hue to me which just throws off my eye. Maybe this is how white is supposed to look but my brain keeps rejecting it.
[Nexus S Android Development] jlevy73:
All the colors look great except for white. White has this yellow hue to it which seems off. Then again, I'm no expert color calibrator just going by what my eye/brain tells me.
[Nexus S Android Development] matt_stang:
Not only that, but every pair of eyes is different too, making for an even more difficult job of calibration. I like the route that you are taking with user configurable calibration.
[Nexus S Android Development] kenvan19:
Mind taking a picture of the screen so I can see?
[Nexus S Android Development] supercurio:
Camera pictures don't help.
[Nexus S Android Development] jlevy73:
Not at all. Will post it after I grab a bit to eat.
[Nexus S Android Development] jlevy73:
I was thinking of doing a screen cap???
[Nexus S Android Development] supercurio:
Lol every screen cap will give you the same resulting image. Color controls are 100% hardware ;)
[Nexus S Android Development] kenvan19:
Why wouldn't camera pictures help? It shows the display and not the screen so I can see the color the screen is display and not what the color the OS is putting out. I mean, it won't be perfect but it gives me a baseline to look at until I can actually flash the kernel.
[Nexus S Android Development] jlevy73:
Good point, time for dinner :)
[Nexus S Android Development] supercurio:
With automatic exposure and auto white balance, basically every photo of the screen will look the same. or wrong.

Also, as the S-AMOLED contrast ratio surpasses by far dynamic range of most digicam sensors and computer screen you will see the picture on. Well.. in the end photos are useless and most times misleading :)
[Nexus S Android Development] matt_stang:
Yes you could take a screen cap with a Nexus One or say an HTC Incredible and get the exact same image. The screen cap comes from Android, not from the actual screen.

Pretty much the only way for someone else to see the colors on your screen is in person. Yet another reason why getting the colors right on these screens is such a difficult task
[Nexus S Android Development] supercurio:
http://dl.project-voodoo.org/nexus-s-kernels/Nexus-S-Voodoo-color-with-calibration-tools-latest.img

Still same URL, but kernel updated.

Added:

Voodoo color: added control to switch of panel initialization sequence between Samsung and Google 2.2.3 ones, allowing to revert live commit 921bfc57db1849d30481b9d8ac98ab1e42feb34c

How to use it:

adb shell echo 0 > /sys/class/misc/voodoo_color/panel_config_sequence
adb shell echo 1 > /sys/class/misc/voodoo_color/panel_config_sequence

the mode 1 is Samsung mode (same as in kernel before 2.2.3). It allow to load directly settings with apply_custom_brightness_gammas issued from Samsung Galaxy S compatible settings without over-contrast and shadows clipping.

Like that:

http://xdaforums.com/showthread.php?p=11695182#post11695182

You can test with this darn fine profile tuned manually, adb pushed to /sys/class/misc/voodoo_color/apply_custom_brightness_gammas

185,184,252
22,11,31
118,110,79
174,174,161
181,185,166
194,197,185
[Nexus S Android Development] mhaedo:
supercurio, very impressive work in an amazingly short period of time. My phone is now usable with 2.3.3 display drivers! Just a touch less red and more blue on the sliders. It is not overly blue, and the yellow tinge is completely gone. I'll edit the post with numbers in a bit...I'm still tweaking things. The "Screen Test" app from the market is helpful for manual calibration.

edit:

Screen color multiplier values that work for my Nexus S (and might not work for yours, since both our displays and color perception may vary slightly):

R:208

G:214

B:240
[Nexus S Android Development] mingkee:
The white balance function of the camera screws up the thing even under daylight (not soft white), soft white only makes thing worse and make everything on camera blue or purple.
[Nexus S Android Development] kenvan19:
Fair enough, I do not know much about photography so I just assumed it would be a good representation and I assumed incorrectly.
[Nexus S Android Development] j.bruha:
So if I'm understanding these updates correctly, it looks like we now have a way to tweak the screen, and we also have a set of display settings direct from the Galaxy S line to use that are unmodified. Please correct me if I'm wrong.

So I guess the next step would be to pull the settings from the 2.3.2 drivers and use those values to accurately match what our screens looked like prior to the update (or we can just guess and manually adjust it as best we can). Is this possible?
[Nexus S Android Development] jlevy73:
The numbers that look good to me are:

Red: 215

Green: 242

Blue: 213
[Nexus S Android Development] xmRipper:
2.3.3 is perfect on my screen. Purple tint has gone at all, better than the Voodoo Color patch. Absolutely great.
[Nexus S Android Development] supercurio:
How to make reports with the current version.

Hey hey :)

I missed time to write some info yesterday, so here am I back!

I will continue to provide new analysis tools (especially, details about color profile calculations) but so far what's available is quite powerful already.

what's most useful:

adb shell cat /sys/class/misc/voodoo_color/red_multiplier
adb shell cat /sys/class/misc/voodoo_color/red_multiplier_original
adb shell cat /sys/class/misc/voodoo_color/green_multiplier
adb shell cat /sys/class/misc/voodoo_color/green_multiplier_original
adb shell cat /sys/class/misc/voodoo_color/blue_multiplier
adb shell cat /sys/class/misc/voodoo_color/blue_multiplier_original

It will allow us to see if the original multipliers, which are based on static values predefined in the kernel, but also on self-calibration data read from the screen, which is one of the new things in 2.3.3.

the non _original values are what you can customize with the sliders ;)

PS: _original values are used in the app when you push the [RESET] button

− preparing an application update that should ease the process a little ;)
[Nexus S Android Development] supercurio:
Thanks for the report, I'm interested by your multiplier values ;) and also later some more infos you can get with this kernel.

Thanks!
[Nexus S Android Development] irishrally:
I know this kernel is just for color development but would you mind adding in voodoo sound so for those of us that want to use 2.3.3 color drivers and want better color accuracy this could be the perfect daily kernel. Thanks.
[Nexus S Android Development] mingkee:
I installed this kernel

http://xdaforums.com/showthread.php?t=876132

as well as installed Voodoo Control Panel and use the color profiles (profile v1 note: 5/10). Now the greyscale is totally perfect, no ANY color distortion or tint!
[Nexus S Android Development] irishrally:
I believe that kernel uses the old 2.3.2 drivers. You should try the kernel on the last page and manually adjust the color settings with the sliders in the control app to get even better color accuracy.