Closed elvanowen closed 3 months ago
Seems the InputService has gone. Few questions:
Here is a more complete log if it might be useful for you. (deleted)
Would you be confident to try out some debug apk's I'd post here?
Sure, I can give it a try.
Looks like the InputService gets destroyed by the OS. Are you running any other a11y services?
There were only 2 services running:
# adb shell dumpsys accessibility
...
Bound services:{Service[label=droidVNC-NG, feedbackType[], capabilities=32, eventTypes=TYPE_WINDOWS_CHANGED, notificationTimeout=50, requestA11yBtn=false],
Service[label=Accessibility menu, feedbackType[FEEDBACK_GENERIC], capabilities=8, eventTypes=, notificationTimeout=0, requestA11yBtn=true]}
Enabled services:{{com.android.settings/com.android.settings.accessibility.accessibilitymenu.AccessibilityMenuService}, {net.christianbeier.droidvnc_ng/net.christianbeier.droidvnc_ng.InputService}}
...
I will try to turn off the accessibility menu and see if it fixes the issue.
Maybe one of the many things mentioned in https://github.com/bitwarden/mobile/issues/596 might help?
Tentatively closing, please post here once there is new info available.
If you'd like to put out an incentive for fixing this bug, you can do so at https://issuehunt.io/r/bk138/droidVNC-NG
Describe the bug After a while, VNC input stop working but will still show what is on the screen. Manual control through phone will still be reflected through the VNC, only input from VNC didn't work.
Expected Behavior Expecting VNC input to work
Logs/Backtraces Seeing these NullPointerException errors from logcat:
Your environment (please complete the following information):