MagSafe disconnects on login (M1)

[OZ_]

Hello.
I need help with MagSafe.
It's not that bug when MagSafe doesn't work with the turned-off machine.
My MagSafe works fine until I enter my password. After that, on any attempt to connect the charger, the bulb becomes orange for 5 seconds, and the charger disconnects.

Monterey 12.1 (same was on 12.0.1),
MBP M1 Pro 16''

Results from "ioreg -w 0 -f -r -c AppleSmartBattery":

smart_b.txt

GitHub Gist: instantly share code, notes, and snippets.

gist.github.com

Results from "pmset -g everything"

https://gist.github.com/e-oz/8dfa17480e65b02568d24cc94e70807d

same without "assertions":

pmset.woassertions.txt

GitHub Gist: instantly share code, notes, and snippets.

gist.github.com

Battery info from "System report":

battery.info.txt

GitHub Gist: instantly share code, notes, and snippets.

gist.github.com

If it's possible to find the source of disconnects using this info - please help.

 

[satcomer]

That's really strange! Your best thing you could do sense it's fairly new call Apple support and explain the strangest to them because it should be still under 90 day AppleCare period!

 

[OZ_]

Update on this:
1 OS reinstall and 2 disk volumes removals didn't help.
If you know where I can find some files related to power settings - please let me know.

P.S.: I've plugged USB-C end of my MagSafe cable into my MBP, and it does charge itself, rofl. Perpetuum mobile
That's what pmset says about this:

Wattage = 7W
Current = 1460mA
Voltage = 5000mV
AdapterID = 0
Family Code = 0xe000400a

 

[OZ_]

I've found a way how to fix that bug I’ve encountered!

It will require just 2 steps. MagSafe should be connected:

1. In Terminal app: ‘sudo pmset -b hibernatemode 25’
2. Close the lid.

MagSafe will start working in 1 minute.

It was a long journey and I’m glad I found this solution, hope it will help someone else.

 

[jdb8167]

I've found a way how to fix that bug I’ve encountered - [MagSafe doesn't work after entering password](https://www.reddit.com/r/macbookpro/comments/rh8qpc/magsafe_3_disconnects_when_i_enter_my_password/) ?

It will require just 2 steps. MagSafe should be connected:

1. In Terminal app: ‘sudo pmset -b hibernatemode 25’
2. Close the lid.

MagSafe will start working in 1 minute.

It was a long journey and I’m glad I found this solution, hope it will help someone else.

That will (according to the pmset manpage) cause your MBP to always hibernate instead of plain old sleep. Waking up will be slower but other than that, it shouldn't affect much. It's odd that is fixes your problem which still seems like a software problem. Have you re-installed Monterey and started without restoring from a previous setup during your troubleshooting steps?

 

[OZ_]

That will (according to the pmset manpage) cause your MBP to always hibernate instead of plain old sleep. Waking up will be slower but other than that, it shouldn't affect much. It's odd that is fixes your problem which still seems like a software problem. Have you re-installed Monterey and started without restoring from a previous setup during your troubleshooting steps?

"Sleep" in MacOS equals "hibernate", there are just multiple modes. "25" means that RAM will not be powered during sleep - that’s exactly what I want when my MBP is sleeping without a charger (”-b” part of the command). With the charger, it will sleep as usual.

To restore the default behavior, run “sudo pmset -b hibernatemode 3”.


I’ve reinstalled OS 3 times, 2 of them with disk volumes removal; “revived” my system using Apple Configurator 2; visited Genius Bar; had 2 useless conversations with Apple Technical Support.

 

[jdb8167]

"Sleep" in MacOS equals "hibernate", there are just multiple modes. "25" means that RAM will not be powered during sleep - that’s exactly what I want when my MBP is sleeping without a charger (”-b” part of the command). With the charger, it will sleep as usual.

To restore the default behavior, run “sudo pmset -b hibernatemode 3”.


I’ve reinstalled OS 3 times, 2 of them with disk volumes removal; “revived” my system using Apple Configurator 2; visited Genius Bar; had 2 useless conversations with Apple Technical Support.

Sleep and hibernate are different. As you say, hibernate writes your RAM to disk and then turns off power to memory. Sleep is much lighter in that RAM stays powered and doesn’t have to read and write to disk making it much faster.

I read that you reinstalled macOS but I was asking specifically if you worked from a clean install by creating a new user without doing a migration from a previous install.

 

[white7561]

"Sleep" in MacOS equals "hibernate", there are just multiple modes. "25" means that RAM will not be powered during sleep - that’s exactly what I want when my MBP is sleeping without a charger (”-b” part of the command). With the charger, it will sleep as usual.

To restore the default behavior, run “sudo pmset -b hibernatemode 3”.


I’ve reinstalled OS 3 times, 2 of them with disk volumes removal; “revived” my system using Apple Configurator 2; visited Genius Bar; had 2 useless conversations with Apple Technical Support.

I think something is wrong either with your MagSafe adapter or cable. Or the computer itself. If it's not the adapter or cable. I suggest exchanging the laptop. Since it's really weird that it's happening

 

[OZ_]

I think something is wrong either with your MagSafe adapter or cable. Or the computer itself. If it's not the adapter or cable. I suggest exchanging the laptop. Since it's really weird that it's happening

No, it's not enough reason to risk.

 

[OZ_]

Sleep and hibernate are different. As you say, hibernate writes your RAM to disk and then turns off power to memory. Sleep is much lighter in that RAM stays powered and doesn’t have to read and write to disk making it much faster.

I read that you reinstalled macOS but I was asking specifically if you worked from a clean install by creating a new user without doing a migration from a previous install.

1) No, “hibernate” and “sleep” is the same thing in macOS, there are just different modes of hibernation. Please read some manuals (pmset, for example). If you want to call “sleep” only hibernation mode 3 - that’s your personal right.

