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

[3.0.3 Hossa/Jolla1 BUG] battery saving mode

asked 2019-05-04 19:13:05 +0300

Leon gravatar image

updated 2019-05-09 21:09:19 +0300

Dakon gravatar image

In the preferences I activated the battery save mode and set the threshold to 20%. Nevertheless the saving mode gets activated with a full charged battery. Right now, it is 91% charged and the saving mode is active (showing a leaf in the upper left corner). Any hints?

edit retag flag offensive close delete

Comments

Switch of the saving mode and wait what hapens when threshold is reached...

rgrnetalk ( 2019-05-04 20:07:57 +0300 )edit

Change the threshold to something else and then put it back to 20%.

Giacomo Di Giacomo ( 2019-05-04 22:24:36 +0300 )edit

Do you have Situations App installed and configured to do something on low battery?

I see the problem that it can't determine the battery state correctly any more, and always thinks it is low.

nephros ( 2019-05-09 09:45:03 +0300 )edit

I never see a leaf in the upper left corner since 3.0.2 I think. No matter how the battery saving mode gets activated. can anyone else confirm that icon bug?

donni106 ( 2019-05-15 02:57:05 +0300 )edit

2 Answers

Sort by » oldest newest most voted
5

answered 2019-05-10 14:46:16 +0300

Leon gravatar image

updated 2019-05-10 14:47:27 +0300

I see my misconception now. The UI shows _one_ checkbox/radio-button and suggests herewith that the selection below (e.g. 20%) only gets applied if this "battery save option" is enabled. Rephrased: the state of this feature is not well represented in the UI, so then also not mentally on users side. One solution would be a second radio-button for the threshold (would substitute the "never" option) and a different german translation (Energiesparmodus aktivieren -> Energiesparmodus sofort aktivieren), means "immediately activ" . Its then clear for the user that the first option gets applied immediately despite what the current battery level is, and the second when the battery level threshold gets reached. Nevertheless there is a fallback behaviour of the "forced power save mode", it gets deactivated when a USB connection starts to charge the battery. UI: So, the second option should be grayed out when the first option is active (to preserve the current config to fallback, either off or with a threshold).

image description

edit flag offensive delete publish link more

Comments

I can confirm that the german translation is confusing and initially I also had to try out the options to understand how it is supposed to work.

Alex ( 2019-05-11 01:02:21 +0300 )edit
1

answered 2019-05-05 16:42:45 +0300

spiiroin gravatar image

The "activated the battery save mode and set the threshold" makes me wonder...

There are two controls in that settings page. One that activates "forced power save mode" and another one that is used for setting activation battery level threshold (and activating non-forced power save mode).

Getting power save mode activated when battery level is above the set threshold sounds like if you had activated the forced psm toggle.

Can you run mcetool |grep -i -e psm -e sav from command line? Apart from possibly different threshold value it should output something like:

Power saving mode:                   enabled (inactive)
Forced power saving mode:            disabled
PSM threshold:                       20 (%)
edit flag offensive delete publish link more

Comments

@spiiroin: Thanks for your answer. I get the same result as you, now (forced switch is off). I think the problem is the UI design (in combination with the translation) that leads the user wrongly. See my own answer below ...

Leon ( 2019-05-10 14:46:37 +0300 )edit
Login/Signup to Answer

Question tools

Follow
3 followers

Stats

Asked: 2019-05-04 19:13:05 +0300

Seen: 536 times

Last updated: May 10 '19