Comment 3 for bug 1540062

Here is another graph when this issues is reproduced again.

It shows the problem with upower history (orange) not containing enough data to generate a graph corresponding to the actual capacity of the device (which confuses users a lot)

Then it shows over the last hour the effect of the adjustment function in the battery driver when the capacity (in purple) drops quickly from 21% to 0% then oscillates between 0 and 1 for 30 minutes until the device really dies (device was at 0% when voltage reached 3.4V then shutdown at 3.0V)

Now, there are the following possibilities:
1. The battery meter returns wrong data to the driver (calculation of the capacity is incorrect for example)
2. UI_SOC and SOC diverge and the adjustment is not triggered.
3. There is a battery calibration or a battery profile issue