yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] mingkee:
I don't think I have to do it anymore. Moreover, I notice the audio is different after the kernel applied. Generally the sound has better depth and more realistic with 192kbps ogg vorbis (with winamp).
[Nexus S Android Development] jlevy73:
Check post #51 from this thread. AFAIK, that kernel has the latest inclusion of Super's color tweaks. I agree though, sounds don't seem as good compared to the version you are referring to.
[Nexus S Android Development] supercurio:
Yeah, big new for a fix that took me 10 minutes to write.

I really got fed up of the terrible colors while using my phone on 2.3.3 and wanted to make something quick.

As a result, a bad-ass dirty hack than I'm really not proud of, but you know, it works and looks good.

Anyway it shows the path to the real solution.

With this hack, I apply a constant negative offset on v0, which is kind of master gamma value for dark tones.

In the values calculated by the driver based on the gamma table v0 value is abnormally high on my phone for some reason, and this gamma point is what makes the colors look so dull.

The new kernel is at the usual URL, try it:

PS: the v0 offsets for Red Green and Blue are customizable and I'll soon publish an App update on market so you can play with it.

The annoying part is that it's just a dirty hack. It's not the solution. Also, I don't know how it behave on phones with different screens.

Tell me !! :)

http://dl.project-voodoo.org/nexus-s-kernels/Nexus-S-Voodoo-color-with-calibration-tools-latest.img
[Nexus S Android Development] jlevy73:
Installed the latest kernel and it does look a little better than the previous one. Most notably, whites seem sharper to me...the yellowish hue I had is gone
[Nexus S Android Development] irishrally:
The latest kernel looked marginally better than stock 2.3.3 on my screen. I was able to get a more satisfactory result with the sliders.
[Nexus S Android Development] mingkee:
I think the OP should add contrast with the next Voodoo release.

I found the contrast is lower with 2.3.3 than previous versions. I have been doing fine tuning to make it truly white without ANY tint, but I found I still can't fix the contrast (the winamp widget is still pale even I got the tint right).
[Nexus S Android Development] supercurio:
Did you tried the latest version ?
[Nexus S Android Development] jlevy73:
Yeah, and I agree with post above yours. I didn't bother putting the winamp on my desktop but when I did, it looked a bit to light
[Nexus S Android Development] supercurio:
I didn't had time to write a new control app version, but you you want to customize the visual contrast you can already:

https://github.com/project-voodoo/linux_samsung/commit/c4ffa32b8414954538ee164e7d23a9ccf94d8753

-30 : very high gamma/contrast

0 : standard 2.3.3
[Nexus S Android Development] mingkee:
Yes, it is. I downloaded and installed few hours ago (Voodoo app shows RGB multiplier).

Previous version (I stated it has perfect color on V1) has strange cellular problem, that I lose internet (but the signal doesn't have problem) connection after extended time of no signal.

update:

I decide to go back to Feb 26 release which has simpler (2 profiles and one of them is 100% perfect) Voodoo settings, but your mileage may vary.

The phone cellular radio has strange behavior with the "Feb 26" kernel, but after update the radio ROM to KB3, it looks OK, but I have to spend a couple more days to verify.

Once the experiment is done and successful, I will make a guide how to fix "low contrast" and yellow tint issue.
[Nexus S Android Development] ogdobber:
I'm getting an over active kernel with the latest built from linux_samsung....,

keep checking in gps every 5-10 seconds

**edit and other misc things, hard to keep up
[Nexus S Android Development] supercurio:
Kernel just updated !

Voodoo color: v0 offsets tuning and fix for sysfs green_v0_offset and blue_v0_offset read controls

Also I added Voodoo sound :)

Still a driver hack, color are not like they should be.

As usual, same URL:

http://dl.project-voodoo.org/nexus-s-kernels/Nexus-S-Voodoo-color-with-calibration-tools-latest.img
[Nexus S Android Development] jlevy73:
Awesome, I was missing voodoo sound on your the posted kernel. Will give this a go. Thanks!
[Nexus S Android Development] KnightMAREcrow:
Quick question, to actually flash the image I would use:

fastboot flash boot Nexus-S-Vodoo.img

Correct?

I have just been booting the image to be able to revert quickly without having to flash back another kernel

*I shortened the name of the image
[Nexus S Android Development] supercurio:
That's correct.

Personally as I use mainly my Nexus S as a dev phone i only boot kernels without flashing them and keep official Google one as default, but you can do as you prefer :)
[Nexus S Android Development] jlevy73:
This latest version feels like a step backwards. Whites are washed out for me, it looks almost grey instead of white. Thanks for everything, just reporting my feedback.
[Nexus S Android Development] supercurio:
Yes this one is not satisfying either.

