Enable Lid Closed action delay

When I try to check the "Enable Lid Closed action delay" checkbox in Power Manager, I receive a dialog box instructing me to:
Please enable "Active System Protection" before enabling Lid Closed action delay
However, the Active System Protection checkbox is greyed-out and cannot be selected. Is this because my X300 has a solid-state HDD? If so, is there a way to use the Enable Lid Closed action delay functionality?
Thanks.

This terminal command will disable lid sleep, a 0 is off, 1 is on.
Disable Lid Sleep
sudo pmset -a lidwake 0
Enable Lid Sleep
sudo pmset -a lidwake 1
Check Staus, look for the Lid Wake value
pmset -g
http://www.mactricksandtips.com/2008/06/changing-sleep-setting-on-mac-laptop.htm l

Similar Messages

Lid closed actions

Is there a way to set up my Mac to do no action when the lid is closed? In other words I want to be able to close the lid and have the laptop continue to do whatever it is currently doing, such as continue to play music with iTunes.

This terminal command will disable lid sleep, a 0 is off, 1 is on.
Disable Lid Sleep
sudo pmset -a lidwake 0
Enable Lid Sleep
sudo pmset -a lidwake 1
Check Staus, look for the Lid Wake value
pmset -g
http://www.mactricksandtips.com/2008/06/changing-sleep-setting-on-mac-laptop.htm l

Gnome3: Cannot set laptop lid close action

I've checked the lid closing sensor with watch /proc/acpi/button/lid/LID/state and the status changes without problems, but i can't set the lid closing action in gnome-tweak-tool or under power options. The laptop suspends only when an external monitor is not connected, i want to change it so it always suspends when the lid is closed.
How can I fix this?
Screenshots
power options
gnome-tweak-tool
Last edited by klingt.net (2014-03-19 20:28:05)

Seems to be a bug in gnome, gnome-tweak-tool outputs the following messages:
INFO : GSettings missing key org.gnome.settings-daemon.plugins.power (key lid-close-battery-action)
INFO : GSettings missing key org.gnome.settings-daemon.plugins.power (key lid-close-ac-action)
INFO : GSettings missing key org.gnome.settings-daemon.plugins.power (key lid-close-suspend-with-external-monitor)
I added the keys manually to the schema but gnome-tweak-tool show this error when i try to start it with the new keys:
GLib-GIO-ERROR **: Settings schema 'org.gnome.settings-daemon.plugins.power' does not contain a key named 'lid-close-battery-action'
There are more people having a similar problem.
Last edited by klingt.net (2014-03-23 10:12:03)

Dell Inspiron 9400 not suspending on lid closing

I am currently running arch linux 64 bit with LXDE. I aslo have loaded modules acpid, howvever when I close the laptop lid it does not suspend to ram. After using google, I did not doscover any solution that worked for me. According to one site, I added tthe following code to /etc/acpi/events/lid
event=button/lid
action=/etc/acpi/actions/lid.sh
/etc/acpi/actions/lid.sh contains:
#!/bin/bash
sleep &
sudo /usr/sbin/pm-suspend
acpid is runnig, however, when the lid is closed and acpi_listern is running there is printed to the terminal.
Would appreciate any help that help me solve this problem.

