VNC server on Vero4K

Hi, apologies for resurrecting an old thread.

I am struggling to get this working; I had no problems with installation and the session is established but there is no reaction to keyboard or mouse input. Using UltraVNC on Windows 10, also tested RealVNC with the same result.

Console output below:

06/09/2018 17:19:42 Listening for VNC connections on TCP6 port 5900
06/09/2018 17:19:57 Got connection from client 192.168.2.22
06/09/2018 17:19:57   other clients:
06/09/2018 17:19:57 Normal socket connection
06/09/2018 17:19:57 Client Protocol Version 3.8
06/09/2018 17:19:57 Protocol version sent 3.8, using 3.8
06/09/2018 17:19:57 rfbProcessClientSecurityType: executing handler for type 1
06/09/2018 17:19:57 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8
06/09/2018 17:19:58 Pixel format for client 192.168.2.22:
06/09/2018 17:19:58   32 bpp, depth 32, little endian
06/09/2018 17:19:58   true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
06/09/2018 17:19:58 no translation needed
06/09/2018 17:19:58 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000A)
06/09/2018 17:19:58 rfbProcessClientNormalMessage: ignoring unsupported encoding type zlibhex
06/09/2018 17:19:58 Using compression level 6 for client 192.168.2.22
06/09/2018 17:19:58 Enabling full-color cursor updates for client 192.168.2.22
06/09/2018 17:19:58 Enabling cursor position updates for client 192.168.2.22
06/09/2018 17:19:58 Using image quality level 6 for client 192.168.2.22
06/09/2018 17:19:58 Using JPEG subsampling 0, Q79 for client 192.168.2.22
06/09/2018 17:19:58 rfbProcessClientNormalMessage: ignoring unsupported encoding type xorEnable
06/09/2018 17:19:58 Enabling LastRect protocol extension for client 192.168.2.22
06/09/2018 17:19:58 Enabling NewFBSize protocol extension for client 192.168.2.22
06/09/2018 17:19:58 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFF8000)
06/09/2018 17:19:58 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFF8001)
06/09/2018 17:19:58 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFF8004)
06/09/2018 17:19:58 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFF8002)
06/09/2018 17:19:58 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFF8003)
06/09/2018 17:19:58 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xC0A1E5CE)
06/09/2018 17:19:58 Using hextile encoding for client 192.168.2.22

I have Vero (VERSION_ID=“2019.07-1”) I try to run VNC server.
I did:
sudo apt install libvncserver1
sudo wget https://github.com/zjoasan/vnc-vero3/raw/master/aml-vnc -O /usr/bin/aml-vnc
sudo chmod +x /usr/bin/aml-vnc
aml-vnc

VNC server is now runnig :slight_smile:

Then I try connect VNC server from my Win7 box with RealVNC client.
The client show me screen of Vero, but does not respond of mouse or keyboard.
Any suggestion/advice?

1 Like

I’m sorry to say i haven’t had time to keep up with it, there were some changes that were never applied and others were removed so it’s in a flux. Gonna try to get it working again, i have a self compiled version here that keyboard works on (mouse is a lost cause).

Moving the mouse will cause a huge lag so keyboard events will get queued, almost like nothing happens once hte mouse has been moved.

I use VNC client on PC or iPad for display only, and use iPhone app to do the control.

Does this currently work on Vero4k with latest Kodi?

Yes, this is independent of Kodi.

so which commands works with the latest kodi? there were mentioned different libvncserver 0/1 packages and different git repos…

thanks

Try this one, should work.

@fzinken seems that mouse is not responding at all; i can see the screen but no reaction… on the mouse…

