Fully discharging a battery and charging it back to full charge again wears it out sooner than you might expect. Battery Buddy can help you increase the battery lifetime by automatically pausing and resuming charging. You can set alerts for low and full enough charge levels, too.
New! Version 4.3.0 adds support for PineTab, developed by nephros! Thank you!
New! Version 4.2.0 adds support for setting maximum charge current for selected devices.
New! Version 4.1.0 adds initial support for Jolla Tablet.
Important: Sailjail support is enabled in Battery Buddy 4.0.0-1, which means it requires at least Sailfish OS 4.3 to work properly. For Sailfish OS 3.3 and up you should be able to use Battery Buddy 3.17-1. For older versions Battery Buddy 3.15-1 should work fine. For Sailfish OS 2.2 you have to download the legacy build.
The application comes with a service component that takes care of charger control and alerts. This means that the application doesn't have to be opened for alerts and limits to work - which is against Jolla Store policy, and hence worth mentioning here. You can control the service from the application (start/stop and enable/disable on boot).
There is now a logging option, which can be accessed via the Settings page pulley menu, with three logging options. You can copy the log contents, too, so submitting the service log for debugging purposes is now a lot more convenient! Using --verbose and --debug flags still work as before.
Please note that the charger control mechanism may not work for every device out there. So far it has been successfully tested with the following devices:
For some devices there's partial support:
Please let me know if it works for your device, or if it doesn't work!
Bug reports and translations are most welcome!
If you like my work and would like to support me, you can now buy me a coffee.
Source code can be found in GitHub.
4.3.2-1
4.3.1-1
4.3.0-1
4.2.5-1
4.2.4-1
4.2.3-1
4.2.2-1
4.1.1-1
4.1.0-1
4.0.0-1
3.17.0-1
3.16.2-1
Full changelog in GitHub.
Comments
Historyscholar
Tue, 2020/11/17 - 12:56
Permalink
Can you update Chinese translation?I have update it.
direc85
Wed, 2020/11/18 - 18:07
Permalink
I just merged a small update yesterday, did you mean that?
I added one new string ("Current:" as in electric current) so there's not that much to update this time :)
moses_s
Tue, 2020/11/10 - 01:28
Permalink
Bug: I second the last commentor and confirm that on the Sony Xperia 10 Plus (mine is the dual-sim model i4213) there is a bug since the Sailfish 3.4 updade (I am running v3.4.0.24 Pallas-Yllastunturi). The app does not stop the charging of the phone once "Pause charging limit" setting is met. By the way, thanks a lot for a great, great app, direc85!
direc85
Sun, 2021/01/31 - 22:56
Permalink
Thanks, this should be now fixed in 3.8-1.
zipotron
Fri, 2020/10/30 - 09:40
Permalink
Hello! I just want to report a regression bug, since the last two updates, when the charge reach the 'stop charging limit', is true that charge don't rice more but seams that charging doesn't stop, and before was stopping and discharging until the low limit. I hope the report is useful for improve this amazing app.
direc85
Sun, 2021/01/31 - 22:56
Permalink
Sorry for the delay, but it should be fixed in 3.8-1. Can you test it?
PawelSpoon
Tue, 2020/10/27 - 08:55
Permalink
Works now well on xperia 10 !
direc85
Wed, 2020/10/28 - 14:36
Permalink
Great! Thanks for the update!
rob_k
Wed, 2020/10/21 - 22:14
Permalink
Yes, solved after reboot. Thanks!
rob_k
Tue, 2020/10/20 - 09:04
Permalink
Battery Buddy makes a pling sound when charging from 75% every minute, even though my settings are 89%, 5 minutes. Great app nonetheless! It's up to date, so 3.5-2 I guess.
rob_k
Sat, 2020/11/21 - 20:11
Permalink
This is still the case (or again). My XA2 has a new installation of Pallas 3.4.0.24. The Dutch weather app WelkWeer did not work after installation, and it appeared that Jolla has changed some things deep down. For instance, I do no longer have a user nemo but defaultuser instead. And the directory /run/state is no longer there.
So, I am up to date with Battery Buddy. My settings are:
- Start background service: on
- Automatic charging control: on, 89% and 65%
- Notification both off, settings at 89% and 30%, both intervals at 10:00
Still, after plugging in the power USB cable, I get a notification when battery level reaches 75%, and I get it every minute. What can be the cause of this?
direc85
Sat, 2020/11/21 - 21:21
Permalink
Hi, and thanks for reporting.
There has always been something unreliable about delivering changes from the GUI to the daemon. I have improved it a few fimes, but it's still not that reliable, it seems. The glorious state of Works For Me (TM) is not good enough - I'll see what I can do. (Well, if you lads and lasses have good ideas, please share them.)
About 3.4.0.24: It seems that I completely forgot that `nemo`isn't the default user, but `defaultuser` instead (pun not inteded actually). This requires rethinking some areas around the same config changes, and I think using DBus would be The Right Thing (TM) to do, but I'll have to learn that first.
I'm quite busy at the time, so this will take some time.I opened tickets in GitHub. I'll open a ticket regarding this in GitHub.
direc85
Tue, 2020/10/20 - 09:16
Permalink
Try stopping and starting the service using the buttons, or reboot the device.
Historyscholar
Mon, 2020/10/19 - 08:59
Permalink
Can you update Chinese translation?
direc85
Mon, 2020/10/19 - 09:33
Permalink
Updated and released in 3.5-2, as well as the French translation!
stickedlabel
Sat, 2020/10/10 - 00:09
Permalink
Looks like after last system update the service is unable to start. I installed BB after taking last system update of SFOS 3.4
direc85
Sun, 2020/10/18 - 19:39
Permalink
Thanks for commenting.
I only did rather quick testing, and didn't notice that some parts of the application doesn't work anymore. On my Xperia XA2 Ultra, charge control still works, but stopping/starting the service using the buttons don't work anymore. It looks like the services are both up and running just fine, but I need to double check that.
Edit: Oh shoot, SFOS 3.4 is now a) updated b) released to all. I really gotta bump this up!
oxygenh
Tue, 2020/10/13 - 12:33
Permalink
I have same trouble.
enrish
Sat, 2020/06/13 - 21:38
Permalink
That was a quick implementation. Thanks!!!
zipotron
Sat, 2020/06/13 - 13:45
Permalink
Hi Derec! amazing improvement the daemon, just report a bug, plus the issue that if your battery is charged more than the lower boundary of charging regime and you plug the phone because you what to charge is not going a charge... there is another issue, if you deactivate the daemon, when restart is active again, could be nice to remember the active status and boot.
Thanks!!!!
direc85
Sun, 2020/06/14 - 11:43
Permalink
Thanks! I actually forgot to check if the service is running or not when starting the app, fixing that soon!
There really should be a setting for enabling or disabling the service at boot, good idea! Fixing that soon, too!
enrish
Fri, 2020/06/12 - 00:20
Permalink
Thanks. I see, under the hood it's quite complicated, but the solution you described would be nice, hope it will turn out.
As for the feedback here is more: just now i run again into the ' connected but not charging issue'... This time I tried to press the 'Pause' button in the app (it was not already paused as 'Resume' was greyed out) then 'Resume' again and it started charging. So no need to reboot the phone...
enrish
Thu, 2020/06/11 - 00:57
Permalink
Hi Direc, I have just noticed the daemon implementation in the last update. While it's handy and requested by many, it'd be nice to have a toggle to disable it, a bit like in Depecher.
Some people like to have as little daemons running as possible, even just for battery life.
More importantly, if something goes wrong with the app and it interferes with charging, it would be nice to be able to turn it off.
Two days ago I connected the phone to the charger and the status was 'connected' but not charging. I closed battery buddy, disconnected and reconnected, the system icon was showing the charger was connected but the battery wasn't charging. I thought the cable was broken and moved it a bit, but nothing worked until I restarted the phone. So now I guess it might have been the daemon underneath that got 'stuck' and kept charging disabled... and restarting the phone stopped the daemon.
Anyway, thanks once more for this very essential app!
direc85
Thu, 2020/06/11 - 09:50
Permalink
Thanks for the feedback!
Originally there was only a one-shot daemon to fix the file permissions issue regarding charger control, and that always ran at boot. One solution could be to bring that back, and then run the current daemon in user context. That way - I think - it would be possible to create the UI elements to stop and start the service.
I have been thinking about that one for a while, I'll create an issue about it in GitHub.
objectifnul
Mon, 2020/06/08 - 10:19
Permalink
Service restart doesn't help (J1 phone): "Could not find any zN.M subdirs!"
direc85
Mon, 2020/06/08 - 13:09
Permalink
That specific message is ambience-related, and you can fix it by creating the said dir :)
objectifnul
Mon, 2020/06/08 - 13:52
Permalink
Okay, but the link ambience-batterybuddy is beyond my understanding.
nephros
Sun, 2020/06/07 - 23:20
Permalink
Yes, service restart seems to fix the misfiring alerts.
objectifnul
Sun, 2020/06/07 - 16:10
Permalink
Works fine with my XperiaX but not with my Jolla phone:
When I execute /usr/bin/harbour-batterybuddy-daemon in fingerterm, I get a "Segmentation error".
direc85
Sat, 2020/06/06 - 23:39
Permalink
It might be that the daemon loses touch with the config file. I'll see what I can do about it.
Pages