2) All installations were “clean”, I never use migration/restore tools.

 

[white7561]

No, it's not enough reason to risk.

What do you mean by its not enough reason to risk? Risk of what?

1) No, “hibernate” and “sleep” is the same thing in macOS, there are just different modes of hibernation. Please read some manuals (pmset, for example). If you want to call “sleep” only hibernation mode 3 - that’s your personal right.

Actually. Hibernation and sleep is different. Sleep means it's still running . The stuff is actually still on the ram powered on. That's why it's super duper fast to wake up. Hibernation on Macs means it's storing the ram data to the SSD. And turning of the ram that's why it's more power efficient..

Keep in mind this is based on pre M1 information. Idk if it's still the same but it should be.

 

[jdb8167]

2) All installations were “clean”, I never use migration/restore tools.

Then it almost certainly means you have a hardware problem since this problem is not being widely reported. It might just be your power adapter that has an issue.

 

[OZ_]

What do you mean by its not enough reason to risk? Risk of what?


Actually. Hibernation and sleep is different. Sleep means it's still running . The stuff is actually still on the ram powered on. That's why it's super duper fast to wake up. Hibernation on Macs means it's storing the ram data to the SSD. And turning of the ram that's why it's more power efficient..

Keep in mind this is based on pre M1 information. Idk if it's still the same but it should be.

Risk of receiving defected unit.

Actually what you call “sleep” is just one of the hibernation modes in MacOS, and I’m tired of arguing about that, it's not related to the topic.

 

[white7561]

Risk of receiving defected unit.

Actually what you call “sleep” is just one of the hibernation modes in MacOS, and I’m tired of arguing about that, it's not related to the topic.

Yes you can call it what you want. But it's still called sleep (the hibernationmode that acts as sleep) the 25 is technically hibernation mode since it does turn off the power (which is prob why your charging works again. Since if you noticed the MagSafe and type c charging restarts when it's either going from off to on or vice versa)

Anyways. I think the chances of you getting another defective unit one after another is so much smaller that it's more worth it to exchange the unit. But again it's your choice...

 

[OZ_]

Yes you can call it what you want. But it's still called sleep (the hibernationmode that acts as sleep) the 25 is technically hibernation mode since it does turn off the power (which is prob why your charging works again. Since if you noticed the MagSafe and type c charging restarts when it's either going from off to on or vice versa)

Anyways. I think the chances of you getting another defective unit one after another is so much smaller that it's more worth it to exchange the unit. But again it's your choice...

You think wrong - chances are not decreasing or increasing with every try. Every time chance is similar. It's just math.