I guess there is no good configuration with this approach, as expected!

Preparing an update for the control app so you can easily change the offsets manually ;)
[Nexus S Android Development] jlevy73:
Look forward to it.
[Nexus S Android Development] supercurio:
Alright, screen settings yet again updated (more like previous ones)

Finalizing the app udpate
[Nexus S Android Development] supercurio:
Pushed the control app updated on market !

Now with controls for v0 gamma offsets.

You'll see how it's interesting, but also what are the limits
[Nexus S Android Development] ogdobber:
seems that the bug that was in there earlier today is fixed;). whites are still too "off-white" for my taste but I can get a happy setting with the sliders...
[Nexus S Android Development] jlevy73:
What values did you find work good for your device in v0?

The 2.3.3 defaults look pretty good. White is finally white. All the other colors seem to be pretty accurate as well. Being able to manually offset the color hack is pretty cool.
[Nexus S Android Development] ogdobber:
sweetness:p This is going somewhre

I need to mess with it for a while...I will report back later
[Nexus S Android Development] irishrally:
I'm liking:

Profile: V1 (looks identical to original to me)

RGB Multiplier: Reset + blue moved to 260

V0: Punchy

I have no idea if these are accurate settings but they are the most pleasing to my eye on my screen (I think :) )

Thanks for this Super. I'm no developer but I do enjoying playing around with these things.

EDIT: The only problem with having all this choice is not being able to make up my mind what I like best. I think my eyes are starting to play tricks on me.
[Nexus S Android Development] jlevy73:
Profile: V1 (looks identical to original to me)

RGB Multiplier: Reset + blue moved to 260

That looks nice and bright :) Slightly blue to me but it does look good to my eye as well.
[Nexus S Android Development] supercurio:
Thanks guys, please continue to share your settings!

PS :

gamma tables / color profiles are only available for kernels versions < 2.3.3.

Those contains 16 points, the 2.3.3 gamma table is 91-points and I prevent loading incompatible gamma tables.

you can verify this in dmesg ;)
[Nexus S Android Development] irishrally:
Are there any combination of settings that would be harmful in any way to the screen?
[Nexus S Android Development] supercurio:
Yes, every RGB slider to the maximum can probably drive the screen over its specifications.

I don't have specific data about it, except that it has the ability to drain the battery very fast (faster than the changer charge it!) and get hot.
[Nexus S Android Development] ogdobber:
first run what i am liking...

sliders

red-213

green-196

blue-220

v0

red -9

green=-12

blue=-7
[Nexus S Android Development] ogdobber:
you need to wear welding goggles with the RGB's at max:eek:
[Nexus S Android Development] jlevy73:
I tried it, no welding goggles required but definitely a good pair of sunglasses :eek:
[Nexus S Android Development] terryhau:
If i install a kernel such as netarchy 1.2.7 with the latest voodoo colors, and don't use the voodoo control app to change any settings, will the color profile be the same as stock 2.3.3 ?
[Nexus S Android Development] jlevy73:
I've spent some time playing around with the color profiles and it still seems to me that white is still off a bit. Great progress though in such a short period of time.
[Nexus S Android Development] ajftl:
Superc r we going to have the microphone settings presets for the ns?
[Nexus S Android Development] littlesthobo:
Similar result here; I've rolled back to the earlier driver for now (the one in netarchy 1.2.5. Is that voodoo V.1 or V.0?) It gives me great colours without playing with any levels manually.

None of the voodoo drivers have had exact stock 2.3.3 colours. Try netarchy 1.2.5, the default voodoo colours for me are perfect.
[Nexus S Android Development] alexis_p3300:
i agree,netarchy's 1.2.5 have excellent colours as it
[Nexus S Android Development] supercurio:
I'm sorry I pushed so many updates and versions real fast it's confusing for users ;)
[Nexus S Android Development] jlevy73:
Are you kidding lol, the speed in which you have worked on this is simply astounding. I purchased your donate version since your "thanks" button seems to be broken :p

I'm sure I speak for all when I say thanks for everything. Now get back to work and push out some more update :D
[Nexus S Android Development] ajftl:
Lol. Harsh. Yes like microphone setting presets. Please. I have on my vibrant. It's the ****. Can finally hear my videos when recording at the club
[Nexus S Android Development] supercurio:
Measurements on my Nexus S screen running Google's kernel for 2.3.3 OTA.

