HP Monitor 1600x900 thinks it's showing 1440x900
 

Hi,

Just joined the forums to say that I'm coming across this issue, and hopefully can help nail it down a little.

I've just bought a whole bunch of HP 20" monitors for my workplace, and I'm finding when giving users new Windows 10 laptops, the Displaylink drivers (even the newest ones) are making the displays blurry...

But it seems to happen only on these monitors with their native resolution. All other monitors that I have are fine.

Interestingly, the resolution is 1600x900, but when I look at the monitor menu itself (using the buttons on the front of the monitor), it thinks it's showing 1440x900, which may explain the text blurring. This is when connected via VGA with a docking station.

When connected via VGA straight into the VGA port of the laptop and not the docking station, the display is fine, the monitor reports 1600x900, and everything is sharp.

The monitors are the HP ProDisplay P202.

This seems to DEFINITELY be a DisplayLink driver issue.

Hopefully someone can respond - and let me know if you need some more info.

Thanks!

Hello Congo,

I created a new thread for this as that was an old thread and your text is not blurry but should be stretched or compressed.
Would you please be able to provide the log files as described in my forum signature so I can look into what is going on?

OSD doesn't measure the signal. OSD gives what is the closest to what it thinks the signal is. Our log files will tell me the timing being sent to the monitor.

Kind regards,
Alban

You're right - Win10 thinks the monitor is displaying 1600x900, but the monitor thinks it's displaying 1440x900. That's why it looks blurred.

Anyway, log files attached!

Hello Congo,

Thank you for the logs, this is helpful.
Your monitor does not use the VESA standard timing whereas the VESA standard timings are being sent.
The signal sent to the monitor is 1600*900 @ 118.25 MHz
The signal the monitor expects is 1600*900 @ 108.00 MHz

This is not really a resolution issue but a "detailed timing" one. The OSD doesn't measure but does a guess, and guesses wrong.

I've flagged this to engineering to see what we can do to use the monitor detailed timings instead of the standard VESA timings. However this is not a quick fix I can just give you now, unfortunately.

Kind regards,
Alban

Thanks for the update. Hopefully there will be a fix at some point in the future, as I've bought 15 of those monitors! For now, I'll need to get users to plug monitors directly into their laptops instead.

Hi Congo,
I've scheduled a fix for this for version 8.0 and this is currently getting assigned to a developer.
If you wish to get a development build for you to try when this is addressed, would you please create a support ticket by sending an email to technical_enquiries? You could title it 8.0 Development Build for 22482, for instance.
I'll attach the internal bug number and will have your details to email a link to you.
Thanks for your patience!
Alban