Not functional on MacOS Tahoe (Develeper Beta)`
-
@izyilq yes the only fix for now is to disable 'automatic brightness' in the displays control panel (which is kind of a bad fix)
-
thanks all for the patience - beta 5 fixes the issue and f.lux works with automatic brightness again
-
@herf Where can I find the download link for beta versions? The version that downloads from the main page is from several years ago. Thanks for the hard work to fix the issues!
-
@macuser usually those are announced here as a direct link. We did not roll out any of our Tahoe fixes as Apple fixed the bugs before Tahoe went live.
Are you having issues with a current release?
-
@herf Hi. I have the same problems on Mac OS Tahoe 26.3.1 MacBook M5 Pro. Automatic Brightness is off. True Tone also off. Flux works on my LG UltraFine 5K but not on my MacBook. :-( Any fix here soon? I love flux so much and don't want to miss it.
-
We are tracking this bug on m5 pro and max (with built-in displays) - you can read more here:
https://developer.apple.com/forums/thread/819331
We hope there will be a fix in upcoming macOS builds.
We believe that all M4-era MBPs and Neo are working. It is the "pro" M5s with a retina XDR that are not.
-
It works on my external monitor connected to the 16" MBP M5 Max but not the retina display. I might have found a hacky workaround for now -- first open flux and wait for it to adjust to desired color, then change the System Settings Displays color profile of the retina display to something else then change it back to your desired color profile.
-
@herf - Yes, I just picked up a new M5 MBP with an XDR Retina display and can verify that f.lux is not working. Seems like you guys are on top of it, though. So, I'm looking forward to the fix. Thank you. ~gabriel
-
@bobby It's working indeed! Thank you so much
-
I switched from an M1 Pro to an M5 Pro today (Mac OS Tahoe 26.5.1) and that's when I discovered F.lux no longer works. Is there any news on the upcoming fix? @herf
I've been using this software for over 10 years now and honestly can't do without it. In the meantime I've applied @bobby's workaround and it's doing the job for now.
Thank you for all your work on this.
