When running with windows version of android sdk getting error: cannot open kbd device /dev/input/event3

qaavi / android-vnc-server

Automatically exported from code.google.com/p/android-vnc-server

1 stars 1 forks source link

When running with windows version of android sdk getting error: cannot open kbd device /dev/input/event3 #1

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. When executed through windows sdk i am getting following sequence of 
messages.
#./androidvncserver
Initializing framebuffer device /dev/graphics/fb0...
xres=320, yres=480, xresv=320, yresv=960, xoffs=0, yoffs=0, bpp=16
Initializing keyboard device /dev/input/event3 ...
cannot open kbd device /dev/input/event3

What is the expected output? What do you see instead?
android vnc server should start running without any error message.

What version of the product are you using? On what operating system?
latest one, released on Jun 08 2009

Please provide any additional information below.

Original issue reported on code.google.com by deepraj....@gmail.com on 15 Jun 2009 at 2:01

GoogleCodeExporter commented 9 years ago

When tried setting different Keyboard device and mouse device, got following 
lines 
of errors:

#./androidvncserver -k "/dev/input/event0" -t "/dev/input/mouse0"
Initializing framebuffer device /dev/graphics/fb0...
xres=320, yres=480, xresv=320, yresv=960, xoffs=0, yoffs=480, bpp=16
Initializing keyboard device /dev/input/event0 ...
Initializing touch device /dev/input/mouse0 ...
cannot get ABS_X info, Not a typewriter
#

Original comment by deepraj....@gmail.com on 15 Jun 2009 at 2:08

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

Same issue here running emulator on mac.

Original comment by amacb...@gmail.com on 27 Jun 2009 at 7:27

GoogleCodeExporter commented 9 years ago

This appears to be working on the emulator using:
#./androidvncserver -k "/dev/input/event0" -t "/dev/input/event0"

Original comment by amacb...@gmail.com on 27 Jun 2009 at 9:17

GoogleCodeExporter commented 9 years ago

run getevent first to see eventX<->device

Original comment by zhaosih@gmail.com on 14 Jan 2010 at 7:36

GoogleCodeExporter commented 9 years ago

I have the same problem

Original comment by i7gab...@googlemail.com on 25 Apr 2013 at 10:29

GoogleCodeExporter commented 9 years ago

我也是同样问题 乐视盒子 c1s,有什么解决办法吗？

Original comment by kwing....@gmail.com on 27 Jan 2014 at 5:40

zyzand commented 4 years ago

我也是同样问题 乐视盒子 c1s,有什么解决办法吗？
Original comment by kwing....@gmail.com on 27 Jan 2014 at 5:40

Some Android devices are not connected to an touch device, and will not be displayed in the /dev/input directory until the mouse is connected. Try to connect the mouse and restart.