search

bk138 / droidVNC-NG

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

Service not able to start #179

Closed ntropia2 closed 7 months ago

ntropia2 commented 7 months ago

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 The app does not start after assigning all permissions.

To Reproduce

  1. Provide permissions for Input and Notifications
  2. "Screen capturing" stays grayed out as "unknown", but the start button is active. Screenshot_20231123_094116_droidVNC-NG
  3. press the Start button, and a confirmation is shown to allow the app to start casting: Screenshot_20231123_094051_Finder
  4. accept by pressing "Start now"
  5. the service is not started

Expected Behavior

The service should start.

Your environment (please complete the following information):

bk138 commented 7 months ago

The app was tested successfully on an S21FE :thinking:

ntropia2 commented 7 months ago

Took me a while but I finally had the time to test it.

And this is odd. I've tried ScreenRecorder and it worked fine, but DroidVNC had the same behavior (Screen Capturing: UNKNOWN).

Then I've installed and configured LogCat, and when opened the VNC server two things changed:

I reissued the input permissions (Accessibility) and it worked.

No idea why or how that fixed it since I've tried multiple things before this (including rebooting), but this did it. The only thing that changed from earlier was that I had enabled the remote debugging port (adb tcpip 5555) while developer mode was already enabled. Again, no idea, but following this procedure somehow fixed it.

Thanks for looking into it, hopefully this might help someone else with similar issues.