f.lux f.lux forum
    • Recent
    • Popular
    • Register
    • Login

    Monitor comes back from standby without f.lux colors

    Windows v4
    8
    15
    797
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      nekminnit
      last edited by

      I am having the same issue as this user - https://forum.justgetflux.com/topic/3876/monitor-comes-back-from-standby-without-f-lux-colors-fixed-in-new-beta

      Restarting f.lux does not work. To fix it, I either have to restart my PC, or close f.lux, manually turn off my monitor's display, open f.lux while the display is off then turn it back on. This has been an issue since AMD Adrenalin 2020 drivers were released.

      1 Reply Last reply Reply Quote 0
      • herfH
        herf
        last edited by

        Can you post f.lux options > driver info so we can see the version?

        N 1 Reply Last reply Reply Quote 0
        • N
          nekminnit
          last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • N
            nekminnit @herf
            last edited by

            @herf

            Advanced Micro Devices, Inc. 26.20.15019.15019: Radeon (TM) RX 480 Graphics (20200226)

            Generic PnP Monitor, 597 x 336mm, built 2017
            Chromaticities:
            R=0.666016 0.330078
            G=0.309570 0.629883
            B=0.150391 0.040039
            W=0.313477 0.329102
            sRGB gamut: 99%, AdobeRGB gamut: 69%

            LG MP59G(DP), 480 x 270mm, built 2016
            Chromaticities:
            R=0.641602 0.334961
            G=0.291016 0.635742
            B=0.153320 0.042969
            W=0.313477 0.329102
            sRGB gamut: 100%, AdobeRGB gamut: 73%

            Monitor 1 on Radeon (TM) RX 480 Graphics: VCGT=0 gamma=1

            Windows Build: 18363.693

            1 Reply Last reply Reply Quote 0
            • U
              user_6541
              last edited by

              I have the same problem.

              Advanced Micro Devices, Inc. 26.20.15019.19000: Radeon RX 580 Series (20200228)

Generic PnP Monitor, 725 x 428mm, built 2019
Chromaticities: 
  R=0.672852 0.319336
  G=0.267578 0.672852
  B=0.151367 0.060547
  W=0.313477 0.329102
  sRGB gamut: 100%, AdobeRGB gamut: 82%

Winlimit=0, 1
Monitor 1 on Radeon RX 580 Series: VCGT=0 gamma=1

