Thanks for the info.
We are currently looking into it. It seems like a bug on our latest spacedesk Android viewer app.
The fix for this issue will be available in the next version of android viewer app.
Nope! No pen, no touch input. But I haven’t got that popup message anymore. The secondary display connects and mouse input works, but the Spacedesk window in the primary machine shows “No remote connection”.
Hi @viviane,
Ok thanks for the info.
So pen and touch input are still not working?
..and there’s no display connected but remote mouse is working? so it’s connected but black screen only?
The second screen connects properly and the mouse input also works, but not the touch, neither the pen. However, the spacedesk Driver window in the primary machine (Win 10) shows “No remote connection”, and nothing happens when I try to change the “Settings” to, for instance, OFF. I receive a popup message “Dou you really want to disable…”, I choose “Yes”, but nothing changes. The tablet is connected through wi-fi hotspot, and everything is updated (NVIDIA driver 471.41) NoPenNoTouch.
Hi @viviane,
Could you please run services.msc on your primary machine, find spacedeskService ,right-click restart it then try again to reconnect the spacedesk viewer app.
It worked, but the pen is now too laggy. Moreover, I had a death blue screen. It is still too unstable. I’m going to uninstall everything and waiting for a further version. Thank you for the assistance.
I’m still experiencing this problem and would like to pursue it. I’m running the viewer on a Samsung S7+.
my Windows machine is using Beta Version 1.0.7
Android is using v0.9.73
I’ve rebooted and I’ve explicitly run services.msc and restarted the spacedesk service. Still to no avail.
Hi @viviane,
We are currently fixing it on server side.
We will let you know as soon as we have new version for you to test.
As for the BSOD (blue screen of death), when did it exactly happened?
Could you please send us the following for further analysis:
– run dxdiag.exe on your primary machine, click “Save All Information”, save the output file (dxdiag.txt)
– most recent dump file (*.dmp) of your BSOD with spacedesk which is located in C:\Windows\minidump folder.
Hi @viviane,
Thanks for sending the dxdiag files.
Please save the dump files in one folder, then right-click Send to -> Compressed (zipped) folder, then attach the *.zip file on your next reply.
By the way, when did the BSOD (blue screen of death) exactly happened?
The BSOD occurred when I tried to change Settings in the driver window (primary machine).
Is it in the display settings window? Or spacedesk server menu settings?
Can you specify which settings exactly are you trying to change?
After installing the driver the Win10 starting Menu stopped working. I had to reboot the computer.
Is it consistently happening? Or only after installation?
It seems like a window explorer is crashing or hanging.. To verify, when it happens again please open the task manager then find the Windows Explorer, right-click -> Restart it. Then try again to click/open the Windows start button.
Hi @viviane,
I assume your spacedesk is connected over WiFi network, is that correct?
Routers can cause lags and latency. Bypassing them always improves performance. Configure Windows PC or Android device as WiFi Access Point (Hotspot) and connect to it before connecting spacedesk.
USB Tethering achieves the same result.
Please check the chapter “Performance Tuning” in the instruction manual: https://spacedesk.net/user-manual
By the way, does the BSOD upon settings OFF still happening on latest spacedesk version 1.0.8?
So far the BSOD hasn’t occurred anymore. Regarding the connection, I’ve been using only the WiFi Access Point (Hotspot) since I installed Spacedesk for the first time.
Currently the only option to improve performance is by eliminating the router.
If your Android tablet supports USB tethering, you can also try that with spacedesk.
If it did not help, then you’ll probably have to wait for our next performance improvement feature.
spacedesk will offer h264 hardware encoding very soon.
.
