search

bk138 / droidVNC-NG

VNC server app for Android that does not require root privileges.
GNU General Public License v2.0
1.32k stars 187 forks source link

Inputs not working after some time #241

Open master255 opened 4 days ago

master255 commented 4 days ago

Steps to reproduce the behavior:

  1. Install droidVNC-NG 2.7.2 from Play market.
  2. Launch. Give all necessary permissions.
  3. From another computer check that all permissions are available and working.
  4. Do not open this phone for 2 days. Do not use this phone. But it should work and be on charge.
  5. The permission to click the mouse is gone.

Expected Behavior The permission to click the mouse is present

Your environment (please complete the following information):

bk138 commented 3 days ago

re #88 #38

bk138 commented 3 days ago

@master255 Few questions:

master255 commented 3 days ago

@bk138

  1. Right! I checked. The permission is still in the system and it's enabled. But mouse clicks don't work (from any vnc viewer)
  2. DroidVNC-NG is enabled
  3. The logcat is erased very quickly. It stores data for the last few minutes. And there is no data about input disconnection.
master255 commented 3 days ago

@bk138 I found a error, when I tap on my phone screen and nothing works, then this error occurs: MotionEventInjector installation timed out image

When I hit stop in the management console and go to settings where permissions are listed, the permissions there are turned off.

bk138 commented 2 days ago

Hm, https://www.google.com/search?q=%22MotionEventInjector+installation+timed+out%22 doesn't list anything helpful, at least for me. I figure we'd need a complete logcat dump over time. You can use something like adb shell logcat > logcat.txt to dump to a file.

master255 commented 1 day ago

@bk138 I think your program should disconnect and destroy your service on the onDetach() event and reconnect it on the onCreateView event. In my application, if I don't do this, the service stops working. This is a result of Doze mode.

bk138 commented 17 hours ago

@bk138 I think your program should disconnect and destroy your service on the onDetach() event and reconnect it on the onCreateView event. In my application, if I don't do this, the service stops working. This is a result of Doze mode.

Well the server is supposed to keep running without a UI, that's why there's a ForegroundService; no onDetach() nor onCreateView() there...

master255 commented 14 hours ago

We need to test DOZE mode. There are special commands for testing.