OK i just tested again on my pixel 3a. Yes indeed android is hiding the mouse from virtualhere (I notice when i plug a mouse into my phone a mouse cursor appears when i move the mouse just like a computer screen) and Android is no longer sending an event telling virtualhere a mouse is connected.
I looked in android settings to see if i could disable the mouse somehow but couldn't see the setting anywhere there.
So for the time being (hopefully android adds a way to turn off automatic mouse capture) virtualhere cannot capture the mouse and redirect it anymore.
This appears to apply to all mouse/physical keyboard devices used with an android sever. I cannot get any keyboard or mouse device passed through from my Huawei Mate 20 Pro (Android 10) to the windoes client. No problems with any other devices.
Yeah they've blocked mice/keyboard permanently from being redirected for some reason. Google must only want the mouse/keyboard to be used with Android now and not to be redirected.
The link i gave shows the android source code has an entry in there to block keyboard/mice from being redirected. Phone manufacturers can change the source code but probably most just leave it as is as there is no reason to modify that so yes it will be blocked from being redirected by virtualhere. I can make a request to google and also you could make a request also, perhaps they might listen if a few people request this https://source.android.com/setup/contribute/report-bugs#bug-queues It in the "System" item listed there.
I posted this comment accidentally on a different thread on the site, sorry ?. At any rate, I found that not connecting your devices until AFTER SteamLink (SL) is open and connected to host running Virtual Here server (I'm using steam version) somehow allows Virtual Here client to capture the devices and pass them through properly. You'll need to connect them, configure them to be shared in SL settings disconnect all, connect to host PC( this might work for GeForce now as well) and then plug them in. This worked to allow me to passthrough wired KB and mouse and wire headset via RF dongle perfectly.
Hi @Michael, there's been some activity on the Google bug tracking issue page in the last week or so, and they've asked some follow-up questions about it, any chance you could pop over and have a look? I've been keeping an eye on it hoping it'll eventually get fixed for a couple years now...!
.
What android device are you running virtualhere server on?
.
it happens on all devices I have used: OnePlus 7T, Samsung S9+, Samsung Tab A 10 2019
.
for context. It used to work on my Samsung Tab A before the Android 10 update 2 weeks ago
.
OK i just tested again on my pixel 3a. Yes indeed android is hiding the mouse from virtualhere (I notice when i plug a mouse into my phone a mouse cursor appears when i move the mouse just like a computer screen) and Android is no longer sending an event telling virtualhere a mouse is connected.
I looked in android settings to see if i could disable the mouse somehow but couldn't see the setting anywhere there.
So for the time being (hopefully android adds a way to turn off automatic mouse capture) virtualhere cannot capture the mouse and redirect it anymore.
This appears to apply to all
This appears to apply to all mouse/physical keyboard devices used with an android sever. I cannot get any keyboard or mouse device passed through from my Huawei Mate 20 Pro (Android 10) to the windoes client. No problems with any other devices.
.
Yes its a bug in android 10 on some platforms. They hide USB mice, you will need to wait for android 11
.
The problem has not been solved in Android 11.
.
OK i just checked the android source again (https://github.com/aosp-mirror/platform_frameworks_base/blob/c5d02da0f6…)
Yeah they've blocked mice/keyboard permanently from being redirected for some reason. Google must only want the mouse/keyboard to be used with Android now and not to be redirected.
.
Does that mean you can't use your mouse and keyboard on Android with the exception of root?
.
The link i gave shows the android source code has an entry in there to block keyboard/mice from being redirected. Phone manufacturers can change the source code but probably most just leave it as is as there is no reason to modify that so yes it will be blocked from being redirected by virtualhere. I can make a request to google and also you could make a request also, perhaps they might listen if a few people request this https://source.android.com/setup/contribute/report-bugs#bug-queues It in the "System" item listed there.
Edit: This is the issue i created https://issuetracker.google.com/u/1/issues/193949757
.
I got feedback from google, they said they will investigate this...
Issue Tracker/Work-Around
I posted this comment accidentally on a different thread on the site, sorry ?. At any rate, I found that not connecting your devices until AFTER SteamLink (SL) is open and connected to host running Virtual Here server (I'm using steam version) somehow allows Virtual Here client to capture the devices and pass them through properly. You'll need to connect them, configure them to be shared in SL settings disconnect all, connect to host PC( this might work for GeForce now as well) and then plug them in. This worked to allow me to passthrough wired KB and mouse and wire headset via RF dongle perfectly.
.
Hi @Michael, there's been some activity on the Google bug tracking issue page in the last week or so, and they've asked some follow-up questions about it, any chance you could pop over and have a look? I've been keeping an eye on it hoping it'll eventually get fixed for a couple years now...!
.
Sure, thats done now.