I tried that first, but it did not work.
/etc/acpi/handler.sh contains:
#!/bin/sh
# Default acpi script that takes an entry for all actions
minspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq`
maxspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq`
setspeed="/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed"
set $*
case "$1" in
button/power)
#echo "PowerButton pressed!">/dev/tty5
case "$2" in
PBTN|PWRF) logger "PowerButton pressed: $2" ;;
*) logger "ACPI action undefined: $2" ;;
esac
button/sleep)
case "$2" in
SLPB|SBTN) echo -n mem >/sys/power/state ;;
*) logger "ACPI action undefined: $2" ;;
esac
ac_adapter)
case "$2" in
AC|ACAD|ADP0)
case "$4" in
00000000)
echo -n $minspeed >$setspeed
#/etc/laptop-mode/laptop-mode start
00000001)
echo -n $maxspeed >$setspeed
#/etc/laptop-mode/laptop-mode stop
esac
*) logger "ACPI action undefined: $2" ;;
esac
battery)
case "$2" in
BAT0)
case "$4" in
00000000) #echo "offline" >/dev/tty5
00000001) #echo "online" >/dev/tty5
esac
CPU0)
*) logger "ACPI action undefined: $2" ;;
esac
button/lid)
case "$3" in
close)
#echo "LID closed!">/dev/tty5
sudo /usr/sbin/pm-suspend
logger -s "ACPI lid closed";
open)
#echo "LID opened!">/dev/tty5
logger -s "ACPI lid opened"
esac
logger "ACPI group/action undefined: $1 / $2"
esac
According to one site I give member of the power group the ability to shutdown and restart the system without the requiring a password.
/etc/sudoers contains:
## sudoers file.
## This file MUST be edited with the 'visudo' command as root.
## Failure to use 'visudo' may result in syntax or file permission errors
## that prevent sudo from running.
## See the sudoers man page for the details on how to write a sudoers file.
## Host alias specification
## Groups of machines. These may include host names (optionally with wildcards),
## IP addresses, network numbers or netgroups.
# Host_Alias WEBSERVERS = www1, www2, www3
## User alias specification
## Groups of users. These may consist of user names, uids, Unix groups,
## or netgroups.
# User_Alias ADMINS = millert, dowdy, mikef
## Cmnd alias specification
## Groups of commands. Often used to group related commands together.
# Cmnd_Alias PROCESSES = /usr/bin/nice, /bin/kill, /usr/bin/renice, \
# /usr/bin/pkill, /usr/bin/top
## Defaults specification
## You may wish to keep some of the following environment variables
## when running commands via sudo.
## Locale settings
# Defaults env_keep += "LANG LANGUAGE LINGUAS LC_* _XKB_CHARSET"
## Run X applications through sudo; HOME is used to find the
## .Xauthority file. Note that other programs use HOME to find
## configuration files and this may lead to privilege escalation!
# Defaults env_keep += "HOME"
## X11 resource path settings
# Defaults env_keep += "XAPPLRESDIR XFILESEARCHPATH XUSERFILESEARCHPATH"
## Desktop path settings
# Defaults env_keep += "QTDIR KDEDIR"
## Allow sudo-run commands to inherit the callers' ConsoleKit session
# Defaults env_keep += "XDG_SESSION_COOKIE"
## Uncomment to enable special input methods. Care should be taken as
## this may allow users to subvert the command being run via sudo.
# Defaults env_keep += "XMODIFIERS GTK_IM_MODULE QT_IM_MODULE QT_IM_SWITCHER"
## Uncomment to enable logging of a command's output, except for
## sudoreplay and reboot. Use sudoreplay to play back logged sessions.
# Defaults log_output
# Defaults!/usr/bin/sudoreplay !log_output
# Defaults!/usr/local/bin/sudoreplay !log_output
# Defaults!/sbin/reboot !log_output
## Runas alias specification
## User privilege specification
root ALL=(ALL) ALL
## Uncomment to allow members of group wheel to execute any command
%wheel ALL=(ALL) ALL
## Same thing without a password
# %wheel ALL=(ALL) NOPASSWD: ALL
## Uncomment to allow members of group sudo to execute any command
# %sudo ALL=(ALL) ALL
## Uncomment to allow any user to run sudo if they know the password
## of the user they are running the command as (root by default).
# Defaults targetpw # Ask for the password of the target user
# ALL ALL=(ALL) ALL # WARNING: only use this together with 'Defaults targetpw'
## Read drop-in files from /etc/sudoers.d
## (the '#' here does not indicate a comment)
#includedir /etc/sudoers.d
%power ALL=(ALL) NOPASSWD: /usr/sbin/pm-hibernate
%power ALL=(ALL) NOPASSWD: /usr/sbin/pm-suspend
%power ALL=(ALL) NOPASSWD: /sbin/halt
%power ALL=(ALL) NOPASSWD: /sbin/reboot
%wheel ALL=(ALL) NOPASSWD: /usr/bin/yaourt -Sy
%jupiter ALL=NOPASSWD: /usr/lib/jupiter/scripts/bluetooth, /usr/lib/jupiter/scripts/camera, /usr/lib/jupiter/scripts/cpu-control, /usr/lib/jupiter/scripts/resolutions, /usr/lib/jupiter/scripts/rotate, /usr/lib/jupiter/scripts/touchpad, /usr/lib/jupiter/scripts/vga-out, /usr/lib/jupiter/scripts/wifi
The pm-suspend does work, I can suspend from lxde menu and the suspend button but not when the lid is closed.
Last edited by amcollie (2012-04-16 13:15:36)

