My feedback

  1. 2,763 votes
    Sign in
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      2002 comments  ·  DisplayLink Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

      Update: November 5th
      Dear DisplayLink macOS users,

      DisplayLink has worked for many months to maintain support for its users during the transition from macOS High Sierra to Mojave. While functionality such as Ethernet and audio or charging, where implemented, is unaffected on all releases, display connectivity has been limited on macOS releases 10.13.4, 10.13.5 and 10.13.6.

      macOS 10.14 Mojave with DisplayLink driver v5.0.1 allows you to run up to 4 extended displays with now optional clamshell and mirror modes. Support for rotated displays is also improved.
      DisplayLink driver v5.0.1 is applicable to macOS 10.14 only.
      Driver v5.0.1: http://www.displaylink.com/downloads/file?id=1257

      Should you experience black extended display(s) with only mouse cursor on 10.14. We recommend you use macOS 10.14.2 Beta 1 or newer. We have also left DisplayLink driver v4.3 Beta available to force an AirPlay extended display on these machines if you cannot update to 10.14.2 Beta 1 with DisplayLink driver 5.0.1.…

      jacob commented  · 

      I'm quite surprised that no one from DL have answered my question on _why DisplayLinkManager.app has such high CPU usage_. Is it by design? If so, why? Using two cheap dedicated DP->USB-C dongles is both faster, more reliable and doesn't burn my CPU in the way that DL does.

      However, I found a way to force using the dedicated GPU in my MacBook Pro which improves responsiveness a bit. Just uncheck the "Switch graphics card automatically" in Energy settings.

      So, for those occasions when my screens work with the DL dock, there's another frustrating moment that hasn't been there before: somehow Mojave thinks that my screen is being shared, which disables the auto unlocking feature from my Apple Watch. Apparently the solution is to… uninstall DL driver. (https://discussions.apple.com/thread/8601456) Which raises the same question I've been trying to get an answer to in the first place: how is this solution implemented? How come are two cheap dongle adapters a faster, more stable and more compatible solution than a $300+ DL-based docking station?

      jacob commented  · 

      @Amin: There's an explanation for that, see my 2 comments written on Nov 9th. Although we still haven't heard a word from DisplayLink on WHY DisplayLinkManager behaves like this.

      Unacceptable product and customer support.

      jacob commented  · 

      (Update to my previous comment, see below)

      17 minutes. That's all I got before image corruption this time. UNRELIABLE and USELESS are the right words for DisplayLink docks.

      And regarding sluggishness: my MacBook Pro is dual-graphic. When the screens are connected with cheap USB-C->DP dongles, everything works brilliant and I can see (in System information app) that my AMD Radeon card has two screens connected. Additionally, Activity Monitor app gives me information about which graphic card is used, and it is the "High performance" one. (If you want to find out yourself, check out the "Energy" tab, and the table in the bottom of the app, it will say either "Graphic card: Integrated" or "High perf.")

      However, when I connect my screen to the dock, computer stops using the dedicated high performance graphic, and falls back to using the integrated one. Hence the sluggishness I guess.

      What a useless piece of hardware and software, DisplayLink.

      jacob commented  · 

      With 10.14.1 and driver 5.0.1 I can get it to run with two standard resolution (no 4K) screens connected to my HP dock with DisplayPort. Sometimes the image on both screens get "corrupted" (just random lines white and dark, sometimes magenta and other colors, no desktop whatsoverever).

      But even when it's not corrupted, I can't help but notice HOW SLUGGISH it is compared to using two separate USB-C->DP dongles, and connecting my screens though them.

      In the Activity Control app I can see how a process named "DisplayLinkManager" kind of eats my CPU even when I'm doing NOTHING. Just having Activity Monitor and one Safari window open (to write this) makes DisplayLinkManager use between 10-15 % of CPU on a top notch 2017 MacBook Pro.

      Can DisplayLink answer this: why is your solution so much slower than simple, dedicated, $15 dongles? I'm not talking about gaming with ridiculous FPS expectation but basic code editor and browser work.

      jacob commented  · 


      I've tried 5.0 driver and it is incredibly buggy. Installation, a couple of restarts, allowing software in Security & Privacy all went smooth and well.

      Next, I connected my two DP displays to the HP-branded DisplayLink dock and it all was perfect! So I started working and, suddenly, my both displays went "corrupt" - white and colored vertical straps all over them. So I disconnected the displays, and reconnected. Still same corrupted image pattern. Restart solved it, but only for another 3 minutes. Disconnecting the dock from MacBook solved it this time, but again only for a while. After about ten times I lost patience and reconnected my DP-to-USB-C dongles.

      It doesn't matter whether I run in calmshel mode (MacBook lid closed) or not.

      This won't probably help anyone, as we all went to 10.13.4 already in the first place. But if you think that driver 5.0 on macOS 10.14 will solve it for your MacbookPro14,3, think again. Or just wait till 5.1 driver…

      jacob supported this idea  · 

    Feedback and Knowledge Base