I have no idea how, as the color profile remains the same, but whenever I close the lid on my MacBook, the external monitor changes to a blue tint. I've tried changing the monitor's settings, as well as ensuring the right color profile is on.

The way I am setup, my MBP (2020) does not face me. I use it in clamshell mode, but it gets really hot, much hotter than when the lid is open. If the lid is open though, I lose performance because it has to run another screen. I also lose my cursor when it accidentally goes onto the screen I can't see, and is annoying when a window decides to open in the screen I can't see. Is there a way, either software or hardware, to fool the MBP into thinking the lid is closed?

I've had this problem since I first bought the Macbook, and I'm still having this problem after messing around with certain settings. I'm running macOS 12.5 (Monterey), a 14-inch 2021 model, with the Apple M1 Pro chip: I have a wide AOC monitor, connected to my laptop via HDMI: I disabled the power management options that would turn the display off – I set it to never. I also tried setting it to never, even when the macbook is unplugged and plugged. Whenever I connect my laptop to the monitor and close the lid, the laptop locks and the monitor provides a "No signal" message. I also wiggle the mouse, and press keys on the keyboard in an attempt to wake the device, yet nothing seems to work.

How can one configure MacOS (10.8 or higher) to automatically and immediately call a user-designated script (probably a bash script) upon the user closing the display lid of a MacBook Air or Pro? Details. I want to do this because in some scenarios my MacBook Air 2013 running 10.8.5 does not immediately sleep/lock the screen upon lid close (possibly because a VPN client is trying to open a connection). As such, I want the system to immediately execute a script which calls [this screen-saving-and-locking procedure](https://apple.stackexchange.com/a/80061/13179) upon lid close. However, I don't know how to call scripts upon display-lid closing.

Monitor: HP Z24n G2 Display MacBook Air M2 running Sequoia 15.2 (issue was present in previous sequoia versions) USB-C hub: UGREEN Revodok Pro 313 Monitor-hub connection method: HDMI to HDMI MacBook power source: MagSafe cable connected to a 3-port, 65W Anker brick. Doesn't go through the hub. Issue description: the monitor randomly disconnects from the clamshell MacBook as if the HDMI cable was disconnected. The issue can sometimes be solved by key presses, mouse clicks, cable disconnections, but not always. The only sure fix is to open the MacBook lid and the monitor will reconnect. This is quite inconvenient, as I was considering buying a laptop shelf to tuck it under my desk. Issue was also present with an older DELL monitor I used, paired with the same hub and peripherals, but with a USB-C to VGA cable. I haven't managed to reproduce the issue nor fix it. The power brick, which I use to charge both my MacBook and my phone (fast-charging disabled) forwards 45W to the MacBook if both devices are connected to it. I will now charge my phone elsewhere to determine if it's a power issue, but I believe not, as it's a recurrent issue and my phone isn't always charging. I cannot yet test if the issue lies in the hub, as they're quite the expensive item to buy for the sake of troubleshooting. Important note: this happens during active use, usually when opening apps and minimised windows or toggling full-screen. Any known fixes for this? Browsing forums didn't provide one that took an exact root cause into consideration.

Since having switched to Apple Silicon, or rather a display with the notch, I'm occasionally experiencing an incorrectly sized Menu bar on the primary display. It looks like this: I think it happens in the following scenario: I'm using the MacBook in clamshell mode (closed + external monitors). Then I unplug the monitors while the system is sleeping. And then I open the MacBook, and at that point the Menu bar is rendered incorrectly. For apps with lots of items in the Menu bar, the reserved placeholder for the notch is also in the wrong place. See the image below; the placeholder is between File and Edit, while Git, Window and Help are in fact not visible as they are rendered under the notch. Another example: This is probably yet another bug in macOS, so while we wait for a bugfix, I'm trying to find a workaround. I've tried killall Dock, which re-renders the Menu bar, but still incorrectly sized. Reconnecting the external displays while awake/sleeping doesn't fix the problem, only a reboot seems to work. I'd rather find a less disruptive workaround. What can I do when this happens? I'm currently on macOS 15.0, but this also happened with 14.x (various minor versions).

So I saw a lots of old discussion on this topic, but I'm trying to find out an actual solution that still works on Mojave / Catalina, **without the use of external monitor/keyboard/mouse/with power adapter**. When looking up Amphetamine, they claimed that you can only do it when the 4 criteria are met, and cannot overridden it. But on the other hands, Anti Sleep provide the feature in their pro version... So, which one gets the real deal ? Is Anti Sleep lying about it or Amphetamine (and all other caffeine app on the appStore) is out of date ? I also heard about InsomniaX and built-in caffeine but it's really not user friendly, and appear not to be supported anymore...

I have an old Macbook Pro with Big Sur (11.7.10) that I use to execute an Applescript that typically runs for 1-2 hours. The first thing I do in this script is set caffeinatePid to do shell script "caffeinate -d > /dev/null 2>&1 & echo $!" to prevent the computer from going to sleep (and to be able to kill the caffeinate process at the end of the script) but it doesn't work. The screen sleeps after the set time (3 minutes) and this pauses the execution of the script. The only workaround I have found so far is to connect to the machine using Screen Sharing. Why does caffeinate not work? How should I use it in this situation?

I have an M1 Macbook Pro (2020) running Ventura. Most of the time I use it in clamshell mode. I can easily wake it from sleep the using the external wireless keyboard (I hear the fans come on, the external drive flashes, there is a 'dong' sound when I press Option+Cmd - so the mac is definitely awake). But very often the display just says no signal and goes to sleep. It is very inconvenient to take the mbp out of it's stand and open up the display to log in - which does turn the external monitor on. The only trick that works is to unplug the power lead from the mac for several seconds and then plug it back in. The technical details of my set up are: 1. The mac is connected to an Anker USB C hub. 2. The hub connects via HDMI to an HDMI switch (which also has an input for a Windows laptop where things work fine). 3. The HDMI switch connects to an external monitor via HDMI.

One of the requirements to use clamshell mode is to have the power adapter plugged in. Is their any file modification or app that will work around this? Like to switch throughout the day from a sit down desk to stand up and bringing the power adapter back and forth, is becoming more of a hassle.

I got my MacBook M2 to work in closed-clamshell mode without AC power using the pmset commands. However, if I intentionally put the MacBook to sleep (using hot corners), I cannot seem to wake it up again. I have to necessarily open the lid to wake it up again. When connected to AC power, pressing a key on the keyboard or moving the mouse wakes it up. Note, that I tried Amphetamine and the Closed-display mode is greyed out. How do I wake it up from sleep in the clamshell mode? Any thoughts/solutions would be highly appreciated. **EDIT 1:** Here are the commands I used:

sudo pmset -a sleep 0
sudo pmset -a hibernatemode 0
sudo pmset -a disablesleep 1

The MacBook Pro is a 2022 model - Apple M2 processor, 16GB RAM and 1TB HDD. The monitor is connected via HDMI, keyboard via bluetooth and Mouse via a wireless receiver.

Recently I bought Philips 272E1GAEZ display. Important Edit: if I first power up macbook without external display, then close the lid and connect power and display - no lags whatsoever on the external display. The problem only when I first connect external display, then power up macbook, then open the lid to enter password (bluetooth keyboard not working on authentication screen), close the lid and use display with clamshell mode - lags happen. I read reviews about 144hz and wanted to try it out with my Macbook Pro 2019, 16". I connected it via HDMI. I tried Display Port -> Type C adapter at first, which gave me 165hz and Adaptive Sync, but after 1 hour of usage screen started flickering, switching off for 1 second (basically display port became unusable, no matter the refresh rate, after restarting macos 1 time I ended up with 100% CPU usage with fseventsd and unusable ANYTHING, lags were everywhere, imagine 3FPS, I don't know what was that but after restart they disappeared). So now I use 120hz and 1080p resolution via HDMI port. (changing refresh rate does not affect problem) My Macbook has 2 video cards: AMD Radeon Pro 5300M 4 GB Intel UHD Graphics 630 1536 MB It seems that any program that requires somewhat powerful video card uses my Radeon Pro video card has problems with lags. The problem also with anything that I assume has extensive graphics card uses. Browser tabs, when hovering them, some menus in settings on macOS, scrolling lags so much. I noticed the problems after I connected external display first time with display port (not HDMI) and I had like SUPER SMOOTH everything, even Blender. Of course, without external display I have no such lags and this is what shocks me the most. I mean I have 1080p resolution on external display and retina resolution on macbook - why would anything lag on such low resolution on external display? Now, if I connect Display, I have heavy lags on basically any program that requires good graphics card. If it matters, Macbook in vertical position, back side on the bottom, clamshell mode. Here are my settings for display:

I am trying use my macbook with an external device in Clamshell Mode without the power adapter. Hence, I am following this tutorial . The author gives, first, a GUI approach. Then, he suggests the following commands on terminal:

pmset -g | grep hibernatemode

sudo pmset -a sleep 0
sudo pmset -a hibernatemode 0
sudo pmset -a disablesleep 1

sudo pmset -a sleep 1
sudo pmset -a hibernatemode 
sudo pmset -a disablesleep 0

The point that intrigues me the most is that before giving the instructions, he says: > Note: I have not tested these commands because Apple recommends not changing the hibernatemode using the pmset command, and these commands do just that. However, these commands will disable your laptop’s sleep on lid-close trigger, so they should also solve the problem of being unable to use your laptop in clamshell mode without the power adapter. That said, use them at your own risk. Hence, my doubts are: 1. Why does Apple not recommend tweaking hibernate-mode with the pmset command? 2. What could go wrong? Why is it dangerous? 3. If something bad happens, is it possible to revert the problem? And how to do it?

MacBook Air M1 won't connect to the external display (MSI MAG2732) in clamshell mode (power adapter connected to the device with lid off) after updating to macOS Ventura on October 24th (Day of release). I tried to use my updated iPad Air M1 as an external display 2, alongside the monitor as an external display 1. Turns out - after closing the lid, both of the display works! But as soon as the iPad is disconnected, the monitor loses signal (HDMI to USB-c cable). I tried clearing/removing NVRAM, caches, and windowserver.plist files inside ~/Library/Preferences (couldn't find windowserver files, so any help on this would be highly appreciated!), and none of them worked. I also installed the macOS in safe mode again, changing the display refresh rate to default in both main and external displays. At this point, none of them seemed to work, and the only way I can use the external monitor is by keeping the lid on. I also made sure that the system isn't falling asleep as soon as I turn the lid off. The system is not asleep when I close the lid, the application seems to be working and the external display also seems to be working normally, but no signals! Update: External monitor seems to work with the lid closed in safe mode. It gets back to not working when restarted.