How do I use my macbook pro lid closed

How do I use my macbook pro lid closed?

Well what i'm trying to do is keep file sharing on while macBook is closed so i can access files through "newtwok" (Back to my mac) with my imac...
Ideally i would then control my macBook with screen sharing on my imac while the MacBook is stored behind my iMac...
Somehow it worked before but now it stopped...and everytime i close the lid ..mac book pro goes black screen and completly disconnects from the newtwork...
Everything works fine with lid open..
I am trying to do this because i have a new imac with thunderbold and an older macbook pro with mini display port..and as you might already know...you canot connect these thow devices using thunderbolt cable...which really *****....there is also no adaport enabling this...and i really dont need to buy another mac book that just has one more hole in it >.<
Anyway..hope there is a solution somewhere to keep file sharing going while lid down..
regards remo

Thinkpad X220: bad wlan connection when docked and lid closed

Dear forum
I use a Lenovo ThinkPad X220. I have no trouble with the wlan connection when i use the notebook alone. The wlan connection is also stable when i use the notebook plugged in the dockingstation with the lid open. But when I use the notebook plugged in the dockingstation with the lid closed my wlan connection drops regularely to about 2 Mbps and gets very unstable.
The ThinkPad uses the Intel Centrino Advanced-N 6205 wlan network controller:
$ lspci | grep 6205
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)
The network controller uses the iwlwifi driver, that comes with the current linux-firmware package:
$ pacman -Ss linux-firmware
core/linux-firmware 20150206.17657c3-1 [Installiert]
Firmware files for Linux
I didn't change any options of the kernel module, everything runs in default mode:
$ modinfo -p iwlwifi
swcrypto:using crypto in software (default 0 [hardware]) (int)
11n_disable:disable 11n functionality, bitmap: 1: full, 2: disable agg TX, 4: disable agg RX, 8 enable agg TX (uint)
amsdu_size_8K:enable 8K amsdu size (default 0) (int)
fw_restart:restart firmware in case of error (default true) (bool)
antenna_coupling:specify antenna coupling in dB (default: 0 dB) (int)
wd_disable:Disable stuck queue watchdog timer 0=system default, 1=disable (default: 1) (int)
nvm_file:NVM file name (charp)
uapsd_disable:disable U-APSD functionality (default: Y) (bool)
bt_coex_active:enable wifi/bt co-exist (default: enable) (bool)
led_mode:0=system default, 1=On(RF On)/Off(RF Off), 2=blinking, 3=Off (default: 0) (int)
power_save:enable WiFi power management (default: disable) (bool)
power_level:default power save level (range from 1 - 5, default: 1) (int)
fw_monitor:firmware monitor - to debug FW (default: false - needs lots of memory) (bool)
At first I thought, the problem could be caused by the KDE power saving settings. I changed the settings, so nothing happens when I close the lid (no hibbernation or screen lock or something like that), but without success (the wlan connection is still unstable under the described circumstances).
Also dmesg shows nothing that points out a problem (as far as I can see):
$ dmesg | grep iwlwifi
[ 19.688522] iwlwifi 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 19.688679] iwlwifi 0000:03:00.0: irq 31 for MSI/MSI-X
[ 19.696095] iwlwifi 0000:03:00.0: loaded firmware version 18.168.6.1 op_mode iwldvm
[ 19.718023] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
[ 19.718027] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[ 19.718028] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
[ 19.718029] iwlwifi 0000:03:00.0: Detected Intel(R) Centrino(R) Advanced-N 6205 AGN, REV=0xB0
[ 19.718145] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
[ 19.753757] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0
[ 20.128443] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
[ 20.128652] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[ 20.403905] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
[ 20.404212] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[ 68.922975] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
[ 68.923192] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
So I have no idea where this strange behaviour comes from (only wild guesses: buildfactor, antenna orientation,...).
Any help would be really appreciated.

