[ElJimador]

Some resources about brightness,contrast,gamma etc.:
http://www.poynton.com/notes/brightness_and_contrast/
http://www.poynton.com/notes/colour_and_...mmaFAQ.htm
http://www.audioholics.com/tweaks/calibr...-xvycc-rgb
http://lareservediscomobile.free.fr/doc/...er-07.html

I believe that when this is fixed it should be removed from autostart.sh.
But, I dont believe that this will be fixed soon, as far I found out is that Intel is stalling here.... I really hope that I am wrong here.
It might that OE devs will find something to bring contrast directive to xrandr, but I am sure that they are experts, they know what are doing, they are doing a really good job and if there was sollution they would already implemented it.
Well see what will happen when haswell will be available in the next few weeks or so.

What I was told by some friend who is ingeneer in embedded systems is that manufacturers (like intel, nvidia, amd) actually sell "features" to computer manufacturers.
As feature I mean for example HW 3D acceleration methods and also access to settings like brightness, contrast... etc.
They make a lot of money for "feature access" and they cannot in the same time sell this and give it for free for open source.
You know what I mean by now.
But this is all unconfirmed and you have to take is only as roumor... I can be totaly false here.

Thanks for links! Really appreciate that. As for what Intel is doing with it's drivers I would know but to me it's an entirely different thing to market access to settings controls like brightness and contrast as a feature than to have them set wrong to begin with. I'm a layperson on this stuff but isn't the issue that with the current drivers the black and green levels are automatically set too high? If that's the case then it shouldn't be a "feature" for them to simply fix it, right?