Windows Build: 18363.720
              1 Reply Last reply Reply Quote 1
              • N
                nekminnit
                last edited by

                I just discovered that the issue only occurs if the option to disable flux when certain applications are being used is enabled. Does this happen to anyone else?

                D 1 Reply Last reply Reply Quote 0
                • D
                  d8949t9t
                  last edited by

                  I'm having the same issue. I can't recreate @nekminnit's workaound because I only have one monitor.

                  Advanced Micro Devices, Inc. 26.20.15029.15007: Radeon RX 580 Series (20200317)
                  Citrix Systems Inc. 12.40.44.247: Citrix Indirect Display Adapter (20190123)

                  Generic PnP Monitor, 600 x 340mm, built 2018
                  Chromaticities:
                  R=0.652344 0.334961
                  G=0.304688 0.636719
                  B=0.148438 0.061523
                  W=0.313477 0.329102
                  sRGB gamut: 100%, AdobeRGB gamut: 71%

                  Monitor 1 on Radeon RX 580 Series: VCGT=0 gamma=1

                  Windows Build: 18362.720

                  1 Reply Last reply Reply Quote 0
                  • D
                    d8949t9t @nekminnit
                    last edited by

                    @nekminnit Not for me, it's happening on the regular global setting as well.

                    @herf Although I was just able to get it back on by switching my monitor to another input and switching back, all without closing f.lux.

                    1 Reply Last reply Reply Quote 0
                    • U
                      user_6541
                      last edited by

                      The new driver version (20.4.1) does not fix the issue either.

                      However I remembered that pressing "Win+Ctrl+Shift+B" restarts the graphics driver which fixes the problem for me, at least temporarily.

                      1 Reply Last reply Reply Quote 0
                      • R
                        RMCholewa
                        last edited by

                        I am getting the same behavior.

                        After resuming from screen power saving mode, I have to click on f.lux icon for it to apply the filters.

                        DisplayLink 8.2.1952.0: DisplayLink USB Device (20170522)
                        DisplayLink 8.2.1952.0: DisplayLink USB Device (20170522)
                        NVIDIA 26.21.14.4587: NVIDIA GeForce RTX 2060 (20200403)
                        Intel Corporation 26.20.100.7262: Intel(R) UHD Graphics 630 (20191011)

                        Monitor Genérico PnP, 885 x 498mm, built 2017
                        Chromaticities:
                        R=0.639648 0.330078
                        G=0.299805 0.599609
                        B=0.150391 0.059570
                        W=0.312500 0.329102
                        sRGB gamut: 100%, AdobeRGB gamut: 64%

                        LG W2243(Analog), 477 x 268mm, built 2009
                        Chromaticities:
                        R=0.634766 0.341797
                        G=0.291992 0.611328
                        B=0.147461 0.070313
                        W=0.313477 0.329102
                        sRGB gamut: 93%, AdobeRGB gamut: 64%

                        Monitor Genérico PnP, 344 x 194mm, built 2016
                        Chromaticities:
                        R=0.584961 0.363281
                        G=0.349609 0.579102
                        B=0.162109 0.142578
                        W=0.312500 0.328125
                        sRGB gamut: 63%, AdobeRGB gamut: 42%

                        Monitor Genérico PnP, 480 x 270mm, built 2016
                        Chromaticities:
                        R=0.644531 0.334961
                        G=0.304688 0.629883
                        B=0.148438 0.049805
                        W=0.313477 0.329102
                        sRGB gamut: 100%, AdobeRGB gamut: 70%

                        Monitor Genérico PnP, 677 x 290mm, built 2013
                        Chromaticities:
                        R=0.651367 0.332031
                        G=0.306641 0.630859
                        B=0.150391 0.059570
                        W=0.313477 0.329102
                        sRGB gamut: 100%, AdobeRGB gamut: 70%

                        Monitor 1 on Intel(R) UHD Graphics 630: VCGT=0 gamma=1
                        Monitor 2 on NVIDIA GeForce RTX 2060: VCGT=0 gamma=1
                        Monitor 3 on NVIDIA GeForce RTX 2060: VCGT=0 gamma=1
                        Monitor 4 on NVIDIA GeForce RTX 2060: VCGT=0 gamma=1
                        Monitor 5 on DisplayLink USB Device: VCGT=0 gamma=0

                        Windows Build: 18363.720

                        1 Reply Last reply Reply Quote 0
                        • N
                          nekminnit
                          last edited by

                          @nekminnit said in Monitor comes back from standby without f.lux colors:

                          I just discovered that the issue only occurs if the option to disable flux when certain applications are being used is enabled. Does this happen to anyone else?

                          Update: yeah recently I noticed that the issue still happens regardless of this ^. I have found two workarounds -

                          1. Win+Ctrl+Shift+B like user_6541 mentioned.
                          2. Closing the flux app, manually turning off my display then opening flux while the display is off. Ridiculous.

                          @RMCholewa -this solution does not work for me.

                          Still not sure if this is a flux bug or related to AMD 2020 drivers as it never occurred pre 2020 drivers. Any devs on here to reply?

                          A 1 Reply Last reply Reply Quote 0
                          • A
                            audiblenod @nekminnit
                            last edited by audiblenod

                            Having a similar issue. Doesn't always happen, but sometimes when the monitor wakes from being powered off, f.lux is stuck on its previous lighting setting regardless of the time, and clicking on the f.lux icon in the taskbar does nothing. Seems like it could be an AMD issue.

                            Advanced Micro Devices, Inc. 27.20.12029.1000: AMD Radeon RX 5700 (20200909)

                            Generic PnP Monitor, 597 x 336mm, built 2019
                            Chromaticities:
                            R=0.658203 0.333008
                            G=0.299805 0.626953
                            B=0.148438 0.056641
                            W=0.312500 0.328125
                            sRGB gamut: 100%, AdobeRGB gamut: 72%

                            Winlimit=0, 0
                            Monitor 1 on AMD Radeon RX 5700: VCGT=0 gamma=1

                            Windows Build: 19041.508

                            Should mention I'm also using the latest AMD drivers (20.9.1)

                            1 Reply Last reply Reply Quote 0
                            • N
                              ncsibra
                              last edited by

                              Same issue here, I work from home, having 2 PC and 2 monitors, using both monitors for both PCs.
                              I switch between the PC-s using the builtin input switcher on the monitors and sometimes after switching f.lux colors are missing, closing f.lux and restart does not help and I need to restart my PC to make it work again.

                              NVIDIA 26.21.14.3200: NVIDIA GeForce GTX 1050 (20190724)

