I wonder if people might think a more generic approach, e.g. a shepherd app could be useful in such cases (I wrote one for myself, but it's quite hacky, GUI-less python so not exactly for end-users). It's basically a glorified CRON that has not just time, but a power and connectivity axis, too. You can define:

• 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 - launches the app if it is not already running and the conditions are met, and kills it if they aren't (but only if they were started by the shepherd app). Not sure if Fremantle can do such things on it's own or if there is interest for turning this into a 'real' app...