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

[Xperia X] White LED stuck on after charging [released]

Tracked by Jolla (In release)

asked 2017-10-13 08:42:08 +0300

Manatus gravatar image

updated 2019-01-08 09:30:29 +0300

This was with official Sailfish X.

White LED did not go off when the charging cable was removed. It was blinking before taking the cable off and stuck on plain white. This happened after the first overnight full charge.

The light went out when the screen was open, but it turned back on when the screen went off (both by power button or by timeout).

I run csd and its LED test and all of the leds were ok. This did not clear up the problem, and eventually the restart of the phone fixed it.

Briefly testing with the power cable didn't bring the issue up again. I'll report here if I see it again, and try to find something in the dmesg/logs.

Might be important! I had disabled email notification LED with mcetool just previous day with:

mcetool --disable-led-pattern=PatternCommunicationEmail

Update 24.11.2017

I finally had this bug again. It may have been triggered by either: 1) Email arriving at night during the charging, which lights up the screen even when I have disabled the led pattern for it, or 2) timely removal of USB charging cable from the device (the moment when the pulsing LED cycle is at its brightest), or 3) both.

After removing the cable from the phone grep . /run/state/namespaces/Battery/* showed

run/state/namespaces/Battery/Capacity:100.000000
/run/state/namespaces/Battery/ChargePercentage:100
/run/state/namespaces/Battery/ChargingState:discharging
/run/state/namespaces/Battery/Current:332792
/run/state/namespaces/Battery/Energy:8360000
/run/state/namespaces/Battery/EnergyFull:8360000
/run/state/namespaces/Battery/IsCharging:0
/run/state/namespaces/Battery/Level:normal
/run/state/namespaces/Battery/LowBattery:0
/run/state/namespaces/Battery/OnBattery:1
/run/state/namespaces/Battery/Power:1756000
/run/state/namespaces/Battery/State:discharging
/run/state/namespaces/Battery/Temperature:245
/run/state/namespaces/Battery/TimeUntilFull:0
/run/state/namespaces/Battery/TimeUntilLow:17136
/run/state/namespaces/Battery/Voltage:4258550

That looked pretty normal to me. State is discharging even though the led burns white (or very bright blue, I'm not sure which one it is).

Then I followed spiiroin's advice to increase logging, but grepping journalctl for modules/led or even just led did not show anything at all. I noticed that my phone had not logged _anything_ in journalctl since 12th of November, which explains that.

Current uptime was 22 days, so I lost 12 days for some reason. Last entries were:

Nov 12 15:49:04 Sailfish kernel: PM: suspend exit 2017-11-12 13:49:04.787473380 UTC
Nov 12 15:49:04 Sailfish kernel: PM: suspend entry 2017-11-12 13:49:04.787496391 UTC
Nov 12 15:49:04 Sailfish systemd[1]: Time has been changed
Nov 12 15:49:04 Sailfish mce[1411]: modules/proximity.c: report_proximity(): state: CLOSED -> OPEN
Nov 12 15:49:04 Sailfish systemd[2598]: Time has been changed

I noticed that when I had run mcetool --deactivate-led-pattern=PatternBatteryCharging, the led had gone off when the screen was off too. I activated it again with mcetool --activate-led-pattern=PatternBatteryCharging, and saw that the problem was still on. So at least we know that it is related to PatternBatteryCharging.

At this point I plugged the phone into my computer in developer mode, at which point the led went out and did not light up again.

I'll try to trigger the problem sooner by email and timely removal of USB charging cable.

Edit 2018.01.18: I simply haven't been able to reproduce the problem. It is very rare. Sry! :(

Update 2018.04.21

I got the charging led problem now with the community Sailfish X Compact (2.1.3.7) for the very first time.

The phone had run out of power previous night. I plugged it in charger and started the phone normally. When Sailfish had started it requested what to do with already plugged in USB-connection -> I chose 'Charge only'. After this I removed the cable once and plugged it back in just in case, and pressed power button once to close the screen and went to bed.

In the morning the phone showed white LED as it should. When I removed the device from the charging cable (from the end of the charger first), I saw that I had two unread emails in the status screen. When I pressed the power button to close the screen, the white LED was re-lit again. I do not remember whether I removed the cable from phone end after or before pressing the power button to close the screen.

I gathered dmesg, battery status and full journal from the device, first with the defaults and then with verbosity at notice level, both PatternBatteryCharging on and off. Luckily the journal is not very long since the device had run out of juice in the previous night.

Journal_20180421.zipcontaining logs can be found here: https://perhonen.net/s/28P2o4FkHyoHJwr

Edit: I forgot to put battery state file into the zip. It showed following:

/run/state/namespaces/Battery/Capacity:100.000000
/run/state/namespaces/Battery/ChargePercentage:100
/run/state/namespaces/Battery/ChargingState:discharging
/run/state/namespaces/Battery/Current:124816
/run/state/namespaces/Battery/Energy:8360000
/run/state/namespaces/Battery/EnergyFull:8360000
/run/state/namespaces/Battery/IsCharging:0
/run/state/namespaces/Battery/Level:normal
/run/state/namespaces/Battery/LowBattery:0
/run/state/namespaces/Battery/OnBattery:1
/run/state/namespaces/Battery/Power:301000
/run/state/namespaces/Battery/State:discharging
/run/state/namespaces/Battery/Temperature:272
/run/state/namespaces/Battery/TimeUntilFull:0
/run/state/namespaces/Battery/TimeUntilLow:99986
/run/state/namespaces/Battery/Voltage:4258550

Note:

I have PatternCommunicationEmail disabled and haptic and ffmemless lines deleted in email.ini to prevent reacting for emails. The phone screen still lights up though, as I haven't found a way to disable that.

I still suspect that receiving emails during charging phase may be triggering the problem, especially as it lights up the screen. I don't get emails often and I have email active hours from 7:00am to 10:00pm, but this time I woke up later and removed the device from the charger later than usual.

Update 2018.07.11

For the first time I got pulsing LED indicator (battery fully charged indicator) stuck after removing the device from the charger in the morning. Same symptoms otherwise, except this time I did not have any messages or emails during the night. So this was not triggered by any other notification event.

Xperia X device. SailfishOS version 2.2.0.29.

Update 2019.01.08

Fixed in SFOS 3.0.1.11.

edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by Manatus
close date 2019-01-08 09:31:12.358190

Comments

I have been also countered this bug. I can't remember when it happened and how many times I was countered this bug. But at least twice I countered this bug.

Jk ( 2018-10-10 18:25:39 +0300 )edit

3 Answers

Sort by » oldest newest most voted
7

answered 2017-10-30 09:53:39 +0300

spiiroin gravatar image

@Manatus If you bump into this again, it would be nice to know whether the whole battery status is stuck to some charging state or not. The relevant information can be obtained via:

grep . /run/state/namespaces/Battery/*

In normal verbosity level led pattern evaluation is not logged, so journal/dmesg probably is not that useful.

However, you could try increasing mce verbosity and then manually stopping the charging pattern. The resulting journal logging should give some indication whether it is charging pattern or something else that gets stuck. Something like:

mcetool --set-verbosity=notice
mcetool --deactivate-led-pattern=PatternBatteryCharging
journalctl -u mce -b | grep modules/led

In any case, restarting mce should reset led state (unless it is something external to mce - say notification related).

systemctl restart mce

Note that mcetool needs to be installed manually:

pkcon refresh
pkcon install mce-tools
edit flag offensive delete publish link more

Comments

1

Thanks! I saw this immediately the next overnight charge (white led) once, but not since.

As with the blue led case I suspect this is related to notifications, also possibly screen lighting up when you get the notification. I've changed my email check interval not to check mail at night, which would correlate with the absence of the problem for me lately.

Manatus ( 2017-10-30 11:49:32 +0300 )edit

Had this again. Updated the original post.

Manatus ( 2017-11-24 08:41:16 +0300 )edit

I hited that bug too.

There seems nothing unusual:

[nemo@Sailfish ~]$ grep . /run/state/namespaces/Battery/*
/run/state/namespaces/Battery/Capacity:95.000000
/run/state/namespaces/Battery/ChargePercentage:95
/run/state/namespaces/Battery/ChargingState:discharging
/run/state/namespaces/Battery/Current:124663
/run/state/namespaces/Battery/Energy:7942000
/run/state/namespaces/Battery/EnergyFull:8360000
/run/state/namespaces/Battery/IsCharging:0
/run/state/namespaces/Battery/Level:normal
/run/state/namespaces/Battery/LowBattery:0
/run/state/namespaces/Battery/OnBattery:1
/run/state/namespaces/Battery/Power:344000
/run/state/namespaces/Battery/State:discharging
/run/state/namespaces/Battery/Temperature:250
/run/state/namespaces/Battery/TimeUntilFull:0
/run/state/namespaces/Battery/TimeUntilLow:83113
/run/state/namespaces/Battery/Voltage:4187139

Led turned off as expected with:

[root@Sailfish ~]# mcetool --deactivate-led-pattern=PatternBatteryCharging

BTW My general remark: I would prefer more white color when charging as now it has some pink/blue hue.

Filip K. ( 2017-12-17 23:48:20 +0300 )edit

Happened again on 2.1.4.14. I deactivated it as nemo. Nothing in logs.

[nemo@Sailfish ~]$ grep . /run/state/namespaces/Battery/*
/run/state/namespaces/Battery/Capacity:100.000000
/run/state/namespaces/Battery/ChargePercentage:100
/run/state/namespaces/Battery/ChargingState:discharging
/run/state/namespaces/Battery/Current:6408
/run/state/namespaces/Battery/Energy:8360000
/run/state/namespaces/Battery/EnergyFull:8360000
/run/state/namespaces/Battery/IsCharging:0
/run/state/namespaces/Battery/Level:normal
/run/state/namespaces/Battery/LowBattery:0
/run/state/namespaces/Battery/OnBattery:1
/run/state/namespaces/Battery/Power:188000
/run/state/namespaces/Battery/State:discharging
/run/state/namespaces/Battery/Temperature:225
/run/state/namespaces/Battery/TimeUntilFull:0
/run/state/namespaces/Battery/TimeUntilLow:160084
/run/state/namespaces/Battery/Voltage:4254888
Filip K. ( 2018-04-19 02:22:27 +0300 )edit
3

answered 2018-10-10 09:43:00 +0300

spiiroin gravatar image

Probable cause: mce does not get woken up to process battery state changes reported by statefs -> mce is left believing that charging is still ongoing despite the cable disconnect and everything -> charging led pattern does not get deactivated.

Internal ticket has been filed about this.

edit flag offensive delete publish link more
1

answered 2018-01-15 14:59:11 +0300

voulo gravatar image

I can confirm the issue on Sailfish X with uptime of 15 days. Led blinks about a week.

edit flag offensive delete publish link more

Comments

I also have this some times, very rarely. After reboot it is working again.

poddl ( 2018-01-22 02:56:38 +0300 )edit

I see this frequently with the last few Sailfish versions. Reboot usually helps.

SagaciousT ( 2018-07-12 12:05:29 +0300 )edit
1

Happens sometimes.

I think it is annoying but harmless.

juiceme ( 2018-07-12 14:37:45 +0300 )edit

Question tools

Follow
12 followers

Stats

Asked: 2017-10-13 08:42:08 +0300

Seen: 1,597 times

Last updated: Jan 08 '19