We have moved to a new Sailfish OS Forum. Please start new discussions there.

Dead digitizer (only when OS fully turned ON)

asked 2017-02-16 21:10:09 +0300

Naecken gravatar image

updated 2017-05-22 19:46:44 +0300


When phone display turns off, the notification LED quickly blinks double time with turquoise color. What does it means? Is there any possibility to fix non working digitizer? (uhm, I don't believe it, but for 2 seconds display recognised touches)

UPDATE: I found this: When phone is on charger, touch screen reacts on touches (double tap) without any problem. When phone is turned ON for alarm, touch screen reacts on touches (swipe gestures) without any problem. When phone is turning ON, I'm able to interact with UI for few seconds.

Then nothing... I guess that isn't absolutely hardware problem. Calibration issues? I still didn't tried recovery, so maybe it could help, but I'm not sure, if it helps.

UPDATE: Recovery didn't help.

edit retag flag offensive close delete



@Naecken: "When phone display turns off, the notification LED quickly blinks double time with turquoise color" is most likely: Powering down display is taking longer than expected (ref: https://git.merproject.org/mer-core/mce/blob/master/inifiles/debug-led.ini#L39).

Is there anything interesting looking in journal around display power down / up?

spiiroin ( 2017-03-27 19:15:47 +0300 )edit

spiiroin: Nice reference, thanks for reaction :)

Well, I didn't saw anything special or unexpected. Video attached Is there any possibility to get other error feedback from system? LED blinking at 1:50.

Naecken ( 2017-03-28 21:13:25 +0300 )edit

@Naecken: As the freezes happen in middle of already ongoing interaction... primary candidates that come to my mind are:

  • the touch events stop flowing somewhere along the hw->fw->kernel->lipstick line
  • lipstick itself gets stuck for some reason

The latter seems unlikely because there is a long power key press shutdown in the video and it manages to produce shutdown logo (i.e. power button -> power key event -> mce -> shutdown request -> dsme -> shutdown indication -> lipstick -> switch graphics to shutdown logo -chain is working as expected).

Also the cyan panic led points to kernel problems (if lipstick were stuck there would be green/red blinking), so I'm wondering if the driver needs to do retries / otherwise fails to communicate with the touch panel i.e. are the still issues with the contacts / flex?

You can debug the touch even flow for example by running evdev_trace (from mce-tools package), something like:

ssh nemo@<ip-addr>
evdev_trace -it 0 # 0 due to Jolla1 having touch input device at /dev/input/event0

Then you should get constant flow of things like below when holding finger on screen:

/dev/input/event0: 17893.959 - 0x03/EV_ABS - 0x035/ABS_MT_POSITION_X - 783
/dev/input/event0: 17893.959 - 0x03/EV_ABS - 0x036/ABS_MT_POSITION_Y - 587
/dev/input/event0: 17893.959 - 0x03/EV_ABS - 0x03a/ABS_MT_PRESSURE - 75
/dev/input/event0: 17893.959 - 0x00/EV_SYN - 0x002/SYN_MT_REPORT - 0
/dev/input/event0: 17893.959 - 0x00/EV_SYN - 0x000/SYN_REPORT - 0
spiiroin ( 2017-03-29 08:48:04 +0300 )edit

Well, after few days I finally login in chroot. Sadly, I still didn't find a way how install mce-tools package and run evdev. I stucked on ipforwarding in Ubuntu :(

Naecken ( 2017-04-09 13:12:18 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2017-05-22 19:47:22 +0300

Naecken gravatar image

Motherboard changed, problem fixed.

edit flag offensive delete publish link more


Where did you get the motherboard? I am in dire need of a touch pad replacement for my Jolla 1

DameCENO ( 2018-11-20 16:38:47 +0300 )edit
Login/Signup to Answer

Question tools



Asked: 2017-02-16 21:10:09 +0300

Seen: 616 times

Last updated: May 22 '17