Connection error

[pr4x77]

Hi,

sometimes when I try to connect I get an error using bVNC. I will attach a screenshot. Other VNC clients arent working anymore too then but wont give such an detailed error.

I cant reproduces this error consistently. It just happens sometimes over the day.

• droidVNC-NG version: newest Playstore Version
• Android version: 12
• Client-side OS and version: android 12
• VNC client and version: bVNC but with other clients doesnt work either

Some one can help?

Here is the error:

Thanks!

[bk138]

Looks like there's nothing running on 5900 anymore. What's the output of telnet 192.168.178.250 5900 from some box in the LAN for a working server and then your error case?

[pr4x77]

Couldnt reproduce it by now but it seems that DroidVNC crashed and wasn't running anymore. I will try to reproduce it.

I go another error today. I was able to connect the whole day but after long time running I wasn't able to control anything anymore. I just could only watch the display nothing more. I made a logcat but don't know what I have to look for.

I checked the granted rights and DroidVNC was still running with all rights granted but could control anything. Different VNC Viewers tested.

Could it be this:
03-14 19:47:19.172 634 728 I InputDispatcher: Dropping event because there is no touchable window or gesture monitor at (2147483647, 2147483647) in display 0.
03-14 19:47:19.227 634 728 I InputDispatcher: Dropping event because there is no touched foreground window in display 0 or gesture monitor to receive it.
03-14 19:47:19.271 634 728 I InputDispatcher: Dropping event because there is no touchable window or gesture monitor at (2147483647, 2147483647) in display 0.
03-14 19:47:19.321 634 728 I InputDispatcher: Dropping event because there is no touched foreground window in display 0 or gesture monitor to receive it.
03-14 19:47:19.824 634 728 I InputDispatcher: Dropping event because there is no touchable window or gesture monitor at (2147483647, 2147483647) in display 0.
03-14 19:47:19.872 634 728 I InputDispatcher: Dropping event because there is no touched foreground window in display 0 or gesture monitor to receive it.
03-14 19:47:19.926 634 728 I InputDispatcher: Dropping event because there is no touchable window or gesture monitor at (2147483647, 2147483647) in display 0.
03-14 19:47:19.978 634 728 I InputDispatcher: Dropping event because there is no touched foreground window in display 0 or gesture monitor to receive it.

If yes why it fails after some hours running?

[bk138]

Your other issue sounds like #121 and/or #113.

[pr4x77]

I don't have any OutOfMemoryException as mentioned in #113

Is there a fix or a way to test for #121 ? I already tried different vnc viewers like bVNC, Multi VNC, Ultra VNC, Tightvnc. None of them is able to control the device.

Just to give more details, the screen isn't freezed. I can watch the display change using the vnc connection if I control it locally after the problem occurs. Im just not able to take any action.

[pr4x77]

3-14 19:38:23.363 634 661 W DisplayManagerService: Display DisplayDeviceInfo{"droidVNC-NG": uniqueId="virtual:net.christianbeier.droidvnc_ng,10089,droidVNC-NG,0", 1280 x 800, modeId 9, defaultModeId 9, supportedModes [{id=9, width=1280, height=800, fps=60.0, alternativeRefreshRates=[]}], colorMode 0, supportedColorModes [0], hdrCapabilities null, allmSupported false, gameContentTypeSupported false, density 244, 244.0 x 244.0 dpi, appVsyncOff 0, presDeadline 16666666, touch NONE, rotation 0, type VIRTUAL, deviceProductInfo null, state ON, owner net.christianbeier.droidvnc_ng (uid 10089), frameRateOverride , brightnessMinimum 0.0, brightnessMaximum 0.0, brightnessDefault 0.0, FLAG_PRIVATE, FLAG_PRESENTATION} does not support input device matching.

Gives out a resolution of 1280x800 but my device running droidVNC is connected to a monitor using 1920x1080. Could this cause the error?

[bk138]

Just saw that I owed you an answer. No, different resolutions should not pose a problem. The only thing I can think of is to gather more info by means of debug logs...

[bk138]

@pr4x77 can you check if the problem persists with the newest version?

[bk138]

Tentatively closing, please post here in case there is new info.