Reply
Thread Tools
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.
 
Posts: 65 | Thanked: 26 times | Joined on Mar 2012 @ Cagliari, Italy
#12
Uhao....that's sound hard for me......
If I understood well, I have to search and download "evest.c", than to put in my N9, and, via the "terminal" to run it....
I'll try whitin 2hours......thanks for the moment!!!
I'd like to avoid nokia care, specially 'coz I'm in Italy, where the N9 is not supported by Nokia....
 
Posts: 1,067 | Thanked: 2,383 times | Joined on Jan 2012 @ Finland
#13
# devel-su
# apt-get install wget
# wget http://linuxi.org/evtest
# chmod a+x evtest
# aegis-exec ./evtest /dev/input/event3

For people who are not able to compile their own stuff. (normally you of course compile the file yourself, and not execute random binaries from untrusted sources....)
 
Posts: 65 | Thanked: 26 times | Joined on Mar 2012 @ Cagliari, Italy
#14
Thank You, Rainsto!

What I'm doing right now is to reflash with this line (flasher -f -F main.bin -F emmc.bin --erase-user-data), than I'll try to use Your stuff......but if the problem persist,it will be nearly impossible to use the device,and,of course,go and using the "terminal"....because the "ghosts events" are all the time,not random...



UPDATE:

after switch on the phone, ghost event stop me to do anything: I even cannot insert my PIN code. It seems to get worst....so I can't test the touch screen....

Last edited by requiem_76; 2012-05-07 at 13:45. Reason: update...
 
Dared's Avatar
Posts: 187 | Thanked: 143 times | Joined on Nov 2011
#15
If you backed it up and did a restore, then that would make the issue reappear. But if you did a full flash, and reinstalled everything from scratch, then that shouldn't be an issue. Try flashing it and NOT installing any 3rd party apps... If the problem continues, then it may be a hardware problem
 
Posts: 65 | Thanked: 26 times | Joined on Mar 2012 @ Cagliari, Italy
#16
Yes , Dared, that's the clue....
I've done a FULL FLASH ( zeroize), without putting any back up....and the problem reappear during basic set up!!!!!
So.i decided to give my phone to a Nokia care, just to tell me if I'm right about the touch screen hardware problem....
I'll let You know....
Does anybody know the price for a replacement screen? I mean the original one.....
I really don't wanna give up.... I'm mad about my N9.after trying the swipe ,I cannot going back with an android or other stuff.....
Thanks for YOUR support.......
 
Posts: 1,067 | Thanked: 2,383 times | Joined on Jan 2012 @ Finland
#17
you can always look the dismantling guide on the youtube, you could remove your display and reconnect it back, if it was just contact problem which would be fixed by shaking the cables.
 
Posts: 1,067 | Thanked: 2,383 times | Joined on Jan 2012 @ Finland
#18
and if display is really broken then replacement costs you around 115e, like http://www.ebay.ie/itm/New-Original-...-/280836435486
 
Posts: 65 | Thanked: 26 times | Joined on Mar 2012 @ Cagliari, Italy
#19
Thank You,Rainisto!!!d almost the same price,that deliver it to Italy too.
So, now I've to wait the check at the nokia care,than I will decide...of course,they told me that woldn't be possible to change my screen with not original spare parts from nokia.
I'll let You know!!!!
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 05:52.