Problem with Android server (licenced) - Works for about 3-5 minutes then suddenly stops working

Hello

After some confusion i bought the Android server licence and it seems to working fine.

Im not using SSL.

I have both "keep wifi on" and "keep awake" checked in the virtualhere app.

I then minimize the app and launch moonlight client for stream to my computer.

Everything works fine for a while (even though the mouse sensitivity is pretty awful, any way to fix this? =S), but after a few minutes i can hear my client disconnecting my USB-inputs. Only way to get it working is pull out the OTG from the phone and reinsert it.

Pretty annoying when it happens like every few minutes and will definitly ruin my gaming in a pinch.

Any ideas what i can do to fix this?

Specs:
Oneplus 7 pro latest android OS
All battery saving disabled for virtualhere
Using stable Wifi, connecting via reverse client

Client: Latest win 10 pc at home, connecting via WAN

#2

In the virtualhere app, can you click the menu at the top right then go to system messages, copy to clipboard and paste into this forum

#3

--------- beginning of system
07-03 13:57:18.237 28358 28358 W ViewRootImpl[GUI]: Dropping event due to no window focus: MotionEvent { action=ACTION_MOVE, actionButton=0, id[0]=0, x[0]=625.5, y[0]=2509.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x1, edgeFlags=0x0, pointerCount=1, historySize=2, eventTime=562054490, downTime=562054332, deviceId=7, source=0x1002 }
07-03 13:57:18.248 28358 28358 W ViewRootImpl[GUI]: Dropping event due to no window focus: MotionEvent { action=ACTION_MOVE, actionButton=0, id[0]=0, x[0]=636.0, y[0]=2477.5, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x1, edgeFlags=0x0, pointerCount=1, historySize=1, eventTime=562054498, downTime=562054332, deviceId=7, source=0x1002 }
07-03 13:57:18.249 28358 28358 W ViewRootImpl[GUI]: Cancelling event due to no window focus: MotionEvent { action=ACTION_CANCEL, actionButton=0, id[0]=0, x[0]=632.0, y[0]=2495.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x1, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=562054502, downTime=562054332, deviceId=7, source=0x1002 }
07-03 13:57:18.249 28358 28358 I chatty : uid=10211(com.virtualhere.androidserver) identical 1 line
07-03 13:57:18.249 28358 28358 W ViewRootImpl[GUI]: Cancelling event due to no window focus: MotionEvent { action=ACTION_CANCEL, actionButton=0, id[0]=0, x[0]=632.0, y[0]=2495.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x1, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=562054502, downTime=562054332, deviceId=7, source=0x1002 }
--------- beginning of main
07-03 14:01:28.488 28358 11054 I vhusbd : Wed Jul 3 14:01:28 2019 LOG_INFO Device 1003 [046d:c52b] UNBOUND from connection 1
07-03 14:01:29.499 28358 11054 I vhusbd : Wed Jul 3 14:01:29 2019 LOG_INFO Connection 1 successfully removed (reason:timeout)
07-03 14:01:37.682 28358 11054 I vhusbd : Wed Jul 3 14:01:37 2019 LOG_INFO 90.236.89.19 connected as connection 3
07-03 14:01:38.158 28358 11054 I vhusbd : Wed Jul 3 14:01:38 2019 LOG_INFO Device 1003 [046d:c52b] BOUND to connection 3
07-03 14:01:44.750 28358 11797 D DecorView: onWindowFocusChangedFromViewRoot hasFocus: true, DecorView@69952c4[GUI]
07-03 14:01:45.744 28358 28373 E libc : Access denied finding property "persist.vendor.fps.history.enabled"
07-03 14:01:45.744 28358 28373 E libc : Access denied finding property "persist.vendor.hwui.skia.multithread.enabled"
07-03 14:01:45.745 28358 28373 E libc : Access denied finding property "persist.vendor.hwui.skia.reduce.overdraw.enabled"
07-03 14:01:45.781 28358 28373 E libc : Access denied finding property "persist.vendor.hwui.skia.multithread.enabled"
07-03 14:01:45.781 28358 28373 E libc : Access denied finding property "persist.vendor.hwui.skia.reduce.overdraw.enabled"
07-03 14:01:45.860 28358 28358 D OnePlusJankManager: Chor uploadMDM JANK_TYPE_NODRAW mViewTitle = com.virtualhere.androidserver/com.virtualhere.androidserver.GUI--- jank level = 1

#4

It also makes the sound like you disconnect a usb from a windows, only works if i remove the OTG and plug it back in, then the "new usb-device-sound" plays and it works for a few minutes

#5

OK your connection is dropping. Are you on ethernet or wifi? I think you need to use ethernet cable if you can

#6

Client is on stable ethernet, android server is on stable wifi and im not moving. The connection is absolutley fine since im using moonlight to stream waaay more data than virtualhere is using without any problems..

#7

Is that all of the log? Usually the log is much longer than that. All i can see is "connection timeout" but im looking for a SURPRISE UNBOUND or something like that.

#8

The log i linked is everything that is in the log on the server, but this is the log from the client that happens the exact same moment i lose control:
The description for Event ID 1 from source VirtualHere Client USB Sharing cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Server ping timeout, shutting down connection 4...

The request is not supported

--------------------------------

The description for Event ID 1 from source VirtualHere Client USB Sharing cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Connection 4 socket closed (rx)

The request is not supported

#9

I uninstalled the service on my client and tried running it without service, exact same problem, here is the client log:

