Package Details: auto-cpufreq-git 1.9.6.r3.gff72e1e-2

Git Clone URL: (read-only, click to copy)
Package Base: auto-cpufreq-git
Description: Automatic CPU speed & power optimizer
Upstream URL:
Licenses: LGPL-3.0
Conflicts: auto-cpufreq
Provides: auto-cpufreq
Submitter: crian
Maintainer: crian
Last Packager: crian
Votes: 18
Popularity: 0.164420
First Submitted: 2020-01-07 09:54 (UTC)
Last Updated: 2022-10-21 14:32 (UTC)

Dependencies (10)

Required by (0)

Sources (2)

Pinned Comments

OlexandrCh commented on 2020-08-13 20:44 (UTC) (edited on 2020-08-13 20:44 (UTC) by OlexandrCh)

Currently, we don't need to run --install on AUR
After installing from AUR, we need to start the systemd service.
systemctl enable auto-cpufreq
systemctl start auto-cpufreq

and check if it enabled and running with
systemctl status auto-cpufreq

Latest Comments

1 2 3 4 Next › Last »

teetest commented on 2023-03-23 23:32 (UTC)

If anyone want to change governors use command "sudo auto-cpufreq --force=governor". You must create a folder in /opt name as auto-cpufreq.

sh1sh1n11 commented on 2022-11-12 08:23 (UTC)

@crian, thanks much for clarifying that. That makes a lot of sense. Please ignore my previous comment in that case, and sorry for the trouble!

crian commented on 2022-11-12 08:21 (UTC)

@sh1sh1n11 this is the git version of this package. It is build straight from git with all the new changes. The battery indicator is fixed in upstream but not yet released in a new version.

sh1sh1n11 commented on 2022-11-12 06:02 (UTC) (edited on 2022-11-12 06:05 (UTC) by sh1sh1n11)

Hi @crian,

Thank you very much for creating and maintaining a package build for this downstream version of auto-cpufreq! I had a question regarding commit "a345eb5924a2" the one made on 2022-10-21 at 16:32:28 +0200 hrs with the title Fix and package version 1.9.6.r3.gff72e1e.

The upstream release version v1.9.6 has a battery indicator issue that prevents the program from running. As noted below.

Did you make any changes in that regard to fix that issue? Because your patched version mentioned above seems to be working fine with the new Battery Percentage Indicator feature. Also depending on your availability would you be so kind to share the patch with the upstream team on the above mentioned GitHub issue. That would be super helpful. Thanks again!

crian commented on 2022-10-21 15:03 (UTC)

everything is up to date!

johnjohn commented on 2022-07-13 06:54 (UTC)

I am using pyenv. To fix any installation issue, I had to change python version to system $ pyenv global system

InkedHand commented on 2022-04-10 12:43 (UTC)

I tried bobselpt's changes on the PKGBUILD and I was able to install auto-cpufreq successfully.

bobslept commented on 2021-12-25 20:59 (UTC) (edited on 2021-12-25 21:00 (UTC) by bobslept)

We use the python virtual environment on auto-cpufreq, so the current systemd service file is made for the python virtual environment.

I'm not a Arch user myself, and there are maybe better ways of doings this, but this seems to fix the issue.

Hope the maintainer find this patch helpfull.

diff --git a/PKGBUILD b/PKGBUILD
index 85ceacc..88cae6c 100644
@@ -26,6 +26,18 @@ pkgver() {
 prepare() {
     cd "$srcdir/${pkgname%-git}"
     sed -i 's|usr/local|usr|g' "scripts/${pkgname%-git}.service" auto_cpufreq/
+    cat > auto-cpufreq.service <<EOF
+Description=auto-cpufreq - Automatic CPU speed & power optimizer for Linux
+ExecStart=/usr/bin/auto-cpufreq --daemon

 build() {
@@ -39,5 +51,5 @@ package() {
     install -Dm644 LICENSE "$pkgdir/usr/share/licenses/${pkgname%-git}/LICENSE"
     install -Dm644 "$pkgdir/usr/share/doc/${pkgname%-git}/README"
     install -Dm755 scripts/ -t "$pkgdir/usr/share/${pkgname%-git}/scripts"
-    install -Dm644 "scripts/${pkgname%-git}.service" -t "$pkgdir/usr/lib/systemd/system"
+    install -Dm644 "auto-cpufreq.service" -t "$pkgdir/usr/lib/systemd/system"

rori commented on 2021-10-18 19:00 (UTC)

I ran into a problem installing this package on my system. I could not start the daemon properly using systemctl start auto-cpufreq .

The problem was pyenv, since it cause the package to be in a different location than expected. Modifying the pkgbuild and replacing python with env PATH=$(getconf PATH) python solved the problem for me.

yochananmarqos commented on 2021-08-10 15:54 (UTC)

@adrianteri: Please unflag the package.

Note: VCS packages are not considered out of date when the pkgver changes, do not flag them as the maintainer will merely unflag the package and ignore you.