I have installed Linux Mint 22 in a DELL laptop with a buggy ACPI implementation (the kernel complains about it during boot). The laptop hangs if it goes to sleep (I tried various Linux distros/kernel-versions, the result is the same).

Because of that, I have disabled SLEEP in the firmware (latest version for that laptop btw). So basically, when you close the lid, nothing happens (it just locks the screen).

However, sometimes you might be in a hurry and you close the lid to do something else, and then you forget about it. The result would be for the battery to run dry, which eventually destroys the battery.

My question is: what would be the best way to setup an audible alarm if the battery reaches 20%?

  • Eugenia@lemmy.mlOPEnglish
    10·
    1 month ago

    Ok, I managed it by myself after a bit of tinkering. This is the bash script:

    #!/bin/bash
while true
    do 
        battery_level=`cat /sys/class/power_supply/BAT0/capacity`
        battery_status=`cat /sys/class/power_supply/BAT0/status`
        if [ $battery_status = "Discharging" ] && [ $battery_level -lt 21 ];
        then
            /usr/bin/aplay  /home/eugenia/Music/alarm.wav
        fi
       sleep 120
    done

    Obviously change the path the .wav audio file to suit yours (I downloaded mine from the internet). Then, save the file (in my case, I named it battery.sh), make the script file executable ( chmod +x battery.sh via the terminal, or via the file manager).

    Then add it to the Startup Applications settings panel on your distro (usually gnome and cinnamon have one). The alarm will sound if the battery reaches below 21%.

    • nous@programming.devEnglish
      12·
      1 month ago

      Worth running shell scripts though https://www.shellcheck.net/ (has a cli as well). Finds lots of common issues that can blow up scripts when input is not what you expect. With links to why they make the suggestions they do.

      Line 4:
        battery_level=`cat /sys/class/power_supply/BAT0/capacity`
                      ^-- SC2006 (style): Use $(...) notation instead of legacy backticks `...`.

Did you mean: (apply this, apply all SC2006)
        battery_level=$(cat /sys/class/power_supply/BAT0/capacity)
 
Line 5:
        battery_status=`cat /sys/class/power_supply/BAT0/status`
                       ^-- SC2006 (style): Use $(...) notation instead of legacy backticks `...`.

Did you mean: (apply this, apply all SC2006)
        battery_status=$(cat /sys/class/power_supply/BAT0/status)
 
Line 6:
        if [ $battery_status = "Discharging" ] && [ $battery_level -lt 21 ];
             ^-- SC2086 (info): Double quote to prevent globbing and word splitting.
                                                    ^-- SC2086 (info): Double quote to prevent globbing and word splitting.

Did you mean: (apply this, apply all SC2086)
        if [ "$battery_status" = "Discharging" ] && [ "$battery_level" -lt 21 ];
        • nous@programming.devEnglish
          10·
          1 month ago

          The problem with bash scripts is they tend to explode in unexpected ways when thing don’t go as intended. This could be one of the command you run returning some expected or not output which might work now but might not in the future. Best to program bash defensively.

    • Deckweiss@lemmy.world
      3·
      1 month ago

      Since you say

      change the path the .wav audio file

      fyi, the sys BAT paths are also different per laptop. Just in case it doesn’t work for somebody else or for you on a different laptop.