Android Server Licence Question

Hi, i bought what i thought was a lifetime standalone VH android server licence for one device about three years ago for Shield TV but havent used it for about a year. After sideloading VH android server on Shield TV today i was pleasantly surprised to discover it is now available directly from Google Play Store but there does not seem to be any way to enter licence key which i paid about $50 for as it was sold as a life time licence for one device to be used as VH server.

Surprisingly there is no sticky thread describing the changes of VH server licence changing over to subscription service.

Is my life time VH android server licence still usable on same device i always used it on and if so how do i enter licence key manually in VH server on android?

i also purchased VH server licence (windows, macos and linux servers) through Steam Store about three years ago and would like confirmation of any changes to licensing requirements regarding that to as can see linux/steamos support has simply been dropped even to older paying customers and yet there is no sticky thread annpouncing these changes. ref: https://www.virtualhere.com/content/virtualhere-steamlink-does-not-work… There are other stickies here that indicate otherwise (i.e. linux is still supported), so could be considered misleading as could the info on Steam Store which clearly indicates windows , macos and linux servers are all supported and no mention of any subscription licencing model. https://store.steampowered.com/app/440520/VirtualHere_For_Steam_Link/

Thanks in advance.

#2

Have tried entering my life time licence key through VH client but does not seem to work like expected.

Visiting the Google Play Store page for VH Server on Shield TV shares info that indicates it is now integrated with VH for Steam Link so will try that for now but i bought standalone VH server for system wide use of usb devices and so am not limited by 5 device or other restrictions from using VH inside Steam runtime but would like more info on the updated Steam Link functionality of VH.

After trying VH for Steam Link xbox controller does stay connected so is unusable. After searching Steam discussion group for VH i found info that seems to indicate buying VH app AND its DLC is needed for VH android server licence through Steam.

Does this app also work on the Steam Link Android App?
----------------------------------------------------------------------------
Yes! If you own this DLC already then you get VirtualHere for Android for no extra cost.

INSTRUCTIONS FOR RUNNING THE ANDROID APP

1. Install https://play.google.com/store/apps/details?id=com.virtualhere.androidse… on your Android Device.
2. Thats it! No need to Open or Start the VirtualHere Android App, or do anything else

The Steam Link Android App will automatically detect that VirtualHere is installed and add a "VirtualHere" option to the settings.

There you select the device you want to use via VirtualHere and start streaming.

https://steamcommunity.com/app/440520/discussions/0/358416640399205034

Please clarify status of my old life time licence and what is exactly needed to use VH on android using Steam version of VH as the info in that old VH for Steam link thread totally conflicts with the info on Google Play Store for VH server on android.

#3

After trying VH for Steam Link xbox controller does stay connected so is unusable.

should read

After trying VH for Steam Link xbox controller does NOT stay connected so is unusable.
#4

Nothing much has changed, it still works the same way as it always did regarding licensing. The Steam Linux/SteamOS support i removed it because it wasnt working and no one was using it.

The only thing i had to change recently was to use google playstore to take payments via the app rather than people having to use my website to pay for the app. Although you can still use my website to purchase the app too

Any purchased license keys work as before. If that is not the case then that is a bug and email me and i can figure it out.

#5

Thanks for clarifying. It more likely PEBCAK and i am doing something wrong. Have reached out via email asking about key for standalone server and havent worked out how to get Xbox One controller for PC (have no dongle) working with USB cable through VH for Steam Link yet either. Dont get any useful message in client but think server system messages are showing info that may help.

