C2 Shuts down with sudden dropped battery level after update (5.0.0.76)

REPRODUCIBILITY: Always when disconnected from PSU.
OS VERSION: 5.0.0.77 (Tampella)
HARDWARE: Jolla C2 (hw rev 1.0.0.59)
UI LANGUAGE: Dutch
REGRESSION: since 5.0.0.76

DESCRIPTION:

Some hours (today about 3hrs, but also some 5 or 8 hrs in the days after the upgrade) after disconnecting the USB-C power supply the phone suddenly shuts down and can only be rebooted properly after a power is connected.

Yesterday this happened some ten minutes after I observed the battery level around 85~90% (indicator in the top of the screen).
So the drain seemed to happen unusual quick.

After that I had no access to a power supply (on a 5 hour hike through a forest), but I tried to reboot it a couple of times to gather some phenomenology.

Common behaviour thereafter: the phone shut down every time after typing the device pin first and second time and then the sim pin.

  1. First startup the initial indicated power level was 8%, which dropped to 5% suddenly and the device shut down with the “goodby”-message.
  2. Second time after waiting (hiking, without connection to ANY power supply) a couple of minutes: The initial display of the power level was of order 38% (?!?) but shortly after the third (SIM) PIN-entry, The device warned about an empty battery and shut down with a “goodby” again.
  3. After waiting some 20-30 minutes, I switched it on again: the initial battery indicator claimed 50% which changed to 45% after the PINs, but some seconds later the “goodby” shut down occurred again.

PRECONDITIONS:

Disconnect with a fully charged battery, use the phone some 3-10 hours later. The actual shutdown seems to happen when busy interacting with the phone.

STEPS TO REPRODUCE:

  1. Disconnect from charger

  2. Use the phone normal, the battery level does not seem to drop alarmingly fast.

  3. While interacting with it (one time it happened immediately when I picked it up for the first time in the morning ) it will shutdown, claiming that the battery is empty.

EXPECTED RESULT:

A gradual decrease of battery level after disconnecting, sufficiently slow to last at least 8-10 hours without needing a recharge.

ACTUAL RESULT:

A sudden shutdown due to a reported low battery level.

MODIFICATIONS:

  • OpenRepos: yes
  • ChumGui: yes
  • SD card is luks encrypted and unlocked at boot time (not auto-mounted)

ADDITIONAL INFORMATION:

I made enquiries about this in two earlier posts:
Reply to similar looking problem

Initial attempt to report in Tampella’s release notes.

I installed BatteryLog today, just before another shutdown.
After recharging I managed to find a sqlite-database file in
/home/defaultuser/.local/share/harbour-batterylog/harbour-batterylog/QML/OfflineStorage/Databases
batterylog.targz (1.2 KB)
If there is another location where I can find logs of the battery level, please tell me.

<Content of /home/defaultuser/.cache/harbour-batterybuddy-daemon.log>
[09:51:01] harbour-batterybuddy-daemon 4.3.2-1
[09:51:01] Using /home/defaultuser/.config/harbour-batterybuddy/harbour-batterybuddy.conf
[09:51:01] Load: highAlert 82
[09:51:01] Load: highNotificationsInterval 13
[09:51:01] Load: lowNotificationsInterval 13
[09:51:01] Load: healthNotificationsInterval 13
[09:51:01] Load: highLimit 80
[09:51:01] Battery charge file: /sys/class/power_supply/battery/capacity
[09:51:01] Charging/discharging current file: /sys/class/power_supply/battery/current_now
[09:51:01] Max charge current file: not found
[09:51:01] Status file: /sys/class/power_supply/battery/status
[09:51:01] Charger status file: not found
[09:51:01] AC status file: not found
[09:51:01] Battery temperature file: /sys/class/power_supply/battery/temp
[09:51:01] Battery health file: /sys/class/power_supply/battery/health
[09:51:01] Charger control file not found!
[09:51:01] Please contact the developer with your device model!
[09:51:01] Battery: 4%
[09:51:01] Battery current inverted
[09:51:01] State: charging
[09:51:01] Temperature: 34°C
[09:51:01] Health: good
[09:51:24] Temperature: 35°C
[09:51:54] Battery: 5%
[09:51:54] Temperature: 34°C
[09:52:24] Temperature: 32°C
[09:52:54] Temperature: 29°C
[09:53:24] Battery: 6%

</Content of /home/defaultuser/.cache/harbour-batterybuddy-daemon.log>
1 Like

Just had a shutdown when I tried to start the native Camera program at 80%-battery level indication.

At the first startup without power attached, my C2 shut down again right after the SIM-pin

After connecting it to power, it booted up displaying level of 45%.
While it started charging slowly, I managed to get SystemDatascope installed and working.

Just got a phonecall and as you can see from the screenshot, after that the battery charge indication suddenly started growing significantly faster.

From that I’m pretty sure that HW is broken.

Bit weird that this coincides with the update, but alas.

Thanks, Just submitted a request for guidance at the zendesk.

I guess it’s a strange coincidence. You can still reflash to exclude upgrade a bit more.

How many is coincidence? I have same situation. I had used phone about 7 hours and it was around 50%, when I installed 5.0.0.76. 10 minutes after install/reboot phone said good bye and battery was 0%. Now I have wired phone. I have contacted zendesk.

1 Like

I recommend then to mention it in Release notes topic with link to this bug report. There might be more with this issue.

1 Like

I did mention it in 5.0.0.76. And after few days of investigation I made bug report where Hansdej was the only one to comment with similar situation. But as SFOS has been my (only) daily driver since 2014 I´m used to little hickups

3 Likes

Me too, I got the same issue the last days: 5.0.0.77, France, C2.

Also I noticed this even before the latest update on my C2. This happens especially when the phone is running for days and then suddenly there comes the drop. As suspected, I do also think it could be related to the default camera app not closing properly. In combination with other apps running simultaneously and losing network reception the power consumption is accelerating but then all over suddenly, the power consumption is increasing very much so that it’s even hard to prevent damaging the battery (the level drops very quickly). I also use SystemDataScope to check power consumption.

It feels as if a calibration of a Battery Charge Monitor is broken:

Like, if the charge is derived from some monitoring Voltage, one typically needs an offset and a “percent per mV” to calculate the remaining battery charge.
(battery_pct = offset_pct + cal_V_to_pct * V_monitor)

When my C2 indicates its charge is still firmly above 80% it suddenly dies and when I attach a power supply (before starting it up) I often see it creep up from 0 to a few percent (some hardware charge-damage protection mechanism?) and then charge VERY fast to “100%”.

If the calibration reports “100%” when the charge actually is something like 20% the device stops charging because it “thinks” it is at 100%.
Then it discharges again and at “80%” some independent security mechanism detects an (almost) empty battery and enforces a shutdown.

I submitted a tarball with rrd-files to the Zendesk, anyone knows how to load these into pandas dataframes?

The graphs below show several shutdown while the phone was disconnected from a power supply: gradual %-drops until shutdown and often a sudden much lower % at bootup.



Affected, too, also before the latest updates.

Everything seems fine until around 40% battery. It then drops within 5 minutes to less than 5% and shuts down…

So the shown percentage doesn’t seem right…

For me nothing changed with the last update 5.0.0.77:

Not always but often discharging-drop under 25% and very fast under 20/15% with same load.

That’s something else. I think it’s the same as on fingus graph. I always experience that. It seems to me like bad calibration of lower battery percentage or something like that.

That’s not Battery Log app is it?

It looks a lot like System Monitor to me.

2 Likes

System Monitor it is

1 Like