10.15.5 (19F101) battery issues?

[iFoggy]

Hi,

Running macos catalina 10.15.5 (19F101) which over the last week I have noticed that I would close the lid @ around 60% battery and when I go back to it hours later it is dead and flashes the battery empty graphic.

Thought it might be a software issue since updating to 10.15.5 so reloaded init fresh with a 10.5.5 installer and it did the same thing again

Run Coconut & Battery 2 app and they say the battery is in 'good' health

Just happen again with the battery empty icon and plugged it in to the charger and it booted up showing 65% left of the battery which was what it was when I closed the lid because now I am conscious of the issue

Anyone else getting this?

Battery health is enabled

 

[matram]

For me battery management reduces max charge slowly in step of -1% when on charger. Currently down to 97%. It does not sound like what you are experiencing.

Note that the battery is very sensitive to deep discharge. A handfull of times is enough to kill the battery. Make sure that your computer is really suspended before putting it aside.

 

[iFoggy]

Thanks..I have also just been able to close the screen and a day later open up and maybe the battery has gone down a couple of %.

the issue is not that the battery is dead but without attaching it to the charger it displays the empty battery logo, attach it and it boots to the % of when last used like 65%

 

[matram]

Sounds like your battery is bad

 

[FNH15]

Hi,

Running macos catalina 10.15.5 (19F101) which over the last week I have noticed that I would close the lid @ around 60% battery and when I go back to it hours later it is dead and flashes the battery empty graphic.

Thought it might be a software issue since updating to 10.15.5 so reloaded init fresh with a 10.5.5 installer and it did the same thing again

Run Coconut & Battery 2 app and they say the battery is in 'good' health

Just happen again with the battery empty icon and plugged it in to the charger and it booted up showing 65% left of the battery which was what it was when I closed the lid because now I am conscious of the issue

Anyone else getting this?

Battery health is enabled

What machine do you have? My 2018 15” sometimes does this - indeed 10.15.5 reports that I need a new battery. Unacceptable for such a new machine, honestly.
What does System Preferences show under Energy Saver?

 

[Honza1]

Try reseting SMC and PRAM or whatever we can resent these times. May be the battery is not read correctly...
If that does not help, it may be bad battery or some other hardware issue. This is not normal and should be fixed. Hope you have it under warranty.

 

[Taz Mangus]

Do a SMC reset this will reset the battery management.

Reset the SMC of your Mac - Apple Support

The SMC is responsible for managing power on your Mac. Resetting it can resolve certain uncommon issues related to power or thermal management.

support.apple.com

 

[Henriiiii]

Believe me im suffering the same since I upgraded my 2016 macbookpro to 10.15.3. It’s a bug that keeps running some programs to keep your Mac from sleep on Catalina. All we can do is to hope apple to fix it on the next OS upgrade.

 

[posguy99]

Believe me im suffering the same since I upgraded my 2016 macbookpro to 10.15.3. It’s a bug that keeps running some programs to keep your Mac from sleep on Catalina. All we can do is to hope apple to fix it on the next OS upgrade.

You do realize that 10.15.7 is the latest release of Catalina.

 

[Honza1]

Believe me im suffering the same since I upgraded my 2016 macbookpro to 10.15.3. It’s a bug that keeps running some programs to keep your Mac from sleep on Catalina. All we can do is to hope apple to fix it on the next OS upgrade.

It is not a common bug, it is some problem on your specific Mac. Something is wrong on that specific MPB and Apple will not fix it for you. Well, it may accidentally during upgrade.
What you need to do is find out which program is doing that and fix it. Or, take the easy way out which Apple would take. Backup your system preferably twice (on two different media). May be using CarbonCopy Cloner or Disk Duper.
Wipe the hard drive.
Reset PRAM/SMC
Install fresh system. Verify it does not have problems...
Migrate your accounts back.
Sounds drastic (and it is) but should fix these issues. And is easier than you may think, Apple Guru at Apple Store will do this for you while you wait (in about 2 hours or so) ;-)
Well... Not always. I think I saw somewhere notes from someone with issues in iCloud (or Keychain?) and this procedure did not help. Eventually he/she ended up fixing those other issues and all was fine again.
Waiting for Apple to fix this kind of one-off problem is not going to help you with anything. This is not as common as you may believe, sources of issues vary, and so this is not systematic bug which can be fixed once for all.

 

[Henriiiii]

It is not a common bug, it is some problem on your specific Mac. Something is wrong on that specific MPB and Apple will not fix it for you. Well, it may accidentally during upgrade.
What you need to do is find out which program is doing that and fix it. Or, take the easy way out which Apple would take. Backup your system preferably twice (on two different media). May be using CarbonCopy Cloner or Disk Duper.
Wipe the hard drive.
Reset PRAM/SMC
Install fresh system. Verify it does not have problems...
Migrate your accounts back.
Sounds drastic (and it is) but should fix these issues. And is easier than you may think, Apple Guru at Apple Store will do this for you while you wait (in about 2 hours or so) ;-)
Well... Not always. I think I saw somewhere notes from someone with issues in iCloud (or Keychain?) and this procedure did not help. Eventually he/she ended up fixing those other issues and all was fine again.
Waiting for Apple to fix this kind of one-off problem is not going to help you with anything. This is not as common as you may believe, sources of issues vary, and so this is not systematic bug which can be fixed once for all.

