Build 37.7 for El Capitan
-
I have three monitors hooked up to my iMac and since upgrading to 37.2 my iMac monitor does not return to day mode when the other two external monitors do.
-
I have installed 37.2 on My MacBook Pro (13-inch, Early 2011) running OS X 10.11.5. My laptop have Sudden Motion Sensor (SMS). When I move my laptop, it affects flux functionality. For example when flux is disabled at day, moving my laptop suddenly makes flux enable! and vice versa.
Is it a bug? Or is it a compatibility issue with older MacBooks? -
This post is deleted! -
@herf this worked for me!
-
@mayhem Great!
-
@herf :( installed yesterday but no change for me, just jumped back to sunset mode, quit flux and a few minutes later the profile activated again with the app closed. Reboot.
-
I may have spoken too soon.. the night time color was much faded from the previous version, but the day time colors were not in effect. Today, the night mode colors were still present on the main iMac monitor while the two external monitors are set correctly. Sorry for the false positive.
-
a bit more info, pressing the Daytime, Sunset and Bedtime buttons works perfectly with all three monitors.
-
Can you post the exact model Mac?
-
@herf iMac 27inch mid 2011. AMD Radeon HD 6970M 2048 MB
-
Questions:
- Does the bug still happen if you run "Calibrate..." on the display (System Prefs > Displays > Color)?
- Does the bug happen on wake from sleep, or at other times?
- Is the f.lux profile selected when the bug happens?
Based on earlier reports, I'm assuming this bug goes away if automatic brightness is turned off.
-
@herf my answers:
- haven't tried recalibration.
- on wake from sleep the morning after the last restart
- yes, the flux profile is selected, as soon as i select the imac profile (in my particular case) it resets to normal color... a few minutes after it changes color again until i reboot. Tried uninstalling flux with appzapper and removing the flux profile manually, still changes color after a few minutes until i reboot.
hope this helps.
-
My theory is that the automatic brightness feature in the OS is seeing f.lux as an "interesting" profile (not the default one), and it is holding onto it, beyond when it should.
So, when we reset the profile, it keeps using ours. "Calibrate" might provide an alternative 'interesting' profile to use instead.
There should be two workarounds as of the current build:
- Disable automatic brightness (the new system that's doing this, in 10.11)
- Disable f.lux's profile writer: https://justgetflux.com/news/2014/10/28/profile.html - this may cause some flashing when the system switches between video cards (AMD <-> Intel)
-
@herf Will try your suggestions. FYI i disabled automatic brightness when the problem started, so 37.3 never had it applied.
-
@carlosfescobar FWIW: on the PC we have seen some strange behavior due to AMD drivers (holding onto profiles), but I have not seen it previously on the Mac. Another option is to investigate which GPU is active at the time with https://gfx.io/
-
@herf said:
Questions:
1. Does the bug still happen if you run "Calibrate..." on the display (System Prefs > Displays > Color)? 2. Does the bug happen on wake from sleep, or at other times? 3. Is the f.lux profile selected when the bug happens?- Just re-calibrated.. I will find out.
- Wake from sleep and other times.
- No.
I also turned out automatic brightness.
-
@herf So when's an official fix coming please? It's driving me nuts too ... I suspect Chrome may also be a factor here. MBP Mid 2012 Retina 15".
-
@herf Thanks. It seems that the bug is solved in 37.3.
-
do we?? really dont know
-
Since I upgraded to Build 37.2 with El Capitan, I have been getting orange screen often during the daytime. Also as noted in another post, this does not necessarily go away if I quit f.lux. This is just using safari or email. Can anyone help?
