Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Careful. #38

Open
YTF1shhh opened this issue Jul 2, 2021 · 5 comments
Open

Careful. #38

YTF1shhh opened this issue Jul 2, 2021 · 5 comments

Comments

@YTF1shhh
Copy link

YTF1shhh commented Jul 2, 2021

After leaving this on for a long time the pixels are burnt into the OLED screen. This is expected but if you don't want this don't use it for long periods of time. To prevent this you could add a thing where it moved around the OLED sort of like what the Always On Display does on android phones with OLED displays. I know if this is possible.
Picture: https://prnt.sc/184pqpd

@mtricht
Copy link
Owner

mtricht commented Jul 5, 2021

Is it just the icon that is burnt into the OLED screen? Or more? @YTF1shhh

@ACanadianBear
Copy link

The logo would probably burn in over time as it is static. Could a pixel shift be implemented?

@YTF1shhh
Copy link
Author

YTF1shhh commented Jul 6, 2021

@ACanadianBear yes I said that in the first message Android devices that have OLED displays have pixel shift with their Always On Display to prevent pixel burns. @mtricht The icon and where the numbers are for the clock but you can't really tell what the numbers are it's sort of just all the numbers mixed together.

@Paft
Copy link

Paft commented Jan 4, 2024

So there's no solution to this until pixel shift is implemented? When I discovered and tried this that was my first concern.

Even if you disable icons, there are times when some pixels will almost constantly be lit up, like the colons in the clock for example.

I think this is the only thing stopping me from using it.

@Enrico9431
Copy link

Enrico9431 commented Jan 19, 2024

Reading this, pixel shift would be a nice implementation indeed. Anyway how long is a "long time" before pixel burn may happen, minutes, hours, days?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants