Build 37.7 for El Capitan

mayhem

@herf iMac 27inch mid 2011. AMD Radeon HD 6970M 2048 MB

herf

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.

carlosfescobar

@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.

herf

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)

carlosfescobar

@herf Will try your suggestions. FYI i disabled automatic brightness when the problem started, so 37.3 never had it applied.

herf

@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/

mayhem

@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.

rbarraud

@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".

hamid914

@herf Thanks. It seems that the bug is solved in 37.3.

bbbbb

do we?? really dont know

pyris

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?

Katya K.

@pyris I have the same issue.

Guys, please fix this. Since I upgraded to 37.2, I constantly get the "orange screen" i.e. "Bedtime" during the day. Mostly before noon. I then quit f.lux and the screen gets reset to "daytime" mode, but after a while it switches itself to "Bedtime" again even though the f.lux app isn't started. When I start f.lux, then screen fixes itself again. I'm doing this on and on and it drives me nuts.

I went to System Preferences and disabled "Automatically adjust brightness", but that didn't help.

I'm using El Captian 10.11.6 Beta (15G26a). I was also using an El Capitan Beta with f.lux v36, but I had no problems then.

agottschling

@herf It appears with this new build that f.lux is deleting its color profile when it is daytime. Is this intended behavior or a bug?

herf

@agottschling yes 37.3 does this - it helps fix unplugged monitors. Previously (37.2) f.lux would select the "old" profile and leave the last "f.lux profile" there. It doesn't seem that 37.3 has helped much.

What's happening with the new 10.11.5 OS is that the system is remembering our profile even when we tell it to use the default one - in fact, unless we constantly tell it again and again to stop doing it (which is very expensive).

Regarding the v37 update: the previous build (v36.6) in some cases was constantly setting your profile because the OS told us it was always changing, which is about 100x as expensive as not doing so. Apple seems to have fixed most of these bugs so far, so we released 37 after a few weeks of testing, and it's less aggressive about fixing this case.

The remaining bugs seem to be related to Radeon chipsets and sometimes to automatic brightness. I'm trying to sort out which is which.

It's complicated because we don't have a machine in-house that's exhibiting the bug.

agottschling

@herf Ah. I understand now. I've got a MacBook Pro with the dual gpus (Radeon 6750m and Intel HD 3000). If I can be of any help testing, let me know.

herf

@Katya-K. Can you post your machine type (and GPU type) also? thanks!

Katya K.

@herf

Sure, here's my iMac info.

alt text

herf

Ok - the case that reliably fails for me on our Intel/NVIDIA machines is this one:

Enable automatic brightness
Disable it.
Don't reboot!
...

So if you are in this state, please reboot and don't change the automatic brightness setting after. AMD may be still another case.

Katya K.

Just wanted to say it seems the issue no longer occurs on my side. Here is what I remember I did:

Installed f.lux 37.2
Preferences -> Displays -> Color. I removed the f.lux display profile.
"Automatically adjust brightness" stays enabled.
Rebooted my iMac

I thought f.lux is not going to work after I removed the profile, however, it does seem to work. I'm using the Classic f.lux theme. I'll update my info should any changes occur.

agottschling

OK. I've found a replicatable scenario that will cause f.lux to get stuck, and whenever I leave Google Chrome open but minimized, it can "remember" the f.lux color profile such that when I maximize it, it will revert the display back to the old color. I'm running the latest stable build of chrome and flux 37.3.