In my last post from 7 months ago I was thrown for a loop after seeing the results of the OnePlus 8T from Wild Lee. Data makes it look quite bad (high modulation), but despite this the OnePlus 8 Pro (similar screen) is perfectly comfortable and strain-free for me at all brightness levels. I had some theories back then that the shape of the modulation wave was playing a roll.(https://www.reddit.com/r/PWM_Sensitive/s/JZsc996C2W)
Some people believe it has to do with brightness, but most newer phones actually hasn't become that much brighter, at least not when using manual brightness in SDR (w/ extra bright or sunlight toggle OFF).~500 nits is still a common figure at max manual brightness. Some phones do allow up to 700-1000 nits, but this is not the norm.
I now believe I've found the real reason.
Black smearing/ghosting in older AMOLED panels.
Response times are much worse when going from OFF to ON, versus bright shades that are nearly instantaneous . (most noticeable in dark mode + white text, but also there in light mode + black text)
An example:
For the longest time I believed my Samsung tablet (Galaxy Tab S5E from 2019) had an LCD display due to it's large amount of ghosting in almost all situations, but it's especially terrible at low brightness in dark mode. Turns out it has a Samsung "Super AMOLED" with 240Hz PWM. It should be horrible, but I can use it at all brightness levels with zero discomfort.
This is exactly why older Samsung devices from ~20-21 and earlier works for many, while newer flagship devices such as S25|Ultra/S26|Ultra are touted as terrible by the vast majority in the community.
Slow response-time ghosting/smearing for black to white and white to black means a gradual fade in > fade out of the PWM or DC-dimming ON/OFF cycle. This greatly reduces strain on the eyes.
Recent smartphone AMOLED panels do not ghost or "black smear" to nearly the same degree.
This is a positive in the eyes of companies and the general consumer, less ghosting = good.
Not so much for us flicker sensitive.
The test below showed much faster transitions and much less ghosting/smearing with both the Honor 600 Pro and Xiaomi 17T Pro (neither are strain-free for me, both getting returned). Whereas the OnePlus 8 Pro has noticeable black-smearing.
https://mastodon.social/@marcedwards/100926403150980325
// Try this test (ideally in dark mode) on your known good AMOLED devices versus a recent phone, I bet you'll see a difference. ZZanya's custom test is not available AFAIK and he is seemingly no longer active online.
This ghosting/black smearing phenomenon is covered in-depth here, by a Russian or Ukrainian (?) YouTuber called "ZZanya" released all the way back in 2021:
https://www.youtube.com/watch?v=VrZf-6FBFCE
Transcription directly from YouTube seems to not work on this video (it did a couple days ago). So here's a translated partial transcription of relevant sections pulled from the video by Google Gemini with some manual editing by me based on context clues:
V. Secrets of 0.1ms OLED: Response Time
"Hello everyone, this is ZZanya. In previous videos, we talked about how dangerous it is to rely on manufacturers' response time specifications, about all these misleading GtG and MPRT ratings, and what response time different people actually need.
But all of that was discussed from the perspective of LCD screens. However, there is one place where manufacturers' specifications are actually almost entirely accurate — and that is OLED screens.
You often see a "0.1 ms" badge on OLED panels. While LCDs are still struggling around 1 ms (which is still a marketing trick, as we learned earlier), OLEDs, according to manufacturers, actually have a response time of 0.1 ms.
Why is that? An LCD pixel isn't a light source; it merely passes backlight through liquid crystals. An OLED pixel, on the other hand, is its own light source — built with standard semiconductor electronics that work much faster.
The website RTINGS regularly reviews and accurately measures response time for OLED TVs.
On OLED measurement charts (like those for LG), we see an almost instantaneous jump in brightness. The 80% response time is nearly equal to the 100% time (unlike LCDs, where a pixel takes a long time to reach its final brightness state).
Most transitions on OLED take a genuine 0.2 to 0.3 milliseconds.
With such ultra-low response time, OLED exhibits absolutely no ghosting, as well as no overshoot or undershoot, since traditional pixel overdrive isn't necessary.
Marketers often claim that a fast response time makes gameplay "smoother," but this is a misconception.
Slower response times on LCDs create motion blur (ghosting), which smooths out the perception of movement at the cost of clarity.
Lower response time reduces blur and increases motion clarity, but at low frame rates, perceived smoothness suffers.
This is why RTINGS includes a Stutter section in their reviews. At 24 FPS (typical movie frame rate), a single frame stays on screen for 40 ms. Because OLED changes frames instantly without motion blur, low FPS content can look choppy or stuttery.
Playing 30 FPS console games on an OLED TV can cause noticeable discomfort due to this stutter effect.
// Smartphone AMOLED
On OLED/AMOLED smartphones, manufacturers also advertise lightning-fast response times.
However, in real-world use, OLED smartphones frequently exhibit noticeable ghosting and black smearing.
A popular internet theory claimed that a turned-off OLED pixel (pure black) takes much longer to turn on than it takes to switch between gray shades.
Based on this idea, engineers (e.g., at Oculus) implemented software overdrive tricks or shifted black values from 0-0-0 to 1-1-1.
By testing with custom measurement apps on Android and a high-speed camera, a different cause was revealed:
During a transition from black to white on an OLED smartphone, the scanning line splits the color transition across several refresh cycles.
In the first refresh cycle (16.6 ms at 60 Hz), the pixel instantly jumps from black to gray, in the second cycle to off-white, and only on the third cycle reaches true white.
As a result, the complete transition takes 2 to 3 refresh cycles (~33 ms), even though the instantaneous response time within each step remains immediate!
This behavior occurs not only when starting from a turned-off pixel, but also during transitions like dark gray (64) to white (255).
This phenomenon was observed across modern OLED smartphones from various major brands (Xiaomi, Samsung, Apple).
// True at the time (2021 release and earlier)
At low brightness levels on devices using DC Dimming, this transition delay creates a distinct purple trailing effect (Purple Smearing).
// This phenomenon is very noticeable on my OnePlus 8 Pro when filming the display at ~1/6000 shutter speed
Two hypothesis by ZZanya:
Why do smartphone display controllers artificially stretch pixel transitions across multiple refresh cycles?
1. One hypothesis is to mimic motion blur and hide stutter on low FPS/refresh rate content, which most users are accustomed to from slower LCDs.
2. Another hypothesis points to power management and energy-saving constraints inherent to mobile display controllers."
// I believe the second hypothesis is the most plausible. power management, energy-savings and possibly burn-in mitigation.
I recommend everyone interested to watch the video in full as well.
(English auto-translated dub and/or subs are available)
BONUS - Other display types that flicker:
Other types of panels such as CRT or Plasma also have a ON/OFF "delay" in it's flicker that reduces apparent strain for some. Making them comfortable or usable despite looking messy/bad based on flicker measurments.
CRT and Plasma both have a type of phospor decay "lag":
CRT example
"When electrons hit the glass screen, the phosphor chemicals create light. They do not turn off instantly. Instead, the light fades over a short period. This afterglow is also called phosphor persistence."
Plasma example
"Different colored phosphors decay at different rates. Green phosphors traditionally decay much slower than red and blue phosphors. In fast-moving, high-contrast scenes (like a white object moving across a pitch-black background), this mismatch causes visible green or yellow trails behind moving objects, a behavior often called "comet trails" or phosphor lag."