Releas androidSpice-0.1.3

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:
http://code.google.com/p/spice-client-android/
   All introductions of porting can be found or redirected in the wiki page and my previous blogs about libspicec.so porting.

   The structure of androidSpice:
1.Data layer,extracted from spice-gtk-0.5, the main logic and datatransportation/proccessing of spice protocol,along with all itsdependencies,built statically into libspicec.so
2.Data layer will add two new threads in android-worker.c for the I/Owith 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:

"The damned greatest obstacle I've faced in the portingliesin the structure of Android itself:It has no(at least forversion<2.3 )exposed audio/image output and input API for C(only Java!)! So I haveto transport all the fixed data got from spice-server to Java layer byadding two new threads to handle the I/O communication with Java UI viatwo UNIX-sockets,that's the leg-drawing of speed. Besides, quic.c inclient is buggy of SIGBUS or SIGSEGV on android(anyone can fixit?thx!),I have no better way but to force use of JPEG compression inserver and the client will send jpeg data directly to Java UI foroutput, it's queerand should be condemned('cause Spice's value is in the image processingability)"

So now It just WORKS,but works badly, the first untolerable bug is this

Bug1:If press fast on the device the spice-server as well as theandroid-spice-client will be choked and no image updates will be sentout from server.
I'm still working on this bug,I need help!