macOS App: Clamshell / Lid Closed Mode
The macOS App driver does not allow me to operate on external monitors with the laptop closed. I had to uninstall the driver and reinstall the one from November to be able to work in clamshell mode. This is glitchy in the old driver, often freezing my computer. I was hoping to see this stabilize so I wouldn't have to restart so often (almost every time I disconnect my laptop from the docking station).
Anonymous
shared this idea
macOS 12 Monterey is now released and addresses the clamshell / lid closed use case on Intel macbook computers.
276 comments
-
Dayel
commented
Guys, I know things aren't as simple as we'd like them to be, however, it's been 17 months since the problem was detected (yes a problem, not a feature improvement), and it's already been 7 months of development. I believe that many other users, believing that the problem is already addressed, did not comment on the post, and others certainly returned the hardware (according to some reports here in this thread). Can someone please give us some news about the progress in solving this problem, which has been affecting me for months as well?!
-
akos buzinkay
commented
I've found a simple solution: returning my docking station :D and switching back to my old one without DisplayLink
-
Anonymous
commented
Hi there! Any update on a fix coming to intel macs?
-
Claudio
commented
hi, i've installed the latest version of driver (1.4.0 build 57120) on MacBook Pro 13,3 2017 but i have the same problem. Can you help me?
-
Alfredo Nunez
commented
Please follow up on this enhancement. I use this displaylink adapter for work and given my desk setup it is unbearable to use with my laptop screen open.
-
M Tauras
commented
While we continue to wait for a proper solution (which, to be a real solution, would need to do away with this screen recording hack), I have found a combination of two MacOS apps to allow for clamshell mode with the current driver: 1) Amphetamine to disable sleeping when lid is closed and 2) SwitchresX to disable the built-in display so it does not appear in the list of monitors when moving windows between tabs, moving mouse around, etc.
It is absurd I have had to buy these two apps, but it is what it is at this point.
-
John Topp
commented
sounds great, most appreciated and looking very much forward to release of the updated driver as I am too very annoyed with current old driver.
-
Bryce
commented
Is there any update from DisplayLink on when this will be completed?
-
Corey Franco
commented
I was able to work around clamshell not working by downloading Amphetamine from the App Store. I have it trigger on connecting my dock and make sure you have "Allow system to sleep when display is closed" unchecked. I'd rather displaylink just work but this is the next best thing for me.
-
Chandra Sekhar
commented
I am posting an update: I switched to previous DisplayLink version (1.3.1 (Build 56.126)) on BigSur, my problems are solved - Monitors do not sleep after sometime.
DisplayLink Manager 1.3.1 (Build 56.126) is fine with both my MBP 13" (TouchBar) and MBP 16" TouchBar versions. 3 external monitors.
-
Ben Wagner
commented
Any update?
-
Chandra Sekhar
commented
Recent comment is on July 6th. That means this is not solved yet.
My current problems are...
1. Monitors sleep after sometime in clamshell mode (Dell D6000 Universal dock)
2. Minor problem: No night shift color on the monitors that are powered by DisplayLink.I hope this problems get solved.
-
cubcougar73
commented
What a daunting and disturbing set of tasks for a work around solution to Displaylink software to make your high priced best in the world hardware to work.
If I understand correctly ... there are only just Two workarounds.
1) See if I can install another 3rd party software correctly ... to see if it works.
2) I program the Mac OS with, on the face of it, 4 individual written commands using the terminal pmset command back door sub system - then dance with Displaylink software a different more complex way with the Mac OS preferences ... to see if it works.
Of course the 3) is to wait .. until you fix it with a better Displaylink Installer ..
(to which I have to then uninstall the aforementioned 3rd party software if used as suggested... or ... spend 18 hours doing a Command Restore startup to clean out the terminal pmset commands.)
-
cubcougar73
commented
Unfortunately this is how it all works now.
Clamshell should be available soon - even though do not have the date available yet, I know that we are heading in the right direction.
As we work with the OS vendor and are dependent on them to support Clamshell mode it takes more time and requires more processes to take place.
You can sign up for notifications and you will get an email informing about the next driver release and new features/improvements: Notifications (displaylink.com) -
Brady
commented
Scratch that, it works for about 5 minutes, then cuts out and has same issues. Clamshell still not fully operational.
-
Brady
commented
I started having this same behavior today. I was able to update to the latest beta version of Mac OS (12.0 Beta of macOS Monterey) and install the latest driver (1.4) and now everything works again in clamshell mode.
-
JDG8R
commented
Remove all other versions first. Then Install DisplayLink USB Graphics Software for macOS (5.2.5).
-
zmeden
commented
I see it is in development from 8 of January this year? It has been more than 6 moths, is there ant new info on this? This is basic functionality IMO. If I connect to passive dongles to my MAC and connect 2 monitors I can close the lid and it works. Why do you guys have such an issue for more than 1 year now implementing this? This is just unacceptable. I payed 200 EUR plus for my dock and it is half useful..... PLS guys can you set this to the highest prio because it is very embarrassing for you tbh.
@JDG8R 5.2.5 or the latest version do not work for me.
MBP 16 2019
-
JDG8R
commented
Installed DisplayLink USB Graphics Software for macOS (5.2.5). That seems to have worked.
-
daniel.grm25@gmail.com
commented
Why are you so slow with this? I can't roll out a proper solution to the coporate fleet of macs where I work. Is there a timeline?