-
Notifications
You must be signed in to change notification settings - Fork 25
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
issue: Charging threshold setting not found. #104
Comments
It seems unlikely. Based on the contents of your BAT0 folder, those variables all have different purposes unrelated to setting the charging threshold. |
If I change the battery with a modern, third party one could there be a chance of working? I guess what I ask is, is the variables reported directly from the battery, or the BIOS? |
Interesting question! It would need to be an ASUS battery, but I think it's not the battery, it's the charger that is part of the board that has the capacity to expose this through the kernel module By the way, so fun to see you here, I was an avid OSNews reader decades ago..! |
I suggest having a look at the extensive documentation for the Battery Health Charging extension for GNOME. They support and have a page for Intel Macs. Maybe that all that is required is installing the applesmc-next kernel module like they write. It mentions the same API endpoint as |
Subject of the issue
I'm using a Macbook Air 2015, and it says that "Charging threshold setting not found". Going inside the folder BAT0 it has only these inside:
alarm current_avg manufacturer subsystem voltage_min_design
capacity current_now model_name technology voltage_now
charge_full cycle_count power temp wakeup42
charge_full_design device present type
charge_now hwmon2 status uevent
Any chance it has that feature, to charge it up to a point only but it's named differently?
Your system
Macbook Air 2015
Mint 22
6.8 kernel
Version
1.2 (Latest)
Steps to reproduce
No response
Expected behaviour
No response
Actual behaviour
No response
The text was updated successfully, but these errors were encountered: