Currently Being ModeratedFeb 17, 2013 1:16 PM (in response to John in Paris)
Thanks john in paris, that fix works great.
I can switch back and forth without any change to the screen.
Instead of gamma settings, I think it is more related to the white point calibration.
Currently Being ModeratedMar 1, 2013 9:52 AM (in response to ndada)
I just started having this happen after a clean install of ML on a new SSD. Here's (I think) how I fixed it. I was trying so many things, so I apologize if this doesn't exactly work for you. But it's definitely possible to get auto-graphics switching without the color-temp changing.
1. With no other programs open (after a fresh reboot is probably best), calibrate your monitor as you like it under System Prefs -> Display -> Color
2. Turn off auto-graphics switching under System Prefs -> Energy Saver
4. Navigate to /Library/ColorSync/Profiles/Displays and delete any profile that isn't your newly calibrated display profile. (In my case, two "Display" profiles were showing up)
6. Turn on auto-graphics switching under System Prefs - Energy Saver
I think that should do it. I realized that it was impossible to separately calibrate the discrete graphics card because whenever it opened up the calibration application, the computer would switch back to the integrated graphics card.
Currently Being ModeratedMar 5, 2013 7:45 PM (in response to mcgeeb)
This did not work for me. I had some problems along the way: system prefs->energy saver->autographics switching wouldn't stay OFF despite clicking the lock to prevent further changes--every reboot, it was back on.
After much frustration, and no progress, I couldn't see where I'd gone wrong, so I was trying again, and it wouldn't let me start a new calibration because the original/official display profile (sorry, didn't take a screenshot of the dialog box) was missing, and I had to drag profiles out of the trash and put them back.
So not sure why it didn't work, but getting a 'can't recalibrate due to missing original profile' message was disturbing. I did check with Apple again recently, and was told that this is a bug that is supposed to be fixed with 10.8.3.
Currently Being ModeratedMar 23, 2013 8:49 AM (in response to Donot Haveone)
I spoke too soon. Opening iPhoto still blues the screen. I thought it was ok because I was taking screenshots and comparing them, but D'oh!, screenshots don't work to show the color changes. Careful observation with a fixed desktop wallpaper made it clear.
Unbelievable that Apple still didn't get this right.
Please SEND FEEDBACK! so they know they need to keep trying to fix this.
Currently Being ModeratedMar 31, 2013 2:39 PM (in response to ndada)
I have a Macbook Pro 15 the late 2011 model and I am running 10.8.3 which I installed today. All of a sudden I have the same issues!!! I never had this problem before but now whenever my system switches to Discreet graphics card, the screen takes on a blue tint. I tried all the solutions mentioned and I have had no luck. I have sent feedback to Apple and I am hoping that this issue will be resolved soon.
Currently Being ModeratedMar 31, 2013 3:23 PM (in response to ndada)
People, it turns out that if you re-installt your current OSX version, the problem is fixed! I downloaded Mountain Lion 10.8.3 (which is my current version) from the Apple support here http://support.apple.com/kb/DL1640 and re-installed and the issue is gone.
Try it out and see if it works for you too.
Currently Being ModeratedApr 4, 2013 9:15 PM (in response to Spyridonas)
Reinstalled from the recovery partition, no blue for a few minutes, but after a restart, same problem as after installing 10.8.3: it's a temporary fix.
Unbelievable that they still haven't figured it out.
Currently Being ModeratedJun 15, 2013 1:27 AM (in response to Leschy)
The problem is that the blue-tint screen can come upon you usddenly - and then just disappear... I've found that it has nothing to do with system updates, etc. I first experienced it running early versions of Mountain Lion... and the never experienced the problem again.
For me, the solution was just to 'wait it out'. The problem appeared, lasted for a couple of weeks, and then disappeared... and I've never had it again.