search

toryl / android-vnc-server

Automatically exported from code.google.com/p/android-vnc-server
0 stars 0 forks source link

The screen is garbled on Samsung Galaxy 5 #23

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
I'm running tightvncviewer on Ubuntu Linux 10.04.2 accessing the device over 
the wifi. I am able to access it but all I can see is a garbled screen as in 
the attached screenshot. The log of androidvncserver can be seen below and the 
raw framebuffer contents is also attached.

I tried several different configurations on the client side but none worked. 
Could you please help?

Euler

------------------- log follows ------------------------------------

Initializing framebuffer device /dev/graphics/fb0...
xres=240, yres=320, xresv=240, yresv=640, xoffs=0, yoffs=0, bpp=32
Initializing keyboard device /dev/input/event3 ...
Initializing touch device /dev/input/event1 ...
Initializing VNC server:
    width:  240
    height: 320
    bpp:    32
    port:   5901
Initializing server...
25/02/2011 07:46:42 Listening for VNC connections on TCP port 5901
$ 25/02/2011 07:47:32 Got connection from client 192.168.0.237
25/02/2011 07:47:32   other clients:
25/02/2011 07:47:32 Client Protocol Version 3.8
25/02/2011 07:47:32 Protocol version sent 3.8, using 3.8
Dirty page: 240x320+0+0...
25/02/2011 07:47:32 rfbProcessClientSecurityType: executing handler for type 1
25/02/2011 07:47:32 rfbProcessClientSecurityType: returning securityResult for 
client rfb version >= 3.8
25/02/2011 07:47:34 Pixel format for client 192.168.0.237:
25/02/2011 07:47:34   32 bpp, depth 24, little endian
25/02/2011 07:47:34   true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
25/02/2011 07:47:34 Using compression level 1 for client 192.168.0.237
25/02/2011 07:47:34 Using image quality level 6 for client 192.168.0.237
25/02/2011 07:47:34 Enabling X-style cursor updates for client 192.168.0.237
25/02/2011 07:47:34 Enabling full-color cursor updates for client 192.168.0.237
25/02/2011 07:47:34 Enabling cursor position updates for client 192.168.0.237
25/02/2011 07:47:34 Enabling LastRect protocol extension for client 
192.168.0.237
25/02/2011 07:47:34 Using tight encoding for client 192.168.0.237
Dirty page: 240x18+0+12...
Dirty page: 240x280+0+40...
Dirty page: 240x280+0+40...
Dirty page: 240x320+0+0...
Dirty page: 240x320+0+0...
Dirty page: 240x108+0+212...
Dirty page: 240x63+0+256...
Dirty page: 240x308+0+12...
Dirty page: 240x152+0+168...
Dirty page: 240x111+0+209...
Dirty page: 240x313+0+7...
Dirty page: 240x108+0+212...
Dirty page: 240x57+0+263...
Dirty page: 240x110+0+210...
Dirty page: 240x313+0+7...
Dirty page: 240x280+0+40...
Dirty page: 240x280+0+40...
Dirty page: 240x280+0+40...
Dirty page: 240x313+0+7...
Dirty page: 240x27+0+40...
25/02/2011 07:48:24 Client 192.168.0.237 gone
25/02/2011 07:48:24 Statistics             events    Transmit/ RawEquiv ( saved)
25/02/2011 07:48:24  FramebufferUpdate   :     21 |         0/        0 (  0.0%)
25/02/2011 07:48:24  LastRect            :     21 |       252/      252 (  0.0%)
25/02/2011 07:48:24  tight               :    521 |    352411/  4192812 ( 91.6%)
25/02/2011 07:48:24  PointerPos          :      1 |        12/       12 (  0.0%)
25/02/2011 07:48:24  RichCursor          :      1 |       255/      255 (  0.0%)
25/02/2011 07:48:24  TOTALS              :    565 |    352930/  4193331 ( 91.6%)
25/02/2011 07:48:24 Statistics             events    Received/ RawEquiv ( saved)
25/02/2011 07:48:24  PointerEvent        :    257 |      1542/     1542 (  0.0%)
25/02/2011 07:48:24  FramebufferUpdate   :     22 |       220/      220 (  0.0%)
25/02/2011 07:48:24  SetEncodings        :      1 |        52/       52 (  0.0%)
25/02/2011 07:48:24  SetPixelFormat      :      1 |        20/       20 (  0.0%)
25/02/2011 07:48:24  TOTALS              :    281 |      1834/     1834 (  0.0%)

Original issue reported on code.google.com by eulerdgr...@gmail.com on 25 Feb 2011 at 11:26

Attachments:

GoogleCodeExporter commented 8 years ago 
Seeing the same issue on SE X10mini.

Original comment by conrad....@gmail.com on 4 May 2011 at 11:46

GoogleCodeExporter commented 8 years ago 
Try installing androidvncserver from this location:  
https://github.com/oNaiPs/droid-VNC-server/tree/master/res/raw

It is from the Android App VNC Server and clears up a similar issue in my 
device (BeagleBoard).

Original comment by jonyoung...@gmail.com on 13 Jun 2011 at 1:48

Attachments:

GoogleCodeExporter commented 8 years ago 
This might be the cause:

http://code.google.com/p/android-vnc-server/source/browse/trunk/fbvncserver.c

Line 191:   /* TODO: This assumes scrinfo.bits_per_pixel is 16. */
Line 192:   vncscr = rfbGetScreen(&argc, argv, scrinfo.xres, scrinfo.yres, 5, 
2, 2);

As you can see the screen is always initialized for 16-bit color depth. All 
devices that do not work use 32-bit depth.

Too bad this project seems to be abandoned and not maintained any more...

Original comment by robert.p...@gmail.com on 21 Jul 2011 at 9:05

GoogleCodeExporter commented 8 years ago 
m having the same problem on samsung galaxy pop gt-s5570. Any solutions for 
this? 

vnc viewer screenshot is attached

Original comment by nkbspidy...@gmail.com on 18 Sep 2013 at 9:55

Attachments: