4 ms·
From the name alone I assumed this was going to move the browser UI around to prevent burn-in. Has anyone attempted this yet? Perhaps as a native feature?
by vultour 1y ago
From the name alone I assumed this was going to move the browser UI around to prevent burn-in. Has anyone attempted this yet? Perhaps as a native feature?
- eknkc 1y agoIs burn in still a thing? Early gen OLEDs had abysmal burn in and I had devices with static ui elements like status bars etched into screen in a couple of months. It feels like history now.
- bloqs 1y agoVery much so. Getting it on a 360hz monitor currently due to my own neglect
- dcow 1y agoWhat did you do?
- dcow 1y agoThe on-device hardware even does neat little tricks like shift your image around by a pixel or two so you don’t have to think about it. Haven't ever seen burn-in on an OLED, myself.
- LtdJorge 1y agoThe pixel shifting that GP mentions is already included in most if not all. I'm dailying an LG C3 42" as a monitor and these 16 months, so far so good. However, I am on Linux and running a custom "DE" with Sway, my background is pure black and swayidle locks my screen in 3 minutes (to black). Also, anytime I get up, I power it off because even if it's displaying only black, the screensaver kicks in after some time (dumb feature that I cannot disable and would be better served by my solution).
- wtcactus 1y agoYes, OLED burn in it’s still very much a thing and it didn’t improve significantly- or at all. You can see this YouTube channel (my go to when choosing monitors) and the tests they did on that particular subject: https://youtu.be/k-NOoMklpPM https://youtu.be/k-NOoMklpPM
- WindowsDev 1y agoIt currently does not, just handles applying a uniform black theme across all domains. Good suggestion though, I will look into implementing this today. (My idea is, to use a custom zooming offset determined by the date- applying a random zoom % between 0 and 116 while keeping font size original, not too obvious to the person but enough to shift the pixels around a bit.