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).
Development is in progress with a third party.
@Imran: to get rid of the third display, set your first monitor to mirror your MacBook screen rather than extend the display.
How long will development take DisplayLink? This is basically making the product useless for a lot of users on Mac Intel.
I am having the same issue as the last comment, I installed Amphetamine it kept the display from going dark but it does not remove the 3rd display. Please let us know when this will be fixed. Thanks. I am using a 2012 MacBook Air.
To validate all the comments already made, Amphetamine kept the display from going black as the drives begin to sleep but it does not remove the 3rd display of the closed laptop. Please complete the development ASAP.
Gather feedback - Feb 19, 2020 // Planned - - Aug 20, 2020 // Started - Jan 8, 2021
Hahahahahaha... this is never getting done lol.
My dear Admin - at least show the courtesy and reply to people who have bought the product (and it's not cheap) and aren't able to use it the way they'd like!! Absolutely no respect for the customers.
Karthik Akkur commented
Any fix for this issue ??
Diptiman Basak commented
Update - Likewise with @Randy with Amphetamine it still shows 3 displays and sometimes new window opens on the third screen (macbook) which is annoying, Anyone has any solution for this which can be done on Amphetamine?
Zane Hitchcox commented
Any estimate on when this will be done? This is a very important feature to my workflow.
Can an admin from Displaylink please respond to the *myriad* comments asking for a release date for the fix to this issue? The lack of customer service on this is ridiculous -- I'm considering returning my dock and buying a different one which doesn't rely on this buggy software.
Randy Lim commented
Even if Amphetamine, it is showing 3 displays instead of the 2 in clamshell mode. So much issue that I had to revert to the legacy build. 5.2.5.
Yet even if the legacy build, I face tons of issues.
With my MacBook hooked up to my D6000 docking station, when I off the power for the day, the next morning when I turn on the power and open up the lid, it macbook's lid is blank then it hangs and the reboot my machine.
Managed to get Amphetamine work on Intel Based Macbook Pro running DisplayLink driver 1.3. Create a new trigger in Amphetamine and uncheck Allow Display Sleep, Allow System sleep when display is closed.
Max Olaïzola commented
@alex I'm on MBP M1 ! But I have still issue with my second displaylink when I leave sleep mode...
The driver doesn’t work in clamshell mode for older Intel Macs NORMALLY, as Alban stated, but it DOES work when you have Amphetamine installed! Forgive me for my long winded comment, but I have a suggestion based on my end-user experience:
Basically, MacOS has a set of simple “Clamshell Rules” for when/IF clamshell mode works. Mac doesn't send a continuous signal to the USB port when the lid is closed UNLESS there is a Mini DisplayPort/Thunderbolt (MBP/TB) device connected and you’re connected to power. The rules do NOT include USB 3.0 connected displays on older Intel Macs, only newer devices with USB-C (which is *technically* playing by the original rules anyway because USB-C for Mac is actually TB, and it also carries power). The DisplayLink driver just doesn’t meet the simple requirements of MacOS’s code because of that final 3rd rule- Lid closed, be plugged in, BE CONNECTED TO MDP/TB. Because there isn’t a MDP/TB device connected, the HDMI-USB signal drops and the screen goes black. It’s not that the video signal has dropped. It’s that your Mac is basically prepping to sleep! The normal human reaction when a computer screen goes black is to wiggle the mouse. So basically your MacBook wakes back up because of mouse movement, and then cycle starts all over again: Mac sends a signal to the monitor for about 30 seconds because it recognizes a display device, but then it starts checking the “Clamshell Rules”, screen goes black, your Mac starts the sleep process, you wiggle the mouse. Repeat. Repeat, Repeat. Essentially the DisplayLink drivers fail because it’s trying to get your device to act one way, but the normal behavior of MacOS ends up winning in the end because of how simple the rules are.
The reason Amphetamine makes DisplayLink work because their app has a setting that is basically circumventing the rules- When the lid is closed, please don’t go to sleep, but please shut off the BUILT IN display- other displays are totally cool to show. What ends up happening is your MacBook acts more like a Mac desktop connected to a traditional monitor where the power button was switched off. The lid is closed, but the USB ports still receive their signal because MacOS didn’t go to sleep. Perhaps you guys can do some digging into how this works overall and implement it into your next update?
FYI, I’m on a 2017 MacBook Air I5 A1466.
Does anyone know of another product that actually works to run 2 additional screens in clamshell mode for a MacBook pro running Big Sur??
Ashish Aggarwal commented
Any update on this issue as I am experiencing the same issue with the latest driver.
@Max No that is only possible on M1 Macs not Intel based Macs.
Max Olaïzola commented
Hello Alban ! I just found this https://support.displaylink.com/knowledgebase/articles/1963276-clamshell-and-rotation-support-on-macos-big-sur-11 Does this mean that this issue is now resolve or it's other problem ?
any idea when it will be available?
Just now started yet its been a complaint for how long???? I have never seen such an unorganized company before, don't you want to please your customers??? Guess not.
Got a nice hub today, they use this broken software unfortunately. This is the dumbest thing I've read in a while. And an issue for so long? gg