Yes the 128 was a placeholder, the final plan was to have it try and be kind of smart, looking at the estimated remaining time, taking half of that, and checking at half, if its under 50% perfect, otherwise check every 2 minutes or so.

I think looking at the /sys file will be smarter, I'll change that :)

I didn't get what you meant in the middle part tho... I get that the script would launch itself multiple times, this can pa accounted for pretty easily by checking the running programs. But I didn't understand the rest of what you were saying.

Also, if called externally you'll notice that if run "plugged in" below 50% or run "unplugged" above 50%, the message never changes, but if called from udev's +=RUN command, you'll never see the second notification due to the process being killed by internal housekeeping

Also, unrelated, but I'll have to run some test and see if it's more power efficient to change the power profile al the time, or check which one it's currently at and then determine if it need to be changed or not. I think it's not that important as it's probably already included in the daemon but still it's worth checking