[G Tablet General] rajeevvp:
OK. The first 4 lines are nothing new. I can see them on my gTablet too. They're routine messages from the device driver telling you that the code was initialized. But, the /devices/virtual/input/input3 message might be of interest. Here's why:

$ dmesg | fgrep virtual/
<6>[ 8.731815] input: so340010_kbd as /devices/virtual/input/input1
<6>[ 9.453749] input: nvodm_touch as /devices/virtual/input/input2
<6>[ 9.483643] input: gps_control as /devices/virtual/input/input3
<6>[ 9.495626] input: dummy_sensor as /devices/virtual/input/input4
<6>[ 9.502132] input: accelerometer as /devices/virtual/input/input5
<6>[ 9.512175] input: light_sensor as /devices/virtual/input/input6

As you can see, all the input drivers, when they are initialized, write out a message like we saw above, telling us where they will present data from their device. Let's check the non-GPS devices one by one--press the keys, or touch the screen, or whatever, as appropriate. Kill hexdump using Ctrl-C when you're done looking:

$ su
# hexdump -C /dev/input/event0 # check HW keys (volume, power)
00000000 c0 28 00 00 e7 61 0c 00 01 00 73 00 01 00 00 00 |.(...a....s.....|
00000010 c0 28 00 00 59 6f 0c 00 00 00 00 00 00 00 00 00 |.(..Yo..........|
00000020 c0 28 00 00 89 f4 0e 00 01 00 73 00 00 00 00 00 |.(........s.....|
00000030 c0 28 00 00 a5 f4 0e 00 00 00 00 00 00 00 00 00 |.(..............|
00000040 c2 28 00 00 dd 72 02 00 01 00 72 00 01 00 00 00 |.(...r....r.....|
^C
# hexdump -C /dev/input/event1 # check the Android softkeys.
00000000 2b 29 00 00 0e ee 0c 00 01 00 8b 00 01 00 00 00 |+)..............|
00000010 2b 29 00 00 36 06 0f 00 01 00 8b 00 00 00 00 00 |+)..6...........|
^C
# hexdump -C /dev/input/event2 # check the touchscreen data--lots of it.
00000000 92 29 00 00 2a df 05 00 03 00 35 00 ef 03 00 00 |.)..*.....5.....|
00000010 92 29 00 00 42 df 05 00 03 00 36 00 41 01 00 00 |.)..B.....6.A...|
00000020 92 29 00 00 6c e2 05 00 03 00 30 00 0a 00 00 00 |.)..l.....0.....|
00000030 92 29 00 00 7e e2 05 00 03 00 32 00 14 00 00 00 |.)..~.....2.....|
00000040 92 29 00 00 84 e2 05 00 00 00 02 00 00 00 00 00 |.)..............|
^C
[I]
Skip the dummy sensor[/I]

# hexdump -C /dev/input/event5 # Check the accelerometer data. You'll have to load something that uses the accelerometer. I ran Google Maps. Lots of data.
00000000 fc 29 00 00 67 3c 05 00 03 00 02 00 c2 01 00 00 |.)..g<..........|
00000010 fc 29 00 00 a3 3d 05 00 00 00 00 00 00 00 00 00 |.)...=..........|
00000020 fc 29 00 00 be 84 05 00 03 00 01 00 84 03 00 00 |.)..............|
00000030 fc 29 00 00 d5 84 05 00 00 00 00 00 00 00 00 00 |.)..............|
00000040 fc 29 00 00 1c d3 05 00 03 00 01 00 72 03 00 00 |.)..........r...|
^C
# hexdump -C /dev/input/event6 # check light-sensor data. Cover and uncover the sensor.
00000000 74 2a 00 00 48 b3 0a 00 03 00 28 00 2c 01 00 00 |t*..H.....(.,...|
00000010 74 2a 00 00 5b b6 0a 00 00 00 00 00 00 00 00 00 |t*..[...........|
00000020 75 2a 00 00 a5 06 00 00 03 00 28 00 46 00 00 00 |u*........(.F...|
00000030 75 2a 00 00 62 08 00 00 00 00 00 00 00 00 00 00 |u*..b...........|
00000040 75 2a 00 00 fa 98 04 00 03 00 28 00 96 00 00 00 |u*........(.....|
^C
#

Now, we check /dev/input/input3. I think you should,

a) enable the GPS GPIO pins using the echo command.

b) Go to Settings > Location & security, and there enable the "Use GPS satellites" setting, and then

c) Check if Google Maps works, and at the same time, see if there is any data coming out of the /dev/input/event3 device:

$ su
# hexdump -C /dev/input/event3

However, I doubt it. As I mentioned, the GPS driver code does not read any data--it just enables or disables the GPS GPIO pins/port. But, better to try the command above and cover all the bases.

Next check: since GPS modules are usually connected to serial ports, you could try the hexdump commands on whatever serial port you can see in /dev--after you've set the baud rate on the device.

There are 3 serial port devices in /dev/ that I suspect are bluetooth-related, but, you could try to see if there is any data presented there when Google Maps is running:

$ su
# stty speed 9600 < /dev/ttyS0
# hexdump -C /dev/ttyS0

Similarly for /dev/ttyHS2 and /dev/ttyHS3.

Keep us informed.