10% low battery warning not appropriate.

asked 2017-07-21 17:55:53 +0200

6918 ●221 ●320 ●327

On SFOS 2.1.0.11 Intex Aquafish i notice that the battery warning at 10% doesnt work very well. Based on a average say 6hr battery runtime under normal use 10% should give you 36minutes of using the phone.

What i notice is that often with ~10min of the low battery warning the recharge device warning comes on and a couple minutes the device shuts down. In addition the closer it gets to shutting down the hotter it gets as well.

What it should be doing is warn when 2hrs are remaining, 1hr is remaining and 30min is remaining.

It should not provide multiple repeat warning with screen unlocked and active and the user obviously already being aware if low battery at 10% or lower.

Ideally once 30min is remaining it should automatically turn off wifi, GPS, bluetooth, reduce screen brightness and clear memory for apps that arent active.

edit retag flag offensive close delete

Comments

1

6 hours max battery with "normal" use?? i would trash every phone with these values. my j1 - still with first battery lasts 3days... but overall the possibility to choose between % battery and x min left (based on usage data) seems a legit idea.

kaktux ( 2017-07-21 18:12:15 +0200 )edit

last 10% was always like that for me=( on j1 and on FP2. Maybe not 10mins exactly but still not proportional to other 90%

virgi26 ( 2017-07-21 22:51:27 +0200 )edit

1

I am using Situations app .. Under set X % values of battery charge Situations changes the settings and cuts off the choosen functions.

N9Sailfish ( 2017-07-23 08:41:49 +0200 )edit

4

answered 2017-07-22 05:56:55 +0200

olf
10393 ●104 ●201 ●158

updated 2017-07-22 22:59:34 +0200

Well, how long a battery lasts at x% charge is dependent on the age and past usage of the battery, its temperature (as you already noticed), the power draw of the device (which is highly variable) etc.

Hence a time based scheme would implicitly provide a very inaccurate (and "jumping", dependent on actual power draw) remaining run time.

But there is Battery notifier 2 for you (easily installable via Warehouse), which offers an additional warning below a battery charge percentage of your choice.

edit flag offensive delete publish link

Comments

@olf its a workaround and ill try it out and will report back if its stable, actually works amd is reliable.

DarkTuring ( 2017-07-22 21:44:25 +0200 )edit

@DarkTuring, if third party software alleviating SailfishOS weaknesses are "solutions" or "workarounds" depends on one's point of view. Well, the "workaround" perspective is often founded by the "I want it from Jolla" tune, to which I wholeheartedly disagree and which I am tired of hearing.

But sure, Battery notifier 2 runs "stable, actually works and is reliable" on my Jolla 1 phones for almost a year, now (otherwise I would not have recommended it). I assume that to be the case for Jolla C / Intex AquaFish, too. If not, Battery notifier 2's author is usually quite responsive to proper bug reports via Openrepos comments.

P.S.: Specifically Battery notifier 2 really looks a little bit like a "workaround", as it employs an additional battery charge level warning scheme instead of altering the existing one. But properly configured everything works perfectly (at least for me), and Battery notifier 2 has a couple of nice extra features. :)

olf ( 2017-07-22 22:21:22 +0200 )edit

1

answered 2017-10-11 23:07:40 +0200

olf
10393 ●104 ●201 ●158

Hunger Meter (available in the Jolla Store) does exactly what you want: Displaying an estimated remaining runtime (on its second page).

But if you (also) like its monitoring capabilities (i.e. on Hunger Meter's first page), then you should try SysMon, which is a far more complete monitoring application. Mind that configuring SysMon to autostart correctly may need some manual intervention, once.

edit flag offensive delete publish link

Comments

Hunger Meter would be more usefull if energy consumption was highlighted by application/process similar to Mac OS activity monitor showing you items consuming significant battery, this would have to be normalized of course by process usage, so that if you use one app 12hours its divided by 12 versus an app you only used 1hour is divided by 1.

DarkTuring ( 2017-12-16 21:59:51 +0200 )edit

@DarkTuring, please address feature-suggestions and bug-reports directly to the authors of the specific software! In this case: https://github.com/miska/HungerMeter
Making such statements here at TJC constitutes just plain complaining and is not useful.

olf ( 2017-12-17 00:37:26 +0200 )edit

10% low battery warning not appropriate.

Comments

2 Answers

Comments

Comments

Question tools

Stats

Related questions

10% low battery warning not appropriate.

Comments

2 Answers

Comments

Comments

Question tools

Public thread

Stats

Related questions