Generic PnP Monitor, 597 x 336mm, built 2019
Chromaticities: 
  R=0.679688 0.307617
  G=0.263672 0.666016
  B=0.151367 0.043945
  W=0.313477 0.329102
  sRGB gamut: 101%, AdobeRGB gamut: 83%

Generic PnP Monitor, 597 x 336mm, built 2020
Chromaticities: 
  R=0.645508 0.333984
  G=0.301758 0.635742
  B=0.154297 0.056641
  W=0.312500 0.329102
  sRGB gamut: 100%, AdobeRGB gamut: 71%

Winlimit=0, 0
Monitor 1 on NVIDIA GeForce GTX 1050: VCGT=1 gamma=1
Monitor 2 on NVIDIA GeForce GTX 1050: VCGT=1 gamma=1

Windows Build: 19041.508
                              1 Reply Last reply Reply Quote 0
                              • herfH
                                herf
                                last edited by

                                @audiblenod - yes if this never resolves after wakeup, it is a driver issue. At our level, we try to restore the color settings on wakeup and every time you switch apps in Windows.

                                Hi @ncsibra - I do wonder what is going on there. You may be able to update this driver for better results (2019 is a little bit older than the latest).

                                1 Reply Last reply Reply Quote 0
                                • T
                                  Tetsuo6995
                                  last edited by

                                  I have a similar issue too. I put my computer (3 monitors) in sleep mode when I go to sleep at night and when I wake it up the f.lux colors are not active on all my screens. After a few seconds on the windows unlock screen the tinting comes back only on that screen. In summary:

                                  • Computer goes to sleep with f.lux active at night.
                                  • Just after waking up (f.lux shouldn't be active at this time) everything seem to go fine and the tint is not there on any screen.
                                  • After one or two seconds, f.lux seems to reactivate only on the screen displaying the windows unlock prompt.
                                  • F.lux remains that way and only restarting f.lux restores everything to normal.

                                  The issue started I would say about a month and a half ago after a Windows update if I recall correctly.

                                  Here is my Driver Info:

                                  NVIDIA 27.21.14.5655: NVIDIA GeForce RTX 2060 (20200924)

                                  Moniteur Plug-and-Play générique, 521 x 293mm, built 2013
                                  Chromaticities:
                                  R=0.640625 0.337891
                                  G=0.315430 0.628906
                                  B=0.159180 0.058594
                                  W=0.313477 0.329102
                                  sRGB gamut: 89%, AdobeRGB gamut: 63%

                                  Moniteur Plug-and-Play générique, 544 x 303mm, built 2016
                                  Chromaticities:
                                  R=0.639648 0.330078
                                  G=0.299805 0.599609
                                  B=0.150391 0.059570
                                  W=0.312500 0.329102
                                  sRGB gamut: 100%, AdobeRGB gamut: 64%

                                  Winlimit=0, 0
                                  Monitor 1 on NVIDIA GeForce RTX 2060: VCGT=1 gamma=1
                                  Monitor 2 on NVIDIA GeForce RTX 2060: VCGT=1 gamma=1
                                  Monitor 3 on NVIDIA GeForce RTX 2060: VCGT=1 gamma=1

                                  Windows Build: 19041.508

                                  1 Reply Last reply Reply Quote 0
                                  • First post
                                    Last post
                                  Copyright © 2014 NodeBB Forums | Contributors