Build 37.7 for El Capitan
@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?
@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.
@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.
@Katya-K. Can you post your machine type (and GPU type) also? thanks!
Sure, here's my iMac info.
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.
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 last edited by 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.
I have the following issue:
When using f.lux in the evening and shutting down my computer, the next morning when I reboot my Computer the warm color temperature is active and my screen is, like in the evening orange. Only after a few seconds I got a flicker and the right temperature (6500K) is set.
Can anybody help me?
Thanks in advance. :)
By the way ... I am running Mac OS X 10.11.6 (Macbook Pro Retina, 15', Mid 2014)/ 2.5 Ghz Intel Core i7 / 16 GB 1600 Mhz DDR3 / NVIDIA GeForce GT 750M 2048 M
I think this is expected to work this way (f.lux doesn't get time to run immediately on wake or reboot, so it takes us a minute to fix things from the previous night).
Do you sleep the machine or shutdown? Sleeping might fix things a little faster.
@agottschling please send your system info and if you're using automatic brightness or not?
I do have automatic brightness turned on.
snack last edited by
I'm also having this exact issue, except I am on 10.11.5. I ended up reverting to 36.6, and will keep using that version until this can be sorted out.
Can you please tell me how to disable or remove this terrible version of f.lux? I love the software but versions 37.2 and 37.3 are driving me INSANE, switching to sunset all through the day, whether I enable or disable the app. And now, having completely quit f.lux, and DELETED both the f.lux profile and then the Color LCD profile, it keeps switching my display to sunset mode. Despite not being enabled and there being no f.lux profile present for the monitor. What is going on??
Mid 2012 Retina MBP, OS X 10.11.6, running on Intel integrated graphics.
Can someone please set your daytime color temperature to 6400K and see if this helps?
@herf I've done that now - will let you know if it misbehaves. Time is 9:55am AEST here (and time zone is set based on location).
@MatthewK thanks - I have two workarounds in mind, and one is basically a less noticeable version of this - but I'm hoping this works.
No issues so far - it was switching every minute or so previously, so this is definitely better so far. Please let me know if I can provide any more feedback. Thanks for your responsive help! I teach neuroscience and the regulation of sleep and I always recommend this to my students.
@MatthewK great - keep us posted!
I posted this workaround at the top of the thread, and hopefully it will give some people a solution until we find a new trick to convince the OS to do what we ask. :)
All has been well across the day, and it's now shifting for sunset as it should. Thanks again.
Sorry I missed the tip at the top of the page, but for some reason that post doesn't always display when I visit this thread.