This needs a better description as to specific issues on Mac that need addressing. Some issues are already documented and being worked on by DisplayLink. as documented in knowledgebase articles.

V7.9 M3 is required to be compatible with the latest Intel and NVIDIA graphics drivers on Windows 10.

If you are having issues, please let us know through the contact area of the support site, including as much information as possible and your DisplayLink log files so we can look into it further.

Telephone technical support is offered by the device manufacturers. DisplayLink is unable to offer telephone support and instead offers support through forums and emails.

I must highlight that in most cases for DisplayLink driver investigation, telephone support would NOT be helpful as log file analysis and/or consultation with engineering are necessary. Similarly, remote desktop or other remote control tool would not be more helpful as we would not see what is actually on the screen itself.

This requires fixes from Apple on later versions of OS X.The crashes do not occur on 10.8, even though it is the same driver.

DisplayLink does NOT design, manufacture, distribute or sell any end product. DisplayLink is a semiconductor company. We are delighted to provide email support as debugging graphics issues are impossible by phone as we need data for a diagnosis.

The assistance for installation, and sales support, is coming from the product manufacturer and the seller as they know best the product they decided to build.

Unfortunately we are unable to support Kitkat versions. We rely on the operating system to get the pixels to display. This was only implemented from Android 5 Lollipop. That means we are unable to make it work on non-modified Kitkat versions because there is nothing for us to interface with.

http://support.displaylink.com/knowledgebase/articles/557862-known-issues-and-limitations-with-displaylink-for

Thanks for the idea, but this is not something specific for DisplayLink to do.

This would be a product built by a DisplayLink partner who would take the DisplayLink technology and build a KVM around it.

This is currently possible using the standard Windows APIs. It is forbidden for a graphics driver to change layout and it will make it fail qualification. When a driver is not qualified, it is not Microsoft signed and cannot be on Windows Update.

We have removed versions affected by a small security sensitivity from our website so everyone uses a newer version. 8.1 did not have any specific feature removed afterwards.

Having investigated this, it looks to be specific to Windows on the SP3.

DisplayLink drivers and software make no changes to the position of the task bar. The OS certainly thinks that the DisplayLink display is the primary monitor, but does not always move the task bar to reflect this.

There is nothing DisplayLink can do to change this behaviour.

See the comment from Carlo on this being an OS X feature, which can be disabled.

This is a problem in the Intel graphics driver and has been fixed by Intel in the latest graphics driver (15.60.0.4849 or later).
https://downloadcenter.intel.com/download/27266/Graphics-Intel-Graphics-Driver-for-Windows-15-60-

Instructions are developed by the product manufacturer/seller of the product. DisplayLink does not design, manufacture or sell any end product.

Our Android app works on Oxygen OS today (like the Oneplus 3T), but we believe the Oneplus 2 may not support USB host mode, so cannot connect DisplayLink, (or any other USB device) to it.

DisplayLink is not responsible for the product design. We provide ICs which can be integrated into products. Physical hardware failures such as this, should be fed back to the product manufacturer.

The touch screen controllers are separate from DisplayLink and there is no touch screen technology built into our ICs.

Touch screen support is enabled by customers integrating DisplayLink and a touch screen controller into the same product.

This means that the drivers for the touch screen controller differ between products and are not part of the DisplayLink driver.

For touch support on Android, the touch screen drivers would need to be integrated into the Android OS, and this is not something DisplayLink can do as we do not own the OS on phones or tablets.

This needs fixing in Android OS by Google. There is an open bug on Google for this here: https://issuetracker.google.com/issues/37096466

Please highlight this bug to Google to try and get the issue fixed.

This is unfortunately not possible using the Windows UMDF USB driver and is documented in http://support.displaylink.com/knowledgebase/articles/942862

This can be done today, using standard OS interfaces. DisplayLink displays can be managed using OS APIs.

Any known issues or problems that can be detected or worked around are already done today.

DisplayLink will not be able to implement this as this is an operating system feature. But DisplayLink is working to get the operating system writers to select the best GPU available for the task instead of selecting the first one.