-
-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tightvnc Java 2.8.3 won't stay connected to droidVNC-NG 1.3.3 #101
Comments
This might be due to changes in LibVNCServer. You can help debug the problem by trying with LibVNCServer's example server and using git-bisect to track down the change that might cause this. The revisions in question are:
|
I am willing to give this a try if no one more experience can at the moment, but I am not very familar with C, cmake, or LibVNC. I am mostly a Java developer but use to do C++ years ago. I have cloned the repo in ubuntu, I built the project (via https://github.com/LibVNC/libvncserver#how-to-build ), and it is successfully built examples_simple. I assume I just execute pure
Edit:
|
Hmm, then it might have to do with the host platform, i.e. it might only happen when the server is running on ARM instead of x86. I can look into this, but am currently overwhelmed with €€€-work, so this might take a while. |
There is no rush from me. I would assist by checking other versions of the apk to assist narrowing down, but there are no other previous releases attached here, and I can't get the source to compile. |
Thank you, and that being said, there are more .apk's available at https://f-droid.org/packages/net.christianbeier.droidvnc_ng/ - though not all, they seem to make available only the last three... |
Installed the oldest, 1.3.1, and the issue persists there. Stack trace on client side for info:
|
Alright, tried the following which is as close as possible to your setup @rnveach but it works 🤷
Maybe it's the Windows Java? Edit: Just tried with v1.3.3 and am able to reproduce your issue. So it seems v.1.3.4 has this fixed. Are you able to confirm? |
Tentatively closing, feel free to post something if there's new info. |
Sorry for the delay as I was at my job around the clock last week.
I just installed 1.3.5 and yes, it is working now and isn't disconnecting me instantly. I am sorry I did not mentioned I set a password, but I figured that was something trivial. |
Describe the bug
TightVnc 2.8.3 for Java fails to stay connected droidVNC-NG 1.3.3.
While the screen is being displayed (top is partially displayed), the viewer gets: "Unsupported encoding code: -1869469441". The number on unsupported changes on every connection.
To Reproduce
Install droidVNC-NG 1.3.3 from the playstore.
Setup droidVNC-NG and get all permissions granted.
Download tightvnc Java 2.8.3.
Have tightvnc connect to droidVNC-NG.
Exception occurs.
Expected Behavior
Expected to be able to connect to the device with droidVNC-NG 1.3.3 with no exception and be able to control device.
Logs/Backtraces
N/A
Your environment (please complete the following information):
Additional context
Reverting droidVNC-NG back to 1.2.6 while changing nothing else resolves the issue and connection works and is stable. Don't know the specific version that the break occurs in.
The text was updated successfully, but these errors were encountered: