Microsoft mouse stops working on client

Submitted by ayavilevich on #1

Hi,

I am using a raspi B+ server and a windows 10 client.
I have several devices connected and working with VirtualHere, including a keyboard and a webcam.
I have a mouse device that is problematic. It works at the beginning, but then after a short time stops working. I need to go and toggle it off and on again in the client UI for it to start working again (briefly).
I have tried two different mouse. Use receiver is called "MicrosoftAR 2.4Ghz Transceiver v8.0" and another is "MicrosoftAR Nano Transceiver v1.0" (A is an accented A and R is the registered symbol). Both mouse misbehave the same way.

I am running `vhusbdarm` with `-b`.
How would I get the server log?
How would I terminate the existing instance to run another one?
Is this a known issue?
What should I do to troubleshoot?

Regards,
Arik.

Submitted by Michael on Fri, 2018/08/10 - 21:39

#2

Yes its a known issue. Im pretty sure your adapter is going to sleep. In windows Device Manager, go to the adapter and then select Properties and UNcheck "Allow Computer to Turn Off Device to Save Power"

Submitted by ayavilevich on Sat, 2018/08/11 - 07:38

#3

Hmmm. I don't have this setting or the "power management" tab for this device. It shows up as "Microsoft Mouse and Keyboard Detection Driver (USB)" in the list. Not under the same name as in the VirtualHere client list.

What about my other questions:
How would I get the server log?
How would I terminate the existing instance to run another one?

Submitted by Michael on Sat, 2018/08/11 - 10:11

#4

OK, im pretty sure its a power thing you might need to use a powered hub, but anyway the log is in /var/log/syslog (grep vhusbd) and to terminal just run 

sudo pkill vhusbdarm

Submitted by ayavilevich on Sun, 2018/08/12 - 18:28

#5

Hi Michael,

Tried a powered hub. It didn't change a thing.
The mouse works at first, then after about 10 seconds of not moving it stops working. there are no log entries in the server side.
Is there a log for the client side?
Can you get a simple wireless MS mouse and try to reproduce?

Submitted by Michael on Mon, 2018/08/13 - 18:23

#6

OK try this first.

In windows Control Panel -> Hardware and Sound -> Change plan settings for the active plan -> Change Advanced Power Settings-> USB Settings -> USB Selective Suspend -> Disable all those entries.

Now try it again (when the mouse is working first)

Submitted by ayavilevich on Tue, 2018/08/14 - 03:32

#7

Changed the option but it didn't affect the issue. Any other suggestions?

Submitted by Michael on Wed, 2018/08/15 - 16:13

#8

I went and bought a cheap 2.4Ghz wireless mouse VendorID: 0x0e8f and Product Id:0x00a8 and used it via virtualhere. I didnt get any drops after leaving it idle for minutes or using it continuously

Could you update to the latest client. I did make a change that may have something to do with your issue. Download and run client 4.5.6 and see if it fixes the issue.

Submitted by ayavilevich on Wed, 2018/08/15 - 16:47

#9

Hi Michael, thanks for trying to resolve this. I updated from client 4.5.1 to 4.5.6 but unfortunately it didn't make a difference.
I have this issue with Microsoft mouse specifically. Two different types of wireless MS mouse, simple kind.
Would it help if I send you the VendorID and ProductID of the mouse I have trouble with? How do I check this?

Submitted by Michael on Wed, 2018/08/15 - 16:51

#10

You can just right click on the device in the client and select properties. Anyway i dont have a microsoft mouse to test with. Just buy another mouse or use a wired mouse if you really need to use a mouse via virtualhere

Submitted by ayavilevich on Wed, 2018/08/15 - 22:16

#11

Hi, I will use a wired mouse. Of course it is unfortunate that your software doesn't support all devices.
For the record, the problematic device has VID=0x045E and PID=0x07B2 .