hmmm...
how about checking both your wired and wireless nic drivers in device manager to make sure that the "allow computer to turn off this device to save power" checkbox on the power management tab is deselected.
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество
Community Resources: Participation Rules • Images in posts • Search (Advanced) • Private Messaging
PM requests for individual support are not answered. If a post solves your issue, please mark it so.
X1C3 Helix X220 X301 X200T T61p T60p Y3P • T520 T420 T510 T400 R400 T61 Y2P Y13
I am not a Lenovo employee.

Problem with lid closed mode

So as far as i know, to get the computer to run in lid closed mode you press f7 until you get video mirroring, the second mode i believe, close the display, then wake the computer with the external mouse or keyboard. I've done this, but almost as soon as i wake the computer, it goes back to sleep again.
How do i fix this??
Is it a problem for I'm using a windows keyboard, but i wouldn't think that could be it.

Also, if you haven't already done this, make sure that Bluetooth is enabled and that you "Allow Bluetooth devices to wake this computer" (Systpref/Bluetooth/Settings)

Running macbook pro with lid closed

Hi all,
I want to run the Macbook Pro with the lid closed, like maybe when I'm downloading a file or using it as a desktop with an external screen.
I have insomniaX, however I am concerned about heat.
The vent in the back seems to put out as much air as it does with the lip opened.
Any insight on this?
tia
edit: oh yea I have an early '09 mac book pro; 15" if it matters
Message was edited by: große geld

If you use InsomniaX, you should certainly be concerned about heat. I recommend trashing InsomniaX, because it enables you to abuse your MBP in a way that Apple intended to make impossible.
To use the machine with its display closed as it was designed to be used, follow the instructions in this article:
http://support.apple.com/kb/HT3131

Can iTunes play with lid closed?

I am a newbie, so please excuse me if this sounds like a dumb question. I just moved from Windows world (after using it for 25 years) to MacBook Pro about 4 months ago.
I am using AiportExpress to stream music from iTunes to 3 different audio system throught my home. I would like play iTunes to play the music even when my MacBook lid is closed. I can't seem to get this work. Seems like such a basic function. Is it possible to play iTunes with lid closed? What am I missing?

{quote:title=Chris CA wrote:}If Apple were to allow it with a setting and the user burned up the computer, then it would have to be covered under warranty, which it isn't.{quote}
Don't mean to argue.. but I still believe that it should be a user enabled/disabled function. I've used it on all my PCs for several years (when playing CD on Windows Media Player) and I am yet to BURN a single device
If I have to keep the MacBook open to keep running iTunes, wouldn't I run the same risk of BURNING (like you said)?
OK.. this is what I need to do...
I have all my music in iTunes. I have setup 3 AirportExpress (AirTunes) hooked up to receivers on 3 levels on my home. I'd like to play the music from iTunes (wirelessly streaming throughout the house via AirTunes) without having to keep the MacBook open. How do I do it?
I don't want to see any third party apps (e.g. Insomnia) to prevent my computer from going to sleep. I just want to accomplish what I described above. Can this be done or not?
Another question is if the iTunes is running on one of my Windows-based laptops, and I close the lid on that, iTunes (on PC) should continue to run. Right?
Any help is greatly appreciated.

Suspends only every second time when lid closed

Hello everybody, my problem is as the subject: to suspend I have to close usually the laptop lid twice.
I'm using kde, but I have also used years ago fluxbox, tweaking scripts and using laptop-mode (which is not running now). Thanks in advance for every idea where to look.
/etc/acpi$ cat handler.sh
#!/bin/sh
# Default acpi script that takes an entry for all actions
minspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq`
maxspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq`
setspeed="/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed"
set $*
case "$1" in
button/power)
case "$2" in
PBTN|PWRF)
logger "PowerButton pressed: $2"
poweroff
logger "ACPI action undefined: $2"
esac
button/sleep)
case "$2" in
SLPB|SBTN)
echo -n mem >/sys/power/state
logger "ACPI action undefined: $2"
esac
ac_adapter)
case "$2" in
AC|ACAD|ADP0)
case "$4" in
00000000)
echo -n $minspeed >$setspeed
#/etc/laptop-mode/laptop-mode start
00000001)
echo -n $maxspeed >$setspeed
#/etc/laptop-mode/laptop-mode stop
esac
logger "ACPI action undefined: $2"
esac
battery)
case "$2" in
BAT0)
case "$4" in
00000000)
logger 'Battery online'
00000001)
logger 'Battery offline'
esac
CPU0)
*) logger "ACPI action undefined: $2" ;;
esac
button/lid)
case "$3" in
close)
logger 'LID closed'
open)
logger 'LID opened'
logger "ACPI action undefined: $3"
esac
logger "ACPI group/action undefined: $1 / $2"
esac
# vim:set ts=4 sw=4 ft=sh et:

