diff --git a/README.md b/README.md index 4eba9a2..310d3fa 100644 --- a/README.md +++ b/README.md @@ -1,92 +1,74 @@ # Pixelbook Charge Control +## Goal +This is a small project I hacked together to preserve the battery of a +Pixelbook running vanilla Linux (in my case Debian). +What I want to achieve is that the battery is not constantly being charged +to and held at 100%, which will quickly destroy the battery. -## Getting started +The Pixelbook Linux runtime contains a tool called "ectool" which can +control the charge control code embedded in the EC. Newer EC version also +allow for a "battery sustainer" pretty much implementing what I want but the +Pixelbook (aka Eve) EC is too old to use this. -To make it easy for you to get started with GitLab, here's a list of recommended next steps. +So I came up with a bash script that can run in teh background. -Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! - -## Add your files - -- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files -- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: +For it to work you need the "ectool" in Linux. I tried to compile the ectool +from source under Debian but failed. So I took the alternative path and used +teh ChromeOS binary. But this will also not run diretcly under normal Linux +due to libc version conflicts. So I copied all necessary files one by one +and created a subdir that one can chroot into to execute the ectool: ``` -cd existing_repo -git remote add origin https://source.dpin.de/nica/pixelbook-charge-control.git -git branch -M main -git push -uf origin main +# tar tvf pixelbook-bin.tar.bz2 +drwxr-xr-x root/root 0 2022-11-14 06:19 pixelbook-bin/ +drwxr-xr-x root/root 0 2022-11-14 06:40 pixelbook-bin/sbin/ +-rwxr-xr-x root/root 1035536 2022-11-14 06:34 pixelbook-bin/sbin/ldconfig +-rwxr-xr-x root/root 38408 2022-11-14 06:40 pixelbook-bin/sbin/ec_sb_firmware_update +-rwxr-xr-x root/root 210192 2022-11-14 06:20 pixelbook-bin/sbin/ectool +-rwx------ root/root 5960 2022-11-14 06:40 pixelbook-bin/sbin/ec_battery_wa +-rwxr-xr-x root/root 10536 2022-11-14 06:40 pixelbook-bin/sbin/ec_parse_panicinfo +drwxr-xr-x root/root 0 2022-11-14 06:37 pixelbook-bin/lib64/ +-rwxr-xr-x root/root 2060112 2022-11-14 06:19 pixelbook-bin/lib64/libc-2.33.so +-rwxr-xr-x root/root 222152 2022-11-14 06:19 pixelbook-bin/lib64/ld-2.33.so +-rwxr-xr-x root/root 138360 2022-11-14 06:28 pixelbook-bin/lib64/libpthread.so.0 +-rwxr-xr-x root/root 42096 2022-11-14 06:27 pixelbook-bin/lib64/libftdi1.so.2 +-rwxr-xr-x root/root 222152 2022-11-14 06:19 pixelbook-bin/lib64/ld-linux-x86-64.so.2 +-rwxr-xr-x root/root 112456 2022-11-14 06:37 pixelbook-bin/lib64/libudev.so.1 +-rwxr-xr-x root/root 82520 2022-11-14 06:36 pixelbook-bin/lib64/libusb-1.0.so.0 +-rwxr-xr-x root/root 2060112 2022-11-14 06:19 pixelbook-bin/lib64/libc.so.6 ``` -## Integrate with your tools +This needs to be placed into some known folder. I currently put this in the +root user's home dir. Then I added `~root/bin/` to teh root user's PATH so +that scripts placed in `~root/bin/` will be found. -- [ ] [Set up project integrations](https://source.dpin.de/nica/pixelbook-charge-control/-/settings/integrations) +In `~root/bin/` I first placed a simple script that will chroot exec the +real ectool: -## Collaborate with your team +``` +#!/bin/sh +chroot /root/pixelbook-bin /sbin/ectool $* +``` -- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) -- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) -- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) -- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) -- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) +Somewhat crude but works. -## Test and Deploy +The second script in `~root/bin/` is the one controlling the charge control +then, currently called 'do_not_charge'. It will by default disable charging +under almost any circumstance, except the battery state of charge (SOC) has +dropped below 30%. Only then it will allow the charger to become or remain +active until SOF is > 80% again. In other words it will stop charging at +80%. -Use the built-in continuous integration in GitLab. +With this I still get more than enough charge in the Pixelbook for all my +tasks but on the other hand prevent teh battery from premature aging. Each +charge cycle means wear to the battery. -- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) -- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) -- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) -- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) -- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) +Please note that all this of course only works as long as the operating +system is running. Each time power is disconnected and reconnected the EC +reset the charge logic. So if the laptop is in suspend and you disconnect +and reconnect the charger it will again charge to 100% no matter what. -*** - -# Editing this README - -When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template. - -## Suggestions for a good README -Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. - -## Name -Choose a self-explaining name for your project. - -## Description -Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. - -## Badges -On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. - -## Visuals -Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. - -## Installation -Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. - -## Usage -Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. - -## Support -Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. - -## Roadmap -If you have ideas for releases in the future, it is a good idea to list them in the README. - -## Contributing -State if you are open to contributions and what your requirements are for accepting them. - -For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. - -You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. - -## Authors and acknowledgment -Show your appreciation to those who have contributed to the project. - -## License -For open source projects, say how it is licensed. - -## Project status -If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. +Enjoy! +Feedback welcome. diff --git a/do_not_charge b/do_not_charge new file mode 100755 index 0000000..d79218f --- /dev/null +++ b/do_not_charge @@ -0,0 +1,50 @@ +#!/bin/sh + +STOP_THRESHOLD=80 +START_THRESHOLD=30 + +SHALL_CHARGE=0 +IS_CHARGING=0 + +set_charger() { + if [ $1 == 1 ]; then + ectool chargecontrol normal + else + ectool chargecontrol idle + fi +} + + +while true; do + AC_STATE=`cat /sys/class/power_supply/AC/online` + if [ $AC_STATE == "1" ]; then + echo "on AC" + BAT_LEVEL=`cat /sys/class/power_supply/BAT0/capacity` + CURRENT=`cat /sys/class/power_supply/BAT0/current_now` + echo "current=$CURRENT" + if [ $CURRENT -gt 0 ]; then + IS_CHARGING=1 + else + IS_CHARGING=0 + fi + if [ $BAT_LEVEL -gt $STOP_THRESHOLD ]; then + echo "bat level > $STOP_THRESHOLD%" + echo "charger disabling" + SHALL_CHARGE=0 + elif [ $BAT_LEVEL -lt $START_THRESHOLD ]; then + echo "bat level < $START_THRESHOLD%" + echo "charger enabling" + SHALL_CHARGE=1 + else + echo "charger state OK, idling..." + fi + else + echo "not on AC, idling..." + SHALL_CHARGE=0 + fi + echo $SHALL_CHARGE $IS_CHARGING + if [ $SHALL_CHARGE != $IS_CHARGING ]; then + set_charger $SHALL_CHARGE; + fi + sleep 10 +done diff --git a/ectool b/ectool new file mode 100755 index 0000000..d4c66df --- /dev/null +++ b/ectool @@ -0,0 +1,2 @@ +#!/bin/sh +chroot /root/pixelbook-bin /sbin/ectool $* diff --git a/pixelbook-bin.tar.bz2 b/pixelbook-bin.tar.bz2 new file mode 100644 index 0000000..cd158cb Binary files /dev/null and b/pixelbook-bin.tar.bz2 differ