In whole this tread, I’ve got 0 help and just advices of level “well, replace it” or “call support”. And some bs arguing from people who are too lazy to read some info before arguing.

In other words, I’m quite disappointed in the level of this forum.

If there is a way to lock a thread - please do.

 

[white7561]

You think wrong - chances are not decreasing or increasing with every try. Every time chance is similar. It's just math.

In whole this tread, I’ve got 0 help and just advices of level “well, replace it” or “call support”. And some bs arguing from people who are too lazy to read some info before arguing.

In other words, I’m quite disappointed in the level of this forum.

If there is a way to lock a thread - please do.

Lol. Tbh you have been one of the most weirdest people I've encountered in this forum . What do you expect? Your laptop is new and not working correctly. It's normal for people to think the best thing to do next. Is to exchange it. But again you seem to not want to do that.

Also you're complaining that all people's advice is to exchange it or ask support. Well you didn't say that you didn't want that advice now did you? Yet you wonder why people keep advising that to you (nothing wrong since it's the best thing to do unless you have a specific reason not to. Which again is not stated until I posted my post advising you to exchange it)

So again. Do what you want. But IMO with your attitude I don't think anyone will want to even spend some minutes helping you.

 

[jdb8167]

You think wrong - chances are not decreasing or increasing with every try. Every time chance is similar. It's just math.

In whole this tread, I’ve got 0 help and just advices of level “well, replace it” or “call support”. And some bs arguing from people who are too lazy to read some info before arguing.

In other words, I’m quite disappointed in the level of this forum.

If there is a way to lock a thread - please do.

You seem to have broken hardware. What kind of help do you expect other than take it to Apple and have it fixed/replaced under warranty?

 

[OZ_]

You seem to have broken hardware. What kind of help do you expect other than take it to Apple and have it fixed/replaced under warranty?

Yeah, and I’ve fixed that “hardware” using the software. You are very smart No advice is needed from you, thanks. I expected someone who can say something else than “replace it”. You know, engineers usually try to fix things instead of throwing them away Bye.

 

[OZ_]

Also you're complaining that all people's advice is to exchange it or ask support.

“All people” here are just 2 of you, jdb8167 and white7561 (what a coincidence of nicknamed similarity), and you’ve started posting AFTER I wrote how to fix this issue. Keep liking each others posts, you pair of professionals

 

[white7561]

“All people” here are just 2 of you, jdb8167 and white7561 (what a coincidence of nicknamed similarity), and you’ve started posting AFTER I wrote how to fix this issue. Keep liking each others posts, you pair of professionals

Oh so you're just gonna act like there isn't anyone other than us that suggested you to call apple support??

That's really strange! Your best thing you could do sense it's fairly new call Apple support and explain the strangest to them because it should be still under 90 day AppleCare period!

And for the nickname similarities. Really ? You're gonna go with that?

For the posting after you posted how to "fix" the problem. Why does it matter? It literally doesn't have anything to do with any of my replies to you.


Please. Drop this weird act. This is just plain old weird dude. This is a public forum. If you asked for help. Just be grateful that there are people trying to help you.. even if it's not the answers you wanted (which you didn't state from the first post what answers you don't want even tho it's obvious that people will suggest that) so yeh..

Edit = also. This is more of a MacBook pro problem. It's probably should be on the MacBook pro forums. Not the apple silicon forums. But you do you mate

 

[OZ_]

I should be grateful that you wrote “replace it” after I’ve posted how I fixed it? LoL, you are pathetic.

 

[white7561]

I should be grateful that you wrote “replace it” after I’ve posted how I fixed it? LoL, you are pathetic.

if by fixed it you meant found a workaround. Then you do you..

And no. I'm not saying you should be grateful after I wrote exchange it for a new unit. I'm saying you should be grateful that people even replied and tried to give you the best next step. But again, you seem to know better so you know what.. I'm done lol. I'm not gonna spend more time replying to a troll like you lol.

Every forum always have people like you lol. Sorry but you're no longer worth my time... I hope you are smart enough to understand that

 

[OZ_]

Yeah, you brought so much good content to this topic, you are full of wisdom. Bye already.

 

[OZ_]

Sorry for bumping up an old thread, but just in case if someone else will look for information about the same issue:

the issue was in the cable. 50€ for cable replacement and the issue is completely gone