Just discovering HCFR powers...

Measurements ran at 100% brightness.

Interpretation:

Gamma should be equal to 2.2 but on the whole brightness range it's far from it like eyes told us already.

Median value for Gamma is around 1.98 instead, and not constant.

Short story: The lower a pixel brightness is, the brighter it's rendered compared to how it should be (lower gamma value).

Of course this also confirm that the color change don't look dull because it's calibrated.

You'll see by yourself, calibrated colors are beautiful ;)
[Nexus S Android Development] Serious_Beans:
Will you be releasing the proper calibration settings?
[Nexus S Android Development] supercurio:
Yeah that's the whole purpose of this project :)

.. But also not only for my screen, I need moar data from you guys :D
[Nexus S Android Development] Serious_Beans:
How do I get the data you need to you?
[Nexus S Android Development] supercurio:
If you have a colorimeter too, you can run the same test with HCFR and simple patterns.

It will be useful to see if the color/gamma response is about the same or not.

Also by Discussing with Arve I learn more about how works and is supposed to work the "auto calibration" feature of the updated driver.

It may be a key to understand why it looks okay on some screen and not on others.
[Nexus S Android Development] Serious_Beans:
Ohh, that's quite expensive to calibrate my phones screen but if I get some extra cash I'll pick one up and send you the info. Thanks for all your work!
[Nexus S Android Development] supercurio:
Just published here stupid simple 0-100 greyscale patterns to take measurements from the standard web Browser.

In HCFR, uses the "DVD Manual" method and its all good.

http://dl.project-voodoo.org/screen-tests/calibration-patterns/

I will probably integrate patterns directly into Voodoo app later ;)

− also allowing more accuracy than 10 measurements, but it was just a quick start.
[Nexus S Android Development] supercurio:
Yes, however you can find Eye-ONE LT at about $130.

Those are already quite accurate, usable for lots of funky adjustement like TV and now also mobile screens

Best is of course a cheap upgrade for all your Computer's display !
[Nexus S Android Development] Serious_Beans:
So it would let me calibrate all my screen in my house? :O if that's the case then I'm definitely going to pick one up!
[Nexus S Android Development] supercurio:
Yes for PC & Mac & Linux it's fully automatic, for external displays however it's a manual process, IMO worth it.

Cannot live without calibrated displays now ^^ warning its addictive
[Nexus S Android Development] Serious_Beans:
Oh no, I get addicted to improving technology easily, thanks I think you just help me find my new addiction :)
[Nexus S Android Development] supercurio:
Hehe this one is an addition sometimes time consuming but cheap, as eventually you get much better results from the equipment you own already...

And often better results than equipment you would have bought as upgrade ;)
[Nexus S Android Development] scrizz:
hahahah excellent.

I'll probably pick one up soon! :D
[Nexus S Android Development] Serious_Beans:
Can't wait to calibrate my LG LED TV, I didn't think the colors could get better lol. Does it increase the contrast ratio (or is that a hardware limitation?). How exactly does calibration work? If it's a long explanation I'll just google it lol. So basically the colors on your Nexus S are "PERFECT"?
[Nexus S Android Development] irishrally:
I've paid $300 to get my plasma tv calibrated (Kuro) and it made an enormous improvement. You should have seen the equipment the guy brought with him. He applied an isf patch and hooked it up.
[Nexus S Android Development] supercurio:
Every hardware has its limitations (hardware or software)

But Nexus S / Galaxy S screen and controller limitations are almost inexistent. When hacking the driver, it allows as powerful tweaks as you can imagine.

- still not a real gamma LUT, but still - it's a different technology.

I'm just a rookie about external display calibration − discovering and sharing with you guys ;)

Loved this guide a cool follower sent me: http://www.curtpalme.com/forum/viewtopic.php?t=10457
[Nexus S Android Development] ogdobber:
ordered...
[Nexus S Android Development] terryhau:
Wow that looks awesome, and quite technical. Even though i don't understand the graphs at all, can't wait for the results.

Question, if you calibrate it at full brightness, will it still look right at lower brightness?

Using automatic brightness, it will be at 70 brightness most of the time.

Really wonder why google couldn't do this sort of hardware calibration.

Seems like they just took a guess.
[Nexus S Android Development] denis_y_s:
Sorry, a bit off topic, but for everyone who don't like new color settings with Google's 2.3.3 update please add your comment at http://www.google.com/support/forum/p/Google+Mobile/thread?tid=26fa0683976754c4&hl=en and star this thread http://code.google.com/p/android/issues/detail?id=15039 to help things move on the Google side. Thanks!
[Nexus S Android Development] shrivelfig:
Here's my data: (file deleted because I included the images in the post)

