Notification LED not turning on and fails test

Question

4

Notification LED not turning on and fails test

asked 2014-01-13 18:31:36 +0300

ottulo

411 ●6 ●10 ●14

updated 2014-01-14 10:06:37 +0300

eric

12967 ●88 ●133 ●123

https://twitter.com/erkki...

I edited the ini file some time ago to customize the LED patterns and had no problems with it, the edited file worked fine. However, since a couple days ago the LED has not been turning on anymore when it should, for example for charging or when I receive a message.

I have tried the following:

LED test in CSD Tool: Fail, tested before, after and in between all changes
Reboot: LED turns on, white, for a few seconds at the start of booting, then off again; above test fails
Restore original ini, restart mce.service: still fails test, remains off
Manually set the brightness from /sys/class/leds/... : LED turns on as it should

Clearly there is nothing wrong with the hardware as each of the colours works (red, green and blue tested). The ini file I restored is the completely unedited original file that I kept as a backup. Yet somehow the LED won't respond when it should.

Any further debugging ideas or ways to restore the functionality? I'd hate to manually turn on the led every time I get a message...

Edit: Fixed typo.

This is what I have in the folder, bolded file has the edited patterns that I thought may be the problem. I have not touched the other files. Does something look suspicious?

[root@localhost nemo]# cd /etc/mce
[root@localhost mce]# ls -l
total 68
-rw-r--r-- 1 root root 26103 Dec 16 21:28 10mce.ini
-rw-r--r-- 1 root root 1481 Dec 16 21:28 20als-defaults.ini
-rw-r--r-- 1 root root 2041 Jan 7 10:52 20hybris-led.ini
-rw-r--r-- 1 root root 2053 Jan 9 22:44 20hybris-led.ini.error
-rw-r--r-- 1 root root 147 Dec 16 21:28 20mce-radio-states.ini
-rwxr-xr-x 1 root root 808 Dec 13 13:35 30csdpatterns.ini
-rw-r--r-- 1 root root 468 Dec 20 17:31 60-als-jolla.ini
-rw-r--r-- 1 root root 301 Dec 20 17:31 60-doubletap-jolla.ini
-rw-r--r-- 1 root root 49 Dec 20 17:31 60-mce-display-blank-timeout.conf
-rw-r--r-- 1 root root 46 Dec 20 17:31 60-mce-display-brightness.conf
-rw-r--r-- 1 root root 72 Dec 20 17:31 60-mce-possible-display-dim-timeouts.conf
[root@localhost mce]#

edit retag flag offensive close delete

Comments

1

all the files in the dir will be loaded, so check for any extra files, e.g. editor backups there? (I assume mcd was just a typo)

sp3000 ( 2014-01-13 22:53:25 +0300 )edit

@ottulo, have you had any luck getting your led back? I tried and re-tried the fix given by @Mohjive in his answer, but I still get no led notifications, and csd test fails...

ssahla ( 2014-01-19 21:56:33 +0300 )edit

@ssahla Sadly, no. I tried the solutions below, but had no luck. I'm hoping we might get some other hints, as I am not too keen on doing a factory reset.

ottulo ( 2014-01-19 22:12:36 +0300 )edit

@ottulo, me neither. I thought I'll see if the next system update fixes this before resorting to a factory reset.

ssahla ( 2014-01-19 22:18:22 +0300 )edit

Same issue for me as described above. White LED blinking for few seconds while booting. No other LED turns on or is blinking at all afterwards. Solution provided below didn't work. I did not any customizing or editing files on OS Level. For sure it is not a hardware issue. Waiting for next update?

vision ( 2014-01-19 22:55:21 +0300 )edit

@vision Ok, so it's isn't because of my tinkering after all :)

ssahla ( 2014-01-19 23:00:51 +0300 )edit

Did you try to activate the LED manually? dbus-send --print-reply --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_enable

Cermit ( 2014-01-20 18:58:42 +0300 )edit

@Cermit, tried that now. It returns

method return sender=:1.11 -> dest=:1.147 reply_serial=2

I don't know how to interpret that. But no change in led, still doesn't work.

ssahla ( 2014-01-20 19:07:29 +0300 )edit

I tried it as well, and got the same result with one exception. The "dest=:" part has a different number, and it is incremented when I try the command again. I had it go from 1.268 to 1.270 on three tries. I guess this is intended behaviour?

ottulo ( 2014-01-20 20:27:12 +0300 )edit

I remotely connected via ssh from N9 to Jolla (where display was off) and I tried to activate the LED manually via dbus command. Didn't work as well. The only error in journal log is "... Open 367 - Error accessing property file". I don't think it is related to the LED issue. What's next?

