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
What is the issue? (required)
While the 'maintain %' command works as expected (excluding accuracy mentioned in #295), other functions such as 'charge', 'maintain stop' and 'calibrate' seem to be affected by the limit set by the 'maintain' command.
I don't use the GUI version. Everything here is only applicable to the CLI version.
What exactly did you do to produce the issue? (required)
Steps to reproduce the behavior:
Execute 'battery maintain 80'
Wait until the charge level reaches 80% and the charging stops
Execute one of the following
a. 'battery maintain stop' or with any other (!= 80) target percentage
b. 'battery charge 100'
c. 'battery calibrate'
d. 'battery discharge' with the percentage lower than 80 maintained previously
Observe unexpected behaviour:
a. the tool reports that the charging has been enabled: Battery at 80% (attached; remaining), 11.867V, smc charging enabled
but the next battery status results in smc charging disabled
(--force-discharge helps to discharge, but once the charge level has reached the set value, charging gets enabled again and it goes back to initial 80)
b. the maintaining mode is not switched to charging to 100%
c. the battery discharges (to be checked if it goes down to 15% or not) then returns to around 80%
d. reporting Enabling battery discharging followed by the endless waiting to discharge. After the charge state changes (from 80 to 79%), the power source becomes 'Power Adapter' again and the battery is maintained at this level (cat .battery/maintain.percentage shows 50 because I set it 50 by executing 'battery maintain 50')
I also observe that the log message 🚨 Calibration process have been stopped appears after every 'maintain' command execution, even though the calibration supposed to be cancelled long time ago.
Expected behavior (required)
CLI tool consistently executes given commands
What is the issue? (required)
While the 'maintain %' command works as expected (excluding accuracy mentioned in #295), other functions such as 'charge', 'maintain stop' and 'calibrate' seem to be affected by the limit set by the 'maintain' command.
I don't use the GUI version. Everything here is only applicable to the CLI version.
What exactly did you do to produce the issue? (required)
Steps to reproduce the behavior:
a. 'battery maintain stop' or with any other (!= 80) target percentage
b. 'battery charge 100'
c. 'battery calibrate'
d. 'battery discharge' with the percentage lower than 80 maintained previously
a. the tool reports that the charging has been enabled:
Battery at 80% (attached; remaining), 11.867V, smc charging enabled
but the next
battery status
results insmc charging disabled
(--force-discharge helps to discharge, but once the charge level has reached the set value, charging gets enabled again and it goes back to initial 80)
b. the maintaining mode is not switched to charging to 100%
c. the battery discharges (to be checked if it goes down to 15% or not) then returns to around 80%
d. reporting
Enabling battery discharging
followed by the endless waiting to discharge. After the charge state changes (from 80 to 79%), the power source becomes 'Power Adapter' again and the battery is maintained at this level (cat .battery/maintain.percentage shows 50 because I set it 50 by executing 'battery maintain 50')I also observe that the log message
🚨 Calibration process have been stopped
appears after every 'maintain' command execution, even though the calibration supposed to be cancelled long time ago.Expected behavior (required)
CLI tool consistently executes given commands
Related issues
#282
#290
#295
#301
#302
#321
The text was updated successfully, but these errors were encountered: