the phone should switch itself off before completely draining battery

Worth linking back to the following related defect: https://bugs.launchpad.net/indicator-power/+bug/1317858

android does warn when it goes below 15% ... i wonder if we should not do teh same here ...

Not Fix Committed yet because it's not mentioned in the spec.

Needs spec documentation.

MPT, please change these statuses to "Triaged" once the spec defines this behavior.

Specification updated. <https://wiki.ubuntu.com/Power?action=diff&rev2=74&rev1=72>

upower already has logic to detect at 10%, 3% and 2%

It looks like upower should be handling this; it has triggers for hibernation / power off at configured battery percentage.

I'll see if I can figure out why that's not kicking in.

mzanetti mentions that this bug is critical to him, because every time a frieza device reaches 0% charge he's blocked from further using it because it needs to charge up to some safe value before being able to turn it on.

It is not limited to frieza. Once you have 3 or 4 developer devices, you will frequently run into this issue. Whenever you need to test something on that particular device, rest assured it wants to be charged for 10 mins before turning on :)

As a FYI : some of those devices may have an IC that allows for NOBATOP
operation. For example, the TI BQ24160 was popular in Android handsets and
has support for such a mode.

On Mon, Feb 15, 2016 at 2:28 PM, Michael Zanetti <
<email address hidden>> wrote:

> It is not limited to frieza. Once you have 3 or 4 developer devices, you
> will frequently run into this issue. Whenever you need to test something
> on that particular device, rest assured it wants to be charged for 10
> mins before turning on :)
>
> --
> You received this bug notification because you are a member of Indicator
> Applet Developers, which is subscribed to indicator-power in Ubuntu.
> https://bugs.launchpad.net/bugs/1317860
>
> Title:
> the phone should switch itself off before completely draining battery
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1317860/+subscriptions
>

Just to add a note here:

The upower config is NOT using percentages. It's using the calculated remaining time...

From /etc/UPower/UPower.conf

# Policy for warnings and action based on battery levels
#
# Whether battery percentage based policy should be used. The default
# is to use the time left, change to true to use the percentage, which
# should work around broken firmwares.
# default=false
UsePercentageForPolicy=false

Alright, so I did some tests and here's what I needed to change ON THE PHONE.

UsePercentageForPolicy=true
CriticalPowerAction=PowerOff

The default critical power action is: HybridSleep

Those changes work fine on the phone, but upower has only 1 configuration file, there is no different configuration for the desktop and the phone.

If we change the values like I noted above this is going to affect the desktop.

I think we should create a separated config package for each device config.

BTW,

we could leave UsePercentageForPolicy=false and use the time estimation instead, but on the phone we need to change the action to PowerOff as HybridSleep is not supported.

Status changed to 'Confirmed' because the bug affects multiple users.

If we want to avoid changes the upower package itself, we could add an override using the environment variable
UPOWER_CONF_FILE_NAME
the providing a modified file in the ubuntu-touch-session package such as UPower.override

It was further suggested to make the changefrom comment #15 in ubuntu-touch-settings