InfiniTimeOrg / InfiniTimeOrg/InfiniTime
Burn-in after using always-on-display
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.4k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Verification
- I searched for similar issues (including closed issues) and found none was relevant.
Introduce the issue
I got my pinetime a few weeks ago, and have been using it with always-on-display enabled since. I am beginning to notice a burn-in effect, where parts of the watch face (infineat) are visible on other screens, particularly notifications, but I can also make it out in the gray portions of the settings and quick-actions menus. I have also noticed it on the pong game and the pinecone loading screen at boot. It is currently pretty subtle, but I'm worried it could become worse over time. The effect is far less noticeable on a camera vs. looking at it directly, so I have included both an uneditied photo and one with the contrast adjusted to make the effect closer to what I'm seeing.
Notification Screen (Unedited):
Notification Screen (Contrast Adjusted):
Pong Game (Unedited):
Preferred solution
I would like to see this investigated further, and if it's determined that this effect continues to get worse over time, possibly a warning in InfiniTime that pops up when you turn on always on display, saying that burn in may occur on some watches.
Version
v1.15.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported display persistence on a Pinetime running InfiniTime v1.15.0 with always-on display enabled, comparing the notification, settings, quick-actions, Pong, and boot screens. Done means documenting whether the effect worsens over time and determining whether a warning in InfiniTime is warranted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100