keyboard stops after 10 seconds

I'm using moonlight and connected the mouse and keyboard (so I can use the windows key) via VirtualHere. The mouse works fine, but the keyboard stops after 10 seconds not using it.
I've read the same problem at this forum so I disabled the "USB selective suspend setting", that didn't work. After some search I found to disable it in the registry, that works, but sometimes after a reconnect, Windows installs it as a new device and then I have to change the registry again to make it work.
Isn't it possible to "support" the "selective suspend" setting or that it pretends to suspend?

#2

Yes virtualhere software tells windows it doesnt support selective suspend but it selective suspends anyway. Not sure if its a bug in virtualhere or some devices just ignore that suggestion. (I suspect the later)

Anyway what exact keyboard model is it? And is the server android version ? and the client windows 10 (latest version)?

#3

It's a Microsoft all in one keyboard, recognized as "Microsoft nano transceiver v2.0". I've updated Windows 10 (client) to the latest version (1909) and using a Asus tinker board as server, Armbian 20.11.3 kernel version 4.4.213.

#4

Indeed it seems like some devices ignore that setting, because when I change it in the registry it works like it should, but everytime when it's recognized as a new device it get's the default values in the registry.

#6

Wow I think that did the trick, thank you! This also prevents the mouse from resetting it's settings (cursor speed) was pretty annoying with the trackball mouse I use that has a way too fast default speed.

#7

Thanks for letting me know. That info might be useful for other users...

#8

Necrobump but I am actually having the same issue with the exact same all-in-one Microsoft media keyboard/trackpad. If its not too much trouble, could you explain the steps you took in more detail? How did you find the registry entry of the keyboard as it is assigned through VirtualHere? Then later it sounds like you had to assign a port manually to it?

Thank you very much for your guys' help in advance. It is getting very annoying having to leave Moonlight then having to reconnect just to get the keyboard working again. 

#10

Excuse my ignorance but how do I find what port I need to assign the keyboard address to? I used 1 as the port and my computer BSOD's whenever I start VirtualHere

Edit: Think i found it in device manager: Port 1 hub 4 

How would I put that into the registry?

#11

  1. In the virtualhere client right click on the All-in-one keyboard and select Properties and note the address e.g 112
  2. Edit that Windows registry entry and make up a port number e.g 1

    So you would enter

    1=112

    in the registry and then reboot

     

#12

I actually did exactly that but then when I reboot, my computer would BSOD the moment I start the VirtualHere client. For the record I have two devices on the Android server hub so I put but 1=1234,2=5678 and it would still BSOD.

Any ideas? Is it because my Port1 and Port2 are already being used?

#13

Actually it looks like I might have been adding it as a string. Will try it as a key and report back

#14

It should be a string. It works fine for me - i just tested it again like so:

  1. Right click on the device in the virtualhere client and select Properties and the look at the address. Mine says 31
  2. I would like this device to go on virtual port 5 so i run regedt32 and navigate to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vhusb3hc\Parameters and right click and New->String Value then name PortMappings then the value is  5=31 then i click OK and reboot. I then use that device again via virtualhere and it appears connected to port 5 I confirm this using  https://www.uwe-sieber.de/usbtreeview_e.html to see the layout.
#15

Ok now I think I got that part working but my game controller, whenever that device starts getting used the computer blue screens

The strangest thing is that the game controller changes device address everytime I turn it on so I apparently can't even add a registry key for it? Very strange occurence. Thanks for your help though I'm going to try and get to the bottom of this

#16

Actually you are right, after i rebooted again it did crash on whatever device i tried to use via virtualhere. This used to work so something must have changed.  Anyway remove that entry from the registry and reboot and it wont crash again. Although there is no way to force a particular port then at the moment...