Display at 100%, stock 2.3.3 GRI54, DTP-94 sensor.

Images:
[Nexus S Android Development] supercurio:
Very interesting !

Please include the graphs / screen captures directly in the message so anyone can see them without downloading

I'll comment them then ;)
[Nexus S Android Development] supercurio:
Thank you again shrivelfig for these measurements, they are really useful.

I'll decrypt it for readers here − feel free to correct me if my explanations are inaccurate)

Notable values:

On your screen Delta E is really not that bad except for 30 IRE.

xy values don't suffer from much deviations.

Really, the new 2.3.3 color scheme & driver seems to work pretty well on your screen.

Delta E below 5 is considered good, so the values here can be considered good.

Here too, luminance value is not that far from the reference 2.2 gamma.

Confirmed by the Gamma graph:

There are 2 things very interesting in this graph in correlation with mine: which was:

http://supercurio.project-voodoo.org/color/Nexus-S-2.3.3-analysis/greyscale-gamma-measurements.png

- Curves have the exact same shape, despite the large differences between our screens, despite the fact we didn't used the same colorimeter hardware.

It means it's an issue with the color profile (gamma table + calculations)

- around and below 10% grey, things goes very bad on both of our measurements.

It's the main causes for washed out colors and blurry text.

However, average gamma on your screen is much closer to the expected 2.2 gamma, it confirms the large variation between screens and demonstrate why 2.3.3 OTA colors looks okay on some screens and terrible on others.

With the same measurement method, my screen gives an average of 1.98 gamma (brighten shadows, duller colors)

Delta E (pink) is not that bad but demonstrate profiles inconsistencies.

In perfect correlations with the RGB values.

Color temperature graph is not that bad, but can be improved also.

This exact graph means that colors are cooler (more blue component) when you raise the brightness or when the pixels displayed on screen are brighter.

Okay, no comment on this one.

New measurements like those will be really useful :)

I will also redo mine with more points in shadows because it's where most of the issue is.
[Nexus S Android Development] supercurio:
New batch of measurement, evaluating the effect of the v1 hack on my screen (incorrectly named v0 hack previously)

Standard - Luminance :

V1 hack Alt. settings:

WOW, right on 2.2 ! Amazing :)

− except a terrible deviation at 30% gray, told you it was interesting but wrong ;)

Same thing for the gamma graphs:

Standard 2.3.3:

Alt. settings v1 hack:

Pretty interesting for the rest.. It seems I can trust my eyes somehow :P

Not reassuring, however is the bad gamma value for 10% gray, it indicates nothing good for the future using the 2.3.3 screen init sequence.
[Nexus S Android Development] loganno:
who knows the values of "Gamma" and "Color multipliers" of 2.3.2?

What are the best values for our SAMOLED screen?

I use 1.2.6 Netarky cfs for CM7 nightly #12, 1.2.7 is black to boot.
[Nexus S Android Development] supercurio:
There are no multipliers in 2.3.2.

Gamma table (source for every color calculations) is different too.

Answer to the question behind you didn't ask;) no there is no simple way to get the 2.3.2 colors on a 2.3.3 kernel, except with those who kept the previous Super AMOLED driver code.

like mine here: http://xdaforums.com/showthread.php?t=876132 - but it may change.
[Nexus S Android Development] loganno:
Sorry I did not see the answer.

What are the best values for 2.3.3?

I use these that I have always found here on XDA:

Gamma set to :
Red = -26
Green = -30
Blue = -33

Colour Multipliers :
Red = 353834880
green = 3374617280
blue = 3568913600
[Nexus S Android Development] supercurio:
new measurements, running 2.3.2 display/color code this time:

I got my new colorimeter (cheap x-rite Eye-One display LT) and this time I can measure the color temperature again :)

100% brightness

The most interesting is this one:

near black, from 0 IRE to 10 IRE (0 to 25 RGB) is quite good, much better than what i get with 2.3.3 because it follows the curve.

RGB levels: too much blue too much green, really not enough red to fit D65 / 6500K.

Means my screen is really blue.

Confirmed by the temperature measured: more than 9000K!

And the classics: gamma and luminance. Far from perfect of course:

Conclusion

Despite its deficiencies, 2.3.2 color code looks much better (on my screen) than any based on 2.3.3 including with my current hacks because of the more accurate response in shadows.

