Battery Buddy support thread

Applications
142

Sounds great! Will be good to be looking after the battery. Thanks for the great app.

1 Like
143

I don’t know if it’s related to Battery Buddy 4.4.0 beta4, but after installing it and testing the upper limit of charging (it was fine, charging turned off), I can’t charge the mobile anymore when discharging to the set limit of 22%, more here

Before installing it, charging worked fine for me. But it could be a coincidence, it might not be related to BB.

144

X10 IV
Today I charged for the second time since installing v. 4.4.0 beta4.
Conditions

  • BB settings: charge interruption limit 85%;
  • OS settings: Threshold not activated, Charging mode: normal

The mobile phone was charged until it was fully charged at 100% (the 85% charge interruption limit did not work).
It’s a change from the first attempt, I don’t remember what the settings were in the SFOS, because in the meantime I was solving the JP2 charging error and changing the settings on other devices for comparison.

146

JP2026

  • discharge low the set limit - notification works
  • charging up to the specified limit works, but with this finding: charging ends (the current drops and has a negative sign, the charging percentage does not increase, but the status remains “charging”) the status changes to discharging only after disconnecting the charger
147

It’s logical that the status remains ”charging” because probably the phone is trying to keep the charge at upper limit. Btw, charging in iPhone (to be my ex-phone soon) works the same way.

1 Like
148

On the X10 III and 10 IV, it works so that when charging is complete (reaching the upper limit set in BB), the status changes to “discharging”.

149

Noticed this as well. Jolla Phone works a bit differently here, it would require more work to get working properly. So I’m likely not doing that for the next release, but I still need to do the translations work I mentioned for it.

1 Like
150

I translated SK_sk, I don’t know if I messed something up when working with github. :frowning:

151

JP2026
With BB 4.4.0-0 beta4, I charged JP2 a second time. The result is different from the first charge.

Conditions

  • battery system settings: saving mode Not activated; charging mode Normal,
  • charger Anker 140W PD (previously Sony 25W non-PD),
  • BB announced discharge to the lower limit of 22%,
  • BB upper charge limit set to 85%.

Charging progress and termination

  • charging in the lower half approx. 5000 mA/25-30 W; in the upper half approx. 1500 mA/14-16 W
  • charged to approx. 90% (I checked the status when it was 89%)
  • BB showed low negative current, status: Charging
  • the charger displayed zero charging power (not charging)

EDIT: next charging confirmed the previous finding (charging ended at 88%, not at the set 85% in BB)

152

Hi @direc85 ,

This is a little more info on the 10V community port. Sorry for not feeding back faster. I hope you have not yet made an effort into incorporating the proposed charging solution that I posted about previously. The detail in this post has been discussed briefly on the 10V community port forum topic. Importantly, the learning in this post, and the 10V thread, is the result of many peoples work and effort.

Further testing after my initial report revealed that using /sys/class/battchg_ext/smart_charging_interruption to suspend charging doesn’t work. It turned out a kernel watchdog resets this back to it’s default value every 30 minutes. So altering the value, stops the charging, but only for 30 minutes.

We also tried to use /sys/class/power_supply/battery/input_current_limit to suspend charging. Which was initially effective. But this too was reset by the same watchdog after 30 minutes had lapsed.

As it turns out, charging can be suspended by using both /sys/class/qcom-battery/restrict_chg (setting to 1 activates the restricted current value set next, 0 is default) and /sys/class/qcom-battery/restrict_cur (setting it to 0 sets a charge current of 0, 1000000 is default). The good news is that the watchdog does not touch these settings, so they can be used permanently - no resetting after 30 minutes.

In the case of batterybuddy, is it easy enough to use two files to stop charging? I am not sure. But @sharks took this further to ensure the inbuilt battery ageing protection works.

The community port of the 10V now has a helper script, inbuilt into the port, to suspend charging with the above restrict_chg and restrict_cur settings:
echo 1 > /run/qcom-charge-control/trigger suspends charging, and,
echo 0 > /run/qcom-charge-control/trigger allows charging to resume.

This methodology is not effected by the watchdog, and seems to be reliable. It has been tested now for ~ 1 week by a couple of people. So I think this is a solution that actually works - unlike my previous suggestion.

This helper file will be only on the 10V community port devices, not the official port devices. The devices do identify themselves differently I believe. ssu s reveals Device model: Xperia 10 V (xqdc72 / community). Hopefully that can help you include these changes just for the zambezi community port.

Let me know if any further information is required, otherwise I do help you can add support for this phone to batterybuddy when you get some time.

Thanks again for the work on a great app, and possibly including these changes in the future.

4 Likes