Set battery charging threshold / charging limit / charging mode Battery Health Charging: An extension to maximize the battery life of laptops by setting their charging threshold or modes. Compatible with - Asus - LG - Samsung - Sony/Vaio - Huawei - Toshiba/Dynabook - System76 - Lenovo (Ideapad, Legion) - Thinkpad - Panasonic - Fujitsu - Acer (dependencies: kernel module) - MSI (dependencies: kernel module) - Tuxedo (dependencies: kernel module) - Slimbook (dependencies: kernel module) - Tuxedo IntelQC71 (dependencies: kernel module) - XMG IntelQC71 (dependencies: kernel module) - Eluktronics IntelQC71 (dependencies: kernel module) - Purism Librem (dependencies: kernel module) - Gigabyte Aero/Aorus (dependencies: kernel module) - Dell (dependencies: custom package libsmbios) - Dell (dependencies: custom package Dell Command Center) - Apple Macbook Intel-series chip (dependencies: kernel module) - Apple Macbook M-series chip (dependencies: custom kernel) - Razer (dependencies: custom package razer-cli) - Framework (dependencies: kernel module) Not all models are comaptible. Please read about the compatibility and dependencies of your device on github link below. https://maniacx.github.io/Battery-Health-Charging/
Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.
Version | Status |
---|---|
65 | Active |
64 | Active |
63 | Active |
62 | Active |
61 | Inactive |
60 | Inactive |
59 | Inactive |
58 | Inactive |
57 | Inactive |
56 | Inactive |
55 | Inactive |
54 | Rejected |
53 | Inactive |
52 | Inactive |
51 | Inactive |
50 | Inactive |
49 | Inactive |
48 | Inactive |
47 | Inactive |
46 | Rejected |
45 | Rejected |
44 | Inactive |
43 | Inactive |
42 | Inactive |
41 | Inactive |
40 | Inactive |
39 | Inactive |
38 | Rejected |
37 | Inactive |
36 | Inactive |
35 | Inactive |
34 | Inactive |
33 | Rejected |
32 | Inactive |
31 | Inactive |
30 | Inactive |
29 | Inactive |
28 | Inactive |
27 | Rejected |
26 | Inactive |
25 | Inactive |
24 | Inactive |
23 | Inactive |
22 | Inactive |
21 | Inactive |
20 | Inactive |
19 | Inactive |
18 | Inactive |
17 | Inactive |
16 | Inactive |
15 | Inactive |
14 | Inactive |
13 | Inactive |
12 | Inactive |
11 | Inactive |
10 | Inactive |
9 | Inactive |
8 | Inactive |
7 | Inactive |
6 | Inactive |
5 | Inactive |
4 | Rejected |
3 | Inactive |
2 | Inactive |
1 | Inactive |
It's better to create your settings in extension.js and then pass that instance to the classes needed settings. It will be much easier for 45 port too: https://gjs.guide/extensions/upgrading/gnome-shell-45.html#extensionutils
Thanks JP. For 44-43-42 version, I will leave it as is, since it is working, and it becomes a handful, if I go through that road of testing 29 different configurations on 3 distros. However, for the port for gnome45 is almost ready by passing settings in extension and other neccesary stuff. One question I have is, how can I continue supporting both Gnome45 version and my previous version Gnome44-43-42 version (Incase there are some bug or adding new device feature)? Yesterday, I was on fedora rawhide (Gnome45) and was testing my Gnome45 port for this extension, and when you approved version 25 (which only supports Gnome44-43-42 and not Gnome45 as added metadata.json), the extension manager updated automatically to version 25. I was under the assumption that extension-manger wont install, upgrade or run the extension if, shell-version I am running is not list in metadata.json So is it possible to support both versions under the same name/uuid Or do I have to upload Gnome45 extension under a new name/UUID?
Maybe the version was the same or not higher for testing, because ego supports multi versioning. Always add a higher version than the latest version here for testing.