AppHouseKitchen / AlDente-Charge-Limiter

macOS menubar tool to set Charge Limits and prolong battery lifespan
https://apphousekitchen.com/
Other
7.63k stars 286 forks source link

Display does not turn off when lid is closed when "Disable Sleep until Charge Limit" is enabled on Apple Silicon MacBooks #1161

Closed alexanderhorner closed 2 months ago

alexanderhorner commented 4 months ago

Describe the bug The Display does not turn off once the lid is closed when the Macbook is charging and "Disable Sleep until Charge Limit" is enabled.

To Reproduce Steps to reproduce the behavior:

  1. Charge MacBook (Charge Limit must not be reached)
  2. Enable "Disable Sleep until Charge Limit"
  3. Close lid slowly

Expected behavior The internal display should turn off once the lid is closed.

MacBook (please complete the following information):

MatthiasKerbl commented 4 months ago

Hi @alexanderhorner,

Thank you for reporting this issue. We will try to do something about it in one of the upcoming updates.

Best, Matthias

nathang21 commented 4 months ago

+1 i'm having the same issue, see attached for debug file, happy to reproduce or provide more details if needed. aldentepro-debug-2024-02-19-21:55:01.pasta.zip

What i've noticed, is my Macbook struggles to charge while in clamshell mode when my display is on, but when the display sleeps, or I switch to my other device via my KVM switch, then it will adequately charge. This is WAI, and was the status quo before I started using AlDente. Note: This is due to the KVM switch which can power 2 devices via PD at once, can only supply up to ~56W at once to a single laptop, which is plenty for sustained use, and will also charge the laptop when either A) the display is off or B) i'm using the 2nd device. However with AlDente, option A no longer works.

However WITH AlDente, if I walk away, even though sleep is disabled via "Disable Sleep until Charge Limit", my display will never turn off, and thus the Mac won't charge sufficiently to ever reach the charge limit for it to actually sleep. I've been hovering around 29% all day today, despite leaving the house for a few hours and not using my device for 6+ hours.


Edit: I tested option B) above overnight by leaving my laptop plugged in, but with the dock switched to the other KVM device, and my display was physically off. However, it seemed that my mac was still attempting to drive the display (or at least using sufficient power) such that overnight it actually lost 1% and was at 28%. Thus I think tl;dr I don't have I have any workarounds other than disabling AlDente to let the device sleep.


Edit 2: Looks like i had a rogue process consuming a ton of CPU, hence the excess battery drain/lack of charging. So I think back to the root issue, is the display will not turn off until charge limit is reached. Apologies for any confusion.

dreit-p commented 3 months ago

Still find my laptop overheated with working display in closed state... I hope that the author is working on a fix for the bug, because at the moment this program is harming, not helping.

MatthiasKerbl commented 3 months ago

Still find my laptop overheated with working display in closed state... I hope that the author is working on a fix for the bug, because at the moment this program is harming, not helping.

Hi @dreit-p,

We understand your frustration. This issue will become a priority and we will try to do something about it in one of the upcoming updates.

Best, Matthias

dreit-p commented 3 months ago

Still find my laptop overheated with working display in closed state... I hope that the author is working on a fix for the bug, because at the moment this program is harming, not helping.

Hi @dreit-p,

We understand your frustration. This issue will become a priority and we will try to do something about it in one of the upcoming updates.

Best, Matthias

Thank you Matthias! I'll be looking forward to it :)

MatthiasKerbl commented 2 months ago

Hi everyone,

I have just noticed that there is already an issue open about this bug. Therefore, I will close this issue and will give updates about it in the other issue #998.

Best, Matthias