GregAtkinson

I read sometime similar in Eizo documentation about letting the display warm up for color accuracy. Perhaps something else is the cause that has intermittent behavior.

You might be interested in this paper on OLED flicker from 2020 if you haven't read it already:
https://ledstrain.org/d/2652-eyestrain-from-oled-monitorstvs-but-not-oled-smartphones-a-theory/23

    photon78s Perhaps something else is the cause that has intermittent behavior.

    In my experience, some panels temporarily disable pixel inversion under certain conditions. For instance, for some panels, I can only see the pixel inversion when the image only takes up a small part of the screen. And once I display a large image, it isn't enough to make the image smaller - I have to make the image smaller, then maximize a different window (like I am somehow resetting the screen) and then bring up the smaller image and then I can see the pixel inversion. And it isn't just my eyes playing tricks on me because the photodetector is detecting the same thing.

    That's a pretty specific example and it might not apply to your situation, but it does indicate that pixel inversion can be intermittent.

      GregAtkinson

      This is not directly relevant I think to pixel inversion but this oled paper does make me suspect some limitation inherent in the engineering of screens that is causing these behaviors:

      Improving Flicker of Low-Refresh-Rate Driven Active-Matrix Organic Light-Emitting Diode Display
      https://ieeexplore.ieee.org/abstract/document/9852200

      We propose a novel driving method to suppress the brightness variation by applying a high voltage to the source and drain of the DTFT during the non-emitting time which is inserted periodically for dimming the organic light-emitting diode (OLED) display. Our experimental results show that the brightness variation can be reduced from 3.7 % to 1.4 % at the 63rd gray level by the proposed DTFT reset scheme.

      I don't understand this statement (flicker at low frequencies?):

      Especially, brightness stability could become a critical problem because human sensitivity to brightness is increased under lower refresh rate

        photon78s I don't understand this statement:

        Especially, brightness stability could become a critical problem because human sensitivity to brightness is increased under lower refresh rate

        Maybe they mean "...human sensitivity to brightness instability or variation"??? I've put the whole paragraph here for reference.

        However, in order to take advantages of LTPO, some technical challenges should be taken on. Modified pixel circuits and additional process steps are mandatory. Nevertheless, unknown problems may occur. Especially, brightness stability could become a critical problem because human sensitivity to brightness is increased under lower refresh rate [5], [6], [7], [8]. It has been reported that brightness variation is detected irrespective of charge loss in the storage capacitor even with LTPO [8]. The brightness instability under a low-refresh-rate may result from many unknown causes. Our measurement data show that electron trapping into the gate insulator of the driving TFT is one of the causes of the brightness instability. We propose a novel solution to this problem and report the effects of our solution under the low-refresh-rate driving condition.

        When I read articles like this I'm reminded that I'm an amateur kind of grasping at straws hoping to find something...

          GregAtkinson

          The frustrating thing is where are the "real pros" in the industry who have eyestrain issues? Anyways, my takeaway is that they are trying to lower power consumption (LTPO tech), and they are acknowledging the downside of "brightness instability" and trying to find a "solution" because the industry demands it. The rest is EE jargon.

            3 months later

            photon78s

            Sir, could you help me, and write, how to connect Fnirsi 1C15 to photodiode (which one?), to measure flickering…?

              14 days later
              dev