How to modify the trigger value?

[ecoholic84]

Hey there! Thanks for building this. I just discovered this very helpful widget and was wondering if I can tweak the value of trigger from default to something of my like. For example, I found that the default value of Conservation Mode is 75-80%, that is, the laptop wont be charged more than 80% and I assume it is the limit of charging that is set to this widget by default.

I would like to change the limit to 60-65% for personal interests and was wondering if I can do that. If yes, could you please explain how/where is the tweaking to be done? As a newbie Linux user, this would be much appreciated because this would do much good to my laptop's battery lifespan.

Thank You.

[enielrodriguez]

Hi! I don't know much about this, but I do understand that this feature of defining a custom threshold is not available on all Lenovo laptops, from what I have read, only ThinkPads can do this:
Limit battery charge on Lenovo laptop
Setting Charge Threshold

However, you have given me a couple of ideas and maybe I will develop a feature to achieve what you want:
1- Try to automatically detect if the laptop has that feature and add an option to change the threshold.
2- Those that do not have this feature, achieve the same effect by deactivating and activating the conservation mode automatically until the desired threshold is achieved.

[ecoholic84]

That makes sense. It seems like even though my device supports Conservation Mode, it doesnt support custom threshold (Its a Yoga). I don't have the mentioned stop_charge_thresh and start_charge_thresh files in the mentioned directory from the arch thread you have mentioned. I did do echo 1 > /sys/bus/platform/drivers/ideapad_acpi/VPC2004:00/conservation_mode mentioned in the same thread, let's see if it works.

And BTW I just noticed that when I boot up my machine, the widget says "The Conservation Mode is not available" (screenshot attached). But when I delete the widget and add it again, it shows the ordinary turn on, off setting. Anyway, Thanks for the reply! I will add here if I find something that works for me.

[enielrodriguez]

The error you mention should no longer occur in the latest releases. Please check it, and if it has not been solved, let me know. Thank you!