I hacked together a perl script with a similar goal but it used SIGSTOP when the battery got too low instead of killing the process. I didn't use it very much and I don't know if that's a viable solution for most applications. However if that does work for the app, that's probably better than killing it outright.
Additionally there is a signal SIGPWR which is supposed to be used when a battery is running low, but I doubt that is used very much. The solution you have I would call power profiles but at the application level in addition to the system level. As a user, I think this absolutely should be available if it isn't already in Fremantle, preferably with a GUI normal people can use. Attila Csipa wrote: > A RFC for people who know details about Fremantle's power aspect: > > I wrote a python script called Shepherd for my Diablo N810, basically a > glorified CRON that has not just time, but a power and connectivity axis, > too. > This means you can define for various processes: > > * hours allowed > * connection type allowed (I guess you could define exact connections, > but > I never got that far) > * power requirements (plugged in, or a minimum % of battery) > * user inactivity (also started to implement, but never actually finished) > > I used it for a couple of things... Flipclock (turn on if charging), > transmission (turn on if charging and on WLAN between 2AM and 8AM) and > killing > maps if battery gets below 25%. It's very rudimentary, no GUI or other magic > - > it just launches the app if it is not already running and conditions are met, > and kills it if they aren't (but only if they were started by the shepherd > app). > > Now, my question for people already working with Fremantle would be whether > it > already includes similar scheduling/battery/bill saving functionality (or > parts of it) and if you think a script like this would be interesting to get > ported to Fremantle and get a proper GUI ? > > _______________________________________________ > maemo-developers mailing list > [email protected] > https://lists.maemo.org/mailman/listinfo/maemo-developers > _______________________________________________ maemo-developers mailing list [email protected] https://lists.maemo.org/mailman/listinfo/maemo-developers