I'm currently using the aldente app and Belkin dock pro3, but I don't know what's wrong. I need help 🙏 I'm currently using smb and sftp. So, I checked if there was an incoming signal with the tcpdump command, but there was no problem. Below is the output of

pmset -g log | grep "Entering Sleep state"

in text and as a screenshot:

2022-10-23 01:10:29 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 923 secs
2022-10-23 02:26:31 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 196 secs
2022-10-23 02:30:47 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 940 secs
2022-10-23 02:47:13 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 6 secs
2022-10-23 03:47:48 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 934 secs
2022-10-23 04:04:07 +0900 Sleep               	Entering Sleep state due to 'Sleep Service Back to Sleep':TCPKeepAlive=active Using AC (Charge:63%) 282 secs
2022-10-23 05:35:15 +0900 Sleep               	Entering Sleep state due to 'Notification Wake Back to Sleep':TCPKeepAlive=active Using AC (Charge:63%) 8 secs
2022-10-23 05:36:08 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 911 secs
2022-10-23 05:52:04 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 6 secs
2022-10-23 05:52:55 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 960 secs
2022-10-23 06:10:41 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 927 secs
2022-10-23 07:26:33 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 234 secs
2022-10-23 07:31:27 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 942 secs
2022-10-23 07:47:54 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 922 secs
2022-10-23 09:03:57 +0900 Sleep               	Entering Sleep state due to 'Sleep Service Back to Sleep':TCPKeepAlive=active Using AC (Charge:63%) 949 secs
2022-10-23 09:20:31 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 977 secs
2022-10-23 09:37:48 +0900 Sleep               	Entering Sleep state due to 'Sleep Service Back to Sleep':TCPKeepAlive=active Using AC (Charge:63%) 1054 secs
2022-10-23 10:55:47 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 967 secs
2022-10-23 11:12:39 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 819 secs
2022-10-23 11:27:03 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 945 secs
2022-10-23 12:44:08 +0900 Sleep               	Entering Sleep state due to 'Sleep Service Back to Sleep':TCPKeepAlive=active Using AC (Charge:63%) 947 secs
2022-10-23 13:00:40 +0900 Sleep               	Entering Sleep state due to 'Sleep Service Back to Sleep':TCPKeepAlive=active Using AC (Charge:63%) 980 secs
2022-10-23 13:17:45 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 1045 secs
2022-10-23 14:35:25 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 959 secs
2022-10-23 14:52:09 +0900 Sleep               	Entering Sleep state due to 'Sleep Service Back to Sleep':TCPKeepAlive=active Using AC (Charge:63%) 31 secs
2022-10-23 14:53:25 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 972 secs
2022-10-23 16:10:58 +0900 Sleep               	Entering Sleep state due to 'Sleep Service Back to Sleep':TCPKeepAlive=active Using AC (Charge:63%) 266 secs
2022-10-23 16:16:09 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 650 secs
2022-10-23 16:27:44 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 332 secs
2022-10-23 21:12:49 +0900 Sleep               	Entering Sleep state due to 'Clamshell Sleep':TCPKeepAlive=active Using AC (Charge:63%) 6 secs
2022-10-23 21:13:40 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 7 secs
2022-10-23 21:14:32 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 198 secs
2022-10-23 21:18:35 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 322 secs
2022-10-23 21:24:42 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 644 secs
2022-10-23 21:42:03 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 104 secs
2022-10-23 21:44:33 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 39 secs
2022-10-23 21:45:58 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 20 secs
2022-10-23 21:47:03 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 13 secs
2022-10-23 21:48:01 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 156 secs
2022-10-23 21:51:22 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 205 secs
2022-10-23 21:55:32 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 634 secs
2022-10-23 22:18:44 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 904 secs
2022-10-23 22:34:48 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 543 secs
2022-10-23 22:44:36 +0900 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:63%) 59 secs

