Openmoko - User contributions [en]

Buzz Fix

2009-04-06T08:36:51Z

Gromgull: New page: Fixing the buzzing that occurs with some GSM networks can be done with a bit of soldering, the semi official instructions are here: http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_re...

Fixing the buzzing that occurs with some GSM networks can be done with a bit of soldering, the semi official instructions are here:

http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP_rc2.pdf

TangoGPS

2009-03-01T19:40:03Z

Gromgull: added log conversion

{{Languages|tangoGPS}}
{{Application|tangoGPS}}

__TOC__

tangoGPS is a map application which can utilize Neo's built-in GPS to show your current location.

[[Image:TangoGPS1.jpg]]

Website: http://www.tangogps.org

== Running tangoGPS ==
=== [[Om 2008.8]] ===

From the freerunner connected to the internet:
<pre>
opkg update
opkg install gpsd
</pre>
{{note|I experienced hangups if gpsd was not installed.}}
<pre>
opkg install http://www.tangogps.org/downloads/tangogps_0.9.5-r0_armv4t.opk
</pre>
If opkg complains about not being able to acquire a lock, try:
<pre>pkill packagekit</pre>
To get gpsd working on the FreeRunner you have to change the configuration according to [[Gpsd#GPS_on_GTA02]].
Then start gpsd by:
<pre>
/etc/init.d/gpsd start
</pre>
If you get an error about no GPS device in /etc/default/gpsd execute:
<pre>
echo "GPS_DEV=\"/dev/ttySAC1\"" > /etc/default/gpsd
</pre>
Now you must power up the GPS-chip by opening the "Settings" application and setting the GPS entry to "on". Now you can run tangoGPS and wait until it get's a GPS fix. This can take up to a few minutes.

=== [[Debian]] ===

tangoGPS is a very nice GPS mapping application. The latest version is available in [[Debian]].

It depends on gpsd which conflicts with frameworkd in fso-frameworkd, but there is a package available that provides
the gpsd interface to clients while using the services of the FSO frameworkd daemon, fso-gpsd. The install.sh script for the Debian distribution on the OpenMoko already installs it. To add tangogps run

# apt-get install tangogps

To turn the gps on, you have two options.
You can start the gps application in [[Zhone]], this will turn on the gps device for you or you can manually turn
on the gps device using
# echo 1 >/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron

Now you should be able to start tangoGPS from the X-mouse start menu (must have XFCE installed) :
Start > other > GPS & Map

'''Issues:'''
* Both gpsd and the framework publish GPS data through dbus, though with different interfaces. This suggests a number of possible solutions.
** gpsd or the framework could implement the other's interface (along with their own).
** a translator could read one interface and emulate the other. This is what fso-gpsd does.
** the framework could have an option to read data from gpsd.
** ogpsd/gypsy could be extended to be backwards compatible with the majority of gps applications.

=== FSO Milestone 3 ([[OpenmokoFramework]]) ===

There are two various GPS interfaces -- (1) one provided with default gpsd and (2) the other provided by ogpsd (part of the frameworkd). tangoGPS requires the ad 1 and it obtains information from gps from the dbus interface provided by gpsd.

On FSO milestone 3, there is tangoGPS pre-installed as well as both gpsd and ogpsd (see <code>/etc/frameworkd.conf</code>, section <code>ogpsd</code>). As mentioned above, there also exists a fso-gpsd package, that converts from ad 2 to ad 1 (unfortunately fso-gpsd is not in default image and must be installed with <code>opkg install fso-gpsd</code>).

You cannot have both "providers" (ad 1 & ad 2) running, but you can have ad 2 (recommended for FSO) and "convertor" (fso-gpsd) providing the ad 1. To get usable tangoGPS on FreeRunner, one has to:

# check that <code>/etc/frameworkd.conf</code>, section <code>ogpsd</code> reads GPS data from the right device (<code>/dev/ttySAC1</code>)
# if changes were made to configuration, one should restart the frameworkd -- <code>/etc/init.d/frameworkd stop && /etc/init.d/frameworkd start</code>
# check that gpsd is not running -- <code>/etc/init.d/gpsd stop</code>
# check that fso-gpsd is installed and running -- <code>opkg install fso-gpsd; fso-gpsd</code>
# check that gps chip is online (<code>echo 1 > /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron</code>)
# finally start up the tangoGPS and locate the gps signal; it should be up in a few minutes.

Note 1: handy application for testing the gps (and gps signal strength) is <code>openmoko-agpsui</code>, see general gps info at [[Gps]]

Note 2: You can automate the process -- (1) remove the startup script for gpsd (<code>update-rc.d -f gpsd remove</code>) and (2) create a simple startup scipt for fso-gpsd (you can use current script for gpsd as a skeleton)

== Downloading Maps ==
=== pre-load for offline use ===

tangoGPS can bunch-download the map images so you don't need an internet connection while walking around. By default tangoGPS stores downloaded maps to /tmp/. This folder is lost every time you reboot the device. But you can use the "Config" tab within tangoGPS to change the "Cache Dir" location to , for example, /osm/ . So downloaded maps will be kept in the Neos flash, also after reboot. Note that the map files can take up large amounts of space, so you may want to store them on your sd card, in /media/card/osm.

If you find that TangoGPS does not remember configuration changes that you make to it, be sure to run it from the touchscreen, and not an SSH session. TangoGPS uses gconf to store its settings, and cannot access gconf when run via SSH.

Once you have set the location to a non-volatile path, you can connect your Neo to the internet by USB or WiFi at home and start downloading the maps of your area. Tap the map screen and select "map download". Now on-the-road tangoGPS will be able to show you maps in different zoom levels even though you are not connected to the internet.

=== Downloading Maps via GPRS ===
I think tangoGPS may have started working after I followed the instructions to get GPRS working with GSM multiplexing here: [[Manually_using_GPRS#Option_1:_With_GSM_multiplexing_and_with_a_GUI]]

There are steps included in those instructions to improve GPS performance. The great thing is that once you get GPRS working, you can roam with TangoGPS running and have it download maps as needed over the GPRS connection!

== Using tangoGPS for OpenStreetMap.org ==
=== creating tracks ===
tangoGPS works fine to create track for Openstreetmap. However, it records and stores a track in its native format, use [http://www.tangogps.org/downloads/convert2gpx.pl convert2gpx.pl] (see also: [http://psung.blogspot.com/2008/07/sharing-gps-tracks-from-tangogps-on.html tools])(you can also use [http://minucci.net/file/convert2gpx.py convert2gpx.py]) to convert the track to GPX (i.e to import into JOSM):

perl convert2gpx.pl 20080903_111508.log > 20080903_111508.gpx

==== tangoGPS logging format ====

<lat>,<lon>,<elevation>,<speed>,<course>,<hdop>,<datetime>

=== using OpenStreetBugs ===
[http://wiki.openstreetmap.org/wiki/TangoGPS#Using_together_with_OpenStreetBugs see OSM wiki]

== Importing Tracks into tangoGPS ==

tangoGPS does not support the import of tracks. You may help yourself by using [http://relet.net/frog/archives/68 this tool] to import GPX trackpoints as a series of POIs directly into the sqlite database which tangoGPS uses to store POIs.

== Using the TangoGPS logs ==

You can convert the logfiles from TangoGPS to other formats using gpsbabel and this style-file:

<pre>
DESCRIPTION TangoGPS 0.92
EXTENSION log
DATATYPE TRACK

FIELD_DELIMITER COMMA
RECORD_DELIMITER NEWLINE

IFIELD LAT_DECIMAL,"","%f"
IFIELD LON_DECIMAL,"","%f"
IFIELD ALT_METERS,"","%f"
IFIELD PATH_SPEED,"","%f"
IFIELD PATH_COURSE,"","%f"
IFIELD GPS_HDOP,"","%f"
IFIELD ISO_TIME,"","%s"
</pre>

Save this as '''tangogps.style''' and you can use gpsbabel to for instance convert to google-earth files like this:

gpsbabel -i xcsv,style=tangogps.style -o kml -f file.log -F file.kml

== Add POI from address ==

You can use [[gtkaddpoi]] for searching the destination address and add it as a POI.

== Using Google Maps with tangoGPS ==

Go to Config and create a new repository.

Set the url for '''street-maps''' to:
<pre>http://mt1.google.com/mt?&x=%d&y=%d&zoom=%d</pre>
for '''satellite-maps''' to:
<pre>http://khm.google.com/kh?&x=%d&y=%d&zoom=%d</pre>
for '''topographic-maps''':
<pre>http://mt.google.com/mt?v=app.81&x=%d&y=%d&zoom=%d</pre>

Check the "Inverted Zoom" box. Press save Repository Configuration and you're ready to go.

'''Since TangoGPS 0.9.5''' the "Inverted Zoom" box is no longer available because Google changed the addressing scheme; instead, select "xyz instead of zxy" and use the following URLs:
<pre>
Maps:
http://mt3.google.com/mt/v=w2.89&hl=en&x=%d&y=%d&z=%d&s=Galileo

Sat:
http://khm3.google.com/kh/v=36&hl=en&x=%d&y=%d&z=%d&s=Galileo
</pre>
<onlyinclude>
{{ApplicationBox|
Name=[[TangoGPS]]|
Description= TangoGPS is a map application which can utilize Neo's built-in GPS to show your current location. It automatically downloads maps from http://openstreetmap.com and you can download map tiles for offline use too.|
Screenshot=TangoGPS1.jpg|
Homepage=http://www.tangogps.org|
TestedOn=Om 2008.8|
PackageName=tangogps
}}
</onlyinclude>

[[Category:GPS Applications]]

SwapSpace

2009-02-14T12:59:13Z

Gromgull:

The Freerunner has only 128mb ram, when this is used up applications get killed.

To help this you can add a bit of swap space on the microsd card:

dd if=/dev/zero of=/media/card/swapfile.img bs=1024k count=512
mkswap /media/card/swapfile.img
swapon /media/card/swapfile.img

Taken from http://lists.openmoko.org/nabble.html#nabble-td2171203

SwapSpace

2009-02-14T12:49:30Z

Gromgull: New page: The Freerunner has only 128mb ram, when this is used up applications get killed. To help this you can add a bit of swap space on the microsd card: dd if=/dev/zero of=/media/card/swapfi...

The Freerunner has only 128mb ram, when this is used up applications get killed.

To help this you can add a bit of swap space on the microsd card:

dd if=/dev/zero of=/media/card/swapfile.img bs=1024k count=512
mkswap /media/nickcard/swapfile.img
swapon /media/nickcard/swapfile.img

Taken from http://lists.openmoko.org/nabble.html#nabble-td2171203

Talk:Community Updates

2008-11-30T08:33:24Z

Gromgull: /* Hardware */

Add news to this page, and from time to time we will issue a community update.

Watch these links:
* Git logs: [http://git.openmoko.org/?p=kernel.git;a=log;h=stable kernel/stable], [http://git.openmoko.org/?p=kernel.git;a=log;h=stable-tracking kernel/stable-tracking], [http://git.openmoko.org/?p=qtopia.git;a=log;h=master Qtopia/master], [http://git.openmoko.org/?p=openmoko.git;a=summary Openmoko's OpenEmbedded], [http://git.openmoko.org/?p=u-boot.git;a=log;h=stable uboot/stable], [http://git.openmoko.org/?p=qi.git;a=log Qi/master]
* Mailing lists: [http://lists.openmoko.org/nabble.html#nabble-f528196 hardware], [http://lists.openmoko.org/nabble.html#nabble-f528196 devel], [http://lists.openmoko.org/nabble.html#nabble-f1954 community], [http://lists.openmoko.org/nabble.html#nabble-f681789 kernel], [http://lists.openmoko.org/nabble.html#nabble-f528183 support], [http://lists.openmoko.org/nabble.html#nabble-f832940 SHR devel], [http://lists.projects.openmoko.org/pipermail/fdom-development/ FDOM devel]
* [http://projects.openmoko.org/ Project news].

How are newsletters organized elsewhere:
http://lists.openmoko.org/pipermail/community/2008-October/032628.html

[[/Archive 1]]

== Applications ==

* A [http://scalde.free.fr/index.php?option=com_content&view=article&id=93:pong-pogresses&catid=43:openmoko&Itemid=66 Pong]
* [http://blog.1407.org/2008/11/19/openmoko-newrotate-050-lazy-edition-is-out/ Newrotate 0.5] is out, uses really little CPU now.
* Valério won the first 24h-coding prize at Sapo Codebits by turning [http://www.valeriovalerio.org/?p=187 freerunner in a mouse and gamepad] using the accelerometers. Code will be merged with [[ReMoko]].
* [[Gtkaddpoi]] 0.5 : software to add a Point Of Interest to TangoGPS.
* neoqplayer 0.1 : codenamed frog. A media player that conserves CPU cycles.
* First release of [[TwitterMoko]], a twitter client for openmoko.
* ShortOm 0.2 : an application/shell launcher.
* openmoko-panel-plugin 0.6 : support for fso frameworkd milestone 4.
* [[Unison]] works.
* [http://www.srcf.ucam.org/~taw27/openmoko/openmoocow/ OpenMooCow] 0.2. Mooes more, runs headless, tickleable.
* [http://www.cs.helsinki.fi/u/rantalai/freerunner/aaterm/ AaTerm], an improved openmoko-terminal2.
* Azmodie proposed a solution for right and middle clicking: Use the gnome accessibility tool [http://live.gnome.org/Mousetweaks/Home mousetweaks] ([http://packages.debian.org/lenny/mousetweaks .deb]).

== Distributions ==

* The [http://downloads.openmoko.org/releases/ official 2008.9 image] is back online without the questionable audio codecs.
* ASU. 2008.11 is not going to see the light, but at least the bug count is decreasing in the testing build (see testing [http://lists.openmoko.org/pipermail/devel/2008-November/003312.html penultimate] and [http://lists.openmoko.org/pipermail/devel/2008-November/003493.html latest] reports, where A7 with capacitor is declared good for mess roduction ;). The testing build is the one with all the fixes from optimization team (read their [http://lists.openmoko.org/pipermail/community/2008-November/036276.html last], [http://lists.openmoko.org/pipermail/community/2008-November/035769.html previous] reports), i.e. about 1 minute boot and [http://git.openmoko.org/?p=qtopia.git;a=commit;h=eb855af76018bedf6a89b9ac736d2ffa3961932b Volume control] during call.
* SHR. [http://lists.openmoko.org/nabble.html#nabble-td1576966 newer snapshot] available.
* For [[Android]]: Walter Chang [http://lists.openmoko.org/pipermail/community/2008-November/036054.html made a soft keyboard]. Rui Castro implemented an [http://lists.openmoko.org/pipermail/community/2008-November/036564.html OnScreen Keyboard]. It was immediately included in Sean's image, to be released at [[User:Seanmcneil3|the usual page]] without mp3 support soon.

== Hardware ==

* For an armband to hold the Freerunner while exercising, Gilles Casse recommends the [http://www.caselogic.com/universal_mp3_sport_case_large/product_detail/index.cfm?modelid=120544 UMC-3] from Case Logic.
* Patrick Beck grafted a light on a miniusb - connector, to make an [http://yourse.de/wiki/doku.php?id=openmoko:usb_light OpenMoko flash light]. More lumens the bright white screen one get with the [http://projects.openmoko.org/projects/flashlight/ Flashlight] script.
* The [http://lists.openmoko.org/pipermail/community/2008-November/036132.html official fix] for buzzing is to add a 100uF capacity here and replace one resistor there. Technical details to be published in an Openmoko rework SOP paper. The company is looking at how to fix *all* devices sold.
* The Calypso GSM firmware moko10 was released, it fixes {{ticket|666}} for those users with 3G SIM cards. A few Indiana Jones types did try and follow [http://wiki.openmoko.org/wiki/GSM/Flashing the wiki instructions] to reflash, most with success, some with hubris (def: excessive pride). For the rest of us, a user-friendly installer is being prepared.

== Kernel and bootloaders ==

Big bad bug of the month prize goes to {{ticket|1841}} white screen of death (WSOD) after resume. This bug shows itself only by cold weather! Nicolas Dufresne found out that the culprit was probably a too tight timing in the JBT driver. Hopefully this will be fixed soon now, and we can all switch to Linux 2.6.28 happily everafter. Developpers must read [http://lists.openmoko.org/pipermail/community/2008-November/036142.html Andy's explanations] about kernel branch management.

* Preview upcoming [http://lists.openmoko.org/nabble.html#nabble-td1569863 changes to the /sys] directory.
* Improvements to the touchscreen, backlight and accelleremometers kernel drivers.
* [[Qi]] gets lots of GTA03 love, audio back and a memory test ability (called when there are no valid kernels).
* The opkg package manager was patched to cache downloaded files.

==Community==
* Removed the tagcloud extension that messed up with page formatting.
* There are many links to nice [[Ringtones]] on the wiki, but the page and the whole topic need a good overhaul.
* GnuPhone here we come: Sten Kvamme explains how to [http://lists.openmoko.org/pipermail/devel/2008-November/003318.html make a call from the command line] (on FSO).
* For your pleasure, here is the OpenMoko [[Jokes]] page. Thanks to the community, keep them coming ;) We (Coolcat and I) are also thinking about adding a pic of the week to the homepage, so stay tuned.
* Courtesy of Dale Maggee, [http://lists.openmoko.org/pipermail/community/2008-November/036053.html here] and [http://lists.openmoko.org/pipermail/community/2008-November/036142.html here] are a few funny splash screens. Note that you already trust Dale if you are using ''neotool'' to flash your Neo.

User:Gromgull

2008-11-27T09:19:18Z

Gromgull: /* Invitation */

I made a crappy "game" in python using the accelerometer:

http://www.semikolon.co.uk/blog/index.php?entry=entry081123-230715

It's not much fun to play for more than 10s, but the code is commented and shows many things.

Tickets I am interested in:
* https://docs.openmoko.org/trac/ticket/1743
* https://docs.openmoko.org/trac/ticket/677
* https://docs.openmoko.org/trac/ticket/1802
* https://docs.openmoko.org/trac/ticket/2082

==Invitation==
Hi:
I would like to invite you to write an introduction page for your game.
Would you like to share with us?

[[User:Coolcat|coolcat]]

Gromgull: It's not so much a game as a programming example. I have continued working on a few little things, I will write them up eventually and let you know!

User:Gromgull

2008-11-24T09:27:53Z

Gromgull:

Wiki Issues

2008-11-10T17:55:34Z

Gromgull: /* = Disappearing Pre-formatting */

If you think something is wrong with a Wiki page, please fix it. If the problem is larger with this Wiki in general, please add your thoughts on this page and mail the openmoko [https://lists.openmoko.org/mailman/listinfo/documentation| documentation mailing list]. You may just want to read existing proposals and put your vote on them, [[Wiki Maintainers]] will appreciate. [[Wiki Maintenance Agenda]].

When adding an issue please

* Provide a reason
* Provide your name as vote for the action to be taken (you can automatically enter your username by typing "

<nowiki>~~~</nowiki> ")

{{Warning|Comments without name might be deleted without consideration. We may need to ask for more information before implementing a proposal. Thanks for understanding.}}

Accepted and implemented requests should be deleted. Rejected requests should be moved to the bottom of the page to avoid requesting them again.

==Wiki Pages==

I think that we should use specific "editor's notes templates" rather that nominate individual pages here. We can make automatic list of pages using a given template by having a Category:X tag inside the template. See for example the [[:Category:ToDo]] . [[User:MinhHaDuong|MinhHaDuong]] 09:44, 7 October 2008 (UTC)

===Pages capable of development===
* [[Openmoko:Community Portal]]
* [[AR6K]] (Needs more info)
* [[GTA02 partitions]]: seems to be about the GTA01; could someone with a GTA02 please correct the partition sizes and names?
* [[Advanced_End-user]], [[Basic_End-user]], [[System_Developer]]: These are not up to the standard we set for List Pages on [[Openmoko_Wiki_Editing_Guidelines#List_pages]] [[User:Kempelen|Kempelen]]

===Redundant Pages===
* There are several pages concerning Openmoko compatible service providers:
** [[Carriers]], most up-to-date, confirmed service providers.
*** [[Carriers/ATT]]
*** [[Carriers/TMobile]]
*** [[Carriers/Fido]]
*** [[Carriers/Rogers]]
** [[Neo1973 compatible cellphone providers]]

*I suggest merging the editing help pages:
**[[Help:Editing]]
**[[Edit Wiki]]

*pages about GPS:
**[[Hardware:AGPS]]
**[[Gpsd]]
**[[Neo 1973 GPS]]
**[[Neo FreeRunner GPS]]

*applications:
**[[Available Packages]]
**[[Applications]]
**[[Applications directory]]
**[[Om 2007.2 Applications]]

===Tidy up===
* [[Wishlist:Text Input]] - tidy up/sort, give short feedback to each method
* [[Booting_from_SD]] - tidy up and a rewrite

=== Pages proposed for deletion ===

'''Please help cleaning these''': Check if there is a red (nonexisting) link in this table, click it, click "What links here" in the toolbox and '''update the broken links'''. When done, remove the deleted entry from this table.

{| border=1 cellspacing=0
!Page
!Reason
!Yes kill it votes
!No keep it votes
|-
| Nothing is propsed for deletion at the moment || || ||
|}

See also: [[:Category:Candidates for speedy deletion]]

=== Pages that especially need work ===

* [[Special:Lonelypages]] - Orphaned pages
* [[Special:DoubleRedirects]] - Pages that redirect to a redirected page
* [[Special:Popularpages]] - Pages that get viewed a lot
* [[Special:Ancientpages]] - Old pages
* [[Special:Newpages]] - New pages
* [[Special:Wantedpages]] - Wanted pages
* [[Special:Uncategorizedpages]]
* [[Special:Shortpages]] - Informationally light pages
* [[Special:BrokenRedirects]] - Broken redirects

=== Application pages ===

Maturity level ideas from the documentation list copied by [[User:Kempelen|Kempelen]] 19:05, 1 October 2008 (UTC):

* It might be nice to have a single word stating the code maturity, perhaps only 3 simple options like prototype, functional, mature
* Why not stick with pre-alpha, alpha, beta, stable, mature

Decision postponed. :-) (Feel free to vote here anyway.)

== Categories ==

{{Main|:Category talk:Categories}}

== CSS ==

We have discussed design on the mailing list, with the conclusion that revising was not a big priority. However, the wiki should be skinnable from user-space by editing : http://wiki.openmoko.org/wiki/MediaWiki:Common.css . And for development, each user can have his/her own CSS to eat his own dogfood. But I can't seem to make this feature work here.
Reference: http://en.wikipedia.org/wiki/Help:Monobook
[[User:MinhHaDuong|MinhHaDuong]] 12:26, 12 September 2008 (UTC).

* The gutter is too wide
* Too much footer's padding
* Could shave 1 or 2 em of vertical space in the header
* The tabbed navigation layout is non-standard (no framing effect)
* The search box is below the fold (depends on window height of course)
* The toolbox (bottom left) has no border
* Mediawiki's user personal toolbox is prohibited
* Too many links in the navbar that belongs to the home page but not to every page

== Portals ==

We should explore another wiki organization tool: [http://en.wikipedia.org/wiki/Portal:Contents/Portals portals]. A portal is an introductory page for a given topic. It complements the main article of the subject by introducing the reader to key articles, images, and categories that further describe the subject. Portals also help editors find related projects and things they can do to help. [[User:MinhHaDuong|MinhHaDuong]] 13:53, 20 September 2008 (UTC)

== Navigation templates ==

(FYI Description moved to [[Openmoko_Wiki_Editing_Guidelines#Navigation_templates]], [[User:Kempelen|Kempelen]])

* The [[Distributions]] page feature a non-templated navigation box
* We should name these templates distinctly. I suggest using a prefix like "NavBox:".
* Visual design is by hand (not CSS), and not beautiful
* Need to test positioning at bottom of article.

'''References'''

http://en.wikipedia.org/wiki/Wikipedia:Navigation_templates
http://en.wikipedia.org/wiki/Wikipedia:Categories,_lists,_and_series_boxes

[http://lists.openmoko.org/pipermail/documentation/2008-August/000405.html First discussion in the mailing list] (Note: in the middle of a thread about left navboxes)

* '''Yes votes''': [[User:Kempelen|Kempelen]] (For real wikipedia like navigation templates at the bottom, not at TOC position, we should move this section to editing guidelines as soon as template implementation improves a bit. Do not delete this please!)

== DolfjeBot1 proposals ==
Their is a bot on the openmoko wiki that's controlled by [[User:Dolfje]]. If you have tasks for the bot, please put them [[User:DolfjeBot1|here]].
A request has been made to tag DolfjeBot1 user account with the 'bot' flag. [[Special:Listusers/bureaucrat| Here is the lists of users]] with permissions at the necessary `bureaucrat' level.

==Wiki engine issues==

=== Disappearing Pre-formatting ===
There is an issue with pre-formatting disappearing when people edit. See for instance recent edits here:

http://wiki.openmoko.org/index.php?title=Accelerometer_data_retrieval&diff=59334&oldid=55556

Actually I thing it's whitespace in general that is lost since python/ruby code is also messed up.
I have confirmed that this happens cross browser (both firefox3 and opera), but not on all pages, and not for all people.

[[User:Gromgull|Gromgull]] 10:47, 9 November 2008 (UTC)

----

Can we please install/fix the following features for this wiki:
* '''Math''' - the Tex math markup does not work currently. Test:
** <math> z =\left (1-\left(\frac{P_{ind}}{101.325}\right)^{0.190263} \right ) \times \frac{87.828}{0.00198122} </math>
** <math> P_{ind} </math>
* [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi '''Syntax''' Highlighting - makes code much more readable]
* [http://www.mediawiki.org/wiki/Extension:GraphViz GraphViz] works with the commonly known dot language - it allows us to draw '''graphs''' using easy markup.
* [http://www.mediawiki.org/wiki/Extension:AnyWikiDraw AnyWikiDraw] allows us to draw svg '''diagrams''' directly on the wiki page.
* Make '''visited links''' a different color.

== Change Sitename ==

The name of this wiki is currently "Openmoko". I think it should be "Openmoko Wiki" for the following reasons:

* The other parts of this site (Planet, Projects, Docs) have similar names
* Media Wiki automatically creates a [http://www.mediawiki.org/wiki/Manual:Namespace namespace] for the Sitename (currently "Openmoko"). This means that content of pages beginning with "Openmoko:" cannot be found through the normal search function of this wiki. (At the moment there are five pages of this kind: [[Openmoko:About]], [[Openmoko:Community Portal]], [[Openmoko:Current events]], [[Openmoko:Searching]], [[Openmoko:Privacy policy]])--[[User:Marko Knöbl|Marko Knöbl]] 18:33, 8 August 2008 (UTC)

'''Yes votes''': [[User:Marko Knöbl|Marko Knöbl]], [[User:MinhHaDuong|Minh]]

'''No votes''':

::OpenmokoIT still do some research now. [[User:Coolcat|coolcat]]

== Organize translations ==

I suggest moving the translations to sub-wikis, like the way wikipedia does it. Currently all translations show up in searches and under category-lists. --[[User:Johndoesacc|Johndoesacc]] 12:03, 25 August 2008 (UTC)

+1. See issues and solutions for a multilingual mediawiki at:
http://www.mediawiki.org/wiki/Multilingual_MediaWiki
Also, the correspondence between translation should be maintained with tags:
http://en.wikipedia.org/wiki/Help:Interlanguage_links
The request [http://lists.openmoko.org/pipermail/documentation/2008-September/000557.html has been heard] but maybe not in the right places. What is the best operational frequency to ping the hosting engineers for that ? [[User:MinhHaDuong|MinhHaDuong]] 13:02, 10 September 2008 (UTC)

After discussion on the Documentation ML, sub-wikis are out. We want to try namespaces. [[User:MinhHaDuong|MinhHaDuong]] 09:31, 7 October 2008 (UTC)

== Downloads ==

=== Symlinks in download directories ===

This is not strictly Wiki issue, but discussed on the documentation list as being a serious usability disadvantage. Symlinks and .tar.gz files should be removed from the release directories because they confuse users. Ref: [http://lists.openmoko.org/pipermail/documentation/2008-September/000808.html]

=== Improve README.html ===

Example: http://downloads.openmoko.org/releases/Om2008.9/README.html

It should at least link to: [[Om_2008.9_Update#Download_and_Flashing]]

== Rejected requests ==

When a requested Wiki Issue is voted for not to be done, it must be moved here, to make sure it won't get continously requested again.

* '''Don't translate the wiki - rejected''' proposed by [[User:Minime|Minime]] August 2007, moved to rejected by [[User:Kempelen|Kempelen]] August 2008: the Documentation Team looks to support the idea.
* '''Use namespaces to separate user-oriented and developper-oriented content'''. Assuming the default namespace is user-oriented that would exclude developper-oriented pages from searches (unless the user ticks the box, but who does ?). And it can't be done purely in the wiki, it needs admin time. Better to use categories and a prefix in the page name (like BlendeWiki). [[:User:MinhHaDuong|MinhHaDuong]]
* '''Use category pages instead List Pages''' Good list pages are allowed and encouraged, as the documentation team today agreed on the mailing list. [[User:Kempelen|Kempelen]] 21:27, 30 August 2008 (UTC)

[[Category:Wiki Editing]]

User talk:AlainBb

2008-11-09T13:15:51Z

Gromgull: New page: Hi, I've made the edit to the accelerometer page. Space disappears for me too, but I copy paste the original ruby and python code and I was able to make the edit. Something is very broken ...

Hi, I've made the edit to the accelerometer page. Space disappears for me too, but I copy paste the original ruby and python code and I was able to make the edit. Something is very broken though, I've added a note to [[Wiki Issues]] and emailed the documentation mailinglist, hopefully someone will sort this out.

[[User:Gromgull|Gromgull]] 13:15, 9 November 2008 (UTC)

Accelerometer data retrieval

2008-11-09T13:14:12Z

Gromgull: /* Test application */

==Scope==

This document describes a way to access the data provided by the
accelerometers. Furthermore the format of the acquired datastream is explained
in detail. This document does not cover the physical basics of acceleration or
the mathematical details on this subject.

==Axis orientation==

To understand the values provided by the accelerometers it is crucial to
understand how the sensors are oriented. In the following I will refer to the
sensors as first and second sensor. The way to access the data sources of
these two will be described later on in this document.

The Z axis is pointing from the display downwards to to the back of the
openmoko. This applies to both of the sensors.

===Orientation of the first sensor===

To explain the axis orientation I have created some images for easier
understanding.

[[Image:Accelerometer_orientation1.png|Axis orientation of the first accelerometer]]

===Orientation of the second sensor===

In contrast to the first sensor the second one is turned 45 degrees around the
Z axis. See the attached image to get a clue about its orientation.

[[Image:Accelerometer_orientation2.png|Axis orientation of the second accelerometer]]

==Data acquisition==

The information from both of the accelerometers is exported through two
different input event based file mappings. These device nodes can be found at
''/dev/input/event2'' and ''/dev/input/event3''.

The sensor I am refering to as the first one is ''event2''. Therefore the second
one is accessible through the ''event3'' device.

These device nodes can be opened by the default filesystems calls for reading
files. The data can be read from the stream as soon as the sensor measures it.

==Data structure==

To be able to use the measured data it is important to understand the format
in which the data is provided.
The structure of the given data is based on the kernel input event message
system which exports the following data structure:

<pre>
struct input_event {
struct timeval time;
__u16 type;
__u16 code;
__s32 value;
};
</pre>

The data is written to the stream message by message. Therefore the minimal
used blocksize is 128 bit (16 byte).

Lets have a look at an example readout of the accelerometer data, divided into
the used sections.

<pre>
|----- time ------| |type| |code| |-value-|
8c66 4819 721c 0006 0002 0002 03a8 0000
8c66 4819 7222 0006 0000 0000 0000 0000
8c66 4819 99e6 0006 0002 0000 0048 0000
8c66 4819 9a36 0006 0002 0001 0024 0000
8c66 4819 9a50 0006 0002 0002 0396 0000
8c66 4819 9a57 0006 0000 0000 0000 0000
</pre>

I think the time structure does not need further explaination. A lot more
interesting is the type, code and value part of every message. Lets take a
closer look at these parts.

===Event types===

The types categorize the incoming messages. All possible types can be found in
the kernel sources or include files in ''INCLUDEDIR/linux/input.h''
During the tests with the accelerometers I observed the fact that only two
different message types are used.

;0x00:
:According to ''linux/input.h'' this event is called ''EV_SYN''. It signals the wish to ''syncronize''. Normally this event is used in combination with code 0x00 to mark the send data complete and therefore applyable.

;0x02:
:This event is called ''EV_REL'' and signals ''relative movement''. It is used to transmit the acceleration the sensors encounter.

The definition should not be taken too seriously in this context, because the
data values provided by the accelerometer always represent the absolute
acceleration measured at the given time.

===Event codes===

Both types of event may supply different codes. These codes can be understood
as some kind of further specification about the specified data values

====Syncronization event codes====

The syncronization event may use quite a lot of codes, as ''linux/input.h''
shows. However the only used one seems to be the 0x00 code.

;0x00:
:This code is refered to as SYN_REPORT. It means that the last dataset was completely transmitted. Therefore the before transmitted set of data values can be considered complete. This means if this message is recieved you may process the given data further.

====Relative movement event codes====

The amount of possible codes for this event type is quite big. The only used
ones are the following ones.

;0x00:
:REL_X - Acceleration in x direction

;0x01:
:REL_Y - Acceleration in y direction

;0x02:
:REL_Z - Acceleration in z direction

The X, Y and Z axis are to be understand as defined in the chapter about [[#Axis_orientation|Axis orientation]].

===A typical message block===

A typical message block consists of 3 messages containing the acceleration
data for every of the three axis followed by a syncronization message to
signal the end of the block.

The following example is such a message block with detailed explanation of its
different messages and data sections.

<pre>
8c66 4819 99e6 0006 0002 0000 0048 0000
|------Time-------| EV_REL REL_X |-Value-|
(Measured acceleration in x axis direction of 72)

8c66 4819 9a36 0006 0002 0001 0024 0000
|------Time-------| EV_REL REL_Y |-Value-|
(Measured acceleration in y axis direction of 36)

8c66 4819 9a50 0006 0002 0002 0396 0000
|------Time-------| EV_REL REL_Z |-Value-|
(Measured acceleration in z axis direction of 918)

8c66 4819 9a57 0006 0000 0000 0000 0000
|------Time-------| EV_SYN SYN_REPORT |-Value-|
(The transmitted data block is complete you may process the given data)
</pre>

==Test application==

A simple test application written in ruby:
<pre>
#!/usr/bin/env ruby
x = 0
y = 0
z = 0
File.open("/dev/input/event3") do |f|
while true
event = f.read(16).unpack("llSSl")
time = event[0] + event[1] / 1000000.0
type = event[2]
code = event[3]
value = event[4]
if type == 2
x = value if code == 0
y = value if code == 1
z = value if code == 2
end
if type == 0 && code == 0
sum = Math::sqrt(x*x + y*y + z*z).to_i
printf("%5d %5d %5d %5d\n", x, y, z, sum)
end
end
end

</pre>

Equivalent version in python:

<pre>
#!/usr/bin/python
import struct
from math import sqrt

x = 0
y = 0
z = 0
secondsensorfile = "/dev/input/event3"
#int, int, short, short, int
fmt = 'iihhi'
#open file in binary mode
in_file = open(secondsensorfile,"rb")
event = in_file.read(16)
while event:
(time1,time2, type, code, value) = \
struct.unpack(fmt,event)
time = time1 + time2 / 1000000.0

if type == 2:
if code == 0:
x = value
if code == 1:
y = value
if code == 2:
z = value
if type == 0 and code == 0:
sum = int(sqrt(x*x + y*y + z*z))
print x, y, z, sum
event = in_file.read(16)
in_file.close()

</pre>

Equivalent in Perl

<pre>
#!/usr/bin/perl

$x = 0;
$y = 0;
$z = 0;

$secondsensorfile = "/dev/input/event3";
#open file in binary mode
open FILE, $secondsensorfile;
binmode FILE;

while (read FILE, $buf,16) {
($t1,$t2,$type,$code,$value)=unpack "iissi",$buf;
if ($type==2) {
if ($code==0) {$x=$value};
if ($code==1) {$y=$value};
if ($code==2) {$z=$value};
}
if (($type==0) && (code==0)) {
printf "%f %05d %05d %05d\n",$t1+$t2/1000000,$x,$y,$z;
}
}

</pre>

== The /sys interface ==

To get the sampling rate of the first accelerometer ''spi0.0'' :

# cat /sys/bus/spi/drivers/lis302dl/spi0.0/sample_rate
100

To set the sampling rate :

# echo 400 > /sys/bus/spi/drivers/lis302dl/spi0.0/sample_rate
# cat /sys/bus/spi/drivers/lis302dl/spi0.0/sample_rate
400

The other one is ''spi0.1''. See [[GTA02 sysfs#Accelerometers]] for the other options.

==See also==
* [[Accelerometer_Fundamentals]]
* [[Gestures]], [http://code.google.com/p/accelges/source/browse/trunk/accelneo/src/accelneo.c code sample]

==External Links==
* [http://projects.openmoko.org/projects/gestures/ Openmoko Motion Gestures]
* [http://en.wikipedia.org/wiki/Accelerometer Wikipedia - Accelerometer]
* [http://dev.borza.ro/demo/Motion-based%20Gesture%20Recognition%20with%20an%20Accelerometer/Paper.pdf Motion-based Gesture Recognition with an Accelerometer - Paper]
* [http://www.youtube.com/watch?v=s5QMW8k5nis YouTube video: Playing with Accelerometers]
* [http://westhoffswelt.de/blog/my_first_openmoko_application.html Magic Eightball Application using the Accelerometers]

[[Category:Accelerometer]]
[[Category:Application Developer]]

Wiki Issues

2008-11-09T10:47:26Z

Gromgull: /* Wiki engine issues */

If you think something is wrong with a Wiki page, please fix it. If the problem is larger with this Wiki in general, please add your thoughts on this page and mail the openmoko [https://lists.openmoko.org/mailman/listinfo/documentation| documentation mailing list]. You may just want to read existing proposals and put your vote on them, [[Wiki Maintainers]] will appreciate. [[Wiki Maintenance Agenda]].

When adding an issue please

* Provide a reason
* Provide your name as vote for the action to be taken (you can automatically enter your username by typing "

<nowiki>~~~</nowiki> ")

{{Warning|Comments without name might be deleted without consideration. We may need to ask for more information before implementing a proposal. Thanks for understanding.}}

Accepted and implemented requests should be deleted. Rejected requests should be moved to the bottom of the page to avoid requesting them again.

==Wiki Pages==

I think that we should use specific "editor's notes templates" rather that nominate individual pages here. We can make automatic list of pages using a given template by having a Category:X tag inside the template. See for example the [[:Category:ToDo]] . [[User:MinhHaDuong|MinhHaDuong]] 09:44, 7 October 2008 (UTC)

===Pages capable of development===
* [[Openmoko:Community Portal]]
* [[AR6K]] (Needs more info)
* [[GTA02 partitions]]: seems to be about the GTA01; could someone with a GTA02 please correct the partition sizes and names?
* [[Advanced_End-user]], [[Basic_End-user]], [[System_Developer]]: These are not up to the standard we set for List Pages on [[Openmoko_Wiki_Editing_Guidelines#List_pages]] [[User:Kempelen|Kempelen]]

===Redundant Pages===
* There are several pages concerning Openmoko compatible service providers:
** [[Carriers]], most up-to-date, confirmed service providers.
*** [[Carriers/ATT]]
*** [[Carriers/TMobile]]
*** [[Carriers/Fido]]
*** [[Carriers/Rogers]]
** [[Neo1973 compatible cellphone providers]]

*I suggest merging the editing help pages:
**[[Help:Editing]]
**[[Edit Wiki]]

*pages about GPS:
**[[Hardware:AGPS]]
**[[Gpsd]]
**[[Neo 1973 GPS]]
**[[Neo FreeRunner GPS]]

*applications:
**[[Available Packages]]
**[[Applications]]
**[[Applications directory]]
**[[Om 2007.2 Applications]]

===Tidy up===
* [[Wishlist:Text Input]] - tidy up/sort, give short feedback to each method
* [[Booting_from_SD]] - tidy up and a rewrite

=== Pages proposed for deletion ===

'''Please help cleaning these''': Check if there is a red (nonexisting) link in this table, click it, click "What links here" in the toolbox and '''update the broken links'''. When done, remove the deleted entry from this table.

{| border=1 cellspacing=0
!Page
!Reason
!Yes kill it votes
!No keep it votes
|-
| Nothing is propsed for deletion at the moment || || ||
|}

See also: [[:Category:Candidates for speedy deletion]]

=== Pages that especially need work ===

* [[Special:Lonelypages]] - Orphaned pages
* [[Special:DoubleRedirects]] - Pages that redirect to a redirected page
* [[Special:Popularpages]] - Pages that get viewed a lot
* [[Special:Ancientpages]] - Old pages
* [[Special:Newpages]] - New pages
* [[Special:Wantedpages]] - Wanted pages
* [[Special:Uncategorizedpages]]
* [[Special:Shortpages]] - Informationally light pages
* [[Special:BrokenRedirects]] - Broken redirects

=== Application pages ===

Maturity level ideas from the documentation list copied by [[User:Kempelen|Kempelen]] 19:05, 1 October 2008 (UTC):

* It might be nice to have a single word stating the code maturity, perhaps only 3 simple options like prototype, functional, mature
* Why not stick with pre-alpha, alpha, beta, stable, mature

Decision postponed. :-) (Feel free to vote here anyway.)

== Categories ==

{{Main|:Category talk:Categories}}

== CSS ==

We have discussed design on the mailing list, with the conclusion that revising was not a big priority. However, the wiki should be skinnable from user-space by editing : http://wiki.openmoko.org/wiki/MediaWiki:Common.css . And for development, each user can have his/her own CSS to eat his own dogfood. But I can't seem to make this feature work here.
Reference: http://en.wikipedia.org/wiki/Help:Monobook
[[User:MinhHaDuong|MinhHaDuong]] 12:26, 12 September 2008 (UTC).

* The gutter is too wide
* Too much footer's padding
* Could shave 1 or 2 em of vertical space in the header
* The tabbed navigation layout is non-standard (no framing effect)
* The search box is below the fold (depends on window height of course)
* The toolbox (bottom left) has no border
* Mediawiki's user personal toolbox is prohibited
* Too many links in the navbar that belongs to the home page but not to every page

== Portals ==

We should explore another wiki organization tool: [http://en.wikipedia.org/wiki/Portal:Contents/Portals portals]. A portal is an introductory page for a given topic. It complements the main article of the subject by introducing the reader to key articles, images, and categories that further describe the subject. Portals also help editors find related projects and things they can do to help. [[User:MinhHaDuong|MinhHaDuong]] 13:53, 20 September 2008 (UTC)

== Navigation templates ==

(FYI Description moved to [[Openmoko_Wiki_Editing_Guidelines#Navigation_templates]], [[User:Kempelen|Kempelen]])

* The [[Distributions]] page feature a non-templated navigation box
* We should name these templates distinctly. I suggest using a prefix like "NavBox:".
* Visual design is by hand (not CSS), and not beautiful
* Need to test positioning at bottom of article.

'''References'''

http://en.wikipedia.org/wiki/Wikipedia:Navigation_templates
http://en.wikipedia.org/wiki/Wikipedia:Categories,_lists,_and_series_boxes

[http://lists.openmoko.org/pipermail/documentation/2008-August/000405.html First discussion in the mailing list] (Note: in the middle of a thread about left navboxes)

* '''Yes votes''': [[User:Kempelen|Kempelen]] (For real wikipedia like navigation templates at the bottom, not at TOC position, we should move this section to editing guidelines as soon as template implementation improves a bit. Do not delete this please!)

== DolfjeBot1 proposals ==
Their is a bot on the openmoko wiki that's controlled by [[User:Dolfje]]. If you have tasks for the bot, please put them [[User:DolfjeBot1|here]].
A request has been made to tag DolfjeBot1 user account with the 'bot' flag. [[Special:Listusers/bureaucrat| Here is the lists of users]] with permissions at the necessary `bureaucrat' level.

==Wiki engine issues==

=== Disappearing Pre-formatting ==
There is an issue with pre-formatting disappearing when people edit. See for instance recent edits here:

http://wiki.openmoko.org/index.php?title=Accelerometer_data_retrieval&diff=59334&oldid=55556

Actually I thing it's whitespace in general that is lost since python/ruby code is also messed up.
I have confirmed that this happens cross browser (both firefox3 and opera), but not on all pages, and not for all people.

[[User:Gromgull|Gromgull]] 10:47, 9 November 2008 (UTC)

----

Can we please install/fix the following features for this wiki:
* '''Math''' - the Tex math markup does not work currently. Test:
** <math> z =\left (1-\left(\frac{P_{ind}}{101.325}\right)^{0.190263} \right ) \times \frac{87.828}{0.00198122} </math>
** <math> P_{ind} </math>
* [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi '''Syntax''' Highlighting - makes code much more readable]
* [http://www.mediawiki.org/wiki/Extension:GraphViz GraphViz] works with the commonly known dot language - it allows us to draw '''graphs''' using easy markup.
* [http://www.mediawiki.org/wiki/Extension:AnyWikiDraw AnyWikiDraw] allows us to draw svg '''diagrams''' directly on the wiki page.
* Make '''visited links''' a different color.

== Change Sitename ==

The name of this wiki is currently "Openmoko". I think it should be "Openmoko Wiki" for the following reasons:

* The other parts of this site (Planet, Projects, Docs) have similar names
* Media Wiki automatically creates a [http://www.mediawiki.org/wiki/Manual:Namespace namespace] for the Sitename (currently "Openmoko"). This means that content of pages beginning with "Openmoko:" cannot be found through the normal search function of this wiki. (At the moment there are five pages of this kind: [[Openmoko:About]], [[Openmoko:Community Portal]], [[Openmoko:Current events]], [[Openmoko:Searching]], [[Openmoko:Privacy policy]])--[[User:Marko Knöbl|Marko Knöbl]] 18:33, 8 August 2008 (UTC)

'''Yes votes''': [[User:Marko Knöbl|Marko Knöbl]], [[User:MinhHaDuong|Minh]]

'''No votes''':

::OpenmokoIT still do some research now. [[User:Coolcat|coolcat]]

== Organize translations ==

I suggest moving the translations to sub-wikis, like the way wikipedia does it. Currently all translations show up in searches and under category-lists. --[[User:Johndoesacc|Johndoesacc]] 12:03, 25 August 2008 (UTC)

+1. See issues and solutions for a multilingual mediawiki at:
http://www.mediawiki.org/wiki/Multilingual_MediaWiki
Also, the correspondence between translation should be maintained with tags:
http://en.wikipedia.org/wiki/Help:Interlanguage_links
The request [http://lists.openmoko.org/pipermail/documentation/2008-September/000557.html has been heard] but maybe not in the right places. What is the best operational frequency to ping the hosting engineers for that ? [[User:MinhHaDuong|MinhHaDuong]] 13:02, 10 September 2008 (UTC)

After discussion on the Documentation ML, sub-wikis are out. We want to try namespaces. [[User:MinhHaDuong|MinhHaDuong]] 09:31, 7 October 2008 (UTC)

== Downloads ==

=== Symlinks in download directories ===

This is not strictly Wiki issue, but discussed on the documentation list as being a serious usability disadvantage. Symlinks and .tar.gz files should be removed from the release directories because they confuse users. Ref: [http://lists.openmoko.org/pipermail/documentation/2008-September/000808.html]

=== Improve README.html ===

Example: http://downloads.openmoko.org/releases/Om2008.9/README.html

It should at least link to: [[Om_2008.9_Update#Download_and_Flashing]]

== Rejected requests ==

When a requested Wiki Issue is voted for not to be done, it must be moved here, to make sure it won't get continously requested again.

* '''Don't translate the wiki - rejected''' proposed by [[User:Minime|Minime]] August 2007, moved to rejected by [[User:Kempelen|Kempelen]] August 2008: the Documentation Team looks to support the idea.
* '''Use namespaces to separate user-oriented and developper-oriented content'''. Assuming the default namespace is user-oriented that would exclude developper-oriented pages from searches (unless the user ticks the box, but who does ?). And it can't be done purely in the wiki, it needs admin time. Better to use categories and a prefix in the page name (like BlendeWiki). [[:User:MinhHaDuong|MinhHaDuong]]
* '''Use category pages instead List Pages''' Good list pages are allowed and encouraged, as the documentation team today agreed on the mailing list. [[User:Kempelen|Kempelen]] 21:27, 30 August 2008 (UTC)

[[Category:Wiki Editing]]

Accelerometer data retrieval

2008-11-09T10:35:42Z

Gromgull: /* Test application */

==Scope==

This document describes a way to access the data provided by the
accelerometers. Furthermore the format of the acquired datastream is explained
in detail. This document does not cover the physical basics of acceleration or
the mathematical details on this subject.

==Axis orientation==

To understand the values provided by the accelerometers it is crucial to
understand how the sensors are oriented. In the following I will refer to the
sensors as first and second sensor. The way to access the data sources of
these two will be described later on in this document.

The Z axis is pointing from the display downwards to to the back of the
openmoko. This applies to both of the sensors.

===Orientation of the first sensor===

To explain the axis orientation I have created some images for easier
understanding.

[[Image:Accelerometer_orientation1.png|Axis orientation of the first accelerometer]]

===Orientation of the second sensor===

In contrast to the first sensor the second one is turned 45 degrees around the
Z axis. See the attached image to get a clue about its orientation.

[[Image:Accelerometer_orientation2.png|Axis orientation of the second accelerometer]]

==Data acquisition==

The information from both of the accelerometers is exported through two
different input event based file mappings. These device nodes can be found at
''/dev/input/event2'' and ''/dev/input/event3''.

The sensor I am refering to as the first one is ''event2''. Therefore the second
one is accessible through the ''event3'' device.

These device nodes can be opened by the default filesystems calls for reading
files. The data can be read from the stream as soon as the sensor measures it.

==Data structure==

To be able to use the measured data it is important to understand the format
in which the data is provided.
The structure of the given data is based on the kernel input event message
system which exports the following data structure:

<pre>
struct input_event {
struct timeval time;
__u16 type;
__u16 code;
__s32 value;
};
</pre>

The data is written to the stream message by message. Therefore the minimal
used blocksize is 128 bit (16 byte).

Lets have a look at an example readout of the accelerometer data, divided into
the used sections.

<pre>
|----- time ------| |type| |code| |-value-|
8c66 4819 721c 0006 0002 0002 03a8 0000
8c66 4819 7222 0006 0000 0000 0000 0000
8c66 4819 99e6 0006 0002 0000 0048 0000
8c66 4819 9a36 0006 0002 0001 0024 0000
8c66 4819 9a50 0006 0002 0002 0396 0000
8c66 4819 9a57 0006 0000 0000 0000 0000
</pre>

I think the time structure does not need further explaination. A lot more
interesting is the type, code and value part of every message. Lets take a
closer look at these parts.

===Event types===

The types categorize the incoming messages. All possible types can be found in
the kernel sources or include files in ''INCLUDEDIR/linux/input.h''
During the tests with the accelerometers I observed the fact that only two
different message types are used.

;0x00:
:According to ''linux/input.h'' this event is called ''EV_SYN''. It signals the wish to ''syncronize''. Normally this event is used in combination with code 0x00 to mark the send data complete and therefore applyable.

;0x02:
:This event is called ''EV_REL'' and signals ''relative movement''. It is used to transmit the acceleration the sensors encounter.

The definition should not be taken too seriously in this context, because the
data values provided by the accelerometer always represent the absolute
acceleration measured at the given time.

===Event codes===

Both types of event may supply different codes. These codes can be understood
as some kind of further specification about the specified data values

====Syncronization event codes====

The syncronization event may use quite a lot of codes, as ''linux/input.h''
shows. However the only used one seems to be the 0x00 code.

;0x00:
:This code is refered to as SYN_REPORT. It means that the last dataset was completely transmitted. Therefore the before transmitted set of data values can be considered complete. This means if this message is recieved you may process the given data further.

====Relative movement event codes====

The amount of possible codes for this event type is quite big. The only used
ones are the following ones.

;0x00:
:REL_X - Acceleration in x direction

;0x01:
:REL_Y - Acceleration in y direction

;0x02:
:REL_Z - Acceleration in z direction

The X, Y and Z axis are to be understand as defined in the chapter about [[#Axis_orientation|Axis orientation]].

===A typical message block===

A typical message block consists of 3 messages containing the acceleration
data for every of the three axis followed by a syncronization message to
signal the end of the block.

The following example is such a message block with detailed explanation of its
different messages and data sections.

<pre>
8c66 4819 99e6 0006 0002 0000 0048 0000
|------Time-------| EV_REL REL_X |-Value-|
(Measured acceleration in x axis direction of 72)

8c66 4819 9a36 0006 0002 0001 0024 0000
|------Time-------| EV_REL REL_Y |-Value-|
(Measured acceleration in y axis direction of 36)

8c66 4819 9a50 0006 0002 0002 0396 0000
|------Time-------| EV_REL REL_Z |-Value-|
(Measured acceleration in z axis direction of 918)

8c66 4819 9a57 0006 0000 0000 0000 0000
|------Time-------| EV_SYN SYN_REPORT |-Value-|
(The transmitted data block is complete you may process the given data)
</pre>

==Test application==

A simple test application written in ruby:
<pre>
#!/usr/bin/env ruby
x = 0
y = 0
z = 0
File.open("/dev/input/event3") do |f|
while true
event = f.read(16).unpack("llSSl")
time = event[0] + event[1] / 1000000.0
type = event[2]
code = event[3]
value = event[4]
if type == 2
x = value if code == 0
y = value if code == 1
z = value if code == 2
end
if type == 0 && code == 0
sum = Math::sqrt(x*x + y*y + z*z).to_i
printf("%5d %5d %5d %5d\n", x, y, z, sum)
end
end
end

</pre>

Equivalent version in python:

<pre>
#!/usr/bin/python
import struct
from math import sqrt

x = 0
y = 0
z = 0
secondsensorfile = "/dev/input/event3"
#int, int, short, short, int
fmt = 'iihhi'
#open file in binary mode
in_file = open(secondsensorfile,"rb")
event = in_file.read(16)
while event:
(time1,time2, type, code, value) = \
struct.unpack(fmt,event)
time = time1 + time2 / 1000000.0

if type == 2:
if code == 0:
x = value
if code == 1:
y = value
if code == 2:
z = value
if type == 0 and code == 0:
sum = int(sqrt(x*x + y*y + z*z))
print x, y, z, sum
event = in_file.read(16)
in_file.close()

</pre>

== The /sys interface ==

To get the sampling rate of the first accelerometer ''spi0.0'' :

# cat /sys/bus/spi/drivers/lis302dl/spi0.0/sample_rate
100

To set the sampling rate :

# echo 400 > /sys/bus/spi/drivers/lis302dl/spi0.0/sample_rate
# cat /sys/bus/spi/drivers/lis302dl/spi0.0/sample_rate
400

The other one is ''spi0.1''. See [[GTA02 sysfs#Accelerometers]] for the other options.

==See also==
* [[Accelerometer_Fundamentals]]
* [[Gestures]], [http://code.google.com/p/accelges/source/browse/trunk/accelneo/src/accelneo.c code sample]

==External Links==
* [http://projects.openmoko.org/projects/gestures/ Openmoko Motion Gestures]
* [http://en.wikipedia.org/wiki/Accelerometer Wikipedia - Accelerometer]
* [http://dev.borza.ro/demo/Motion-based%20Gesture%20Recognition%20with%20an%20Accelerometer/Paper.pdf Motion-based Gesture Recognition with an Accelerometer - Paper]
* [http://www.youtube.com/watch?v=s5QMW8k5nis YouTube video: Playing with Accelerometers]
* [http://westhoffswelt.de/blog/my_first_openmoko_application.html Magic Eightball Application using the Accelerometers]

[[Category:Accelerometer]]
[[Category:Application Developer]]

Accelerometer data retrieval

2008-11-09T10:33:30Z

Gromgull: /* Data structure */

==Scope==

This document describes a way to access the data provided by the
accelerometers. Furthermore the format of the acquired datastream is explained
in detail. This document does not cover the physical basics of acceleration or
the mathematical details on this subject.

==Axis orientation==

To understand the values provided by the accelerometers it is crucial to
understand how the sensors are oriented. In the following I will refer to the
sensors as first and second sensor. The way to access the data sources of
these two will be described later on in this document.

The Z axis is pointing from the display downwards to to the back of the
openmoko. This applies to both of the sensors.

===Orientation of the first sensor===

To explain the axis orientation I have created some images for easier
understanding.

[[Image:Accelerometer_orientation1.png|Axis orientation of the first accelerometer]]

===Orientation of the second sensor===

In contrast to the first sensor the second one is turned 45 degrees around the
Z axis. See the attached image to get a clue about its orientation.

[[Image:Accelerometer_orientation2.png|Axis orientation of the second accelerometer]]

==Data acquisition==

The information from both of the accelerometers is exported through two
different input event based file mappings. These device nodes can be found at
''/dev/input/event2'' and ''/dev/input/event3''.

The sensor I am refering to as the first one is ''event2''. Therefore the second
one is accessible through the ''event3'' device.

These device nodes can be opened by the default filesystems calls for reading
files. The data can be read from the stream as soon as the sensor measures it.

==Data structure==

To be able to use the measured data it is important to understand the format
in which the data is provided.
The structure of the given data is based on the kernel input event message
system which exports the following data structure:

<pre>
struct input_event {
struct timeval time;
__u16 type;
__u16 code;
__s32 value;
};
</pre>

The data is written to the stream message by message. Therefore the minimal
used blocksize is 128 bit (16 byte).

Lets have a look at an example readout of the accelerometer data, divided into
the used sections.

<pre>
|----- time ------| |type| |code| |-value-|
8c66 4819 721c 0006 0002 0002 03a8 0000
8c66 4819 7222 0006 0000 0000 0000 0000
8c66 4819 99e6 0006 0002 0000 0048 0000
8c66 4819 9a36 0006 0002 0001 0024 0000
8c66 4819 9a50 0006 0002 0002 0396 0000
8c66 4819 9a57 0006 0000 0000 0000 0000
</pre>

I think the time structure does not need further explaination. A lot more
interesting is the type, code and value part of every message. Lets take a
closer look at these parts.

===Event types===

The types categorize the incoming messages. All possible types can be found in
the kernel sources or include files in ''INCLUDEDIR/linux/input.h''
During the tests with the accelerometers I observed the fact that only two
different message types are used.

;0x00:
:According to ''linux/input.h'' this event is called ''EV_SYN''. It signals the wish to ''syncronize''. Normally this event is used in combination with code 0x00 to mark the send data complete and therefore applyable.

;0x02:
:This event is called ''EV_REL'' and signals ''relative movement''. It is used to transmit the acceleration the sensors encounter.

The definition should not be taken too seriously in this context, because the
data values provided by the accelerometer always represent the absolute
acceleration measured at the given time.

===Event codes===

Both types of event may supply different codes. These codes can be understood
as some kind of further specification about the specified data values

====Syncronization event codes====

The syncronization event may use quite a lot of codes, as ''linux/input.h''
shows. However the only used one seems to be the 0x00 code.

;0x00:
:This code is refered to as SYN_REPORT. It means that the last dataset was completely transmitted. Therefore the before transmitted set of data values can be considered complete. This means if this message is recieved you may process the given data further.

====Relative movement event codes====

The amount of possible codes for this event type is quite big. The only used
ones are the following ones.

;0x00:
:REL_X - Acceleration in x direction

;0x01:
:REL_Y - Acceleration in y direction

;0x02:
:REL_Z - Acceleration in z direction

The X, Y and Z axis are to be understand as defined in the chapter about [[#Axis_orientation|Axis orientation]].

===A typical message block===

A typical message block consists of 3 messages containing the acceleration
data for every of the three axis followed by a syncronization message to
signal the end of the block.

The following example is such a message block with detailed explanation of its
different messages and data sections.

<pre>
8c66 4819 99e6 0006 0002 0000 0048 0000
|------Time-------| EV_REL REL_X |-Value-|
(Measured acceleration in x axis direction of 72)

8c66 4819 9a36 0006 0002 0001 0024 0000
|------Time-------| EV_REL REL_Y |-Value-|
(Measured acceleration in y axis direction of 36)

8c66 4819 9a50 0006 0002 0002 0396 0000
|------Time-------| EV_REL REL_Z |-Value-|
(Measured acceleration in z axis direction of 918)

8c66 4819 9a57 0006 0000 0000 0000 0000
|------Time-------| EV_SYN SYN_REPORT |-Value-|
(The transmitted data block is complete you may process the given data)
</pre>

==Test application==

A simple test application written in ruby:
<pre>
#!/usr/bin/env ruby
x = 0
y = 0
z = 0
File.open("/dev/input/event3") do |f|
while true
event = f.read(16).unpack("llSSl")
time = event[0] + event[1] / 1000000.0
type = event[2]
code = event[3]
value = event[4]
if type == 2
x = value if code == 0
y = value if code == 1
z = value if code == 2
end
if type == 0 && code == 0
sum = Math::sqrt(x*x + y*y + z*z).to_i
printf("%5d %5d %5d %5d\n", x, y, z, sum)
end
end
end
</pre>

Equivalent version in python:

{{TODO: The whitespace here has been lost! And the python is now broken :)}}
<pre>
#!/usr/bin/python
import struct
from math import sqrt

x = 0
y = 0
z = 0
secondsensorfile = "/dev/input/event3"
#int, int, short, short, int
fmt = 'iihhi'
#open file in binary mode
in_file = open(secondsensorfile,"rb")
event = in_file.read(16)
while event:
(time1,time2, type, code, value) = \
struct.unpack(fmt,event)
time = time1 + time2 / 1000000.0

if type == 2:
if code == 0:
x = value
if code == 1:
y = value
if code == 2:
z = value
if type == 0 and code == 0:
sum = int(sqrt(x*x + y*y + z*z))
print x, y, z, sum
event = in_file.read(16)
in_file.close()

</pre>

== The /sys interface ==

To get the sampling rate of the first accelerometer ''spi0.0'' :

# cat /sys/bus/spi/drivers/lis302dl/spi0.0/sample_rate
100

To set the sampling rate :

# echo 400 > /sys/bus/spi/drivers/lis302dl/spi0.0/sample_rate
# cat /sys/bus/spi/drivers/lis302dl/spi0.0/sample_rate
400

The other one is ''spi0.1''. See [[GTA02 sysfs#Accelerometers]] for the other options.

==See also==
* [[Accelerometer_Fundamentals]]
* [[Gestures]], [http://code.google.com/p/accelges/source/browse/trunk/accelneo/src/accelneo.c code sample]

==External Links==
* [http://projects.openmoko.org/projects/gestures/ Openmoko Motion Gestures]
* [http://en.wikipedia.org/wiki/Accelerometer Wikipedia - Accelerometer]
* [http://dev.borza.ro/demo/Motion-based%20Gesture%20Recognition%20with%20an%20Accelerometer/Paper.pdf Motion-based Gesture Recognition with an Accelerometer - Paper]
* [http://www.youtube.com/watch?v=s5QMW8k5nis YouTube video: Playing with Accelerometers]
* [http://westhoffswelt.de/blog/my_first_openmoko_application.html Magic Eightball Application using the Accelerometers]

[[Category:Accelerometer]]
[[Category:Application Developer]]

Accelerometer data retrieval

2008-11-09T10:33:03Z

Gromgull: /* A typical message block */

==Scope==

This document describes a way to access the data provided by the
accelerometers. Furthermore the format of the acquired datastream is explained
in detail. This document does not cover the physical basics of acceleration or
the mathematical details on this subject.

==Axis orientation==

To understand the values provided by the accelerometers it is crucial to
understand how the sensors are oriented. In the following I will refer to the
sensors as first and second sensor. The way to access the data sources of
these two will be described later on in this document.

The Z axis is pointing from the display downwards to to the back of the
openmoko. This applies to both of the sensors.

===Orientation of the first sensor===

To explain the axis orientation I have created some images for easier
understanding.

[[Image:Accelerometer_orientation1.png|Axis orientation of the first accelerometer]]

===Orientation of the second sensor===

In contrast to the first sensor the second one is turned 45 degrees around the
Z axis. See the attached image to get a clue about its orientation.

[[Image:Accelerometer_orientation2.png|Axis orientation of the second accelerometer]]

==Data acquisition==

The information from both of the accelerometers is exported through two
different input event based file mappings. These device nodes can be found at
''/dev/input/event2'' and ''/dev/input/event3''.

The sensor I am refering to as the first one is ''event2''. Therefore the second
one is accessible through the ''event3'' device.

These device nodes can be opened by the default filesystems calls for reading
files. The data can be read from the stream as soon as the sensor measures it.

==Data structure==

To be able to use the measured data it is important to understand the format
in which the data is provided.
The structure of the given data is based on the kernel input event message
system which exports the following data structure:

struct input_event {
struct timeval time;
__u16 type;
__u16 code;
__s32 value;
};

The data is written to the stream message by message. Therefore the minimal
used blocksize is 128 bit (16 byte).

Lets have a look at an example readout of the accelerometer data, divided into
the used sections.

|----- time ------| |type| |code| |-value-|
8c66 4819 721c 0006 0002 0002 03a8 0000
8c66 4819 7222 0006 0000 0000 0000 0000
8c66 4819 99e6 0006 0002 0000 0048 0000
8c66 4819 9a36 0006 0002 0001 0024 0000
8c66 4819 9a50 0006 0002 0002 0396 0000
8c66 4819 9a57 0006 0000 0000 0000 0000

I think the time structure does not need further explaination. A lot more
interesting is the type, code and value part of every message. Lets take a
closer look at these parts.

===Event types===

The types categorize the incoming messages. All possible types can be found in
the kernel sources or include files in ''INCLUDEDIR/linux/input.h''
During the tests with the accelerometers I observed the fact that only two
different message types are used.

;0x00:
:According to ''linux/input.h'' this event is called ''EV_SYN''. It signals the wish to ''syncronize''. Normally this event is used in combination with code 0x00 to mark the send data complete and therefore applyable.

;0x02:
:This event is called ''EV_REL'' and signals ''relative movement''. It is used to transmit the acceleration the sensors encounter.

The definition should not be taken too seriously in this context, because the
data values provided by the accelerometer always represent the absolute
acceleration measured at the given time.

===Event codes===

Both types of event may supply different codes. These codes can be understood
as some kind of further specification about the specified data values

====Syncronization event codes====

The syncronization event may use quite a lot of codes, as ''linux/input.h''
shows. However the only used one seems to be the 0x00 code.

;0x00:
:This code is refered to as SYN_REPORT. It means that the last dataset was completely transmitted. Therefore the before transmitted set of data values can be considered complete. This means if this message is recieved you may process the given data further.

====Relative movement event codes====

The amount of possible codes for this event type is quite big. The only used
ones are the following ones.

;0x00:
:REL_X - Acceleration in x direction

;0x01:
:REL_Y - Acceleration in y direction

;0x02:
:REL_Z - Acceleration in z direction

The X, Y and Z axis are to be understand as defined in the chapter about [[#Axis_orientation|Axis orientation]].

===A typical message block===

A typical message block consists of 3 messages containing the acceleration
data for every of the three axis followed by a syncronization message to
signal the end of the block.

The following example is such a message block with detailed explanation of its
different messages and data sections.

<pre>
8c66 4819 99e6 0006 0002 0000 0048 0000
|------Time-------| EV_REL REL_X |-Value-|
(Measured acceleration in x axis direction of 72)

8c66 4819 9a36 0006 0002 0001 0024 0000
|------Time-------| EV_REL REL_Y |-Value-|
(Measured acceleration in y axis direction of 36)

8c66 4819 9a50 0006 0002 0002 0396 0000
|------Time-------| EV_REL REL_Z |-Value-|
(Measured acceleration in z axis direction of 918)

8c66 4819 9a57 0006 0000 0000 0000 0000
|------Time-------| EV_SYN SYN_REPORT |-Value-|
(The transmitted data block is complete you may process the given data)
</pre>

==Test application==

A simple test application written in ruby:
<pre>
#!/usr/bin/env ruby
x = 0
y = 0
z = 0
File.open("/dev/input/event3") do |f|
while true
event = f.read(16).unpack("llSSl")
time = event[0] + event[1] / 1000000.0
type = event[2]
code = event[3]
value = event[4]
if type == 2
x = value if code == 0
y = value if code == 1
z = value if code == 2
end
if type == 0 && code == 0
sum = Math::sqrt(x*x + y*y + z*z).to_i
printf("%5d %5d %5d %5d\n", x, y, z, sum)
end
end
end
</pre>

Equivalent version in python:

{{TODO: The whitespace here has been lost! And the python is now broken :)}}
<pre>
#!/usr/bin/python
import struct
from math import sqrt

x = 0
y = 0
z = 0
secondsensorfile = "/dev/input/event3"
#int, int, short, short, int
fmt = 'iihhi'
#open file in binary mode
in_file = open(secondsensorfile,"rb")
event = in_file.read(16)
while event:
(time1,time2, type, code, value) = \
struct.unpack(fmt,event)
time = time1 + time2 / 1000000.0

if type == 2:
if code == 0:
x = value
if code == 1:
y = value
if code == 2:
z = value
if type == 0 and code == 0:
sum = int(sqrt(x*x + y*y + z*z))
print x, y, z, sum
event = in_file.read(16)
in_file.close()

</pre>

== The /sys interface ==

To get the sampling rate of the first accelerometer ''spi0.0'' :

# cat /sys/bus/spi/drivers/lis302dl/spi0.0/sample_rate
100

To set the sampling rate :

# echo 400 > /sys/bus/spi/drivers/lis302dl/spi0.0/sample_rate
# cat /sys/bus/spi/drivers/lis302dl/spi0.0/sample_rate
400

The other one is ''spi0.1''. See [[GTA02 sysfs#Accelerometers]] for the other options.

==See also==
* [[Accelerometer_Fundamentals]]
* [[Gestures]], [http://code.google.com/p/accelges/source/browse/trunk/accelneo/src/accelneo.c code sample]

==External Links==
* [http://projects.openmoko.org/projects/gestures/ Openmoko Motion Gestures]
* [http://en.wikipedia.org/wiki/Accelerometer Wikipedia - Accelerometer]
* [http://dev.borza.ro/demo/Motion-based%20Gesture%20Recognition%20with%20an%20Accelerometer/Paper.pdf Motion-based Gesture Recognition with an Accelerometer - Paper]
* [http://www.youtube.com/watch?v=s5QMW8k5nis YouTube video: Playing with Accelerometers]
* [http://westhoffswelt.de/blog/my_first_openmoko_application.html Magic Eightball Application using the Accelerometers]

[[Category:Accelerometer]]
[[Category:Application Developer]]

Accelerometer data retrieval

2008-11-09T10:32:44Z

Gromgull: /* Test application */

==Scope==

This document describes a way to access the data provided by the
accelerometers. Furthermore the format of the acquired datastream is explained
in detail. This document does not cover the physical basics of acceleration or
the mathematical details on this subject.

==Axis orientation==

To understand the values provided by the accelerometers it is crucial to
understand how the sensors are oriented. In the following I will refer to the
sensors as first and second sensor. The way to access the data sources of
these two will be described later on in this document.

The Z axis is pointing from the display downwards to to the back of the
openmoko. This applies to both of the sensors.

===Orientation of the first sensor===

To explain the axis orientation I have created some images for easier
understanding.

[[Image:Accelerometer_orientation1.png|Axis orientation of the first accelerometer]]

===Orientation of the second sensor===

In contrast to the first sensor the second one is turned 45 degrees around the
Z axis. See the attached image to get a clue about its orientation.

[[Image:Accelerometer_orientation2.png|Axis orientation of the second accelerometer]]

==Data acquisition==

The information from both of the accelerometers is exported through two
different input event based file mappings. These device nodes can be found at
''/dev/input/event2'' and ''/dev/input/event3''.

The sensor I am refering to as the first one is ''event2''. Therefore the second
one is accessible through the ''event3'' device.

These device nodes can be opened by the default filesystems calls for reading
files. The data can be read from the stream as soon as the sensor measures it.

==Data structure==

To be able to use the measured data it is important to understand the format
in which the data is provided.
The structure of the given data is based on the kernel input event message
system which exports the following data structure:

struct input_event {
struct timeval time;
__u16 type;
__u16 code;
__s32 value;
};

The data is written to the stream message by message. Therefore the minimal
used blocksize is 128 bit (16 byte).

Lets have a look at an example readout of the accelerometer data, divided into
the used sections.

|----- time ------| |type| |code| |-value-|
8c66 4819 721c 0006 0002 0002 03a8 0000
8c66 4819 7222 0006 0000 0000 0000 0000
8c66 4819 99e6 0006 0002 0000 0048 0000
8c66 4819 9a36 0006 0002 0001 0024 0000
8c66 4819 9a50 0006 0002 0002 0396 0000
8c66 4819 9a57 0006 0000 0000 0000 0000

I think the time structure does not need further explaination. A lot more
interesting is the type, code and value part of every message. Lets take a
closer look at these parts.

===Event types===

The types categorize the incoming messages. All possible types can be found in
the kernel sources or include files in ''INCLUDEDIR/linux/input.h''
During the tests with the accelerometers I observed the fact that only two
different message types are used.

;0x00:
:According to ''linux/input.h'' this event is called ''EV_SYN''. It signals the wish to ''syncronize''. Normally this event is used in combination with code 0x00 to mark the send data complete and therefore applyable.

;0x02:
:This event is called ''EV_REL'' and signals ''relative movement''. It is used to transmit the acceleration the sensors encounter.

The definition should not be taken too seriously in this context, because the
data values provided by the accelerometer always represent the absolute
acceleration measured at the given time.

===Event codes===

Both types of event may supply different codes. These codes can be understood
as some kind of further specification about the specified data values

====Syncronization event codes====

The syncronization event may use quite a lot of codes, as ''linux/input.h''
shows. However the only used one seems to be the 0x00 code.

;0x00:
:This code is refered to as SYN_REPORT. It means that the last dataset was completely transmitted. Therefore the before transmitted set of data values can be considered complete. This means if this message is recieved you may process the given data further.

====Relative movement event codes====

The amount of possible codes for this event type is quite big. The only used
ones are the following ones.

;0x00:
:REL_X - Acceleration in x direction

;0x01:
:REL_Y - Acceleration in y direction

;0x02:
:REL_Z - Acceleration in z direction

The X, Y and Z axis are to be understand as defined in the chapter about [[#Axis_orientation|Axis orientation]].

===A typical message block===

A typical message block consists of 3 messages containing the acceleration
data for every of the three axis followed by a syncronization message to
signal the end of the block.

The following example is such a message block with detailed explanation of its
different messages and data sections.

8c66 4819 99e6 0006 0002 0000 0048 0000
|------Time-------| EV_REL REL_X |-Value-|
(Measured acceleration in x axis direction of 72)

8c66 4819 9a36 0006 0002 0001 0024 0000
|------Time-------| EV_REL REL_Y |-Value-|
(Measured acceleration in y axis direction of 36)

8c66 4819 9a50 0006 0002 0002 0396 0000
|------Time-------| EV_REL REL_Z |-Value-|
(Measured acceleration in z axis direction of 918)

8c66 4819 9a57 0006 0000 0000 0000 0000
|------Time-------| EV_SYN SYN_REPORT |-Value-|
(The transmitted data block is complete you may process the given data)

==Test application==

A simple test application written in ruby:
<pre>
#!/usr/bin/env ruby
x = 0
y = 0
z = 0
File.open("/dev/input/event3") do |f|
while true
event = f.read(16).unpack("llSSl")
time = event[0] + event[1] / 1000000.0
type = event[2]
code = event[3]
value = event[4]
if type == 2
x = value if code == 0
y = value if code == 1
z = value if code == 2
end
if type == 0 && code == 0
sum = Math::sqrt(x*x + y*y + z*z).to_i
printf("%5d %5d %5d %5d\n", x, y, z, sum)
end
end
end
</pre>

Equivalent version in python:

{{TODO: The whitespace here has been lost! And the python is now broken :)}}
<pre>
#!/usr/bin/python
import struct
from math import sqrt

x = 0
y = 0
z = 0
secondsensorfile = "/dev/input/event3"
#int, int, short, short, int
fmt = 'iihhi'
#open file in binary mode
in_file = open(secondsensorfile,"rb")
event = in_file.read(16)
while event:
(time1,time2, type, code, value) = \
struct.unpack(fmt,event)
time = time1 + time2 / 1000000.0

if type == 2:
if code == 0:
x = value
if code == 1:
y = value
if code == 2:
z = value
if type == 0 and code == 0:
sum = int(sqrt(x*x + y*y + z*z))
print x, y, z, sum
event = in_file.read(16)
in_file.close()

</pre>

== The /sys interface ==

To get the sampling rate of the first accelerometer ''spi0.0'' :

# cat /sys/bus/spi/drivers/lis302dl/spi0.0/sample_rate
100

To set the sampling rate :

# echo 400 > /sys/bus/spi/drivers/lis302dl/spi0.0/sample_rate
# cat /sys/bus/spi/drivers/lis302dl/spi0.0/sample_rate
400

The other one is ''spi0.1''. See [[GTA02 sysfs#Accelerometers]] for the other options.

==See also==
* [[Accelerometer_Fundamentals]]
* [[Gestures]], [http://code.google.com/p/accelges/source/browse/trunk/accelneo/src/accelneo.c code sample]

==External Links==
* [http://projects.openmoko.org/projects/gestures/ Openmoko Motion Gestures]
* [http://en.wikipedia.org/wiki/Accelerometer Wikipedia - Accelerometer]
* [http://dev.borza.ro/demo/Motion-based%20Gesture%20Recognition%20with%20an%20Accelerometer/Paper.pdf Motion-based Gesture Recognition with an Accelerometer - Paper]
* [http://www.youtube.com/watch?v=s5QMW8k5nis YouTube video: Playing with Accelerometers]
* [http://westhoffswelt.de/blog/my_first_openmoko_application.html Magic Eightball Application using the Accelerometers]

[[Category:Accelerometer]]
[[Category:Application Developer]]

User:Gromgull

2008-11-09T10:01:30Z

Gromgull: /* Test Section */

Tickets I am interested in:
* https://docs.openmoko.org/trac/ticket/1743
* https://docs.openmoko.org/trac/ticket/677
* https://docs.openmoko.org/trac/ticket/1802
* https://docs.openmoko.org/trac/ticket/2082

== Test Section ==

Here is some text too.

this is preformatted
oh it is oh so preformatted

and this is some more text

User:Gromgull

2008-11-09T10:00:12Z

Gromgull: /* Test Section */

Tickets I am interested in:
* https://docs.openmoko.org/trac/ticket/1743
* https://docs.openmoko.org/trac/ticket/677
* https://docs.openmoko.org/trac/ticket/1802
* https://docs.openmoko.org/trac/ticket/2082

== Test Section ==

this is preformatted
oh it is oh so preformatted

and this is some more text

User:Gromgull

2008-11-09T09:59:52Z

Gromgull:

Orrery

2008-11-09T09:53:00Z

Gromgull: /* Revision(ist) History */

{{Application|Orrery}}

----
Please note: Some websites have links directly to the .ipk files for this program. While it is very gratifying that other people like the program enough to include a link to the .ipk file, those links will not automatically update when a newer .ipk file is uploaded. So using one of those links might cause you to install an obsolete version of the program. If your version of the code doesn't match the description below, please download the most recent version from here: [http://projects.openmoko.org/projects/orrery/]. The current version is 2.2, and the version is shown
under the "opts" menu, at the top of the "About Orrery / Symbol Key" page.
----

== Overview ==
The orrery is a simple open-source application for the Openmoko platform
which displays the night (and day!) sky. It is nowhere near as elaborate as, for
example Google Sky or xephem. It is intended to be a small application
that will have a storage footprint comparable to a ringtone, or one of
the games bundled with the openmoko rootfs. It requires no network connection,
but does use the GPS information, by querying gpsd.
It will be converted to work with Gypsy once the dbus based software stack
becomes available.

The star database was extracted from the Hipparcos catalog. To ease the
computational load, the coordinates are not precessed or nutated before
being displayed. Orbital elements are used,
rather than ephemerides, to calculate planet positions. Although
this is less accurate, it dramatically reduces the memory
footprint. The planet positions are accurate to a few arc
minutes, from 3000 BC to 3000 AD. Since the scale
on the default display is approximately 8 arc minutes
per pixel, these small errors are imperceptible, unless a very
large zoom factor is used.

Note, the screen grabs shown below were taken with the orrery running
atop the 2007.2 stack, because I find it easier to do a screen grab with
that stack. The program works with 2008.x too.

== The Display ==

[[Image:OrreryWithMenuTabs.png|200px|Orrery with Menu Tabs]]

The image above shows the default display - all stars visible to the unaided
eye, with colors for the brightest ones. It's displayed with a
Transverse Mercator projection (similar to Norton's Star Atlas) which works
well with the VGA aspect ratio in portrait mode.
It's a conformal transformation, so the
constellations have about the right shapes. The Sun, Moon and planets are
plotted, and the Moon is shown with the proper phase. The Sun and Moon are
plotted with a size about 3.5 times larger than their true angular size on
the sky.

The blue line near the bottom of the display is the horizon. Nothing below that line is visible, but the
program plots objects there anyway, because it is often
useful to know which objects are just about to rise, and
which ones have recently set.

=== The orrery as a compass ===
The green numbers at the bottom are the azimuth values. The
azimuth is measured along the horizon, from north through east.
So the azimuth of due north is 0, east is 90, south is 180
and west is 270 degrees. By using these azimuth values, the
orrery can be used as a celestial compass, if the sky above you
is at least partially clear. Notice that the azimuth values are
not exactly evenly spaced. This is caused by the distortion
introduced by the Transverse Mercator projection.

=== Constellations Display ===
There are two display screens defined. By default, one of them shows
the display shown above, and the other shows the constellations, and
symbolic representations of the solar system objects.

[[Image:OrreryFullScreenConstellations.png|200px|Orrery Full Screen Constellation]]

The constellations are plotted in three colors. The twelve zodiac
colors are plotted in hot pink. The constellations plotted in
gold are the classical Greek constellations, as listed in Ptolomy's Almagest (apart from the zodiac constellations, which are
also in the Almagest). The only constellation from the Almagest which is not
plotted is Argo Navis, which is not one of the official modern
constellations (Argo Navis was broken up into the modern constellations
Carina, Puppis and Vela). The remaining constellations, plotted in blue, where
added during the last few hundred years.

In addition to constellation names and figures, three great circles, the Celestial Equator
(light yellow), Ecliptic (red) and Galactic Plane (blue-green), are shown.
Solar system objects are shown symbolically (see Mercury, Venus,
the Moon and the Sun in the above image).

== Control Modes ==
The orrery has two control modes, "finger mode" and "stylus mode".
By default the program is in finger mode. In finger mode, the image
can be panned by tapping your finger in
the bottom 1/5 of the display (excluding menus). The size of
the panning step is controlled by how close your finger is
to the edge of the display. If you tap in the center, it pans
by 0 degrees, and nothing happens. If you tap near the
left or right edges, it
pans by the maximum allowed amount, +-45 degrees. Pan steps are
quantized in increments of 5 degrees. You may exit fullscreen mode
by tapping anywhere in the upper 1/5 of the display area.
Tapping anywhere else toggles between the two screens.

If you are in stylus mode, the view can be panned around the sky by
tapping the green arrows at the bottom, or the green azimuth values.
In stylus mode, to exit from fullscreen you must tap in the area
above the upper blue line, in the region where the time and location
are displayed. Tapping anywhere else toggles between the two screens.

There is a check box in the opts menu which allows you to turn finger mode on and off.

One may enter fullscreen mode by tapping the FS button at the
bottom left of the display.

== Menus ==
When not in fullscreen mode, one button and four menus are displayed at the bottom of the screen.

===FS===
Pushing the "FS" button pops you into fullscreen mode. To exit,
tap the top 1/5th of the display (if you are in finger mode) or
the region where the location and time is displayed (in stylus mode).

=== opts ===
==== Toggles ====
The opts menu allows you to toggle between finger and stylus mode.
It also has a checkbox labeled "Save All Changes". If that box is
checked, all changes you make within the menus are saved to flash
memory when you click the "OK" button. If "Save All Changed" is not
selected, you must click the "Save to Configuration File" to save
changed configurations to flash - clicking "OK" makes the changes
active for the current session, but does not save to flash.

==== Flashlight Modes ====
The "White Flashlight" button paints the entire screen white, and the
"Red Flashlight" button paints the entire screen red. Both may
be used as a flashlight, but the red one is best if you are trying
to preserve your night vision.

==== Sunrise, Moonrise, etc ====
The "Sun and Moon Information" button displays a page giving the
sun and moon positions, rise and set times, phase etc for five
days, centered on today:

[[Image:OrrerySunMoonPage.png|200px|Sun and Moon Information page]]

The highlighted date is the current UT date (unless the time menu
has been used to select a different time). The highlighted
rise and set times are the next ones which will occur at your
location. Of course, that may be on a different UT date (for
example, during daylight hours, the next sunrise will be tomorrow).
The times are shown as Universal Times (UT), which may annoy people,
UT is used because the orrery allows you to select any location on the
earth, and any time from 3000 BC until 3000 AD. It would be very
difficult to keep track of all the timezone, daylight savings change
dates, etc for that time range! So I have wimped out, and displayed
UT, which is always reasonably well defined.

The current sun and moon positions shown are geocentric - no
topocentric correction has been applied. However topocentric
corrections are applied when rise and set times are calculated,
so they should be reasonably accurate for a specific location on earth.

The moon illumination percentage shown on the line with the
rising and setting times is the value at transit. The
illumination shown on the line that has the drawing of the
moon phase is the illumination percentage at this moment.

==== Moon Calendar ====
The moon calendar is a graphic display of the phase of the moon for
each day from 10 months before the current month, until 10 months after
the current month (roughly 640 days), as shown below:

[[Image:OrreryMoonCalendar.png|200px|Moon Calendar]]

Each column shows one month, and the day number is shown for each row.
At the top and bottom of each column is shown the first letter of the
name of the month
shown in the column. Two vertical green lines separate years.
The current Universal Time date is outlined in a red box.

To exit the Moon Calendar display, just tap the screen anywhere.

==== About Orrery / Symbol Key ====
This button displays an annotated list of
all the symbols used on the orrery display.

=== time ===
The time menu allows you to specify an
explicit time between 3000 BC and 3000 AD, or the current
time. If "Now" is selected, the current time is used and the display updates
automatically once per minute. If a specific time is selected,
it is shown in red, to remind you that the display is not
going to update automatically as time passes. The time may be
specified as a calendar date, or as a Julian Date.

The Julian Date is a less ambiguous way of entering times
in the distant past than using a calendar date, because of the
differing calendar systems in use worldwide before the late 16th
century. For example, the date October 10, 1582 never occurred in
some European countries. Many countries have gaps in their calendars
with missing dates when they adopted the Gregorian Calendar.

=== place ===
The place menu allows you to select the GPS-derived location,
a user specified latitude and longitude, or a city or
astronomical observatory selected from a menu. The lists of
locations are stored in ASCII text files under the menus subdirectory
of the program installation area on your phone. You may
save your selected location, by hitting the "Save
to Configuration File" button, so it will be used the
next time you start the orrery. If you would like
to add additional cities etc to one of the menus, you may simply
edit one of the menu files, and add the name, latitude and longitude
of the location. You will need to restart the orrery program for
your new locations to become available.

If you select a "Custom" or "Menu" location, a button labeled
"Save in Private Menu" will appear. After you select your new position,
you may push that button to save it in the menu labeled "Private".
That menu is initially empty.

=== items ===
The display menu allows you to configure the display, selecting
such things as the faintest magnitude object displayed, whether constellation
lines are plotted, whether or not star names are displayed, etc.

==== Deep Sky Objects ====
If you select "Deep Sky Obs" from the items menu, you will
be shown some of the brightest Deep Sky Objects. Deep Sky
Objects are objects such as galaxies, expelled envelopes of
dying stars, clusters of young stars and lumious gas. A few,
such as the Andromeda Galaxy, are visible to the unaided eye.
Many more are visible with binoculars or a small telescope.
The orrery shows all messier objects, and many other
well known bright nebulae and star clusters.
The image bellow shows the Messier objects in Sagittarius.

[[Image:OrrerySagitarriusClusters.png|200px|Star clusters in Sagittarius]]

===== Adding Your Own Deep Sky Object List =====
You may add your own list of deep sky objects to be
plotted. Simply create a file within the directory
/usr/share/orrery/deepSky/ with any name. The
file should contain lines of text with the format

name HH MM SS.SS DD MM SS.S type mag

where name is the object name, which may not include
white space, HH MM SS.SS is the Right Ascension,
DD MM SS.S is the declination (do not include a + sign
for positive declinations) "type" is an integer
specifying the type of object. 0 = Supernova Remnant,
1 = Globular Cluster, 2 = Open CLuster, 3 = Diffuse
Nebula (HII region, etc), 4 = Planetary Nebula, and
5 = Galaxy. The "mag" is the visual magnitude. The
orrery program currently does nothing with the visual magnitude, but future versions may use it.

==== Changing the Magnitude Limit ====
By default, the orrery displays every star a person with excellent
eyesight located in a very dark area on a moonless night can see.
If your observing conditions are less ideal than that, it can be
helpful to use the "Mag. Limit" filed in the item menu to lower
the limit of the faintest object plotted. The plot below shows
the "Summer Triangle" region plotted with the default 6.6 limiting
magnitude on the left, and a 5.0 limiting magnitude on the right.

[[Image:OrreryMagComparison.png|400px|Changing the limiting magnitude]]

If you tap "Save to Configuration FIle" your new magnitude limit
will be the default the next time orrery is run.

== Touchscreen Gestures ==
There are four types of touchscreen gestures which you can make
in the plotting area which are recognized by the orrery: Taps,
Zooms, Pans and Presses.

=== Taps ===
If you press the display area, and withdraw your finger or stylus
within 0.25 seconds, that gesture is considered a tap.

[[Image:orreryTapRegions.png|200px|Orrery Tap Regions]]

Tapping in the lower 1/5 of the display area will pan the display in
azimuth. If you are in fullscreen mode, then tapping in the upper 1/5
of the display will take you out of fullscreen mode. Tapping anywhere
else toggles between the default screen and the constellation screen.

=== Zooms ===
If you press the screen and trace out a roundish figure, and remain
in contact with the screen for more than 0.25 seconds, and if
the figure encloses a nontrivial (> 300 pixels) area, the gesture
is considered to be a zoom. As you move your finger or
stylus, the region you are outlining will be shown
as a green dotted line. After you release your finger
from the display, a red box will be shown.
The red box is a rectangle with the aspect ratio of the
display area, and the same area and centroid as the region you
traced out with your finger. The display will then be zoomed so
that the region in the red box fills the display area:

[[Image:orreryZoomDemo.png|400px|Orrery Zoom Demo]]

The image above shows the display immediately after the zoom gesture
has been made (left) and after the zoom has become active (right).
One may zoom an image which has already been zoomed.

Zooming can do some non-intuitive things, especially if you zoom near
the upper left or upper right of the display. This is because
the orrery's transverse mercator projection always has a line of
constant azimuth in the center. This means that something zoomed
at the edge of the display area will be rotated as it is zoomed, and
some of the stars you wish to display may be rotated out of the
display area. It is best, especially if you are zooming in on
an area near the zenith, to first pan the display so that the region
is near the center of the display, before zooming. The nice
thing about the transverse mercator projection is that a zoomed
area is displayed with the orientation it would have if you were
directly facing it at the time indicated by the display.

If your zoom area includes the zenith, the display any do weird
things. This is a bug.

=== Pans ===
A pan is like a zoom, but with a more linear, rather than roundish
gesture. A pan can be used to move the center of a zoomed region.
It has no effect if the display area is not zoomed. After you
release your finger or stylus following a zoom gesture, orrery
will show the region you traced out in green, and will draw a red
arrow showing the direction and size of the pan. After that,
the display is re-drawn with the new center position.

[[Image:orreryPanDemo.png|400px|Orrery Pan Demo]]

The image above shows the display immediately after a pan gesture
has been made (left) and following the re-drawing of the display
area (right).

=== Presses ===
If you push down on the touchscreen for more than 0.25 seconds, and
do not move your finger or stylus significantly while making contact,
you will have made a press gesture. Since one almost always moves
one's finger a little by while pressing the screen, some small motion
is allowed during a press gesture. This means that a zoom or pan
gesture cannot be arbitrarily small, because it will be interpreted
as a press.

If the screen is zoomed, then the press gesture unzooms it. If the
screen is already unzoomed, then the press gesture has the same
effect as a tap gesture.

== Symbols ==
=== Symbol Key ===
If you select "About Orrery / Symbol Key" from the "opts" menu, you
will be shown an annotated list of the symbols used by the orrery,
which is reproduced below:

[[Image:OrrerySymbolKey.png|200px|Symbols used by the orrery]]

=== Planet Symbols ===
The solar system symbols, used by default on the constellation
page (screen two), are the standard astronomical symbols for these
objects. They are explained here:
[http://en.wikipedia.org/wiki/Planet_symbols]

=== Plotted Lines ===
The dotted yellow line is the Celestial Equator, the intersection of
the Earth's equatorial plane with the celestial sphere. The red
dotted line is the Ecliptic. The Ecliptic is the intersection
of the Earth's orbital plane with the celestial sphere. The
Ecliptic is also the path of the Sun across the sky, and the intersection
points between the Celestial Equator and the Ecliptic are where the
Sun is at the time of an equinox. Constellations lying along the
Ecliptic plane are zodiac constellations. The planets and the Moon
are always near, but usually not exactly on, the Ecliptic.
The blue-green dotted line is
the Galactic Plane, the intersection of the plane of the Milky Way's
disk and the celestial sphere.

== Displaying Stars Too Faint for the Unaided Eye to See ==
The default sky catalog used by the orrery contains every star
you can see with your unaided eye. If you wish to display stars
which require binoculars or a small telescope to be seen, you can
download the file hipparcos_9.0.dat from the orrery area of the
gForge site:
[http://projects.openmoko.org/projects/orrery/]. You must then load that file to your phone
with the name /usr/share/orrery/hipparcos.dat (you will be overwriting
the smaller catalog which comes with the package). If you
prefer to put the file elsewhere (on your microSD, for example), you
may make /usr/share/orrery/hipparcos.dat a soft link.

The default orrery star catalog contains 9931 stars. hipparcos_9.0.dat
contains 83392 stars, and is complete to 9th magnitude. Note
that the orrery will be more sluggish if you use this larger catalog.
Most people definately won't want to use it. The plot below shows
Lyra with limiting magnitudes of 6.6 (left) and 9.0 (right).

[[Image:orreryLyraComparison.png|400px|Orrery Catalogs]]

== System Requirements ==
=== Supported Phones ===
This program will run on either the neo1973 (gta01)
or the FreeRunner (gta02). Users of the neo1973
may wish to move the files to the microSD card, to
save space in the limited builtin flash memory
(see below).

=== Supported Software Stacks ===
This program has been tested running atop the
2007.2 and 2008.8 distributions. It probably will
work with FSO too. It is gtk based.

=== Memory Requirements ===
This program requires 630 kbytes of storage space in the phone's
builtin flash storage or microSD card. By default, most of
the files (everything except the .desktop file, the launch
icon and the executable) are stored under /usr/share/orrery.
This directory tree may be moved elsewhere, if the new
location is specified with the -d switch on the orrery
invocation line in the .desktop file. The .desktop
file resides in /usr/share/applications .

== Installing this Program ==
.ipk files for this program are now available for both the 2007.2
and 2008.8 stacks, at the gForge site. It is much easier to install
than it used to be. The latest .ipk files can be found here:
[http://projects.openmoko.org/projects/orrery/].

== Known Bugs ==

=== Zooming the zenith area doesn't work ===
If you make a zoom gesture that includes the zenith, or if
you pan a zoomed region so that the zenith falls within it,
the orrery goes nuts.

=== Restarting gpsd crashes orrery ===
If you restart gpsd while the orrery is running, the
orrery will crash if it is configured to use the GPS position.

'''Send more bug reports!'''

== Revision(ist) History ==

Version 2.2:
New user features:
Added a moon calendar, which shows the
phase of the moon for every day over
a 21 month period centered on the current
month.

Bug Fixes:
Flipped the orientation of the moon by
180 degrees on the "Sun and Moon Information"
page, for locations in the southern
hemisphere. It is oriented correctly on
the new moon calendar. It has always
been correct on the sky display.

== Contact Information ==
Please send comments, suggestions, questions and/or
abuse to orrery.moko@gmail.com

<onlyinclude>
{{ApplicationBox|
Name=[[Orrery]]|
Description=Orrery displays the objects in the night (or day) sky. It uses the GPS position, if available|
Screenshot=OrreryWithMenuTabs.png|
Homepage=http://projects.openmoko.org/projects/orrery/|
TestedOn=Om 2008.8|
PackageName=orrery
}}
</onlyinclude>

[[Category:Graphics Applications]]

Python

2008-11-09T09:42:35Z

Gromgull: /* Minimal ETK gui */

'''Python''' is a programming language which is applicable to scripting phone functionalities and graphical user interfaces. Currently, at least [[SettingsGUI]], [[SMSTool]] and [http://pavelmachek.livejournal.com/42672.html MokoMenu] use it. There is also [[Python ncurses]] for character user interfaces. [[Manually using Bluetooth]] is partially based on using Python.

== Environment ==

Source packages for Python contained in [[OpenEmbedded]] include:
python python-pygtk python-pycairo python-pygobject python-dbus

Binary packages for Python are not officially built yet but at least ScaredyCat's [[repositories]] provide them:
python-core python-misc python-lang python-subprocess python-threading etc.

ETK/EFL applications need the following binary packages too:
python-etk python-efl

GTK applications need the following binary packages too:
python-pygtk python-pycairo python-pygobject

{{note|These packages take up a considerable amount of space (several megabytes). Make sure that you have enough free space or install the packages to the media card as explained in [[package management]].}}

=== Missing ===

Parts of the Openmoko platform are not available in python yet, including gconf and evolution data server. python-openmoko is in the works for [[gsmd]] access etc. A recipe for PyWebKitGtk
is at [http://bugs.openembedded.org/show_bug.cgi?id=3028 OpenEmbedded bug #3028].

== See also ==

* [[Application Development Crash Course#Adding Python scripts as applications]]
* [[Wishlist:BuiltInScriptingLanguage]]
* [[Pexpect]] a pure Python module for spawning child applications
== Simple Example Scripts ==
=== Minimal ETK gui ===
See also [[EFL_Documentation]] for more links and examples.
<pre>
import etk

#create a button (not yet on any window)
b = etk.Button(label="Hello")

#create a (nonvisible) window and put the button on the window
w = etk.Window(title="Hello", child=b)

#create a silly callback function
def hello(target):
print 'Hello World'
etk.main_quit()

#make the button call the callback when pressed
b.on_clicked(hello)

#make the window display
w.show_all()

#start processing screen events
etk.main()
</pre>

=== Minimal GTK gui ===
import gtk

#create a (nonvisible) window
w = gtk.Window()

#create a button (not yet on any window)
b = gtk.Button('Hello')

#put the button on the window
w.add(b)

#create a silly callback function
def hello(target):
print 'Hello world'
exit()

#make the button call the callback when pressed
b.connect('clicked', hello)

#make the window display
w.show_all()

#start processing screen events
gtk.main()

[[Category:Application Developer]]

Themes

2008-10-27T11:54:53Z

Gromgull:

This page is a stub about making Openmoko pretty, waiting for openmono-look.org, see also [[Artwork]] for more general pretty things.

Everything is customizable already, but there is not much yet by way of ready-to-use themes for changing everything at once. Eventually, the plan is to offer readymade packages to change the phone's look and feel simply with `opkg' (or the graphical installer).
* For the eyes, one may change three things. First, the [[Configuring the boot splash screens| boot splash screens]]. Second, [[Customize Application Icons]] (also on [[Hacking the UI|this page]]). Three, everything else is determined by an Illume theme discussed below.
* For the ears, we can change [[Ringtones]], [[Boot sound]] and [[Tap sound]].
* By touch, we are not doing much with the vibrators and accels yet.

== Changing the Illume theme ==

To change the illume theme, download an already compiled ''.edj'' file and put it into ''~/.e/e/themes/illume.edj''. The [http://exchange.enlightenment.org/ Enlightenment exchange] repository offers many themes, modules and applications. The following themes were made specifically with the FreeRunner in mind:

* A Tango variant for Illume based distros is at [http://52grad.de/.stuff/freerunner/].
* CarloRatm [http://forum.telefoninux.org/index.php/topic,649.0.html illume theme]. If you do not read Italian try [http://lists.openmoko.org/nabble.html#nabble-tc1377326%7Ca1377326 this thread on the mailing list] first.''I've made it only for testing an application, there are some errors (e.g. the charging battery icon...) i'll try to solve next days -- CarloRatm''
<pre>
> In the enlightenment archives there's a new Rasterman image:
> - openmoko-illume-image-glibc-ipk--20080929-om-gta02.rootfs.jffs2 [1]
> It looks so cool with the new illume theme [2] [3] [4] [5] [6], but
> practically it has no telephony related software installed in since it
> seems a simple OE built with these scripts [7], so (I figure) that
> you're free to put in both the FSO and/or the Om2008.8 stack, just
> install the needed packages!
>
> [1] http://download.enlightenment.org/misc/Illume/
> [2] http://forum.telefoninux.org/index.php/topic,533.0/topicseen.html
> [3] http://www.rasterman.com/files/illume-01.ogg
> [4] http://www.rasterman.com/files/illume-02.ogg
> [5] http://www.rasterman.com/files/illume-03.ogg
> [6] http://www.rasterman.com/files/illume-04.ogg
> [7] http://www.rasterman.com/files/oe-setup.tar.gz
</pre>
Creating or modifying an Illume theme is not as simple as editing a text file, because for performance reasons the ''.edj'' files are compiled. See the instructions about [[Edje]].

== Where to find other themes elements ==

A GTK theme following the Tango line is at [http://www.3v1n0.net/openmoko/moko-sun-gtkrc].

There are a few background images for the [[Display Locker]] screen in Om 2007.2.

Unreleased ongoing work:
* http://arbnora.projects.openmoko.org/
* http://ninja.projects.openmoko.org/

[[Category:Settings]]

Themes

2008-10-27T11:54:12Z

Gromgull:

This page is a stub about making Openmoko pretty, waiting for openmono-look.org, see also [Artwork] for more general pretty things.

Everything is customizable already, but there is not much yet by way of ready-to-use themes for changing everything at once. Eventually, the plan is to offer readymade packages to change the phone's look and feel simply with `opkg' (or the graphical installer).
* For the eyes, one may change three things. First, the [[Configuring the boot splash screens| boot splash screens]]. Second, [[Customize Application Icons]] (also on [[Hacking the UI|this page]]). Three, everything else is determined by an Illume theme discussed below.
* For the ears, we can change [[Ringtones]], [[Boot sound]] and [[Tap sound]].
* By touch, we are not doing much with the vibrators and accels yet.

== Changing the Illume theme ==

To change the illume theme, download an already compiled ''.edj'' file and put it into ''~/.e/e/themes/illume.edj''. The [http://exchange.enlightenment.org/ Enlightenment exchange] repository offers many themes, modules and applications. The following themes were made specifically with the FreeRunner in mind:

* A Tango variant for Illume based distros is at [http://52grad.de/.stuff/freerunner/].
* CarloRatm [http://forum.telefoninux.org/index.php/topic,649.0.html illume theme]. If you do not read Italian try [http://lists.openmoko.org/nabble.html#nabble-tc1377326%7Ca1377326 this thread on the mailing list] first.''I've made it only for testing an application, there are some errors (e.g. the charging battery icon...) i'll try to solve next days -- CarloRatm''
<pre>
> In the enlightenment archives there's a new Rasterman image:
> - openmoko-illume-image-glibc-ipk--20080929-om-gta02.rootfs.jffs2 [1]
> It looks so cool with the new illume theme [2] [3] [4] [5] [6], but
> practically it has no telephony related software installed in since it
> seems a simple OE built with these scripts [7], so (I figure) that
> you're free to put in both the FSO and/or the Om2008.8 stack, just
> install the needed packages!
>
> [1] http://download.enlightenment.org/misc/Illume/
> [2] http://forum.telefoninux.org/index.php/topic,533.0/topicseen.html
> [3] http://www.rasterman.com/files/illume-01.ogg
> [4] http://www.rasterman.com/files/illume-02.ogg
> [5] http://www.rasterman.com/files/illume-03.ogg
> [6] http://www.rasterman.com/files/illume-04.ogg
> [7] http://www.rasterman.com/files/oe-setup.tar.gz
</pre>
Creating or modifying an Illume theme is not as simple as editing a text file, because for performance reasons the ''.edj'' files are compiled. See the instructions about [[Edje]].

== Where to find other themes elements ==

A GTK theme following the Tango line is at [http://www.3v1n0.net/openmoko/moko-sun-gtkrc].

There are a few background images for the [[Display Locker]] screen in Om 2007.2.

Unreleased ongoing work:
* http://arbnora.projects.openmoko.org/
* http://ninja.projects.openmoko.org/

[[Category:Settings]]

User:Gromgull

2008-10-25T09:26:43Z

Gromgull:

User:Gromgull

2008-10-25T09:26:22Z

Gromgull: New page: Tickets I am interested in: * https://docs.openmoko.org/trac/ticket/1743 * http://docs.openmoko.org/trac/ticket/677 * https://docs.openmoko.org/trac/ticket/1802 * https://docs.openmok...

Tickets I am interested in:
* https://docs.openmoko.org/trac/ticket/1743
* http://docs.openmoko.org/trac/ticket/677
* https://docs.openmoko.org/trac/ticket/1802
* https://docs.openmoko.org/trac/ticket/2082

Debian

2008-10-16T09:53:20Z

Gromgull: /* Using matchbox-window-manager with XFCE */

= Installation =
There are "official" instructions on how to install [http://wiki.debian.org/DebianOnFreeRunner Debian on FreeRunner] or [http://wiki.debian.org/DebianOnNeo1973 Debian on Neo1973] (see the [http://lists.linuxtogo.org/pipermail/smartphones-standards/2008-August/000232.html original announcement]).

Previous information (partly outdated, now) on how to install Debian manually has been moved to [[Manual Debian]].

See also : http://www.debian.org/ to know more about Debian.

From time to time the Debian packages may be broken, which will cause the install.sh script to fail. Since waiting for the packages to be fixed can take quite a lot of patience, [http://dgym.homeunix.net/projects/freerunner/debian-install/ here] is an alternative method of getting Debian installed on the FreeRunner.

= System =
== Password ==

The default root password is blank. You should change that as soon as you can:
# passwd
If entering a blank password does not work at first, try rebooting. If still no success, boot to 2008.08/2007.02, chroot to the micro SD card and set a new password.

== Speeding up booting ==
'''Note''': By default, Debian is already configured to write limited messages to the console during boot. Does this actually speed things up anymore?

What's good for every linux booting is also good for our debian on the freerunner: booting in quiet mode. To do so by default just boot your Neo FreeRunner in NOR-Flash and execute this configure-script: [http://paste.ubuntuusers.de/391456/ configure-uboot.sh].

It changes default booting to quiet-mode and adds another boot-option to boot without quiet-mode for debugging purpose.

== Suspend ==

'''Note''': As of Sep. 15 2008, suspend works 'out-of-the-box'; installing apm and the idle clock configuration changes do not seem to be necessary any more. Press the power button for two seconds (in zhone) or run 'apm -s' to suspend.

To make suspend available you have to install apmd:
apt-get install apmd
After that you can suspend your phone with:
apm -s
and make it wake up again with pressing the power button.

Issues:
* [[User:Wuth|Wuth]] 06:28, 17 August 2008 (UTC): I found that apmd was already installed by using the official debian installation procedure, but that the kernel didn't support apm. I haven't yet resolved this issue. [[User:Wuth|Wuth]] 05:31, 7 September 2008 (UTC): Worked fine on second install. Perhaps this is no longer a problem.

* [[User:Phyce|Phyce]] 21:33, 20 August 2008 (UTC) installed apm without problems; apm -s shutdowns the freerunner but I couldn't wake it up with power button... I had to remove the battery to boot again. suspend/resume was working quite reliably with latest kernels on ASU.

To wake up successfully, the idle-clock of the SD card needs to be enabled right before suspend. It can be disabled again right after resume (this reduces GPS interference). Write into /etc/apm/suspend.d/00sd_idleclk
#!/bin/sh
echo 1 > /sys/module/glamo_mci/parameters/sd_idleclk
touch /home/root/.profile
and into /etc/apm/resume.d/00sd_idleclk
#!/bin/sh
echo 0 > /sys/module/glamo_mci/parameters/sd_idleclk
These are from -stacy on the community list.

And anotherone from [[User:Morlac|Morlac]]: (more debianish i think ;) 
etc/apm/scripts.d/sd_idleclk and corresponding link in /etc/apm/event.d 
(don't forget to chmod +x /etc/apm/scripts.d/sd_idleclk)

#!/bin/sh
SD_IDLECLK="/sys/module/glamo_mci/parameters/sd_idleclk"
[ -e "${SD_IDLECLK}" ] || exit 0

case "${1},${2}" in
(suspend,*)
echo 1 > ${SD_IDLECLK}
touch /etc
;;
(resume,suspend)
echo 0 > ${SD_IDLECLK}
;;
esac

exit 0

== Time ==

The default time zone is UTC. Reconfigure it by running

# dpkg-reconfigure tzdata

To set the clock manually do something like

# date -s 00:33

If you have a network connection, do something like

# apt-get install ntpdate
# ntpdate-debian

Issues:
* That's probably not sufficient to keep the clock accurate. It might be worth configuring some form of NTP.
** Setting the clock could be done via GPS: [[Getting_GPS_console_output_with_gllin#GPRMC_message]]

== WLAN ==
=== wifi-radar ===

If you don't want to mess up with configuration files and is looking for an easy gui for wireless configuration, then wifi-radar is what you are looking for.

<pre>apt-get install wifi-radar
wifi-radar</pre>

If you are looking for more, read on...

=== Installing prerequisites ===

Make sure the following packages are installed
apt-get install wireless-tools wpasupplicant dhcp3-client

=== Example configurations ===

==== Single network configuration ====

Assuming your wireless router uses WPA security and DHCP,
edit <code>/etc/network/interfaces</code> to include a section like this:
<pre>
auto eth0
iface eth0 inet dhcp
wpa-driver wext
wpa-ssid "MyWirelessName"
wpa-psk "MyWirelessPassword"
</pre>
Where, of course, you're using the name of your wireless network and it's password
instead of ''MyWirelessName'' and ''MyWirelessPassword''.

You can test by running
# ifup eth0

You can determine your IP address by running
# ifconfig eth0

Issues:
* only works if in presence of wireless network on boot, or when manually running <code>ifup eth0</code>
* booting away from wireless network is slower because waits for DHCP to time out
* does not reestablish connection when leaving wireless area and then returning
* does not support multiple wireless networks or open hotspots that you may travel between

Once wpa_supplicant has begun managing your wifi interface, you should type "wpa_action eth0 stop" instead of "ifdown eth0".

==== Roaming configuration ====

'''Todo''': Which of the issues that single network configurations suffer from are addressed by WPA roaming mode? Would ifplugd / guessnet help, or just make things more complicated?

* Roaming from network to network is not automatic. Instead, you need to manually run "wpa_action eth0 stop; ifup eth0" to switch networks

===== wpa_supplicant.conf =====

To configure WPA to roam between wireless networks, you will need to create a new configuration file:

/etc/wpa_supplicant/wpa_supplicant.conf

a template for this file (and more documentation) is available in:

/usr/share/doc/wpasupplicant/examples/wpa-roam.conf

You'll need to add networks to this file. Examples:

WEP:

network={
ssid="MySSID"
key_mgmt=NONE
wep_key0="abcdefghijklm"
# wep_key0=6162636465 # <- no quotes, so hex number
wep_tx_keyidx=0
id_str="MySSID"
}

No key:

network={
ssid="SomeNetwork"
key_mgmt=NONE
}

WPA:

network={
ssid="Example WPA Network"
psk="mysecretpassphrase"
id_str="home"
}

===== /etc/network/interfaces =====

Next, you'll need to edit /etc/network/interfaces. This lets you configure your wireless networks to use dhcp, or other appropriate TCP/IP settings:

auto eth0
iface eth0 inet manual
wpa-driver wext
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf

# MySSID comes from an id_str above.
iface MySSID inet dhcp

# default is what's used if there is no id_str setting.
# so the 'SomeNetwork' network will use DHCP.
iface default inet dhcp

iface home inet static
# static interface settings, or whatever...

Finally, if you want attempts to access the internet to default to eth0 (and not usb0), then comment out this line under usb0 adapter configuration:

gateway 192.168.0.200

For some reason, I had to reboot for the id_str settings to take effect. However, you should now be able to use "ifup eth0" to associate with the access point and "wpa_action eth0 stop" to down the wifi adapter.

=== Further reading ===

To use all the possibilities of <code>wpasupplicant</code> like roaming and automatic connection to different networks,
you should read <code>/usr/share/doc/wpasupplicant/README.Debian.gz</code>

== Bluetooth ==

The FreeRunner uses the standard Linux bluez stack, installed with
# apt-get install bluez-utils

There is also a module missing from /etc/modules, which is critical to getting your device recognized. (kudos to johnsu01 on irc.freenode.net:#openmoko-debian for the find)
# echo ohci-hcd >> /etc/modules

The first time you try this, you can also
# modprobe ohci-hcd

The only atypical part of using bluetooth on the FreeRunner is turning it on, which can be done with
# echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on
# echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset

Then the device should be visible using
# hcitool dev

== Better Xorg ==
By default debian uses fbdev... But we can use Xglamo:
<pre>apt-get install xserver-xglamo</pre>
after that edit /etc/X11/xorg.conf and change the line
<pre>Driver "fbdev"</pre>
to:
<pre>Driver "Xglamo"</pre>
and if you want to run xserver as normal user:
<pre>chmod u+s /usr/bin/Xglamo</pre>

with that you:
*can use xrandr
*don't have the pointer callibration bug with the rotated mode
*have better performances

== Running X as normal user ==
1. Create a new user
<pre>
# useradd -m -G audio,dialout,floppy,video,staff username
# passwd username
</pre>

2. Edit <code>/etc/init.d/zhone-session</code> and change <code>USER=root</code> to <code>USER=username</code> in it. Then to make sure changes are not lost on upgrade, run
<pre>
dpkg-divert --add /etc/init.d/zhone-session
</pre>
This will make new versions of <code>/etc/init.d/zhone-session</code> be written to <code>/etc/init.d/zhone-session.distrib</code>

3. Edit <code>/etc/X11/Xwrapper.config</code> and change <code>allowed_users=console</code> to <code>allowed_users=anybody</code>

4. Make apm setuid root so that zhone can do suspend and make it only executable for users in the staff group
<pre>
dpkg-statoverride --update --add root staff 4750 /usr/bin/apm
</pre>
It would also be possible to use sudo, but then you would have to edit /usr/bin/zhone.

== Sound ==
Make sure to put your user in the audio group ("adduser <username> audio").

If there is no error but no sound, try these state files:
[[Talk:Manual_Debian#Sound]]

== How to replace the default kernel with a recent openmoko kernel ==

If you would like to update to a new kernel, here is a short summary of what to do to update the kernel to an actual OM kernel. But only do this if you know what you are doing.
At the moment there is a little problem in the question which kernel to use. Hopefully it will be solved in the near future.

The original openmoko kernel works fine except for the fact that suspending with zhone doesn't work. But this kernel supports different really nice usb gadgets. :) 
download stable: http://downloads.openmoko.org/releases/Om2008.8-update/ 
download testing: http://downloads.openmoko.org/daily/

The new FSO3 kernel works fine and suspend/resume with zhone is also possible. But this kernel still has no loadable usb gadget modules (17-Sep-2008 01:39). :/ 
download testing: http://downloads.freesmartphone.org/fso-testing/images/ 
download unstable: http://downloads.freesmartphone.org/fso-unstable/images/
# Download a recent'' kernel'' and ''rootfs'' (tar.gz) from one of the above mentioned sources. It's your decision if you want suspend or usb gadget modules at the moment.
# Backup your running kernel like <code>mv /boot/uImage.bin /boot/uImage.bin.old</code>, then copy the downloaded uImage file to the freerunner as <tt>/boot/uImage.bin</tt>.
# Backup your actual modules like <code>mv /lib/modules/2.6.24 /lib/modules/2.6.24.old</code>, then extract the downloaded rootfs tar.gz to a temporary directory and copy <tt>lib/modules/2.6.24</tt> from the temp directory to <tt>/lib/modules/2.6.24</tt> on the FreeRunner.
# Run a <code>depmod -a</code>.
# Do a <code>chown -R root.root /lib/modules/2.6.24</code> because the owner from the tar.gz is something else.
# This step is only needed for the OM kernel but it doesn't harm the FSO kernel setup. Add "g_ether" Module to /etc/modules like <code>echo g_ether >> /etc/modules</code>. I read in an email, that the module "ohci-hcd" is also needed for some bluetooth functions, but i don't know this for real. I inserted it to my modules file to be on the safe side.
# Reboot and hope everything works as expected. :)
--[[User:Pini]] Sun Sep 28 15:01:46 UTC 2008
* Actually suspend/resume doesn't work anymore on the Neo Freerunner with the FSO3 kernel starting from september 16th. It does work with the Om2008.8 kernel from september 3rd.

= Software =
You can install <tt>[http://packages.debian.org/search?keywords=dselect dselect]</tt>(~2.2MB) or <tt>[http://packages.debian.org/search?keywords=aptitude aptitude]</tt>(~12MB) to visually inspect the available debian packages using the desktop's console. 
Also the gtk-based package-manager <tt>[http://packages.debian.org/search?keywords=synaptic synaptic]</tt>(~15.7MB) is probably working. 
Finally, on constrained systems, just issue the command:
grep -e Package: -e Description /var/lib/dpkg/available|more
== Web Browser ==
[http://lists.openmoko.org/nabble.html#nabble-td781547 Arne Anka suggested] trying the light-weight webkit-based [http://en.wikipedia.org/wiki/Midori_(browser) midori] browser:
apt-get install midori

== TangoGPS ==
{{main|TangoGPS}}
== e-book reader ==
{{main|FBReader}}

Evince is also available in debian, and handles pdf, djvu, cbz, and other formats.

There is also a hack to convert drm protected adobe ebooks to .cbz files readable with evince, which is mentioned on the mailing list.

== XFCE ==

xfce is small and lightweight and so is quite fast for the FreeRunner.

apt-get install xfce4
cp /etc/init.d/zhone-session /etc/init.d/xfce

Then you may hack /etc/init.d/xfce making

PROG_FSO=/usr/bin/startxfce4

Customize the boot process (this may have to be redone when zhone-session is updated):

update-rc.d -f zhone-session remove
update-rc.d -f xfce defaults

edit your /etc/hosts to have :

127.0.0.1 localhost debian-gta02

Start XFCE !

/etc/init.d/zhone-session stop
/etc/init.d/xfce start

The desktop takes a while to start but once up was snappy as can be expected.
I've not yet looked at the reason for the seemingly too slow start for the desktop.

zhone is available from the "Office" menu in xfce.
The matchbox keyboard is available in "Accessories".

If you want to display the screen on the long side (ie rotated, 4:3 aspect), add the following to the /etc/X11/xorg.conf in both the Device and InputDevice sections :

Option "Rotate" "CCW"

and then (re)start xfce.

=== Using matchbox-window-manager with XFCE ===

XFCE's window manager is poorly configured for use with the FreeRunner. Fortunately, matchbox's window manager is compatible with xfce. To use the matchbox window manager, arrange to run the following commands at X startup. If you followed the instructions above to run X as a normal user, put this in ~/.xinitrc:

#!/bin/sh

zhone &
matchbox-keyboard-toggle &
exec matchbox-window-manager -use_titlebar no -use_cursor no &
xfce4-session

{{Todo|And if I didn't run X as a normal user?}}

= Miscellaneous =
== Making the cursor invisible ==

=== Using matchbox ===

Matchbox has an option, <code>use_cursor</code>, that can be used to control whether to show the cursor.
For the default setup, edit <code>/usr/bin/zhone-session</code> and change the matchbox command to
matchbox-window-manager -use_titlebar no -use_cursor no

=== Using unclutter ===

Unclutter is a program that hides the cursor after a period of inactivity. To use unclutter, install it
#apt-get install unclutter
and choose ''Yes'' to the question <code>Start unclutter automatically?</code>. To change settings edit
<code>/etc/default/unclutter</code>.

=== Changing the cursor ===
To make the cursor invisible create a file called empty.cursor with this content:
#define empty.cursor_width 16
#define empty.cursor_height 16
static unsigned char empty.cursor_bits[] = {
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};
Now you can execute:
xsetroot -cursor empty.cursor empty.cursor
and the cursor will be invisible. To make this permanent you have to invent something ;) It must be executed after zhone has finished starting up.

== Running X applications on your desktop in nested X server ==
Sometimes it is helpful to have a big screen, keyboard and mouse. You can run X applications in a nested X server window.
On your desktop install the nested X server application Xephyr (better that Xnest)
apt-get install xserver-xephyr
Run a nested X server as display :1
Xephyr :1 -ac -br -screen 480x640 -reset -terminate &
Now you are able to run apps on your Neo which will display on your desktop PC. Make sure to set the display, for example if "mydesktop" is your desktop hostname
DISPLAY=mydesktop:1 xfce4-session &

== Using the mouse and keyboard from your desktop on the OM device ==
If you are running Linux (or a similar xorg capable operating system) on your Desktop, you can export your xsession to the openmoko device and use your mouse and keyboard on the Neo screen. A little program called x2x makes it even possible to do this simultaneously on the fly. When activated you just move your mouse to the edge of your monitor and then the mouse cursor continues on the screen of your openmoko device. If you select a window on the OM, the input of your keyboard is automatically entered in that window. You can even use the clipboard to copy data from tour desktop to OM and in the reverse direction.

Configure your desktop computer to export your xsession:
On your desktop (with root permissions):
Make sure that sshd is installed and in /etc/ssh/sshd_config you have set
X11Forwarding yes

In K/Ubuntu sshd is in the package openssh-server.

On your OM device install x2x (with root permissions)
apt-get install xauth x2x
Now open a new X terminal on your desktop computer. You MUST be the same user that is running the xsession on your desktop (i.e. do not su to root or another user in your x terminal!). Use the same username that is running an xsession on your OM device. Assuming that you have a usb networking connection to OM (with standard configuration) on the user prompt of your desktop type:
user@desktop:~$ ssh -X openmoko@192.168.0.202 "/usr/bin/x2x -east -to :0.0"
Hit return and enter your password. The xterm window will be unresponsive after that, but keep it open until you disconnect your OM device.

Now move your mouse cursor across the right edge of your monitor. It should enter the screen of your OM device from the left. Of course you can also use -west, -north or -south, depending on your preference where you place your OM.

If computer says:
sh: /usr/X11R6/bin/xauth: No such file or directory
X11 connection rejected because of wrong authentication.
x2x - error: can not open display localhost:11.0

It means you haven't installed xauth on your OM. So on your OM (with root permissions)
apt-get install xauth

= Support =

Debian is supported on the linux to go
[http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland smartphone mailing list]

= Known Issues =

== apt-get segmentation fault ==

Whenever you get a segmentation fault while using apt-get or aptitude, clean the database so it will rebuild it
rm /var/cache/apt/*.bin

= Why use debian =

The point of debian on the freerunner is that you get a huge army of software in a repository, all compiled for the arm processor.

Debian is used on many other embedded devices too and so there's a much larger repository of software already available than in the 2008.8 opkg archives.

You can build your own things without need to play with openembedded.

For example compiling natively is a snap w/ debian, just apt-get gcc&libc-dev (on gentoo too) and not so easy w/ om images :) (borked compiler, borked headers).

[[Category:Debian]]

Talk:Artwork

2008-10-15T22:36:43Z

Gromgull:

I started updating this page a bit, and then discovered that it overlaps slightly with [[Themes]] and it's not really linked from anywhere either.
What to do now? :)
[[User:Gromgull]]

this came up on #openmoko: [http://62.75.157.44/openmoko/] --[[User:Minime|Minime]] 18:05, 28 July 2007 (CEST)

== great stuff ==

well done - this looks great [[User:Johan|Johan]] 18:51, 28 July 2007 (CEST)

Artwork

2008-10-15T22:34:35Z

Gromgull: /* OpenMoko Wallpapers */

== Icons ==
[[User:nenadgrujicic|Nenad Grujicic]]: some ideas, device and suite icons

=== Device Icon ===

Here is a 256x256 png device icon for fic neo1973

preview:

http://i18.tinypic.com/62n9sba.jpg

save as ..

http://i15.tinypic.com/5yd5onm.png

=== Openmoko "Suite" Icons Idea: ===
[[Image:Mainicon.png]]
[[Image:Openmokosync.png]]
[[Image:Mediatransfer.png]]
[[Image:Ghostbackup.png]]
[[Image:Filebrowser.png ]]

[http://i11.tinypic.com/4yii7io.jpg link My Desktop Screenshot with icons]

== Application Themes ==

See also [[Themes]]

* The Tange Theme: http://52grad.de/.stuff/freerunner/

== OpenMoko Wallpapers ==

Wallpapers for the FreeRunner!

See [[Changing wallpaper]]

== PC Wallpapers ==

OpenMoko themed wallpapers for your desktop/laptop!

See also [[Desktop wallpaper gallery]]

=== Logo Plain ===

preview:

[[Image:Moko_plain_black.png|300px|black]]
[[Image:Moko_plain_white.png|300px|white]]
[[Image:Moko_plain_transparent.png|300px|transparent]]

=== Logo Wired 3D ===

preview:

[[Image:Moko_wire_black.png|300px|black]]
[[Image:Moko_wire_white.png|300px|white]]

{{Languages|Artwork}}

[[Category:User Interfaces]]

Artwork

2008-10-15T22:34:18Z

Gromgull:

== Icons ==
[[User:nenadgrujicic|Nenad Grujicic]]: some ideas, device and suite icons

=== Device Icon ===

Here is a 256x256 png device icon for fic neo1973

preview:

http://i18.tinypic.com/62n9sba.jpg

save as ..

http://i15.tinypic.com/5yd5onm.png

=== Openmoko "Suite" Icons Idea: ===
[[Image:Mainicon.png]]
[[Image:Openmokosync.png]]
[[Image:Mediatransfer.png]]
[[Image:Ghostbackup.png]]
[[Image:Filebrowser.png ]]

[http://i11.tinypic.com/4yii7io.jpg link My Desktop Screenshot with icons]

== Application Themes ==

See also [[Themes]]

* The Tange Theme: http://52grad.de/.stuff/freerunner/

== OpenMoko Wallpapers ==

Wallpapers for the FreeRunner!

See [Changing wallpaper]

== PC Wallpapers ==

OpenMoko themed wallpapers for your desktop/laptop!

See also [[Desktop wallpaper gallery]]

=== Logo Plain ===

preview:

[[Image:Moko_plain_black.png|300px|black]]
[[Image:Moko_plain_white.png|300px|white]]
[[Image:Moko_plain_transparent.png|300px|transparent]]

=== Logo Wired 3D ===

preview:

[[Image:Moko_wire_black.png|300px|black]]
[[Image:Moko_wire_white.png|300px|white]]

{{Languages|Artwork}}

[[Category:User Interfaces]]

Artwork

2008-10-15T22:30:41Z

Gromgull: /* Wallpaper */

== Icons ==
[[User:nenadgrujicic|Nenad Grujicic]]: some ideas, device and suite icons

=== Device Icon ===

Here is a 256x256 png device icon for fic neo1973

preview:

http://i18.tinypic.com/62n9sba.jpg

save as ..

http://i15.tinypic.com/5yd5onm.png

=== Openmoko "Suite" Icons Idea: ===
[[Image:Mainicon.png]]
[[Image:Openmokosync.png]]
[[Image:Mediatransfer.png]]
[[Image:Ghostbackup.png]]
[[Image:Filebrowser.png ]]

[http://i11.tinypic.com/4yii7io.jpg link My Desktop Screenshot with icons]

== Wallpaper ==

See also [[Desktop wallpaper gallery]]

=== Logo Plain ===

preview:

[[Image:Moko_plain_black.png|300px|black]]
[[Image:Moko_plain_white.png|300px|white]]
[[Image:Moko_plain_transparent.png|300px|transparent]]

=== Logo Wired 3D ===

preview:

[[Image:Moko_wire_black.png|300px|black]]
[[Image:Moko_wire_white.png|300px|white]]

{{Languages|Artwork}}

[[Category:User Interfaces]]

Artwork

2008-10-15T22:30:28Z

Gromgull:

== Icons ==
[[User:nenadgrujicic|Nenad Grujicic]]: some ideas, device and suite icons

=== Device Icon ===

Here is a 256x256 png device icon for fic neo1973

preview:

http://i18.tinypic.com/62n9sba.jpg

save as ..

http://i15.tinypic.com/5yd5onm.png

=== Openmoko "Suite" Icons Idea: ===
[[Image:Mainicon.png]]
[[Image:Openmokosync.png]]
[[Image:Mediatransfer.png]]
[[Image:Ghostbackup.png]]
[[Image:Filebrowser.png ]]

[http://i11.tinypic.com/4yii7io.jpg link My Desktop Screenshot with icons]

== Wallpaper ==

See also [Desktop wallpaper gallery]

=== Logo Plain ===

preview:

[[Image:Moko_plain_black.png|300px|black]]
[[Image:Moko_plain_white.png|300px|white]]
[[Image:Moko_plain_transparent.png|300px|transparent]]

=== Logo Wired 3D ===

preview:

[[Image:Moko_wire_black.png|300px|black]]
[[Image:Moko_wire_white.png|300px|white]]

{{Languages|Artwork}}

[[Category:User Interfaces]]

Talk:Building a hello world application

2008-10-15T21:34:36Z

Gromgull:

Thanks Talpa for this nice tutorial ! --[[User:Micktaiwan|Micktaiwan]] July 17 2007

So what is actually the problem with not using bitbake? These docs don't actually say anything!

Talpa, this is a great tutorial. Thanks!
Shouldn't step 4 refer to GTK?
[[User:MichaelShiloh|MichaelShiloh]] November 13, 2007

This page is good! - but it should be tidied up. I got here linked from MokoMakefile, but this page is more GTK centric.
The GTK specific info could perhaps be extracted into a [[Developing with C and GTK]] (following the pattern of [[Developing with C++ and Qt]])
and this page could be left with just a "how to compile your first hello.c as a openembedded-package using MokoMakefile?

[[User:Gromgull|Gromgull]]

Openmoko developer guide

2008-10-15T21:28:18Z

Gromgull: /* Part II Coding and compiling */

{{Languages|Openmoko developer guide}}

This page describes how to start your Openmoko development plan - how to prepare your development environment and use the tools provided to help test and share your programs.

[[Image:OpenmokoFramework08.png|center|450px]]

==Part I Choose your software development tool==
*[[System Developer]]
*[[Development Environment]]
*[[Java]]
*[[Development with Eclipse]]
*[[Python]]
*[[BitBake]]
*[[Qtopia_on_X11|Qtopia on X11]]
*[[Developing with C++ and Qt|C++ / Qt]]
===OS===
*[[Other OSes]]

==Part II Coding and compiling==

{{todo|The relationship between the below should be clarified. Now it looks like it's a choice between them, but I believe using the MokoMakefile will build all the points above it?}}

*[[Toolchain]]
*[[OpenEmbedded]]
**[[BitBake]]
*[[MokoMakeFile]]
*[[Application UI Design Recommendations]]

==Part III Running your program==

*[[Customizing the Openmoko Distribution]]

===Emulation===
*[[Automatic emulation in Ubuntu]]
*[[Host-based development with Xoo and Xephyr]]
*[[Running Openmoko on PC]]
*[[Test Openmoko Emulation with chroot image]]

==Part IV Sharing programs==

So you have just made this cool program, and wonder what will be an efficient way to share it ? Consider the following options:

* Adding a link in the [[Applications directory]] page.
* Creating a page on this wiki.
* Packaging for the [[Community Repository]].
* Hosting as a project on the [http://projects.openmoko.org/ Openmoko GForge]
* Entering a record on [http://freshmeat.net/ Freshmeat] or similar.
* Announcing on the [http://lists.openmoko.org/mailman/listinfo/community community mailing list].

See also

*[[Latest Images]]
*[[Users Repositories]]
*[[Distributions]]

==Part V Installation==
===Install===
*[[Package management]]
*[[How to run Openmoko Apps on PC]]
*[[Downloads]]
*[[Repositories ]]

===Image Flashing===
* [[MacOS X]]
* [[Flashing the Neo Freerunner]]
* [[Flashing the Neo 1973]]

==Part VI Tools used on Openmoko==

*[[U-boot|Bootloader]]
*[[Bootloader_commands|Bootloader Command]]
*[[Bootloader_environment|Bootloader Environment]]
*[http://www.denx.de/wiki/U-Boot/WebHome u-boot]
*[[Bootloader versions]]
*[[NetBSD]]
*[[Dfu-util]]

====Linux Core Services====
* [[Gsmd]]
*[[Alarm daemon]]
*[[Qpegps]]
*[[D-Bus]]
*[[Dbus device API]]
*[[Opkg]]
*[[QEMU command line]]
*[[Ompower]] Power management daemon
====Resources====
*[[Development resources]]

[[Category:Application Developer]]
[[Category:System Developers]]
[[Category:Community]]

Desktop wallpaper gallery

2008-10-08T20:15:46Z

Gromgull:

Openmoko-inspired wallpapers designs for your desktop systems.

Do you have nice openmoko-themed wallpaper? Please share it!

[[Image:gromgull wallpaper1.png|thumb|300px|center|SVG sources at http://www.dfki.uni-kl.de/~grimnes/2008/10/openmokowallpaper/]]
[[Image:gromgullwallpaper2.png|thumb|300px|center|SVG sources at http://www.dfki.uni-kl.de/~grimnes/2008/10/openmokowallpaper/]]

[[Image:Om-wallpaper-thumb.png|thumb|300px|center|For full sizes see http://lion.xaraya.hu/pictures/openmoko-wallpapers]]

[[Image:Om-wallpaper-circle-thumb.png|300px|center|thumb|For full sizes see http://lion.xaraya.hu/pictures/openmoko-wallpapers]]

[[Image:Om-choose-wallpaper-thumb.png‎|300px|center|thumb|For full sizes see http://lion.xaraya.hu/pictures/openmoko-wallpapers]]

[[Image:FreerunnerBlueprint1280x1024.png|300px|center|thumb|'' '''Blueprints'''. This image helps to design graphics to fit the FreeRunner display, both portrait and landscape, as well as other common display resolutions. 1280x1024 PNG file.'']]

== See also ==

* Effective wallpaper quality guidelines are explained in the [http://designinginterfaces.com/Deep_Background Deep Background] chapter of Jennifer Tidwell (2005) Designing Interfaces: Patterns for Effective Interaction Design.

[[category:Host OSes]]

File:Gromgullwallpaper2.png

2008-10-08T20:14:48Z

Gromgull: wallpaper added

wallpaper added

File:Gromgull wallpaper1.png

2008-10-08T20:14:16Z

Gromgull: uploaded a new version of "Image:Gromgull wallpaper1.png"

Wallpaper

File:Gromgull wallpaper1.png

2008-10-08T20:10:28Z

Gromgull: Wallpaper

Wallpaper

BitBake

2008-09-02T21:19:16Z

Gromgull:

{{Languages|BitBake}}
BitBake is the build tool used by [[OpenEmbedded]]. [[BitBake recipe]]s are simple, declarative files. Here is an example for the openmoko-calculator2 application:

DESCRIPTION = "A Calculator for Openmoko"
SECTION = "openmoko/tools"
DEPENDS = "libmokoui2"
PV = "0.1.0+svnr${SRCREV}"
PR = "r0"

inherit openmoko2

The user manual is available at the [http://bitbake.berlios.de/manual/ BitBake berlios page].

[[Category:Application Developer]]

Gsmd

2008-09-02T17:59:04Z

Gromgull:

{{Languages | Gsmd}}
[[gsmd]] is the [[GSM]] daemon running in background of an Openmoko phone, managing the traditional 'phone' parts (voice/sms/gprs communication links) of the phone.

Further technical details and API documentation in progress, is available [[Gsmd/document |here]].

Note that this does not hold for phones running [[Om_2008.8]] - then gsmd has been replaced with [[Qtopia]]'s mobile stack. Installing gsmd and related tools will conflict with qpe and things may not work.

== Usage ==

=== On the phone ===
gsmd is usually started as a background daemon when booting by the /etc/init.d/gsmd script, in this case gsmd outputs debug messages to the file "/tmp/gsm.log" (stdout and stderr is redirected there).

For debugging purposes gsmd can be run in foreground mode, options can be queried like:
<pre>
> gsmd --help
gsmd - (C) 2006 by Harald Welte <laforge@gnumonks.org>
This program is FREE SOFTWARE under the terms of GNU GPL

Usage:
-v --version Display program version
-d --daemon Deamonize
-h --help Display this help message
-p dev --device dev Specify serial device to be used
-s spd --speed spd Specify speed in bps (9600,38400,115200,...)
-F --hwflow Hardware Flow Control (RTS/CTS)
-L --leak-report Leak Report of talloc memory allocator
-l file --logfile file Specify a logfile to log to
</pre>

If your GSM modem is attached to ttySAC0 (like in the [[:Category:Neo1973 Hardware | Neo1973]]), invoke it as e.g.:
> gsmd -p /dev/ttySAC0 -s 115200 -F
(baud rate seems to be autodetected by the modem)

In order to kill the actual gsmd process and then run gsmd with a separate logfile and in background, but not as daemon:
> kill -SIGTERM `pidof gsmd`
and then to create a logfile with the date in the name
> gsmd -p /dev/ttySAC0 -s 115200 -F -l logs_gsmd-`date +%Y-%m-%d_%Hh%M` &

=== From host PC===
With recent [[uboot]] (svn > r2885), the gsm modem can be powered on and connected to uboot's serial console from uboot itself. Thus allowing the host PC to interact directly with the modem. Some notes about getting gsmd running in this manner is [[User:Miki/hosted_gsmd|here]].

== libgsmd ==

libgsmd is a library with C language API for application programs. Programs using this library can use the phone, e.g. make phone calls, receive incoming calls, register to the network, etc.

== libgsmd-tool ==

libgsmd-tool is a small demo application that can be used to demonstrate the usage of the libgsmd API.

== Usage ==

libgsmd-tool has multiple modes.

=== Usage of shell mode ===

Shell mode provides a simple text-based command interface for making voice calls.

The shell mode can be started using

libgsmd-tool -m shell

It can be used like in the following example:

<pre>
> src/util/libgsmd-tool -m shell
libgsm-tool - (C) 2006 by Harald Welte
This program is Free Software and has ABSOLUTELY NO WARRANTY

?
A Answer incoming call
D Dial outgoing number
H Hangup call
O Antenna Power On
o Antenna Power Off
gos Get Antenna Status
V Vibrator Enable (CVIB=1)
v Vibrator Disable (CVIB=0)
M Modem Power On
m Modem Power Off
r Register to network
R Register to given operator (R=number)
U Unregister from netowrk
P Print current operator
N Print current operator in numeric
L List available operators
Q Read signal quality
nr Query network registration
S Sleep (S[=second], default 5)
T Send DTMF Tone
n Print subscriber numbers
pd PB Delete (pb=index)
pr PB Read (pr=index)
prr PB Read Range (prr=index1,index2)
pf PB Find (pf=indtext)
pw PB Write (pw=index,number,text)
ps PB Support
pm PB Memory
pp PB Set Memory (pp=storage)
sd SMS Delete (sd=index,delflg)
sl SMS List (sl=stat)
sr SMS Read (sr=index)
ss SMS Send (ss=ask_ds,number,text|["text"])
sw SMS Write (sw=stat,number,text)
sm SMS Storage stats
sM SMS Set preferred storage (sM=mem1,mem2,mem3)
sc SMS Show Service Centre
sC SMS Set Service Centre (sC=number)
gvm Get Voicemail number
svm Set Voicemail number(svm=number)
im Get imsi
mf Get manufacturer
ml Get model
rv Get revision
sn Get serial number
cs Get Call status
gp Get PIN status
cbc Get Battery status
Rh Release all held calls (+CHLD=0)
UDUB User Determined User Busy (+CHLD=0)
Ra Release all active calls (+CHLD=1)
Rx Release specific active call x (Rx=x)(+CHLD=1x)
Ha Hold all active calls and accept held or waiting call (+CHLD=2)
Hx Hold all active calls except call x (Hx=x)(+CHLD=2x)
MP Add a held call to the conversation (+CHLD=3)
CFD Disable call forwarding (CFD=reason)
CFE Enable call forwarding (CFE=reason)
CFQ Query the status of call forwarding (CFQ=reason)
CFR Register call forwarding (CFR=reason,number)
CFe Erase a record of call forwarding (CFe=reason)
q Quit

O
# EVENT: PIN request (type=1) Please enter PIN: 6582
r
# EVENT: Netreg searching for network
EVENT: Netreg registered (home network)

D03024033902
# Dial 03024033902
EVENT: Call Progress: UNKNOWN
EVENT: Call Progress: PROCEED
EVENT: Call Progress: SYNC
EVENT: Call Progress: ALERT
H
# Hangup
EVENT: Call Progress: DISCONNECT
EVENT: Call Progress: RELEASE

EVENT: Incoming call type=2!
EVENT: Incoming call clip=`"03024033902"'
EVENT: Incoming call type=2!
A
# Answer
RSTR=`OK'
H
# Hangup
RSTR=`OK'
</pre>

=== Usage of atcmd mode ===

The atcmd mode is a passthrough-mode. Passthrough means that it accepts [[GSM 07.07]] commands, passes them through the daemon to the phone, and returns you the response. this is very useful for debugging.

The atcmd mode can be started using

libgsmd-tool -m atcmd

Usage is like in the following example:

<pre>
> src/util/libgsmd-tool -m atcmd
libgsm-tool - (C) 2006 by Harald Welte
This program is Free Software and has ABSOLUTELY NO WARRANTY

AT+CPAS
STR=`AT+CPAS'
RSTR=`+CPAS: 0'
AT+COPS=?
STR=`AT+COPS=?'
RSTR=`+COPS: (2,"E-Plus","E-Plus","26203"),(3,"o2 - de","o2 - de","26207"),(3,"Vodafone.de","Vodafone","26202"),(3,"T-Mobile D","TMO D","26201")'
</pre>

== Network related functions ==
Operator selection functions were implemented and merged into SVN head[http://lists.openmoko.org/pipermail/gsmd-devel/2007-September/000216.html]:

The new commands in libgsmd-util are as followings:
R - Register to given operator (R=number)
P - Print current operator
L - Detect available operators
Q - Read signal quality

This is implemented by the functions with "_opers_" naming.
== Currently missing ==

(please add items to this list if you're missing more features)

* Phone related functions
** Airplane mode / gsmd stop (this will be done outside gsmd, by using runlevels / upstart)
** Capability to set-up Emergency Calls, even if the device does not hold a SIM card
** obtain manufacturer/model/revision/IMEI
** Ability to notify user if the SIM card is locked (or even automagically unlock it?)

* SMS related features
** send SMS
** receive SMS
** obtain IMSI
** access to SIM-card stored SMS - ''No longer missing - see help''

* SIM related functions
** read phonebook entry - ''No longer missing - see help''
** write phonebook entry - ''No longer missing - see help''

* GPRS related functions - ''No longer missing - see [http://www.freesmartphone.org/index.php/Implementations/gsm0710muxd gsm0710muxd] for 07.10 multiplexing, and [https://wiki.muc.ccc.de/openmoko#gprs GPRS setup/de] for ppp via GPRS''
** set up GPRS link, use it via separate DLC of TS07.10 multiplex

* GSM clock related functions
** time output suitable for ntpd clock source?

* gsmd internal infrastructure
** fine-grained event subscriptions (rather than wildcard-subscribe)
** possibility to specify log-level from command line
** logfile re-opening on SIGUSR1 or SIGHUP (logrotate)
** permission handling
** d-bus interface

== Implementation Thoughts ==

== Testing framework ==

Emulating/mocking the firmware, gsmd and libgsmd can be tested for functionality; on any machine.
See [[User:Kero|Kero's page]] or go directly to [http://chmeee.dyndns.org/om/testing_gsmd.html the (lib)gsmd testing page].

== State tracking ==

gsmd needs to do apropriate state tracking of the underlying GSM hardware. For many of the state transition we only get events from the GSM Modem, but don't have apropriate query commands. Thus, assuming gsmd runs all the time, applications can come and go, but still have an idea about the current state of the modem, even if they missed the initial state transitions.

Also, gsmd state tracking allows us to allow for safer interoperability of multiple applications. If i.e. one applications has just started an outgoing call, gsmd can detect another application who intends to interfere with that and deny access

=== device power state ===

* modem completely off, not responding to AT commands
* modem responding to AT commands, but powered off (CFUN=0)
* modem responding to AT commands, in some power saving mode
* modem responding to AT commands, powered on, fully operational (CFUN=1)

=== Suspend power state ===

It must also configure the modem so that it can on appropriate events wake the system from sleep.

=== network registration state ===

* not registered to any network, not trying to register
* not registred to any network, searching/trying to register
* registered to home network (including cellID)
* registered to roaming network (including cellID)

=== ciphering indication state ===

* ciphering indications not supported by modem
* ciphering indications supported, but disabled in SIM
* ciphering indications supported, ciphering active
* ciphering indications supported, ciphering inactive

=== call state ===

* idle
* busy

Sources of gsmd are kept in [[Openmoko svn]] in src/target/gsm directory.

[[Category:Application Developer]]
[[Category:Implemented]]

Gsmd

2008-09-02T17:58:40Z

Gromgull:

{{Languages | Gsmd}}
[[gsmd]] is the [[GSM]] daemon running in background of an Openmoko phone, managing the traditional 'phone' parts (voice/sms/gprs communication links) of the phone.

Further technical details and API documentation in progress, is available [[Gsmd/document |here]].

Note that this does not hold for phones running [[Om_2008.08]] - then gsmd has been replaced with [[Qtopia]]'s mobile stack. Installing gsmd and related tools will conflict with qpe and things may not work.

== Usage ==

=== On the phone ===
gsmd is usually started as a background daemon when booting by the /etc/init.d/gsmd script, in this case gsmd outputs debug messages to the file "/tmp/gsm.log" (stdout and stderr is redirected there).

For debugging purposes gsmd can be run in foreground mode, options can be queried like:
<pre>
> gsmd --help
gsmd - (C) 2006 by Harald Welte <laforge@gnumonks.org>
This program is FREE SOFTWARE under the terms of GNU GPL

Usage:
-v --version Display program version
-d --daemon Deamonize
-h --help Display this help message
-p dev --device dev Specify serial device to be used
-s spd --speed spd Specify speed in bps (9600,38400,115200,...)
-F --hwflow Hardware Flow Control (RTS/CTS)
-L --leak-report Leak Report of talloc memory allocator
-l file --logfile file Specify a logfile to log to
</pre>

If your GSM modem is attached to ttySAC0 (like in the [[:Category:Neo1973 Hardware | Neo1973]]), invoke it as e.g.:
> gsmd -p /dev/ttySAC0 -s 115200 -F
(baud rate seems to be autodetected by the modem)

In order to kill the actual gsmd process and then run gsmd with a separate logfile and in background, but not as daemon:
> kill -SIGTERM `pidof gsmd`
and then to create a logfile with the date in the name
> gsmd -p /dev/ttySAC0 -s 115200 -F -l logs_gsmd-`date +%Y-%m-%d_%Hh%M` &

=== From host PC===
With recent [[uboot]] (svn > r2885), the gsm modem can be powered on and connected to uboot's serial console from uboot itself. Thus allowing the host PC to interact directly with the modem. Some notes about getting gsmd running in this manner is [[User:Miki/hosted_gsmd|here]].

== libgsmd ==

libgsmd is a library with C language API for application programs. Programs using this library can use the phone, e.g. make phone calls, receive incoming calls, register to the network, etc.

== libgsmd-tool ==

libgsmd-tool is a small demo application that can be used to demonstrate the usage of the libgsmd API.

== Usage ==

libgsmd-tool has multiple modes.

=== Usage of shell mode ===

Shell mode provides a simple text-based command interface for making voice calls.

The shell mode can be started using

libgsmd-tool -m shell

It can be used like in the following example:

<pre>
> src/util/libgsmd-tool -m shell
libgsm-tool - (C) 2006 by Harald Welte
This program is Free Software and has ABSOLUTELY NO WARRANTY

?
A Answer incoming call
D Dial outgoing number
H Hangup call
O Antenna Power On
o Antenna Power Off
gos Get Antenna Status
V Vibrator Enable (CVIB=1)
v Vibrator Disable (CVIB=0)
M Modem Power On
m Modem Power Off
r Register to network
R Register to given operator (R=number)
U Unregister from netowrk
P Print current operator
N Print current operator in numeric
L List available operators
Q Read signal quality
nr Query network registration
S Sleep (S[=second], default 5)
T Send DTMF Tone
n Print subscriber numbers
pd PB Delete (pb=index)
pr PB Read (pr=index)
prr PB Read Range (prr=index1,index2)
pf PB Find (pf=indtext)
pw PB Write (pw=index,number,text)
ps PB Support
pm PB Memory
pp PB Set Memory (pp=storage)
sd SMS Delete (sd=index,delflg)
sl SMS List (sl=stat)
sr SMS Read (sr=index)
ss SMS Send (ss=ask_ds,number,text|["text"])
sw SMS Write (sw=stat,number,text)
sm SMS Storage stats
sM SMS Set preferred storage (sM=mem1,mem2,mem3)
sc SMS Show Service Centre
sC SMS Set Service Centre (sC=number)
gvm Get Voicemail number
svm Set Voicemail number(svm=number)
im Get imsi
mf Get manufacturer
ml Get model
rv Get revision
sn Get serial number
cs Get Call status
gp Get PIN status
cbc Get Battery status
Rh Release all held calls (+CHLD=0)
UDUB User Determined User Busy (+CHLD=0)
Ra Release all active calls (+CHLD=1)
Rx Release specific active call x (Rx=x)(+CHLD=1x)
Ha Hold all active calls and accept held or waiting call (+CHLD=2)
Hx Hold all active calls except call x (Hx=x)(+CHLD=2x)
MP Add a held call to the conversation (+CHLD=3)
CFD Disable call forwarding (CFD=reason)
CFE Enable call forwarding (CFE=reason)
CFQ Query the status of call forwarding (CFQ=reason)
CFR Register call forwarding (CFR=reason,number)
CFe Erase a record of call forwarding (CFe=reason)
q Quit

O
# EVENT: PIN request (type=1) Please enter PIN: 6582
r
# EVENT: Netreg searching for network
EVENT: Netreg registered (home network)

D03024033902
# Dial 03024033902
EVENT: Call Progress: UNKNOWN
EVENT: Call Progress: PROCEED
EVENT: Call Progress: SYNC
EVENT: Call Progress: ALERT
H
# Hangup
EVENT: Call Progress: DISCONNECT
EVENT: Call Progress: RELEASE

EVENT: Incoming call type=2!
EVENT: Incoming call clip=`"03024033902"'
EVENT: Incoming call type=2!
A
# Answer
RSTR=`OK'
H
# Hangup
RSTR=`OK'
</pre>

=== Usage of atcmd mode ===

The atcmd mode is a passthrough-mode. Passthrough means that it accepts [[GSM 07.07]] commands, passes them through the daemon to the phone, and returns you the response. this is very useful for debugging.

The atcmd mode can be started using

libgsmd-tool -m atcmd

Usage is like in the following example:

<pre>
> src/util/libgsmd-tool -m atcmd
libgsm-tool - (C) 2006 by Harald Welte
This program is Free Software and has ABSOLUTELY NO WARRANTY

AT+CPAS
STR=`AT+CPAS'
RSTR=`+CPAS: 0'
AT+COPS=?
STR=`AT+COPS=?'
RSTR=`+COPS: (2,"E-Plus","E-Plus","26203"),(3,"o2 - de","o2 - de","26207"),(3,"Vodafone.de","Vodafone","26202"),(3,"T-Mobile D","TMO D","26201")'
</pre>

== Network related functions ==
Operator selection functions were implemented and merged into SVN head[http://lists.openmoko.org/pipermail/gsmd-devel/2007-September/000216.html]:

The new commands in libgsmd-util are as followings:
R - Register to given operator (R=number)
P - Print current operator
L - Detect available operators
Q - Read signal quality

This is implemented by the functions with "_opers_" naming.
== Currently missing ==

(please add items to this list if you're missing more features)

* Phone related functions
** Airplane mode / gsmd stop (this will be done outside gsmd, by using runlevels / upstart)
** Capability to set-up Emergency Calls, even if the device does not hold a SIM card
** obtain manufacturer/model/revision/IMEI
** Ability to notify user if the SIM card is locked (or even automagically unlock it?)

* SMS related features
** send SMS
** receive SMS
** obtain IMSI
** access to SIM-card stored SMS - ''No longer missing - see help''

* SIM related functions
** read phonebook entry - ''No longer missing - see help''
** write phonebook entry - ''No longer missing - see help''

* GPRS related functions - ''No longer missing - see [http://www.freesmartphone.org/index.php/Implementations/gsm0710muxd gsm0710muxd] for 07.10 multiplexing, and [https://wiki.muc.ccc.de/openmoko#gprs GPRS setup/de] for ppp via GPRS''
** set up GPRS link, use it via separate DLC of TS07.10 multiplex

* GSM clock related functions
** time output suitable for ntpd clock source?

* gsmd internal infrastructure
** fine-grained event subscriptions (rather than wildcard-subscribe)
** possibility to specify log-level from command line
** logfile re-opening on SIGUSR1 or SIGHUP (logrotate)
** permission handling
** d-bus interface

== Implementation Thoughts ==

== Testing framework ==

Emulating/mocking the firmware, gsmd and libgsmd can be tested for functionality; on any machine.
See [[User:Kero|Kero's page]] or go directly to [http://chmeee.dyndns.org/om/testing_gsmd.html the (lib)gsmd testing page].

== State tracking ==

gsmd needs to do apropriate state tracking of the underlying GSM hardware. For many of the state transition we only get events from the GSM Modem, but don't have apropriate query commands. Thus, assuming gsmd runs all the time, applications can come and go, but still have an idea about the current state of the modem, even if they missed the initial state transitions.

Also, gsmd state tracking allows us to allow for safer interoperability of multiple applications. If i.e. one applications has just started an outgoing call, gsmd can detect another application who intends to interfere with that and deny access

=== device power state ===

* modem completely off, not responding to AT commands
* modem responding to AT commands, but powered off (CFUN=0)
* modem responding to AT commands, in some power saving mode
* modem responding to AT commands, powered on, fully operational (CFUN=1)

=== Suspend power state ===

It must also configure the modem so that it can on appropriate events wake the system from sleep.

=== network registration state ===

* not registered to any network, not trying to register
* not registred to any network, searching/trying to register
* registered to home network (including cellID)
* registered to roaming network (including cellID)

=== ciphering indication state ===

* ciphering indications not supported by modem
* ciphering indications supported, but disabled in SIM
* ciphering indications supported, ciphering active
* ciphering indications supported, ciphering inactive

=== call state ===

* idle
* busy

Sources of gsmd are kept in [[Openmoko svn]] in src/target/gsm directory.

[[Category:Application Developer]]
[[Category:Implemented]]

Gsmd

2008-09-02T17:58:24Z

Gromgull:

{{Languages | Gsmd}}
[[gsmd]] is the [[GSM]] daemon running in background of an Openmoko phone, managing the traditional 'phone' parts (voice/sms/gprs communication links) of the phone.

Further technical details and API documentation in progress, is available [[Gsmd/document |here]].

Note that this does not hold for phones running [[Om2008.08]] - then gsmd has been replaced with [[Qtopia]]'s mobile stack. Installing gsmd and related tools will conflict with qpe and things may not work.

== Usage ==

=== On the phone ===
gsmd is usually started as a background daemon when booting by the /etc/init.d/gsmd script, in this case gsmd outputs debug messages to the file "/tmp/gsm.log" (stdout and stderr is redirected there).

For debugging purposes gsmd can be run in foreground mode, options can be queried like:
<pre>
> gsmd --help
gsmd - (C) 2006 by Harald Welte <laforge@gnumonks.org>
This program is FREE SOFTWARE under the terms of GNU GPL

Usage:
-v --version Display program version
-d --daemon Deamonize
-h --help Display this help message
-p dev --device dev Specify serial device to be used
-s spd --speed spd Specify speed in bps (9600,38400,115200,...)
-F --hwflow Hardware Flow Control (RTS/CTS)
-L --leak-report Leak Report of talloc memory allocator
-l file --logfile file Specify a logfile to log to
</pre>

If your GSM modem is attached to ttySAC0 (like in the [[:Category:Neo1973 Hardware | Neo1973]]), invoke it as e.g.:
> gsmd -p /dev/ttySAC0 -s 115200 -F
(baud rate seems to be autodetected by the modem)

In order to kill the actual gsmd process and then run gsmd with a separate logfile and in background, but not as daemon:
> kill -SIGTERM `pidof gsmd`
and then to create a logfile with the date in the name
> gsmd -p /dev/ttySAC0 -s 115200 -F -l logs_gsmd-`date +%Y-%m-%d_%Hh%M` &

=== From host PC===
With recent [[uboot]] (svn > r2885), the gsm modem can be powered on and connected to uboot's serial console from uboot itself. Thus allowing the host PC to interact directly with the modem. Some notes about getting gsmd running in this manner is [[User:Miki/hosted_gsmd|here]].

== libgsmd ==

libgsmd is a library with C language API for application programs. Programs using this library can use the phone, e.g. make phone calls, receive incoming calls, register to the network, etc.

== libgsmd-tool ==

libgsmd-tool is a small demo application that can be used to demonstrate the usage of the libgsmd API.

== Usage ==

libgsmd-tool has multiple modes.

=== Usage of shell mode ===

Shell mode provides a simple text-based command interface for making voice calls.

The shell mode can be started using

libgsmd-tool -m shell

It can be used like in the following example:

<pre>
> src/util/libgsmd-tool -m shell
libgsm-tool - (C) 2006 by Harald Welte
This program is Free Software and has ABSOLUTELY NO WARRANTY

?
A Answer incoming call
D Dial outgoing number
H Hangup call
O Antenna Power On
o Antenna Power Off
gos Get Antenna Status
V Vibrator Enable (CVIB=1)
v Vibrator Disable (CVIB=0)
M Modem Power On
m Modem Power Off
r Register to network
R Register to given operator (R=number)
U Unregister from netowrk
P Print current operator
N Print current operator in numeric
L List available operators
Q Read signal quality
nr Query network registration
S Sleep (S[=second], default 5)
T Send DTMF Tone
n Print subscriber numbers
pd PB Delete (pb=index)
pr PB Read (pr=index)
prr PB Read Range (prr=index1,index2)
pf PB Find (pf=indtext)
pw PB Write (pw=index,number,text)
ps PB Support
pm PB Memory
pp PB Set Memory (pp=storage)
sd SMS Delete (sd=index,delflg)
sl SMS List (sl=stat)
sr SMS Read (sr=index)
ss SMS Send (ss=ask_ds,number,text|["text"])
sw SMS Write (sw=stat,number,text)
sm SMS Storage stats
sM SMS Set preferred storage (sM=mem1,mem2,mem3)
sc SMS Show Service Centre
sC SMS Set Service Centre (sC=number)
gvm Get Voicemail number
svm Set Voicemail number(svm=number)
im Get imsi
mf Get manufacturer
ml Get model
rv Get revision
sn Get serial number
cs Get Call status
gp Get PIN status
cbc Get Battery status
Rh Release all held calls (+CHLD=0)
UDUB User Determined User Busy (+CHLD=0)
Ra Release all active calls (+CHLD=1)
Rx Release specific active call x (Rx=x)(+CHLD=1x)
Ha Hold all active calls and accept held or waiting call (+CHLD=2)
Hx Hold all active calls except call x (Hx=x)(+CHLD=2x)
MP Add a held call to the conversation (+CHLD=3)
CFD Disable call forwarding (CFD=reason)
CFE Enable call forwarding (CFE=reason)
CFQ Query the status of call forwarding (CFQ=reason)
CFR Register call forwarding (CFR=reason,number)
CFe Erase a record of call forwarding (CFe=reason)
q Quit

O
# EVENT: PIN request (type=1) Please enter PIN: 6582
r
# EVENT: Netreg searching for network
EVENT: Netreg registered (home network)

D03024033902
# Dial 03024033902
EVENT: Call Progress: UNKNOWN
EVENT: Call Progress: PROCEED
EVENT: Call Progress: SYNC
EVENT: Call Progress: ALERT
H
# Hangup
EVENT: Call Progress: DISCONNECT
EVENT: Call Progress: RELEASE

EVENT: Incoming call type=2!
EVENT: Incoming call clip=`"03024033902"'
EVENT: Incoming call type=2!
A
# Answer
RSTR=`OK'
H
# Hangup
RSTR=`OK'
</pre>

=== Usage of atcmd mode ===

The atcmd mode is a passthrough-mode. Passthrough means that it accepts [[GSM 07.07]] commands, passes them through the daemon to the phone, and returns you the response. this is very useful for debugging.

The atcmd mode can be started using

libgsmd-tool -m atcmd

Usage is like in the following example:

<pre>
> src/util/libgsmd-tool -m atcmd
libgsm-tool - (C) 2006 by Harald Welte
This program is Free Software and has ABSOLUTELY NO WARRANTY

AT+CPAS
STR=`AT+CPAS'
RSTR=`+CPAS: 0'
AT+COPS=?
STR=`AT+COPS=?'
RSTR=`+COPS: (2,"E-Plus","E-Plus","26203"),(3,"o2 - de","o2 - de","26207"),(3,"Vodafone.de","Vodafone","26202"),(3,"T-Mobile D","TMO D","26201")'
</pre>

== Network related functions ==
Operator selection functions were implemented and merged into SVN head[http://lists.openmoko.org/pipermail/gsmd-devel/2007-September/000216.html]:

The new commands in libgsmd-util are as followings:
R - Register to given operator (R=number)
P - Print current operator
L - Detect available operators
Q - Read signal quality

This is implemented by the functions with "_opers_" naming.
== Currently missing ==

(please add items to this list if you're missing more features)

* Phone related functions
** Airplane mode / gsmd stop (this will be done outside gsmd, by using runlevels / upstart)
** Capability to set-up Emergency Calls, even if the device does not hold a SIM card
** obtain manufacturer/model/revision/IMEI
** Ability to notify user if the SIM card is locked (or even automagically unlock it?)

* SMS related features
** send SMS
** receive SMS
** obtain IMSI
** access to SIM-card stored SMS - ''No longer missing - see help''

* SIM related functions
** read phonebook entry - ''No longer missing - see help''
** write phonebook entry - ''No longer missing - see help''

* GPRS related functions - ''No longer missing - see [http://www.freesmartphone.org/index.php/Implementations/gsm0710muxd gsm0710muxd] for 07.10 multiplexing, and [https://wiki.muc.ccc.de/openmoko#gprs GPRS setup/de] for ppp via GPRS''
** set up GPRS link, use it via separate DLC of TS07.10 multiplex

* GSM clock related functions
** time output suitable for ntpd clock source?

* gsmd internal infrastructure
** fine-grained event subscriptions (rather than wildcard-subscribe)
** possibility to specify log-level from command line
** logfile re-opening on SIGUSR1 or SIGHUP (logrotate)
** permission handling
** d-bus interface

== Implementation Thoughts ==

== Testing framework ==

Emulating/mocking the firmware, gsmd and libgsmd can be tested for functionality; on any machine.
See [[User:Kero|Kero's page]] or go directly to [http://chmeee.dyndns.org/om/testing_gsmd.html the (lib)gsmd testing page].

== State tracking ==

gsmd needs to do apropriate state tracking of the underlying GSM hardware. For many of the state transition we only get events from the GSM Modem, but don't have apropriate query commands. Thus, assuming gsmd runs all the time, applications can come and go, but still have an idea about the current state of the modem, even if they missed the initial state transitions.

Also, gsmd state tracking allows us to allow for safer interoperability of multiple applications. If i.e. one applications has just started an outgoing call, gsmd can detect another application who intends to interfere with that and deny access

=== device power state ===

* modem completely off, not responding to AT commands
* modem responding to AT commands, but powered off (CFUN=0)
* modem responding to AT commands, in some power saving mode
* modem responding to AT commands, powered on, fully operational (CFUN=1)

=== Suspend power state ===

It must also configure the modem so that it can on appropriate events wake the system from sleep.

=== network registration state ===

* not registered to any network, not trying to register
* not registred to any network, searching/trying to register
* registered to home network (including cellID)
* registered to roaming network (including cellID)

=== ciphering indication state ===

* ciphering indications not supported by modem
* ciphering indications supported, but disabled in SIM
* ciphering indications supported, ciphering active
* ciphering indications supported, ciphering inactive

=== call state ===

* idle
* busy

Sources of gsmd are kept in [[Openmoko svn]] in src/target/gsm directory.

[[Category:Application Developer]]
[[Category:Implemented]]

Group sales

2008-04-29T11:35:53Z

Gromgull:

Openmoko have announced a scheme to sell the forthcoming Neo Freerunner at a discount if bought in multiples of 10 (US$369, instead of 399), to be shipped in one package. Group buying will thus save money on the purchase, and on the shipping. This page is to to organise group purchases by region.

Steve from Openmoko announced "Every 10 pack, will come with a box of stuff. 10 pouches and 10 head sets."
So join us within a local group !

<div style='float:right'>__TOC__</div>

== Australia ==
=== Western Australia ===
==== Perth ====

* Fred Janon mailto:fjanon@yahoo.com

=== New South Whales ===
==== Sydney ====
status: 5/10

* 1X dbmoodb ---> [http://wiki.openmoko.org/wiki/Special:Emailuser/Dbmoodb contact me here]
* 1 x Mark Chandler [http://wiki.openmoko.org/wiki/Special:Emailuser/Openmarko contact me here]
* 1 x bing [http://wiki.openmoko.org/wiki/Special:Emailuser/Bingquick contact me here]
* 1 x ch0gan [http://wiki.openmoko.org/wiki/Special:Emailuser/ch0gan contact me here]
* 1 x Neil Brown [http://wiki.openmoko.org/wiki/Special:Emailuser/Neilbrown contact me here]

=== Victoria ===
==== Melbourne ====
Status: 4/10

* 4x Dennis Wollersheim, mailto: dewoller (at) gmail (dot) com

=== ACT ===
==== Canberra ====
Status: 1/10

* J Dinale [http://wiki.openmoko.org/wiki/Special:Emailuser/Noledil Contact me here]

=== Queensland ===
==== Brisbane ====
Status: 3/10 (possibly 20)

* Nick Devereaux x 2 [http://wiki.openmoko.org/wiki/Special:Emailuser/Monkeypanic Contact me here]
* Matt Gallagher [http://wiki.openmoko.org/wiki/Special:Emailuser/mattg Contact me here]

== Austria ==
There is a group-buy page at MetaLab, available here: http://metalab.at/wiki/OpenMoko .. we almost have the full 10 slots assigned, and its quite possible that we will order *20* phones, so please register on the Metalab pages and let us know if you're interested ..

=== Salzburg ===
Status: 1/10

* D. Kepplinger [http://wiki.openmoko.org/wiki/Special:Emailuser/Wedge Contact me here]
=== Wien ===
Status: 1/10
* M. Greifeneder [http://wiki.openmoko.org/wiki/Special:Emailuser/mikegr Contact me here]
* J. Vaughan (torpor) -- http://metalab.at/wiki/OpenMoko [http://wiki.openmoko.org/wiki/Special:Emailuser/torpor Contact me here]

=== Styria ===
==== Graz ====
Status: 6/10

* F Hackenberger [http://wiki.openmoko.org/wiki/Special:Emailuser/Deadman66 Contact me here]
* J Florineth [http://wiki.openmoko.org/wiki/Special:Emailuser/Flojoh Contact me here]
* G Michelitsch [http://wiki.openmoko.org/wiki/Special:Emailuser/graf_ithaka Contact me here] (I've found others @ TU Graz !)
* R Stoegbuchner [http://wiki.openmoko.org/wiki/Special:Emailuser/stoero Contact me here]
* M Lipp [http://wiki.openmoko.org/wiki/Special:Emailuser/Neldoreth Contact me here]
* M Maier [http://wiki.openmoko.org/wiki/Special:Emailuser/species Contact me here]

== Belgium ==
=== Flanders ===
==== Brussel/Aalst/Gent/Brugge ====
Status 7/10
* Yorick, mailto: yorick DOT matthys AT gmail DOT com
* 2x Dolfje [http://wiki.openmoko.org/wiki/Special:Emailuser/Dolfje Contact me here]
* XVens, mailto: xavier DOT vens AT gmail DOT com
* Arno85, mailto: aaron DOT helin AT gmail DOT com, Kortrijk
* Philoufr, mailto: philoufr AT gmail DOT com
* Js Op de Beeck [http://wiki.openmoko.org/wiki/Special:Emailuser/Js.opdebeeck Contact me here]
ps: Dolfje can bring freerunners to Brugge if needed

==== Antwerp ====
Status 5/10

* michielv [http://wiki.openmoko.org/wiki/Special:Emailuser/Michielv Contact me here]
* Peter N [http://wiki.openmoko.org/wiki/Special:Emailuser/Bubsy Contact me here]
* Ivo [http://wiki.openmoko.org/wiki/Special:Emailuser/Ivo Contact me here]
* Peter Leemans, mailto: peter AT x-tend DOT be
* Richard B [http://wiki.openmoko.org/wiki/Special:Emailuser/richardb Contact me here]

== Bulgaria ==
=== Sofia ===
==== Sofia ====
Status : 2/10

* Dimitar Staykov, mailto:meditache@gmail.com
* Vernim, [http://wiki.openmoko.org/wiki/Special:Emailuser/Vernim Contact]

== Canada ==

=== British Columbia ===
Status : 8/10

* Justin (Vancouver): mailto: stryderjzw AT gmail
* Dave (Vancouver) Vancouver Linux users group (unconfirmed but about 7 so far): mailto: doc AT skynet REMOVE dot REMOVE ie

=== Alberta ===
Status : 3/10

* [[User:Wuth|Wuth]] : [mailto:wuth@acm.org]
* [[User:Slm3095om|stacy]] (2 units) : slm3095om AT millions dOt ca

=== Ontario/Quebec ===
==== GTA (Toronto) ====
Status : 10/10

* Gerald A [http://wiki.openmoko.org/wiki/Special:Emailuser/Historybuff Contact me here]
* MattC, mailto: quirkz AT gmail
* Sergey K, openmoko AT deeptown dOt org
* Peter Baldwin, vendor.openmoko AT pointclark DOT net (3 units)
* Kristin Low, kristin dot low at gmail dot com (Kingston)
* Daniel Lister, dan.lister-->gmail
* Ronnie Wong: 3 units - r25wong AT ryerson dOT ca
* Paul V [http://wiki.openmoko.org/wiki/Special:Emailuser/Roju Contact me here]

Group 2 Status: 1/10

* Gabriel D - ace AT staticwave DOT ca

== Chile ==
=== Santiago ===
Status : 2/10

* [[User:Mankeke]] Ricardo Manríquez C., mailto: ricardo.manriquez "remove this and add AT" gmail "dot" com
* [[User:XKnightmareX]] Gonzalo Pesenti., mailto: mare.knight1 "remove this and add AT" gmail "dot" com

== Denmark ==
If we do not reach a total large enough, Denmark **is** a very small place - surely we could figure out a way of getting them to find their way 'round the country :)

=== Jutland ===
==== Aalborg ====
Status: 3/10

Should anyone need it, transportation from Aalborg to Thisted for phones can be arranged, if you don't want to pick it up in Aalborg yourself :) ~~leinir

* Dan Leinir Turthra Jensen mailto:admin@leinir.dk [[User:Leinir]]
* Fabian Olesen mailto:firewalkerx@gmail.com
* Helge Willum Larsen mailto:helge.at.helges.dk

==== Skjern ====
Status: 1/10

* [[User:Carlo]]

=== Fyn ===
Status: 2/10

* [[User:EsbenDamgaard]]
* [[User:apm]]

=== Sjælland ===
==== Copenhagen ====
Status: 22/10

* [[User:Fursund]]
* [[User:Rasmusjensen]]
* [[User:tabac]] Thomas Ammitzbøll-Bach
* [[User:UlrikRasmussen | Ulrik Rasmussen]]
* [[User:KlaymenDK | Jan Gundtofte-Bruun]] (Pending final hw, eg. low-power LEDs)
* [[User:OleTange | Ole Tange]] (I need 14 with invoice)
* [[User:Pascal | Pascal d'Hermilly]] (I need 1 with invoice)
* [[User:Miwer]] Michael Andersen
* M. Stenderup [http://wiki.openmoko.org/wiki/Special:Emailuser/Mast contact me here]

== Finland ==
=== Uusimaa ===
==== Helsinki I (Full)====
Status : 10/10

* Mikko Rauhala x2 [mailto:mjr@iki.fi mjr@iki.fi]
* Aleksi Hankalahti [mailto:aleksi.hankalahti@iki.fi aleksi.hankalahti@iki.fi]
* Seppo Hätönen [mailto:karrde@iki.fi karrde@iki.fi]
* Arttu Sund [mailto:thearttu@gmail.com thearttu@gmail.com]
* Ville-Pekka Vainio vpivaini AT cs.helsinki.fi
* Heikki Hallamaa [mailto:heikki.hallamaa@iki.fi heikki.hallamaa@iki.fi]
* Tomi Jylhä-Ollila tomi.jylha-ollila@helsinki.fi
* Richard Braakman
* Timo Jyrinki [mailto:timo.jyrinki@iki.fi timo.jyrinki@iki.fi]

==== Helsinki II ====
Status : 5/10

* [[User:Piksi]] openmoko ÄT pi-xi PISTE net ''(i'll post more info on my userpage when the group is full)''
* Risto H. Kurppa risto AT kurppa DOT fi
* Aapo Rantalainen aapo DOT rantalainen AT gmail DOT com
* Matti Laakso matti DOT laakso AT kotiposti DOT net
* Ismo Haanaho ismo DOT haanaho AT gmail DOT com

=== Varsinais-Suomi ===
==== Turku ====
Status : 3/10

* 2x Teemu Välimäki, [mailto:teemu.valimaki@iki.fi teemu.valimaki@iki.fi]

* Jaakko Lehtinen, jaakko dot lehtinen at gmail dot com

== France ==
=== Bretagne ===
==== Brest ====
Status : 1/10

* StevenLeRoux [mailto:steven@pourri.fr steven@pourri.fr] Jabber_Id:Steven@jabber.fr
* Acheteur potentiel #2

==== Rennes ====
Status : 2/10

* Cédric DUFOUIL (openmoko at tsleg point com)
* Yves MAHE (ymahe at zindep dot com)

=== Ile de france ===
==== Paris ====
Status : 9/10

* StevenLeRoux
* [[User:Phyce|Phyce]]
* Yann SLADEK
* [[User:Wilk|Wilk]] [http://wiki.openmoko.org/wiki/Special:Emailuser/Wilk Contact me here]
* Jonathan Magano ([http://wiki.openmoko.org/wiki/Special:Emailuser/JonathanMM Contact me here])
* Benjamin Renard (bn8[AT]zionetrix.net)
* [[User:OlivierBerger|OlivierBerger]]
* [[User:BartGS|BartGS]] [http://wiki.openmoko.org/wiki/Special:Emailuser/BartGS Contact me here]
* [[User:rcoscali|Rémi Cohen-Scali]]

You may also see :
http://bearstech.com/openmoko/register

=== Pays de la Loire ===
==== La Roche sur Yon ====
Status : 1/10

* [http://wiki.openmoko.org/wiki/Special:Emailuser/Vtouchar Vincent Touchard] (I may soon move to Bretagne/Brest)

=== Rhône-Alpes ===
==== Lyon ====
Status : 2/10

* [http://wiki.openmoko.org/wiki/Special:Emailuser/patou Vincent MEURISSE]
* [http://wiki.openmoko.org/wiki/Special:Emailuser/pini Gilles FILIPPINI]

==== Grenoble ====
Status : 1/10

* [http://wiki.openmoko.org/wiki/Special:Emailuser/pbollard Philippe BOLLARD]

=== Provence Alpes Cote d'Azur ===
==== Sophia Antipolis ====
Status : 1/10

* [http://wiki.openmoko.org/wiki/Special:Emailuser/nico.inc Nicolas HUOT]

== Germany ==
=== Sachsen-Anhalt ===
==== Stendal (evtl. Magdeburg) ====
Status 1/10

* Fabian Off [http://wiki.openmoko.org/wiki/Special:Emailuser/Fabian2de Contact me here]

=== Hamburg ===
==== Hamburg ====
Status 9-10

* Jan 4-5[http://wiki.openmoko.org/wiki/Special:Emailuser/Jan07 Contact me here]
* Varacanero [http://wiki.openmoko.org/wiki/Special:Emailuser/varacanero Contact me here]
* Ole 3-5 pcs [http://wiki.openmoko.org/wiki/Special:Emailuser/Olemoko Contact me here]

=== Sachsen ===
==== Chemnitz ====
Status 1/10

* Tobias [http://wiki.openmoko.org/wiki/Special:Emailuser/Tobydox Contact me here]

=== Thueringen ===
==== Weimar ====
Status 1/10

* [[User:Fries43]]

=== NRW ===
==== Bielefeld ====
Status 4/10

* David, infos on my [[User:Raven|user page]], or you can [[Special:Emailuser/Raven|contact me here]]
* Sebastian, infos on my [[User:Seppi|user page]], or you can [[Special:Emailuser/Seppi|contact me here]]
* Dackel, infos on my [[User:Killerdackel|user page]], or you can [[Special:Emailuser/Killerdackel|contact me here]]
* Conny
* Arndt, infos on my [[User:Arndot|user page]], or you can [[Special:Emailuser/Arndot|contact me here]]

==== Aachen ====
Status 2/10
* Henrik, infos on my [[User:Henrikz|user page]], or you can [[Special:Emailuser/Henrikz|contact me here]]
* David, infos on my [[User:TechnoFan|user page]], or you can [[Special:Emailuser/TechnoFan|contact me here]]

==== Düsseldorf ====
* mac2k, infos on my [[User:mac2k|user page]], or you can [[Special:Emailuser/mac2k|contact me here]]

=== Baden-Württemberg ===
==== Karlsruhe ====

Status 8/10

* 2 for André (one for me and one for a friend), you can [[Special:Emailuser/Spacemarine|contact me here]]
* [[Special:Emailuser/Dr.Nop|Dr.Nop]]
* [[Special:Emailuser/JensB|JensB]]
* [[Special:Emailuser/Tedo|Tedo]]
* 3 devices at least, [[Special:Emailuser/ZaPPaS|ZaPPaS]]

* [[Special:Emailuser/Gromgull|Gromgull]] (in Kaiserslautern, but Karlsruhe is close enough, and I doubt that I'll find 10 people here.

=== Bayern ===
==== München ====

Status 1/10

* [[Special:Emailuser/Eriks|Eriks]]

=== Berlin===
==== Berlin ====

for berlin-talk: http://de.groups.yahoo.com/group/openmoko-berlin/

* first member of new group

This group has finished its forming:
Status 10/10
* Stephan [http://wiki.openmoko.org/wiki/User:Fischel Contact me here]
* Robert [http://wiki.openmoko.org/wiki/User:Thebohemian Contact me here]
* Nico [http://wiki.openmoko.org/wiki/User:Nico Contact me here]
* Torsten [http://wiki.openmoko.org/wiki/User:Torsten_Grote Contact me here]
* Bastian [[User:Fries43]]
* Sven-Ola [http://wiki.openmoko.org/wiki/User:Sven-ola Contact]
* Arne [http://wiki.openmoko.org/wiki/User:arnepp Contact me here]
* MM [http://wiki.openmoko.org/wiki/User:MM Contact]
* Keks [http://wiki.openmoko.org/wiki/User:Keksdosenmann Contact]
* Matthias [http://wiki.openmoko.org/wiki/User:mk Contact]

== Italy ==
If we don't reach the 10 phones limit in each city, maybe we could place an order in the "most requested city", and from shipping to other buyers. We'll have anyway a good discount although the "double-shipping". ([http://thread.gmane.org/gmane.comp.handhelds.openmoko.community/10937/focus=10981 Read here for reference]).

=== Toscana ===
==== Firenze (e dintorni) ====
Status 2/10

* [[User:Treviño|Marco Trevisan (Treviño)]] - [http://blog.3v1n0.net/contatti-trevino/ Contacts here]
* [[User:Niccolo|Niccolo Rigacci]] - ''niccolo [AT] rigacci.org''
* [[User:pcav|Paolo Cavallini]] - ''cavallini [AT] faunalia.it''
* [[User:BiggMatt|Mattia Gentile]] - ''biggmatt@hotmail.it''

=== Lombardia ===

==== Milano e dintorni ====
Status 12/10

* Marco Crociani - [http://wiki.openmoko.org/wiki/Special:Emailuser/Tyrael Contacts here]
* Marcello Gorla
* Maxxer [mailto:maxxer@yetopen.it maxxer@yetopen.it] (Lecco)
* Pietro Montorfano [mailto:monto84@gmail.com monto84@gmail.com] (from como)
* Gianluigi Belli - [http://wiki.openmoko.org/wiki/Special:Emailuser/Pulciux Contacts here] (Milano)
* Michele Castellano - [http://wiki.openmoko.org/wiki/Special:Emailuser/mubumba Contacts here] (Milano)
* Maurizio Lipreri - [http://wiki.openmoko.org/wiki/Special:Emailuser/Maldido Contacts here]( Como )
* Guido Conaldi - [http://wiki.openmoko.org/wiki/Special:Emailuser/skepz Contacts here] (Varese)
* Christian [mailto:christian.marzola@alice.it] (ferrara)
* [[User:Furester|Igor Scabini (furester)]] -[http://wiki.openmoko.org/wiki/Special:Emailuser/Furester Contacts here] (Milano)
* Dario Panico (sempre che la cosa sia possibile, #11) [http://wiki.openmoko.org/wiki/Special:Emailuser/Dareus Contacts here] (Busto Arsizio, VA)
* Marco Zanzotera (Milano città) - qualcuno sa indicarmi i metodi di pagamento per favore?

=== Piemonte ===
==== Torino (and province) ====
Status 2/10

* Claudio Carnino (jollyr0g3r AT gmail DOT com)
* Alessandro Degano (a.degano AT gmail DOT com)

=== Trentino-Alto Adige ===
==== Trento (Padova too :)) ====
Status 1/10

* Andrea Debortoli (debortoland AT gmail DOT com)

=== Friuli Venezia Giulia ===
==== Trieste ====
Status: 1/10

* dorje [mailto:dorje@libero.it dorje@libero.it] - [[User:dorje|dorje]]

=== Veneto ===
Status: 4/10

==== Verona ====

* Persegat [mailto:persegat@alice.it persegat@alice.it] - [[User:Pecce|Pecce]]

==== Vicenza ====

* Matteo [mailto:matteo@member.fsf.org matteo@member.fsf.org] - [[User:Tchernobog|Tchernobog]] Also Padova is okay.

==== Venezia ====

* Tommaso [mailto:tommaso.gardumi@gmail.com tommaso.gardumi@gmail.com] - [[User:Tobarello|Tobarello]] Also Padova, Vicenza & Trento are ok.

==== Treviso ====

* Dario [mailto:aliasbrain@gmail.com aliasbrain(at)gmail.com] - [[User:Rastafan|Rastafan]] one, maybe two.

* Pedro [mailto:paguilar@junkerhq.net paguilar(at)junkerhq.net] - [[User:Paguilar|Paguilar]] Also Padova and Vicenza are ok.

=== Emilia Romagna ===
==== Parma ====
Status : 1/10

* [[User:Delian|Marco Albanese]] [mailto:delian2@gmail.com delian2@gmail.com] For Me, it's ok for the decentralized shipment ( Milano for example :) ).

=== Puglia ===
==== Lecce ====
Status : 1/10

* [[User:Morpheus90|Morpheus90]] [mailto:ugopiemontese@rudiaelinux.com ugopiemontese@rudiaelinux.com]
==== Bari ====
Status : 2/10

* [[User:Fradeve11|Fradeve11]] [mailto:fradeve@ubuntu-it.org fradeve@ubuntu-it.org]

=== Campania ===
==== Caserta (and province) ====
Status 1/10

* fenoxxx [mailto:fenoxxx@gmail.com] - Aversa

=== Lazio ===
==== Roma ====
Status 5/10

* Hire X 2 [mailto:hiretto@gmail.com hiretto@gmail.com] (Roma)
* Darkbasic X 1 (Ancona)
* zione X 1 [mailto:alessio.filipponio@gmail.com alessio.filipponio@gmail.com](Roma)
* AntoMan X 1 (Roma)

=== Liguria ===
==== Genova ====
Status 1/10

* Luca Maranzano X 1 (liuk AT linux DOT it) [[User:liuk|liuk]]

=== Sicilia ===
==== Palermo ====
Status 2/10

* Giorgio Marciano' X 1 [mailto:giorgio.marciano@email.it giorgio.marciano@email.it]
* Michele Puccio X 1 [mailto:puccio@eng.it michele]

== Macedonia ==
=== Skopje ===
* Kristijan Krsteski 1/10 [[User:neutrino]] [mailto:kristijan.krsteski@gmail.com]
===Status ===
1/10

== México ==
=== Ciudad de México ===
* Kozapatista [[Special:Emailuser/User:kozapatista|Contact]]
===Status ===
1/10

== [http://wiki.openmoko.org/wiki/Talk:GroupSales#The_Netherlands The Netherlands] ==
(Discuss this group sale on the [http://wiki.openmoko.org/wiki/Talk:GroupSales#The_Netherlands talk page])

* Marijn Kruisselbrink 1 [[Special:Emailuser/User:mkruisselbrink|Contact]]
* Andy Powell 1/10 [[Special:Emailuser/User:ScaredyCat|Contact]]
* Arjan Veenstra 1/10 [[User:AVee]] [[Special:Emailuser/User:AVee|Contact]]

=== Gelderland ===

==== Nijmegen ====
* [[User:A.dre|André Disselhorst]] (Nijmegen 1x) [[Special:Emailuser/User:A.dre|Contact]]

=== Limburg ===

==== Griendtsveen ====
* [[User:KenSentMe|Jeroen van de Nieuwenhof]] (Griendtsveen 1x) [[Special:Emailuser/User:KenSentMe|Contact]]

=== Noord-Brabant ===

==== Bergen op Zoom ====
* [[User:Madjo|Marcel de Jong]] 1/10 [[Special:Emailuser/User:Madjo|Contact]]

==== Eindhoven ====
* Christ van Willegen 1 [[User:ChristW]]

=== Noord Holland ===

==== Amsterdam ====
* Michel van Horssen 1/10 [[Special:Emailuser/User:mivaho|Contact]]
* Frank Richter 1 [[Special:Emailuser/User:res|Contact]]
* Eric Smith 1/10 [[User:Eric Smith]]

==== Bussum ====
* Remco van Zuijlen 1x [[Special:Emailuser/User:Remco|Contact]]

=== Overijssel ===

==== Deventer ====
* Jan de Haan 1/10 [[User:Jan de Haan]] [[Special:Emailuser/User:Jan de Haan|Contact]]

==== Hengelo ====
* Sander Hoentjen 1/10 [[Special:Emailuser/User:Tjikkun|Contact]]
* Peter Hageman 1 [[Special:Emailuser/User:PingPong|Contact]]

==== Zwolle ====
* Boudewijn 1/10 [[User:Boudewijn|empty user page]] [[Special:Emailuser/User:Boudewijn|Contact]]; possibly got a second person interested

=== Den Haag ===

==== Rijswijk ====
* Fernando Martins 1x [[User:fmartins]] [[Special:Emailuser/User:fmartins|Contact]]

=== Utrecht ===

==== Utrecht ====
* Eric Spierings 1/10 [[Special:Emailuser/User:ericsp|Contact]]
* Peter van de Werken 2/10 [[Special:Emailuser/User:PWerken|Contact]]

=== Status ===
19/20

== New Zealand ==
As Telecom are using the 850MHz network for their GSM network, and Vodafone/northelia (possibly aka orcon) are using 900/1800MHz, please state which version you want. This may need more research, I'm not 100%; see [http://www.gsmworld.com/roaming/gsminfo/cou_nz.shtml] for more info 
According to jeremy list, telecom will not be rolling out GSM for four years, so the point becomes moot - no-one is likely to get an 850 gsm phone now and wait that long 

Based on info from steve (openmoko marketing) concerning weight and size, shipping via UPS will be about US$185 (NZ$23 each phone) to Auckland. 
UPS are far from the cheapest, but (again according to steve), OM have a contract with them, so this is what we are stuck with 

Someone on the community list suggested using [http://www.myus.com], a shipping company that will re-post items overseas at decent rates. They claim US$66 for a 3kg package, or NZ$8 per phone. Of course, the cost of shipping the phone from OM to the shipping company has to be added in as well.

As of 2008-04-28, US$399 is worth NZ$508

import duty on mobile phones is 0%[http://www.customs.govt.nz/importers/Private+Importers/Customs+Charges.htm], and GST is 12.5% so the GST added to each phone will be NZ$66; 12.5% * {508 + 23), cos we pay GST on postage too...

So, the total cost of a Freerunner as part of a 10 pack, will be: 
508 + 23 + 66 
= 597 

+ any possible charges to get it posted elsewhere in New Zealand

=== Auckland ===
==== Auckland ====
Status:6/10
*Rob Paulson [[User:Myfanwy]] 900MHz
**i'm quite happy to organise the purchase, if no-one has any objections. to ease any worries about me running off with the money, we could use an escrow service such as [http://safetrader.co.nz], or paypal. or does anyone have any other ideas?
*Simon Wells [[User:Swel024]]
*Jeremy List [[User:Jeremy-list]] mailto:quick.dudley@gmail.com (Wellington, not Auckland, will pay for courier)
*David Murrell [[User:Viddy]] - [mailto:dmurrell@waikato.ac.nz] I'm in Hamilton, either courier, or I'll drive up :)
*Jeremy Gray [[User:Bogdan237]] [mailto:jgra163@ec.auckland.ac.nz] Auckland, 900MHz
*Glen Ogilvie [[User:Nelg]] {mailto:nelg@linuxsolutions.co.nz] Auckland, 900MHz

== Norway ==
=== Nordland ===
==== Bodø ====
Status 2/10

* [[User:AlecTBM|Alexander Frøyseth]] [mailto:alexander.froyseth@gmail.com alexander.froyseth@gmail.com]
* Ole Marius
* Stian Vading
=== Rogaland ===
Status 1/10

*[[User:Dalaker|Tore Dalaker]] [mailto:tore@dalaker.com tore@dalaker.com]

=== Sør-Trøndelag ===
==== Trondheim ====
Status 11/20

*[[User:andy000|Andreas Kalvå]] [mailto:andy@samfundet.no andy@samfundet.no]
Send mail om du er interessert.

=== Østlandet ===
==== Oslo, Akershus, Buskerud, Vestfold ====
Status 20/20(30?)

* [[User:Ixian|Heikki Sørum]] [mailto:heikkis@matnat.uio.no] Interessert? mail meg.
* [[User:Bobkare|Knut Arne Bjørndal]] [mailto:bob@cakebox.net]

== Poland ==
=== podlaskie ===
==== Białystok ====
2 x rhn [http://wiki.openmoko.org/wiki/Special:Emailuser/rhn contact me here]
Inne miasta mile widziane, pod warunkiem, że koszty przesyłki będą niskie

=== dolnośląskie ===
==== Wrocław ====

* Special group buy site: https://www.kumulator.pl/show/group/35

== Portugal ==
=== Aveiro ===
==== Aveiro ====
Status : 2/10

* [[User:Ruben|Ruben Mendes]]
* [[User:kuyky|Tiago Saraiva]] [mailto:destructhor88@gmail.pt]

== Sweden ==
If insufficient number of people, orders could be merged and remailed perhaps.

Domestic remailing with Posten as A-class mail of a letter (criteria: length+width+height max 900 mm) weighing max 1 kg, without insurance should [http://www.posten.se/foretag/vara_tjanster/postageguide/postguideLetterDom.jspv cost 44 SEK]. 50 SEK more for insurance.

If we end up with more than one 10-pack in Sweden, my guess is that it would probably pay to order everything in one shipment to one address in Sweden to save on the international shipping, and then remail domestically.

=== Götaland ===
==== Göteborg ====

* [[User:Fwendt|Fredrik Wendt]] [[Special:Emailuser/Fwendt|Contact]]/wendt.se

==== Malmö ====
Status : 1/10

* Lars Jarlvik mailto:lars@larsfactory.se

=== Svealand ===
==== Stockholm ====
Status : 4/10

* Erland Lewin mailto:erland@lewin.nu
* Simon Kågström mailto:simon.kagstrom@gmail.com
* Ingvaldur Sigurjonsson mailto:ingi@ultimalabor.se
* Adam Johansson mailto:adam@sollentunaholm.se

==== Örebro ====
Status : 1/10

* Anders Petersson [mailto:demitar@worldforge.org demitar@worldforge.org]

==== Västerås ====
Status : 1/10
* Jörgen Lidholm, could join the Falun/Borlänge or Stockholm group [mailto:jorgen.lidholm@gmail.com]

==== Falun & Borlänge ====
Status : 4/10

* [http://wiki.openstreetmap.org/index.php/User:Jth Johan Thelmén], Åke Hoff & a demo/backup
* [http://wiki.openstreetmap.org/index.php/User:eagle87 Pär Eriksson], Borlänge

=== Norrland ===
==== Umeå ====
Status : 2/10

* [[User:Zash|Zash]] [[Special:Emailuser/Zash|Contact]]
* [[User:Benjamin|Benjamin]] [[Special:Emailuser/Benjamin|Contact]]

==== Luleå ====
Status : 2/10

* [[User:Mjukis|Mjukis]] [[Special:Emailuser/Mjukis|Contact]] - 2 Units. Can also join the Malmö group order.

== Switzerland ==
Gabriel Ambuehl would volunteer to order the initial 10pack.
Alexandre Ghisoli could organize the second 10pack.
Both with payment in advance (a 10pack will cost approx 3'800 USD).

Probably we will organize shipping, if we cannot all move to Zürich to get our Neo.

==== Shipping ====
If we would ship Neos, here is the Swiss PostPac prices :

{| border="1" cellspacing="0" cellpadding="2"
! Description
! Size [cm]
! Price CHF TTC
|-
| Size 1
| 22.9 x 14.7 x 9.9
| 2.20
|-
| Size 2
| 31.5 x 22.5 x 12.5
| 2.40
|-
| Shipping Priority
| up to 2Kg
| 8.-
|-
| Shipping Economy
| up to 2Kg
| 6.-
|}

 

Steve posted informations about boxes that will be out with Neo :

* 10 pack : 435mm x 371mm x 119mm, approx 3kg, UPS will charge 160USD (need to be verified)
* Individual pack : 178mm x 104mm x 84mm, 237 grams

So size 1 will fit ! Local delivery in Switzerland will cost 8.20 for Economy or 10.20 Priority.

==== Zurich ====
Status : 20/20

It seems that while there are 20 people listed here, actually the device number is 21, because Tobias Kündig is interested in 2 of them. This means that the total number of devices for Swiss people is 23 (21 for Zürich plus 2 for Genève). -- LucaCapello

* Simon Wenner [http://wiki.openmoko.org/wiki/Special:Emailuser/Nowic Contact]
* Simon Schreiber [http://wiki.openmoko.org/wiki/Special:Emailuser/Magbeat Contact]
* Markus Huggler [http://wiki.openmoko.org/wiki/Special:Emailuser/Magbeat Contact]
* Andre Timmermann [http://wiki.openmoko.org/wiki/Special:Emailuser/darktim Contact]
* Raffael Schmid [http://wiki.openmoko.org/wiki/Special:Emailuser/darktim Contact]
* Pascal Weller [http://wiki.openmoko.org/wiki/Special:Emailuser/darktim Contact]
* Nick Zbinden (Luzern) [mailto:nickik@gmx.ch] oder [http://wiki.openmoko.org/wiki/Special:Emailuser/nickik Contact]
* Marcel Wirth [http://wiki.openmoko.org/wiki/Special:Emailuser/Skarhand Contact]
* Marcel Lütolf (Luzern) [http://wiki.openmoko.org/wiki/Special:Emailuser/NeRo Contact]
* Christian Corrodi [http://wiki.openmoko.org/wiki/Special:Emailuser/Matto Contact]
* Mirko Klingauf [http://wiki.openmoko.org/wiki/Special:Emailuser/RealAtaman Contact]
* Marcel Jost [http://wiki.openmoko.org/wiki/Special:Emailuser/Onsonic Contact]
* Alexandre Ghisoli (Yverdon) [http://wiki.openmoko.org/wiki/Special:Emailuser/Agh Contact]
* Marc Andre Tanner (Biel) [http://wiki.openmoko.org/wiki/Special:Emailuser/mat Contact]
* Tobias Kündig (2 Geräte) (Luzern) [mailto:info@it-media.ch]
* Peter Salvisberg [http://wiki.openmoko.org/wiki/Special:Emailuser/Psal Contact]
* Robin Farine (Auvernier) [http://wiki.openmoko.org/wiki/Special:Emailuser/rfarine Contact]
* Martin Kos [http://wiki.openmoko.org/wiki/Special:Emailuser/KoS Contact]
* Lorenz Schori (Bern) [http://wiki.openmoko.org/wiki/Special:Emailuser/Znerol Contact]
* Jonas Schwarz (Lausanne) [http://wiki.openmoko.org/wiki/Special:Emailuser/jnsc Contact]

==== Geneve ====
Status : 3/10

* Diego Abelenda [http://wiki.openmoko.org/wiki/Special:Emailuser/Aelia Contact]
* Luca Capello [mailto:luca@pca.it]
* Nicolas Produit [http://wiki.openmoko.org/wiki/Special:Emailuser/Produit Contact]

== Spain ==
=== Spain (Country Group Sale) ===
Status: 5/10
=== Madrid ===
==== Madrid ====
Status : 1/10

* Rafael Campos [http://wiki.openmoko.org/wiki/Special:Emailuser/Methril Contact]

=== Zaragoza ===
==== Zaragoza ====
Status : 2/10

* Alejandro R. Mosteo alejandro AT mosteo · com
* Arturo Giner [[Special:Emailuser/artginer|Contact]]

=== Barcelona ===
==== Barcelona ====
Status : 2/10

* José Luis Pérez [[Special:Emailuser/jluis|Contact]]
* David Reyes Samblas Martinez [[Special:Emailuser/mutrox|Contact]]

== UAE ==
Status: 1/10
* Yaser Ammar [[Special:Emailuser/Waraqa|Contact]]

== USA ==
=== Colorado ===
==== Denver (Full) ====
Status: 10/10 (includes the gentleman from Utah)
* Shawn Sullivan [[mailto:shelbydz87@yahoo.com shelbydz87@yahoo.com]]
* Peter Abplanalp [http://wiki.openmoko.org/wiki/Special:Emailuser/alderion Contact]
* Ben Burdette [http://wiki.openmoko.org/wiki/Special:Emailuser/Ansible Contact]
* Tom Russell [http://wiki.openmoko.org/wiki/Special:Emailuser/tazbert Contact]
* Trace [http://wiki.openmoko.org/wiki/Special:Emailuser/gnork Contact]

=== California ===
==== Los Angeles ====
Status: 3/10

* Ian Douglas [http://wiki.openmoko.org/wiki/Special:Emailuser/Iandouglas Contact me here]
* Matthew [http://wiki.openmoko.org/wiki/Special:Emailuser/Wetmoko Contact]
* Daniel [http://wiki.openmoko.org/wiki/Special:Emailuser/Beaker82 Contact]

==== San Francisco Bay Area ====
Status: 4/10

* Ajit Natarajan - [http://wiki.openmoko.org/wiki/Special:Emailuser/ajitk Contact]

* Dirk Bergstrom - [http://wiki.openmoko.org/wiki/Special:Emailuser/krid Contact]

* Tupshin Harper - [http://wiki.openmoko.org/wiki/Special:Emailuser/tupshin Contact]

* Lothar Werzinger (900MHz) - [http://wiki.openmoko.org/wiki/Special:Emailuser/Elektrolott Contact]

==== San Diego (inc. San Diego county) ====
Status: 1/10

* Peter Naulls [http://wiki.openmoko.org/wiki/Special:Emailuser/Pnaulls Contact]

==== Monterey ====
Status: 2/10

* Cry Regarder [http://wiki.openmoko.org/wiki/Special:Emailuser/Cry_Regarder Contact]

=== Indiana / Kentucky ===
Status: 5/10
* Brandon Kruger [mailto:bmk789@gmail.com email]
* Geoff Ruscoe [[Special:Emailuser/Geocode|Contact]]
* Dan Staley [[Special:Emailuser/Pyrasi|Contact]] (Kentucky)
* Donnie Jones [[Special:Emailuser/Donniejones18|Contact]] (Lexington, KY)
* John Sterling [[Special:Emailuser/Sterling|Contact]] (Lexington, KY)
=== Ohio / Michiga ===
Status: 1/10
* David Pais [mailto:davioh2001@yahoo.com email]
=== Washington ===
==== Seattle ====
Status: 1/10
* Jon Pomeroy [[Special:Emailuser/Jepomeroy|Contact]]

=== Tennessee ===
==== Memphis ====
Status: 1/10
* Peter O'Connor [http://wiki.openmoko.org/wiki/Special:Emailuser/poconnor Contact]

=== Texas ===
==== Austin (4/10) ====
* Dale Schumacher [[Special:Emailuser/dalnefre|Contact]]
* Michael Cosby [[Special:Emailuser/mcosby|Contact]]
* Paul Jimenez [[Special:Emailuser/pj|Contact]]
* Charles [[Special:Emailuser/rbn|Contact]]

==== Dallas (1/10) ====
* Philip White [[Special:Emailuser/pmw|Contact]]

=== Mid-Atlantic ===
==== Virginia====
===== Richmond (1/10)=====
* Philippe Gerard [[Special:Emailuser/feydreva|Contact]]

==== New York ====
Status: 2/10 or 3/10

* Bert Hartmann [http://wiki.openmoko.org/wiki/Special:Emailuser/BertHartm Contact me here]
* Michael Cole mailto:mjcole137@gmail.com 
* Jake Thebault-Spieker (probably, may not be able to afford it) [http://wiki.openmoko.org/Spcial:Emailuser/Summatusmentis Contact me here]

==== Maryland (2/10)====
* Paul Buede mailto:paul@buede.com 
* Charles Lohr

== UK ==

* Stroller (Milton Keynes, can travel) mailto:stroller@stellar.eclipse.co.uk 01908 663 513. Thinks that breaking the UK up into regions - at least outside London - is silly. There are unlikely to be 10 people in $your_town who want a Freerunner, so some posting if Freerunners will surely be required; see [http://wiki.openmoko.org/wiki/Talk:GroupSales#Oxford the talk page]. This is the same cost anywhere in the UK. I'm a realist, so I'm prepared to trust someone up front with my cash &/or travel to collect. In principle I'd be prepared to make the group order & post onwards (or allow collection), and I'd expect a 50% up-front payment; however cash is very tight at the moment, and I don't know that I'll be able to front the other 50%.

=== Scotland ===
==== Edinburgh ====
Status : 3/10

* Joe Wells (Edinburgh) [http://wiki.openmoko.org/wiki/Special:Emailuser/jbw Contact]
* Dave Ball (Edinburgh) [http://wiki.openmoko.org/wiki/Special:Emailuser/Daveb Contact]
* Stuart MacKinnon(Livingston) [http://wiki.openmoko.org/wiki/Special:Emailuser/hoagster Contact]

=== England ===

==== Hampshire ====

http://www.hants.lug.org.uk/cgi-bin/wiki.pl?FreerunnerBulkBuy

(Sorry, we set up the page before we knew about this one)

==== London ====

Status : 8/10

* Juergen Schinker mailto:ba1020@homie.homelinux.net
* aled [http://wiki.openmoko.org/wiki/Special:Emailuser/aled Contact]
* Bin Zong (actually in Birmingham) [mailto:hunter_00zb@hotmail.com]
* Robert Piasek (actually in Southampton) [http://wiki.openmoko.org/wiki/Special:Emailuser/Queen6 Contact]
* Tom Scholl (Cambridge, travel to London now and then anyway so could pick up) [mailto:thomasscholl@gmail.com]
* Weiss (Cambridge, could collect from London) [http://wiki.openmoko.org/wiki/Special:Emailuser/Weiss Contact]
* Neil Bentley (in Wiltshire) [http://wiki.openmoko.org/wiki/Special:Emailuser/Ohnez Contact]

==== Oxford ====

Idea to re-ship within the UK, see [http://wiki.openmoko.org/wiki/Talk:GroupSales#Oxford talk]

Status : 3/10

* Tim Coggins [http://wiki.openmoko.org/wiki/Special:Emailuser/sonicated Contact]

* James Olney [http://wiki.openmoko.org/wiki/Special:Emailuser/Webjames Contact]
* David Pottage (actually in Reading) [http://wiki.openmoko.org/wiki/Special:Emailuser/chrestomanci Contact]

==== West Midlands ====
Status : 1/10

* Mo Abrahams (Walsall) mailto:moabrahams@dashavoo.com

== Latvia ==
=== Riga ===
==== Riga ====
Status : 1/10
* Ilya [http://wiki.openmoko.org/wiki/Special:Emailuser/VRGhost Contact]

== Singapore ==
Status : 1/10
* Wee Kiam Peng [http://wiki.openmoko.org/wiki/Special:Emailuser/Jipi Contact]

== Israel==
Status : 1/10
* Ofer Herman [http://wiki.openmoko.org/wiki/Special:Emailuser/oferhe Contact]