View original (French)

MacBook Air M2 Sleep Mode Issue

Maxencio -  
 Anonymous user -

Hello,

I recently got a 13.6-inch MacBook Air with an M2 chip and I've encountered a problem:

every time my screen goes to sleep on its own after about 3 minutes, and I wait around 10 minutes before raising the screen, it remains in sleep mode, and when I press the power button at the top right to wake it up, the screen lights up for half a second and then goes back to sleep. I have to press the button a second time to turn the screen on.

Also, I've noticed that when I wake the Mac from sleep by pressing a button or using the trackpad, the screen makes a small sound, and I'm not sure if that's normal.

If someone knows how to fix this annoying problem over time, I would be very grateful.

Thank you in advance.

2 answers

  1. Anonymous user
     

    Before moving to a new version of macOS, the current issue needs to be resolved. You don't update a virus-infected version... so customer service for a Mac under warranty.

    *_Francis_*
    Have a good day, good evening, good night ;)
    iMac mid-2011 - MacBook Air M1

    1
    1. Maxencio
       

      Okay, that works. Is it still possible to take care of it at an Apple Store or do I need to make an appointment?

      0
      1. Anonymous user > Maxencio
         

        Hello,

        I provided you with a link to find the nearest authorized customer service. You need to call and make an appointment. Quickly, while the warranty is still valid.

        0
  2. Anonymous user
     

    Hello,

    This Mac is very likely still under warranty, so I suggest you go to an Apple authorized service provider for verification:

    https://support.apple.com/en-us/repair/verify-repair-provider

    Best regards.

    *_Francis_*
    Have a good day, good evening, good night ;)
    iMac mid-2011 - MacBook Air M1

    0
    1. Maxencio
       

      Okay, thank you very much, and do you know if they make appointments quickly or not?

      0
    2. Maxencio
       

      And I also forgot to ask you if this issue could be resolved after the next macOS 14 Sonoma update?

      0