Editing User:Magick777/My N900 Scheduling

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Learn more about Contributing to the wiki.

= What do I need to schedule =

== Backups ==
* Regular backups to be scheduled from alarmed at such time as I have a suitable backup script.

== Maintenance ==
* Perform any software or network updates that may be required
* Reset GPRS data counters monthly (done via Alarmed)

== Profiles ==
* Minimise annoyances overnight (but allow alarms to work)
** Turn off e-mail checking & notifications overnight

== Optimisations ==
* Power management - maximise battery life opportunistically
** force 2G mode when phone is in pocket/not being actively used
* Perform updates when on WLAN to minimise transfer via GPRS

= Criteria for scheduling events =

== Cron-based scheduling ==

Certain actions need to be scheduled according to time of day, week or month, i.e. as per the scheduling behaviour of the Unix cron daemon. There seem to be two viable ways of achieving this, via [[fcron]] and [http://talk.maemo.org/showthread.php?t=46594 Alarmed]. The [fcron] page is well-written and useful, but I think [http://talk.maemo.org/showthread.php?t=46594 Alarmed] is the better tool for the job, partly on the strength of the GUI and partly because it uses an existing daemon rather than adding another one.

== Phone status & event scheduling ==

=== Charger plugged in / removed ===

When charging starts, it usually means that the phone is at home and therefore that we want to cancel power saving measures, enable WiFi and so forth. However, this may not always be correct and it would be nice to incorporate some sort of test that we actually are at home and that the actions taken are correct. So, what we need is a script that enables WiFi but sets a timer to disable it again after a fixed amount of time, plus a script that reacts to a successful connection to the home WiFi network by disabling the timer and letting WiFi remain.

This way, if I'm charging from an external power pack in the field, it'll trigger and have a look for WiFi, then decide after one minute that it can't reach my home network so it'll turn WiFi off until I explicitly ask for it. We'll handle the WiFi switching in the same way as the existing WiFi Switcher applet (by nicking the scripts from it), meaning that the existing switcher application can also be used as a manual override to our automations.

The end result of all this will be:

* Using dbus-scripts, when charging commences run the script wifi-enable-home. This will enable the WiFi (if disabled) but also run the script /opt/usr/bin/wifi-kill which, after sleeping for 60 seconds, will disable WiFi again.

* When we get a connection to my home Wifi, run /opt/usr/bin/wifi-unkill which will kill the script that was set to disable WiFi.

=== Device locked / unlocked ===
=== Display on / off ===
=== Specific WLAN connected / disconnected ===

== Calendar-based scheduling ==
== Location-based scheduling ==

* When not at home, turn WiFi off unless and until explicitly requested
* When at home, turn WiFi on and autoconnect

= Changelog for scheduled events =

This will be moved to the bottom of the page later.

2010-07-15

* Installed 'alarmed' from extras-devel, had to ln -sf python2.5 to /usr/bin/python
* Configured alarmed to reset GPRS data at 0000 on 1st of each month

= What have I scheduled? =

== Opportunistic power saving ==

I am working on [[User:Magick777/OPS]].

=== CPU frequency scaling ===
More or less as described in [[Overclocking#Underclock.2FOverclock_when_phone_is_Locked.2FUnlocked__.28by_Fecn.29| this script]], though I implemented it with dbus-scripts-settings. On phone locked we set "kernel-config limits 250 500" and on unlock we set "kernel-config limits 500 850".

=== Set 2G radio mode ===

For battery life, I want the phone to put itself into 2G mode except when I am intensively using the data connection. It would seem sensible to trigger the switch to 2G any time that the phone is locked and remains so for a minute or two, in the assumption that it is in my pocket. But, I would not want this to happen if a) I am on a call b) the phone locked unintentionally and I unlock it again c) the phone is on charge or d) it was in 2G mode in the first place. I do not want it to be constantly switching between the two; it should change when it has good reason.

So, the phone locking should trigger a script that 
*tests whether it should take action and 
**if so, waits a minute to see if I unlock the phone again and 
***if I don't, goes ahead and kills 3G.

This would be achieved by running a script on lock that will sleep for 60 seconds and then switch to 2G mode. On an immediate unlock, we can test if that script is running and kill it thus leaving the dual mode intact.

By what criteria to restore 3G is more difficult; it is by no means automatic that I require 3G because I unlock the phone or plug in a charger. However, as soon as I want to access e-mail, Web or VoIP, 3G will be required. Therefore my options are

*never automate the switch to dual mode and switch manually when required
*automate the switch based simply on using the phone
*automate the switch when I launch any application that requires it
*automate the switch based on data traffic flow

Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!

Summary:

Cancel | Editing help (opens in new window)

Retrieved from "https://wiki.maemo.org/User:Magick777/My_N900_Scheduling"

Personal tools

Navigation

Views

Editing User:Magick777/My N900 Scheduling

@@ Line 19: / Line 19: @@
 = Criteria for scheduling events =
-== Time-based scheduling ==
+== Cron-based scheduling ==
 Certain actions need to be scheduled according to time of day, week or month, i.e. as per the scheduling behaviour of the Unix cron daemon. There seem to be two viable ways of achieving this, via [[fcron]] and [http://talk.maemo.org/showthread.php?t=46594 Alarmed]. The [fcron] page is well-written and useful, but I think [http://talk.maemo.org/showthread.php?t=46594 Alarmed] is the better tool for the job, partly on the strength of the GUI and partly because it uses an existing daemon rather than adding another one.