vision ( 2014-01-21 08:42:05 +0300 )edit

By the way @ottulo, how do you manually set the brightness from /sys/class/leds/...?

ssahla ( 2014-01-25 22:49:59 +0300 )edit

@ssahla like so:

devel-su
echo 10 >/sys/class/leds/led:rgb_red/brightness

You can set the brightness by changing the value after "echo" and control the other colours by changing rgb_red to rgb_blue or rgb_green. The value can be between 0-255 (higher has no effect). 0 is off.

ottulo ( 2014-01-25 23:05:52 +0300 )edit

Seems that nobody is able or willing to explain how it is possible that LEDs are suddenly not functional anymore. I didn't find any logs for further investigations and it would be really nice to get at least some short feedback from the Jolla guys. I am close to a factory reset in the meanwhile... ;)

vision ( 2014-01-25 23:07:14 +0300 )edit

@ottulo, thanks! By googling I already figured that's how it must work, but I didn't know the scale is 0..255, so I only tried 1 and that of course is not visible – so I figured maybe I ask you. :) But yes that way I can get the LED on, so I can be sure there's nothing physically wrong with it.

ssahla ( 2014-01-25 23:18:42 +0300 )edit

@vision, I agree, it would be nice to get this thing at least acknowledged by Jolla... But if you can tell anything by the votes, it's not a very common problem.

ssahla ( 2014-01-25 23:22:59 +0300 )edit

Yes.. based on the votes it never will become visible to Jolla...even if I know more people from another forum who are facing the same issue. Since I don't believe that the next update will fix it I think I will reset the device and to reproduce the issue again in order to identify the root cause.

vision ( 2014-01-25 23:45:23 +0300 )edit

@vision If you're going to reset the device, please tell us whether this fixes the issue (hopefully it does!). I'll wait until next update and see if that does it, that way we'll have both options covered. ;)

ottulo ( 2014-01-26 00:05:48 +0300 )edit

Sounds like a plan ;) I am still using the N9 as primary phone and the Jolla is still in status "move to production". In case my wife doesn't disturb me too much I might have some results already tomorrow ;)

vision ( 2014-01-26 00:33:42 +0300 )edit

@ottulo, the factory reset fixed the issue. LEDs are back and tested successfully for charging, shutdown, boot, email and SMS. Basic configurations are done, no apps from Jolla Store or OpenRepos installed so far. Testing to be continued after each app installation or configuration change.

vision ( 2014-01-26 20:54:16 +0300 )edit

