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
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
