Extremely Blurry Screen M1 MacBook Pro 16

From reading all the posts on everything not working, it's time Apple gets involved with a hands-on evaluation for each of them.

You're all getting nowhere fast.

Be sure that you tell them so.

Here is a site where you can leave them that message:

Product Feedback - Apple

Yes, but it costs about £700 in the UK to do so unfortunately.

The screen you are showing is similar to what you would see if your Mac has been idle and timed you out. It is inviting you to enter your password to get access again. the background is blurred by design, not due to any failure.

The settings is in

System preferences > Security & Privacy > General ...

[√] require password nnn minutes after sleep or screensaver begins

Same issue here, was just working with the M1 macbook and suddenly it was like a black vale spreaded over the screen when pixels started to fade out. Now I only have a blurred, dim image of the desktop on my macbook screen while I work on an external display.

The Macbook is 1.5 years old and is mainly used indoors. I'm puzzled. Went to apple store half a year ago because I suspected this unit was quirky because I have crackling audio when playing sounds/movies but they said it was an issue with OSX.. not so sure about that now...

So was all your data fine? It was just a display issue? Having the same problem myself. It started the other day whilst working in Ableton. I was able to restart after several failed attempts. Then, today it happened again and won’t restart. I stupidly didn’t back it up with Time Machine (most of my most important files are backed up.

It’s a hardware issue, so they should be able to fix it while preserving the data, correct?

thanks so much!

-s

Could you explain it better?

I have exact the same problem. Apple charged me 1200 USD to replace my screen. I can't afford that. We have to do something... I have my MacBook only for one year and 6 months. Have you solved it?

The Better Display app didn't work for me. Here is my brand New MacBook Pro. Here in Brazil it costs almost 5000 USD. It is not acceptable. Please share your Macs image. We have to show Apple what's is happening to everyone.

Just got off the phone with Apple, they don’t even want to acknowledge the problem. I’ll be heading to the Apple Store to make noise. I paid more than $3000 dollars for this machine and they want me to pay another $800 and can’t even acknowledge that people here are all experiencing the same issue.

Well, somebody at the Apple Store is about to have a bad day because I’m going to bark up a storm until someone at Apple acknowledges the issue.🥶

Hi ChimarraoMate,

Could you tell me exactly which feature you used within BetterDisplay which allowed turning off / on the built-in LCD? I have BetterDisplay installed, but there are many menus and many options. I don't know where to find the feature that you used and exactly what it is named.

Thanks!

I have exactly the same issue today. My Macbook Pro M1 16" is 2 years old. I am taking good care of it.

Tried BetterDisplay without luck. I can't afford to replace the screen if that's only the solution.

Mine isn't better. In just over 2 years, the screen died.

I doubt the reliability of the mini-LED tech Apple puts in our Apple silicon MBP.

Apple, please take this seriously. We're genuine MBP users, do not lose us.

@Work_by_Solo - I refused to pay $1000 to fix this laptop that is barely 1.5 year-old. So I just took the laptop back and I'm currently using it like a desktop with a monitor. This is very annoying. How can a PRO machine be so unreliable? I hope someone from Apple can take a look at this and help us fix this issue.

I am having the same issue. Macbook Pro with M1 purchased Nov. of 2021. Just randomly started to pixelate and half the screen went black and then it all went black. Can see light from apple logo but fuzzy. Hooking up to a display does work. I talked to a manager and they literally said I have to pay for it. This is a crime honestly. I already spent $2k and now they want me to pay to fix a hardware issue that isn't user error…