maemo.org - Talk - LocCommand

maemo.org - Talk (https://talk.maemo.org/index.php)

- Development (https://talk.maemo.org/forumdisplay.php?f=13)

- - LocCommand (https://talk.maemo.org/showthread.php?t=69084)

Hey there,

I had this idea while in the cinema, wouldnt it be cool, if within the theatres themselves, phones would turn off or, switch to silent automagically. This would be very handy for in school, as well. So if in school, turn on silent, if at home, turn off silent.

I was relatively new to the the n900 in general, so I wrote some Python code on and off to try and get this desired behavior.

I decided the best way would be to try something similar to crontab.

So heres some code:

loccommand-serv.py works as the server, which checks every so long for change in location, using the gps, and runs predefined commands based on this location.

loccommand.xml is the XML file, which contains details of the commands, co-ordinates, and the radius around which the location should remain active.

loccommand-gui.py is the GUI Editor (uses pyQT) which just parses the xml, displays it in a table for editing, and then parses it back to xml, and writes it back the file.

I was at a loss on how to make the server part, run continually, something like a windows service, or a daemon process, I would think. Theres also the rather big problem of the inaccuracy of the GPS. At least for me, it rarely gets a location within half an hour, if not using a wifi or mobile connection.

I'm posting this here, as I'm in my final year of secondary school here, so my time is quite scarce, as I have numerous projects to complete.

So any ideas, on further implementations, or improvements?

~mc_teo

I can see this is a very good idea for those whom don't have strict schedules. Such as working overtime at a job when you normally set through alarmed to turn off silent mode at a specified time which was defined as your normal time but not your overtime which just happened to occur on that day.

In some ways I would prefer this to be somehow integrated into alarmed as part of a GPS event at a certain location. This can thereby minimise the amount of servers (or basically daemons) that needs to be running in the background.

Then again if Shapeshifter (alarmed developer) isn't keen on integration I suppose portions of his idea can probably be copied (after obtaining appropriate permissions of course) for adaptations of his work.

I am not a programmer so I cannot help much I'm afraid. I can definitely see the benefits and if it was integrated into alarmed it would be ideal as alarmed already has plenty of built-in functions that could potentially benefit if one uses GPS rather than setting specified times and hoping that everything would fall into place.

you might want to have a look at dwimd: http://maemo.org/packages/view/dwimd/

http://hg.alexanderweb.de/dwimd-main...aa9/README.txt

Quote:

dwimd
=====
the ambient sensing gestalt optimizer for the n900

dwimd works by sampling sensors and taking user-defined actions
based on a user-written config file.

Howto
=====
1. Look at http://hg.alexanderweb.de/dwimd-main...alex_config.py
how a config file should look like.
2. Write your own config file. Every function is executed every 30 seconds.
You can use the values and actions explained below.
3. Copy your config file to /etc/dwimd/dwimd_plugins/configs. It should have
a .py extension.

Reference
=========
dwimd ships the following sensors:
* history: Not really a sensor, it buffers data and returns the buffered
data as a list.
* load: Provides the system load as `load`.
* locationcheck: Provides the current location as `location`. Such location
objects then have a `near` method that should be called with
the name of a location that was previously defined with
`define_location`. `define_location` takes a name and either
`network_in_sight="network_name"` for wifi sensing or
`coordinates=(50, 8, 100)` for an 100m circle around
the GPS coordinates 50N 8E.
* moving: Provides `moving` and `not_moving_for_5min`. The latter is useful
for autoaway.
* orientation: Provides `orientation`, `face_up` and `on_stand`. `orientation`
either contains "portrait" or "landscape" or the same string
with " (inverse)" appended (XXX check). The other two variables
are booleans.
* time: Provides `time` which supports `time.between("12:00", "15:00")` like
calls.

It ships the following actions. These are activatable by using the verbs explained below.
* availability: Should be activated with a status like "online" or "away". Additionally,
`availability_message` can be activated with the status message.
* lock: If activated with `off`, avoids that the screen locks.
* profile: Can be activated with a profile name that should be switched to (like
"silent" or "general").
* wifi: Should be activated with a network name as the value.

These verbs are provided to activate an action:
* require(object, value) triggers an error if somebody votes against it
* suggest(object, value) is a weak vote (defaults values but does not count in votes)
* vote(object, value, votes) is used for voting
* force(object, value) overwrites requires and votes
where object is a gestalt name or an action.

Gestalts can be defined like this:
define_gestalt("Default",
availability="available",
profile="general")
They group similar action values.

TODO
====

* Adjustable sample rate for every plugin.
* Planned inputs:
gps, time, weekday, load, location, orientation
charging, playing, display, locked, noise level, ringing
* planned outputs:
availability, profile, cellular, secure, lock, wifi
os.system

The project seems in a limbo state, nevertheless it might have parts and ideas and concepts that are worth pondering.

Keep on hacking, something like a location aware event trigger daemon is quite a useful and missing bit.

cheers
jOERG

Thanks for the feedback,

I am quite busy at the moment with last year of school stuff. (We base our university entry solely on one major three week exam, at the end of academic year), so I am currently studying for a mock exam.

When I finish those exams, I will be keen to take up some projects like this in earnest. the DeSumE Nintendo DS Emulator is another project, I would like to work some more on, in C++.

So thanks, for your feedback.

~mc_teo