EDIT: forgot the 2.3.3 shadows response curve for comparison, will come in a few minutes
[Nexus S Android Development] ogdobber:
i agree with you, the 2.3.2 colors look better on my screen as well...

My eye-one display LT on arrives wednesday...then I can give some useful info
[Nexus S Android Development] supercurio:
2.3.2 / 2.3.3 near black comparison:

2.3.2 with Voodoo v1 gamma table (okay)

2.3.3 (problem)

And what it means in terms of gamma

for 2.3.2 near black with Voodoo v1 gamma table (not so great, but not so terrible either)

for 2.3.3 near black (aoutch!)

Main visual problem is here!
[Nexus S Android Development] jlevy73:
I find if I set my colors as follows, my screen looks pretty much as it did on 2.3.2

Gamma set to :

Red = -26

Green = -30

Blue = -33

Colour Multipliers :

Red = 353834880

green = 3374617280

blue = 3568913600
[Nexus S Android Development] supercurio:
Thanks for sharing.

I see a lot of people use punchy-like values, and more red and blue!
[Nexus S Android Development] supercurio:
Corrected:

I get perfect D65 / 6500K with

Red = 3333712640
Green = 3057607680
Blue = 30703212800

V1 hack offset zeroed.
[Nexus S Android Development] irishrally:
delete ....
[Nexus S Android Development] supercurio:
it was at 100% brightness, but the color temperature shifts with luminance of pixels displayed: not good.
[Nexus S Android Development] supercurio:
Okay I have enough of calculations by the driver so far.

Now I'll stick to my previous plan a little bit and make a few manually calibrated settings and see if its useful.
[Nexus S Android Development] jlevy73:
So you have the v0 gamma offset hack color hack all set to 0?
[Nexus S Android Development] supercurio:
Yes, as the offsets affect the whole rendering
[Nexus S Android Development] jlevy73:
That looks good too :)
[Nexus S Android Development] loganno:
I have a problem when I go to change the profile, if I choose one or the other, nothing changes, they are equal. Why?
[Nexus S Android Development] ogdobber:
the profile are for the 2.3.2 drivers. use the sliders
[Nexus S Android Development] loganno:
So it is normal that now does not change anything or if I choose a profile or the other?

P.S. I gave you a Thanks
[Nexus S Android Development] loganno:
I understand you, thank you.

So it is normal that nothing changes in the profiles?

I have CyanogenMod 7 RC02 and Netarky 1.2.7 cfs.

If you want to use the profiles I to do?
[Nexus S Android Development] supercurio:
1/ its screen hardware controls, you cannot make screen captures of it

2/ as it says on displays, the current profiles are for versions < 2.3.3
[Nexus S Android Development] jlevy73:
Perhaps a stupid question but what does the rating 3/10, 5/10 mean? If it was explained previously my apologies.
[Nexus S Android Development] loganno:
Profiles then use them only with 2.3.2, right?

Here: http://xdaforums.com/showthread.php?t=949292 we have three kernel for CM7:

# the first in the colors of 2.3.2

# the second is?

# the third one has the colors of 2.3.3?

P.S. I gave you a Thanks
[Nexus S Android Development] ogdobber:
10/10 would be "perfect" colors;)
[Nexus S Android Development] ogdobber:
first kernel is for 2.3.2 cm7 rom (uses profiles)

second kernel is for 2.3.3 cm7 rom however it has the 2.3.2 color drivers (uses profiles)

third kernel is for 2.3.3 cm7 rom (uses RGB and v0(v1) sliders

note* in your previous post you stated you are running the netarchy kernel...if you try one of these kernels then follow the instructions above the link
[Nexus S Android Development] loganno:
Now I understand. One last question: if I edit with "sliders" colors, and then I put another kernel, even the default CyanogenMod, the colors back to normal?

TNXXXXXXXXXXXX :cool:
[Nexus S Android Development] ogdobber:
the "colors" are attached to the kernel. flash another kernel or rom and they will be overwritten (back to stock)
[Nexus S Android Development] loganno:
You are the best, very kind. :-)
[Nexus S Android Development] Si_NZ:
I have just read the calibration guide linked by supercurio, I have a few questions if anyone knows the answer to. Do you simply play around with red and blue sliders (keep green default as suggested by the guide?) and measure? Is there any other control I can play with? What controls are the RGBHighEnd and what controls RGBLowEnd?

I was going to calibrate my phone with my Spyder 2, but the comment about Spyder 2 being noticeably inaccurate has put me off a bit :(

I doubt posting my results will be useful at all. Should I try none-the-less?