answered
2014-09-20 09:20:56 +0200
Led control is handled by mce service. Led pattern triggering happens both within mce (charging, startup/shutdown etc) and via d-bus interface (csd, emal, sms, etc). The fact that patterns activated by external entity (=csd) still work means the whole pipeline should be working and the problem is likely to be in led configuration or settings - both of which persist over mce restarts / device reboot.
In this case csd patterns work, others do not. The csd leds are by default configured as "type=5 / always show pattern, even if LED disabled". All the other patterns obey the "master" led switch.
Any chance that you would have at some point disabled the leds?
You could try enabling them again via:
If that does not fix the situation, it would be interesting to capture some debug logs before restarting anything....
So no LED notifications at all work? Try out CSD tool: --> Dial ##310## and CSD tools start. Chose "Individual test" and scroll down till u find LED test.
Sounds like you need to reboot though, check out this possible duplicate: https://together.jolla.com/question/33445/led-not-working-while-charging-solved/
Btw 2+ months sounds pretty crazy - I turn my Jolla off almost every night ;-)
molan ( 2014-09-19 22:16:43 +0200 )editOh yeah forgot to mention. The LEDs work fine with the CSD tool. After this long of an uptime only two things don't work. LEDs and clipboard.
And its not crazy. It's how it is supposed to work. ;) You should not reboot unless you get an update.
ApB ( 2014-09-19 22:25:31 +0200 )editOk at least no HW defect. I meant crazy because you could keep it run that long :-D I simply turn it off because I don't need it when I sleep and at least every 2 weeks it happens that I run out of battery before I can charge it. So 2 months would be an incredible difficult challenge for me...
Make sure you keep some screenshots of the uptime :)
molan ( 2014-09-19 23:31:41 +0200 )editAs i said this is how a phone is supposed to work. It should be a reliable tool that has minimal downtime (if any). And we should get a graphical way to restart services (systemctl restart) like these when they fail. Even thought they shouldn't fail in the first place.
ApB ( 2014-09-19 23:40:05 +0200 )edit