I’ve already try all this several times and none of them works. Even I took it to the Genius Bar and they couldn’t find out what the cause is. After testing for several days the way they find out is telling me to pay hundreds bucks to replace the whole logicboard. So there’s literally nothing I can do.

 

[Honza1]

I’ve already try all this several times and none of them works. Even I took it to the Genius Bar and they couldn’t find out what the cause is. After testing for several days the way they find out is telling me to pay hundreds bucks to replace the whole logicboard. So there’s literally nothing I can do.

OK, that is bad, but what is that telling you is, that this is hardware problem and Apple will not fix this in software. If this was not happening in prior releases of macOS, you can try to downgrade. It is possible this hardware problem was not interfering with prior macOS systems. It is also possible hardware issue developed around the upgrade or was provoked by firmware upgrade which may have been associated with 10.15.3.
Either way, it is unlikely this will be fixed in software and, unluckily, means you will have to get this fixed or live with it. If sleep/discharge is all what the problem does, shutting down the system for longer times seems relatively cheap solution compared to mainboard replacement.

 

[Henriiiii]

OK, that is bad, but what is that telling you is, that this is hardware problem and Apple will not fix this in software. If this was not happening in prior releases of macOS, you can try to downgrade. It is possible this hardware problem was not interfering with prior macOS systems. It is also possible hardware issue developed around the upgrade or was provoked by firmware upgrade which may have been associated with 10.15.3.
Either way, it is unlikely this will be fixed in software and, unluckily, means you will have to get this fixed or live with it. If sleep/discharge is all what the problem does, shutting down the system for longer times seems relatively cheap solution compared to mainboard replacement.

It’s defiantly a bug that apple didn’t admit it. The main thing is even the so called “genius” works for apple couldn’t tell what’s going on here. They can‘t even make sure if it’s due to software or hardware. It can’t be explained with such a simple “hardware problem”. And it’s not just happening on me, you can go search “battery drain during sleep/lid closed” in this forum, it‘s troubling way more people than you think. So do you think a simple OS update is breaking all their hardware?

 

[Honza1]

It’s defiantly a bug that apple didn’t admit it. The main thing is even the so called “genius” works for apple couldn’t tell what’s going on here. They can‘t even make sure if it’s due to software or hardware. It can’t be explained with such a simple “hardware problem”. And it’s not just happening on me, you can go search “battery drain during sleep/lid closed” in this forum, it‘s troubling way more people than you think. So do you think a simple OS update is breaking all their hardware?

There is lot of problems with sleep function - but if you carefully read through this and many more forum chains, you will find out that there are some recurring culprits and some weird stuff, one off. I fought with this problem myself few times in the last 8+ years. iCloud sync seems common source of troubles and few other processes. Typically related to troubles between computer and Apple services. So there are issues which cause these problems, even though Apple will not call them bugs - they are issues with device configuration. Typically these can be fixed at least by full wipe/reinstall - unless something is wrong with account on the server side. These are specific issues impacting small number of people. These are not fixed by system wide fix but by fix on a user machine.
If you wiped and reinstalled clean system - and sleep still did not work, then something is wrong with that specific hardware. Other same systems are NOT doing this - there are literally millions of the same machine you have and most people do not have problem.
Minor hardware problems can cause behavior which looks like software bugs.
And yes, OS upgrade stresses the system lot more than typical use, it rewrites lots of data, may flash firmware (which can get corrupted also), typically loads CPU a lot for long time... Marginally performing hardware may be pushed over the edge. And people pay lot more attention to what computer is doing after upgrade, seeing stuff they may have missed before. More hardware issues seem to be identified at the time of OS upgrade than normally.

 

[Henriiiii]

There is lot of problems with sleep function - but if you carefully read through this and many more forum chains, you will find out that there are some recurring culprits and some weird stuff, one off. I fought with this problem myself few times in the last 8+ years. iCloud sync seems common source of troubles and few other processes. Typically related to troubles between computer and Apple services. So there are issues which cause these problems, even though Apple will not call them bugs - they are issues with device configuration. Typically these can be fixed at least by full wipe/reinstall - unless something is wrong with account on the server side. These are specific issues impacting small number of people. These are not fixed by system wide fix but by fix on a user machine.
If you wiped and reinstalled clean system - and sleep still did not work, then something is wrong with that specific hardware. Other same systems are NOT doing this - there are literally millions of the same machine you have and most people do not have problem.
Minor hardware problems can cause behavior which looks like software bugs.
And yes, OS upgrade stresses the system lot more than typical use, it rewrites lots of data, may flash firmware (which can get corrupted also), typically loads CPU a lot for long time... Marginally performing hardware may be pushed over the edge. And people pay lot more attention to what computer is doing after upgrade, seeing stuff they may have missed before. More hardware issues seem to be identified at the time of OS upgrade than normally.

Man, I think there’s no need for further discussion here. You really don’t know what we’re facing and what really troubling us. What your suggestions and conclusions are not helping at all. And I, as a sufferer, just wanna share the information I’ve found for this specific problem to the one who is suffering the same.