support

Bitte oder Registrieren, um Beiträge und Themen zu erstellen.

Driver failure? during screen mirroring

Hello,

These days I have run into a possible driver issue while mirroring the screen of my laptop(ASUS TUF Gaming A15 FA507XU) to my Android Phone via LAN. Spacedesk driver/viewer on both devices has been updated to the newest version and GPU drivers are pretty new, but I reckon this is not an issue about GPU.

So the problem is, I can connect my phone to my laptop without any issues, but after some time, the display on my phone may suddenly get stuck and do not respond to touch. This “some time” seems random, it can be 10min or 1h, and there are even times when Spacedesk runs 3h+ without showing this problem. Anyway, if the problem occurs, a message will pop up and it says the bandwidth is low. At last, the display on my phone will black out and shows “Connected – Display off”. If I try to disconnect manually, the viewer will wait for 40s and says it has disconnected.

Meanwhile, on the primary machine, it seems that the driver ran into some problem. In the Windows settings, there are still two screens attached which work in the duplicate mode – even after I disconnect manually on my phone. Also, the Spacedesk control panel still shows that one Android secondary device is connected to my laptop. More interestingly, sometimes I just cannot switch the driver off after this problem has occured.

I have done some survey via Google but unfortunately they did not solve my problem. I turn on the diagnostics and tried to reproduce the problem twice (The log of debug view is attached, but I fail to find where’s the dump files). The log likely says that there is a network issue, so I use Wireshark to capture the traffic. The captured result says that at some time Spacedesk seems to refuse to recognize TCP patches and as the result, the viewer and driver tries to retransmit the patch again and again. However, as the driver stop to respond to further connection (maybe) after the problem has occured, I guess there is still a driver issue.

Is there any way to solve this problem?

Thanks!

Hochgeladene Dateien:
  • Du musst dich anmelden um auf Uploads zugreifen zu können.

Hi @tadshi,

Can you also try with USB and see if the same issue occurs? Also, may we ask again for your diagnostic logs? There were some that weren’t included in the package you sent. Please follow the steps provided in the image below which you can also see in the Diagnostics section of the Driver console. If the file size exceeds 512 kb, please upload it via Dropbox and attach the link on your next reply.

Thank you.

Hochgeladene Dateien:
  • Du musst dich anmelden um auf Uploads zugreifen zu können.

Hi Renz,

Thanks for your reply.

It turned out that I have made some mistake while saving diagnostic information – the “save all information” button should be clicked again after elevation. I just managed to reproduce the problem again on LAN and upload the diagnostics to Dropbox, plz check them.

https://www.dropbox.com/scl/fi/gm51v1oyhseac6cny5sfv/spacedeskRuntimeDiagnostics.zip?rlkey=h1aczqn8hqav3s49tuy0lxepa&st=akxf2zxj&dl=0

As for the USB, I have tried it but the problem has not shown up so far. I cannot tell whether the problem has nothing to do with USB connection or it is just sheer luck, but I’ll report it ASAP if it is reproduced on USB.

 

Hi @tadshi,

Thank you for uploading your logs. We are currently analyzing them and will get back to you as soon as possible. In the meanwhile, you can continue to connect using USB.