Hello, long time no update!
There’s 4.4.0 beta3 available in GitHub, please test it and give feedback! Both positive and negative feedback are appreciated! Please mention what device and SFOS version you’re on; it was compiled for SFOS 5.1 so it so BB may not work on SFOS 5.0 and/or earlier. Due to things, I don’t have older targets installed, but if there’s demand I can compile it using an older target - if you need it, please comment below.
JP2026 (5.2.0.16):
The rest seems fine to me (quick test only).
EDIT:
X 10 IV Lineage based port (5.1.0.11)
EDIT:
X 10 III (5.1.0.11)
What a pity that you haven’t included those few tiny additions to support the Nagara port (the Xperia 1 IV & 5 IV)… 
Then I’m forced stay on my modified 4.3.2-1.
I relly think the positive/negative current indication serves no purpose at all.
Why not Math.abs(value) all the things?
It’s just current, signs have no real meaning.
Well, current direction technically does matter and is well defined. Current out of the source/battery is positive. But it seems that some kernel drivers don’t respect that.
Edit: but I of course agree that this is unimportant technicality.
Alao the ‘Health’ thing keeps confusing folks.
‘Health’ needs to be renamed - any suggestions?
For some context, the health status as reported by the kernel /driver gives the current (as in momentary) condition the battery is in.
“Unhealthy” conditions are things like overvoltage, or too high or too low temperature. Details depend on the driver.
Health: good means only one thing: no unhealthy conditions currently apply.
It does NOT indicate a long-term status, like how much ‘charge’ is left and such.
Which unfortunately most assume it to mean exactly.
I have not yet tried the new update, but I thought it worth reporting that BatteryBuddy works great on my X10IV Lineage based port!
Since “health” does not “fit, is not used” for technique in the Slovak language, I translated it as (kondícia) condition. I don’t know if it also describes the essence of the phenomenon/state in other languages.
For me, that mark has a symbolic meaning, because the current flows into or out of the accumulator (charging/discharging). But you are right that technically current is an absolute value. Perhaps an arrow could be used, like on stock boards ↑↓ instead of a minus sign.
I’d suggest ‘Battery state’ and the other one ‘Status’. In Polish it should be ‘Stan baterii’ and ‘Status’, whereas at present they are both incorrectly translated as ‘Stan’ (‘Stan’ and ‘Stan baterii’), which I reported a few years ago here: Battery Buddy support thread - #78 by wetab73
P.S. Maybe even better than ‘Battery state’ would be ‘Current state’ but I’m afraid that again the word ‘current’ might confuse some people… So maybe ‘Present state’?
Thanks for the suggestions!
I’ve been thinking about just calling it ‘Warnings’, or ‘Warning conditions’ and then have good->no warnings as value.
Or go the funny route and call it ‘Battery Mood’. With ‘good->happy’. Or ‘Feeling’.
JP 2026 5.2.0.16
App indicates now charger connected on. 
However back- ground operation mystery? Just when you keep app open, start pushing stop and start buttoms at set percentage value, app gives a sound. Otherwise no indication. Just like it was with earlier version.
Thanks for the feedback, that’s great!
Charging control works for me, but the sign seems to be wrong indeed. I’ll have to double check those. (I don’t have X10IV with Lineage, so I can’t investigate that.)
Whoops, missed those! They’ll be in the next beta.
Negative current means the battery is draining, positive means it’s charging. The sign can be redundant, but it is explicit, and helps debugging.
Yeah, something like “condition” or “state” could work. Could be hidden when normal…
I already have more fixes coming in left and right, stay tuned! And I’m probably touching many translation strings as well, so just a heads up 
Seems to work fine on Jolla 2. But very limited what shows in information
Fantastic! Thank you!
And sorry for being lazy, next time I’ll do it the proper way via Github as PR or something
Having the sign visible is also very useful in real life as it lets one quickly see whether the battery is actually gaining or losing power. There are situations when despite the battery being charged the power consumption of the device is higher than the current provided by the charger - it happens with e.g. weaker chargers, low current (0.5 Amp) USB 2.0 ports, poor USB cables and extensions, etc. With this sign visible, you can see it at a glance, so it is extremely useful.
Great idea. I don’t recall ever seeing anything else but OK on any of my phones, so maybe it’d be useful to only show it when there is some ‘other than OK’ condition, but highlighted to attract user’s attention…
Big thank you for this fantastic application that I’ve been enjoying for so many years already!
Two small PRs created.
Decided to just call it “Warning(s)”.
There’s now a 4.4.0 beta4 available. This fixes daemon-reload and service restart during install, which I did manually by old habit, and also fixes Jolla Phone behaviour a bit, along several other changes and improvements. Please do give it another round!
There’ll still be (at least) beta5 which will contain (at least) the translation changes.
A quick short check:
Excellent work, thanks!
Hi @direc85 ,
Thanks for all the great work on Battery Buddy. It seems to be a really great utility - that is partly working on my 10V - I have tried the 4.4 beta 4 you linked to just above. Thanks to @Sharks I am running a fantastic community port based on lineage os on my Xperia 10V (Zambezi).
Much of battery buddy is working well. All the stats are there, current limitation works on charging (the same logic that you implemented for Nagara works on zambezi for the charging current), time to full works etc. Unfortunately on start, the log notes that Charger control file: not found. And indeed Battery Buddy fails to stop charging when the specified percentage is reached.
I wonder, would it be possible for you to include Zambezi specific charging control files in Battery Buddy? Note that I think this works, but my knowledge of what is actually going on is minimal.
There seems to be a good way I have found to stop the battery charging:
/sys/class/battchg_ext/smart_charging_interruption (can be either 1 or 0). Setting this to 1 certainly seems to stop the charging. The current shown in battery buddy goes to 0mA. So I don’t know if this is magically matching charging current to consumption, or if it is just blocking the ability for battery buddy to see current. The battery remains at the percentage it was when plugged in, so I would say using this file is the best option on the 10V that I have been able to find. Setting this back to 0, allows charging to resume.It would be great if you could add it, so then the 10V can be fully supported by Battery Buddy “out of the box”.
If this doesn’t look like the right path to go down, please let me know, and I will keep digging for the correct/better approach.
Thanks for the app, and looking forward to getting it working on the 10V community port.
Sure, I can add that! Thanks for testing!