all the files in the dir will be loaded, so check for any extra files, e.g. editor backups there? (I assume mcd was just a typo)
sp3000 ( 2014-01-13 22:53:25 +0300 )edit
@ottulo, have you had any luck getting your led back? I tried and re-tried the fix given by @Mohjive in his answer, but I still get no led notifications, and csd test fails...
ssahla ( 2014-01-19 21:56:33 +0300 )edit
@ssahla Sadly, no. I tried the solutions below, but had no luck. I'm hoping we might get some other hints, as I am not too keen on doing a factory reset.
ottulo ( 2014-01-19 22:12:36 +0300 )edit
@ottulo, me neither. I thought I'll see if the next system update fixes this before resorting to a factory reset.
ssahla ( 2014-01-19 22:18:22 +0300 )edit
Same issue for me as described above. White LED blinking for few seconds while booting. No other LED turns on or is blinking at all afterwards. Solution provided below didn't work. I did not any customizing or editing files on OS Level. For sure it is not a hardware issue. Waiting for next update?
vision ( 2014-01-19 22:55:21 +0300 )edit
@vision Ok, so it's isn't because of my tinkering after all :)
ssahla ( 2014-01-19 23:00:51 +0300 )edit
Did you try to activate the LED manually? dbus-send --print-reply --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_enable
Cermit ( 2014-01-20 18:58:42 +0300 )edit
@Cermit, tried that now. It returns
method return sender=:1.11 -> dest=:1.147 reply_serial=2
I don't know how to interpret that. But no change in led, still doesn't work.
ssahla ( 2014-01-20 19:07:29 +0300 )edit
I tried it as well, and got the same result with one exception. The "dest=:" part has a different number, and it is incremented when I try the command again. I had it go from 1.268 to 1.270 on three tries. I guess this is intended behaviour?
ottulo ( 2014-01-20 20:27:12 +0300 )edit
I remotely connected via ssh from N9 to Jolla (where display was off) and I tried to activate the LED manually via dbus command. Didn't work as well. The only error in journal log is "... Open 367 - Error accessing property file". I don't think it is related to the LED issue. What's next?
vision ( 2014-01-21 08:42:05 +0300 )edit
By the way @ottulo, how do you manually set the brightness from /sys/class/leds/...?
ssahla ( 2014-01-25 22:49:59 +0300 )edit
@ssahla like so:
devel-su echo 10 >/sys/class/leds/led:rgb_red/brightness
You can set the brightness by changing the value after "echo" and control the other colours by changing rgb_red to rgb_blue or rgb_green. The value can be between 0-255 (higher has no effect). 0 is off.
ottulo ( 2014-01-25 23:05:52 +0300 )edit
Seems that nobody is able or willing to explain how it is possible that LEDs are suddenly not functional anymore. I didn't find any logs for further investigations and it would be really nice to get at least some short feedback from the Jolla guys. I am close to a factory reset in the meanwhile... ;)
vision ( 2014-01-25 23:07:14 +0300 )edit
@ottulo, thanks! By googling I already figured that's how it must work, but I didn't know the scale is 0..255, so I only tried 1 and that of course is not visible – so I figured maybe I ask you. :) But yes that way I can get the LED on, so I can be sure there's nothing physically wrong with it.
ssahla ( 2014-01-25 23:18:42 +0300 )edit
@vision, I agree, it would be nice to get this thing at least acknowledged by Jolla... But if you can tell anything by the votes, it's not a very common problem.
ssahla ( 2014-01-25 23:22:59 +0300 )edit
Yes.. based on the votes it never will become visible to Jolla...even if I know more people from another forum who are facing the same issue. Since I don't believe that the next update will fix it I think I will reset the device and to reproduce the issue again in order to identify the root cause.
vision ( 2014-01-25 23:45:23 +0300 )edit
@vision If you're going to reset the device, please tell us whether this fixes the issue (hopefully it does!). I'll wait until next update and see if that does it, that way we'll have both options covered. ;)
ottulo ( 2014-01-26 00:05:48 +0300 )edit
Sounds like a plan ;) I am still using the N9 as primary phone and the Jolla is still in status "move to production". In case my wife doesn't disturb me too much I might have some results already tomorrow ;)
vision ( 2014-01-26 00:33:42 +0300 )edit
@ottulo, the factory reset fixed the issue. LEDs are back and tested successfully for charging, shutdown, boot, email and SMS. Basic configurations are done, no apps from Jolla Store or OpenRepos installed so far. Testing to be continued after each app installation or configuration change.
vision ( 2014-01-26 20:54:16 +0300 )edit

Accepted Answer

0

answered 2014-01-13 23:42:31 +0300

Mohjive

8581 ●166 ●226 ●250

http://www.y3k.se/

updated 2014-01-14 00:27:50 +0300

I noticed the same issue just now. Most probably something since I ran the CSD tests. I removed the executable flag from 30csdpatterns.ini

chmod -x /etc/mce/30csdpatterns.ini

moved it out of the way

mv /etc/mce/30csdpatterns.ini /etc/mce/30csdpatterns.ini.disabled

and then restarted the mce service

systemctl restart mce.service

then I got the led back. Don't know which of the actions that were needed. Now that I try to roll back any of the changes the led still works even when the executable bit is set and the 30csdpatterns.ini file has its original name. All my action done in devel-su mode.

edit flag offensive delete publish link

Comments

I also have the same issue, after editing 20hybris-led.ini to customize led behavior. I tried to repeat your steps. But with sysctl I get

error: "restart" is an unknown key
error: "mce.service" is an unknown key

Can you tell me why this is? (I'm not good with this stuff.)

ssahla ( 2014-01-14 00:25:15 +0300 )edit

Typo by me, sorry. It should be

systemctl restart mce.service

I've updated the answer as well

Mohjive ( 2014-01-14 00:27:31 +0300 )edit

Ok thanks :) Tried again, with no error messages this time. I also deleted the 20hybris-led.ini I had edited and replaced it with the original. But still no led.

ssahla ( 2014-01-14 00:35:47 +0300 )edit

Same here, I tried it earlier (noticed the typo) but the LED didn't get fixed. Worst of all, after a reboot for a moment I had this issue: http://youtu.be/BB56cz7MxuU This video is not mine, I just happened to see it earlier today. I got rid of this with a reboot, but the LED issue still persists.

ottulo ( 2014-01-14 00:59:02 +0300 )edit

I've seen the blinking display as well. I got it when I restarted the mce service a couple of times. I solved that by locking and unlocking the display with the power button.

Mohjive ( 2014-01-14 01:18:00 +0300 )edit

Notification LED not turning on and fails test

Comments

1 Answer

Comments

Question tools

Stats

Related questions

Notification LED not turning on and fails test

Comments

1 Answer

Comments

Question tools

Public thread

Stats

Related questions