> ...if you're getting smearing of any kind it wasn't an OLED
I have a Pixel 5a.
It has _comically_ slow switching times between dark-ish colors and blacks that's most obvious with dark blue-family colors.
If you have such a phone, go check out the "Gunnerkrigg Court" webcomic (<https://gunnerkrigg.com>), scroll down to the border between the comic and the blog part, and jostle the viewport up and down.
If you go check out today's episode (comic 2929), you get an especially long trail of slow-transitioning pixels in the art that is particularly noticeable in the bottom panels of the comic, itself. (Examine the black borders of the people's hair, as well as the black frame of the comic panels. If you're not noticing it, scroll at a rate of travel of roughly one-quarter of the screen's height per second.)
I realize that this is not even on topic, but _what a jolt of nostalgia_. I haven't even thought of that comic in what feels like a decade. Perhaps that's the optimal way of reading a webcomic (waiting until it's binge-able)? It's tripled in length since I last read it, and now my phone actually will display it :D (now if only the web interface tracked what page I was on, so that coming back months later didn't show Today's page, and instead showed where I last read ...)
On-topic, I have tried jostling the page on my Pixel 6a (also a 60hz OLED screen), and I don't notice _at all_ the display latency or issues that you mention. The only time I've noticed any kind of delay or ghosting like that is when I have it in extremely low brightness settings (reading at night in the dark), with "extra dim" enabled.
> Perhaps that's the optimal way of reading a webcomic (waiting until it's binge-able)?
Man, I tend to think so. (Though... I say that, and I've been reading Gunnerkrigg thrice a week for what seems like five years now, so sometimes I think one thing and do another sometimes. ;))
It's a good comic, IMO.
> The only time I've noticed any kind of delay or ghosting like that is when I have it in extremely low brightness settings (reading at night in the dark), with "extra dim" enabled.
I would have never thought to play with the brightness settings.
So, I nearly always have my screen on "8->10% brightness, automatic brightness adjust, 'extra dim' disabled.". I played with the brightness settings just now and discovered that I have to get the brightness up to 100% before the smearing is _nearly_ gone. At 50%, the trails are much, MUCH smaller than at ~10%, but still obviously there. 75% is not _that_ much better than 50%.
> [I have a] Pixel 6a
Hmm! Maybe in the year between the 5a and the 6a's release, they got on display manufacturers' collective asses to substantially reduce the amount of color smearing in the display that they selected for their next phone.
> This is a limitation/downside/flaw of "VA" LCD panels. OLED panels will not experience this...
I don't know what to tell you, man. I'm seeing this behavior on a Pixel 5a. Purchased _directly_ from Google's store. Google says this model of phone has a OLED display... an HDR one, at that. [0]
Not even the worst color transitions for my my VA monitor (a BenQ EWE3270U) streak this badly.
Pixel response times are one small part of the equation. The vast majority of modern display blur comes from sample and hold motion blur, not pixel transition times.
> No idea what display you are looking at, but if you're getting smearing of any kind it wasn't an OLED
I am looking at a 27" LG27GR95QE. A 240hz WOLED panel produced by LG. Just one of multiple OLED panels I currently own. This is just in addition to a few high end LCD FALD panels, a couple of 21" Trinitrons and a handful of JVC broadcast CRT's.
