I just downloaded and built this:
Then ran it on the host as ./simple-tcp-proxy <lan-ip> 5900 127.0.0.1
5900. From there, you can just connect the smartphone to any machine
in the network, and point the VNC viewer at <lan-ip>.
On Jan 15, 7:26 am, Randy <rhall...@yahoo.com
> Great job. I setup android and fbvncserver on my laptop. I can run the
> VNC Viewer on my laptop using localhost and see the Android emulator.
> To run the VNC Viewer on my Moto Q do I need to use a tunneling
> solution to connect the VNC Viewer from the Moto Q using localhost? Is
> there a tunneling solution you would recommend?
> On Dec 28 2007, 7:16 am, Josh Guilfoyle <jast...@gmail.com
> > Screw it. I wrote my own VNC server:http://android-vnc.googlecode.com
> > On Dec 23, 12:55 am, Josh Guilfoyle <jast...@gmail.com
> > > One note here. The protocol implementation is broken in the most
> > > trivial way imaginable. The version handshaking requires that the
> > > server send something like "RFB003.003\n" (specifying protocol
> > > version 3.3). Android's implementation, instead, sends "RFB
> > > 003.003\0". This causes dotnetvnc (the VNC viewer I am using on my
> > > smartphone) to reject the server. Ugh!!
> > > On Dec 23, 12:16 am, Josh Guilfoyle <jast...@gmail.com
> > > > I built a simple TCP proxy and was able to make it work.
> > > > Unfortunately, the VNC protocol implementation is extremely crude and
> > > > will only work if the VNC viewer natively requests a 16 bits-per-pixel
> > > > depth (possibly other restrictions as well, like endianness maybe?).
> > > > But it does work. Keyboard input seems to be fully supported, but I
> > > > am unable to use any other encoding than "raw", which is highly
> > > > inefficient. Specifying anything else causes the platform to implode
> > > > and automatically reboot.
> > > > Further study is needed, though...
> > > > On Dec 22, 11:31 pm, Josh Guilfoyle <jast...@gmail.com
> > > > > Found a little more information. When you connect to 5900 on the
> > > > > emulator, the following line appears in the Android log:
> > > > > D/RFBServer( 463):RFBServer Thread created
> > > > > I searched for this string in the filesystem and found it is
> > > > > implemented in /system/lib/libsurfaceflinger.so, which is exactly
> > > > > where you'd expect a fullRFBimplementation. A quick run of strings
> > > > > and grep over that object shows many relevant symbols implementing
> > > > > what appears to be the main scope of the protocol. Interesting stuff,
> > > > > I will try to design a proxy that will permit me to connect to the
> > > > > server and find out more...
> > > > > On Dec 22, 9:25 pm, Josh Guilfoyle <jast...@gmail.com
> > > > > > I had a thought to create a VNC server for Android so that I could
> > > > > > connect my Windows Mobile smartphone to the Android emulator via the
> > > > > > sync cable and thus test the usability of some of my developing
> > > > > > programs without actually having installed the firmware anywhere. I
> > > > > > started tinkering with creating this server myself but quickly
> > > > > > discovered that port 5900 is already bound inside the emulator, with
> > > > > > apparently a functional protocol implemented that identifies the
> > > > > > desktop as "AndroidRFB".