I actually do not understand who comands at the end - this handler.sh or the settings in Kde-powermanaging, I guess it's the second, I did remove the actions for suspend on lid close time ago. I made a test now, when I change handler.sh and check "do nothing when lid close" in kde powersettings happens exact the same: performs suspend every second time only.
button/lid)
case "$3" in
close)
logger 'LID closed'
/usr/sbin/pm-suspend
open)
logger 'LID opened'
logger "ACPI action undefined: $3"
esac
Last edited by steff (2012-07-21 17:08:46)

MacBook Pro does not sleep when lid closed

Hi there. I recently upgraded my MacBook Pro from Snow Leopard to Mountain Lion. Before the upgrade my mac would sleep automatically when the lid closed. However, ever since I've upgraded, when I close the lid, my mac doesn't go to sleep. However, if my mac isn't plugged in (running off the built in battery) it goes to sleep. I looked through system preferences and I can't seem to find any settings relating to this, does anyone have any suggestion on what's happening and how I can fix it? Many thanks in advanced.

Test after each of the following steps that you haven’t already tried: Step 1 Apple menu > System Preferences > Print & Scan > Open Print QueueCheck all printers for unfinished jobs. Deal with any you find. Step 2 Apple menu > System Preferences > Energy Saver > Power Adapter > Wake for network access: uncheck. You may need to unlock the preference pane by clicking the lock icon in the lower left corner and entering your administrator password. Step 3 Apple menu > System Preferences > Energy Saver > Schedule > Start up or wake: uncheck. Step 4 Apple menu > System Preferences > Sharing: uncheck all boxes. Step 5 Disconnect all wired peripherals except keyboard, mouse or trackball, and monitor, if applicable. Step 6 Launch the Activity Monitor application. Select All Processes from the menu in the toolbar of the Activity Monitor window, if not already selected. Enter “powerd” (without the quotes) in the "Filter" text field. Select the powerd process and click the Quit Process button in the toobar (stop-sign icon.) In the sheet that opens, click Force Quit. You’ll be prompted for your administrator password. The process will be relaunched immediately. Step 7 Reset the SMC. Step 8 Boot in safe mode and log in. The instructions provided by Apple are as follows:
Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
When you see the gray Apple logo, release the shift key.
If you are prompted to log in, type your password, and then hold down the shift key again as you clickLog in.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin. Note: If FileVault is enabled under OS X 10.7 or later, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode. Safe mode is much slower to boot and run than normal. Don’t launch any applicationsat first. If sleep still doesn’t work properly, back up all data and reinstall the OS. After that, if you still have the issue, make a “Genius” appointment at an Apple Store to have the machine tested. If sleep now works as expected, go on to the next step. Step 9 Still in safe mode, launch the usual set of applications that are running when you have the problem, including your login items, one at a time, testing after each one. Some applications may not work; skip them. You might be able to identify the cause of the problem this way. Step 10 If sleep is still working after you’ve launched all the usual applications, reboot as usual (not in safe mode) and test again. If sleep still works, you’re done, at least for the moment. If you still have the sleep issue after booting out of safe mode, post again.

Can I work with MBA's lid closed?

I have connected my 23" Cinema Display to my MBA, and it works beautifully. However, everytime I close the lid of the MBA, both displays go off and there is no way to reactivate the main one by clicking with the mouse or pressing on the Bluetooth keyboard. Is there any reason why the MBA should not work with its lid closed?

Try giving it a little more time to kick back on. Mine didn't work either when I first hooked it up because I was expecting a short delay before the monitor went back on. I tried several times to no avail. So was keeping the lid fairly far down while working when the cat stepped on it (grrr) and shut it. While cursing cat and trying to get her off the desk, I left the lid down and after a delay it all just kicked in. Go figure. I've had it woking with lid closed since then. Tried it several times and just had to leave it down longer. Hope this helps

