Thread: Keyboard is going crazy
View Single Post
rainisto is offline rainisto
2012-05-07 , 10:12
Posts: 1,067 | Thanked: 2,383 times | Joined on Jan 2012 @ Finland
#11
I've only seen touch events gone haywired when restored a broken backup or using a broken charger which messed up all the events with interference. (but you can rule that one out if your not charging while you use your device?)

If you really want to test if screen touch sensor is broken, you can just googlesearch evtest.c and compile that to your device. And then run "aegis-exec ./evtest /dev/input/event3" in there you can see raw touch events and can see if you get ghost events when your not touching the device. (I've installed gcc on my N9, but normal users need to use scratchbox to compile).

Code:
RM696-07-1_PR_001:~# gcc -o evtest evtest.c
RM696-07-1_PR_001:~# aegis-exec ./evtest /dev/input/event3
Input driver version is 1.0.0
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "Atmel mXT Touchscreen"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 330 (Touch)
  Event type 3 (Absolute)
    Event code 0 (X)
      Value    541
      Min        0
      Max      853
    Event code 1 (Y)
      Value    255
      Min        0
      Max      479
    Event code 48 (?)
      Value      0
      Min        0
      Max      853
    Event code 53 (?)
      Value      0
      Min        0
      Max      853
    Event code 54 (?)
      Value      0
      Min        0
      Max      479
    Event code 57 (?)
      Value      0
      Min        0
      Max        9
  Event type 4 (Misc)
    Event code 2 (Gesture)
Testing ... (interrupt to exit)
When you touch the screen you should be getting event like this:
Code:
Event: time 1336385284.627016, type 1 (Key), code 330 (Touch), value 1
Event: time 1336385284.627107, type 3 (Absolute), code 0 (X), value 565
Event: time 1336385284.627107, type 3 (Absolute), code 1 (Y), value 120
Event: time 1336385284.627138, type 3 (Absolute), code 53 (?), value 565
Event: time 1336385284.627138, type 3 (Absolute), code 54 (?), value 120
Event: time 1336385284.627138, type 3 (Absolute), code 48 (?), value 54
Event: time 1336385284.627168, type 3 (Absolute), code 57 (?), value 0
Event: time 1336385284.627168, -------------- Config Sync ------------
if you get those events without touching the screen, then its time for nokia care.