Touch input not forwarded on first tap after ~1 min idle (spacedesk Viewer on secondary touch laptop)
Hi,
I’m having an issue with touch input after a period of inactivity and wanted to ask whether this is known behavior or a bug.
Setup:
– Primary PC with the spacedesk Driver installed, connected via LAN to a second touch laptop running the spacedesk Viewer.
Issue:
– After about 1 minute without touch input, the first tap afterward is not forwarded to the primary PC – it seems to only serve to “wake up” something internally. The window/app remains active and in focus the whole time, and the screen does not go into standby. Only the second tap is actually registered as input.
– This happens reliably after about 1 minute of inactivity, every time.
What I’ve already ruled out:
– Screen standby on the touch laptop is disabled (confirmed via spacedesk’s own settings, the screen never turns off).
– Power management for the touch digitizer in Device Manager (HID-compliant touch screen) – “Allow the computer to turn off this device to save power” was never enabled in the first place.
– USB Selective Suspend is disabled system-wide (both plugged in and on battery).
– The spacedesk Viewer window remains the active/focused window throughout – so it’s not a Windows focus issue.
This points to some kind of internal idle/standby timeout specifically in spacedesk’s touch input handling (viewer or driver side), rather than a Windows power setting.
Is there a setting to disable this idle behavior, or is this a known issue that’s being worked on? Happy to provide logs if needed.
Thanks!
Hi @jan_grz,
Can you provide the following:
- spacedesk Viewer type (Windows 7 Legacy version or Windows Store version)
- Dxdiag output file of Viewer laptop by running dxdiag.exe on your viewer laptop, then click “Save all information”
- Diagnostic logs from Primary machine.
For the diagnostic logs, you may collect these by opening the spacedesk Driver console as administrator and clicking on Diagnostics then follow the steps below:
1. Download the DebugView.
2. Check the Diagnostic Collection box.
3. Reproduce the issue by tapping on the Viewer screen TWICE ONLY after period of inactivity
4. Uncheck the Diagnostic Collection box.
5. Click “Save All Information” button (this might take a while to finish).
6. Compress/Zip the folder which contains the logs, then attach to your next reply to this post. If the folder exceeds 512kb, you may upload it to Dropbox or Google Drive then include the download link on your next reply.
Thank you.
Hi,
Thanks for the detailed steps
One additional observation that might be useful in the meantime: when I connect the same two machines remotely over VPN instead of directly on the local LAN, the issue does not occur at all – touch input is forwarded correctly even after being idle for a while. It only happens when both machines are on the same local network.
My current suspicion is Energy Efficient Ethernet (EEE / 802.3az) putting the physical link into a low-power state after a period of no traffic, since VPN connections typically send periodic keep-alive traffic that would prevent this, while an idle LAN connection wouldn’t. I’ll give that a try.
Thanks!
https://drive.google.com/drive/folders/1bKGojLfQaXdAta3WlyH5YHmrceuK6nOG?usp=sharing
Hi,
Quick update: the issue is resolved. After disabling Energy Efficient Ethernet and the related power-saving options (Green Ethernet, Advanced EEE) on the network adapters of both machines, the first tap after a longer idle period is now forwarded reliably.
Thanks for your help!