Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with Closing the display #1

Open
AuricX opened this issue Dec 21, 2023 · 4 comments
Open

Issue with Closing the display #1

AuricX opened this issue Dec 21, 2023 · 4 comments

Comments

@AuricX
Copy link

AuricX commented Dec 21, 2023

In versions of Amphetamine prior to 5.3, I would run Amphetamine and close my laptop's lid and the display would turn off but the laptop wouldn't go to sleep which was expected.

After updating, closing the lid doesn't turn off the display anymore which is draining the battery. I have Closed-Display mode disabled, and if enable it, my Mac just goes to sleep when the lid is closed.

@x74353
Copy link
Owner

x74353 commented Dec 21, 2023

In 5.3, I had added a line of code to force the display to sleep when the lid is closed. I did this because in my testing the display did not ever sleep when using the closed-display mode script, even if you had enabled Allow Display Sleep. I was worried about screen burn-in. However, I later realized that the display never sleep behavior was occurring because I'm an idiot.

In the original closed-display mode script (included in 5.3) I was setting the display to never sleep. This was a mistake. The original closed display mode script should have only keep the Mac awake and the display sleep behavior should have been handled by the menu checkbox's state (on/off).

In 5.3.1, I removed the line of code that forces the display to sleep when the lid is closed and the new Power Protect script does not make changes to display sleep behavior. This is the way things worked prior to 5.3.

So, in 5.3.1+, if you check the Allow Display Sleep box, then closed the lid, your Mac's display(s) (internal/external) should sleep after X minutes as defined in macOS System Settings. If you have Allow Display Sleep unchecked, the display(s) should stay on even in closed-display mode.

If you're finding that your display(s) won't sleep even with Allow Display Sleep enabled, double check your macOS System Settings.

ScreenShot 2023-12-21 at 13 57 01

@AuricX
Copy link
Author

AuricX commented Jan 25, 2024

Display now turns off normally after 1 minute, thank you.
However, is there a way to make the display turn off immediately? The minimum I can go is 1 minute.

EDIT: A new problem faces me that when I am watching YouTube (which stops the screen sleeping) the display never turns off even when it's closed. If I can know the original command to force display sleep, that'd be great.

@Timsonrobl
Copy link

Timsonrobl commented Oct 3, 2024

Somehow prior to last week the display would turn off immediately upon closing the lid with "Allow display sleep" - on, and "Allow system sleep with closed lid" - off. Which I always thought is the desired behaviour since burning display backlight with closed lid makes no sense, wastes battery and overheats the device (especially fanless macbook airs).
Now I encountered several cases when my display won't turn off with this settings for hours, and it never turns off the display immediately upon closing the lid. Probably happened after macOS 14.6.1 update.

If that was not the intended behaviour all along (which I think is weird since the is much more use cases when you want background processes running with closed lid rather than having closed display on) it would be great at least to have an option to do so again.

@zzJinux
Copy link

zzJinux commented Oct 6, 2024

Same here. I can't find a way to make the display off immediately as soon as the lid is closed. As a temporary workaround, I manually force the display to turn off with sudo pmset displaysleepnow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants