One UI 6 Feedback: Users bring attention to potential Screen Burn-In problems

  • Facebook
  • Twitter
  • Reddit
  • Flipboard
  • Email
  • WhatsApp
One UI 6 Feedback: Users bring attention to potential Screen Burn-In problems (Image: reddit.com/user/dragosslash)
One UI 6 Feedback: Users bring attention to potential Screen Burn-In problems (Image: reddit.com/user/dragosslash)

Delhi : A few devices have received the update with new features following the recent release of One UI 6. Users have, however, noted a problem with OLED screens' pixel shift feature that could result in screen burn-in. Reddit users brought attention to this issue, with dragosslash offering insights.

When One UI 5 and One UI 6 screenshots are compared, it is clear that One UI 6's status bar is static, which could be a sign of an issue with the burn-in protection feature. The navigation bar's pixel shift feature appears to be working, but the status bar's unmoving icons point to a potential One UI 6.0 problem.

Screen burn-in, a persistent discoloration that can impair display quality, is a possibility with OLED screens. The One UI 6 upgrade appears to be broken in terms of the pixel shifting feature, which was included in One UI 5 to prevent burn-in. It has been observed by users that the icons in the status bar no longer move in the proper alignment. According to Reddit user dragosslash, a straightforward three-step test can be used to confirm the problem:

  1. Snap a picture while the status bar is still visible.
  2. Five times, rotate the screen from portrait to landscape orientation.
  3. To view the location of the status bar, open the screenshot in Samsung Gallery.

Concerns concerning the efficacy of One UI 6's burn-in prevention have been raised by multiple users who have confirmed experiencing the same problem on the Reddit thread. If One UI 6's burn-in protection is actually broken, customers are hoping that Samsung would provide a quick repair. Given the awareness raised by users on the r/oneui Reddit forum, the business may address this issue in a future release.