Missing low battery notifications

Question

2

Missing low battery notifications

Tracked by Jolla (In release)

asked 2019-12-03 21:46:27 +0300

Mohjive

8581 ●166 ●226 ●250

http://www.y3k.se/

updated 2019-12-03 21:47:04 +0300

My Xperia 10 with Sailfish 3.2.0.14 shut down due to low battery, but I received no low battery notifications. I knew I had little battery left, approximately 14%, when I started using the phone this afternoon. After some heavy usage (streaming audio to bt headset while simultaneously surfing the web) the phone shut down, giving me the “goodbye” screen, without prior notice (I should have seen them, as I was looking at the screen all the time).

edit retag flag offensive close delete

Comments

1

I've noticed that sometimes (too often) the notification system just doesn't work anymore. The only "Fix" I have found is to restart lipstick.

Tanghus ( 2019-12-04 00:36:12 +0300 )edit

@Mohjive You do not happen to have persistent logs enabled? Battery level changes are logged, so getting journal from period leading to battery empty shutdown might be informative.

spiiroin ( 2019-12-04 08:37:34 +0300 )edit

@spiiroin: I have not enabled them manually, so not if they're not on by default. If you tell me where to enable them, I can do that in case I get the behavior again.

Mohjive ( 2019-12-04 10:59:02 +0300 )edit

1

@Mohjive Instructions for persistent logging can be found from here: https://together.jolla.com/question/4842/how-to-enable-more-detailed-and-persistent-logs-on-jolla-device/?answer=27827#post-id-27827

If you get battery empty shutdown, the logs from the previous bootup (i.e. the one which should contain events leading to the battery empty situation) can be obtained with:

devel-su
journalctl -b -1 > previous-boot.log

The result is likely to have lots of data we do not really care about. You can use something like:

grep -e DSME -e mcebat_update previous-boot.log

to locate where the interesting part starts - when battery gets around 10 percent or so. Which looks something like this:

... mcebat_update(): battery_level : 11 -> 10

and then cut out the leading part.

spiiroin ( 2019-12-04 13:38:04 +0300 )edit

I've noticed that sometimes (too often) the notification system just doesn't work anymore. The only "Fix" I have found is to restart lipstick.
Tanghus ( 2019-12-04 00:36:12 +0300 )edit
@Mohjive You do not happen to have persistent logs enabled? Battery level changes are logged, so getting journal from period leading to battery empty shutdown might be informative.
spiiroin ( 2019-12-04 08:37:34 +0300 )edit
@spiiroin: I have not enabled them manually, so not if they're not on by default. If you tell me where to enable them, I can do that in case I get the behavior again.
Mohjive ( 2019-12-04 10:59:02 +0300 )edit
@Mohjive Instructions for persistent logging can be found from here: https://together.jolla.com/question/4842/how-to-enable-more-detailed-and-persistent-logs-on-jolla-device/?answer=27827#post-id-27827
If you get battery empty shutdown, the logs from the previous bootup (i.e. the one which should contain events leading to the battery empty situation) can be obtained with:
devel-su journalctl -b -1 > previous-boot.log
The result is likely to have lots of data we do not really care about. You can use something like:
grep -e DSME -e mcebat_update previous-boot.log
to locate where the interesting part starts - when battery gets around 10 percent or so. Which looks something like this:
... mcebat_update(): battery_level : 11 -> 10
and then cut out the leading part.
spiiroin ( 2019-12-04 13:38:04 +0300 )edit

Answer 1

1

answered 2019-12-04 09:45:34 +0300

spiiroin
13237 ●151 ●224 ●199

moderator

Possibly related to: https://together.jolla.com/question/209293/bug-volumealarm-indication-barscreenshot-notification-at-top-missing/

-> when the misbehavior gets triggered, it is likely to affect all notification banners.

But as that should not stop audible battery low beeps from occurring, this could be something else too - e.g. sometimes some devices like xperia 10 do not emit battery level change events on every percent value

-> some slippage / delay near battery empty can happen.

But getting from 14% to battery empty shutdown without any indication in between would be something new

-> I'll file internal ticket about this.

If anybody can get logs from period leading to battery empty shutdown without notifications, it would be helpful.

edit flag offensive delete publish link

Comments

Could me listening to audio resulting in not getting the audio warnings? Or not hearing them (if not directed to my headset)?

If I know where to find the logs, I can post them.

Mohjive ( 2019-12-04 10:57:12 +0300 )edit

But getting from 14% to battery empty shutdown without any indication in between would be something new

Or maybe the BMS chip inside the battery isn't calibrated correctly ?!

(It thinks that it's still having 14% left, then suddenly notices that the voltage is to low, jump straight to 0% and the smartphone promptly goes into shut down. Such ">10% to ~0%" jump happen a lot with dis-calibrated laptop batteries).

DrYak ( 2019-12-04 14:17:27 +0300 )edit

Missing low battery notifications

Comments

1 Answer

Comments

Question tools

Stats

Related questions

Missing low battery notifications

Comments

1 Answer

Comments

Question tools

Public thread

Stats

Related questions