-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better limitter #2
Comments
Actually, it do have this feature currently. It is just not configurable (can be added in the future). When you set a limit to I will try to add a configuration for this in the next few releases. |
Hi, configurable upper and lower limit is implemented in the lastest commits, see https://github.com/charlie0129/batt#upper-and-lower-charge-limit . This feature will be in the next release. The files below are the binaries for the latest commits, in case you want to test it now. batt-v0.1.0-beta.4-2-g7833398-checksums.txt |
As I can see working, but one bug: |
Yes, I see. The reason why your mac starts charging between min/max is that when your Mac restarts, the charging state is always set to enabled by macOS (this behavior cannot be altered). So your mac is always charging after a reboot. When Restarting the daemon shouldn't have this problem because the charging state is kept (disabled) even if daemon is down (until rebooting or other major power event happens). There is one possible solution to solve this. We can store the charging state before rebooting and restore it after rebooting. Of course it may introduce more code complexity. But since it only affects rebooting (I think Macs don't reboot often) and the charging limit is still working (It will just charge to the upper limit, which is fine in my opinion, for a rare event.), I may not work on it in the near future. Of course, pull requests are welcomed. |
I agree with you. |
I'm here again, charging with two thresholds working not as desired (imho):
idea, don't know possible it is or not: here is part of log
|
IMO, this is expected.. Just keeping the lid open is the easiest way to make it keep charging to the upper limit.
There are two sleep modes: I have already delayed But I can't do anything about Another way to solve this is to disable the disable-charging-pre-sleep feature |
Idk, but according small research, there are working solution to prevent force sleep on lid close. I will made impl for myself, but can make PR for control api. |
Interesting. Does preventing forced sleep come with other drawbacks? Previously, I know this can be done but I'm afraid of other side effects so I didn't dig deep. It's great if you can make a PR to implement it. I will add your id to acknowledgements :) |
Classical charge limiter have 2 levels:
When we have battery charged up to limit 1.) and still does not discharged to level 2.) charging does not started
This logic prevent unnecessary small charing
Can you add this functionality?
The text was updated successfully, but these errors were encountered: