2015 MacBook Air battery drains quickly (when off)

darkness974 Posted messages 1767 Registration date   Status Member Last intervention   -  
darkness974 Posted messages 1767 Registration date   Status Member Last intervention   -

Hello team,

I'd like to get your help with a concern that I find quite worrying.

So, I have a MacBook Air from 2015. I recently had the battery replaced by an authorized store specializing in Apple products sales and repairs.

Following the installation of the new battery (not a generic one found online but a genuine Apple battery)

I've noticed that when the laptop is turned off (Apple menu > Shut Down Mac), when I turn the computer back on (let's say 1 hour later), even if I had 100% charge before shutting down, I've already lost 2 to 3% of the charge. If I turn it on after 5 hours, for example, I can easily lose 8 to 15%. I tested not touching the Mac for a whole day (still after charging to 100%), and by the end of the day, I only have 50% left.

As I said, the computer is definitely shut down, I've tried everything, disabled WiFi, Bluetooth, I ran a diagnostic on the device, the scan doesn't find anything, I reset the SMC, and it's still the same problem.

I even reinstalled OS Monterey 12.4 by formatting the hard drive and starting from scratch.

Nothing works, I just updated the OS to Monterey 12.5 (still the same).

I noticed online that many people have the same problem with different MacBooks, but there's no miracle solution.

By the way, is it advisable to leave the Mac in sleep mode for a long time instead of turning it off? Since that's the temporary solution that works for me.

At worst, as the support mentioned, I need to bring the Mac in for checks…

In the meantime, I'm brooding.

Oddly enough, when I put the Mac in sleep mode, if I shut it down at 100% charge, upon waking the system, even after 5 hours of non-use, I've lost a maximum of 1%.

1 answer

  1. Anonymous user
     

    Hello,

    I tested not touching the Mac for a whole day (still after charging to 100%) and by the end of the day, I only had 50% left.

    hmmm... that's not really normal... I wonder if this battery is really new and original Apple??

    However, it is not recommended to charge the battery to 100% - to avoid this, I use an application that limits the charge... in my case, I opted for a limit around 85% - If you use this application, first do a calibration - just the first time, then use your Mac either on charge or on battery, and when it is charging, make sure the application is running, the application is called AlDente. There are quite a few articles explaining why charging to 100% can be harmful to the battery's lifespan.

    https://apphousekitchen.com

    By the way, is it not advisable to leave the Mac in sleep mode for a long time instead of turning it off? since it's the temporary solution that satisfies me.

    No, it is not discouraged to leave a Mac in sleep mode instead of turning it off. On the contrary, it is better to use sleep mode rather than turning it off.

    @+ :)


    0
    1. darkness974 Posted messages 1767 Registration date   Status Member Last intervention   240
       

      Thank you for your response,

      so for the battery, I installed Coconut Battery to check the battery status, and it's clear that it's new, with 2 cycles when I picked it up from the workshop.

      Currently, I'm probably at about 10 or 15 cycles, and it's not changing. I'm going to take the equipment back to the service center first, and we'll see after that, but I'll likely use the log you recommend as soon as I receive the machine.

      In fact, I charge the battery until it gets down to almost 25%, and then when I use it normally, the battery seems to be working well (internet use, YouTube, Plex, streaming, and doing some office tasks for work). I even disabled Spotlight since the Activity Monitor often showed that Safari and Spotlight were the most resource-hungry.

      Actually, I reset the SMC because that's the most well-known solution on the internet; I really hoped that was the issue, but it wasn't.

      0