[](https://i.sstatic.net/V0PIb.jpg)

I have a MacBook Pro (13-inch, M1, 2020) in clamshell mode, connected to a 4k monitor and power through a USB-C hub. If I use only the external screen, with the lid closed, wifi becomes unusable. As soon as I open the lid (both screens on, mirrored) the problem goes away. In closed-clamshell mode: moe@Moes-MBP ~> ping google.com PING google.com (142.250.217.110): 56 data bytes Request timeout for icmp_seq 0 64 bytes from 142.250.217.110: icmp_seq=1 ttl=117 time=254.020 ms 64 bytes from 142.250.217.110: icmp_seq=2 ttl=117 time=206.079 ms Request timeout for icmp_seq 3 64 bytes from 142.250.217.110: icmp_seq=3 ttl=117 time=1207.436 ms 64 bytes from 142.250.217.110: icmp_seq=4 ttl=117 time=214.452 ms 64 bytes from 142.250.217.110: icmp_seq=5 ttl=117 time=224.992 ms 64 bytes from 142.250.217.110: icmp_seq=6 ttl=117 time=230.388 ms ^C --- google.com ping statistics --- 8 packets transmitted, 6 packets received, 25.0% packet loss round-trip min/avg/max/stddev = 206.079/389.561/1207.436/366.069 ms Immediately after opening the lid: moe@Moes-MBP ~> ping google.com PING google.com (142.250.217.110): 56 data bytes 64 bytes from 142.250.217.110: icmp_seq=0 ttl=117 time=17.263 ms 64 bytes from 142.250.217.110: icmp_seq=1 ttl=117 time=17.297 ms 64 bytes from 142.250.217.110: icmp_seq=2 ttl=117 time=44.884 ms 64 bytes from 142.250.217.110: icmp_seq=3 ttl=117 time=13.996 ms 64 bytes from 142.250.217.110: icmp_seq=4 ttl=117 time=19.013 ms 64 bytes from 142.250.217.110: icmp_seq=5 ttl=117 time=22.815 ms ^C --- google.com ping statistics --- 6 packets transmitted, 6 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 13.996/22.545/44.884/10.329 ms What could be causing this?

I recently got a dock / hub for my MacBook. A single USB-C connection provides power and connects it to my external monitor, keyboard, and mouse. When I'm actually using the computer, I always have the lid open. Whenever the lid is closed, I want it to sleep. But it doesn't. Even if I explicitly click Apple -> Sleep, it will wake if the mouse is jiggled slightly, so I find the monitors turning on when I'm not using the computer. Is there a setting for "remain asleep until the lid is opened"?

I'm running two external displays from a MacBook Pro 16 inch in closed clamshell mode. I notice however that the internal display is still on as well: it is pictured as a third screen in System Preferences > Displays, and when I open the lid ever so slightly, I can see it. When I use the laptop without external displays, the display turns off as it should when closing the lid. I've tried to reset SMC and NVRAM but to no avail.

I have a mid-2015, 15 inch MacBook Pro, connected to a Dell P2715Q with a Display Port to mini-DP cable. With the lid open, I get both displays working. I used to be able to close the lid and it would switch to just using the external monitor, but I have changed something in the settings so that when it is closed, the display is black. I am using SwitchResX, to change the resolution, and I think I changed the colour from Millions to Billions, which broke it. I now can't change it back as it is only broken when the lid is closed. I want to have just the single monitor. How can I change the settings back to normal so that it works properly? The MacBook Pro is plugged in to mains power, and is connected a USB Keyboard and Bluetooth Mouse. I use the exact same setup at work, with identical Keyboard and Mouse, but a different monitor, and that works fine. It appears that the configuration for the monitor in open clamshell mode is different to that in closed clamshell mode, and I'm trying to find out how to re-configure the closed clamshell mode when it does not display anything with it closed.

At my desk I use my intel CPU 11" MacBook Air with the lid closed, an external monitor with no camera, and a headset with microphone. After updating to Mojave from Sierra, I can no longer use FaceTime Audio in that configuration. I'm looking for a way to stop FaceTime from waiting for video from the inactive FaceTime camera. Under Sierra, I could open the FaceTime app, and place or receive FaceTime Audio calls normally. Now, under Mojave, when I open FaceTime, the window is black, and after a minute or so, I get an alert saying "No Video - FaceTime has not received any video from the connected camera. Restarting the computer may fix this issue." I'm not able to place calls, and restarting doesn't help. I'm still able to receive calls. I can plug in an old USB webcam, but I'd rather not, because I don't want video, it seems to use a significant amount of CPU, uses a USB port, etc. I might be willing to change my OS to Catalina if that would solve it, but my computer doesn't support any OS newer than that. Are there solutions I can use to make this work without having to keep the lid open or plug in a camera?