Steam Hardware
A place to discuss and support all Steam Hardware, including Steam Deck, Steam Machine, Steam Frame, and SteamOS in general.
As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title
The following is a list of suggested flairs:
[Deck] - Steam Deck related.
[Machine] - Steam Machine related.
[Frame] - Steam Frame related.
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.
If your post is only relevant to one hardware device (Deck/Machine/Frame/etc) please specify which one as part of the title or by using a device flair.
These are not enforced, but they are encouraged.
Rules:
- Follow the rules of Sopuli
- Posts must be related to Steam Hardware or Steam OS in an obvious way.
- No piracy, there are other communities for that.
- Discussion of emulators are allowed, but no discussion on how to illegally acquire ROMs.
- This is a place of civil discussion, no trolling.
- Have fun.
view the rest of the comments
A lot of people have done burn in tests on the OLED, and it's barely a concern. The tech has really improved.
Since you said 'the oled' i assume you mean the steam deck oled. Im not denying its bad, on contrary. Steam deck is a device that is constantly changing whats displayed. Thats good to prevent burn in on any device. The guy said oled is always better, which is what i disagreed with. Ive seen enough phones and computers monitors that were oled that had the windows taskbar, or android status bar, burned in over the years cause its a static thing. Like any display, burn in is possible but dont underestimate oled on burn in
Even then, the concerns are way way way waaaaaay overblown.
Hardware unboxed have been purposely trying to burn in an OLED for thousands of hours, and it's still barely perceptible even when you're trying to look for it by taking a picture of the screen then applying filters to make it more visible. In real world usage its effectively impossible.
With any modern OLED display, burn in is something you don't need to worry about.
I've been hearing how burn in isn't an issue for years, but every phone I've had has had burn in. So I make sure to avoid apps that has a persistent UI if they are ones I'd use frequently.
I wouldn't notice in normal use cases then be surprised when I read manga or webtoons on the display.
I've not had a single phone that's suffered burn in.
Regardless, I'd trust someone who reviews displays for a living over my own anecdote.
The one group I can think of that actually tests burn in is rtings and they do that for TVs and monitors.
Phone reviewers just cycle through multiple phones so are the least reliable not using one phone as often or as long as regular people. Especially even more now that how long people retain phones has gone up with price increases.
Which actually has me wondering. How long do you typically use phones. Some upgrade every year. Some every 2. I've upgraded maybe on average 3 years or longer. So long it was the reason I shifted to custom roms in the past as security updates stopped. And getting nav burn taught me to try things like auto hide it.
I still have a oneplus 6 I use as a back up which is a phone that came out 7 years ago. Not sure how many years I've had it, but that's got burn in couple years ago. Do you use phones that long?
Ehhh, it's still a thing. I had burn in on my S9, and I babied that thing explicitly to prevent burn in. And that was after 4-5 years. My desktop monitors are nearly a decade old starting next year (wow, 1440p still has amazing staying power).
I'd definitely worry about burn-in if you have Teams open for nine hours a day and the taskbar on. It's crazy to me that phones still burn in from casual use. :/
I didn't say it's not a thing, I said it's not something you really have to worry about with modern displays.
And yet, the testing seems to show that's not an issue.