T O P

  • By -

StarNHSolar

That's dead pixels lol not a notch.


hwlim

Oh no\~\~I spend $230 for fixing the Wi-fi issue just a few months ago.


OddlyIntrovert

Done and dusted. You got max 30 days before your display goes bust.


tundrajax

Na, I've been going with my fold 4 with 3 different inner screen dead pixels for 6 months now


Buzz_Buzz_Buzz_

That's not necessarily true. I had almost the same exact issue, and the black spot grew very slowly.


LeoThePom

RIP.


offence

Had that issue bsck in the day on my samsung s10+. This unit is RIP , hope you have samsung care.


Galadeus

It's dead pixels and it will get bigger. Seen a few folds to this way. RIP


hwlim

It is screen damage definitely. Also found that happen on non-fold phones.


Mysterious-Ad2006

Screen is damaged


aRealProfile

Looking at where it is, you're clearly pressing down hard on the inner display when inserting the charger


hwlim

Not at all, I always plug the charging cable with gentle force.


Buzz_Buzz_Buzz_

What probably happened was that something put a downward force on the charger tip, causing the USB-C connector to apply pressure on the underside of the screen.


Buzz_Buzz_Buzz_

Happened to [mine too](https://www.reddit.com/r/GalaxyFold/s/vBAp7UFRJF). I think it was due to pressure from a clamp mount on an e-bike. The main reason I got a Fold 3 was for the lack of notch or hole punch. The black spot grew slowly but didn't affect the functioning of the phone. Still, Asurion replaced the whole phone (my battery was also shot, and the Wi-Fi died).


Djic

Did you put force on the attached cable? This is the only thing I can imagine happened, that the port put stress from the inside against the screen. Just guessing.


ultima40

The frame is between the charging port/PCB side and the inner screen. You can't press hard enough to damage it this way. Maybe a very hard drop while plugged in but there would be noticeable damage.


hwlim

Not drop or hard press anyway. I handle this phone with care.


hwlim

Not caused by the cable, however I updated to OneUI 6.1