=====I have found a solution to the screen flickering=====
With chrome or opera, install the extension h264ify. This works for me to end the flickering. Not sure about Firefox. I had to register just for this post because it's so sad to see you guys flounder without a real solution.
Best,

Flux 4.33 beta, windows 7 x64. Can't get tray icon to front. "Control Panel\All Control Panel Items\Notification Area Icons" - show all icons is unchecked. When I set "Show icon and notifications" for flux, every time computer is restarted there is new entry for flux and tray icon is hidden.
I removed /nohide from executable but this brings flux window to front, not tray icon.

here the picture links since embedding didn't work:

https://www.dropbox.com/s/f1mu1azacaohefp/Screenshot 2017-02-21 23.30.39.png?dl=0

https://www.dropbox.com/s/x3cyex5yr50e0ry/Screenshot 2017-02-21 23.32.06.png?dl=0

Also I haven't noticed the problem when playing a video file with VLC or similar -- just from streaming.

My 5cents, disabling the auto brightness adjustment didn't help my issue.
What helped in my case is that I replaced the cable of the monitor.

lightning to D-SUB adapter with a D-SUB cable connected to the monitor -> constant screen refreshing waving/flickering effect (strangely only when flux enabled and color is warm)

HDMI -> DVI cable connected to the monitor - No flickering

I tried with 2 different monitors and I had the same issue / effect / resolution one LG and one Samsung. (Simply changing the D-SUB cable to another D-SUB didn't help, using another Lightning socket or adapter didn't help either)

@herf Thank youuuu!!

Had a crash this morning. Machine was up, I could SSH to it, but the screen was dark and flickering. Rebooted and checked the system.log. This may be a GPU failure issue, but I figured I would throw this in for those with similar errors and a LOT of Flux messages, but the more I dug the more it seemed like the issue was my GPU and not Flux.

Oct 25 08:04:05 max kernel[0]: IOVendorGLContext::ReportGPURestart Oct 25 11:49:04 max watchdogd[402]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive Oct 25 11:49:05 max watchdogd[402]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - failed to gather a spindump for (com.apple.WindowServer) Oct 25 11:05:10 max kernel[0]: NVDA(OpenGL): Channel timeout! Oct 25 11:05:35 max kernel[0]: NVDA(OpenGL): Channel timeout! Oct 25 11:06:21 --- last message repeated 1 time --- Oct 25 11:06:21 max kernel[0]: NVDA(OpenGL): Channel timeout! Oct 25 11:06:41 max kernel[0]: NVDA(OpenGL): Channel timeout! [... above repeated several times, then ... ] Oct 25 11:49:05 max Dock[360]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died Oct 25 11:49:05 max Upwork[341]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died Oct 25 11:49:05 max Flux[951]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died Oct 25 11:49:05 max Google Chrome[333]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died Oct 25 11:49:05 max Upwork[341]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port Oct 25 11:49:05 max Flux[951]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port Oct 25 11:49:05 max GPGSuite_Updater[1355]: Set a breakpoint at CGSLogError to catch errors as they are logged. Oct 25 11:49:05 max CalNCService[383]: Set a breakpoint at CGSLogError to catch errors as they are logged. Oct 25 11:49:05 max Upwork[341]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port Oct 25 11:49:05 max SystemUIServer[362]: HIToolbox: received notification of WindowServer event port death. [... later, Flux repeating every few seconds ...] Oct 25 11:51:04 max Flux[951]: Empty gamma size Oct 25 11:51:04 max Flux[951]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port

Early 2008 Mac Pro, 18GB RAM
OS X 10.11.6
NVIDIA GeForce 8800 GT 512 MB
F.lux 37.7

I've now updated my NVIDIA card with their drivers, maybe it is a GPU issue and not a Flux issue. Wait and see FTW!

Thanks for this feedback @David-J.-Bookbinder - appreciate you taking the time to spell it out for me

Sure @herf, here is what is shown:

Intel Corporation 27.20.100.9126: Intel(R) Iris(R) Xe Graphics (20201223) Generic PnP Monitor, 309 x 174mm, built 2019 Chromaticities: R=0.589844 0.349609 G=0.330078 0.554688 B=0.153320 0.119141 W=0.313477 0.329102 sRGB gamut: 63%, AdobeRGB gamut: 40% Unlimited gamma ramp=1, Internal ramp=0 Monitor 1 on Intel(R) Iris(R) Xe Graphics Has VCGT profile=0, Gamma Ramp works=1 Windows Build: 19043.1110

@ersanzop
how to resolve it.? . .

@CTS_AE please post f.lux options > driver info here. Usually f.lux uses its "fallback" mode due to a lack of driver support, such as with a USB adapter.

@Tungsten_smooth said:

@Gentz Now you can open the magnifier and invert the colors (ctrl alt i). I think it's the APU not understanding the color inversion part.

Yeah, something somewhere is definitely not allowing f.lux to work correctly. :/

Thank you Elhem! I will give that a shot.

@dsw2222 said in "Sorry, we only support 8 and 10-bit displays right now.":

#!/bin/bash
/usr/bin/xflux11 -r 0 $*

you can go further and do this the elegant debian way

create the script as /usr/local/bin/xflux and make it executable copy the xflux12 binary as /usr/local/bin/xflux12 and make it executable run this once: update-alternatives --install /usr/bin/xflux xflux /usr/local/bin/xflux 100

Sadly vers. 4.100 didn't do anything either ;-(

@TwoCables said in UWP f.lux:

Also, as you can see from the update page, it says "These pages are popping up too early for Windows App Store users. Sorry, we’re working on a fix!"

Sorry, I totally missed that! It's good information to know! I will probably just stick to Windows App in this case since developers know about the issue :-)

Thank you for the very quick reply!