hi chilldmaster_D . are you using the same display? What OS and model do you have?
Have you tried TimingSnoop? I'm wondering if it has anything to do with the missing EDID data or is it some sort of hardware reset on the nvidia chip (more likely :/ ) that's required to get it back to normal?
Have been looking on the net for ages in hope to at least find someone with the same problem.... At least this is some news.
I have a 2010 macbook pro 15" 2,4ghz i5, 4gb, with 330m 256mb nvidia gpu, running on 10.6.8 snow leopard
I have found that a lot of people are experiencing the same problem. I am using a different display, a Samsung t240 24" with 1920x1200 resolution.
I do not know if has something to do with EDID as that goes beyond my expertise, neither have i tried timingsnoop. it does seem likely that the nvidia chip resets.
Alot of people say the fix is to simply go to the colors tab at the system preferences > display. But for me that does nothing, neither does Detect Display.
The problem happens like this: i open my macbook from sleep mode, it awakes, i connect my external screen and then the colors on my external screen are desaturated/ washed out, the blacks are not as black etc.
I leave it plugged in and reboot, problem "solved", the colors on my external screen are natural and saturated. If i plug out my external screen and plug it back in at this point, the colors are back to being desaturated/washed out.
Again, this is not the gamma problem that's fixed by just opening the display preferences and resetting the colour profile.
This seems to be somehow related to the display's EDID and the video adapter (Nvidia) not resetting properly when first unplugged and then plugged back in. My support request with Apple is more than a year old in total now and replies have been trickling but all of them add little (if anything at all) to a fix.
My particular problem is finding these "a lot of" people who are experiencing this problem. Everyone I've seen so far talks about the gamma/colours problem, never about the brightness and reboot. So yours is the first instance of someone having exactly the same problem. Hopefully we can find more people? Do you know where I should be looking?
Another idea I've had is to possibly talk to the OSX86 community? If Apple are not interesting in issuing a fix for this, maybe someone else has done some work? After reviewing Apple's code (at least that part which is made public) I'm pretty convinced this is in Nvidia's territory, and that gives me very little hope..
I'm interested to know if this has been fixed on Lion at all..? Ideas?
I am having this same issue with my macbook pro 2010 i5 2.4 330m nvidia as well. I have tested the same exact cabling and display device with my iMac 2009 core 2 duo 3.06 radeon 4850 and my iMac's color looks perfectly fine. It is quite frustrating trying to find the cause even though it is a very specific use case that produces it.
still very interested to know if Mac OS X Lion (10.7) fixes this or not. All the research I could do points to Nvidia's graphics card not being managed optimally by the driver, but that driver doesn't seem to have been updated since 10.6.5... Apple's software is updated around it but the changes (available with the public sources for Darwin) aren't significant and/or in that area..
for the sake of "closure", Apple never fixed this.
I believe from their point of view it's an old, smallish, VGA display with a generic panel, no EDID to speak of, connected though an adapter, to an all digital port. Plus it's a Dell, not their best of friends. And the problem seems to be in NVidia's garden more than Apple's.
Snow Leopard 10.6.4 broke this. Mountain Lion 10.8.2 still had it. I tried everything with Apple's bug reporting system. Then I gave up. I got a 2412M with a display port interface.It worked greatt right out of the box.