- Sep 10, 2012
- 1,901
- 117
- 63
Not seeing anything.
Sorta, but it's not that easy to see on my screen.
Are you talking about the lines ? That's a screen defect. I had to do a warranty exchange on my s8 for something similar to this .
Yes it happened on my s8. I only noticed it when I went to a website that was white. I tried to do claim with Asurion , but they sent me to att and att did a warranty exchange for free. They said it was a screen defect.Yes the lines. It just popped up out of the blue though. Did that happen with yours?
Yes it happened on my s8. I only noticed it when I went to a website that was white. I tried to do claim with Asurion , but they sent me to att and att did a warranty exchange for free. They said it was a screen defect.
Hmm odd... it's a really bright pattern. I'm not familiar with burn in... I've no idea what this is but it's really bright
Burn in or any screen defects don't show in screenshots. Only software issues would show.
Yep.. I'm at Verizon store & they said it's burn in. Very odd because based on what the employee said here it's caused from leaving the same screen on all the time like overnight? I cannot think of any instance on when that would happen
Very odd
Yep.. I'm at Verizon store & they said it's burn in. Very odd because based on what the employee said here it's caused from leaving the same screen on all the time like overnight? I cannot think of any instance on when that would happen
Very odd
If you use the screen on for navigation for long periods of time can cause burn in
Screen brightness is a big factor
Yeah it is strange ..I don't ever use navigation lol. This is really mysterious
Yeah it is strange ..
If you use the screen on for navigation for long periods of time can cause burn in
I use Waze every day to and from anywhere I go, work, play, vacation, etcetera, etcetera. Since Waze came out, one several phones. I've never seen burn in. I also always use auto /adaptive brightness, tho.
Since the OP cannot think of an instance when she's left the sane screen on for long periods of time, I would imagine that is simply a screen failure.
Good luck to the OP in getting it sorted out!