Nvidia Shield pro and disconnecting issues

Server is hosted on an Nvidia Shield pro over wifi, the router is less then 15 feet from the shield so wifi signal is very strong, latency stays below 30ms. 
 

My issue is when I connect my Flydgi Vader 4 pro, it will work for about 30 to 60 seconds then disconnect. When it disconnects there is a 50% chance it takes the server down with it temporarily. If the server doesnt go down the controller will reconnect on its own. 

This is in the log on the client :
2026-07-26 14:59:05 INFO  :In file ../src/msw/treectrl.cpp at line 2285: 'TreeView_SortChildrenCB()' failed with error 0x00000000 (The operation completed successfully.).
2026-07-26 14:59:07 INFO  :In file ../src/msw/treectrl.cpp at line 2285: 'TreeView_SortChildrenCB()' failed with error 0x00000000 (The operation completed successfully.).
2026-07-26 15:00:39 INFO  :Connection 1 remotely disconnected gracefully (rx)
2026-07-26 15:00:50 INFO  :Server ping timeout, shutting down connection 1...
2026-07-26 15:01:57 INFO  :Drivers are up-to-date
2026-07-26 15:01:57 INFO  :Connected to the VirtualHere Client Driver (Version 2)
2026-07-26 15:02:17 INFO  :Connection 2 receiving msg size didnt complete due to error 10054, 
2026-07-26 15:02:26 INFO  :Server ping timeout, shutting down connection 2...
2026-07-26 15:03:16 INFO  :Connection 3 receiving msg size didnt complete due to error 10054, 
2026-07-26 15:03:27 INFO  :Server ping timeout, shutting down connection 3...
 

#2

Its likely your wifi. Are you using the controller via its wifi dongle, or directly plugged in? Latency should be < 5ms for a home wifi setup. 30ms is very high.

#3

Sorry latency stays below 5, it was 30 when i was trying the one on my phone. 
I have swapped the shield over to ethernet and it still drops. Same errors. I have disabled all antivirus, and windows defender protections and it still happens. I will lay around with it some more and see what happens. 

#4

OK latency shouldn't be an issue then. 

Are you using the controller wirelessly via the dongle(and VirtualHere) or is it directly plugged into the shield? If your using the wireless dongle via virtualhere I would still recommend moving the dongle to a better spot if that is the case as it can still be bad reception.  If you are directly connected with USB cable between the controller and the shield then that could be a bug somewhere...

Also looking at the product page. It could have a too high refresh rate. At 1000Hz it would be impossible because your latency approx <5ms (200-300 max updates sec in theory) so i think if possible lower that if its a setting, and use it directly connected and not via its dongle)

 

#5

I think I'm having a similar issue, also on a Nvidia Shield Pro (wired, not wireless).  Tried to connect the USB dongle for a Corsair HS80 Max via VirtualHere.  The device would show up on the client computer ("in-use by you") but about every 30-60 seconds the dialog to allow VirtualHere to access the device pops up.  It worked very briefly once (transmitted audio to the headset), but most of the time it was not transmitting at all.

I've never tried this configuration before so it's possible that trying to stream a USB dongle for a wireless headset isn't recommended or supported.  I'm not sure how to collect client logs but I'll try to figure that out and provide them if I can find them.

#6

VirtualHere should support wireless dongles ok as long as the android box is connected via ethernet. What does your latency look like in the virtualhere client. Right click USB Servers->About->Statistics. What does that generally show?

#7

Latency looks very low, here's a sample:

2026-08-04 09:04:36,Shield LR,1,0.399700
2026-08-04 09:04:39,Shield LR,1,0.520100
2026-08-04 09:04:42,Shield LR,1,0.420400
2026-08-04 09:04:45,Shield LR,1,0.423300
2026-08-04 09:04:48,Shield LR,1,0.383500
2026-08-04 09:04:51,Shield LR,1,0.396500
2026-08-04 09:04:54,Shield LR,1,0.443700
2026-08-04 09:04:57,Shield LR,1,0.453900

I think I isolated the issue.  The Shield/Android OS is trying to use the dongle as its own audio device instead of letting VirtualHere pass it through to the streaming client.  So this isn't really a VirtualHere issue, but do you have any idea how I might be able to force the Shield to "ignore" it?

EDIT: I see the other discussions about USB HID devices, this might be a lost cause.  I'll keep hunting.

#8

Impossible - if android doesnt want to give control to virtualhere there is no way to force it. Its a security feature in Android which seems reasonable....