--------- beginning of main
07-12 11:12:48.312 25592 14306 I vhusbd : Mon Jul 12 11:12:48 2021 LOG_INFO 192.168.1.91 connected as connection 118
07-12 11:12:49.345 25592 14306 I vhusbd : Mon Jul 12 11:12:49 2021 LOG_INFO Device 1098 [045e:02ea] BOUND to connection 118
07-12 11:12:50.215 25592 14306 I vhusbd : Mon Jul 12 11:12:50 2021 LOG_INFO Device 1098 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:12:50.215 25592 14306 I vhusbd : Mon Jul 12 11:12:50 2021 LOG_INFO Unmanaging device 1098 [045e:02ea]
07-12 11:12:50.669 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@d69ecea
07-12 11:12:50.678 25592 14306 I vhusbd : Mon Jul 12 11:12:50 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1100
07-12 11:12:53.818 25592 14306 I vhusbd : Mon Jul 12 11:12:53 2021 LOG_INFO Device 1100 [045e:02ea] BOUND to connection 118
07-12 11:12:54.689 25592 14306 I vhusbd : Mon Jul 12 11:12:54 2021 LOG_INFO Device 1100 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:12:54.689 25592 14306 I vhusbd : Mon Jul 12 11:12:54 2021 LOG_INFO Unmanaging device 1100 [045e:02ea]
07-12 11:12:55.115 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@9fcfd8e
07-12 11:12:55.119 25592 14306 I vhusbd : Mon Jul 12 11:12:55 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1101
07-12 11:12:56.865 25592 14306 I vhusbd : Mon Jul 12 11:12:56 2021 LOG_INFO Device 1101 [045e:02ea] BOUND to connection 118
07-12 11:12:57.732 25592 14306 I vhusbd : Mon Jul 12 11:12:57 2021 LOG_INFO Device 1101 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:12:57.732 25592 14306 I vhusbd : Mon Jul 12 11:12:57 2021 LOG_INFO Unmanaging device 1101 [045e:02ea]
07-12 11:12:58.155 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@2badfa7
07-12 11:12:58.159 25592 14306 I vhusbd : Mon Jul 12 11:12:58 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1102
07-12 11:12:59.870 25592 14306 I vhusbd : Mon Jul 12 11:12:59 2021 LOG_INFO Device 1102 [045e:02ea] BOUND to connection 118
07-12 11:13:00.735 25592 14306 I vhusbd : Mon Jul 12 11:13:00 2021 LOG_INFO Device 1102 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:13:00.735 25592 14306 I vhusbd : Mon Jul 12 11:13:00 2021 LOG_INFO Unmanaging device 1102 [045e:02ea]
07-12 11:13:01.200 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@808d1ec
07-12 11:13:01.210 25592 14306 I vhusbd : Mon Jul 12 11:13:01 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1103
07-12 11:13:01.233 25592 25600 W System : A resource failed to call close.
07-12 11:13:01.234 25592 25600 I chatty : uid=10110(com.virtualhere.androidserver) FinalizerDaemon identical 25 lines
07-12 11:13:01.234 25592 25600 W System : A resource failed to call close.
07-12 11:13:02.837 25592 14306 I vhusbd : Mon Jul 12 11:13:02 2021 LOG_INFO Device 1103 [045e:02ea] BOUND to connection 118
07-12 11:13:03.710 25592 14306 I vhusbd : Mon Jul 12 11:13:03 2021 LOG_INFO Device 1103 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:13:03.710 25592 14306 I vhusbd : Mon Jul 12 11:13:03 2021 LOG_INFO Unmanaging device 1103 [045e:02ea]
07-12 11:13:04.111 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@922a6d
07-12 11:13:04.119 25592 14306 I vhusbd : Mon Jul 12 11:13:04 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1104
07-12 11:13:05.837 25592 14306 I vhusbd : Mon Jul 12 11:13:05 2021 LOG_INFO Device 1104 [045e:02ea] BOUND to connection 118
07-12 11:13:06.707 25592 14306 I vhusbd : Mon Jul 12 11:13:06 2021 LOG_INFO Device 1104 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:13:06.707 25592 14306 I vhusbd : Mon Jul 12 11:13:06 2021 LOG_INFO Unmanaging device 1104 [045e:02ea]
07-12 11:13:07.109 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@8b537fa
07-12 11:13:07.113 25592 14306 I vhusbd : Mon Jul 12 11:13:07 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1105
07-12 11:13:08.829 25592 14306 I vhusbd : Mon Jul 12 11:13:08 2021 LOG_INFO Device 1105 [045e:02ea] BOUND to connection 118
07-12 11:13:09.700 25592 14306 I vhusbd : Mon Jul 12 11:13:09 2021 LOG_INFO Device 1105 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:13:09.700 25592 14306 I vhusbd : Mon Jul 12 11:13:09 2021 LOG_INFO Unmanaging device 1105 [045e:02ea]
07-12 11:13:10.121 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@efa2b23
07-12 11:13:10.126 25592 14306 I vhusbd : Mon Jul 12 11:13:10 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1106
07-12 11:13:11.834 25592 14306 I vhusbd : Mon Jul 12 11:13:11 2021 LOG_INFO Device 1106 [045e:02ea] BOUND to connection 118
07-12 11:13:12.708 25592 14306 I vhusbd : Mon Jul 12 11:13:12 2021 LOG_INFO Device 1106 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:13:12.708 25592 14306 I vhusbd : Mon Jul 12 11:13:12 2021 LOG_INFO Unmanaging device 1106 [045e:02ea]
07-12 11:13:13.113 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@7c3eb38
07-12 11:13:13.121 25592 14306 I vhusbd : Mon Jul 12 11:13:13 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1107
07-12 11:13:14.849 25592 14306 I vhusbd : Mon Jul 12 11:13:14 2021 LOG_INFO Device 1107 [045e:02ea] BOUND to connection 118
07-12 11:13:15.722 25592 14306 I vhusbd : Mon Jul 12 11:13:15 2021 LOG_INFO Device 1107 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:13:15.722 25592 14306 I vhusbd : Mon Jul 12 11:13:15 2021 LOG_INFO Unmanaging device 1107 [045e:02ea]
07-12 11:13:16.115 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@bc5e749
07-12 11:13:16.132 25592 14306 I vhusbd : Mon Jul 12 11:13:16 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1108
07-12 11:13:17.853 25592 14306 I vhusbd : Mon Jul 12 11:13:17 2021 LOG_INFO Device 1108 [045e:02ea] BOUND to connection 118
07-12 11:13:18.725 25592 14306 I vhusbd : Mon Jul 12 11:13:18 2021 LOG_INFO Device 1108 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:13:18.725 25592 14306 I vhusbd : Mon Jul 12 11:13:18 2021 LOG_INFO Unmanaging device 1108 [045e:02ea]
07-12 11:13:19.146 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@53eb326
07-12 11:13:19.152 25592 14306 I vhusbd : Mon Jul 12 11:13:19 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1109
07-12 11:13:19.187 25592 25600 W System : A resource failed to call close.
07-12 11:13:19.188 25592 25600 W System : A resource failed to call close.
07-12 11:13:20.837 25592 14306 I vhusbd : Mon Jul 12 11:13:20 2021 LOG_INFO Device 1109 [045e:02ea] BOUND to connection 118
07-12 11:13:21.711 25592 14306 I vhusbd : Mon Jul 12 11:13:21 2021 LOG_INFO Device 1109 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:13:21.711 25592 14306 I vhusbd : Mon Jul 12 11:13:21 2021 LOG_INFO Unmanaging device 1109 [045e:02ea]
07-12 11:13:22.111 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@d25005f
07-12 11:13:22.119 25592 14306 I vhusbd : Mon Jul 12 11:13:22 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1110
07-12 11:13:23.834 25592 14306 I vhusbd : Mon Jul 12 11:13:23 2021 LOG_INFO Device 1110 [045e:02ea] BOUND to connection 118
07-12 11:13:24.705 25592 14306 I vhusbd : Mon Jul 12 11:13:24 2021 LOG_INFO Device 1110 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:13:24.705 25592 14306 I vhusbd : Mon Jul 12 11:13:24 2021 LOG_INFO Unmanaging device 1110 [045e:02ea]
07-12 11:13:25.140 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@3074344
07-12 11:13:25.146 25592 14306 I vhusbd : Mon Jul 12 11:13:25 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1111
07-12 11:13:26.921 25592 14306 I vhusbd : Mon Jul 12 11:13:26 2021 LOG_INFO Device 1111 [045e:02ea] BOUND to connection 118
07-12 11:13:27.795 25592 14306 I vhusbd : Mon Jul 12 11:13:27 2021 LOG_INFO Device 1111 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:13:27.795 25592 14306 I vhusbd : Mon Jul 12 11:13:27 2021 LOG_INFO Unmanaging device 1111 [045e:02ea]
07-12 11:13:28.226 25592 14306 I vhusbd : Mon Jul 12 11:13:28 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1112
07-12 11:13:28.226 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@1213e5
07-12 11:13:29.877 25592 14306 I vhusbd : Mon Jul 12 11:13:29 2021 LOG_INFO Device 1112 [045e:02ea] BOUND to connection 118
07-12 11:13:31.493 25592 14306 I vhusbd : Mon Jul 12 11:13:31 2021 LOG_INFO Device 1112 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:13:31.493 25592 14306 I vhusbd : Mon Jul 12 11:13:31 2021 LOG_INFO Unmanaging device 1112 [045e:02ea]
07-12 11:13:31.911 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@8121b12
07-12 11:13:31.916 25592 14306 I vhusbd : Mon Jul 12 11:13:31 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1113
07-12 11:13:32.925 25592 14306 I vhusbd : Mon Jul 12 11:13:32 2021 LOG_INFO Device 1113 [045e:02ea] BOUND to connection 118
07-12 11:13:34.532 25592 14306 I vhusbd : Mon Jul 12 11:13:34 2021 LOG_INFO Device 1113 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:13:34.533 25592 14306 I vhusbd : Mon Jul 12 11:13:34 2021 LOG_INFO Unmanaging device 1113 [045e:02ea]
07-12 11:13:34.957 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@5701b5b
07-12 11:13:34.969 25592 14306 I vhusbd : Mon Jul 12 11:13:34 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1114
07-12 11:13:35.865 25592 14306 I vhusbd : Mon Jul 12 11:13:35 2021 LOG_INFO Device 1114 [045e:02ea] BOUND to connection 118
07-12 11:13:37.464 25592 14306 I vhusbd : Mon Jul 12 11:13:37 2021 LOG_INFO Device 1114 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:13:37.464 25592 14306 I vhusbd : Mon Jul 12 11:13:37 2021 LOG_INFO Unmanaging device 1114 [045e:02ea]
07-12 11:13:37.896 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@3846610
07-12 11:13:37.901 25592 14306 I vhusbd : Mon Jul 12 11:13:37 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1115
07-12 11:13:37.953 25592 25600 W System : A resource failed to call close.
07-12 11:13:37.954 25592 25600 I chatty : uid=10110(com.virtualhere.androidserver) FinalizerDaemon identical 16 lines
07-12 11:13:37.954 25592 25600 W System : A resource failed to call close.
07-12 11:13:38.877 25592 14306 I vhusbd : Mon Jul 12 11:13:38 2021 LOG_INFO Device 1115 [045e:02ea] BOUND to connection 118
07-12 11:13:40.491 25592 14306 I vhusbd : Mon Jul 12 11:13:40 2021 LOG_INFO Device 1115 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:13:40.491 25592 14306 I vhusbd : Mon Jul 12 11:13:40 2021 LOG_INFO Unmanaging device 1115 [045e:02ea]
07-12 11:13:40.922 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@aaecc41
07-12 11:13:40.925 25592 14306 I vhusbd : Mon Jul 12 11:13:40 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1116
07-12 11:13:41.885 25592 14306 I vhusbd : Mon Jul 12 11:13:41 2021 LOG_INFO Device 1116 [045e:02ea] BOUND to connection 118
07-12 11:13:43.520 25592 14306 I vhusbd : Mon Jul 12 11:13:43 2021 LOG_INFO Device 1116 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:13:43.520 25592 14306 I vhusbd : Mon Jul 12 11:13:43 2021 LOG_INFO Unmanaging device 1116 [045e:02ea]
07-12 11:13:43.952 25592 14306 I vhusbd : Mon Jul 12 11:13:43 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1117
07-12 11:13:43.954 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@eacdbbe
07-12 11:13:44.913 25592 14306 I vhusbd : Mon Jul 12 11:13:44 2021 LOG_INFO Device 1117 [045e:02ea] BOUND to connection 118
07-12 11:13:46.531 25592 14306 I vhusbd : Mon Jul 12 11:13:46 2021 LOG_INFO Device 1117 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:13:46.532 25592 14306 I vhusbd : Mon Jul 12 11:13:46 2021 LOG_INFO Unmanaging device 1117 [045e:02ea]
07-12 11:13:46.956 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@88df817
07-12 11:13:46.963 25592 14306 I vhusbd : Mon Jul 12 11:13:46 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1118
07-12 11:13:47.889 25592 14306 I vhusbd : Mon Jul 12 11:13:47 2021 LOG_INFO Device 1118 [045e:02ea] BOUND to connection 118
07-12 11:13:49.497 25592 14306 I vhusbd : Mon Jul 12 11:13:49 2021 LOG_INFO Device 1118 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:13:49.498 25592 14306 I vhusbd : Mon Jul 12 11:13:49 2021 LOG_INFO Unmanaging device 1118 [045e:02ea]
07-12 11:13:49.923 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@f8f9f9c
07-12 11:13:49.934 25592 14306 I vhusbd : Mon Jul 12 11:13:49 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1119
07-12 11:13:50.929 25592 14306 I vhusbd : Mon Jul 12 11:13:50 2021 LOG_INFO Device 1119 [045e:02ea] BOUND to connection 118
07-12 11:13:52.524 25592 14306 I vhusbd : Mon Jul 12 11:13:52 2021 LOG_INFO Device 1119 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:13:52.524 25592 14306 I vhusbd : Mon Jul 12 11:13:52 2021 LOG_INFO Unmanaging device 1119 [045e:02ea]
07-12 11:13:52.965 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@657ec5d
07-12 11:13:52.975 25592 14306 I vhusbd : Mon Jul 12 11:13:52 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1120
07-12 11:13:58.045 25592 14306 I vhusbd : Mon Jul 12 11:13:58 2021 LOG_INFO Device 1120 [045e:02ea] BOUND to connection 118
07-12 11:13:59.660 25592 14306 I vhusbd : Mon Jul 12 11:13:59 2021 LOG_INFO Device 1120 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:13:59.660 25592 14306 I vhusbd : Mon Jul 12 11:13:59 2021 LOG_INFO Unmanaging device 1120 [045e:02ea]
07-12 11:13:59.694 25592 25600 W System : A resource failed to call close.
07-12 11:13:59.696 25592 25600 I chatty : uid=10110(com.virtualhere.androidserver) FinalizerDaemon identical 14 lines
07-12 11:13:59.696 25592 25600 W System : A resource failed to call close.
07-12 11:14:00.089 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@135fdce
07-12 11:14:00.090 25592 14306 I vhusbd : Mon Jul 12 11:14:00 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1121
07-12 11:14:04.323 25592 14306 I vhusbd : Mon Jul 12 11:14:04 2021 LOG_INFO Device 1121 [045e:02ea] BOUND to connection 118
07-12 11:14:05.933 25592 14306 I vhusbd : Mon Jul 12 11:14:05 2021 LOG_INFO Device 1121 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:14:05.933 25592 14306 I vhusbd : Mon Jul 12 11:14:05 2021 LOG_INFO Unmanaging device 1121 [045e:02ea]
07-12 11:14:06.337 25592 14306 I vhusbd : Mon Jul 12 11:14:06 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1122
07-12 11:14:06.345 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@aa91039
07-12 11:14:09.745 25592 14306 I vhusbd : Mon Jul 12 11:14:09 2021 LOG_INFO Device 1122 [045e:02ea] BOUND to connection 118
07-12 11:14:10.448 25592 14306 I vhusbd : Mon Jul 12 11:14:10 2021 LOG_INFO Connection 118 remotely disconnected gracefully (rx msg size)
07-12 11:14:10.612 25592 14306 I vhusbd : Mon Jul 12 11:14:10 2021 LOG_INFO Device 1122 [045e:02ea] SURPRISE UNBOUND from connection 118
07-12 11:14:10.612 25592 14306 I vhusbd : Mon Jul 12 11:14:10 2021 LOG_INFO Unmanaging device 1122 [045e:02ea]
07-12 11:14:11.056 25592 25592 W ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@8dd756
07-12 11:14:11.064 25592 14306 I vhusbd : Mon Jul 12 11:14:11 2021 LOG_INFO Found Full speed device [045e:02ea] "Microsoft, Controller" at address 1123
07-12 11:14:19.322 25592 14306 I vhusbd : Mon Jul 12 11:14:19 2021 LOG_INFO Connection 118 successfully removed (reason:timeout)
07-12 11:14:32.322 25592 25600 W System : A resource failed to call close.
07-12 11:14:32.323 25592 25600 I chatty : uid=10110(com.virtualhere.androidserver) FinalizerDaemon identical 7 lines
07-12 11:14:32.323 25592 25600 W System : A resource failed to call close.
07-12 11:15:49.376 25592 25610 E libnvcpl_vendor: NvCplGetAppProfileSettingInt failed to get INvCplHalService
07-12 11:15:49.376 25592 25610 E libnvcpl_vendor: NvCplGetAppProfileSettingInt failed to get INvCplHalService
07-12 11:15:50.971 25592 25610 E libnvcpl_vendor: NvCplGetAppProfileSettingInt failed to get INvCplHalService
07-12 11:15:50.971 25592 25610 E libnvcpl_vendor: NvCplGetAppProfileSettingInt failed to get INvCplHalService

Windows does not recognise usb device when trying to use the VH drivers for xbox one controller when using VH for Steam Link client.

#6

Yes the xbox controllers have never worked via virtualhere directly plugged in. They keep resetting themselves (Note the SURPRISE UNBOUND) messages in the log. That means that the controller has dropped off the USB bus by itself without any virtualhere intervention or the cable being pulled.

You need to use the wireless xbox dongle and use that via virtualhere instead and it will work fine then.