You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Charger Model (Apple, Third Party, Wattage,...): Apple
Charging Cable (MagSafe 2, MagSafe 3, USB-C, Apple, Third Party,...): Apple
AlDente Pro or AlDente Free: Pro
AlDente Version: 1.26.1
List or add screenshots of all enabled/disabled settings in AlDente: Charging—all enabled; Sleep—all disabled; Sailing Mode—enabled 10%; heat protection—enabled; low power mode—disabled;
MacBook used in Clamshell Mode (with the lid closed)? no
Describe the bug
A clear and concise description of what the bug is.
I set the charge limit 56% and twice I have notice that the charge limit "changed" on its own to 51% To Reproduce
Steps to reproduce the behavior: I have not been able to reproduce this
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected Behavior
A clear and concise description of what you expected to happen.
I don't expect Al Dente Pro to change such a setting Screenshots and Screen Recordings
If applicable, add screenshots or screen recordings of the issue to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
MacBook (please complete the following information):
Describe the bug
A clear and concise description of what the bug is.
I set the charge limit 56% and twice I have notice that the charge limit "changed" on its own to 51%
To Reproduce
Steps to reproduce the behavior: I have not been able to reproduce this
Expected Behavior
A clear and concise description of what you expected to happen.
I don't expect Al Dente Pro to change such a setting
Screenshots and Screen Recordings
If applicable, add screenshots or screen recordings of the issue to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: