Hi,all! I'm happy to release the experimental androidSpice under LGPL,welcome to improve! The source and wiki now dwell in google code site here: <a href="http://code.google.com/p/spice-client-android/">http://code.google.com/p/spice-client-android/</a> All introductions of porting can be found or redirected in the wiki page. The structure of androidSpice: 1.Data layer,extracted from spice-gtk-0.5, the main logic and data transportation/proccessing of spice protocol,along with all its dependencies,built statically into libspicec.so 2.Data layer will add two new threads in android-worker.c for the I/O with Java UI layer via UNIX-sockets(see the PROBLEMS below) 3.UI layer,rewritten in Java. Output the Images and capture user-input events and communicate with libspicec.so. PROBLEMS: <blockquote>"The damned greatest obstacle I've faced in the porting lies in the structure of Android itself:It has no(at least for version<2.3 ) exposed audio/image output and input API for C(only Java!)! So I have to transport all the fixed data got from spice-server to Java layer by adding two new threads to handle the I/O communication with Java UI via two UNIX-sockets,that's the leg-drawing of speed. Besides, quic.c in client is buggy of SIGBUS or SIGSEGV on android(anyone can fix it?thx!),I have no better way but to force use of JPEG compression in server and the client will send jpeg data directly to Java UI for output, it's queer and should be condemned('cause Spice's value is in the image processing ability)" </blockquote>So now It just WORKS,but works badly, the first untolerable bug is this <blockquote>Bug 1:If press fast on the device the spice-server as well as the android-spice-client will be choked and no image updates will be sent out from server. I'm still working on this bug,I need help! </blockquote>Best regards, --林