Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Graphics are messed up on Nexus One and input doesn't work. #10

Open
GoogleCodeExporter opened this issue Mar 20, 2016 · 7 comments
Open

Comments

@GoogleCodeExporter
Copy link



See screenshot.
Initializing framebuffer device /dev/graphics/fb0...
xres=480, yres=800, xresv=480, yresv=1600, xoffs=0, yoffs=0, bpp=32
Initializing keyboard device /dev/input/event3 ...
Initializing touch device /dev/input/event1 ...
Initializing VNC server:
        width:  480
        height: 800
        bpp:    32
        port:   5901
Initializing server...
12/03/2010 15:15:12 Listening for VNC connections on TCP port 5901
12/03/2010 15:15:25 Got connection from client 127.0.0.1
12/03/2010 15:15:25   other clients:
12/03/2010 15:15:25 Client Protocol Version 3.8
12/03/2010 15:15:25 Protocol version sent 3.8, using 3.8
Dirty page: 480x800+0+0...
12/03/2010 15:15:25 rfbProcessClientSecurityType: executing handler for type 1
12/03/2010 15:15:25 rfbProcessClientSecurityType: returning securityResult for c
lient rfb version >= 3.8
12/03/2010 15:15:25 Pixel format for client 127.0.0.1:
12/03/2010 15:15:25   8 bpp, depth 8
12/03/2010 15:15:25   true colour: max r 3 g 3 b 3, shift r 4 g 2 b 0
12/03/2010 15:15:25 Enabling full-color cursor updates for client 127.0.0.1
12/03/2010 15:15:25 Enabling NewFBSize protocol extension for client 127.0.0.1
12/03/2010 15:15:25 Using ZRLE encoding for client 127.0.0.1
12/03/2010 15:15:26 Pixel format for client 127.0.0.1:
12/03/2010 15:15:26   16 bpp, depth 15, little endian
12/03/2010 15:15:26   true colour: max r 31 g 31 b 31, shift r 0 g 5 b 10
12/03/2010 15:15:26 Enabling full-color cursor updates for client 127.0.0.1
12/03/2010 15:15:26 Enabling NewFBSize protocol extension for client 127.0.0.1
12/03/2010 15:15:26 Switching from ZRLE to hextile Encoding for client 127.0.0.1

Same for all color depth settings.

Original issue reported on code.google.com by alon.alb...@gmail.com on 12 Mar 2010 at 11:17

Attachments:

@GoogleCodeExporter
Copy link
Author

Same issue here.


Original comment by pllewi...@gmail.com on 14 May 2010 at 4:31

@GoogleCodeExporter
Copy link
Author

Same issue here

Original comment by jdi...@gmail.com on 6 Jun 2010 at 3:47

@GoogleCodeExporter
Copy link
Author

Same here :(

Original comment by street...@gmail.com on 15 Jun 2010 at 10:08

@GoogleCodeExporter
Copy link
Author

please attach the content of fb0.raw, you can get it using

adb push /dev/graphics/fb0 fb0.raw

thanks

Original comment by onaips@gmail.com on 24 Jun 2010 at 5:22

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

Same on HTC Desire

Initializing framebuffer device /dev/graphics/fb0...
xres=480, yres=800, xresv=480, yresv=1600, xoffs=0, yoffs=800, bpp=32
Initializing keyboard device /dev/input/event3 ...
Initializing touch device /dev/input/event1 ...
Initializing VNC server:
        width:  480
        height: 800
        bpp:    32
        port:   5901
Initializing server...
19/11/2010 10:00:05 Listening for VNC connections on TCP port 5901
19/11/2010 10:03:09 Got connection from client 127.0.0.1
19/11/2010 10:03:09   other clients:
19/11/2010 10:03:09 Client Protocol Version 3.3
19/11/2010 10:03:09 Protocol version sent 3.3, using 3.3
Dirty page: 480x800+0+0...
19/11/2010 10:03:09 Using raw encoding for client 127.0.0.1
19/11/2010 10:03:09 Pixel format for client 127.0.0.1:
19/11/2010 10:03:09   8 bpp, depth 8
19/11/2010 10:03:09   true colour: max r 7 g 7 b 3, shift r 5 g 2 b 0

Framebuffer content attached

Original comment by dass2...@gmail.com on 19 Nov 2010 at 10:10

Attachments:

@GoogleCodeExporter
Copy link
Author

I am also having similar issues on the Samsung Charge. Inputs do not work, the 
hard keys at the bottom are on /dev/input/event1 and the touch screen is on 
/dev/input/event8.

./vnc -k /dev/input/event1 -t /dev/input/event8

I attached my log of the connection, the raw framebuffer data, the converted fb 
data and the vnc screen shot.

I converted from the raw data to the png with this command: 
ffmpeg -vframes 1 -vcodec rawvideo -f rawvideo -pix_fmt rgb32 -s 480x800 -i fb0 
-f image2 -vcodec png image.png

Original comment by Bill.c.R...@gmail.com on 21 Jul 2011 at 8:12

Attachments:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant