Yep,it's really nasty.
But if I want to leverage FULL spice image ability,I have to:
1.Fix the bugs of sigbus in quic.c on Android by rewriting the
pointer-type-cast into memcpy.etc..
2.Then,then,I got the processed image buffer in memory,BUT,HOW can I output
it??? AFAIK,android offer no image
On Wed, Apr 27, 2011 at 04:54:55PM +0800, Shuxiang Lim wrote:
Yep,it's really nasty.
But if I want to leverage FULL spice image ability,I have to:
1.Fix the bugs of sigbus in quic.c on Android by rewriting the
pointer-type-cast into memcpy.etc..
No idea what the problem is, is it a compile
On Wed, Apr 27, 2011 at 5:28 PM, Alon Levy al...@redhat.com wrote:
On Wed, Apr 27, 2011 at 04:54:55PM +0800, Shuxiang Lim wrote:
Yep,it's really nasty.
But if I want to leverage FULL spice image ability,I have to:
1.Fix the bugs of sigbus in quic.c on Android by rewriting the
Released with src .apk files with button-double-click fixed.
--Lin--
On 4/26/11, Shuxiang Lim shohyang...@gmail.com wrote:
Hi,all!
After I workaround the bug input will choke output,I'm glad to
release the USABLE androidSpice-0.1.4 on google code:
Hey Lin,
Just gave it a quick shot :
- DNS resolving not working?
- access to server w/o password not supported?
- access w/ password produces a force kill after a vibration
- some traffic is seen on the spice-server side though
(couldn’t connect therefore)
Any logfiles I can provide?
HW/SW :
Hi,all!
Thanks for the trying/feedbacking and sorry for the nascent itches of the
project.
As I've mentioned in the wiki page of this proj.,to use the androidSpice,
the server should be modified to force the use of JPEG compression,and qemu
should not use -vga qxl and should use -usbdevice
