Differences

This shows you the differences between two versions of the page.

--- doc:appunti:linux:lenovo_thinkpad_l380 [2025/12/03 07:52] – [Battery] niccolo
+++ doc:appunti:linux:lenovo_thinkpad_l380 [2025/12/07 06:26] (current) – [Battery] niccolo
@@ Line 86: / Line 86: @@
 <code>
 # Battery charge level below which charging will begin when connecting the charger.
-START_CHARGE_THRESH_BAT0=75
+START_CHARGE_THRESH_BAT0=80
 # Battery charge level above which charging will stop while the charger is connected.
-STOP_CHARGE_THRESH_BAT0=80
+STOP_CHARGE_THRESH_BAT0=85
 </code>
-:!: **NOTICE**: Once configured and restarted the service, the output of ''%%tlp-stat --battery%%'' **may not reflect the configured values**. It is common on the Thinkpad that one of the two threshold values is always displayed incorrectly. Another common pitfall is that you have to discharge the battery below the old start threshold after writing the new threshold.
+:!: **NOTICE**: Once configured and restarted the service, the output of ''%%tlp-stat --battery%%'' **may not reflect the configured values**. As reported in **[[https://linrunner.de/tlp/faq/battery.html|this page]]** it is common on the Thinkpad that one of the two threshold values is always displayed incorrectly. Another common pitfall is that you have to discharge the battery below the old start threshold after writing the new threshold. I can confirm that the **charge_control_end_threshold** reported by the pseudofile does not reflect the set value but it show the same value of **charge_control_start_threshold**, neverthless the charge logic is working correctly.
-=== Setcharge: start and stop (end) thresholds ==
+=== Setcharge: start and stop (end) thresholds ===
 To change the battery charge thresholds temporarily you can issue the command:
@@ Line 107: / Line 107: @@
 </code>
-FIXME **WARNING**: It seems that there is a problem changing these thresholds: if you specify a **start** and an **end** value, the **charge_control_start_threshold** is actually changed, but the **charge_control_end_threshold** is forced to be equal to the start (as reported by ''tlp-stat --battery''). Setting the **charge_control_start_threshold** to zero will automatically set the **charge_control_end_threshold** to 100. So it seems that the ''charge_control_end_threshold'' is ignored and it is set automatically upon the start value.
+:!: **NOTICE**: As noted above, after you set the **charge_control_end_threshold**, its value is reported incorrectly by ''tlp-stat --battery'' (it shows a value equal to the charge_control_start_threshold) despite it is working as expected. So also the **Recommendations** shown by the tlp-stat command are misleading. Notice also that setting the **charge_control_start_threshold** to zero will automatically set the **charge_control_end_threshold** to 100.
-You can also trigger a battery charge to the full capacity (according to the vendor presets) issuing the command:
+You can also trigger a battery charge to the full capacity (according to the vendor presets) issuing the command (FIXME check if this is actually working):
 <code>