Samasung galaxy z flip 4 recent issues

[Members_4dgkZ8Y]

My phone no longer wants to unlock properly. I unfold it and the screen stays black; i use biometrics to open, I hear the unlock sound, but screen stays black; i relocked using button, hear the noise, use the button to unlock, screen finally lights up and unlocks - BUT this is only if i lock the phone with the button before folding it. If I fold it while unlocked, the screen won't turn on. I can hear the locking/unlocking sounds but its still black. I have to restart it twice before the screen comes on, and sometimes that only works if it's on charge. This is a new issue that has been happening for roughly 2 weeks now and may have something to do with the new update, as it was fine beofre then. Samsung, can you please fix this? It's definitely a software issue, not a hardware one, as once the screen come on I can see that it responded to any clicks I did while the screen was black.

[Tourbillon De La Vie]

Contact Samsung support via Members app and let them deal with it

[VioletOrchid]

Hi. I have the same problem with my phone too. I've noticed if I leave the phone open and the screen turns black, if I don't immediately tap the screen to wake it up or hit the side button, I will have a hard time waking up the phone. If it stays black a minute or so I'll have to hit the side button a few times before the screen responds. Sometimes if I hold down the power button as if trying to turn it on the screen will wake up faster. 

If I shut my phone while the display is still on, then open my phone to use it, the screen stays black and it takes several spaced out clicks to the side button before the screen decides to show up; but if it doesn't I will leave the phone open for a few minutes and try again and at that time it usually responds right away. But the issue always repeats it's self the same way.

I only started to notice this after the last 7.0 update. I was going to try maybe going back to the previous version to see if it helps. 

[SP432]

This Problem has been happening since early June to many people worldwide after the latest software update but Samsung is not doing anything to rectify it.
You can read the thread dated 12/6