Make sure you run the installed client (1.9.1), can be confusing if you have multiple versions.
If it still doesn’t connect, provide details on what actually happens, if it gets stuck, what messages are shown in debug console and/or client, …

This kind of situation would usually relate to device and PC not being on the same network, or firewall blocking visibility. To avoid the latter, it can help to run server as admin and verify that firewall allows access (a user reported issues with Avast Internet protection).
As a last resort, you can try setting the IP manually (force IP option in TG server), by setting it to the IP shown in Android Settings>About phone>Status

thanks for letting me know, here’s a couple more test versions. Let’s see if any of these make a difference. When testing, please try both lens calibration enabled and disabled.
Option A
Option B

Still have the same problem with both versions, in both modes (Lens correction on/off).
Maybe it’ll help: the problem occurs in most of the windows, but not in all of them. For example now I have the following situation:
The problem occurs in: (Chrome, Control panel, Foxit reader, Evernote, Total Commander, Windows File Explorer, Visual studio 2013, Unity game window)
The problem does not occur in: (Trinus Gyre server window, Skype, Unity editor)

anybody with the scaling issue has tried to take screenshot with the server version linked above?

maybe, but I need some proof and details. If anybody can test the above server it would give me a good hint:
– install that version (link)
– run as usual and when having a window with the wrong scaling occurring, take a screenshot by pressing 0
– share that screenshot to see if the image is actually a portion of the window as shown in the phone
That would prove that it is the capture step in the server that gets the wrong size, not a scaling issue on device.
Worth noting that my dev PC is a Win 8.1 with AMD graphics and never got that issue, even though it is a laptop with switchable graphics

• This reply was modified 5 years, 1 month ago by  loxai.

Ok, good, so it turns out it is not a problem with the Note4, but the server side. Now, still not sure how to fix it, but there are a few things to try:
– here’s a new server build which tries to detect scaling (dpi settings). With some luck, this will sort out the problem. If it doesn’t…
– try running the target window in Windows 7 compatible mode, or…
– disable display scaling on high DPI settings (this and the above are accessed through the .exe properties of the program that is being cropped)

if none of the above works, I’ll go for a more drastic approach that will most likely fix the issue but require manual tweaking.

thanks for testing