Inputs not working after some time

[master255]

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):

• droidVNC-NG version: 2.7.2
• Android version: 8.0
• Client-side OS and version: Windows 10
• VNC client and version: noVnc buildin

[bk138]

re #88 #38

[bk138]

@master255 Few questions:

• You deduce that the permission is gone from droidVNC-NG's Admin Panel?
• Can you please check in Android's a11y if droidVNC-NG is still enabled?
• A logcat dump of the whole thing would be the most helpful!

[master255]

@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]

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

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

[bk138]

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]

@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]

@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]

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

[bk138]

• https://developer.android.com/training/monitoring-device-state/doze-standby#testing_doze_and_app_standby
• https://source.android.com/docs/core/power/platform_mgmt

Findings

Android 12

• enter doze
• leave doze
• noVNC can connect, inputs do work

[master255]

I'm using droidVNC-NG on my always-on Galaxy s8+. And every 1-2 days I have to restart the app and give permissions for remote access to work. This is very uncomfortable.

[bk138]

@master255 you could try https://play.google.com/store/apps/details?id=de.abr.android.avnc for a few days and see if the problem is there as well.

[master255]

@bk138 I can't install it. Play Market says that this program is not compatible with any of my devices. And Apk program is not available anywhere in its pure form.

[master255]

@bk138 I think you need to use a different method of tapping on the screen. It may work through SU, but it will be stable. It is better to make an option to select the method of pressing the screen.

For today. There is not a single program in the world that allows to control an Android device on a local network.

[bk138]

@bk138 I can't install it. Play Market says that this program is not compatible with any of my devices. And Apk program is not available anywhere in its pure form.

https://alpha-vnc-lite.en.aptoide.com/app has an .apk AFAICT.

[master255]

@bk138 I installed it, but it only allows remote access for 10 minutes a day.

[master255]

@bk138 Okay. Just for you, I've started this scam program for testing. Now we have to wait a few days.

[master255]

@bk138 UPD: This program shuts down after 10 minutes of working. It is impossible to test it.

[master255]

@bk138 I think you need to use a different method of tapping on the screen. It may work through SU, but it will be stable. It is better to make an option to select the method of pressing the screen.

For today. There is not a single program in the world that allows to control an Android device on a local network.

So this is the only solution.

[master255]

@bk138 After uninstalling alpha I have this bug started reproducing immediately after launching your program. Now I have no control at all in the latest version from the Play Market.
I checked the logs. There is nothing new there. It seems this problem is not logged at all. But if you have any ideas, I'm willing to give it a try. What to do? The taps don't work at all. Permission to access is constantly requested after stopping the program.

[master255]

Switched to https://github.com/Genymobile/scrcpy
Same functionality but no need to install the app and the performance and picture quality is much better.