26/12/2020 16:24:16 Got connection from client 192.168.1.26
26/12/2020 16:24:16 other clients:
26/12/2020 16:24:16 Normal socket connection
26/12/2020 16:24:16 Client Protocol Version 3.8
26/12/2020 16:24:16 Protocol version sent 3.8, using 3.8
26/12/2020 16:24:16 rfbProcessClientSecurityType: executing handler for type 1
26/12/2020 16:24:16 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8
26/12/2020 16:24:19 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000018)
26/12/2020 16:24:19 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
26/12/2020 16:24:19 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
26/12/2020 16:24:19 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
26/12/2020 16:24:19 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
26/12/2020 16:24:19 Enabling full-color cursor updates for client 192.168.1.26
26/12/2020 16:24:19 Enabling NewFBSize protocol extension for client 192.168.1.26
26/12/2020 16:24:19 Using ZRLE encoding for client 192.168.1.26
26/12/2020 16:24:19 Pixel format for client 192.168.1.26:
26/12/2020 16:24:19 8 bpp, depth 6
26/12/2020 16:24:19 true colour: max r 3 g 3 b 3, shift r 4 g 2 b 0
26/12/2020 16:24:20 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000018)
26/12/2020 16:24:20 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
26/12/2020 16:24:20 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
26/12/2020 16:24:20 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
26/12/2020 16:24:20 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
26/12/2020 16:24:20 Enabling full-color cursor updates for client 192.168.1.26
26/12/2020 16:24:20 Enabling NewFBSize protocol extension for client 192.168.1.26
26/12/2020 16:24:20 Switching from ZRLE to raw Encoding for client 192.168.1.26
26/12/2020 16:24:23 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000018)
26/12/2020 16:24:23 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
26/12/2020 16:24:23 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
26/12/2020 16:24:23 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
26/12/2020 16:24:23 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
26/12/2020 16:24:23 Enabling full-color cursor updates for client 192.168.1.26
26/12/2020 16:24:23 Enabling NewFBSize protocol extension for client 192.168.1.26
26/12/2020 16:24:23 Switching from raw to ZRLE Encoding for client 192.168.1.26
26/12/2020 16:24:23 Pixel format for client 192.168.1.26:
26/12/2020 16:24:23 32 bpp, depth 24, little endian
26/12/2020 16:24:23 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0

Mouse may not work in that version. But why do you need that. Keys would work fine.

hm you said in diff thread>
That version has mouse support. Both should be fine but try the second one first.

True that was my understanding but as all of that is quite a while ago it might be actually the other way around.

its not usable at all, its Laggy, slow, cant do anything remotely at all ;/

While mouse “movement” is disabled, your vnc client still sends mouse actions to the server, which due to a bad implementation of mouse in the code. So even if you dont see the mouse movement, the server actually recives them and has to ignore every mouse event.

So in short, v18 nightly of kodi had issues with virtual mouse for a while, at the same time i noticed the lag effect building up when using mouse on v.17, Disabled any rutine i could around mouse handling, and still lagging if you move your vnc clients mouse. So i Disabled mouse drawing. Couldn’t find any good way of shuting down the listener. I hve since then searched for a VNC client where you can “ignore sending” mouse events. No luck there either.

In short the VNC for Vero4k, is NOT a proffesional solution, but it can help the few times you have to do do some stuff on the Vero4k while the mrs is occuping the TV.

@[plenart. As I said not proffesional grade. I run my vnc-client in window mode, and I dont let my mouse come over that window, i got no lag at all. But if it move even a smitch over the window borders you get 1-30 secs “hang” depending on vnc-client mouse uodates, what the vero4k is running in the background and other factors.

what about other vnc server? like realvnc etc… thx

The issue is the “binding” to the gpu from the vnc server. Not seen any of the major vnc solution providers doing a Linux arm solution There are general solution using Xserver, but there is no Xserver installed on OSMC, by default.

If there’s enough demand we can probably tidy things up – there’s a bit of low hanging fruit in terms of performance improvements.

But I still don’t understand fully what users intend to achieve with this, and until I do, I don’t know what we need to improve.

simply if you have devices in other houses (parents, etc) without onsite access… its hard to manage / setup it remotely via console. thats my use case.

Would like to add to the demand - same use case here. Major reason why I haven’t purchased a Vero 4k for my parent’s place but am running OSMC on a Pi …