[Android Apps and Games] Neralun:
Garbled screen on Galaxy Tab

With 1.72, things work as long as I don't use rotation 1 or 3.

With no rotation of screen and rotation 1 of input, I get a working display (although the vncviewer display is rotated 90° to the right; top on Tab is right on display)

Command-line:

./vncs -d 300000 -P 5901 -k uinput -s -T 1

Output:

./vncs Version 1.72
need init
Initializing framebuffer device /dev/graphics/fb0...
--Initializing gingerbread access method--
screenshot info: 32 1024 600 2457600
xres=1024, yres=600, xresv=1024, yresv=1200, xoffs=0, yoffs=600, bpp=32
bInitializing VNC server:
scale: 1
width: 1024
height: 600
bpp: 32
port: 5901
Initializing keyboard device uinput ...
init keyboard device as uinput
---Initializing uinput...---
---Initializing uinput...---
Not using TOUCH_DEVICE because of uinput
Initializing server...
rfbGetScreen bpp: 32
15/04/2012 19:40:37 Listening for VNC connections on TCP port 5901
16 8 8 8 0 8
15/04/2012 19:40:45 Got connection from client 192.168.2.2
15/04/2012 19:40:45 other clients:
15/04/2012 19:40:45 Client Protocol Version 3.8
15/04/2012 19:40:45 Protocol version sent 3.8, using 3.8
15/04/2012 19:40:45 rfbProcessClientSecurityType: executing handler for type 1
15/04/2012 19:40:45 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8
15/04/2012 19:40:45 Pixel format for client 192.168.2.2:
15/04/2012 19:40:45 32 bpp, depth 24, little endian
15/04/2012 19:40:45 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
15/04/2012 19:40:45 Using compression level 1 for client 192.168.2.2
15/04/2012 19:40:45 Using image quality level 6 for client 192.168.2.2
15/04/2012 19:40:45 Enabling X-style cursor updates for client 192.168.2.2
15/04/2012 19:40:45 Enabling full-color cursor updates for client 192.168.2.2
15/04/2012 19:40:45 Enabling cursor position updates for client 192.168.2.2
15/04/2012 19:40:45 Enabling LastRect protocol extension for client 192.168.2.2
15/04/2012 19:40:45 Using tight encoding for client 192.168.2.2
15/04/2012 19:40:47 Client 192.168.2.2 gone
15/04/2012 19:40:47 Statistics events Transmit/ RawEquiv ( saved)
15/04/2012 19:40:47 FramebufferUpdate : 3 | 0/ 0 ( 0.0%)
15/04/2012 19:40:47 LastRect : 3 | 36/ 36 ( 0.0%)
15/04/2012 19:40:47 tight : 385 | 300609/ 5350244 ( 94.4%)
15/04/2012 19:40:47 PointerPos : 1 | 12/ 12 ( 0.0%)
15/04/2012 19:40:47 RichCursor : 1 | 255/ 255 ( 0.0%)
15/04/2012 19:40:47 TOTALS : 393 | 300912/ 5350547 ( 94.4%)
15/04/2012 19:40:47 Statistics events Received/ RawEquiv ( saved)
15/04/2012 19:40:47 FramebufferUpdate : 4 | 40/ 40 ( 0.0%)
15/04/2012 19:40:47 SetEncodings : 1 | 52/ 52 ( 0.0%)
15/04/2012 19:40:47 SetPixelFormat : 1 | 20/ 20 ( 0.0%)
15/04/2012 19:40:47 TOTALS : 6 | 112/ 112 ( 0.0%)

If I use rotation 3 (which would put the top of the Tab to the top of the vncviewer display), I still get a garbled screen. Same with -r 1.

Command-line:

./vncs -d 300000 -P 5901 -k uinput -s -T 1 -r 3

Output:

./vncs Version 1.72
need init
Initializing framebuffer device /dev/graphics/fb0...
--Initializing gingerbread access method--
screenshot info: 32 1024 600 2457600
xres=1024, yres=600, xresv=1024, yresv=1200, xoffs=0, yoffs=0, bpp=32
bInitializing VNC server:
scale: 1
width: 1024
height: 600
bpp: 32
port: 5901
Initializing keyboard device uinput ...
init keyboard device as uinput
---Initializing uinput...---
---Initializing uinput...---
Not using TOUCH_DEVICE because of uinput
Initializing server...
rfbGetScreen bpp: 32
15/04/2012 19:44:50 Listening for VNC connections on TCP port 5901
16 8 8 8 0 8
15/04/2012 19:44:51 Got connection from client 192.168.2.2
15/04/2012 19:44:51 other clients:
15/04/2012 19:44:51 Client Protocol Version 3.8
15/04/2012 19:44:51 Protocol version sent 3.8, using 3.8
15/04/2012 19:44:51 rfbProcessClientSecurityType: executing handler for type 1
15/04/2012 19:44:51 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8
15/04/2012 19:44:51 Pixel format for client 192.168.2.2:
15/04/2012 19:44:51 32 bpp, depth 24, little endian
15/04/2012 19:44:51 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
15/04/2012 19:44:51 Using compression level 1 for client 192.168.2.2
15/04/2012 19:44:51 Using image quality level 6 for client 192.168.2.2
15/04/2012 19:44:51 Enabling X-style cursor updates for client 192.168.2.2
15/04/2012 19:44:51 Enabling full-color cursor updates for client 192.168.2.2
15/04/2012 19:44:51 Enabling cursor position updates for client 192.168.2.2
15/04/2012 19:44:51 Enabling LastRect protocol extension for client 192.168.2.2
15/04/2012 19:44:51 Using tight encoding for client 192.168.2.2
15/04/2012 19:44:56 Client 192.168.2.2 gone
15/04/2012 19:44:56 Statistics events Transmit/ RawEquiv ( saved)
15/04/2012 19:44:56 FramebufferUpdate : 2 | 0/ 0 ( 0.0%)
15/04/2012 19:44:56 LastRect : 2 | 24/ 24 ( 0.0%)
15/04/2012 19:44:56 tight : 305 | 325731/ 4918860 ( 93.4%)
15/04/2012 19:44:56 PointerPos : 1 | 12/ 12 ( 0.0%)
15/04/2012 19:44:56 RichCursor : 1 | 255/ 255 ( 0.0%)
15/04/2012 19:44:56 TOTALS : 311 | 326022/ 4919151 ( 93.4%)
15/04/2012 19:44:56 Statistics events Received/ RawEquiv ( saved)
15/04/2012 19:44:56 FramebufferUpdate : 3 | 30/ 30 ( 0.0%)
15/04/2012 19:44:56 SetEncodings : 1 | 52/ 52 ( 0.0%)
15/04/2012 19:44:56 SetPixelFormat : 1 | 20/ 20 ( 0.0%)
15/04/2012 19:44:56 TOTALS : 5 | 102/ 102 ( 0.0%)

Looking at the output, I'd have expected the width and height to be swapped for -r 3, and indeed is the vncviewer display unrotated (but garbled): It has a resolution of 1024x600 (screenshot attached)...