116
this post was submitted on 08 Jul 2024
116 points (99.2% liked)
Asklemmy
43782 readers
892 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Burn-in isn't a light being emitted when off, it's a light being dimmer when on.
An LED works by passing current between two different semiconductors. When an electron jumps over the "gap" between those two semiconductors, it releases a photon of a particular color (determined by the size of the gap). But over time, as an LED is used, the gap can be damaged (by heat, by vibration, etc); when this happens, fewer electrons can jump the gap and thus fewer electrons produce photons. Or the properties of the gap are changed so that they emit a slightly different wavelength photon. So if you leave a particular set of pixels on, producing light, for an extended time, those LEDs will degrade more than the rest of the screen, leading that area to be discolored or dimmer. This is burn-in.
Most of the time, that's fine, because the LEDs on your screen experience wear in a more-or-less uniform pattern. Your phone is somewhat less susceptible to this, since (1) you tend to have your phone screen off most of the time, (2) there aren't as many persistent HUD elements even when it's on, as every app has its own configuration of controls and UI elements, and (3) you tend to replace a phone more often than a monitor. When you replace your phone, it's probably more-or-less evenly dimmer overall than it was when you bought it, but since you don't have anything to compare it to, you won't know; with burn-in, though, that comparison is right next to the burned-in pixels.
By contrast, a computer monitor will typically be on for 8+ hours at a time, and persistent display elements are a part of every major operating system. If you're not using the LEDs in a panel more-or-less evenly, you'll end up with a persistent image.
Bold assumption
Fair point, I don't know you. The average phone user, then. Most people use their phone about 4ยฝ hours a day.
My retort was in fact a joke. I am terminally online and even I only average about 6 hours. But thank you
Edit: Just checked, my average screen time this week was about 7 hours per day.
I figured, but I didn't play along very well.
Thanks, makes sense. But why don't monitors have an "emergency" protocol to let the LEDs rest a while if we can know what's the max stress that they can handle?
So instead of burning out, I'd get a pop up saying that I should do something, or it lowers the brightness in that area or smth.
I have five guesses:
(1) That would require more diagnostics than an LED on a monitor is able to provide at a reasonable cost, (2) if you're leaving the monitor on in a situation where burn-in is likely, you're probably not at the monitor when it matters, (3) monitors are a mission-critical piece of hardware, meaning that them turning themselves off (or even just turning off certain pixels) randomly is not a great idea, (4) it's probably the OS's job to decide when to turn off the monitor, as the OS has the context to know what's important and what isn't, and how long it's been since you've interacted with the device, and (5) it's in the monitor manufacturer's best interest for your monitor to get burn-in so that you have to replace it more often.
The actual answer is probably a combination of multiple things, but that's my guess.
Honestly, setting a screen timeout (or even a screen saver!) is the solution to this problem. So the problem was more or less solved in the early 80s.
very good points, thanks.