System hangs after using external display with lid closed

I often use my MBP with the lid closed with an external display and Bluetooth mouse and keyboard. When done in this mode, I put the system to sleep using the apple menu, then disconnect the monitor. I found some info on the apple site explaining that this was the recommended procedure for exiting the lid-closed mode.
However, sometimes the system doesn't go to sleep. Opening the lid, the LED goes out, but the display remains off. If I then try reconnecting the external monitor, nothing happens. It appears that it has gone into some mode where it is active, but no displays are enabled. My only resource at this point is to power the system off and back on, at which point everything is ok.
I'm wondering if turning off my bluetooth devices after selecting the sleep menu item is causing the system to reawaken at a bad time, causing this state to occur.
I have also run into problems when connecting an external projection monitor. On several occassions I have connected the external display adapter before turning on the projector, or before connecting it to the adapter, and the system locked-up hard (no mouse movement, etc). My only recourse was hard power off.
Any ideas? Is this a broken system or are these known OSX or MBP issues?

Try SleepLess…
http://www.versiontracker.com/dyn/moreinfo/macosx/17893
… or InsomniaX…
http://www.versiontracker.com/dyn/moreinfo/macosx/30315

Satellite 'Won't Wake' Up With the Lid Closed

This may not be a Toshiba problem per se since it has been reported for other brands as well.
I want to run backups overnight. This requires my backup programs to 'wake' the computer from sleep. This works perfectly well for my desktop. It does not work for my laptop if the lid is down: the laptop does not wake, so backups do not run
Some details:
Model L955-S5370, Windows 8, UEFI
Power settings for a closed lid, whether on-battery or off battery, are: Sleep (not hibernate)
Makes no difference whether the power options are to sleep or not to sleep when the lid closes; in neither case does the computer wake up.
When the laptop is set to not sleep when the lid is closed, the laptop eventually goes to sleep in accordance with my general sleep settings ('sleep after 30 minutes')
The same issue has been reported in the user forums for other brands, and in those instances the problem was neither obvious or easy to diagnose. The problem seems to be in the interface between the lid closing mechanism and the operating system. Dell says they'll include a resolution in a BIOS update.
Can Toshiba help with this?
Solved!
Go to Solution.

No, you're not dense. Lacking in appreciation of subtle humor, perhaps.
"Allow wake timers" was disabled. When I changed the setting to "Enabled" my backup ran. So I am .
That said, I have read in other OEM forums that running scheduled tasks with the lid down can be a problem. Something to with the interface between the lid (hardware) and the operating system. Apparently, I don't have that problem.

Using MBP with with the lid closed

I have done some searching for tips on using the MBP with the lid closed and there is some conflicting information. I'm hoping people who use their Apple laptops in this way can help clarify a few things.
First, as I understand it, the MBP will operate with the lid closed if there is a connected power cord, mouse, keyboard, and external display. I plan to use mine with a Bluetooth mouse/keyboard. (More details from Apple can be found here.)
These are my questions:
1) I've heard people issue warnings about laptops overheating when running closed, but it seems Apple endorses using the MBP this way. Is heat really a problem, or are people just spreading misconceptions by predicting an early demise for a laptop used in this way?
2) Can the MBP be turned on/off when closed, or only put to sleep? I want to keep my MBP on a shelf that makes it inconvenient to open every time I want to shut down or power up. I suspect putting it to sleep will be good enough, but if I can shut down and power up without opening the lid, that would be preferable.
3) I've read that the MBP can be glitchy when waking from sleep in the closed-lid configuration. According to some people it sometimes won't wake up and requires at restart. Am I fooling myself into thinking sleep can replace shutting down?
Thanks.

1) As long as you don't place anything between the keyboard and screen, you should be fine. There have been worries about display damage due to heat rising up from the keyboard, but no substantiated reports of real damage occuring.
2) You can obviously turn the MBP off while closed by choosing Apple > Shut Down; powering back on requires pressing the power button. Another option would be enabling the Wake on LAN feature in Energy Saver preferences.
3) AFAIK, the problems are with deep sleep and occur regardless of whether the lid is closed or not. I've not had any problems waking my MBP from sleep, but I always shut it down for the night.

Enable Lid Closed action delay

Similar Messages

Maybe you are looking for