Hi @lakeside - can you try reinstalling and uninstalling from our website? It sounds like f.lux did not uninstall properly. And also, there is an uninstaller fix in the new version.

Also, occasionally there is an issue because we try to load color profiles, and often they are not loaded at all by Windows 7. So if uninstalling doesn't help, you might also check the Color Management control panel to see what is in there.

I'm on a Mac, but I'd also like to see this. If I'm watching a movie or doing something in Photoshop on one screen, I still want to f.lux to be active for the other one.

@herf I also wanted to say, thank you for the quick response. I've had some support take days to respond to a problem. Top notch work.

We do have kind of a complicated state model that considers how long it's been disabled, but we can always do better.

Check out the notes here:

https://forum.justgetflux.com/topic/4653/tinted-screenshots-or-fullscreen-apps-and-games-missing-f-lux

No, because the only time it's using any system resources is when it's adjusting to a different color. So, the only way it can increase battery power usage is if you're frequently changing the color temperature (and/or color effects).

Once it's set to a color or color effect, it's no longer using any system resources and therefore not using any extra battery power. It's not actually using any system resources in order to maintain the color temperature or color effect.

Okay, it did happen again - so changing the earliest wake time wasn't it. After posting, I had also updated the driver to the newest one (390.77) available for Quadro.

If f.lux tries to disable for remote stuff, and that's causing issues here, shouldn't it be off rather than in stuck in Sunset mode? Other than this issue, it seems to work fine for me.

Usually you should just try downloading again, sometimes after clearing your internet cache.

@OutdoorLady still have a problem :(

With my zip code manually entered last night (EST vs. the CST on "Where am I" map near Wichita), the program activated 9 hours before my designated wake time. It appears to be linked to my computer's clock, not the map. To test that, I manually entered a zip code in California this a.m., watched the "Where am I" map change to that city in California and clicked OK. The program saved the California zip but the "Where am I" map changed to Omaha, Nebraska. What's really interesting on the opening window of the program, sunrise was calculated at PST, but the wake time was calculated EST (evidently, based on my computer's clock). Exited, rebooted, opened program again and changed back to my East Coast zip code... the WAI map showed my general neighborhood until I clicked OK... retained the zip and back to Omaha. The sunrise and sunset setting keeps alternating, so I can't tell whether it's EST or CST... the wake time was based on EST.

Knowing now that the program is linked to my computer's clock (not map), my work-around is to designate my wake time on what hour I want f.lux to activate at night (not actual wake time). E.g., if bedtime is 11 p.m., and no blue light after 8 p.m., I'd set my wake time to 5 a.m. Guessing these anomalies might affect the sliders in "Adjust day and night colors together" but I will let the f. lux software engineers determine that.

Yes. Turn off "backwards alarm clock" in the f.lux options.