2019-07-04 10:55:03 INFO :VirtualHere Client 4.7.9 starting (Compiled: Jun 21 2019 16:11:22)
2019-07-04 10:55:03 INFO :Client OS is Windows 10 (build 17763), 64-bit edition
2019-07-04 10:55:03 INFO :Using config at C:\Users\h4kk3\AppData\Roaming\vhui.ini
2019-07-04 10:55:03 INFO :IPC available at \\.\pipe\vhclient
2019-07-04 10:55:03 INFO :Auto-find (Bonjour) on
2019-07-04 10:55:03 INFO :Auto-find (Bonjour SSL) on
2019-07-04 10:55:03 INFO :ReverseLookupService listening on port 7573 (IPv6 dual-stack)
2019-07-04 10:55:03 INFO :SSLReverseLookupService listening on port 7572 (IPv6 dual-stack)
2019-07-04 10:55:24 INFO :Drivers are up-to-date
2019-07-04 10:55:24 INFO :Connected to the VirtualHere Client Driver (Version 2)
2019-07-04 10:59:42 INFO :Server ping timeout, shutting down connection 1...
2019-07-04 10:59:42 INFO :Connection 1 socket closed (rx)

#10

I changed the ping timeout setting on the client from 10->30 sec, still the same thing happens

#11

Youf network is momentarily dropping.

You can try UDP like this:

1. In the virtualhere client right click on the Android Hub and select Properties->EasyFind->Enable->Not Subscribed
2. Sign up for a one week free trial (no payment needed and no auto-renewal) and follow email instructions
3. Remove the reverse client from the server by opening the VirtualHere client, right clicking the Server -> Reverse Clients..-> Remove
4. Exit and start the client again
5. Put in the EasyFind address and see if it connects ok

See if that provides a more stable connection

#12

Hi again!

I followed all your instructions, got connection working using easyfind instead (which feels a bit more laggy, might be imagining things) but after about 4 minutes same thing happens again. This is the most recent log from the client:

2019-07-05 09:39:23 INFO :VirtualHere Client 4.7.9 starting (Compiled: Jun 21 2019 16:11:22)
2019-07-05 09:39:23 INFO :Client OS is Windows 10 (build 17763), 64-bit edition
2019-07-05 09:39:23 INFO :Using config at C:\Users\h4kk3\AppData\Roaming\vhui.ini
2019-07-05 09:39:23 INFO :IPC available at \\.\pipe\vhclient
2019-07-05 09:39:23 INFO :Auto-find (Bonjour) on
2019-07-05 09:39:23 INFO :Auto-find (Bonjour SSL) on
2019-07-05 09:39:23 INFO :ReverseLookupService listening on port 7573 (IPv6 dual-stack)
2019-07-05 09:39:23 INFO :SSLReverseLookupService listening on port 7572 (IPv6 dual-stack)
2019-07-05 09:39:35 INFO :Drivers are up-to-date
2019-07-05 09:39:35 INFO :Connected to the VirtualHere Client Driver (Version 2)
2019-07-05 09:39:51 INFO :Connection 1 remotely disconnected gracefully (rx)
2019-07-05 09:40:10 INFO :Server ping timeout, shutting down connection 1...
2019-07-05 09:44:14 INFO :Connection 2 remotely disconnected gracefully (rx)
2019-07-05 09:44:32 INFO :Server ping timeout, shutting down connection 2...

#13

OK your connection is definitely dropping for longer than 3 seconds. So you need to somehow get a more reliable connection. Both UDP and TCP are dropping. USB cannot tolerate large latency spikes and i think this is the issue. You can see the latency in the client by right clicking on a server then selecting Properties->Latency.

#14

The thing is the connection is fine, im streaming my screen over moonlight and there is no lag whatsoever, the picture continues to stream fine when virtualhere disconnects my usb-devices. The issue must be on the server, like android killing background apps or something similar? But when i check status bar it still says "virtualhere server running" and looks good when i switch to the virtualhere app. But as i said before, usb-devices wont work until i remove and put the OTG-cable back in, then it starts working again.

#15

Also the timing is to consistent to be latency-lag. Its always exactly the same time, after about 3-4 minutes. Never shorter, never longer

#16

It is interesting that you need to replug the devices to get them to work again. I would have expected to see "SURPRISE UNBOUND" in the server log if the devices were disconnecting themselves after that time. Unless the server log is somehow not showing everything.

Anyway the client shows "connection timeout" as if the connection has dropped so that was my assumption.

If possible do you have a usb hub, perhaps try that between the phone and the device(s) . Maybe there is some power issue which is dropping the usb devices after that 4 minutes and hub in between might provide some buffer. A powered USB hub would be an ideal test.

#17

I have now tried to use my android server as only the server for OTG-usb and nothing else, leaving the virtualhere app open and just locking my phone. I then used a computer for moonlight and i could control my home computer for over 10 minutes without interrupts. So the problem seems to be when i minimize the virtualhere app to the background. Any ideas?

#18

Recent versions of android have really restricted what an app can do in regards to taking resources and running in the foreground. Im thinking its something on your android version. There might be a bug there or something

#19

I have the same issue as well. If I leave my phone with the screen on it works like a charm, right after I lock the screen to save power after couple of minutes the client looses connection to the android server. I turn on the screen on my phone wait around a minute of so and the client finds the server again. Is there some option to force the application to stay active when the phone's screen is turned off?

#20

There is - in the Menu at the top right, "Keep Wifi on" and "Keep Awake"  they are the only settings Android allows to keep connected when power saving. If that still doesnt keep it awake then it must be some issue in android. There are no other options to force it to stay connected.

#21

Ye I have both options turned on "keep wifi" "keep awake". The only way would be to keep my phone charging with the USB connected as well and with the screen on. Not really ideal :/. I wonder how other Android users haven't mentioned that the app doesn't work. I'm using OnePlus nord. Same brand as H4kk3

#22

This works for everyone, thats why i think its probably just some bug in OnePlus. A quick search on google about OnePlus Nord bugs shows its full of them.