Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
battery management on thinkpad yoga 12 #183
I have some problems with charging thresholds on thinkpad yoga 12 (2nd generation). It is possible that these issues eventually led to battery being permanently turned off (at least as far as anything I knew to try).
Potentially related issue:
I did not associate the two issues at first but then googling for reports of similar problems I noticed that even Lenovo's own windows software/firmware may have been reported as having a potential of turning off the battery. One of Lenovo technicians mentioned that as a possibility...
Hi, sorry to read of such issues.
Fix: only Lenovo can and should(!) fix their faulty firmware.
Blacklisting: i need the output of
EDIT2: please be more specific about "favorite thresholds":
Just to clarify one comment in your reply: you are saying that this is a
Anyway, output of requested commands is below (run without acpi-call
+++ System Info
+++ System Status
On 01/26/2016 11:26 AM, linrunner wrote:
To further clarify:
You're aware that charging will never start when the charge level is equal or higher than the lower threshold?
May we summarize your symptoms as follows
If you're not shure about
Let me first clarify. Let's say the thresholds are 76-80 and battery is at 80%. I then issue tlp fullcharge command or reset the thresholds to 96-100 and run tlp start. Should the laptop start charging? I was assuming that charging in this situation would be a design behavior but it's not what was happening. If the start threshold were 76% (or any other number that worked), changing thresholds would have no effect until laptop discharges below 76% once.
I have reinstalled acpi_call and will test to give you better answers.
From my recollection the answer to the first question was yes, but as you will see from the output of tlp-stat -b below, right now thresholds are not reported correctly. (Probably my recollection was wrong.)
The answer to the second question is complicated. Generally, thresholds would be obeyed. But if I were to change thresholds, I would need to go below old charge threshold once before new threshold behavior takes over.
And then there was intermittent behavior when the laptop was below (far below) start threshold but would not start charging. It would say "charging" but the rate would be zero (sometimes it would be .001, sometimes it would be similarly small negative number). I understood this in situations when it was at/near stop threshold, but as I said, it also happened far below start threshold. And again, here I do not know whether it was an issue with tlp, firmware or faulty motherboard. But I hope this answers your third question.
Below is the output of tlp-stat -b shortly after installing acpi_call.
--- TLP 0.8 --------------------------------------------
+++ ThinkPad Extended Battery Functions
+++ ThinkPad Battery Status: BAT0 (Main / Internal)
tpacpi-bat.BAT0.startThreshold = 76 [%]
I don't believe in that, it's just the new lower threshold.
As you already admitted, your memory is betraying you. Could we agree that from now on you only write about new test results on your current hardware?
Things that may have happened in the past on a defective systemboard are irrelevant. Only current evidence and results you can reproduce are acceptable for a bug report. And please be brief. OK?
I suggest you set some new thresholds like 
then  discharge on battery to 45% and check if charging starts when AC is connected and stops at 70%. Next 
and check if charging starts immediately.
It's in the FAQ :-) You don't need to uninstall anything. Just comment out the config threshold values and issue
So here is what happens.
Interesting. Seems to me that unplugging/plugging the AC actually activates newly written thresholds. You could as well try to unplug a few seconds only . Powering off and on (not rebooting!) is another option .
I think you'll have to live with this quirky behaviour. I can't do anything about it in TLP.
EDIT: third option to activate the thresholds may be to issue
Thanks, I guess I will have to live with that. I just worried that this quirk and maybe other firmware bugs could have cause my not-charging at all problem.
Btw, this is even quirkier than you think. To clarify: tlp setcharge X Y, then discharge to Z (either running on battery or with tlp discharge, I tried both on the old motherboard), then tlp fullcharge and plug/unplug (tlp fullcharge and replugging can be ussied any number of times in any order; can reboot in between, poweroff-unplug-plug-boot, anything I could think of). The results:
I was wondering whether this somehow could be related to tlp-stat -b reporting the same start and stop thresholds unless those thresholds are defaults.
No, the charging does not start until I go below original X (at least) once. I am actually not sure if it is just once -- I am checking whether somehow 76% start threshold stuck. At least at the moment, my tlp-stat -b shows 96% and 100% thresholds and yet when I plug in the laptop upower shows no charging. So I 'm figuring out how low I need to go for charging to start.
To be honest I'm slightly afraid to check the opposite direction. Right now I'm at 88% and if I plug the laptop in, upower shows laptop as charging but the number for charging rate is the last discharge number and the total energy is not increasing. I am worried that if lower threshold stick permanently, putting X'<X will permanently change my start threshold to something below 76%.