Openmoko - User contributions [en]

Open HW SW Event/de

2010-12-04T09:22:23Z

Mickey: /* Vortrags- und Schulungsmaterial */

= Erstes deutsches Open-HW&SW-Event =
== Zusammenfassung ==
* Ort: Amalienstr. 17, 80333 München
* Datum: 4. und 5. Dezember 2010 (zweiter Advent)
* Uhrzeit: 9:30 - ca. 18:30
* Workshops/Vorträge: siehe Agenda
* Mailingliste: http://lists.goldelico.com/mailman/listinfo/open-hard-software-event
* Live-Stream: http://www.ustream.tv/channel/oshw-workshop

== Note to English Speakers ==
It will be ok if you give your presentation in English, but discussions and other activities will be in German. So please decide yourself if you can follow German discussions well enough that you can take something home. The event is not thought just to be a stage for presentations, but for working together (discussions, workshops, having lunch&fun).

= Beschreibung =

Auf verschiedenen Treffen und Diskussionen ist immer wieder die Frage aufgetaucht, ob sich nicht mal alle an offenen Phones und Plattformen Interessierten (d.h. nicht nur die Openmoko-Fans) einen gemeinsamen Workshop/Treffen/Event irgendwo treffen können. Denn auf anderen Events wie [[http://www.fosdem.org FOSDEM]] oder [[http://www.linuxtag.org LinuxTag]] ist alles so groß und unüberschaubar, daß irgendwie zu wenig Austausch (Diskussion, Kennenlernen) stattfindet.

== Themen ==
Und zwar könnte es um alles rund um Projekte für offene Hardware und Software gehen. Themen könnten sein (ohne Anspruch auf Vollständigkeit):
* [[Openmoko]]
* [http://www.arduino.cc Arduino]
* [http://en.qi-hardware.com/wiki/Ben_NanoNote Nanonote]
* [http://openpandora.org OpenPandora]
* [[Freerunner Navigation Board v2]]
* [http://beagleboard.org BeagleBoard]
* [[SHR]]
* [[QtMoko]]
* [[FSO]]

Deshalb haben wir das neulich auf dem Forum www.freeyourophone.org in Angriff genommen: http://freeyourphone.de/portal_v1/viewtopic.php?f=71&t=1794
Dabei entstand eine Meinungsumfrage die großes Interesse und Themenvielfalt zeigte: http://freeyourphone.de/portal_v1/viewtopic.php?f=71&t=1794&hilit=event&start=15

Wer teilnehmen möchte und/oder etwas vortragen bitte auf der Mailingliste registrieren und Wünsche äußern.

== Ort ==
Wir haben nun einen Veranstaltungsort gefunden:

Ludwig-Maximilians-Universität München
LFE Medieninformatik
Amalienstr. 17
80333 München
http://www.medien.ifi.lmu.de
[http://maps.google.de/maps?f=q&hl=de&geocode=&time=&date=&ttype=&q=amalienstr.+17+m%C3%BCnchen&ie=UTF8&hq=&hnear=Amalienstra%C3%9Fe+17,+M%C3%BCnchen+80333+M%C3%BCnchen,+Bayern&ll=48.147053,11.576141&spn=0.000771,0.000923&t=h&z=20 Google Maps], [http://www.nucleo.com.es/maps/ inkl. Raumübersicht], [http://www.openstreetmap.org/?lat=48.14677&lon=11.576166&zoom=18&layers=M OSM]

Es stehen zwei Seminarräume (A105 und A107) sowie ein kleinerer Raum (A103) zur Verfügung. Außerdem können wir den Gang davor nutzen.

==== Kapazität ====
* '''A105''': 20-30 Zuhörer (mit Tischen) bis max 50 (ohne Tische), oder 8 Tische mit je 2-4 Bastlern
* '''A107''': 15-20 Zuhörer (mit Tischen) bis max. 30 (ohne Tische), oder 5 Tische mit je 2-4 Bastlern
* '''A103''': ruhiger Arbeitsraum für max. 5 Personen

Außerdem können wir noch max. 3 Tische mit je 1-2 Bastlern im Gang an die Wand stellen.

Maximalkapazitäten sind wirklich maximal :)

== Zeit ==

Es gab 18 Voranmeldungen (auf http://www.doodle.com/93cu86vm2s69zsxc) und das Wochenende des 4. Dezembers hat als Rekord 17 Teilnehmer erbracht. Daher haben wir die Räume für diesen Termin reserviert.

== Agenda ==

{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Programm für Samstag'''
! '''Tag''' !! '''Zeit''' !! '''Referent''' !! '''Art''' !! '''Zeitbedarf (inc. Diskussion)''' !! '''Thema'''
|-
| Sa || 09:30-10:00 || alle || Vorstellrunde und Kennenlernen || 30 min || falls jemand zu knapp eintrifft
|-
| Sa || || || || || Projekte
|-
| Sa || 10:00-11:30 || [[User:Cmair]], [[User:MicVM]], Alexander Lehmann || Vortrag || 90 min || Vorstellung des [[FRNBv2]], Grundlagen inertialer Navigation
(Precision und Accuracy, Fehlerquellen, Sampling Frequency, Sensorbandbreite, SNR (Signal to Noise Ratio), Gyro-Integration / Rotationsreihenfolge / Euler vs. Quats, Quadratischer Fehler bei der Positionsbestimmung (Demo), Schwellwert, (Gleitender) Mittelwert, Tiefpass, Kalman)
|-
| Sa || 11:30-12:30 || Evil Dragon || Vortrag || 60 min || Evil Dragon ein Entwickler der Pandora wird in diesem Vortrag über die bewegende Geschichte der Pandora (http://www.openpandora.de) erzählen
|-
| Sa || 12:30-13:15 || Dieter Spaar || Vortrag || 45 min || OsmocomBB, der Open Source GSM Stack (http://bb.osmocom.org/trac/)
|-
| Sa || 13:15-14:15 || || Pause || 60 min ||
|-
| Sa || 14:15-15:15 || [[User:Hns]] || Vortrag, Demo || 60 min || 1. Der OMAP-Board-Zoo - ein kleiner Überblick und Starthilfe
2. [[Openmoko Beagle Hybrid]] - oder wie stopft man ein neue CPU (OMAP3) in einen Freerunner?
|-
| Sa || || || || || Grundlagen
|-
| Sa || 15:15-16:45 || Jörg Eesmann || Vortrag || 90 min || Microcontroller (nicht nur AVR), Einführung in Interfaces ( CAN, I2S, SPI, PWM, ADC, Interrupts (Prioritaeten, Nesting...), Echtzeitsysteme, Reaktionszeiten, Prioritaetsinversion)
|-
| Sa || 16:45-17:45 || Florian Boor || Vortrag, Demo || 60 min || Einführung in Open Embedded (wie installiere, konfiguriere ich mein eigenes Image oder meine Distribution)
|-
| Sa || 17:45-18:45 || Mickey Lauer || Vortrag || 60 min || Einführung in [[FSO]]
|}

<br />

{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Programm für Sonntag'''
! '''Tag''' !! '''Zeit''' !! '''Referent''' !! '''Art''' !! '''Zeitbedarf (inc. Diskussion)''' !! '''Thema'''
|-
| So || || || || || parallele Workshops
|-
| So || 09:30-12:30 || [[User:Cmair]] || Workshop || 3h (180 min) || [[FRNBv2]]: Lötsession HW & SW Integration
Freerunner und evtl. Lötkolben mitbringen!

Mögliche Themen:
* Wie schreibe ich einen Kerneltreiber für I2C-Geräte?
* Hands-on-Sensors: Experimente mit Kompass, Gyroskop und Luftdruckmesser
* Wir bauen mit dem FRNBv2 eine IR Fernbedienung.
* ...
|-
| So || 11:00-13:00 || Juergen Neumann || Vortrag / Workshop || 120 min || OHANDA - Open Source Hardware and Design Alliance - Ready to register? http://www.ohanda.org
Kurze Vorstellung der Idee und des Status Quo. Diskussion und ggf. Ausarbeitung der nächsten Schritte.
|-
| So || ca. 13:00 || || individuelle Pause || || in Absprache mit den Workshopteilnehmern
|-
| So || 13:00-17:00 || ? Mickey Lauer, [[User:Cmair]] || ? Workshop || || Vorschlag: Code-Sprint für FRNB-Integration in FSO
|-
| So || 13:00-18:00 || Rene Leitner || Workshop || 5 h (300 min) || SDL Für Einsteiger. Du wolltest schon immer anfangen zu programmieren, hast aber nie den Weg dazu gefunden. Du möchtest gerne wissen wie du mit C/C++ und SDL ein kleines Spiel Programmieren kannst? In diesen Workshop werden all deine Fragen versucht zu beantworten, von C bis SDL wird alles Anfänger freundlich erklärt und diskutiert, um am Ende des Tages ein kleines Spiel programmiert zu haben.

Bringt bitte euren Rechner mit, das Betriebssystem ist egal. Wenn ihr schon was vorbereiten möchtet dann ladet euch das folgende runter:
Linux Ubuntu:
sudo apt-get install build-essential codeblocks

Windows:
http://prdownload.berlios.de/codeblocks/codeblocks-10.05mingw-setup.exe

MacOS:
http://prdownload.berlios.de/codeblocks/codeblocks-10.05-p1-mac.dmg

Falls ihr ein anders OS nutzt, schaut bitte hier:
http://www.codeblocks.org/downloads
|-
|}

= Vortrags- und Schulungsmaterial =
Die Vorträge können direkt hier in das Wiki hochgeladen werden. Verwendet dazu einfach diesen [[Special:Upload|Upload]]-Link und benutzt in der Tabelle den Dateinamen in einem ''Media''-Link. Der erste Eintrag in der Tabelle demonstriert das beispielhaft. ''Media''-Links auf noch nicht hochgeladene Objekte führen automatisch zu einem Uploadformular.

{| border="1" cellspacing="0" cellpadding="4"
|- bgcolor="#c0e0e0"
|+ '''Vortrag/Workshop'''
|- bgcolor="#c0e0e0"
| align="center" | '''Referent(en)'''
| align="center" | '''Name der Session'''
| align="center" | '''Material'''
|-
|''Anton Beispiel''
|''Zeigen wie es geht''
|[[Media:Beispieldokument.pdf|PDF]]
|-
|[[User:Cmair]], [[User:MicVM]], Alexander Lehmann
|Vorstellung des [[FRNBv2]]
|
[http://chonyota.net/freerunner/OpenMoko_Vortrag.pdf]
[http://chonyota.net/freerunner/FRNB-History.pdf]
|-
|[[User:Cmair]]
|[[FRNBv2]]: Lötsession HW & SW Integration
|
|-
|Evil Dragon
|Entwicklung der Pandora
|
|-
|Florian Boor
|Einführung in OpenEmbedded
|
|-
|Mickey Lauer
|Einführung in [[FSO]]
|[http://www.linuxtogo.org/~mickeyl/misc/Einstieg-in-FSO.pdf]
|-
|[[User:Hns]]
|Überblick und Starthilfe zum Texas Instruments-Hardwarezoo
|
|-
|[[User:Hns]]
|[[Openmoko Beagle Hybrid]] - neue CPU in einen Freerunner
|
|-
|Jörg Eesmann
|Microcontroller (nicht nur AVR)
|
|-
|Dieter Spaar
|[http://bb.osmocom.org/trac/ OsmocomBB] - der Open Source GSM Stack
|
|-
|Juergen Neumann
|OHANDA - Open Source Hardware and Design Alliance - Ready to register?
|
|-
|Mickey Lauer(?), [[User:Cmair]]
|Vorschlag: Code-Sprint für FRNB-Integration in FSO
|
|-
|Rene Leitner
|SDL Für Einsteiger
|
|}

= Mailingliste / Anmeldungen =
Fragen, Anregungen, Kritik bitte die Mailingliste http://lists.goldelico.com/mailman/listinfo/open-hard-software-event schreiben.

Außerdem sollten sich alle (potenziellen) Teilnehmer dort anmelden um eventuelle Änderungen mitzubekommen.

Open HW SW Event/de

2010-10-20T09:52:05Z

Mickey: /* Agenda */

= Erstes deutsches Open-HW&SW-Event =
== Zusammenfassung ==
* Ort: Amalienstr. 17, 80333 München
* Datum: 4. und 5. Dezember 2010 (zweiter Advent)
* Uhrzeit: tbd.
* Workshops/Vorträge: tbd.
* Mailingliste: http://lists.goldelico.com/mailman/listinfo/open-hard-software-event

== Note to English Speakers ==
It will be ok if you give your presentation in English, but discussions and other activities will be in German. So please decide yourself if you can follow German discussions well enough that you can take something home. The event is not thought just to be a stage for presentations, but for working together.

= Beschreibung =

Auf verschiedenen Treffen und Diskussionen ist immer wieder die Frage aufgetaucht, ob sich nicht mal alle an offenen Phones und Plattformen Interessierten (d.h. nicht nur die Openmoko-Fans) einen gemeinsamen Workshop/Treffen/Event irgendwo treffen können. Denn auf anderen Events wie [[http://www.fosdem.org FOSDEM]] oder [[http://www.linuxtag.org LinuxTag]] ist alles so verteilt, daß irgendwie zu wenig Austausch stattfindet.

== Themen ==
Und zwar könnte es um alles rund um Projekte für offene Hardware und Software gehen. Themen könnten sein (ohne Anspruch auf Vollständigkeit):
* [[Openmoko]]
* [http://www.arduino.cc Arduino]
* [http://en.qi-hardware.com/wiki/Ben_NanoNote Nanonote]
* [http://openpandora.org OpenPandora]
* [[Freerunner Navigation Board v2]]
* [http://beagleboard.org BeagleBoard]
* [[SHR]]
* [[QtMoko]]
* [[FSO]]

Deshalb haben wir das neulich auf dem Forum www.freeyourophone.org in Angriff genommen: http://freeyourphone.de/portal_v1/viewtopic.php?f=71&t=1794
Dabei entstand eine Meinungsumfrage die großes Interesse und Themenvielfalt zeigte: http://freeyourphone.de/portal_v1/viewtopic.php?f=71&t=1794&hilit=event&start=15

Wer teilnehmen möchte und/oder etwas vortragen bitte auf der Mailingliste registrieren und Wünsche äußern.

== Ort ==
Wir haben nun einen Veranstaltungsort gefunden:

Ludwig-Maximilians-Universität München
LFE Medieninformatik
Amalienstr. 17
80333 München
http://www.medien.ifi.lmu.de
[http://maps.google.de/maps?f=q&hl=de&geocode=&time=&date=&ttype=&q=amalienstr.+17+m%C3%BCnchen&ie=UTF8&hq=&hnear=Amalienstra%C3%9Fe+17,+M%C3%BCnchen+80333+M%C3%BCnchen,+Bayern&ll=48.147053,11.576141&spn=0.000771,0.000923&t=h&z=20 Google Maps], [http://www.nucleo.com.es/maps/ inkl. Raumübersicht], [http://www.openstreetmap.org/?lat=48.14677&lon=11.576166&zoom=18&layers=M OSM]

Es stehen zwei Seminarräume (A105 und A107) sowie ein kleinerer Raum (A103) zur Verfügung. Außerdem können wir den Gang davor nutzen.

==== Kapazität ====
* '''A105''': 20-30 Zuhörer (mit Tischen) bis max 50 (ohne Tische), oder 8 Tische mit je 2-4 Bastlern
* '''A107''': 15-20 Zuhörer (mit Tischen) bis max. 30 (ohne Tische), oder 5 Tische mit je 2-4 Bastlern
* '''A103''': ruhiger Arbeitsraum für max. 5 Personen

Außerdem können wir noch max. 3 Tische mit je 1-2 Bastlern im Gang an die Wand stellen.

Maximalkapazitäten sind wirklich maximal :)

== Zeit ==

Es gab 18 Voranmeldungen (auf http://www.doodle.com/93cu86vm2s69zsxc) und das Wochenende des 4. Dezembers hat als Rekord 17 Teilnehmer erbracht. Daher haben wir die Räume für diesen Termin reserviert.

== Agenda ==
Es wird ein Mischung aus (Plenar-)Vorträgen und Workshops/Hands-On-Sessions geben. Eventuell am ersten Tag Vorträge für alle, so dass jeder alle Themen kennenlernen kann und dann am zweiten Tag an 2-3 Workshops teilnehmen.

Weitere Vorschläge für Referenten (und Themen) sind willkommen. Bitte einfach auf der Mailingliste anmelden und neue Themen vorschlagen.

Die Liste hier ist noch vorläufig und wird bis zum Workshop laufend angepaßt. Also bitte immer wieder reinschauen.

{| border="1"
! Tag !! Zeit !! Referent !! Art !! Zeitbedarf !! Thema !! Bemerkungen
|-
| 1. || 11:00-12:00 || Mickey Lauer || Vortrag || 60 min || Einführung in [[FSO]] ||
|-
| 1. || 12:00-13:00 || [[User:Cmair]], [[User:MicVM]] || Vortrag || || Vorstellung des [[FRNBv2]], Grundlagen inertialer Navigation (Precision und Accuracy, Fehlerquellen, Sampling Frequency, Sensorbandbreite, SNR (Signal to Noise Ratio), Gyro-Integration / Rotationsreihenfolge / Euler vs. Quats, Quadratischer Fehler bei der Positionsbestimmung (Demo), Schwellwert, (Gleitender) Mittelwert, Tiefpass, Kalman) ||
|-
| 1. || 14:30-18:00 || [[User:Cmair]] || Workshop || || [[FRNBv2]]: Lötsession HW & SW Integration || Freerunner und evtl. Lötkolben mitbringen!
|-
| 1. || 10:00-11:00 || [[User:Hns]] || Vortrag, Demo || 45 min || [[Openmoko Beagle Hybrid]] - oder wie stopft man ein neue CPU (OMAP3) in einen Freerunner? ||
|-
| 1. || 10:00-11:00 || Jörg Eesmann || Vortrag || 90 min || Microcontroller (nicht nur AVR), Einführung in Interfaces ( CAN, I2S, SPI, PWM, ADC, Interrupts (Prioritaeten, Nesting...), Echtzeitsysteme, Reaktionszeiten, Prioritaetsinversion) ||
|-
| 1. || 10:00-11:00 || Florian Boor (angefragt) || Vortrag, Demo || || Einführung in Open Embedded (wie installiere, konfiguriere ich mein eigenes Image oder meine Distribution) ||
|-
| 1. || 10:00-11:00 || tbd. || Workshop || || Code-Sprint für FSO ||
|-
| 1. || 10:00-11:00 || Dieter Spaar || Vortrag || 45 min || OsmocomBB, der Open Source GSM Stack (http://bb.osmocom.org/trac/) ||
|-
| 1. || 10:00-12:00 || Juergen Neumann || Vortrag / Workshop || 120 min || OHANDA - Open Source Hardware and Design Alliance - Ready to register? http://www.ohanda.org || Kurze Vorstellung der Idee und des Status Quo. Diskussion und ggf. Ausarbeitung der nächsten Schritte.
|-
| 2. || 10:00-17:00 || Rene Leitner || Workshop || 5H || SDL Für Einsteiger. Du wolltest schon immer anfangen zu programmieren, hast aber nie den Weg dazu gefunden. Du möchtest gerne wissen wie du mit C/C++ und SDL ein kleines Spiel Programmieren kannst? In diesen Workshop werden all deine Fragen versucht zu beantworten, von C bis SDL wird alles Anfänger freundlich erklärt und diskutiert, um am ende des Tages ein kleines Spiel programmiert zu haben.
|-
|}

= Mailingliste / Anmeldungen =
Fragen, Anregungen, Kritik bitte die Mailingliste http://lists.goldelico.com/mailman/listinfo/open-hard-software-event schreiben.

Außerdem sollten sich alle (potenziellen) Teilnehmer dort anmelden um eventuelle Änderungen mitzubekommen.

Template:News

2010-02-04T00:28:58Z

Mickey: FOSDEM!

* '''2010-02-07:''' [http://fosdem.org/2010/schedule/devrooms/openmoko Openmoko @ FOSDEM 2010]: AW1.124 on Sunday, 09:00-12:00
* '''2010-01-14:''' [[Community Updates/2010-01-14|Community Updates]]
* '''2009-12-31:''' [[Community Updates/2009-12-31|Community Updates]]
* '''2009-12-09:''' [[Community Updates/2009-12-09|Community Updates]]

FOSDEM 2010

2010-02-04T00:25:50Z

Mickey: /* Openmoko @ FOSDEM 2010 */

== Openmoko @ FOSDEM 2010 ==
As every year it takes place in Brussels. This year's date is 6./7. February. This year, we have a devroom AW1.124 on Sunday morning (09:00-12:00). Please see http://fosdem.org/2010/schedule/devrooms/openmoko for the talk program. In short:
<pre>
Sun 09:00-09:30 Openmoko: 20 Minutes of history Michael Lauer
Sun 09:30-10:15 Android on Freerunner Niels Heyvaert
Sun 10:15-11:00 Freesmartphone.org: DBus-Middleware for mobile devices Michael Lauer
Sun 11:00-11:30 SHR: A FSO based Openembedded distribution Thomas Zimmermann
Sun 11:30-12:00 hackable:1, a Debian/Gnome distribution for hackable devices David Wagner
</pre>

=== Talks ===
Please add Openmoko/Freerunner related activities here:

{| border="1"
! Day
! Title
! Link
|-
| Sunday || Learnings from porting QuantumSTEP to different Linux Handhelds (e.g. Openmoko) || [http://fosdem.org/2010/schedule/events/gnustep_porting_quantumstep GNUstep Devroom]

|}
=== Attendants ===
Please add yourself to this list if you attend the event, independently of having any 'official' status:

{| border="1"
! Name
! in Brussels
! where to find me
! Comments

|-
| Nikolaus Schaller || Fri-Sun || [http://fosdem.org/2010/schedule/events/gnustep_porting_quantumstep GNUstep Devroom] || Handheld-Linux/Golden Delicious
|-
| Wim Vandeputte || Sat-Sun || [http://fosdem.org/2010/stands Makerbot RepRap] || KD85
|-
| John Lejeune || Sat-Sun || [http://fosdem.org/2010/stands Makerbot RepRap] || hackable-devices
|-
| Christ van Willegen || Fri-Sat || Around || Looking forward to getting my FR #1024-fixed!
|-
| David Reyes Samblas Martinez || ? || [http://www.fosdem.org/2010/schedule/devrooms/embedded Mobile & Embedded Devroom] || TuxBrain, NanoNote
|-
| Luca Vaudano || Fri-Sun || Around || Babiloo-efl
|-
| Jan Girlich || Fri-Sun || Around || running SHR unstable, having mic volume issues
|-
| Christophe Meurice (Think-Free) || Sat-Sun || Around || Qalee-project developer
|-
| [[user:Pieterc|Pieter Colpaert]] || Sat-Sun || Around || Finding the bastard who stole my FR
|-
| [[user:Jluis|JLuis]] || Fri-Sun || Around || using distcc on the neo
|-
| [[user:RuiSeabra|RuiSeabra]] || Wed-Sun || EDRi convention, + Around FOSDEM || hoping for #1024 fix as well :)
|-
| Deubeuliou || Fri-Sun || Around. maybe near gnome ? || hackable:1
|-
| [[user:Heinervdm|Heinervdm]] || Sun || Around || SHR
|}

= Ooops =
Well, MediaWiki separates [[Fosdem_2010]] from [[FOSDEM_2010]] and so we now have had two pages... Therefore I have copied the previous contents of Fosdem_2010 (in a more informal format) here. Please feel free to move content to the upper area:
== old ==
Fosdem is a great FOSS developers conference located in Brussels, Belgium. For those who don't know fosdem, check the site (scroll down). For those who do know fosdem: I (pieterc) have entered a dev room request (2009/10/27) for openmoko.

1/12: Update: dev room request was declined

This however, should not be a reason why we should be absent. There were a lot of devroom requests, and openmoko could be filed under: Mobile+Embedded devroom. So if someone has an idea, please bring it forward, and maybe we'll be able to bring it to a wider audience.

http://n2.nabble.com/FOSDEM-2010-Devroom-for-openmoko-declined-tp4097204p4097204.html

== Who will be there? ==
* [[User:pieterc|pieterc]] - for sure. I will be the contact person between FOSDEM and community.
* christophe ( Think-Free : qalee.org )
* Denis 'GNUtoo' Carikli ( small Openembedded contributor)
* [[User:jluis|jluis]]
* [[User:Mickey|Mickey (freesmartphone.org)]]
* [[User:Zeusone|zeusOne]]
* David Samblas (Tuxbrain.com)
* Victor Remolina (Tuxbrain.com)
* Julien 'Ainulindalë' Cassignol (Bearstech / SHR)
* Nikolaus Schaller http://www.handheld-linux.com (Golden Delicious Computers) - will have to share my presence at GNUstep http://wiki.gnustep.org/index.php/FOSDEM_2010
* [[User:RuiSeabra|RuiSeabra]] (hope I can go)
* Ghislain & Tine (BaseTrend - openmobile.nl)
* Niels Heyvaert (Tentative)
* Thomas HOCEDEZ (AstHrO @openmoko-fr.org)
* [[User:Tebra|Tebra]]
''add your name here''

== Thoughts... ==

add it here...

== links ==
[http://www.fosdem.org Official website of Fosdem 2010]

[http://n2.nabble.com/FOSDEM2010-tp3895254p3895254.html mailing list announcement ]

User:Warmcat

2009-12-26T17:39:37Z

Mickey:

Andy Green.

He gave love to the Openmoko's [[Kernel]] with the help of a group of programmers. He also took care the [[Kernel_branches|kernel branches]] used in the current development model.

His homepage is http://warmcat.com.

Fosdem 2010

2009-10-28T08:47:01Z

Mickey: /* Who will be there? */

Fosdem is a great FOSS developers conference located in Brussels, Belgium. For those who don't know fosdem, check the site (scroll down). For those who do know fosdem: I (pieterc) have entered a dev room request (2009/10/27) for openmoko.

== Who will be there? ==
* pieterc
* christophe ( Think-Free )
* Denis 'GNUtoo' Carikli(I hope I could come)
* [[User:jluis|jluis]]
* [[User:Mickey|Mickey (freesmartphone.org)]]
''add your name here''

== How to present openmoko ==

''How to present openmoko on fosdem to people who never heard of our project (I know, it's hardly possible)''

== Presentations ==

''if you want to do a presentation, add your idea here''

Presentations about current activities:
* SHR
* FSO
* Qalee
* Android for FR
* QtMoko
* GTA02-core
* Hardware mods
* Graphics acceleration
* How feasible would it be to run iPhone Apps?

== Brainstorming ==

''we will be able to have brainstorm sessions. About what would you like to have one? Add it here''

==Program==

''will be made available when we got more information''

== links ==
[http://www.fosdem.org Official website of Fosdem 2010]

[http://n2.nabble.com/FOSDEM2010-tp3895254p3895254.html mailing list announcement ]

Main Page

2009-10-13T10:43:30Z

Mickey: add link to fso / openmoko framework

{{Languages|Main Page}}
__NOTOC__
__NOEDITSECTION__[[Image:Neo front 3.gif|right]]
<div style="padding: 2.5ex; text-align: center; font: bold x-large sans">Openmoko™ - Open. Mobile. Free.</div>

'''Openmoko™''' is a project dedicated to delivering mobile phones with an [[Source Code|open source software stack]]. Openmoko is currently selling the [[Neo FreeRunner]] phone to advanced users and will start selling it to the general public as soon as the software is more developed.

* [[Introduction]]
* [[Why Openmoko|Why Openmoko?]]

===Get Involved===
Openmoko is a project driven by a community of passionate and intelligent volunteers. If you have the ability, please contribute to our cause. Openmoko's ambitions far exceed the resources available.

* [[Community Resources|Community Portal]]
* [[Gta02-core|Create a new hardware revision of the gta02 hardware]]
* [[Create User Manuals]] for [[Distributions]] and [[Applications]]
* Enhance the multi-device multi-vendor [http://www.freesmartphone.org FSO] middleware used as [[OpenmokoFramework]].

===How To Purchase===
The Neo FreeRunner is sold by various [[distributors]] around the world.

See [[Getting Openmoko]] for more information.

----

====Latest News====

{{News}}
[[News Archive|more news...]]

----

D-Bus

2009-09-12T10:48:29Z

Mickey: remove link to outdated page

Openmoko uses '''[http://www.freedesktop.org/wiki/DBus D-Bus]''', a [http://en.wikipedia.org/wiki/Middleware middleware] message bus system which provides a simple way for applications to talk to one another and to be available as services in the system. If the application providing the service is not running when a message is sent, the application will be started.

There are two separate busses:
*a system bus for root which runs whenever the phone is on
*a session bus which is started for the user when X starts

== Session bus services ==

These can at least be defined in /usr/share/dbus-1.0/services/ and /usr/share/dbus-1/services/

* org.gnome.evolution.dataserver.AddressBook
* org.gnome.evolution.dataserver.Calendar
* org.gnome.GConf
* ...

== System bus services ==

There is information about these in /etc/dbus-1/system.d/

* org.freesmartphone.*
* org.freedesktop.Avahi
* org.bluez.*
* ...

== Accessing the services ==

=== Command line ===

For simple uses, there's a command mdbus. Try
<pre>
mdbus -s
</pre>
to explore the DBus environment.

For example, to dial a number (using FSO milestone 3):
<pre>
mdbus -s org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device org.freesmartphone.GSM.Call.Initiate \'12345\' 'voice'
</pre>

=== Python ===

To use D-Bus in [[Python]], the package python-dbus needs to be compiled and installed. Note that since the interfaces change over time you might want to read the source code of zhone from git.freesmartphone.org to get examples of current API.

To dial a number:
<pre>
#!/usr/bin/env python
import dbus
bus = dbus.SystemBus()
gsm_device_obj = bus.get_object("org.freesmartphone.ogsmd", "/org/freesmartphone/GSM/Device")
gsm_call_iface = dbus.Interface(gsm_device_obj,'org.freesmartphone.GSM.Call')
proxy = bus.get_object("org.openmoko.Dialer", "/org/openmoko/Dialer")
gsm_call_iface.Initiate("12345", "voice")
</pre>

To run the program use the following:
<pre>
dbus-launch python my_program.py
</pre>

== See also ==
* [[OpenmokoFramework/mdbus]]

== External links ==
* [http://docs.freesmartphone.org/ DBus API documentation]
* [http://dbus.freedesktop.org/doc/dbus-python/api/ DBus Python API]
* [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html dbus-python tutorial]

[[Category:D-Bus| ]]

User talk:Mickey

2009-07-20T19:21:55Z

Mickey: /* Status Update 7 */

You're listed as one of the wiki admins -
Would it be possible to install the spam blacklist plugin - as described on http://www.mediawiki.org/wiki/Manual:Combating_spam?

The [http://svn.wikimedia.org/svnroot/mediawiki/trunk/extensions/SpamBlacklist/README README].

Rationale: [[Special:RecentChanges]]
--[[User:Speedevil|Speedevil]] 20:49, 10 June 2007 (CEST)

== Status Update 7 ==
Hi Mickey,
In OpenmokoFramework/Status Update 7 in section 3.4 image download link is broaken:
( http://downloads.freesmartphone.org/fso-stable/milestone5.5/ )
I have searched for some July FSO images on downloads.freesmartphone.org but wasn't able to find any. Can you fix this link?
--[[User:Leadman|LeadMan]] 08:23, 17 July 2009 (UTC)

Hi Leadman, it wasn't broken, it was just not uploaded yet. I always edit the Wiki some days before the release is published. Anyways, it's life now.
--[[User:Mickey|Mickey]] 20 July 2009 (UTC)

OpenmokoFramework/Status Update 7

2009-07-17T09:14:08Z

Mickey: /* Purpose */

<div style="text-align: center; font-weight: bold; font-size: x-large; margin-bottom:1em">Openmoko Framework Team Status Report 2009.7</div>

Hi guys! This is the seventh Openmoko Framework Team Status update, featuring our sixth milestone release and more.

For the general motivation, the goals, and the way we are doing our work, please see [[OpenmokoFramework]].

{{FSO}}

== People & Organization ==

You all should have heard by now that the FSO team is no longer under the hood of Openmoko. The current team still consists of Mickey, Jan, Daniel, and Stefan, however we pretty much sail under the flag of [http://www.freesmartphone.org freesmartphone.org] now. As such, this is the last official OpenmokoFramework status report -- future reports will appear elsewhere.

== DBus APIs ==

All the public DBus API are documented on the official [http://docs.freesmartphone.org freesmartphone.org API reference] site. XML-API files for generating language bindings are available from the [http://git.freesmartphone.org/?p=specs.git;a=tree;f=xml git tree].

The DBus APIs have received little updates and are pretty much considered stable for FSO-1. If your programming language of choice features integrating C libraries, then we recommend using [http://git.freesmartphone.org/?p=libfso-glib.git;a=summary libfso-glib] which handles all the details of dbus communication and ensures that the DBus API contract is respected.

== Implementations ==

'''Freesmartphone.org Framework Image -- 'In Transit' (Milestone V.5)'''

This is the sixth milestone release of the framework and the diagnostic application '[[Zhone]]'. While we announced that we are going to phase Zhone out as phone application, it remains an important diagnostic application, i.e. for GPS and GSM monitoring.

Framework milestones currently ships in the following form:

# fso-console-image: An FSO-compliant image featuring no user interface manager.
# fso-illume-image: An FSO-compliant image featuring the X-Window system with the Enlightenment-based Illume window manager.
# fso-zhone-image: An FSO-compliant image featuring the X-Window system with the Enlightenment-based Illume and the Zhone diagnostic applications.

Note that FSO milestones are not distributions per se, but rather demonstration images for the middleware release. Real distributions that are using FSO as [http://en.wikipedia.org/wiki/Middleware middleware] are:
* [[Om 2009|Openmoko 2009]]
* [[SHR]]
* [[Neovento]]
* [[QtMoko]]
* [[Debian]]
* [[Gentoo]]
* Several unreleased homebrewn...
===Purpose===

A flashable demonstration image that implements the freesmartphone.org APIs that can serve as the basis for mobile application development.

===Thanks===

Thanks to all our contributors, especially the testers and the people who build stuff on top of the freesmartphone.org APIs. Thanks, guys: You Rock!

=== What's new since Milestone V ===

'''Note: These are only the highlights. See the [http://git.freesmartphone.org gitweb] commit logs for the gory details...'''

* General:
** This is the first milestone release incorporating results from our [http://www.freesmartphone.org/index.php/Cornucopia Cornucopia] project -- the next generation reference implementation of the FSO APIs, this time in [http://www.vala-project.org Vala], which compiles to C. For those who write in Vala, we provide a .vapi file for libfso-glib.
** Added interactive loophole for live or post-mortem debugging via telnet.

* fsousaged
** Completely rewritten in Vala with drastically improved performance.
** The ousaged implementation (Python) has been deprecated, we strongly recommend integrators to no longer use this.

* ogsmd
** Improved support for the Freescale Neptune modems as appearing in the Motorola EZX series.
** Fully support the Qualcomm MSM modems as appearing in the HTC smartphone family, including the Touch Pro, the G1, etc.
** Added support for extended SMS properties, including SMS delivery reports.
** Fixed MCC and MNC presentation.
** Relaxed the PDU decoder to deal with sloppy encoded SMS.
** Status report messages are auto-acked now.
** Refresh network status after suspend.
** Added a cell database (This is *not* the final API, but a simple test to make cellhunter data available. Later this functionality will be exposed differently)
** Redesigned the low level AT command parser to cope with unsolicited responses woven in solicited responses.
** Improved datacall support.

* ogpsd
** Reintroduced Ephemeris and Almanac uploading.
** Fixed some bugs.

* ophoned
** Added Bluetooth headset support.

* odeviced
** Fixed heaps of bugs everywhere.

* oeventsd
** Bugfixes

* otimed
** Major bug fixes, especially for multi-zone countries.
** Improved configurability.

* opimd
** MAJOR overhaul thanks to Sebastian Krzyszkowiak!
** added new domain Calls (for phone log functionality)
** working basics of Contacts, Messages and Calls domains
** working Update/Delete methods and signals
** added new backends: SQLite-Contacts, SQLite-Messages, SQLite-Calls with full Add/Update/Delete support and ogsmd-Calls (handler)
** SIM-Messages-FSO and SIM-Contacts-FSO backends: listen to ReadyStatus and AuthStatus signal to init when possible automatically
** CSV-Contacts and SIM-Contacts-FSO backends: full Add/Update/Delete support
** SIM-Messages-FSO: full CSM and message receipts handling
** timestamps and timezones handling in Messages and Calls
** merging entries - you can store some data for the same contact on SIM backend, others on SQLite, and it'll be merged by opimd into one visible contact
** avoid duplicating entries on initing backend second time
** initing backends automatically at boot
** work on API - lot of new dbus calls (mostly for configuration)
** make lot of things configurable
** more error handling
** A LOT of bugfixes

* Cornucopia
** fsousaged: Completely done.
** fsodeviced: Completely done & in testing.
** fsogsmd: Waiting for async. dbus server support in Vala.

===Installation on Flash (for booting with U-Boot or Qi)===

# Grab a uImage and a .jffs2 for your device from freesmartphone.org's download [http://downloads.freesmartphone.org/fso-stable/milestone5.5/ section].
# Flash it to your [[Flashing the Neo 1973|Neo 1973 (om-gta01)]] or [[Flashing the Neo Freerunner|Neo FreeRunner (om-gta02)]] with [[Dfu-util| dfu-util]].
# Boot and wait until the Zhone main window appears.
# ''If the [[Zhone]] main window does not appear on first boot or stays with "connecting to dbus..." longer than 1 minute, then please reboot. The base system still has some problems with dbus starting for the first time''
# Read the [[FSO UI Tutorial]] and have fun. Note though that this has not been updated for this milestone yet (which looks a bit differently and has more features).

===Installation on SD (for booting with Qi)===

# Grab a tar.bz2 for your device from freesmartphone.org's download [http://downloads.freesmartphone.org/fso-stable/milestone5.5/ section].
# Extract it to a partition on the SD card with the tar utility.
# Rename the uImage file in /boot to uImage-GTA01.bin (for a Neo 1973) or uImage-GTA02.bin (for a FreeRunner).
# Insert the SD card, boot, and wait until the Zhone main window appears.
# ''If the [[Zhone]] main window does not appear on first boot or stays with "connecting to dbus..." longer than 1 minute, then please reboot. The base system still has some problems with dbus starting for the first time''
# Read the [[FSO UI Tutorial]] and have fun. Note though that this has not been updated for this milestone yet (which looks a bit differently and has more features).

===Feedback===

* Please provide feedback and comments for the dbus APIs. This is your chance to take an active role into shaping the application programming interface for all your forthcoming cool applications.

* Focus on using the services. Zhone is a diagnostic utility and not a phone application.

* The best way to interact with the framework is by exploring the dbus APIs. For this, you can use these two tools, which are already installed:
** [[OpenmokoFramework/mdbus|mdbus]] -- a dbus introspection and interaction utility,
** [[OpenmokoFramework/cli|cli-framework]] -- a python dbus command line interface.

* Before reporting bugs against the framework, please try with cli-framework to see whether it's really a problem of the framework or rather the UI (which gets much less attention from us).

* If you want to interact with the GSM modem, while the frameworkd is running, you can use [[OpenmokoFramework/mickeyterm|mickeyterm]] -- a MUXer-aware minimal terminal emulator.

===Best way to hand us debug logs===
# log in via ssh
# killall python
# edit /etc/frameworkd.conf and add to the frameworkd section:
## log_level = DEBUG
## log_to = file
## log_destination = /somewhere/where/you/have/space (preferably SD or NFS, etc.)
# Read our [http://git.freesmartphone.org/?p=framework.git;a=blob;f=conf/example/frameworkd.conf documented frameworkd.conf] configuration file to learn about the other options.
# relaunch frameworkd (/etc/init.d/frameworkd stop; /etc/init.d/frameworkd start)
# log in via ssh (yes, again)
# export DISPLAY=:0.0
# run your favourite client (SHR, zhone, cli-framework, ...)

Attach the logs to the tickets, please.

==What's next==

* More work on opimd.
* Moving towards FSO 2.0 reference implementation in Vala.
* Complete switch to fso-abyss.
* Connman integration.
* Streamlining Bluez4 Networking.
* More Device Support (G1, G2, Palm Pre).

==The Team==

Mickey, Jan, Daniel, Stefan.

[[Category:Community Update]]
[[Category:Framework]]

OpenmokoFramework/Status Update 7

2009-07-11T13:40:35Z

Mickey: /* What's next */

<div style="text-align: center; font-weight: bold; font-size: x-large; margin-bottom:1em">Openmoko Framework Team Status Report 2009.7</div>

Hi guys! This is the seventh Openmoko Framework Team Status update, featuring our sixth milestone release and more.

For the general motivation, the goals, and the way we are doing our work, please see [[OpenmokoFramework]].

{{FSO}}

== People & Organization ==

You all should have heard by now that the FSO team is no longer under the hood of Openmoko. The current team still consists of Mickey, Jan, Daniel, and Stefan, however we pretty much sail under the flag of [http://www.freesmartphone.org freesmartphone.org] now. As such, this is the last official OpenmokoFramework status report -- future reports will appear elsewhere.

== DBus APIs ==

All the public DBus API are documented on the official [http://docs.freesmartphone.org freesmartphone.org API reference] site. XML-API files for generating language bindings are available from the [http://git.freesmartphone.org/?p=specs.git;a=tree;f=xml git tree].

The DBus APIs have received little updates and are pretty much considered stable for FSO-1. If your programming language of choice features integrating C libraries, then we recommend using [http://git.freesmartphone.org/?p=libfso-glib.git;a=summary libfso-glib] which handles all the details of dbus communication and ensures that the DBus API contract is respected.

== Implementations ==

'''Freesmartphone.org Framework Image -- 'In Transit' (Milestone V.5)'''

This is the sixth milestone release of the framework and the diagnostic application 'Zhone'. While we announced that we are going to phase Zhone out as phone application, it remains an important diagnostic application, i.e. for GPS and GSM monitoring.

Framework milestones currently ships in the following form:

# fso-console-image: An FSO-compliant image featuring no user interface manager.
# fso-illume-image: An FSO-compliant image featuring the X-Window system with the Enlightenment-based Illume window manager.
# fso-zhone-image: An FSO-compliant image featuring the X-Window system with the Enlightenment-based Illume and the Zhone diagnostic applications.

Note that FSO milestones are not distributions per se, but rather demonstration images for the middleware release. Real distributions that are using FSO as middleware are:
* [[Om 2009|Openmoko 2009]]
* [[SHR]]
* [[Neovento]]
* [[QtMoko]]
* [[Debian]]
* [[Gentoo]]
* Several unreleased homebrewn...
===Purpose===

A flashable image that implements the freesmartphone.org APIs, serving as the basis for mobile application development.

===Thanks===

Thanks to all our contributors, especially the testers and the people who build stuff on top of the freesmartphone.org APIs. Thanks, guys: You Rock!

=== What's new since Milestone V ===

'''Note: These are only the highlights. See the [http://git.freesmartphone.org gitweb] commit logs for the gory details...'''

* General:
** This is the first milestone release incorporating results from our [http://www.freesmartphone.org/index.php/Cornucopia Cornucopia] project -- the next generation reference implementation of the FSO APIs, this time in [http://www.vala-project.org Vala], which compiles to C. For those who write in Vala, we provide a .vapi file for libfso-glib.
** Added interactive loophole for live or post-mortem debugging via telnet.

* fsousaged
** Completely rewritten in Vala with drastically improved performance.
** The ousaged implementation (Python) has been deprecated, we strongly recommend integrators to no longer use this.

* ogsmd
** Improved support for the Freescale Neptune modems as appearing in the Motorola EZX series.
** Fully support the Qualcomm MSM modems as appearing in the HTC smartphone family, including the Touch Pro, the G1, etc.
** Added support for extended SMS properties, including SMS delivery reports.
** Fixed MCC and MNC presentation.
** Relaxed the PDU decoder to deal with sloppy encoded SMS.
** Status report messages are auto-acked now.
** Refresh network status after suspend.
** Added a cell database.
** Redesigned the low level AT command parser to cope with unsolicited responses woven in solicited responses.
** Improved datacall support.

* ogpsd
** Reintroduced Ephemeris and Almanac uploading.
** Fixed some bugs.

* ophoned
** Added Bluetooth headset support.

* odeviced
** Fixed heaps of bugs everywhere.

* oeventsd
** Bugfixes

* otimed
** Major bug fixes, especially for multi-zone countries.
** Improved configurability.

* opimd
** MAJOR overhaul thanks to Sebastian Krzyszkowiak!
** added new domain Calls (for phone log functionality)
** working basics of Contacts, Messages and Calls domains
** working Update/Delete methods and signals
** added new backends: SQLite-Contacts, SQLite-Messages, SQLite-Calls with full Add/Update/Delete support and ogsmd-Calls (handler)
** SIM-Messages-FSO and SIM-Contacts-FSO backends: listen to ReadyStatus and AuthStatus signal to init when possible automatically
** CSV-Contacts and SIM-Contacts-FSO backends: full Add/Update/Delete support
** SIM-Messages-FSO: full CSM and message receipts handling
** timestamps and timezones handling in Messages and Calls
** merging entries - you can store some data for the same contact on SIM backend, others on SQLite, and it'll be merged by opimd into one visible contact
** avoid duplicating entries on initing backend second time
** initing backends automatically at boot
** work on API - lot of new dbus calls (mostly for configuration)
** make lot of things configurable
** more error handling
** A LOT of bugfixes

* Cornucopia
** fsousaged: Completely done.
** fsodeviced: Completely done & in testing.
** fsogsmd: Waiting for async. dbus server support in Vala.

===Installation on Flash (for booting with U-Boot or Qi)===

# Grab a uImage and a .jffs2 for your device from freesmartphone.org's download [http://downloads.freesmartphone.org/fso-stable/milestone5.5/ section].
# Flash it to your [[Flashing the Neo 1973|Neo 1973 (om-gta01)]] or [[Flashing the Neo Freerunner|Neo FreeRunner (om-gta02)]] with [[Dfu-util| dfu-util]].
# Boot and wait until the Zhone main window appears.
# ''If the [[Zhone]] main window does not appear on first boot or stays with "connecting to dbus..." longer than 1 minute, then please reboot. The base system still has some problems with dbus starting for the first time''
# Read the [[FSO UI Tutorial]] and have fun. Note though that this has not been updated for this milestone yet (which looks a bit differently and has more features).

===Installation on SD (for booting with Qi)===

# Grab a tar.bz2 for your device from freesmartphone.org's download [http://downloads.freesmartphone.org/fso-stable/milestone5.5/ section].
# Extract it to a partition on the SD card with the tar utility.
# Rename the uImage file in /boot to uImage-GTA01.bin (for a Neo 1973) or uImage-GTA02.bin (for a FreeRunner).
# Insert the SD card, boot, and wait until the Zhone main window appears.
# ''If the [[Zhone]] main window does not appear on first boot or stays with "connecting to dbus..." longer than 1 minute, then please reboot. The base system still has some problems with dbus starting for the first time''
# Read the [[FSO UI Tutorial]] and have fun. Note though that this has not been updated for this milestone yet (which looks a bit differently and has more features).

===Feedback===

* Please provide feedback and comments for the dbus APIs. This is your chance to take an active role into shaping the application programming interface for all your forthcoming cool applications.

* Focus on using the services. Zhone is a diagnostic utility and not a phone application.

* The best way to interact with the framework is by exploring the dbus APIs. For this, you can use these two tools, which are already installed:
** [[OpenmokoFramework/mdbus|mdbus]] -- a dbus introspection and interaction utility,
** [[OpenmokoFramework/cli|cli-framework]] -- a python dbus command line interface.

* Before reporting bugs against the framework, please try with cli-framework to see whether it's really a problem of the framework or rather the UI (which gets much less attention from us).

* If you want to interact with the GSM modem, while the frameworkd is running, you can use [[OpenmokoFramework/mickeyterm|mickeyterm]] -- a MUXer-aware minimal terminal emulator.

===Best way to hand us debug logs===
# log in via ssh
# killall python
# edit /etc/frameworkd.conf and add to the frameworkd section:
## log_level = DEBUG
## log_to = file
## log_destination = /somewhere/where/you/have/space (preferably SD or NFS, etc.)
# Read our [http://git.freesmartphone.org/?p=framework.git;a=blob;f=conf/example/frameworkd.conf documented frameworkd.conf] configuration file to learn about the other options.
# relaunch frameworkd (/etc/init.d/frameworkd stop; /etc/init.d/frameworkd start)
# log in via ssh (yes, again)
# export DISPLAY=:0.0
# run your favourite client (SHR, zhone, cli-framework, ...)

Attach the logs to the tickets, please.

==What's next==

* More work on opimd.
* Moving towards FSO 2.0 reference implementation in Vala.
* Complete switch to fso-abyss.
* Connman integration.
* Streamlining Bluez4 Networking.
* More Device Support (G1, G2, Palm Pre).

==The Team==

Mickey, Jan, Daniel, Stefan.

[[Category:Community Update]]
[[Category:Framework]]

OpenmokoFramework/Status Update 7

2009-07-11T13:29:19Z

Mickey: /* Installation */

<div style="text-align: center; font-weight: bold; font-size: x-large; margin-bottom:1em">Openmoko Framework Team Status Report 2009.7</div>

Hi guys! This is the seventh Openmoko Framework Team Status update, featuring our sixth milestone release and more.

For the general motivation, the goals, and the way we are doing our work, please see [[OpenmokoFramework]].

{{FSO}}

== People & Organization ==

You all should have heard by now that the FSO team is no longer under the hood of Openmoko. The current team still consists of Mickey, Jan, Daniel, and Stefan, however we pretty much sail under the flag of [http://www.freesmartphone.org freesmartphone.org] now. As such, this is the last official OpenmokoFramework status report -- future reports will appear elsewhere.

== DBus APIs ==

All the public DBus API are documented on the official [http://docs.freesmartphone.org freesmartphone.org API reference] site. XML-API files for generating language bindings are available from the [http://git.freesmartphone.org/?p=specs.git;a=tree;f=xml git tree].

The DBus APIs have received little updates and are pretty much considered stable for FSO-1. If your programming language of choice features integrating C libraries, then we recommend using [http://git.freesmartphone.org/?p=libfso-glib.git;a=summary libfso-glib] which handles all the details of dbus communication and ensures that the DBus API contract is respected.

== Implementations ==

'''Freesmartphone.org Framework Image -- 'In Transit' (Milestone V.5)'''

This is the sixth milestone release of the framework and the diagnostic application 'Zhone'. While we announced that we are going to phase Zhone out as phone application, it remains an important diagnostic application, i.e. for GPS and GSM monitoring.

Framework milestones currently ships in the following form:

# fso-console-image: An FSO-compliant image featuring no user interface manager.
# fso-illume-image: An FSO-compliant image featuring the X-Window system with the Enlightenment-based Illume window manager.
# fso-zhone-image: An FSO-compliant image featuring the X-Window system with the Enlightenment-based Illume and the Zhone diagnostic applications.

Note that FSO milestones are not distributions per se, but rather demonstration images for the middleware release. Real distributions that are using FSO as middleware are:
* [[Om 2009|Openmoko 2009]]
* [[SHR]]
* [[Neovento]]
* [[QtMoko]]
* [[Debian]]
* [[Gentoo]]
* Several unreleased homebrewn...
===Purpose===

A flashable image that implements the freesmartphone.org APIs, serving as the basis for mobile application development.

===Thanks===

Thanks to all our contributors, especially the testers and the people who build stuff on top of the freesmartphone.org APIs. Thanks, guys: You Rock!

=== What's new since Milestone V ===

'''Note: These are only the highlights. See the [http://git.freesmartphone.org gitweb] commit logs for the gory details...'''

* General:
** This is the first milestone release incorporating results from our [http://www.freesmartphone.org/index.php/Cornucopia Cornucopia] project -- the next generation reference implementation of the FSO APIs, this time in [http://www.vala-project.org Vala], which compiles to C. For those who write in Vala, we provide a .vapi file for libfso-glib.
** Added interactive loophole for live or post-mortem debugging via telnet.

* fsousaged
** Completely rewritten in Vala with drastically improved performance.
** The ousaged implementation (Python) has been deprecated, we strongly recommend integrators to no longer use this.

* ogsmd
** Improved support for the Freescale Neptune modems as appearing in the Motorola EZX series.
** Fully support the Qualcomm MSM modems as appearing in the HTC smartphone family, including the Touch Pro, the G1, etc.
** Added support for extended SMS properties, including SMS delivery reports.
** Fixed MCC and MNC presentation.
** Relaxed the PDU decoder to deal with sloppy encoded SMS.
** Status report messages are auto-acked now.
** Refresh network status after suspend.
** Added a cell database.
** Redesigned the low level AT command parser to cope with unsolicited responses woven in solicited responses.
** Improved datacall support.

* ogpsd
** Reintroduced Ephemeris and Almanac uploading.
** Fixed some bugs.

* ophoned
** Added Bluetooth headset support.

* odeviced
** Fixed heaps of bugs everywhere.

* oeventsd
** Bugfixes

* otimed
** Major bug fixes, especially for multi-zone countries.
** Improved configurability.

* opimd
** MAJOR overhaul thanks to Sebastian Krzyszkowiak!
** added new domain Calls (for phone log functionality)
** working basics of Contacts, Messages and Calls domains
** working Update/Delete methods and signals
** added new backends: SQLite-Contacts, SQLite-Messages, SQLite-Calls with full Add/Update/Delete support and ogsmd-Calls (handler)
** SIM-Messages-FSO and SIM-Contacts-FSO backends: listen to ReadyStatus and AuthStatus signal to init when possible automatically
** CSV-Contacts and SIM-Contacts-FSO backends: full Add/Update/Delete support
** SIM-Messages-FSO: full CSM and message receipts handling
** timestamps and timezones handling in Messages and Calls
** merging entries - you can store some data for the same contact on SIM backend, others on SQLite, and it'll be merged by opimd into one visible contact
** avoid duplicating entries on initing backend second time
** initing backends automatically at boot
** work on API - lot of new dbus calls (mostly for configuration)
** make lot of things configurable
** more error handling
** A LOT of bugfixes

* Cornucopia
** fsousaged: Completely done.
** fsodeviced: Completely done & in testing.
** fsogsmd: Waiting for async. dbus server support in Vala.

===Installation on Flash (for booting with U-Boot or Qi)===

# Grab a uImage and a .jffs2 for your device from freesmartphone.org's download [http://downloads.freesmartphone.org/fso-stable/milestone5.5/ section].
# Flash it to your [[Flashing the Neo 1973|Neo 1973 (om-gta01)]] or [[Flashing the Neo Freerunner|Neo FreeRunner (om-gta02)]] with [[Dfu-util| dfu-util]].
# Boot and wait until the Zhone main window appears.
# ''If the [[Zhone]] main window does not appear on first boot or stays with "connecting to dbus..." longer than 1 minute, then please reboot. The base system still has some problems with dbus starting for the first time''
# Read the [[FSO UI Tutorial]] and have fun. Note though that this has not been updated for this milestone yet (which looks a bit differently and has more features).

===Installation on SD (for booting with Qi)===

# Grab a tar.bz2 for your device from freesmartphone.org's download [http://downloads.freesmartphone.org/fso-stable/milestone5.5/ section].
# Extract it to a partition on the SD card with the tar utility.
# Rename the uImage file in /boot to uImage-GTA01.bin (for a Neo 1973) or uImage-GTA02.bin (for a FreeRunner).
# Insert the SD card, boot, and wait until the Zhone main window appears.
# ''If the [[Zhone]] main window does not appear on first boot or stays with "connecting to dbus..." longer than 1 minute, then please reboot. The base system still has some problems with dbus starting for the first time''
# Read the [[FSO UI Tutorial]] and have fun. Note though that this has not been updated for this milestone yet (which looks a bit differently and has more features).

===Feedback===

* Please provide feedback and comments for the dbus APIs. This is your chance to take an active role into shaping the application programming interface for all your forthcoming cool applications.

* Focus on using the services. Zhone is a diagnostic utility and not a phone application.

* The best way to interact with the framework is by exploring the dbus APIs. For this, you can use these two tools, which are already installed:
** [[OpenmokoFramework/mdbus|mdbus]] -- a dbus introspection and interaction utility,
** [[OpenmokoFramework/cli|cli-framework]] -- a python dbus command line interface.

* Before reporting bugs against the framework, please try with cli-framework to see whether it's really a problem of the framework or rather the UI (which gets much less attention from us).

* If you want to interact with the GSM modem, while the frameworkd is running, you can use [[OpenmokoFramework/mickeyterm|mickeyterm]] -- a MUXer-aware minimal terminal emulator.

===Best way to hand us debug logs===
# log in via ssh
# killall python
# edit /etc/frameworkd.conf and add to the frameworkd section:
## log_level = DEBUG
## log_to = file
## log_destination = /somewhere/where/you/have/space (preferably SD or NFS, etc.)
# Read our [http://git.freesmartphone.org/?p=framework.git;a=blob;f=conf/example/frameworkd.conf documented frameworkd.conf] configuration file to learn about the other options.
# relaunch frameworkd (/etc/init.d/frameworkd stop; /etc/init.d/frameworkd start)
# log in via ssh (yes, again)
# export DISPLAY=:0.0
# run your favourite client (SHR, zhone, cli-framework, ...)

Attach the logs to the tickets, please.

==What's next==

* More work on opimd.
* Moving towards FSO 2.0 reference implementation in Vala.
* Complete switch to fso-abyss.
* Connman integration.
* Bluetooth4 Networking.
* More Device Support (G1, G2, Palm Pre).

==The Team==

Mickey, Jan, Daniel, Stefan.

[[Category:Community Update]]
[[Category:Framework]]

OpenmokoFramework/Status Update 7

2009-07-09T15:56:23Z

Mickey: update what we have done

<div style="text-align: center; font-weight: bold; font-size: x-large; margin-bottom:1em">Openmoko Framework Team Status Report 2009.7</div>

Hi guys! This is the seventh Openmoko Framework Team Status update, featuring our sixth milestone release and more.

For the general motivation, the goals, and the way we are doing our work, please see [[OpenmokoFramework]].

{{FSO}}

== People & Organization ==

You all should have heard by now that the FSO team is no longer under the hood of Openmoko. The current team still consists of Mickey, Jan, Daniel, and Stefan, however we pretty much sail under the flag of [http://www.freesmartphone.org freesmartphone.org] now. As such, this is the last official OpenmokoFramework status report -- future reports will appear elsewhere.

== DBus APIs ==

All the public DBus API are documented on the official [http://docs.freesmartphone.org freesmartphone.org API reference] site. XML-API files for generating language bindings are available from the [http://git.freesmartphone.org/?p=specs.git;a=tree;f=xml git tree].

The DBus APIs have received little updates and are pretty much considered stable for FSO-1. If your programming language of choice features integrating C libraries, then we recommend using [http://git.freesmartphone.org/?p=libfso-glib.git;a=summary libfso-glib] which handles all the details of dbus communication and ensures that the DBus API contract is respected.

== Implementations ==

'''Freesmartphone.org Framework Image -- 'In Transit' (Milestone V.5)'''

This is the sixth milestone release of the framework and the diagnostic application 'Zhone'. While we announced that we are going to phase Zhone out as phone application, it remains an important diagnostic application, i.e. for GPS and GSM monitoring.

Framework milestones currently ships in the following form:

# fso-console-image: An FSO-compliant image featuring no user interface manager.
# fso-illume-image: An FSO-compliant image featuring the X-Window system with the Enlightenment-based Illume window manager.
# fso-zhone-image: An FSO-compliant image featuring the X-Window system with the Enlightenment-based Illume and the Zhone diagnostic applications.

Note that FSO milestones are not distributions per se, but rather demonstration images for the middleware release. Real distributions that are using FSO as middleware are:
* Openmoko 2009
* SHR
* Neovento
* QtMoko
* Debian
* Gentoo
* Several unreleased homebrewn...
===Purpose===

A flashable image that implements the freesmartphone.org APIs, serving as the basis for mobile application development.

===Thanks===

Thanks to all our contributors, especially the testers and the people who build stuff on top of the freesmartphone.org APIs. Thanks, guys: You Rock!

=== What's new since Milestone V ===

'''Note: These are only the highlights. See the [http://git.freesmartphone.org gitweb] commit logs for the gory details...'''

* General:
** This is the first milestone release incorporating results from our [http://www.freesmartphone.org/index.php/Cornucopia Cornucopia] project -- the next generation reference implementation of the FSO APIs, this time in [http://www.vala-project.org Vala], which compiles to C. For those who write in Vala, we provide a .vapi file for libfso-glib.
** Added interactive loophole for live or post-mortem debugging via telnet.

* fsousaged
** Completely rewritten in Vala with drastically improved performance.
** The ousaged implementation (Python) has been deprecated, we strongly recommend integrators to no longer use this.

* ogsmd
** Improved support for the Freescale Neptune modems as appearing in the Motorola EZX series.
** Fully support the Qualcomm MSM modems as appearing in the HTC smartphone family, including the Touch Pro, the G1, etc.
** Added support for extended SMS properties, including SMS delivery reports.
** Fixed MCC and MNC presentation.
** Relaxed the PDU decoder to deal with sloppy encoded SMS.
** Status report messages are auto-acked now.
** Refresh network status after suspend.
** Added a cell database.
** Redesigned the low level AT command parser to cope with unsolicited responses woven in solicited responses.
** Improved datacall support.

* ogpsd
** Reintroduced Ephemeris and Almanac uploading.
** Fixed some bugs.

* ophoned
** Added Bluetooth headset support.

* odeviced
** Fixed heaps of bugs everywhere.

* oeventsd
** Bugfixes

* otimed
** Major bug fixes, especially for multi-zone countries.
** Improved configurability.

* opimd
** MAJOR overhaul thanks to Sebastian Krzyszkowiak!

* Cornucopia
** fsousaged: Completely done.
** fsodeviced: Completely done & in testing.
** fsogsmd: Waiting for async. dbus server support in Vala.

===Installation===

# Grab a uImage and a .jffs2 for your device from freesmartphone.org's download [http://downloads.freesmartphone.org/fso-stable/milestone5/ section].
# Flash it to your [[Flashing the Neo 1973|Neo 1973 (om-gta01)]] or [[Flashing the Neo Freerunner|Neo FreeRunner (om-gta02)]] with [[Dfu-util| dfu-util]].
# Boot and wait until the Zhone main window appears.
# ''If the [[Zhone]] main window does not appear on first boot or stays with "connecting to dbus..." longer than 1 minute, then please reboot. The base system still has some problems with dbus starting for the first time''
# Read the [[FSO UI Tutorial]] and have fun. Note though that this has not been updated for this milestone yet (which looks a bit differently and has more features).

===Feedback===

* Please provide feedback and comments for the dbus APIs. This is your chance to take an active role into shaping the application programming interface for all your forthcoming cool applications.

* Focus on using the services. Zhone is a diagnostic utility and not a phone application.

* The best way to interact with the framework is by exploring the dbus APIs. For this, you can use these two tools, which are already installed:
** [[OpenmokoFramework/mdbus|mdbus]] -- a dbus introspection and interaction utility,
** [[OpenmokoFramework/cli|cli-framework]] -- a python dbus command line interface.

* Before reporting bugs against the framework, please try with cli-framework to see whether it's really a problem of the framework or rather the UI (which gets much less attention from us).

* If you want to interact with the GSM modem, while the frameworkd is running, you can use [[OpenmokoFramework/mickeyterm|mickeyterm]] -- a MUXer-aware minimal terminal emulator.

===Best way to hand us debug logs===
# log in via ssh
# killall python
# edit /etc/frameworkd.conf and add to the frameworkd section:
## log_level = DEBUG
## log_to = file
## log_destination = /somewhere/where/you/have/space (preferably SD or NFS, etc.)
# Read our [http://git.freesmartphone.org/?p=framework.git;a=blob;f=conf/example/frameworkd.conf documented frameworkd.conf] configuration file to learn about the other options.
# relaunch frameworkd (/etc/init.d/frameworkd stop; /etc/init.d/frameworkd start)
# log in via ssh (yes, again)
# export DISPLAY=:0.0
# run your favourite client (SHR, zhone, cli-framework, ...)

Attach the logs to the tickets, please.

==What's next==

* More work on opimd.
* Moving towards FSO 2.0 reference implementation in Vala.
* Complete switch to fso-abyss.
* Connman integration.
* Bluetooth4 Networking.
* More Device Support (G1, G2, Palm Pre).

==The Team==

Mickey, Jan, Daniel, Stefan.

[[Category:Community Update]]
[[Category:Framework]]

OpenmokoFramework/Status Update 7

2009-07-09T14:12:45Z

Mickey: /* Implementations */

OpenmokoFramework/Status Update 7

2009-07-09T14:12:03Z

Mickey: /* DBus APIs */

OpenmokoFramework/Status Update 7

2009-07-09T14:09:13Z

Mickey: /* People & Organization */

OpenmokoFramework/Status Update 7

2009-07-09T14:08:23Z

Mickey: /* What's new since Milestone V */

OpenmokoFramework/Status Update 7

2009-07-09T10:48:07Z

Mickey: /* Implementations */

OpenmokoFramework/Status Update 7

2009-07-09T10:45:21Z

Mickey: start with status update 7 for milestone 5.5

Who is Who

2009-05-28T09:27:44Z

Mickey:

''Note: This is severly outdated. Most of the people listed here as officials do not work for Openmoko anymore.''

If you subscribe to a mailing list, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something?

So I propose to fill out this list to help people get to know each other.

== Officials members of the Openmoko Team ==

The Openmoko team (alphabetical by last name):
{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"
! Name !! email !! Wiki username !! IRC nickname !! Position
|-
| Allen Chang || || {{user|allen_chang}} || || GTA Hardware Engineer ('''Left Openmoko''')
|-
| Andy Green || ''andy'' at openmoko dot ''com'' || {{user|warmcat}} || agreen || Software Developer/kernel maintainer ('''Left Openmoko'''. Here for archives.)
|-
| Anthony Chang || || || || Software Developer ('''Left Openmoko''')
|-
| Candy Chou || || {{user|candy_chou}} || || GTA/HXD Hardware Engineer ('''Left Openmoko''')
|-
| Dkay Chen || || {{user|dkay_chen}} || || GTA/HXD Hardware Engineer ('''Left Openmoko''')
|-
| Jeremy Chang || || || || Software Developer ('''Left Openmoko''')
|-
| Jollen Chen || || || || Marketing('''Left Openmoko''')
|-
| Tick Chen || || || || Software Developer('''Left Openmoko''')
|-
| Guillaume 'Charlie' Chereau || ''charlie'' at openmoko dot ''org'' || || || ('''Left Openmoko'''. Here for archives.)
|-
| Julian Chu || ''julian_chu'' at openmoko dot ''com'' || || || Software Developer ('''Left Openmoko''')
|-
| Holger 'Zecke' Freyther || ''zecke'' at openmoko dot ''org'' || || || Software Developer ('''Left Openmoko''')
|-
| Graeme Gregory || ''graeme'' at openmoko dot ''org'' || || XorA || ('''Left Openmoko''')
|-
| Carsten Haitzler || ''raster'' at openmoko dot ''org'' || || raster || ('''Left Openmoko'''. Here for archives.)
|-
| Matt Hsu || || {{user|Matt}} || || Software Developer ('''Left Openmoko''')
|-
| Wendy Hung || || || || Testing ('''Left Openmoko''')
|-
| Regina Kim || || || || Testing ('''Left Openmoko''')
|-
| William Lai || ''will'' at openmoko dot ''com'' || || || Design Team Project Manager
|-
| Michael 'Mickey' Lauer || || {{user|Mickey}} || || Software Developer ('''Left Openmoko'''. Freelancer - maintains FSO.)
|-
| John Lee || || || || Software Developer ('''Left Openmoko''')
|-
| Tim Lee || || {{user|Tim}} || || Hardware Manager
|-
| Marek Lindner || ''marek'' at openmoko dot ''com'' || || || Software Developer ('''Left Openmoko''')
|-
| Xiangfu Liu || ''xiangfu'' at openmoko dot ''org'' || {{user|liuxf}} || || Software Developer ('''Left Openmoko''')
|-
| Jan 'Shoragan' Luebbe || || || || Openmoko student (part-time) ('''Left Openmoko''')
|-
| Steven Mosher || || {{user|steve}} || || Vice President of Marketing
|-
| Sean Moss-Pultz || || {{user|Sean}} || || CEO
|-
| Shawn Lin || || {{user|shawn_lin}} || || RF Engineer('''Left Openmoko''')
|-
| Joerg Reisenweber || || {{user|jOERG}} || || Hardware Engineer ('''Left Openmoko'''. Here for archives.)
|-
| Michael Shiloh || ''michael'' at openmoko dot ''org'' || {{user|Michaelshiloh}} || || Head of Developer Relations ('''Left Openmoko'''. Here for archives.)
|-
| Werner Almesberger || ''werner'' at openmoko dot ''org'' || || || ('''Left Openmoko'''. Here for archives.)
|-
| Wolfgang Spraul || ''wolfgang'' at openmoko dot ''com'' || || || Vice President of Engineering ('''Left Openmoko''')
|-
| Joachim Steiger || ''roh'' at openmoko dot ''org'' || {{user|Roh}} || roh || Central Services ('''Left Openmoko'''. Here for archives.)
|-
| Teenie Hung || || {{user|teenie_hung}} || || Operations Head ('''Left Openmoko''')
|-
| Harry Tsai || ''tsaiharry'' at gmail dot ''com'' || || || long time ago he was Vice President of Sales in Openmoko, but that is past. ('''Left Openmoko'''. Here for archives.)
|-
| Neng-Yu 'Tony' Tu || || {{user|Tony Tu}} || || Project manager (gta01/02), software developer ('''Left Openmoko'''. Here for archives.)
|-
| Brenda Wang || ''brenda_wang'' at openmoko dot ''com'' || {{user|Coolcat}} || || Used to Wiki editor . volunteer now. ('''Left Openmoko''')
|-
| Harald Welte || ''laforge'' at openmoko dot ''org'' || {{user|HaraldWelte}} || LaF0rge || ('''Left Openmoko'''. Here for archives.)
|-
| Daniel 'Alphaone' Willmann || || {{user|DanielWillmann}} || || Software Developer ('''Left Openmoko'''. Here for archives.)
|-
| Thomas Wood || || {{user|ThomasWood}} || || Was hired as part of OpenedHand. ('''No longer employed by Openmoko''')
|-
| OLV Wu || ''olv'' at openmoko dot ''org'' || || || Software Developer ('''Left Openmoko''')
|-
| Erin Yeh || ''erin_yueh'' at openmoko dot ''org''||{{user|erin}} || || Software Developer ('''Left Openmoko''')
|-
| Mirko Lindner || ''mirko'' at openmoko dot ''com''||{{user|Vegyraupe}} || mirko-paroli || Software Developer (om2009/paroli) ('''Left Openmoko''')
|-
| Angus Ainslie || ''nytowl'' at openmoko dot ''org''||{{user|Nytowl}} || nytowl || Distribution maintainer (om2009) ('''Left Openmoko''')
|-
| Ray Chao || ''ray_chao'' at openmoko dot ''org''||{{user|Ray}} || jc || System Administrator ('''Left Openmoko''')
|-
| Chelsea Wei || ''chelsea'' at openmoko dot ''com''||{{user|Chelsea}} || || ('''Left Openmoko''')
|}

== Prominent community members ==

Only add people who made a significant contribution to the Openmoko community.

{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"
! Name !! email !! Wiki username !! IRC nickname !! Position
|-
| Lorn Potter || ''lpotter'' at ''trolltech'' dot ''com'' || || lpotter || Qtopia developer
|-
| Rod Whitby || || {{user|RodWhitby}} || rwhitby || [[MokoMakefile]] author
|}

[[Category:Openmoko Inc]]

Neo FreeRunner Hardware

2009-05-13T17:33:40Z

Mickey: fix standby time

{{Languages|Neo FreeRunner GTA02 Hardware}}

{{gta02menu}}

The [[Neo FreeRunner]] phone is the second hardware platform to take advantage of the Openmoko software stack. You can find specifications of the hardware by reviewing this introduction page and the pages in the category as shown at the bottom of this page.

For basic details please see the Customer-oriented specifications.

=Photos=
<gallery>
Image:Gta02a5 pcba cs.JPG|component (back) side NOTE: GTA02 A5 PCBA Component Side photo
Image:Gta02a5 pcba ps.JPG|display (top) side NOTE: GTA02 A5 PCBA Print Side photo
Image:GTA02 A5 PCB CS.jpg|component (back) side NOTE: GTA02 A5 PCB Component Side photo
Image:GTA02 A5 PCB PS.jpg|display (top) side NOTE: GTA02 A5 PCB Print Side photo
Image:SimpleComponentDiagram.jpg|Simplified Hardware Component Diagram
</gallery>

=Features=
*Display- Topply o2.8, 480 x 640 pixels, VGA, 200 NIT minimum, resistance type touch

*User Interface Navigation- Touch screen on LCD, 2 control “buttons”, 1 Power button, 1 Aux for 911 emergency call

*Built-in 802.11b/g Radio (Atheros chipset AR6001 Flash version)

*Built-in Bluetooth 2.0 + EDR (CSR and support PCM audio , BC4 firmware version)

*Built-in 2D/3D graphics acceleration chip (S-Media 3362)

*2 built-in Tri-Axis sensors (ST accelerometer LIS302DL)

*Built-in GPS Radio – -130 dBm with internal antenna, -157 dBm tracking on chipset specification, TTFF under 40 seconds with -130 dBm signal strength, and tracking (u-Blox)

*Antenna – Specialized antenna for best in hand hold GPS, GPRS and Wi-Fi/Bluetooth performance are required, -105dBm on receiving, Tx 30dbm+2 on GSM

*External Antennae – MMCX GPS connector

*GPRS Radio –GSM/GPRS radio. A Pre-PTCRB certified module will be preferred

*Linux – Linux kernel 2.6.24 or later Openmoko kernel

*USB - Client and Host-mode switchable (to be used for software downloading), provide host 5V power

*Power- Normal mode power will be via 1200 mAh battery with built-in coulomb counter, could charge via specialized charger. Internal Lithium Ion or Lithium Polymer battery will keep device in standby mode. Battery life (Approximation/Ideal Target) Standby time 70h Hrs (GSM) Talk time (Backlight off) Up to 3-4 hrs(GSM)

*LED- LED indicator under Aux/Power button key

=Hardware Specification=

[http://downloads.openmoko.org/developer/schematics/GTA02/Schematics_Freerunner/GTA02_A5-7cumulative_public_RC0.pdf Full schematics] is available.

===Hardware Electrical===

*400/500 MHz Samsung 2442B Processor/SOC (400 minimum, ARM920T core, ARMv4T)
*Unbrickable dual Boot code in NAND FLASH and 2MB NOR FLASH
*128 MB SDRAM total, 64 MB CPU internal, 64 MB external
*256MB NAND Flash MCP package.

=== Display ===
* Topploy VGA, 16 bit color depth
* resolution: 480 x 640 pixels
* size: 43mm x 58mm (1.7” x 2.27”)
* diagonal: 72.2mm (2.84”)
* Transmissive display: good readability in high ambient light is essential
* White LED backlight. Required brightness is 200 NIT minimum.
* Resistance type touch panel.

=== WiFi 802.11 b/g transceiver ===
*Must have GPL support source or GPL compatible policy
*TX power at 11 Mbps: 13 dBm minimum
*RX sensitivity at 11 Mbps: -89 dBm desired, -83 dBm minimum
*AP mode desirable, not required
*WEP and WPA supported
*Atheros preferred because of its GPL policy

=== Serial interfaces (UART) ===
*Three serial interfaces are required
*Console
*A-GPS or GPS
*GSM/GPRS

=== Accelerometer ===
* 2x accelerometer required
* Could support interrupt while suspend or power save mode
* 3 axis sensing

=== A-GPS ===
*GPS chipset receiver and antenna
*Sensitivity at Antenna port: -157 dBm tracking on chipset specification
*LNA and SAW filter for maximum interference protection
*Cold start time to first fix: 40 sec typical at -130 dBm, 60 sec max
*Must support GPL for Assist-GPS function with open API
*Industry quality GPS
*Could fit in GTA01 GPS area on the PCB

=== GPS Antenna Performance ===
*Antenna is passive and internal; 15 mm x 15 mm ceramic patch is nominal design
*Antenna LNA and SAW filter are required to meet GPS performance
*15 mm square ground plane (minimum 1 mm ground border around patch) (TBA)
*There will be one external GPS antenna connector (MMCX)
*C/N ratio should higher than 35 on production testing

=== Buttons ===
*Touch screen over LCD is primary data entry mechanism
*Two “hard” buttons: Power button (on side of Neo1973) is a mechanical switch actuated by a plastic pushbutton in a hole in the housing. Aux (911) button on the top of the device, All two of these buttons, when pushed by the operator, are binary inputs (on/off or pressed/not pressed) to the software. The effect of each button is determined by the application software in the device
*Buttons may need to be backlit
*50000 cycles on hardware specification

=== Sound outputs ===
*Speaker in box (need good volume and acoustic behavior in noisy environments)
*Audio is monophonic
*Max volume: 100 dB at 5 cm to assure good performance in environment.
*Support earphone with mic by jack

=== Power Design Requirements===
*Software-based power management unit preferred
*NXP PCF series preferred
*Need support charge from USB function
*Need support powered by USB function
*Power switch: Neo1973 will have a power switch, for power on/off and suspend
* Power/Aux switch must be backlit
*Switch controls whether device is running or suspended by presses of the switch
*Switch does not shut off the power; it only suspends/resumes the device
*Internal Li-Ion or Li-Polymer battery is included. This battery supplies standby power to the device eliminates the rebooting of the device when local power is again reapplied. Battery is 1200 ma-hr.
*Battery life (Approximation) Ideal/Target Standby time 150-200 Hrs (GSM) Talk time (Backlight off) Up to 4 hrs(GSM)
*Estimated current draw for the entire device when in suspend mode (and ALL peripherals are turned off or set for deep sleep) is <5 mA at 3.6 volts (Li-Ion terminal voltage).
*GSM module deep sleep(alive and keep contact with base station) stage should take less than 8mA
*Battery will reach half capacity (~600 mAh) with 500 charge-discharge cycles. This will occur in less than 2 years of daily service.
*When powered continuously, Neo1973 must suspend (to low power mode) based either on observed low battery voltage condition or a configurable time delay.
*Neo1973 must monitor battery status while suspended and resume automatically if the charger is inserted.
*Primary power connection: 1200mAh battery
*USB charger have ID pin 47.5k pull down for Openmoko identification
*Indicators: an LED indicator visible from the side of the unit will illuminate when charging or have missing incoming call

=== GSM/GPRS ===
*850/1800/1900 and 900/1800/1900 MHz bands must be supported
*Design should allow for multi-band version (850/900 MHz)
*Module based GPRS transceiver could meet PTCRB and appropriate FCC certifications. It preferred that the module be pre-certified with PTCRB or OTA test
*FCC/CE certification required for GSM/GPRS part

=== GSM-GPRS Antenna Performance ===
*-105 dBm receiving on each channel (GSM/PCS)
*30+2 dBm transmission on GSM channel

=== Wi-Fi Modules ===
*Must support GPL driver
*Atheros AR6k preferred
*Flash version required

=== Wi-Fi Antenna Performance ===
*The Wi-Fi antenna with TX 13 to 15 dBm
*RX -89 to -83 dBm @802.11b 11Mbps or an equivalent performance antenna

=== Bluetooth ===
*CSR BC4 or later solutions

=== USB ===
*Neo FreeRunner GTA02 will have USB, client/host. Using USB 1.1
*Provides USB host 5v power
*Could be powered by USB

=== Microphone ===
1 microphone is in the device

=== Firmware Image ===
*Using Linux 2.6.24 or later
*Could support booting from NAND or from NOR
*Shipping image should come with basic phone function
*Could do full firmware upgrade by USB cable

=== PSN ===
*Device will have a PSN (product serial number) printed on the product label and machine readable in system NAND memory

=== IMEI ===
*Production phase should have IMEI code written

= Package Specification =
*Weight: ~133 grams with battery.
*4-in-1 laser pen passed RoHs and safety regulation for laser equipment safety
*1x 512MB microSD Card ([http://www.sandisk.com/ SanDisk] / [http://www.transcendusa.com/ Transcend] [http://www.transcendusa.com/Support/DLCenter/Datasheet/TSxxUSD.pdf TS512MUSD])
*1x USB cable Standard A to mini-B connector
*1x 1200mAh smart/gauge battery
*Quick start guide
*5v USB power cord w/100-240 switchable power plug
*Safety card, warranty card
*Package could pass 1m to 1.5m drop test
*AC USB charger,100v-240v, Passed UL and all required safety regulations
*Must pass FCC/CE certification
*Must pass NCC certification for Taiwan import regulation
*RoHS Compatible
*WEEE Report required

= Life Cycle Specification =

=== Product Life ===
The product is designed to last a minimum of 2 years.

=== Operating Temperature ===
*Target operating range is –10°C to +60°C

=== Storage Temperature ===
*-15 deg C to +70 deg C

=== ESD ===
The device can withstand a 4.0kV contact discharge and 8.0kV air

=== Drop test ===
Should pass 1m direct drop to concrete ground or 1.5m on slide with carpet

= GTA02 Hardware Component Selection =

== Physical Dimensions ==
* 120.7 x 62.0 x 18.5 mm (4.752 x 2.441 x 0.728 inch)
* 110 +/- 5 g (4 ounces) without battery <br>

== Main components ==
=== Processor ===
The main Processor (CPU) of the Neo1973 GTA02 is a [[Samsung S3C2442B B54]] (running at 400 MHz)

* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=SC32442 Samsung SC32442B]
* User Manual: [http://210.118.57.197/Products/Semiconductor/MobileSoC/ApplicationProcessor/ARM9Series/SC32442/um_s3c2442b_rev12.pdf Samsung SC32442B]
* Core: ARM920T
* Instruction Set: ARMv4
* Built-in 64MB SDRAM
* Built-in 256 MB NAND
* GPIO Assignments: https://svn.openmoko.org/trunk/doc/hardware/GTA02v4/gpio.txt<br>
* Evaluation board: [http://www.meritech.co.kr/products/product_view.php?num=52 S3C2442 EVB]

=== Power Management ===
A NXP PCF50633 04 N3 is used for [[Neo1973_Power_Management|power management]].

* NXP PMU index: [http://www.nxp.com/products/power_management/pmu/index.html NXP PMU index page]<br>
* Product Datasheet: [http://people.openmoko.org/tony_tu/GTA02/datasheet/PMU/PCF50633DS_02.pdf NXP PCF50633 Product Data Sheet]<br>
* Product User manual: [http://people.openmoko.org/tony_tu/GTA02/datasheet/PMU/PCF50633UM_6.pdf NXP PCF50633 User Manual]<br>
**Special thanks to NXP for providing a complete user manual and for supporting all developers
**Datasheet/User manual usage [http://lists.openmoko.org/pipermail/community/2008-March/013898.html was legally authorized by NXP]
* Connected to: S3C2442 via I2C, client address is 0x08. <br>
* Driver Source: https://svn.openmoko.org/trunk/src/target/kernel/patches/pcf50633.patch<br>

=== Flash ===
==== NAND Flash ====
256MB integrated Samsung NAND flash inside the 2442 multi-chip package, attached to the S3C2442 NAND controller

* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=SC32442 S3C2442]
* Data Sheet: S3C2442 B54 comes with 256 MB NAND MCP package
* Connected to: S3C2442 NAND controller<br>

==== NOR Flash ====

16MBit ST M58WR016KB706E NOR flash for 'unbrickable emergency boot' feature.

* Product Homepage: [http://www.st.com/stonline/products/families/memories/fl_nor_mob/index.htm ST Mobile Flash NOR/Mobile Terminal]
* Data Sheet: [http://www.numonyx.com/Documents/Datasheets/M58WRxxxKTB.pdf M58WR016]
* Connected to: S3C2442 NAND controller<br>

=== SDRAM ===
128MB SDRAM (64MB inside 2442 MCP, 1x Samsung K4M51323PC) attached to S3C2442 SDRAM controller
* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=136&partnum=K4M51323PC Samsung K4M51323PC]
* Data Sheet: [http://www.samsung.com/global/system/business/semiconductor/product/2007/6/11/MobileSDRAM/MobileSDRSDRAM/512Mbit/K4M51323PC/ds_k4m51323pc.pdf Samsung K4M51323PC]
* Connected to: S3C2442 <br>

== GSM/GPRS ==
The [[GSM]] (including GPRS) modem is Texas Instruments Calypso based.

* Connected to: S3C2442 UART1 (full-uart, RxD, TxD, CTS, RTS), /dev/ttySAC0 in userspace
* PM Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-power_control.patch
* Accessible GSM/GPRS antenna jack (if battery cover is removed)<br>

=== CALYPSO ASIC digital baseband ===
Unfortunately we cannot provide many details on the GSM chipset due to very tight [http://en.wikipedia.org/wiki/Non-disclosure_agreement NDA]s. However, this is not neccessarily required, since it interfaces using a standard UART serial line with the S3C2442. On that interface, [http://www.3gpp.org/ftp/Specs/archive/07_series/07.05/ GSM 07.05], [http://www.3gpp.org/ftp/Specs/archive/07_series/07.10/ GSM 07.10] and other standardized protocols are used.

The NDAd documentation for the calypso, [http://cryptome.org/ti-calypso1.pdf register definition ] and [http://cryptome.org/ti-calypso2.pdf hardware definition ] was leaked onto a public forum on the 4th of March by persons or persons unknown.
The legality of reading these files may vary according to your local laws, as may generating code from them.

*Calypso D751992AZHH<br>
*The firmware within GTA02 should be moko6 or later (internal code name)

=== TI TWL3025BZGMR analog baseband ===
*Product Homepage: [http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=12295&contentId=4703 TWL3014]<br>

=== TI TRF6151 (GSM/PCS) RF Transceiver ===
*Product Homepage: [http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=12296&contentId=4701 TRF6151] <br>
GPRS Class12/CS4 <br>

== AGPS ==
u-blox ANTARIS 4 chip
* Connected to: S3C2442 UART2, /dev/ttySAC1 in userspace
* Driver: none needed, talks standard NMEA
* u-blox Antaris 4 Protocol [http://www.u-blox.com/customersupport/antaris_doc.html Protocol download page]
* ATR0635 Datasheet: [http://www.u-blox.com/products/Data_Sheets/ATR0630_35_SglChip_Data_Sheet(GPS.G4-X-06009).pdf u-blox ATR0635]<br>

== Accelerometers ==
Two [[ST LIS302DL]]
* Homepage: http://www.st.com/stonline/products/literature/ds/12726/lis302dl.htm
* Datasheet: http://www.st.com/stonline/products/literature/ds/12726.pdf
* Connected to: S3C2442 via SPI interface
* S3C2442 SPI EINT interrupt inputs<br>

== Graphics/3D Acceleration ==

Smedia Glamo 3362.
* Homepage: http://www.smediatech.com/product3362.htm
* Driver: http://git.openmoko.org/?p=kernel.git;a=commit;h=911c6fab17f81ea2fdc6ad5e6173ce72bfe01ec4
* Data sheet: This is not available, as it is under NDA. It will likely never be available. (Source: Raster - IRC). It is possible that the glamo chip features may be usable even without a NDA, see [http://unadventure.wordpress.com/2008/06/08/accelerating-in-my-pocket/ the hack here]
* Connected to: S3C2442 Address/Data bus <br>

=== microSD ===
The GTA02 has one microSD aka Transflash slot. Using the Glamo 3362 MMC/SD controller

* It should support SDHC, and 4GB card has been tested. Anyone with 8GB card? MicroSD slot is [[Disassembling_Neo1973#Opening_back_cover|under battery]].
* 8 Gb Transcend microSDHC class 4 card confirmed working on GTA02 (using [https://docs.openmoko.org/trac/ticket/1743 #1743]).
* Connected to: Glamo 3362 MMC/SD controller
* Driver: Check svn for the SMedia driver with SD implementation
* [[Supported microSD cards]]
* Specifications: [http://www.sdcard.org/about/memory_card/pls/ SD Simplified Specification], [http://www.mmca.org/compliance/buy_spec/AN_MMCA050419.pdf MMC (partial)], [http://www.sandisk.com/Assets/File/OEM/Manuals/manual-rs-mmcv1.0.pdf MMC (product manual)]
* SANDISK 128 MB/512 MB and some 4G SDHC card been verified could work on GTA02<br>

== LCD Module (LCM) ==
Toppoly (tpo) 2.8" diagonal (1.7" x 2.27" - 43mm x 58mm) 480x640 TD028TTEC1 module, using a Toshiba JBT6K74 TFT
LCD Driver Chipset.<br>
* Homepage: [http://www.tpo.biz/ENG/business-eng/Activer-Matrix-VGA.htm Activer-Matrix-VGA.htm]
* Specification: FIXME
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-jbt6k74.patch
* Backlight Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-backlight.patch
* Connected to: Glamo3362 LCM interface and Glamo3362 SPI Interface<br>

==== Touch Screen ====
* Connected to: S3C2442 touchscreen controller
* Driver: http://git.openmoko.org/?p=kernel.git;a=blob_plain;f=drivers/input/touchscreen/s3c2410_ts.c;hb=andy-tracking

== Bluetooth Module==
Delta DFBM-CS320 Class2 Module, using CSR BlueCore4

* Data Sheet: [http://www.datasheet4u.com/download.php?id=571424 2.DFBM-CS320.pdf]
* CSR Data Sheet: [http://www.csrsupport.com/download/2302/CS-101564-DSP10%20BlueCore4-ROM%20Product%20Data%20Sheet.pdf CS-101564-DSP10 BlueCore4-ROM Product Data Sheet.pdf]
* Driver: Stock Linux Kernel BlueZ
* Connected to: S3C2442 USB Host controller (OHCI)
* PM Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-power_control.patch<br>

=== Bluetooth Audio ===
This one is wired via PCM bus from the CSR Bluetooth chip to the Wolfson codec.<br>

== WiFi Module==

Accton (WLAN 802.11b/g SiP-M WM3236AQ(Flash Ver:2.0 Atheros AR6001GZ)
* Connected to: S3C2442 SDIO Host controller<br>
* Datasheet: [http://www.accton.com/products/Datasheet/WM3236A.AQ.pdf Accton 3236AQ datasheet]<br>
* Driver: http://svn.openmoko.org/developers/sameo/patches/<br>

== Vibrator ==
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-vibrator.patch
* Connected to: S3C2442 GPIO

== USB Host ==
The USB Host controller is inside the S3C2442
* Driver: Stock Linux kernel ohci_hcd
* USB version 1.1
* Supply USB 5v in Host mode using usb power switch AAT1275IRN-5.0-T1
** http://www.analogictech.com/products/digitalfiles/AAT1275.pdf
* A net EN_USBHOST is controlled by PMU GPIO "GPO", this one signal when asserted (high)
** enables generation of 5V for external device using a charge pump
** enables connection of 15K pulldowns to D+ and D- to allow device insertion and removal detection for host mode
** DISABLES the path for USB power to charge the battery

It should also be possible to use host mode with externally-provided
power. This will allow the FreeRunner to be connected to a USB device
and be powered and charging the battery if present at the same
time. This method is called the Y-cable and was invented by [[User:JOERG|Joerg Reisenweber]]. For
additional info and circuit diagrams see
[[Specialized_USB_cables#How_to_make_a_USB_cable_for_powering_attached_USB_devices_and_charging_the_Neo_while_in_host_mode_.28aka_Y-Cable.29|Specialized
USB Cables]].

* Connect 0V, d+, d-, +5 to your USB device
* Connect a 15k ohm resistor between d+ and ground
* Connect a 15k ohm resistor between d- and ground
* Connect 0V, +5 to your >1A power source
** If your power source was not the Openmoko 1A charger, additionally connect a 47K ohm 5% resistor between the ID pin and ground to pretend to be the 1A charger.

In addition you need to make sure EN_USBHOST signal that enables the physical Host mode power generation and disables the USB -> PMU charging path is deasserted. This may be taken care of automatically shortly by detection of the 48K resistor on a USB insertion leading to forcing EN_USBHOST deasserted. The charge pump that generates the 5V in host mode doesn't seem to mind getting external 5V given to it, but the real issue is that the battery will not be charged at all if we leave EN_USBHOST asserted since one of its jobs is to stop that happening.

== USB Device ==
The USB Device controller is inside the S3C2442
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c2410_udc.patch
* Please see [[USB Product IDs]] on information about which Vendor/Product IDs we use
* 1200mAh lithium battery charges when connected to powered host.
* Mini-AB connector similar to [http://www.cypressindustries.com/shoponline/proddetail.asp?prod=CCMUSBAB-32005-700&cat=34 this one].

== I2C Devices ==
I2C is a simple communication standard intended to move small amounts of data a few inches between chips.
Please see [[I2C | Neo I2C Devices]] for more information & a list of devices & the addresses currently in use & documented for the Neo1973.<br>

== Audio ==
See also: [[Neo1973 Audio Subsystem]]

=== Wolfson Codec ===
There's a [[WM8753]] Wolfson Microelectronics CODEC (This is not a 'smart' codec that can interpret MP3/... it is a simple dumb 'sound card'.)
* Product Homepage: http://www.wolfsonmicro.com/products/WM8753/
* Data Sheet: [http://www.wolfsonmicro.com/uploads/documents/en/WM8753.pdf WM8753.pdf]
* Connected to: S3C2442 IIS interface (PCM data), S3C2442 I2C (Control)

[[Category:Hardware]]

=== Mono Amplifier ===
There's a National Semiconductor [[LM4853]] Mono Amplifier at the analog audio output of the WM8753

* Product Homepage: [http://www.national.com/pf/LM/LM4853.html LM4853.html]
* Data Sheet: [http://www.national.com/ds.cgi/LM/LM4853.pdf LM4853.pdf]
* Connects to (LM4853 pin):
** S3C2442 GPIO: HP_IN, AMP_SHUT (shutdown);
** Wolfson WM8753: LOUTL (LEFTIN), LOUTR (RIGHTIN);
** speaker4102: (LEFTOUT/BLTOUT-, BLTOUT+);
** headset-jack: ring 2 (RIGHTOUT), ring 3 (LEFTOUT/BLTOUT-) via 1uF-33R each

=== Analog wired Headset ===
There's a four-ring 2.5mm stereo jack which provides connectivity to old-fashioned wired headsets.

The headsets used by Motorola smartphones (A780,A1200, ...) and the V-360 have a compatible configuration, as does the headset for an LG muziq 570.

ring<br>
1(base): GND<br>
2: right out<br>
3: left out<br>
4(tip): mic + HOLD-button(press:short to GND)

=== Buttons ===
The Neo1973 GTA02 features two buttons:
* [[Neo1973 Power Button|The Power Button]]
* [[Neo1973 AUX Button|The "Aux" button]]

== Case ==
The case for the FreeRunner is all black, as seen on the front page of the wiki.

Openmoko has released the CAD files for the case of the Neo1973 and Neo FreeRunner. These were created using Pro/ENGINEER (also called Pro/E). They are available in the Pro/E (.asm/.prt) format, but alternative formats are also available.

We welcome your assistance in providing other formats. If you are able to convert CAD files from Pro/E format to other formats, please contact [mailto:michael@openmoko.org]. We are especially interested in the DXF format and in images rendered from these files.

* [http://downloads.openmoko.org/CAD/NeoFreeRunner_ProE.zip The original Pro/E (.asm/.prt) format]

[http://downloads.openmoko.org/developer/CAD/ Browse CAD directory]

=Accessory=

== Stylus ==

Using 4-in-1 laser pen
*Vendor: [http://www.quarton.com/laser_pen.html Quarton XPII]
*GTA02 standard setup comes with [http://www.quarton.com.tw/laser_pen_infiniter_xp_2.html QUARTON XPII 4-in-1 laser pen]

== Battery ==
The [[Neo FreeRunner (GTA02) Battery]] is mechanically and electrically compatible with the [[Neo1973 GTA01 Battery]], as well as limited compatibility with a Nokia BL6C battery.
According to [http://lists.openmoko.org/pipermail/community/2007-February/003758.html this] post on the mailinglist.
[http://wiki.openmoko.org/index.php?title=Image:Neo1973-with-BL5C-battery.png Photo] of the battery inside the Neo1973.

* GTA02 using the smart battery based on TI bq27000 chipset
* SANYO UF653450S 1200mAh cell.<br>
* Battery schematics: [http://people.openmoko.org/tony_tu/GTA02/hardware/GTA02/CT-GTA02.pdf GTA02 Smart Battery Schematics]

== microSD Card ==

GTA02 should come with one of following microSD card

* [http://www.transcendusa.com/ Transcend] 512MB microSD card
* [http://www.sandisk.com/ SanDisk] 512MB microSD card<br>

== Charger ==

AKII Technology Charger

*Model: [http://www.ak2.com.tw/pd_main.asp?sg_id=11 A10P1-05MP]
*Input: 100-240v~ /0.3A
*Output: +5v up to 2.0A
*Add 47.5k 1% resistor between ID pin and ground for openmoko charger identification<br>

= History =

== GTA02v1 ==
First generation of prototypes that was given to internal Openmoko software developers. Total 30 pcs fabricated.

*It is working just fine, but still based on 2440, with external NAND/SDRAM and no NOR flash
*Using the PCF50633 05 N3 due to 04 N3 not available, rework power for basic schematics verification
*Using GTA01 SIM socket
*Add external debug port
*Still using Global locate A-GPS
* ATAG_REVISION: 0310

== GTA02v2 ==
Second generation of prototypes, Total 50 pcs run at Taipei SMT factory MOUNT

*Ideal is have 256 MB NAND on Samsung package, Due to chip availability Start using S3C2442 B43
*Using correct PMU PCF50633 04 N3
*Change new SIM socket
*Change to u-blox A-GPS
*Change LCM power from 3.3v to 1.8v
*USB power switch layout/pin assignment mistake, could not verify USB host supply 5v function
*GPS function verified ok with good sensitivity
* ATAG_REVISION: 0320

== GTA02v3 ==
Production verification version, 2007/10/11 28 pcs fabricate at FIC SuZhou

*Still using S3C2442 B43 for hardware verification
*Using control pilot run to verify S3C2442 B54 chips<br>
* ATAG_REVISION: 0330

== GTA02v4 ==
Mass production release candidate version 1

2 weeks after v3 gerber out, release the v4 gerber, and 2007/10/20 20 pcs fabricate at FIC SuZhou

*Change LCM power from 1.8v to 3.3v for display stability issue
*fabricate another 200 pcs for yield rate/production verification
*fabricate 50 pcs with S3C2442 B43 (128 MB NAND) for quality comparsion
*USB host power chip have some output voltage stability issues with Vb/Vcc comes from different power source, need layout change to fix the issue
*Battery Coulomb design not working on A4
* ATAG_REVISION: 0340

== GTA02v5 ==
Mass production candidate version 2/Mass production version

* First batch fabricate 2008/1/14 at FIC SuZhou
* Mass production A5 trial run start from 2008 March, including some resistor/capacitor change compare with inital 100 pcs prototypes A5, and prototypes for GTA02 developers was tracked in the [[Prototypes| Prototypes Page]]
* Coulomb counter issue fixed
* USB host power switch fixed
* Need add capacitor for PMU Vbat input for stability issue, this could be done by direct SMT or hand rework
* Need rework (still using SMT in production) add capacitor for PMU Vbat input for PMU stability issue.
* Need manual rework GSM IR UART path a 100k pull down for better GSM deep sleep
* ATAG_REVISION: 0350

===GTA02 mass Production version change list===
*PMU's LED power error: PMU potential damage issue
*NOR FLASH enable WP: User can write data into NOR FLASH.
*CE CS/RS fine tune: Audio's background noise too high
*I2C pull high resistor: The resistor is too high and signal is distorted
*GSM leakage current: TX_MODEM has a pull high resistor on IO_3V3
*Power consumption: Disable keep active function
*SDIO clock and esd protect resistor
*Refer to Datasheet: R1526 to 33K
*GSM modem on pin: The R1018 is too small and has some leakage current
*LED driving transistor: When GPIO is on, the transistor will be draw more current on LED. This is component change fix, do not need change PCB or re-work.

== GTA02v6 ==
Mass production candidate version 3/Mass production version<br>

A6 will be fine tune version of A5, only minor [http://downloads.openmoko.org/schematics/GTA02/ schematic] change for better product quality and version control. Capacitor and resistor change A6 also on mass production A5<br>

*First 100 pcs start from 2008 mid April, and factory make component placement mistake on GSM, second 100 pcs PCB arrive time TBD.
*Add capacitor space for Vbat, reduce the SMT effort
*Add GSM IR resistor for better GSM deep sleep
*Reserve 3 GPIO for hardware version control
*Fixed LEDs power usage (from about 150mW of v5 to about 25mW)
* ATAG_REVISION: 0360

=== GTA02 A5 to A6 changes ===
*Power Glitch on VB_SYS: Add capacitor on layout, Mass production A5 also apply this change.
*G-sensor separate these interrupt pins: At A5, each accelerometer INT1/INT2 connected to same line, at A6 only INT1 was connected.
*GSM_modem power source Reduce power's ripple when the phone is talking
*Keep active Disable keep active function, just fine tune
*GPIO for version control
*GSM RX_IR has some noise Add resistor and reduce GSM RX_IR noise and gsm can't enter suspend mode easily, apply on mass production A5.
*LED driving transistor apply on mass production A5.
*LCM's VDDIO We can totally power off LCM's power, save about extra 1mA.

= Debug Board =

== Debug Board Connector definition ==

This is the connector used to connect the [[Debug Board]] and possibly other hardware.

Connections are:
* 39 - GND
* 38 - STDI
* 37 - _RESET
* 36 - STMS
* 35 - STCK
* 34 - STDO
* 33 - GSM_EN
* 29 - _STRST
* 19 - X_I2C_SCL (H-TP4703)
* 18 - X_I2C_SDA (H-TP4704)
* 17 - SPI_CLK0
* 16 - SPI_MOSI0
* 15 - SPI-MISO0
* 14 - SS0
* 13 - EINT3 (H-TP4705)
* 3 - CONSOLE_TXD (H-TP4701)
* 2 - CONSOLE_RXD (H-TP4702)

Information from [http://people.openmoko.org/roh/Debugport_GTA01bv4.png].

= Distinguishing hardware revisions =
== Inside the [[Bootloader]] ==
Every hardware revision has its own u-boot image type. Thus, the bootloader has the revision hard-coded.
The hardware revision is passed on to the kernel via the ATAG mechanism (ATAG_REVISION)

== Inside the [[Kernel]] ==
The kernel receives the ATAG_REVISION during bootup, and saves its contents in the "system_rev" global variable.

== From Userspace ==
The kernel exports the system_rev variable in /proc/cpuinfo as "Revision :" line.

= Certification =

== FCC ==
*For US Import
** 850/1800/1900 Band, FCC ID: EUNGTA02
** 900/1800/1900 Band, FCC ID: EUNGTA02E
** [http://people.openmoko.org/tony_tu/GTA02/certificate/EUNGTA02_850_1800_1900/ FCC test report(GTA02)]
** [http://people.openmoko.org/tony_tu/GTA02/certificate/EUNGTA02E_900_1800_1900/ FCC test report(GTA02E)]

== CE ==
*For Europe
**Registration number: M528583V-EO
**[http://people.openmoko.org/tony_tu/GTA02/certificate/CE/ CE report and certificate]

== NCC ==
*For Taiwan Import
**NCC certification number: CCAF08DG0080T0
**[http://people.openmoko.org/tony_tu/GTA02/certificate/NCC NCC report and certificate]

[[Category:Neo FreeRunner Hardware| ]]

StandbyLifetime

2009-05-13T17:26:29Z

Mickey: oops, i can't count

Standby lifetime test with my FreeRunner running FSO MS5.
No usage except keeping GSM listening for incoming calls and occasionally waking it up to measure.

<pre>
00h Tuesday, 03:00 100%
10h Tuesday, 13:00 85%
15h Tuesday, 18:00 78%
20h Tuesday, 23:00 71%
25h Wednesday, 04:00 64%
34h Wednesday, 13:00 51%
39h Wednesday, 18:00 44%
45h Thursday, 00:00 35%
49h Thursday, 04:00 29%
55h Thursday, 10:00 21%
60h Thursday, 15:00 13%
63h Thursday, 18:00 10%
65h Thursday, 20:00 5%
68h Thursday, 23:00 empty
</pre>

[[category:FSO]]

Distributions

2009-04-16T22:19:23Z

Mickey:

{{Languages|Distributions}}

{|align=left
|__TOC__
|}

== About distributions ==
Openmoko distributions are designed to run on various mobile devices, with the primary aim of supporting Openmoko Inc.'s [[GTA01:Neo 1973|Neo 1973]] and [[Neo FreeRunner]] phones. They are GNU/Linux distributions -- complete operating systems including user applications. You can install any of them on your phone or even have a dualboot system with two distributions installed. For downloads see [[Download]], for installation instructions see [[Flashing the Neo FreeRunner]].

Besides, Openmoko distributions also run on [[Supported devices|other]] mobile devices and some other software distributions also run on the phones of Openmoko Inc.

=== Choosing a distribution ===
* Official/current. As of December 2008, the phones ship with [[Om 2008.9]].The branch currently supported by Openmoko Inc. is [[Om 2008.12 Update]], which is the second minor upgrade of [[Om 2008.9]] (the version formerly named ''ASU'').
* Official/future. The current trunk tip is a "base image" on which the next major release should be based. This next release can be previewed by installing milestones of the [[FSO]] - Free Smartphone.Org project. If you want to develop anything that last, your platform is [[FSO]] (and the choice between EFL, GTK+, Qt, Java, Python or whatever is open). The [[Debian]] packaging team also track that branch.
* Openmoko community. Based on [[Om 2008.8]], the community made the [[FDOM]] distribution by adding lots of fixes and applications to it. Most new users find [[FDOM]] the most comprehensive and functional distribution.
* Other community. The FreeRunner is also a reference platform for TrollTech's ''Qt Extended'' (formerly [[Qtopia]]) distribution. If you want "just a working phone", try [[Qtopia]].
* Other communities. [[Android]] work is in progress; [[Debian]] and [[Gentoo]] are for people who do not need to ask which distribution they should use.

{| class="wikitable" style="float:right;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|<font color=white>Distributions</font>
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* <font color='#BBBBBB'>Openmoko (official)</font>
** [[Om2009]]
** [[Om 2008.12 Update]]
** [[Om 2008.9 Update]]
** [[Om 2008.8]]
** [[Om 2007.2]]
** [[OpenmokoFramework|FSO]]
* <font color='#BBBBBB'>Om Community</font>
** [[SHR]]
** [[FDOM]]
* <font color='#BBBBBB'>Other</font>
** [[Qtopia]]
** [[Debian]]
** [[Gentoo]]
** [[Android]]
** [[Hackable:1]]
** [[Fyp]]
</div>
|-
|}

=== Please note ===

* Stable in the FreeRunner world does not mean the same thing as stable in the Debian world.
* Most distributions use the same bootloader, kernel, drivers and hardware. Therefore, the same low level bugs are commonly found in all distributions. The latest and greatest software usually has most bug fixes, plus a whole set of new fresh bugs.
* Most of these distributions also have package repositories. It is a BAD idea to feed from another distribution's repository.
* Upgrade path between these distributions are mostly not tested, thus updating by changing the feeds will most likely end in broken packages or even an unbootable system. It is advisable to reflash the whole filesystem with [[dfu-util]] to switch between the different distributions, with the reminder that a dual-boot setup (e.g. via sdcard or NFS) can be used.

== Official Openmoko releases ==

'Release targets' offered by Openmoko Inc. are built out of different branches of the [[OpenEmbedded]] metadistribution source tree.

=== Om series ===

* '''[[Om2009]]''' is intended to be the new distro; it is not a simple follow-on from [[Om 2008.12 Update]]. '''It is still very much in development and by no means ready for production use''' and is based on the [http://freesmartphone.org freesmartphone.org] milestone 5.5 framework.

{{Main|Om2009}}

* '''[[Om 2008.12 Update]]''' is the second point release after the initial ''Om 2008.9'' release.

{{Main|Om 2008.12 Update}}

* '''[[Om 2008.9 Update]]''' is the first point release after the initial ''Om 2008.8'' release. Openmoko recommends that all existing installations of Om 2008.8 should be updated to that version. Quality-wise, we are still far from the goal, but this version includes general stability enhancing operating system improvements and a new splash screen. No applications were added or removed. Users with basic telephony needs will find it tolerable as an everyday phone.

{{Main|Om 2008.9 Update}}

* '''[[Om 2008.8]]''' was released on August 8, 2008, to replace 2007.2. Prior to that, its codename was ASU (April/August Software Update). This is still the name of the branch in the version control system. This distribution integrates the [http://trolltech.com/products/qtopia Qtopia] phone stack with a set of new Openmoko applications based on the Enlightenment Foundation Libraries ([[EFL_Documentation|EFL]]). Qtopia being a more mature product than the GNOME Mobile stack, the standard phone applications (dialer, contacts, calculator, calendar) work better than in 2007.2. The Qtopia used in 2008.8 was ported to run on X11, contrary to standard Qtopia which uses the framebuffer. This allows non-Qt applications to safely share the screen with Qt applications. This is a .0 release, many unresolved issues remain in the lower layers (kernel power management, sound, wifi drivers...).

{{Main|Om2008.8}}

* '''[[Om 2007.2]]''' is the base-system which is installed on FreeRunner when it leaves the factory. The interface was totally finger-oriented, optimized for 285ppi, and very orange. It used the GTK+ stack, which is part of the [http://www.gnome.org/mobile/ GNOME Mobile] platform. This distribution is now considered obsolete and not being worked on by Openmoko Inc or by OpenedHand. There is a community effort (see [[SHR]]) to port the GTK based telephony applications to the future middleware from [[FSO]].

{{Main|Om 2007.2}}

=== FSO series ===

'''FSO''' is an abbreviation for FreeSmartphone.Org. Openmoko is working on a stable system services back-end. Focus is on stable highlevel services that you can access from whatever language or UI that supports [http://dbus.freesmartphone.org/ dbus]. The framework will be used in forthcoming Openmoko distributions. FSO is all about middleware, but if one stacks a bootloader+kernel under it and telephony applications on top, one gets a functional distribution. These are made available as FSO-image milestones.

* '''FSO Milestone V''' was released and named 'Calling All Stations'. The telephony application on top of it is Zhone. This is a basic Python dialer/homescreen designed as scaffolding to test the FSO functionalities (even if Zhone is pretty, code path coverage is more critical to it than user-friendliness). More details at
[http://wiki.openmoko.org/wiki/OpenmokoFramework/Status_Update_6 Status Update 6]. You can grab it from http://downloads.freesmartphone.org/fso-stable/milestone5.1/ .

{{Main|FSO}}

== Openmoko community releases ==

=== SHR - Stable Hybrid Release ===

SHR is a community driven distribution. It contains some basic EFL based applications which make use of the FSO. There currently is an [[EFL_Documentation|EFL]] (with elementary) dialer, messages and contacts application programmed in C, as well as a nice Settings-GUI in Python. As of April 12th, 2009, there is no stable release of this distribution yet, as the SHR team doesn't feel it to be good enough. You can find images though on the [http://shr.bearstech.com/shr-testing SHR buildhost].

{{Main|Stable Hybrid Release}}

=== FDOM (FAT and Dirty Openmoko) ===

[[FDOM]] is a distribution based on Openmoko's currently supported image, updated with many ready-to-use applications and with fixes posted in the mailing lists. A combination of applications (everything goes) and fixes to demonstrate the capabilities of the Freerunner and to have a functional phone (sort of). This all while retaining the ability to update through the official feeds.

{{Main|FDOM}}

=== Non-Openmoko distributions ===

These are not Openmoko (and OE) based distributions. These are alternatives you can run on your Openmoko phones.

==== Qt Extended ====

Qt Extended has had several names. The current name is <b>Qt Extended Improved</b>. An Openmoko based community develops Qt Extended Improved as a Free Software project. Qt Extended Improved builds on the foundation of Qt Extended/Qtopia/Qt by Qt Software/Trolltech. Qt Extended Improved provides a robust telephony stack, a webkit based browser and other smartphone features.

On 5th March 2009 Qt Software released Qt Extended 4.4.3. On 3rd March 2009 Qt Software announced that Qt Extended would 4.4.3 would be the last release of the Qt Extended product. Prior to version 4.3, Qt Extended was known as Qtopia.

{{Main|Qtopia / Qt Extended on FreeRunner}}

==== Debian ====

Debian is "the universal operating system". It comes with thousands and thousands of packages (most of them designed for desktops or servers so far). So in the words of Joachim "nomeata" Breitner from the [http://wiki.debian.org/Teams/DebianFSO pkg-fso] team, this is not really a distribution in the Openmoko sense of the word, but rather a different underlying system for Openmoko distributions. At the moment, we ship the software from the FSO stack, but hopefully we’ll also have, for example, the Stable Hybrid Release software in our archive. So for now, Debian is a different way of installing FSO, which takes more space and provides more programs :-)

{{Main|Debian}}

==== [[Gentoo ]]====

Gentoo is all about choices. When installing Gentoo, this is made clear to you several times -- you can choose how much you want to compile yourself, how to install Gentoo, what system logger you want, etc. Gentoo is a fast, modern metadistribution with a clean and flexible design. Gentoo is built around free software and doesn't hide from its users what is beneath the hood. Portage, the package maintenance system which Gentoo uses, is written in Python, meaning you can easily view and modify the source code. Gentoo's packaging system uses source code (although support for precompiled packages is included too) and configuring Gentoo happens through regular textfiles. In other words, openness everywhere.

{{Main|Gentoo}}

==== Android ====

[http://code.google.com/android/ Android] is a software stack for mobile devices developed by the [http://www.openhandsetalliance.com/ The Open Handset Alliance.] Openmoko is fully supporting Android running on the Freerunner.

Android has now reached a point where it is usable on the FreeRunner as an everyday phone, there are, however, still some caveats. Check out the main Android section of the wiki for more info.

{{Main|Android}}You can also visit the user web page for [http://wiki.openmoko.org/wiki/User:Seanmcneil3 Sean McNeil] for some more info.

==== Hackable:1====
Hackable1 is a community distribution for hackable devices like the Neo Freerunner. It is based on Debian and 2007.2 userland which has been abandoned by Openmoko. It follows the GNOME mobile platform.
{{Main|Hackable:1}}

====[[neovento]]====
neovento is a [[Debian|Debian for Freerunner]] based [[Distributions|distribution]] which uses [http://lxde.org/ LXDE] and [[Zhone]] on top. It is a [http://freeyourphone.de FreeYourPhone.de] community project.

{{Main|neovento}}

==== Others / unreleased ====

* The [http://www.neopwn.com/software.php NeoPwn] network auditng system's core is a modified Linux 2.6.24 kernel, with cross-compiled module driver support for the numerous compatible addon devices running on a FULL Debian (ARMEL) operating system. The filesystem has been optimized for performance and size and includes the NeoPwn menu system and several GUI dialogs for hardware control and attack automation. ''Status: Unknown, the GPL requires source code to be distributed only to customers''.
* [http://runningbear.org/trac RunningBear] is an innovative, yet free and open-source Operating System for hackable devices driven by Bearstech. Lightweight, Portable, Secure, Friendly and Useful. ''Status: In development''.
* [http://pokylinux.org/ Poky] and Sato, by OpenedHand/Intel. An open source platform build tool derived from OE. It is a complete software development environment for the creation of Linux devices. It enables you to design, develop, build, debug, and test a complete, modern, software stack using Linux, the X Window System and GNOME Mobile based application frameworks for both ARM and x86 based platforms. ''Status: The "Nightly Build" Image works fine on Neo Freerunner, but phone functionality doesn't.''
* [http://pyneo.org/ PyNeo] pyneo is a stack for mobile devices excessivly using dbus, glib and evas. pyneo can be considered FSO milestone 0. Afterwards, FSO evolved into an own project with different goals. ''Status: still active, ask around on #pyneo.org ''
* [http://www.quantum-step.com/ mySTEP] by Openmoko distributor Golden Delicious Computers is based on GNUstep and brings a Objective-C API to the Neo. Core GUI frameworks are "Foundation" & "AppKit". It has been shown on FOSDEM 2008, LinuxTag 2008 and SYSTEMS 2008 to run on the Neo 1973. If someone reengineers UIKit, (open) source code compatibility to iPhone apps appears achievable. ''Status: it does not have its own kernel so a Freerunner distribution waits for a solid basis and an arm-linux-gnueabi toolchain that runs natively on Mac OS X is currently lacking.''

== Features by distribution/release target ==

Generally, distributions can differ on one or more of the following components:
* The bootsplash screen image. This is purely decorative.
* The bootloader. Theoretically, any version of ''uboot'' could be used with any distribution. In the future ''Qi'' will replace ''uboot''.
* The kernel. GNU/Linux kernels versions 2.6.24, 2.6.26 or 2.6.28 can be found. Some have modules compiled in, others have modules compiled separately. If compiled separately, modules can be distributed in the same package file as the kernel or separately.
* Middleware: daemons to handle GSM calls or GPS, sound system, personal information storage and so on. Qt and Android have their own subsystems, FreeSmartphone.Org (FSO) is working towards a standard-based Free Software one.
* Display driver. The original ''Qt Extended'' uses the framebuffer, most other distributions today use ''X11''.
* Libraries and application framework (widget toolkit and and graphical environment) : EFL, Qt, Gtk+ or Java ?
* Basic telephony applications: voice calls, SMS, alarm clock...
* Smartphone applications: GPS, media player, simple games, web browser...
* Open source applications: more games, scientific, you name it...

=== Hardware Support ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=8%|[[Om 2008.8]] !! width=8%|Om 2007.2 !! width=8%|FSO !! width=8%|SHR !! width=8%|FDOM !! width=8%|Qt Extended !! width=8%|Debian !! width=8%|Gentoo !! width=8%|Android
|-
| GTA01 || ?? || ?? || ?? || {{Yes}} || ?? || {{Yes}} || {{Yes}} || ?? || ??
|-
| GTA02 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}
|-
|}

=== Connectivity ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=8%|[[Om 2008.8]] !! width=8%|Om 2007.2 !! width=8%|FSO !! width=8%|SHR !! width=8%|FDOM !! width=8%|Qt Extended !! width=8%|Debian !! width=8%|Gentoo !! width=8%|Android
|-
| Telephony || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
| SMS || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
| [[GPRS]] || Not through UI || Not through UI|| Not through UI || Not through UI (GUI in unstable) || {{Yes}} || {{Yes}} || {{Yes}} (1) || Not through UI || {{Yes}}
|-
| [[WiFi]] || {{Yes}} (*) || {{Yes}} || Not through UI || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Not through UI || {{Yes}}
|-
| VoIP || ?? || ?? || ?? || ?? || {{Yes}} || {{Yes}} (1) || {{Yes}} || ?? || {{no}}
|-
| Bluetooth || {{Yes}} || {{Yes}} || {{No}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ?? || {{Yes}}
|-
| GPS (1) || {{Yes}} (1) || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || {{Yes}} (1) || {{Yes}}
|-
|}

=== Power ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=8%|[[Om 2008.8]] !! width=8%|Om 2007.2 !! width=8%|FSO !! width=8%|SHR !! width=8%|FDOM !! width=8%|Qt Extended !! width=8%|Debian !! width=8%|Gentoo !! width=8%|Android
|-
| Suspend || {{Yes}} || ?? || ?? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}
|-
| Resumes on Event || ?? || ?? || ?? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ??
|-
| Functions after Resume || {{Yes}} || ?? || ?? || {{Yes}} || {{No}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}
|-
|}

=== User Interaction ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=8%|Om2008.8 !! width=8%|2007.2 !! width=8%|FSO !! width=8%|SHR !! width=8%|FDOM !! width=8%|Qt Extended !! width=8%|Debian !! width=8%|Gentoo !! width=8%|Android
|-
| Stylus friendly || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}
|-
| Finger friendly || Partially || Partially || Partially || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{Yes}} || {{Yes}}
|-
| Accelerometer || {{Yes}} [[Rotate|(1)]][[Gestures|(1)]] || {{No}} || {{No}} || {{yes}} (1) || {{Yes}} || {{No}} || {{Yes}} || ?? || {{Yes}}
|-
|}

=== Applications ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=8%|[[Om 2008.8]] !! width=8%|2007.2 !! width=8%|FSO !! width=8%|SHR !! width=8%|FDOM !! width=8%|Qt Extended !! width=8%|Debian !! width=8%|Gentoo !! width=8%|Android
|-
| Terminal || {{Yes}} (1) || Basic (2) || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || {{Yes}}
|-
| PIM || {{Yes}} || {{Yes}} || {{No}} || N/A || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || ??
|-
| Phonebook || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
| Dialer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
| Web Browser || {{Yes}} (1) || {{Yes}} (1) || ? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
| Mail Client || {{Yes}} || ? || ? || ? || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
| XMPP Client || {{Yes}} [[Instant Messaging|(1)]] || {{Yes}} (1) || ? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || || ??
|-
| Media Player || {{Yes}} (1) || {{Yes}} || ? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
|}

=== Toolkits / Runtimes ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0"
! width=10%| !! width=8%|[[Om 2008.8]] !! width=8%|2007.2 !! width=8%|FSO !! width=8%|SHR !! width=8%|FDOM !! width=8%|Qt Extended !! width=8%|Debian !! width=8%|Gentoo !! width=8%|Android
|-
| GTK+ || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{Yes}} || {{Yes}} || ??
|-
| Qt/Qt Extended || {{Yes}} || {{No}} || {{Yes}} ? || {{Yes}}? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ??
|-
| Middleware || qtopia-x11 || gsmd/neod || FSO || FSO || qtopia-x11 || Qt Extended || FSO || FSO || ??
|-
| [[Java]] || {{Yes|Jalimo}} || {{Yes|Jalimo}} || {{Yes|Jalimo}} || {{Yes|Jalimo}} || {{Yes}} || ?? || {{Yes|CacaoVM, JamVM}} || ?? || ??
|-
| [[Python]] || {{Yes}} || {{Yes}} || {{Yes}} || {{yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ??
|-
| [[Mono]] || {{Yes}} (1) || {{Yes}} (1) || ?? || {{no}} || ?? || ?? || {{Yes}} (1) || ?? || ??
|-
| [[Ruby]] || {{Yes}} || ?? || ?? || ?? || ?? || ?? || {{Yes}} (1) || {{Yes}} (1) || ??
|}

=== Images ===
Latest and stable combinations for Neo FreeRunner gta02
{|class="wikitable" border="1" cellpadding="5" cellspacing="0"
| || OM || FDOM || Qt Extended || Android
|-
| current bootloader || [[U-boot|U-Boot]] from [http://downloads.openmoko.org/distro/releases/Om2008.9/ OM daily] version [http://downloads.openmoko.org/] || [[U-boot|U-Boot]] from [http://downloads.openmoko.org/repository/experimental/ OM daily] version [http://downloads.openmoko.org/daily/gta02v5_and_up-u-boot.bin gta02v5_and_up] || [[U-boot|U-Boot]] from [http://downloads.openmoko.org/repository/experimental/ OM daily] version [http://downloads.openmoko.org/daily/gta02v5_and_up-u-boot.bin gta02v5_and_up] ||
|-
| future bootloader || [[Qi]] from [http://people.openmoko.org/andy/ Andy] latest qi-andy.udfu || [[Qi]] from [http://people.openmoko.org/andy/ Andy] latest qi-andy.udfu || [[Qi]] from [http://people.openmoko.org/andy/ Andy] latest qi-andy.udfu ||
|-
| splash || [[Configuring_the_boot_splash_screens|U-Boot]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest splash.gz || [[Configuring_the_boot_splash_screens|U-Boot]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest splash.gz || [[Configuring_the_boot_splash_screens|U-Boot]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest splash.gz ||
|-
| kernel || [[Linux]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest uImage.bin || [[Linux]] from [http://moko.mwester.net/download/ mwester] latest uImage-gta02-mwester-stable.bin or from [http://downloads.tuxfamily.org/3v1deb/openmoko/ treviño] latest uImage-gta02-stable-3v1n0.bin || [[Linux]] see [[Qt_Extended]] page for latest version || [[Linux]] from [http://koolu.org/releases/ koolu]
|-
| modules || ? || [[Linux]] from [http://moko.mwester.net/download/ mwester] latest modules-min-gta02-mwester-stable.tgz or modules-all-gta02-mwester-stable.tgz || [[Linux]] from [http://moko.mwester.net/download/ mwester] latest modules-min-gta02-mwester-stable.tgz or modules-all-gta02-mwester-stable.tgz ||
|-
| rootfs || [[Main_Page|OM]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest rootfs.jffs2 || [[FDOM]] from [ftp://ftp.tuxbrain.com/openmoko/fdom/releases/ TuxBrain] version [ftp://ftp.tuxbrain.com/openmoko/fdom/releases/Fat_and_Dirty_OM.200809_20081023.rootfs.jff2 200809_20081023] || See [[Qt_Extended]] for latest rootfs || [[Android]] from [http://koolu.org/releases/ koolu]
|}

Footnotes:

(1) works, but need additional software to be installed

(2) unusable due to lack of certain keyboard characters. [[Switching_Keyboards#Matchbox_keyboard|Various fixes available.]]

(*) unstable

==Quick download page==

[[Download]]

== See also ==

* Mickey Lauer's post "[http://www.vanille-media.de/site/index.php/2008/06/28/gtk-asu-fso-tmtla/ GTK, ASU, FSO, TMTLA!]" describes the differences between distributions 2007.2, ASU and FSO.

* Latest news and tips are in [[Community Updates]]

* [[Kustomizer]] is a script to change your 2008.12 to a usable phone

[[Category:Distributions| ]]

User:Mickey

2009-04-06T09:47:04Z

Mickey: /* Michael 'Mickey' Lauer */

[[Image:Mickey.jpg|left]]
===[http://www.vanille-media.de Michael 'Mickey' Lauer]===
Mickey is an independent IT contractor specialized in embedded linux, distributed systems, application frameworks, and GUI toolkits. Next to a doctoral degree in computer science, he brings in more than 20 years of programming experience, 7 years of those in open source contributing to various mobile and embedded Linux projects. He has been consulting and developing the Openmoko project since the beginning until 2009/04.

These days, he works on the multidevice and multivendor [http://freesmartphone.org Freesmartphone.org] mobile middleware project. freesmartphone.org is looking for funding. If you're interested, please contact Mickey.

Who is Who

2009-04-01T10:28:13Z

Mickey:

''Note: This is severly outdated. Most of the people listed here as officials do not work for Openmoko anymore.''

If you subscribe to a mailing list, you will see people speaking, answering some questions, but you may ask:
* Who is who?
* Who can I trust when they say something?

So I propose to fill out this list to help people get to know each other.

== Officials members of the Openmoko Team ==

The Openmoko team (alphabetical by last name):
{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"
! Name !! email !! Wiki username !! IRC nickname !! Position
|-
| Allen Chang || || {{user|allen_chang}} || || GTA Hardware Engineer
|-
| Andy Green || ''andy'' at openmoko dot ''com'' || {{user|warmcat}} || agreen || Software Developer
|-
| Anthony Chang || || || || Software Developer
|-
| Candy Chou || || {{user|candy_chou}} || || GTA/HXD Hardware Engineer
|-
| Dkay Chen || || {{user|dkay_chen}} || || GTA/HXD Hardware Engineer
|-
| Jeremy Chang || || || || Software Developer
|-
| Jollen Chen || || || || Marketing
|-
| Tick Chen || || || || Software Developer
|-
| Guillaume 'Charlie' Chereau || ''charlie'' at openmoko dot ''org'' || || ||
|-
| Julian Chu || ''julian_chu'' at openmoko dot ''com'' || || || Software Developer
|-
| Holger 'Zecke' Freyther || ''zecke'' at openmoko dot ''org'' || || || Software Developer
|-
| Graeme Gregory || ''graeme'' at openmoko dot ''org'' || || XorA ||
|-
| Carsten Haitzler || ''raster'' at openmoko dot ''org'' || || raster || (Left Openmoko. Here for archives.)
|-
| Matt Hsu || || {{user|Matt}} || || Software Developer
|-
| Wendy Hung || || || || Testing
|-
| Regina Kim || || || || Testing
|-
| William Lai || ''will'' at openmoko dot ''com'' || || || Design Team Project Manager
|-
| Michael 'Mickey' Lauer || || {{user|Mickey}} || || Software Developer
|-
| John Lee || || || || Software Developer
|-
| Tim Lee || || {{user|Tim}} || || Hardware Manager
|-
| Marek Lindner || ''marek'' at openmoko dot ''com'' || || || Software Developer
|-
| Xiangfu Liu || ''xiangfu'' at openmoko dot ''org'' || {{user|liuxf}} || || Software Developer
|-
| Jan 'Shoragan' Luebbe || || || || Openmoko student (part-time)
|-
| Steven Mosher || || {{user|steve}} || || Vice President of Marketing
|-
| Sean Moss-Pultz || || {{user|Sean}} || || CEO
|-
| Shawn Lin || || {{user|shawn_lin}} || || RF Engineer
|-
| Joerg Reisenweber || || {{user|jOERG}} || || Hardware Engineer
|-
| Michael Shiloh || ''michael'' at openmoko dot ''org'' || {{user|Michaelshiloh}} || || Head of Developer Relations
|-
| Wolfgang Spraul || ''wolfgang'' at openmoko dot ''com'' || || || Vice President of Engineering
|-
| Joachim Steiger || ''roh'' at openmoko dot ''org'' || {{user|Roh}} || roh || Central Services
|-
| Teenie Hung || || {{user|teenie_hung}} || || Operations Head
|-
| Harry Tsai || ''tsaiharry'' at gmail dot ''com'' || || || long time ago he was Vice President of Sales in Openmoko, but that is past.
|-
| Neng-Yu 'Tony' Tu || || {{user|Tony Tu}} || || Project manager (gta01/02), software developer (Left Openmoko. Here for archives.)
|-
| Brenda Wang || ''brenda_wang'' at openmoko dot ''com'' || {{user|Coolcat}} || || Used to Wiki editor . volunteer now.
|-
| Harald Welte || ''laforge'' at openmoko dot ''org'' || {{user|HaraldWelte}} || LaF0rge || (Left Openmoko. Here for archives.)
|-
| Daniel 'Alphaone' Willmann || || {{user|DanielWillmann}} || || Software Developer
|-
| Thomas Wood || || {{user|ThomasWood}} || ||
|-
| OLV Wu || ''olv'' at openmoko dot ''org'' || || || Software Developer
|-
| Erin Yeh || ''erin_yueh'' at openmoko dot ''org''||{{user|erin}} || || Software Developer
|}

== Prominent community members ==

Only add people who made a significant contribution to the Openmoko community.

{| class="wikitable sortable" style="margin: 0em " cellspacing="0" cellpadding="5" border="1"
! Name !! email !! Wiki username !! IRC nickname !! Position
|-
| Lorn Potter || ''lpotter'' at ''trolltech'' dot ''com'' || || lpotter || Qtopia developer
|-
| Rod Whitby || || {{user|RodWhitby}} || rwhitby || [[MokoMakefile]] author
|}

[[Category:Openmoko Inc]]

People

2009-04-01T10:27:21Z

Mickey: catch up with recent developments...

= People at Openmoko, Inc. =

See also [[Who_is_Who]] which hasn't been updated for some time.

== Staff ==
* Sean Moss-Pultz - CEO
* Steve Mosher - VP Marketing
* Ailsa Huang - Sales

== Former ==
* Harry Tsai - VP Sales
* Elsie Lee- Sales
* Jörg 'DocScrutinizer' Reisenweber - Hardware
* Carsten 'Raster' Haitzler
* Brenda Wang - Wiki
* Dr. Mickey Lauer - R&D FSO
* Werner Almesberger - R&D
* Tony (Neng-Yu) Tu -R&D
* Andy Green - Kernel R&D

User:Mickey

2009-03-17T00:53:08Z

Mickey:

[[Image:Mickey.jpg|left]]
===[http://www.vanille-media.de Michael 'Mickey' Lauer]===
Mickey is an independent IT contractor specialized in embedded linux, distributed systems, application frameworks, and GUI toolkits. Next to a doctoral degree in computer science, he brings in more than 20 years of programming experience, 7 years of those in open source contributing to various mobile and embedded Linux projects. He has been consulting and developing the Openmoko project since the beginning.

These days, he works on the multidevice multivendor [http://freesmartphone.org Freesmartphone.org] mobile middleware project.

OpenmokoFramework

2009-03-05T17:33:02Z

Mickey: /* Q/A */

{{Languages|OpenmokoFramework}}
{{FSO}}
{{Distributions|FSO}}

''s/Openmoko/freesmartphone.org/ :)''

Openmoko is basing on the freesmartphone.org (FSO) middleware. FSO will be in forthcoming Openmoko distributions. For more information see http://www.freesmartphone.org, http://docs.freesmartphone.org, and http://trac.freesmartphone.org.

==Q/A==
* ''Question'': Is this an Openmoko-only thing?
* ''Answer'': No. It's going to be available for all kinds of mobile hardware running Linux, i.e. OpenEZX, HTC, Glosfiish, etc.
* ''Question'': Is this a part of the current images yet?
* ''Answer'': Yes. It comes with SHR and Openmoko 2009.x testing images.
* ''Question'': What's the current status?
* ''Answer'': See right below or hop over to http://trac.freesmartphone.org .
** [[OpenmokoFramework/Status Update 1|Status Update 1]]
** [[OpenmokoFramework/Status Update 2|Status Update 2]]
** [[OpenmokoFramework/Status Update 3|Status Update 3]]
** [[OpenmokoFramework/Status Update 4|Status Update 4]]
** [http://wiki.openmoko.org/wiki/Fso-internal-om.pdf Openmoko Framework Presentation Taipei'08]
** [[OpenmokoFramework/Status Update 5|Status Update 5]]
** [[OpenmokoFramework/Status Update 6|Status Update 6]]
* ''Question'': How do I work the Zhone (FSO demo app) UI?
* ''Answer'': [[FSO UI Tutorial]]
* ''Question'': What is the easiest way to build it?
* ''Answer'': See [[Building_FSO]] for more information. The feeds are now at http://downloads.freesmartphone.org.

==Phases==
# Phase I is about getting the APIs right.
# Phase II is about getting the right APIs fast.

==Timeline (Phase I)==
* ''2009-07-01: [http://trac.freesmartphone.org/milestone/milestone6 milestone 6]''
* ''2009-03-31: [http://trac.freesmartphone.org/milestone/milestone5.5 milestone 5.5]''
* 2009-02-02: [[OpenmokoFramework/Status Update 6|milestone 5]] achieved
* 2008-11-11: [[OpenmokoFramework/Status Update 5|milestone 4]] achieved
* 2008-09-10: [[OpenmokoFramework/Status Update 4|milestone 3]] achieved
* 2008-07-01: [[OpenmokoFramework/Status Update 3|milestone 2]] achieved
* 2008-06-01: [[OpenmokoFramework/Status Update 2|milestone 1]] achieved

==Timeline (Phase II)==

... to be defined ...

==Purposes==
* Give people the infrastructure to create solid and exciting software products based on the Openmoko platform
* Support competing UIs while collaborating on developing services
* Encourage framework users (e.g. application developers) to also contribute to the framework

==Requirements==
* Make it simple
* Concentrate on core services
* Be programming language agnostic
* Be UI toolkit agnostic
* Try to reuse existing technologies as much as possible, but not at the cost of a bad API

==How to achieve that technically==
* Choose [[D-Bus]] as the collaboration line. Below dbus, we can work together. Above dbus, we can differentiate
* Expose features through dbus APIs implemented by UI-agnostic and language-agnostic services (daemons)
* Optimize for Openmoko devices, but support multiple architectures and purposes through plugin interfaces and suitable hardware abstraction mechanisms
* By not being afraid of reinventing the wheel for a wheelbarrow if all the existing wheels are made for sports cars

==Mandatory Reading==
* [http://adam.gomaa.us/blog/frameworks-exist-for-conceptual-integrity/ Frameworks exist for conceptual integrity]
* [http://humanized.com/weblog/2007/10/05/make_oss_humane/ Ten ways to make more humane open source software]
* [http://www.freesmartphone.org FreeSmartPhone.org Wiki]

==What this is NOT about==
This initiative does not cover low level services such as
* Bootloader, Kernel, or System Init.

This initiative does not cover high level services such as
* X-Window-System, Window Manager, UI Toolkits,
* Application Launchers, Applications, or Fancy UIs.

==Architectural Overview==
[[Image:OpenmokoFramework08.png |632px|frontside]]

==Software Components==

Please see the description at http://www.freesmartphone.org/index.php/Architecture

==Known API Consumers==

* [[Zhone]]
* [[SHR]]
* [[Tichy]]
* [[Paroli]]

==Tools==
* [[OpenmokoFramework/mdbus|mdbus]] -- a dbus introspection and interaction utility,
* [[OpenmokoFramework/cli|cli-framework]] -- a python dbus command line interface.
* [[OpenmokoFramework/mickeyterm|mickeyterm]] -- a MUXer-aware minimal terminal emulator.

==How to debug==
# log in via ssh
# killall python
# edit /etc/frameworkd.conf and add to the frameworkd section:
## log_level = DEBUG
## log_to = file
## log_destination = /somewhere/where/you/have/space (preferably SD or NFS, etc.)
# Read our [http://git.freesmartphone.org/?p=framework.git;a=blob;f=conf/example/frameworkd.conf documented frameworkd.conf] configuration file to learn about the other options.
# relaunch frameworkd (/etc/init.d/frameworkd stop; /etc/init.d/frameworkd start)
# log in via ssh (yes, again)
# export DISPLAY=:0.0
# run your favourite client (zhone, cli-framework, ...)

Attach the logs to the tickets, please.

==The role of Python==

Where we write new code, we will use Python to implement the dbus services. The reason for that being the rapid prototyping nature of Python and the emphasis on the [[D-Bus]] APIs. Using Python, the turnaround times to experiment with APIs are incredibly faster than for using a compiled language such as C or C++.

Once the APIs have been used by application programmers, we can start profiling and possibly reimplement some of the services with daemons written in Vala, ''if'' necessary. We might as well succeed in improving performance by using Pyrex/Cython/Ctypes to keep the benefits of Python.

==Team & Roadmap==

===Team===

* [[User:Mickey|Michael 'Mickey' Lauer]] (team leader) -- Openmoko freelancer, working in Frankfurt/Main, Germany.
* [[User:Shoragan|Jan 'Shoragan' Luebbe]] -- Openmoko student, working part-time in Brunswick, Germany.
* [[User:DanielWillmann|Daniel 'Alphaone' Willmann]] -- Openmoko student, working part-time in Brunswick, Germany.
* [[User:StefanSchmidt|Stefan Schmidt]] -- Openmoko student, working part-time in Brunswick, Germany.

===Roadmap===

The milestone releases are combined Openmoko Framework and [[Zhone]] releases. Remember: A feature that isn't visible, working, and tested in our framework testing application (Zhone) does ''not'' exist. Until Framework 1.0.0 (early 2009), we will not use any versioning in components. Afterwards, individual components may see individual releases.

'''Note: The milestones and tasks moved over to our [http://trac.freesmartphone.org issue tracker].'''

=== Download and see also ===

* [http://trac.freesmartphone.org/ Development tracker]
* [http://freesmartphone.org freesmartphone.org]
* [http://downloads.freesmartphone.org fso-testing and fso-unstable images and feeds] (maintained by Rod Whitby, MokoMakefile author)

[[Category:Framework|Framework]]
[[Category:FSO]]

OpenmokoFramework

2009-03-05T17:32:17Z

Mickey: /* Timeline (Phase I) */

{{Languages|OpenmokoFramework}}
{{FSO}}
{{Distributions|FSO}}

''s/Openmoko/freesmartphone.org/ :)''

Openmoko is basing on the freesmartphone.org (FSO) middleware. FSO will be in forthcoming Openmoko distributions. For more information see http://www.freesmartphone.org, http://docs.freesmartphone.org, and http://trac.freesmartphone.org.

==Q/A==
* ''Question'': Is this an Openmoko-only thing?
* ''Answer'': No. It's going to be available for all kinds of mobile hardware running Linux, i.e. OpenEZX, HTC, Glosfiish, etc.
* ''Question'': Is this a part of the current images yet?
* ''Answer'': Yes. It comes with SHR and Openmoko 2009.x testing images.
* ''Question'': What's the current status?
* ''Answer'': See right below or hop over to http://trac.freesmartphone.org .
** [[OpenmokoFramework/Status Update 1|Status Update 1]]
** [[OpenmokoFramework/Status Update 2|Status Update 2]]
** [[OpenmokoFramework/Status Update 3|Status Update 3]]
** [[OpenmokoFramework/Status Update 4|Status Update 4]]
** [http://wiki.openmoko.org/wiki/Fso-internal-om.pdf Openmoko Framework Presentation Taipei'08]
** [[OpenmokoFramework/Status Update 5|Status Update 5]]
** [[OpenmokoFramework/Status Update 6|Status Update 6]]
* ''Question'': How do I work the Zhone (FSO demo app) UI?
* ''Answer'': [[FSO UI Tutorial]]
* ''Question'': What is the easiest way to build it?
* ''Answer'': See [[Building_FSO]] for more information. The feeds are now at http://downloads.freesmartphone.org.

==Timeline (Phase I)==
* ''2009-07-01: [http://trac.freesmartphone.org/milestone/milestone6 milestone 6]''
* ''2009-03-31: [http://trac.freesmartphone.org/milestone/milestone5.5 milestone 5.5]''
* 2009-02-02: [[OpenmokoFramework/Status Update 6|milestone 5]] achieved
* 2008-11-11: [[OpenmokoFramework/Status Update 5|milestone 4]] achieved
* 2008-09-10: [[OpenmokoFramework/Status Update 4|milestone 3]] achieved
* 2008-07-01: [[OpenmokoFramework/Status Update 3|milestone 2]] achieved
* 2008-06-01: [[OpenmokoFramework/Status Update 2|milestone 1]] achieved

==Timeline (Phase II)==

... to be defined ...

==Purposes==
* Give people the infrastructure to create solid and exciting software products based on the Openmoko platform
* Support competing UIs while collaborating on developing services
* Encourage framework users (e.g. application developers) to also contribute to the framework

==Requirements==
* Make it simple
* Concentrate on core services
* Be programming language agnostic
* Be UI toolkit agnostic
* Try to reuse existing technologies as much as possible, but not at the cost of a bad API

==How to achieve that technically==
* Choose [[D-Bus]] as the collaboration line. Below dbus, we can work together. Above dbus, we can differentiate
* Expose features through dbus APIs implemented by UI-agnostic and language-agnostic services (daemons)
* Optimize for Openmoko devices, but support multiple architectures and purposes through plugin interfaces and suitable hardware abstraction mechanisms
* By not being afraid of reinventing the wheel for a wheelbarrow if all the existing wheels are made for sports cars

==Mandatory Reading==
* [http://adam.gomaa.us/blog/frameworks-exist-for-conceptual-integrity/ Frameworks exist for conceptual integrity]
* [http://humanized.com/weblog/2007/10/05/make_oss_humane/ Ten ways to make more humane open source software]
* [http://www.freesmartphone.org FreeSmartPhone.org Wiki]

==What this is NOT about==
This initiative does not cover low level services such as
* Bootloader, Kernel, or System Init.

This initiative does not cover high level services such as
* X-Window-System, Window Manager, UI Toolkits,
* Application Launchers, Applications, or Fancy UIs.

==Architectural Overview==
[[Image:OpenmokoFramework08.png |632px|frontside]]

==Software Components==

Please see the description at http://www.freesmartphone.org/index.php/Architecture

==Known API Consumers==

* [[Zhone]]
* [[SHR]]
* [[Tichy]]
* [[Paroli]]

==Tools==
* [[OpenmokoFramework/mdbus|mdbus]] -- a dbus introspection and interaction utility,
* [[OpenmokoFramework/cli|cli-framework]] -- a python dbus command line interface.
* [[OpenmokoFramework/mickeyterm|mickeyterm]] -- a MUXer-aware minimal terminal emulator.

==How to debug==
# log in via ssh
# killall python
# edit /etc/frameworkd.conf and add to the frameworkd section:
## log_level = DEBUG
## log_to = file
## log_destination = /somewhere/where/you/have/space (preferably SD or NFS, etc.)
# Read our [http://git.freesmartphone.org/?p=framework.git;a=blob;f=conf/example/frameworkd.conf documented frameworkd.conf] configuration file to learn about the other options.
# relaunch frameworkd (/etc/init.d/frameworkd stop; /etc/init.d/frameworkd start)
# log in via ssh (yes, again)
# export DISPLAY=:0.0
# run your favourite client (zhone, cli-framework, ...)

Attach the logs to the tickets, please.

==The role of Python==

Where we write new code, we will use Python to implement the dbus services. The reason for that being the rapid prototyping nature of Python and the emphasis on the [[D-Bus]] APIs. Using Python, the turnaround times to experiment with APIs are incredibly faster than for using a compiled language such as C or C++.

Once the APIs have been used by application programmers, we can start profiling and possibly reimplement some of the services with daemons written in Vala, ''if'' necessary. We might as well succeed in improving performance by using Pyrex/Cython/Ctypes to keep the benefits of Python.

==Team & Roadmap==

===Team===

* [[User:Mickey|Michael 'Mickey' Lauer]] (team leader) -- Openmoko freelancer, working in Frankfurt/Main, Germany.
* [[User:Shoragan|Jan 'Shoragan' Luebbe]] -- Openmoko student, working part-time in Brunswick, Germany.
* [[User:DanielWillmann|Daniel 'Alphaone' Willmann]] -- Openmoko student, working part-time in Brunswick, Germany.
* [[User:StefanSchmidt|Stefan Schmidt]] -- Openmoko student, working part-time in Brunswick, Germany.

===Roadmap===

The milestone releases are combined Openmoko Framework and [[Zhone]] releases. Remember: A feature that isn't visible, working, and tested in our framework testing application (Zhone) does ''not'' exist. Until Framework 1.0.0 (early 2009), we will not use any versioning in components. Afterwards, individual components may see individual releases.

'''Note: The milestones and tasks moved over to our [http://trac.freesmartphone.org issue tracker].'''

=== Download and see also ===

* [http://trac.freesmartphone.org/ Development tracker]
* [http://freesmartphone.org freesmartphone.org]
* [http://downloads.freesmartphone.org fso-testing and fso-unstable images and feeds] (maintained by Rod Whitby, MokoMakefile author)

[[Category:Framework|Framework]]
[[Category:FSO]]

OpenmokoFramework

2009-03-05T17:31:49Z

Mickey: /* Timeline */

{{Languages|OpenmokoFramework}}
{{FSO}}
{{Distributions|FSO}}

''s/Openmoko/freesmartphone.org/ :)''

Openmoko is basing on the freesmartphone.org (FSO) middleware. FSO will be in forthcoming Openmoko distributions. For more information see http://www.freesmartphone.org, http://docs.freesmartphone.org, and http://trac.freesmartphone.org.

==Q/A==
* ''Question'': Is this an Openmoko-only thing?
* ''Answer'': No. It's going to be available for all kinds of mobile hardware running Linux, i.e. OpenEZX, HTC, Glosfiish, etc.
* ''Question'': Is this a part of the current images yet?
* ''Answer'': Yes. It comes with SHR and Openmoko 2009.x testing images.
* ''Question'': What's the current status?
* ''Answer'': See right below or hop over to http://trac.freesmartphone.org .
** [[OpenmokoFramework/Status Update 1|Status Update 1]]
** [[OpenmokoFramework/Status Update 2|Status Update 2]]
** [[OpenmokoFramework/Status Update 3|Status Update 3]]
** [[OpenmokoFramework/Status Update 4|Status Update 4]]
** [http://wiki.openmoko.org/wiki/Fso-internal-om.pdf Openmoko Framework Presentation Taipei'08]
** [[OpenmokoFramework/Status Update 5|Status Update 5]]
** [[OpenmokoFramework/Status Update 6|Status Update 6]]
* ''Question'': How do I work the Zhone (FSO demo app) UI?
* ''Answer'': [[FSO UI Tutorial]]
* ''Question'': What is the easiest way to build it?
* ''Answer'': See [[Building_FSO]] for more information. The feeds are now at http://downloads.freesmartphone.org.

==Timeline (Phase I)==
* ''2009-05-31: [http://trac.freesmartphone.org/milestone/milestone5.5 milestone 6]''
* ''2009-03-31: [http://trac.freesmartphone.org/milestone/milestone5.5 milestone 5.5]''
* 2009-02-02: [[OpenmokoFramework/Status Update 6|milestone 5]] achieved
* 2008-11-11: [[OpenmokoFramework/Status Update 5|milestone 4]] achieved
* 2008-09-10: [[OpenmokoFramework/Status Update 4|milestone 3]] achieved
* 2008-07-01: [[OpenmokoFramework/Status Update 3|milestone 2]] achieved
* 2008-06-01: [[OpenmokoFramework/Status Update 2|milestone 1]] achieved

==Timeline (Phase II)==

... to be defined ...

==Purposes==
* Give people the infrastructure to create solid and exciting software products based on the Openmoko platform
* Support competing UIs while collaborating on developing services
* Encourage framework users (e.g. application developers) to also contribute to the framework

==Requirements==
* Make it simple
* Concentrate on core services
* Be programming language agnostic
* Be UI toolkit agnostic
* Try to reuse existing technologies as much as possible, but not at the cost of a bad API

==How to achieve that technically==
* Choose [[D-Bus]] as the collaboration line. Below dbus, we can work together. Above dbus, we can differentiate
* Expose features through dbus APIs implemented by UI-agnostic and language-agnostic services (daemons)
* Optimize for Openmoko devices, but support multiple architectures and purposes through plugin interfaces and suitable hardware abstraction mechanisms
* By not being afraid of reinventing the wheel for a wheelbarrow if all the existing wheels are made for sports cars

==Mandatory Reading==
* [http://adam.gomaa.us/blog/frameworks-exist-for-conceptual-integrity/ Frameworks exist for conceptual integrity]
* [http://humanized.com/weblog/2007/10/05/make_oss_humane/ Ten ways to make more humane open source software]
* [http://www.freesmartphone.org FreeSmartPhone.org Wiki]

==What this is NOT about==
This initiative does not cover low level services such as
* Bootloader, Kernel, or System Init.

This initiative does not cover high level services such as
* X-Window-System, Window Manager, UI Toolkits,
* Application Launchers, Applications, or Fancy UIs.

==Architectural Overview==
[[Image:OpenmokoFramework08.png |632px|frontside]]

==Software Components==

Please see the description at http://www.freesmartphone.org/index.php/Architecture

==Known API Consumers==

* [[Zhone]]
* [[SHR]]
* [[Tichy]]
* [[Paroli]]

==Tools==
* [[OpenmokoFramework/mdbus|mdbus]] -- a dbus introspection and interaction utility,
* [[OpenmokoFramework/cli|cli-framework]] -- a python dbus command line interface.
* [[OpenmokoFramework/mickeyterm|mickeyterm]] -- a MUXer-aware minimal terminal emulator.

==How to debug==
# log in via ssh
# killall python
# edit /etc/frameworkd.conf and add to the frameworkd section:
## log_level = DEBUG
## log_to = file
## log_destination = /somewhere/where/you/have/space (preferably SD or NFS, etc.)
# Read our [http://git.freesmartphone.org/?p=framework.git;a=blob;f=conf/example/frameworkd.conf documented frameworkd.conf] configuration file to learn about the other options.
# relaunch frameworkd (/etc/init.d/frameworkd stop; /etc/init.d/frameworkd start)
# log in via ssh (yes, again)
# export DISPLAY=:0.0
# run your favourite client (zhone, cli-framework, ...)

Attach the logs to the tickets, please.

==The role of Python==

Where we write new code, we will use Python to implement the dbus services. The reason for that being the rapid prototyping nature of Python and the emphasis on the [[D-Bus]] APIs. Using Python, the turnaround times to experiment with APIs are incredibly faster than for using a compiled language such as C or C++.

Once the APIs have been used by application programmers, we can start profiling and possibly reimplement some of the services with daemons written in Vala, ''if'' necessary. We might as well succeed in improving performance by using Pyrex/Cython/Ctypes to keep the benefits of Python.

==Team & Roadmap==

===Team===

* [[User:Mickey|Michael 'Mickey' Lauer]] (team leader) -- Openmoko freelancer, working in Frankfurt/Main, Germany.
* [[User:Shoragan|Jan 'Shoragan' Luebbe]] -- Openmoko student, working part-time in Brunswick, Germany.
* [[User:DanielWillmann|Daniel 'Alphaone' Willmann]] -- Openmoko student, working part-time in Brunswick, Germany.
* [[User:StefanSchmidt|Stefan Schmidt]] -- Openmoko student, working part-time in Brunswick, Germany.

===Roadmap===

The milestone releases are combined Openmoko Framework and [[Zhone]] releases. Remember: A feature that isn't visible, working, and tested in our framework testing application (Zhone) does ''not'' exist. Until Framework 1.0.0 (early 2009), we will not use any versioning in components. Afterwards, individual components may see individual releases.

'''Note: The milestones and tasks moved over to our [http://trac.freesmartphone.org issue tracker].'''

=== Download and see also ===

* [http://trac.freesmartphone.org/ Development tracker]
* [http://freesmartphone.org freesmartphone.org]
* [http://downloads.freesmartphone.org fso-testing and fso-unstable images and feeds] (maintained by Rod Whitby, MokoMakefile author)

[[Category:Framework|Framework]]
[[Category:FSO]]

OpenmokoFramework

2009-03-05T17:30:39Z

Mickey:

{{Languages|OpenmokoFramework}}
{{FSO}}
{{Distributions|FSO}}

''s/Openmoko/freesmartphone.org/ :)''

Openmoko is basing on the freesmartphone.org (FSO) middleware. FSO will be in forthcoming Openmoko distributions. For more information see http://www.freesmartphone.org, http://docs.freesmartphone.org, and http://trac.freesmartphone.org.

==Q/A==
* ''Question'': Is this an Openmoko-only thing?
* ''Answer'': No. It's going to be available for all kinds of mobile hardware running Linux, i.e. OpenEZX, HTC, Glosfiish, etc.
* ''Question'': Is this a part of the current images yet?
* ''Answer'': Yes. It comes with SHR and Openmoko 2009.x testing images.
* ''Question'': What's the current status?
* ''Answer'': See right below or hop over to http://trac.freesmartphone.org .
** [[OpenmokoFramework/Status Update 1|Status Update 1]]
** [[OpenmokoFramework/Status Update 2|Status Update 2]]
** [[OpenmokoFramework/Status Update 3|Status Update 3]]
** [[OpenmokoFramework/Status Update 4|Status Update 4]]
** [http://wiki.openmoko.org/wiki/Fso-internal-om.pdf Openmoko Framework Presentation Taipei'08]
** [[OpenmokoFramework/Status Update 5|Status Update 5]]
** [[OpenmokoFramework/Status Update 6|Status Update 6]]
* ''Question'': How do I work the Zhone (FSO demo app) UI?
* ''Answer'': [[FSO UI Tutorial]]
* ''Question'': What is the easiest way to build it?
* ''Answer'': See [[Building_FSO]] for more information. The feeds are now at http://downloads.freesmartphone.org.

== Timeline==
* ''2009-03-31: [http://trac.freesmartphone.org/milestone/milestone6 milestone 6]''
* 2009-02-02: [[OpenmokoFramework/Status Update 6|milestone 5]] achieved
* 2008-11-11: [[OpenmokoFramework/Status Update 5|milestone 4]] achieved
* 2008-09-10: [[OpenmokoFramework/Status Update 4|milestone 3]] achieved
* 2008-07-01: [[OpenmokoFramework/Status Update 3|milestone 2]] achieved
* 2008-06-01: [[OpenmokoFramework/Status Update 2|milestone 1]] achieved

==Purposes==
* Give people the infrastructure to create solid and exciting software products based on the Openmoko platform
* Support competing UIs while collaborating on developing services
* Encourage framework users (e.g. application developers) to also contribute to the framework

==Requirements==
* Make it simple
* Concentrate on core services
* Be programming language agnostic
* Be UI toolkit agnostic
* Try to reuse existing technologies as much as possible, but not at the cost of a bad API

==How to achieve that technically==
* Choose [[D-Bus]] as the collaboration line. Below dbus, we can work together. Above dbus, we can differentiate
* Expose features through dbus APIs implemented by UI-agnostic and language-agnostic services (daemons)
* Optimize for Openmoko devices, but support multiple architectures and purposes through plugin interfaces and suitable hardware abstraction mechanisms
* By not being afraid of reinventing the wheel for a wheelbarrow if all the existing wheels are made for sports cars

==Mandatory Reading==
* [http://adam.gomaa.us/blog/frameworks-exist-for-conceptual-integrity/ Frameworks exist for conceptual integrity]
* [http://humanized.com/weblog/2007/10/05/make_oss_humane/ Ten ways to make more humane open source software]
* [http://www.freesmartphone.org FreeSmartPhone.org Wiki]

==What this is NOT about==
This initiative does not cover low level services such as
* Bootloader, Kernel, or System Init.

This initiative does not cover high level services such as
* X-Window-System, Window Manager, UI Toolkits,
* Application Launchers, Applications, or Fancy UIs.

==Architectural Overview==
[[Image:OpenmokoFramework08.png |632px|frontside]]

==Software Components==

Please see the description at http://www.freesmartphone.org/index.php/Architecture

==Known API Consumers==

* [[Zhone]]
* [[SHR]]
* [[Tichy]]
* [[Paroli]]

==Tools==
* [[OpenmokoFramework/mdbus|mdbus]] -- a dbus introspection and interaction utility,
* [[OpenmokoFramework/cli|cli-framework]] -- a python dbus command line interface.
* [[OpenmokoFramework/mickeyterm|mickeyterm]] -- a MUXer-aware minimal terminal emulator.

==How to debug==
# log in via ssh
# killall python
# edit /etc/frameworkd.conf and add to the frameworkd section:
## log_level = DEBUG
## log_to = file
## log_destination = /somewhere/where/you/have/space (preferably SD or NFS, etc.)
# Read our [http://git.freesmartphone.org/?p=framework.git;a=blob;f=conf/example/frameworkd.conf documented frameworkd.conf] configuration file to learn about the other options.
# relaunch frameworkd (/etc/init.d/frameworkd stop; /etc/init.d/frameworkd start)
# log in via ssh (yes, again)
# export DISPLAY=:0.0
# run your favourite client (zhone, cli-framework, ...)

Attach the logs to the tickets, please.

==The role of Python==

Where we write new code, we will use Python to implement the dbus services. The reason for that being the rapid prototyping nature of Python and the emphasis on the [[D-Bus]] APIs. Using Python, the turnaround times to experiment with APIs are incredibly faster than for using a compiled language such as C or C++.

Once the APIs have been used by application programmers, we can start profiling and possibly reimplement some of the services with daemons written in Vala, ''if'' necessary. We might as well succeed in improving performance by using Pyrex/Cython/Ctypes to keep the benefits of Python.

==Team & Roadmap==

===Team===

* [[User:Mickey|Michael 'Mickey' Lauer]] (team leader) -- Openmoko freelancer, working in Frankfurt/Main, Germany.
* [[User:Shoragan|Jan 'Shoragan' Luebbe]] -- Openmoko student, working part-time in Brunswick, Germany.
* [[User:DanielWillmann|Daniel 'Alphaone' Willmann]] -- Openmoko student, working part-time in Brunswick, Germany.
* [[User:StefanSchmidt|Stefan Schmidt]] -- Openmoko student, working part-time in Brunswick, Germany.

===Roadmap===

The milestone releases are combined Openmoko Framework and [[Zhone]] releases. Remember: A feature that isn't visible, working, and tested in our framework testing application (Zhone) does ''not'' exist. Until Framework 1.0.0 (early 2009), we will not use any versioning in components. Afterwards, individual components may see individual releases.

'''Note: The milestones and tasks moved over to our [http://trac.freesmartphone.org issue tracker].'''

=== Download and see also ===

* [http://trac.freesmartphone.org/ Development tracker]
* [http://freesmartphone.org freesmartphone.org]
* [http://downloads.freesmartphone.org fso-testing and fso-unstable images and feeds] (maintained by Rod Whitby, MokoMakefile author)

[[Category:Framework|Framework]]
[[Category:FSO]]

OpenmokoFramework

2009-03-05T17:29:02Z

Mickey: /* Known API Consumers */

OpenmokoFramework

2009-03-05T17:24:51Z

Mickey: /* Software Components */

Neo FreeRunner Battery

2009-02-25T22:59:37Z

Mickey: /* Notes about expected battery life */

{{Neo FreeRunner Menu}}
=== GTA02 1200 mAh Smart Battery ===

*Internally, uses the SANYO 1200mAh cell (note that the Sanyo cell by itself does not have the Coulomb-counter and thus can not be used as a replacement for the Neo FreeRunner battery)
*Battery Technical information: [http://people.openmoko.org/tony_tu/GTA02/hardware/GTA02/CT-GTA02.pdf Detailed Battery Information]

* 1200mAh Smart Battery with Coulomb-counter and protection circuit
* The Smart Battery keeps track of maximum and current capacity for precise prediction of remaining battery power and time until shutdown, based on actual power dissipation.

For more information, see the GTA01 battery info at [[Neo1973 Battery]]

=== Notes about expected battery life ===
Battery life depends on your usage pattern. The maximum you can get is ~70h [[StandbyLifetime]], mostly in suspend, with multiple short wakeups.

== Known Issues ==

=== Make sure your battery never discharges completely. ===

This is an issue because the internal charging circuitry can not be turned on until the FreeRunner has booted, and booting through USB power alone does not work on early A5/6 devices.
If your FreeRunner boots to the point of showing something on screen when battery removed and connected to OM-wallcharger, your device isn't affected by this issue.

Depending on NAND bootloader version there might also be a red flashlight on AUX indicating postponed boot while charging battery to a required minimum - just keep your FR hooked up to the charger then until it boots. Or boot to NOR if it doesn't recover during some ten minutes.

==== What to do if your battery has become completely discharged ====

See the workarounds [[Neo_FreeRunner_Hardware_Issues#Can.27t_boot_with_discharged_or_missing_battery|here]].

==== More tricks ====

''Q: Does anyone know WHY it don't charge when it is off? My logic says that it is very important to have the option charge the battery when it is flat.''

A: I can't give you a simple answer. Charging is controlled by the PCF50633
chip, based on configuration values that are written to it by u-boot,
Linux, and userspace programs. Some of these settings are preserved
across a power-cycle (the PCF50633 has a small backup battery that's
also used to keep the RTC running) so the behavior at startup depends on
the software that you used during your last session.

Another complication is that some Freerunners are capable of starting up
without a battery while others are not (possibly due to different
capacitor values on the internal power rails).

I can give a few hints:
* The current (Sep. 2nd, 2008) u-boot has a bug that means it will not properly charge from the wall charger. Try a USB cable into a PC instead.
** Feb. 2009 -- Is the preceding comment still correct? Bug number?
* Try booting through NOR u-boot instead (hold aux and then power) with both the wall charger or a 500mA USB connection, then try booting Linux.
* Try to boot into the NAND u-boot menu (hold power and then aux) and then select "power off". This may leave the device in a state were it will charge. Wait 15 minutes and then try to boot Linux.
* If the device shuts off during one of the above attempts, let it sit for a few minutes and then try that same item once again

Kudos to Mike Montour on the
[http://lists.openmoko.org/pipermail/community/2008-September/029243.html Community mailing list].

Another trick to get a Freerunner with a flat battery up and running would be to press and hold AUX, and then plug in the wall charger. Suggested by joerg, confirmed to work by user [http://wiki.openmoko.org/wiki/User:Azmodie azmodie], user [http://wiki.openmoko.org/wiki/User:Jhenkins jhenkins], user [[User:Aragorn|aragorn]] (worked even without battery).

== Compatible Replacement Batteries ==

Other known FreeRunner-compatible batteries include the BL-series (BL-4X, BL-5X) from Nokia, and their third-party equivalents.
These may not work to revive a device and may not report charge information.
It is probably a good idea to check that your battery is not greater than the stock battery's voltage of 3.7V (the above suggests that 4.5VDC should be fine) unless you know what you are doing.

{| border="1" cellpadding="4" cellspacing="0"
!Battery Model
!Capacity (mAh)
!Charge info reported
!Notes
|-
|NOKIA BL-4
|
|no
|
|-
|NOKIA BL-4C
|750
|no
|Slightly thinner than original.
|-
|NOKIA BL-5B
|760/890
|
|
|-
|NOKIA BL-5C
|950
|no
|
|-
|NOKIA BL-6C
|1070
|no
|
|-
|NOKIA BR-6C
|?
|no
|
|-
|Garmin GPS 10x
|1100
|no
|
|}

== Alien Charging of Battery ==

Nokia devices (phones and stand-alone chargers) usually will not charge
non-Nokia batteries, most likely because they can't be sure they have
the correct charging parameters (and of course Nokia isn't interested in supporting use of alien batteries with their phones).

Most after-market or no-name brands of Nokia-compatible chargers don't
test the make of the battery, most likely because adding the capability
to perform this test would add to the cost of the charger and limit it's universal character (that's not the interest of second source manufacturers).

Thus:
* You can use a Nokia or Nokia-compatible BL-4C, BL-5C, or BL-6C in the Neo
* You can charge the Neo battery in a Nokia-compatible charger that is not Nokia branded
* You can NOT charge the Neo battery in a Nokia branded phone or charger

Alternatively, the Garmin GPS 10X, a Bluetooth GPS device, uses a compatible battery to the OpenMoko FreeRunner. The device can be used to charge FreeRunner batteries at 100mA, 500mA or 1A over miniUSB (including deep-discharged batteries).

For more information about USB battery chargers that can be used with the Neo FreeRunner see
{{main|USB charger}}

== DIY external battery pack from a Minty case ==

'''Mintyboost:'''

Charge from a couple of AA batteries: [http://www.ladyada.net/make/mintyboost/ Minty Boost!], [http://www.millions.ca/~stacy/mintyboost/ report on a Neo FreeRunner application].

Adding the 47k resistor to the minty boost so that the Freerunner fast charges at 1A is a poor idea for a couple reasons, the biggest one being that the minty boost can't supply 1A the max is 600mA. as far as I know, there is no magic resistor to identify a 500mA charger to the Freerunner, it depends on USB host telling it that it can provide 500mA. Second, the ID pin is in the USB micro connector, so you would either need to put a micro connector on your minty boost (with the correct resistor installed) or use a hacked cable.

Even if the Linear Technology step up voltage converter is supposed to be able to do 600mA, the AA cells seem to have a problem with supplying 500mA. They get a little toasty :-). One powerpack built using D cells doesn't seem to have any issues with supplying 500mA.

[[Category:Battery]]
[[Category:Neo FreeRunner Hardware]]

OpenmokoFramework

2009-02-23T17:32:08Z

Mickey: /* Architectural Overview */

{{Languages|OpenmokoFramework}}
{{FSO}}
{{Distributions|FSO}}

FSO is an abbreviation for FreeSmartphone.Org. With FSO, Openmoko is working on a stable system services software back-end. The framework will be used in forthcoming Openmoko distributions -- a demonstration one is available as FSO-image. For more information see http://www.freesmartphone.org and http://trac.freesmartphone.org .

==Q/A==
* ''Question'': Is this an Openmoko-only thing?
* ''Answer'': No. It's going to be available for all kinds of mobile hardware running Linux, i.e. OpenEZX, HTC, Glosfiish, etc.
* ''Question'': Is this a part of the current images yet?
* ''Answer'': Yes. It comes with SHR and Openmoko 2009.x testing images.
* ''Question'': What's the current status?
* ''Answer'': See right below or hop over to http://trac.freesmartphone.org .
** [[OpenmokoFramework/Status Update 1|Status Update 1]]
** [[OpenmokoFramework/Status Update 2|Status Update 2]]
** [[OpenmokoFramework/Status Update 3|Status Update 3]]
** [[OpenmokoFramework/Status Update 4|Status Update 4]]
** [http://wiki.openmoko.org/wiki/Fso-internal-om.pdf Openmoko Framework Presentation Taipei'08]
** [[OpenmokoFramework/Status Update 5|Status Update 5]]
** [[OpenmokoFramework/Status Update 6|Status Update 6]]
* ''Question'': How do I work the Zhone (FSO demo app) UI?
* ''Answer'': [[FSO UI Tutorial]]
* ''Question'': What is the easiest way to build it?
* ''Answer'': See [[Building_FSO]] for more information. The feeds are now at http://downloads.freesmartphone.org.

== Timeline==
* ''2009-03-31: [http://trac.freesmartphone.org/milestone/milestone6 milestone 6]''
* 2009-02-02: [[OpenmokoFramework/Status Update 6|milestone 5]] achieved
* 2008-11-11: [[OpenmokoFramework/Status Update 5|milestone 4]] achieved
* 2008-09-10: [[OpenmokoFramework/Status Update 4|milestone 3]] achieved
* 2008-07-01: [[OpenmokoFramework/Status Update 3|milestone 2]] achieved
* 2008-06-01: [[OpenmokoFramework/Status Update 2|milestone 1]] achieved

==Purposes==
* Give people the infrastructure to create solid and exciting software products based on the Openmoko platform
* Support competing UIs while collaborating on developing services
* Encourage framework users (e.g. application developers) to also contribute to the framework

==Requirements==
* Make it simple
* Concentrate on core services
* Be programming language agnostic
* Be UI toolkit agnostic
* Try to reuse existing technologies as much as possible, but not at the cost of a bad API

==How to achieve that technically==
* Choose [[D-Bus]] as the collaboration line. Below dbus, we can work together. Above dbus, we can differentiate
* Expose features through dbus APIs implemented by UI-agnostic and language-agnostic services (daemons)
* Optimize for Openmoko devices, but support multiple architectures and purposes through plugin interfaces and suitable hardware abstraction mechanisms
* By not being afraid of reinventing the wheel for a wheelbarrow if all the existing wheels are made for sports cars

==Mandatory Reading==
* [http://adam.gomaa.us/blog/frameworks-exist-for-conceptual-integrity/ Frameworks exist for conceptual integrity]
* [http://humanized.com/weblog/2007/10/05/make_oss_humane/ Ten ways to make more humane open source software]
* [http://www.freesmartphone.org FreeSmartPhone.org Wiki]

==What this is NOT about==
This initiative does not cover low level services such as
* Bootloader, Kernel, or System Init.

This initiative does not cover high level services such as
* X-Window-System, Window Manager, UI Toolkits,
* Application Launchers, Applications, or Fancy UIs.

==Architectural Overview==
[[Image:OpenmokoFramework08.png |632px|frontside]]

==Software Components==

We differentiate between low-level and high-level services -- dbus will be used to communicate horizontally and vertically.

====Low-Level Services====

=====Device Control=====
The low level device control service manages peripheral control, i.e. controlling power for individual subsystems such as
* GSM, WiFi, Bluetooth, GPS, as well as
* Backlight brightness and power,
* Turning LEDs on and off, etc.
It also deals with
* Charging, suspend/resume,
* Accelerometers, and buttons.
Last but not least, it sends notifications about the user's activity so that listeners have a chance to
* Change to powersaving modes, or
* Lock the device.
We implement the following software for that:
* [http://www.freesmartphone.org/index.php/Implementations/OpenDeviceDaemon odeviced]

=====Audio=====
The low level audio service relies on a working ALSA device driver with the dmix software mixing plugin (*). On top of that, there is the GStreamer streaming media framework:
* [http://gstreamer.freedesktop.org/ gstreamer]

'''Gstreamer''' is to be used for all kinds of event sounds where a) multiple audio formats need to be supported and b) a latency of about one second is acceptable. This goes for e.g. ring tones, welcome tones, plug indication.

*) Initially, we wanted to use PulseAudio on top of ALSA, however currently it has serious performance problems on this hardware. [http://lists.openmoko.org/pipermail/devel/2008-July/000253.html]

=====GSM=====
The low level GSM services expect a modem complying to GSM 07.07, GSM 07.05, and assorted GSM specifications, talking an AT-protocol over a serial line. If GSM 07.10 is supported, we use the multiplexing daemon to export virtual serial lines over which -- again -- AT-protocol can be spoken:
* [http://www.freesmartphone.org/index.php/Implementations/gsm0710muxd gsm0710muxd]

=====Bluetooth=====
The low level Bluetooth services rely on the official Linux Bluetooth subsystem:
* [http://www.bluez.org BlueZ].

=====GPS=====
The low level GPS services assume a GPS device that talks NMEA over a device node. We implemented an [[ogpsd]] daemon speaking an extended Gypsy API:
* [http://gypsy.freedesktop.org Gypsy]

=====Network=====
The low level networking service assumes network interfaces, such as USB, Ethernet, Wifi, etc. We rely on the following software here:
* Intel Connection Manager
* PPP

====High Level====

=====Usage=====
The Usage subsystem is concerned with coordinating application I/O requirements. Applications are not supposed to turn on or off devices, since they do not have any knowledge about concurrent applications that may be also using the device -- think ''reference counting'' for I/O requirements.

With this added layer, we could later think about monitoring subsystems, subsystem usage statistics, or accounting.

See discussion page about PolicyKit.

=====Events=====
* Signalling events via I/O (ringing, blinking, vibrating)
* Might use fd.o notification API

=====PIM=====
An intelligent storage database server. This is being carried out as a Google Summer of Code project. See complete description [http://www.neo1973-germany.de/wiki/pyPimd here].

=====Context=====
* Intelligent context API, integrating location as one -- among other -- sources
* Geoclue?

=====[http://www.freesmartphone.org/index.php/Standards/PhoneAPI Phone]=====
The phone subsystem can be used to create and manage voices communications. It makes abstraction of the protocol used.

==== [http://www.freesmartphone.org/index.php/Implementations/OpenPreferencesDaemon Preferences] ====
* Settings database

=====Network=====
* High-level networking queries

==Known API Consumers==

(TODO: add links...)

* [[Zhone]]
* [[SHR]]
* [[Tichy]]
* [[Paroli]]

==Tools==
* [[OpenmokoFramework/mdbus|mdbus]] -- a dbus introspection and interaction utility,
* [[OpenmokoFramework/cli|cli-framework]] -- a python dbus command line interface.
* [[OpenmokoFramework/mickeyterm|mickeyterm]] -- a MUXer-aware minimal terminal emulator.

==How to debug==
# log in via ssh
# killall python
# edit /etc/frameworkd.conf and add to the frameworkd section:
## log_level = DEBUG
## log_to = file
## log_destination = /somewhere/where/you/have/space (preferably SD or NFS, etc.)
# Read our [http://git.freesmartphone.org/?p=framework.git;a=blob;f=conf/example/frameworkd.conf documented frameworkd.conf] configuration file to learn about the other options.
# relaunch frameworkd (/etc/init.d/frameworkd stop; /etc/init.d/frameworkd start)
# log in via ssh (yes, again)
# export DISPLAY=:0.0
# run your favourite client (zhone, cli-framework, ...)

Attach the logs to the tickets, please.

==The role of Python==

Where we write new code, we will use Python to implement the dbus services. The reason for that being the rapid prototyping nature of Python and the emphasis on the [[D-Bus]] APIs. Using Python, the turnaround times to experiment with APIs are incredibly faster than for using a compiled language such as C or C++.

Once the APIs have been used by application programmers, we can start profiling and possibly reimplement some of the services with daemons written in Vala, ''if'' necessary. We might as well succeed in improving performance by using Pyrex/Cython/Ctypes to keep the benefits of Python.

==Team & Roadmap==

===Team===

* [[User:Mickey|Michael 'Mickey' Lauer]] (team leader) -- Openmoko freelancer, working in Frankfurt/Main, Germany.
* [[User:Shoragan|Jan 'Shoragan' Luebbe]] -- Openmoko student, working part-time in Brunswick, Germany.
* [[User:DanielWillmann|Daniel 'Alphaone' Willmann]] -- Openmoko student, working part-time in Brunswick, Germany.
* [[User:StefanSchmidt|Stefan Schmidt]] -- Openmoko student, working part-time in Brunswick, Germany.

===Roadmap===

The milestone releases are combined Openmoko Framework and [[Zhone]] releases. Remember: A feature that isn't visible, working, and tested in our framework testing application (Zhone) does ''not'' exist. Until Framework 1.0.0 (early 2009), we will not use any versioning in components. Afterwards, individual components may see individual releases.

'''Note: The milestones and tasks moved over to our [http://trac.freesmartphone.org issue tracker].'''

=== Download and see also ===

* [http://trac.freesmartphone.org/ Development tracker]
* [http://freesmartphone.org freesmartphone.org]
* [http://downloads.freesmartphone.org fso-testing and fso-unstable images and feeds] (maintained by Rod Whitby, MokoMakefile author)

[[Category:Framework|Framework]]
[[Category:FSO]]

OpenmokoFramework

2009-02-23T17:30:47Z

Mickey: /* Q/A */

{{Languages|OpenmokoFramework}}
{{FSO}}
{{Distributions|FSO}}

FSO is an abbreviation for FreeSmartphone.Org. With FSO, Openmoko is working on a stable system services software back-end. The framework will be used in forthcoming Openmoko distributions -- a demonstration one is available as FSO-image. For more information see http://www.freesmartphone.org and http://trac.freesmartphone.org .

==Q/A==
* ''Question'': Is this an Openmoko-only thing?
* ''Answer'': No. It's going to be available for all kinds of mobile hardware running Linux, i.e. OpenEZX, HTC, Glosfiish, etc.
* ''Question'': Is this a part of the current images yet?
* ''Answer'': Yes. It comes with SHR and Openmoko 2009.x testing images.
* ''Question'': What's the current status?
* ''Answer'': See right below or hop over to http://trac.freesmartphone.org .
** [[OpenmokoFramework/Status Update 1|Status Update 1]]
** [[OpenmokoFramework/Status Update 2|Status Update 2]]
** [[OpenmokoFramework/Status Update 3|Status Update 3]]
** [[OpenmokoFramework/Status Update 4|Status Update 4]]
** [http://wiki.openmoko.org/wiki/Fso-internal-om.pdf Openmoko Framework Presentation Taipei'08]
** [[OpenmokoFramework/Status Update 5|Status Update 5]]
** [[OpenmokoFramework/Status Update 6|Status Update 6]]
* ''Question'': How do I work the Zhone (FSO demo app) UI?
* ''Answer'': [[FSO UI Tutorial]]
* ''Question'': What is the easiest way to build it?
* ''Answer'': See [[Building_FSO]] for more information. The feeds are now at http://downloads.freesmartphone.org.

== Timeline==
* ''2009-03-31: [http://trac.freesmartphone.org/milestone/milestone6 milestone 6]''
* 2009-02-02: [[OpenmokoFramework/Status Update 6|milestone 5]] achieved
* 2008-11-11: [[OpenmokoFramework/Status Update 5|milestone 4]] achieved
* 2008-09-10: [[OpenmokoFramework/Status Update 4|milestone 3]] achieved
* 2008-07-01: [[OpenmokoFramework/Status Update 3|milestone 2]] achieved
* 2008-06-01: [[OpenmokoFramework/Status Update 2|milestone 1]] achieved

==Purposes==
* Give people the infrastructure to create solid and exciting software products based on the Openmoko platform
* Support competing UIs while collaborating on developing services
* Encourage framework users (e.g. application developers) to also contribute to the framework

==Requirements==
* Make it simple
* Concentrate on core services
* Be programming language agnostic
* Be UI toolkit agnostic
* Try to reuse existing technologies as much as possible, but not at the cost of a bad API

==How to achieve that technically==
* Choose [[D-Bus]] as the collaboration line. Below dbus, we can work together. Above dbus, we can differentiate
* Expose features through dbus APIs implemented by UI-agnostic and language-agnostic services (daemons)
* Optimize for Openmoko devices, but support multiple architectures and purposes through plugin interfaces and suitable hardware abstraction mechanisms
* By not being afraid of reinventing the wheel for a wheelbarrow if all the existing wheels are made for sports cars

==Mandatory Reading==
* [http://adam.gomaa.us/blog/frameworks-exist-for-conceptual-integrity/ Frameworks exist for conceptual integrity]
* [http://humanized.com/weblog/2007/10/05/make_oss_humane/ Ten ways to make more humane open source software]
* [http://www.freesmartphone.org FreeSmartPhone.org Wiki]

==What this is NOT about==
This initiative does not cover low level services such as
* Bootloader, Kernel, or System Init.

This initiative does not cover high level services such as
* X-Window-System, Window Manager, UI Toolkits,
* Application Launchers, Applications, or Fancy UIs.

==Architectural Overview==
[[Image:OpenmokoFramework08.png |823px|frontside]]

==Software Components==

We differentiate between low-level and high-level services -- dbus will be used to communicate horizontally and vertically.

====Low-Level Services====

=====Device Control=====
The low level device control service manages peripheral control, i.e. controlling power for individual subsystems such as
* GSM, WiFi, Bluetooth, GPS, as well as
* Backlight brightness and power,
* Turning LEDs on and off, etc.
It also deals with
* Charging, suspend/resume,
* Accelerometers, and buttons.
Last but not least, it sends notifications about the user's activity so that listeners have a chance to
* Change to powersaving modes, or
* Lock the device.
We implement the following software for that:
* [http://www.freesmartphone.org/index.php/Implementations/OpenDeviceDaemon odeviced]

=====Audio=====
The low level audio service relies on a working ALSA device driver with the dmix software mixing plugin (*). On top of that, there is the GStreamer streaming media framework:
* [http://gstreamer.freedesktop.org/ gstreamer]

'''Gstreamer''' is to be used for all kinds of event sounds where a) multiple audio formats need to be supported and b) a latency of about one second is acceptable. This goes for e.g. ring tones, welcome tones, plug indication.

*) Initially, we wanted to use PulseAudio on top of ALSA, however currently it has serious performance problems on this hardware. [http://lists.openmoko.org/pipermail/devel/2008-July/000253.html]

=====GSM=====
The low level GSM services expect a modem complying to GSM 07.07, GSM 07.05, and assorted GSM specifications, talking an AT-protocol over a serial line. If GSM 07.10 is supported, we use the multiplexing daemon to export virtual serial lines over which -- again -- AT-protocol can be spoken:
* [http://www.freesmartphone.org/index.php/Implementations/gsm0710muxd gsm0710muxd]

=====Bluetooth=====
The low level Bluetooth services rely on the official Linux Bluetooth subsystem:
* [http://www.bluez.org BlueZ].

=====GPS=====
The low level GPS services assume a GPS device that talks NMEA over a device node. We implemented an [[ogpsd]] daemon speaking an extended Gypsy API:
* [http://gypsy.freedesktop.org Gypsy]

=====Network=====
The low level networking service assumes network interfaces, such as USB, Ethernet, Wifi, etc. We rely on the following software here:
* Intel Connection Manager
* PPP

====High Level====

=====Usage=====
The Usage subsystem is concerned with coordinating application I/O requirements. Applications are not supposed to turn on or off devices, since they do not have any knowledge about concurrent applications that may be also using the device -- think ''reference counting'' for I/O requirements.

With this added layer, we could later think about monitoring subsystems, subsystem usage statistics, or accounting.

See discussion page about PolicyKit.

=====Events=====
* Signalling events via I/O (ringing, blinking, vibrating)
* Might use fd.o notification API

=====PIM=====
An intelligent storage database server. This is being carried out as a Google Summer of Code project. See complete description [http://www.neo1973-germany.de/wiki/pyPimd here].

=====Context=====
* Intelligent context API, integrating location as one -- among other -- sources
* Geoclue?

=====[http://www.freesmartphone.org/index.php/Standards/PhoneAPI Phone]=====
The phone subsystem can be used to create and manage voices communications. It makes abstraction of the protocol used.

==== [http://www.freesmartphone.org/index.php/Implementations/OpenPreferencesDaemon Preferences] ====
* Settings database

=====Network=====
* High-level networking queries

==Known API Consumers==

(TODO: add links...)

* [[Zhone]]
* [[SHR]]
* [[Tichy]]
* [[Paroli]]

==Tools==
* [[OpenmokoFramework/mdbus|mdbus]] -- a dbus introspection and interaction utility,
* [[OpenmokoFramework/cli|cli-framework]] -- a python dbus command line interface.
* [[OpenmokoFramework/mickeyterm|mickeyterm]] -- a MUXer-aware minimal terminal emulator.

==How to debug==
# log in via ssh
# killall python
# edit /etc/frameworkd.conf and add to the frameworkd section:
## log_level = DEBUG
## log_to = file
## log_destination = /somewhere/where/you/have/space (preferably SD or NFS, etc.)
# Read our [http://git.freesmartphone.org/?p=framework.git;a=blob;f=conf/example/frameworkd.conf documented frameworkd.conf] configuration file to learn about the other options.
# relaunch frameworkd (/etc/init.d/frameworkd stop; /etc/init.d/frameworkd start)
# log in via ssh (yes, again)
# export DISPLAY=:0.0
# run your favourite client (zhone, cli-framework, ...)

Attach the logs to the tickets, please.

==The role of Python==

Where we write new code, we will use Python to implement the dbus services. The reason for that being the rapid prototyping nature of Python and the emphasis on the [[D-Bus]] APIs. Using Python, the turnaround times to experiment with APIs are incredibly faster than for using a compiled language such as C or C++.

Once the APIs have been used by application programmers, we can start profiling and possibly reimplement some of the services with daemons written in Vala, ''if'' necessary. We might as well succeed in improving performance by using Pyrex/Cython/Ctypes to keep the benefits of Python.

==Team & Roadmap==

===Team===

* [[User:Mickey|Michael 'Mickey' Lauer]] (team leader) -- Openmoko freelancer, working in Frankfurt/Main, Germany.
* [[User:Shoragan|Jan 'Shoragan' Luebbe]] -- Openmoko student, working part-time in Brunswick, Germany.
* [[User:DanielWillmann|Daniel 'Alphaone' Willmann]] -- Openmoko student, working part-time in Brunswick, Germany.
* [[User:StefanSchmidt|Stefan Schmidt]] -- Openmoko student, working part-time in Brunswick, Germany.

===Roadmap===

The milestone releases are combined Openmoko Framework and [[Zhone]] releases. Remember: A feature that isn't visible, working, and tested in our framework testing application (Zhone) does ''not'' exist. Until Framework 1.0.0 (early 2009), we will not use any versioning in components. Afterwards, individual components may see individual releases.

'''Note: The milestones and tasks moved over to our [http://trac.freesmartphone.org issue tracker].'''

=== Download and see also ===

* [http://trac.freesmartphone.org/ Development tracker]
* [http://freesmartphone.org freesmartphone.org]
* [http://downloads.freesmartphone.org fso-testing and fso-unstable images and feeds] (maintained by Rod Whitby, MokoMakefile author)

[[Category:Framework|Framework]]
[[Category:FSO]]

File:OpenmokoFramework08.png

2009-02-23T17:29:16Z

Mickey: uploaded a new version of "Image:OpenmokoFramework08.png"

StandbyLifetime

2009-02-12T22:39:11Z

Mickey:

StandbyLifetime

2009-02-12T22:14:30Z

Mickey:

StandbyLifetime

2009-02-12T22:14:17Z

Mickey:

StandbyLifetime

2009-02-12T17:01:26Z

Mickey:

GPRS FSO

2009-02-12T15:18:26Z

Mickey: /* Current state */

{{FSO}}
This page documents the GSM networking solutions (commonly known as GPRS) using the [[OpenmokoFramework|FreeSmartphone.Org]] framework (FSO).

There are other ways to enable wireless communications on the smartphone, including [[Bluetooth]] and [[Wireless_Networking|WLAN]].

== Current state ==

Since milestone 2 the system dbus has been extended with methods that enables connectivity using GPRS. The functionality is available under <code>org.freesmartphone.ogsmd</code> at <code>/org/freesmartphone/GSM/Device</code>.

The implementation should not interfere with other phone functionality, such as placing calls. In other words: you can use GPRS while talking on the phone without hanging up. Note though that depending on hardware and networking, simultaneous data transmission and voice call alerting (let alone performing calls) might not be possible.

Since FSO is a middleware it offers no GUI, however it's fairly easy to use the methods available using any dbus tool.

The methods available:
[METHOD] org.freesmartphone.GSM.PDP.ActivateContext( s:apn, s:user, s:password )
[METHOD] org.freesmartphone.GSM.PDP.DeactivateContext()
[METHOD] org.freesmartphone.GSM.PDP.GetCurrentGprsClass()
[METHOD] org.freesmartphone.GSM.PDP.ListAvailableGprsClasses()
[METHOD] org.freesmartphone.GSM.PDP.SetCurrentGprsClass( s:class_ )
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus( i:index, s:status, a{sv}:properties )

Use ''mdbus -s -l'' to monitor the emitted signals. Signals will look roughly like this:

:ActivateContext( s:apn, s:user, s:password )
<pre>
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus
from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'outgoing'),
dbus.Dictionary({}, signature=dbus.Signature('sv')))
</pre>
:Once the connection is established (takes 3-4 seconds for me) a new signal is emitted
<pre>
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus
from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'active'),
dbus.Dictionary({}, signature=dbus.Signature('sv')))
</pre>
:DeactivateContext
<pre>
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus
from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'release'),
dbus.Dictionary({}, signature=dbus.Signature('sv')))
</pre>

== Using scripts ==

While we wait for the preferences part of FSO to be completed (and a GUI), we can use two shell scripts. You need to know three things to successfully connect via GPRS (your carrier should provide this information to you):
* the APN to use,
* the username, and
* the password.
If your APN has no username or password, you must still provide a string to satisfy the framework's input requirements. Entering bogus data, such as the "x" above, will suffice.

To connect, put the following in a file and make it executable (<code>chmod +x gprs-on.sh</code>):
<pre>
#!/bin/sh
APN="internet.parlino.se"
USERNAME="x"
PASSWORD="x"
BUSNAME="org.freesmartphone.ogsmd"
OBJECTPATH="/org/freesmartphone/GSM/Device"
METHODNAME="org.freesmartphone.GSM.PDP.ActivateContext"
mdbus -s $BUSNAME $OBJECTPATH $METHODNAME $APN "$USERNAME" "$PASSWORD"
</pre>
To disconnect, use the following method instead (<code>chmod +x gprs-off.sh</code>):
<pre>
#!/bin/sh
BUSNAME="org.freesmartphone.ogsmd"
OBJECTPATH="/org/freesmartphone/GSM/Device"
METHODNAME="org.freesmartphone.GSM.PDP.DeactivateContext"
mdbus -s $BUSNAME $OBJECTPATH $METHODNAME
</pre>
The ''on'' script, using the ActivateContext method, will:
* setup a ppp interface (normally ppp0) (and assign IP address)
* setup (replace) the default route
* setup DNS
with settings received from the ISP.

For a list of known APN:s, see the [[GPRS#Some_APN_names_for_reference|main GPRS page]].

== Troubleshooting ==

* When a something like '''org.freedesktop.DBus.Error.UnknownMethod''' appears make sure that:
** frameworkd is started of course
** That the method did not hide in an other place than expected follow the white [[D-Bus|Rabbit]]
* Online script runs without error but pppd did not start
** use '''logread''' to debug....
** Maybe the kernelmodule ppp-generic is not loaded, try modprobe. ( you can do '''echo ppp-generic > /etc/modutils.d/ppp-generic''' to load the module at boot time )
** Maybe you have to do a '''mknod /dev/ppp c 108 0'''
* No MUX Channels available
** Means that the frameworkd has no free channel available to connect to the GSM Modem.
** Restart the frameworkd and the phone Application (aka ophoned or zhone). Works fine for me.
* MISC Troubleshooting
** Switch the frameworkd loglevel to DEBUG (/etc/frameworkd.conf)
** use the source!

== Using a GUI ==
[[Framework-settings]]

== See also ==
* [[GPRS]]
* [[OpenmokoFramework/mdbus]]

[[Category:FSO]]
[[Category:Networking]]
[[Category:Advanced End User]]

StandbyLifetime

2009-02-12T14:33:21Z

Mickey:

StandbyLifetime

2009-02-12T09:09:52Z

Mickey:

StandbyLifetime

2009-02-12T03:03:58Z

Mickey:

StandbyLifetime

2009-02-11T23:01:07Z

Mickey:

StandbyLifetime

2009-02-11T22:56:17Z

Mickey:

StandbyLifetime

2009-02-11T22:54:07Z

Mickey: New page: Standby lifetime test with my FreeRunner running FSO MS5. <pre> 00h Tuesday, 03:00 100% 10h Tuesday, 13:00 85% 15h Tuesday, 18:00 78% 20h Tuesda...

Standby lifetime test with my FreeRunner running FSO MS5.

<pre>
00h Tuesday, 03:00 100%
10h Tuesday, 13:00 85%
15h Tuesday, 18:00 78%
20h Tuesday, 23:00 71%
25h Wednesday, 04:00 64%
34h Wednesday, 13:00 51%
39h Wednesday, 18:00 44%
Thursday, 00:00
</pre>

Toolchain

2009-02-11T22:27:52Z

Mickey: /* Introduction */

{{Languages|Toolchain}}

= Introduction =

A toolchain is a set of tools that allows you to compile code. For Openmoko, we have to differentiate between the following use-cases:

;(a) Developing a single application (or a kernel or a bootloader)
:For this, you should use a prebuilt toolchain from the Openmoko project. On this page you can find a recipe to get started with this toolchain leading you through a series of steps to compile a project and run it on your target device. (You might have heard about ''OpenEmbedded'', however as an application programmer, you should '''not''' be using OpenEmbedded.)
;(b) System Integration and customizing a distribution
:For this task, you should use [[OpenEmbedded]] which builds its own cross compiler during the bootstrapping/build process. System Integration and customizing a distribution is out of scope of this page.

=Basic toolchain usage=

==Prerequisites==

You should be reasonably familiar with Linux and its command line tools, have an x86-compatible computer with at least 1G of free disk space. You should have experience with compiling programs from source using your local compiler. The remainder of this document will also assume you have write access in your home directory (~) and <tt>/usr/local/</tt> (becoming root if needed). If any of this is not the case, please call your local administrator for help.

Last but not least you should have a working setup that allows you to compile native software packages using the autotools build system (the triade of '''./configure, make, make install''').

A (partial) list of required packages -- please append as necessary:

* For most Linux version you might only need to install the packages
** autoconf, automake
** binutils, gcc, gcc-c++
** libtool
** ccache
** intltool

* For Ubuntu 8.04 ( Previous versions don't support libmokoui2 ) the following is required:
sudo apt-get install gcc g++ autoconf automake binutils libtool libglib2.0-dev \
ccache libxrender-dev intltool libmokoui2-dev libgconf2-dev mtools fakeroot alien check

* For Ubuntu 8.10 the following is additionally required, install also those above:
sudo apt-get install uboot-mkimage

* For Fedora-Core the following is required, while logged in as <tt>root</tt>:
yum install gcc gcc-c++ autoconf automake binutils libtool glib2-devel \
ccache libXrender-devel intltool GConf2-devel mtools gettext-devel
Fedora-Core does not appear to have <tt>libmokoui2</tt> available.

* For Debian (Sid) do (as root):
apt-get install build-essential ccache autoconf automake autotools-dev libtool \
gettext intltool curl uboot-mkimage mtools fakeroot alien check libglib2.0-dev \
libxrender-dev libgconf2-dev

==Downloading and installing==

{{Note|If you wish to improve an existing Openmoko application and you are running Debian or Ubuntu i386 (i.e. you can install a .deb), you may wish to skip the below and instead use:
[http://andreasdalsgaard.blogspot.com/2008/07/openmoko-development-in-5-minutes.html Openmoko application development in 5 minutes] by Andreas Dalsgaard. (based on the 2007.2 stack)}}

The prebuilt toolchain can be downloaded from [http://downloads.openmoko.org/developer/toolchains downloads.openmoko.org]:

* Creating a destination directory can be anywhere, but for example:

mkdir ~/sources
cd ~/sources

* Depending on your CPU type (x86_64 or i686) download the proper package:

wget http://downloads.openmoko.org/developer/toolchains/openmoko-x86_64-arm-linux-gnueabi-toolchain.tar.bz2
or
wget http://downloads.openmoko.org/developer/toolchains/openmoko-i686-arm-linux-gnueabi-toolchain.tar.bz2

Next, you want to extract it on your filesystem. This toolchain is ''not'' relocatable, it needs to be installed into <tt>/usr/local/openmoko/</tt>.
Now you have the following options:

* Extract it directly as root, so use command "su" first (or prefix the tar command with "sudo" when you are using Debian/Ubuntu):

cd /
tar -xjvf ~/sources/openmoko-XYZ-arm-linux-gnueabi-toolchain.tar.bz2

* On Debian-based systems (e.g. Ubuntu), you can use alien(+fakeroot) to create an easy-to-uninstall package from this .tar.bz2:

bunzip2 openmoko-*-arm-linux-gnueabi-toolchain.tar.bz2
gzip openmoko-*-arm-linux-gnueabi-toolchain.tar
fakeroot alien -d openmoko-*-arm-linux-gnueabi-toolchain.tar.gz
sudo dpkg -i openmoko_*-arm-linux-gnueabi-toolchain*.deb

* The prebuilt toolchain is for x86_64 or i686. If you wanted, you could build it on your own with OE, using [[BitBake]]:

bitbake meta-toolchain-openmoko

Finally, everytime you want to use this toolchain, you need to alter some environment variables, so that your tools will be found. The toolchain provides a script to do that, so the only thing you need to do is to [http://learnlinux.tsf.org.za/courses/build/shell-scripting/ch10s02.html source] it.
Note that if you are not using a "sh" or "bash" shell (check with "echo $SHELL") that you need
to start "sh" or "bash" first.

. /usr/local/openmoko/arm/setup-env

* At least, you should add /usr/local/openmoko/arm/bin to your $PATH variable, otherwise the next steps won't work (om-conf and make).
export PATH=$PATH:/usr/local/openmoko/arm/bin
Note: This is will only last for your current session. Add it to your shell startup scripts to make it permenant (~/.bashrc for instance).

==Installing New Libraries==

Openmoko toolchain didn't include many libraries in default. However, it can download and install library what has already existed in Openmoko repository. (It refer to [http://downloads.openmoko.org/repository/testing/ Testing Repository] by default.)

*You need to alter some environment variables before you download libraries.
. /usr/local/openmoko/arm/environment-setup

*First, update the opkg database (Notice, you should use alias '''opkg-target''' but not '''opkg'''. If you get an "Could not obtain administrative lock" error, try to become root with "sudo su" and don't forget to rerun the scripts to set your environment variables if necessary.)
opkg-target update

*Second, select a package what you want. Let's use edje as an example. If you want develop an project which use edje of Enlightenment, you can use '''opkg-target list''' to print out how many packages you can have. Of course, command '''grep''' will help you a lot.(Remember, you should install -dev package but not only libedje.)
opkg-target list |grep edje-dev

*Third, install it
opkg-target install libedje-dev
*Fourth, have a cup of coffee and wait.

==Building a sample project==

To build the sample project you need to install libmokoui2-dev and gconf-dbus-dev in your opkg environment. Setup your environment like described there [http://wiki.openmoko.org/wiki/Toolchain#Installing_New_Libraries]. Now install the libarys with the following command:
opkg-target install libmokoui2-dev gconf-dbus-dev

In a chosen destination directory (in this example ~/):

* copy the downloaded sample application source:

cp -r /usr/local/openmoko/source/openmoko-sample2 ~/

* Remember to set the proper environment variables (again with "sh" or "bash") for openmoko:

. /usr/local/openmoko/arm/setup-env

* I came to the conclusion that more has to be done before the next step.

opkg-target update
opkg-target install libedje-dev
opkg-target install packagekit-dev
opkg-target install edbus-dev
opkg-target install libetk-dev
opkg-target install libts-dev

* One can chown -R <your-name>.<your-name> /usr/local/openmoko/arm, and
everything should work under the non-root account. Here is a useful link if you have problems with the command below ( https://kerneltrap.org/mailarchive/openmoko-devel/2008/9/17/3318834 )

* You need to create a build configuration for this application. This also checks if all needed libraries, tools, etc.. is available on your system. If this fails see the notes about the needed packages in the section "Prerequisites" mentioned earlier.

om-conf openmoko-sample2

* Optionally now you can modify the source code in openmoko-sample2/src. Before the next step, go into the sample directory.

cd openmoko-sample2

* If you are using an older version of the toolchain, you may have to create the makefile by running "./autogen.sh". Otherwise, to build the application from the source code just type:

make

* If there are errors (i.e. "You need to install gnome-common from the GNOME CVS") deal with them. Also see "Troubleshooting" section at the end of this page for known issues.

If you want to install this project on host for staging usage later, a shared library, for example, you can do the following to install it into a given configured prefix.
om-conf --prefix=/usr/local/openmoko openmoko-sample2
cd openmoko-sample2
make install

==How to create your own project from the sample project==

In order to build your own project by using openmoko-sample2 files, some changes are needed:

* copy the downloaded sample application source

cp -r /usr/local/openmoko/source/openmoko-sample2 ~/

* rename the folder with the name of your project (in this example your-project-name) and delete old sample files

mv openmoko-sample2 your-project-name
cd your-project-name
cd src
rm *.c

* copy your sources (in this example your-sources) into src/

cp your-sources .
cd ..

* now in the main folder modify autogen.sh by updating the following lines

PKG_NAME="your-project-name"

* modify configure.ac by updating the following lines ('main.c' should be the main file in your project)

AC_INIT(your-project-name, 0.0.1, http://www.openmoko.org/)
AC_CONFIG_SRCDIR(src/main.c)

* go into data/ folder and rename these files with the name of your project

cd data
mv openmoko-sample.png your-project-name.png
mv openmoko-sample.desktop your-project-name.desktop

* modify Makefile.am inside data/ by updating the following lines

dist_desktop_DATA = your-project-name.desktop
dist_appicon_DATA = your-project-name.png

* modify Makefile.in inside data/ by updating the following lines

dist_desktop_DATA = your-project-name.desktop
dist_appicon_DATA = your-project-name.png

* modify your-project-name.desktop by updating the following lines

Name=your-project-name
Encoding=UTF-8
Version=0.0.1
Type=Application
Exec=your-project-name

* and by adding the following line

Icon=your-project-name

* move into src/ folder

cd ..
cd src

* modify Makefile.am by updating the following lines

bin_PROGRAMS = your-project-name
your_project_name_SOURCES = \
main.c
your_project_name_LDADD = @DEPENDENCIES_LIBS@

* be sure to put instead of main.c all your .c and .h files and modify all the '-' characters with '_' in the variable names

==Packaging your application==

We have included a script to make an ipkg out of your application. Note that this is not needed to test your application on the Neo (for that you can just scp the resulting binary and data over), however it's very handy if you want to distribute your application to others.

om-make-ipkg openmoko-sample2

Now you got openmoko-sample2_0.1_armv4t.ipk , you can `scp' it to your
Neo and install it:

scp openmoko-sample2_0.1_armv4t.ipk root@192.168.0.202:
ssh root@192.168.0.202 opkg install openmoko-sample2_0.1_armv4t.ipk

Note that while you can redistribute the generated ipkg, be aware that this is a bare-bones ipk that contains no further information, i.e. you will lack library dependencies. See below how to fix this.

You can also supply the version number, a description, and an author / contacts string in a control file:

om-make-ipkg myapp myapp_control

A template of myapp_control:

Package: $appname
Version: 0.1
Description: package built by openmoko toolchain
Section: openmoko/applications
Priority: optional
Maintainer: $USER
Architecture: armv4t
Homepage: http://www.openmoko.org/
Depends:
Source: ${SRC}

==Where to go from here==

Using the external toolchain is an easy way to build applications for your Neo. If you are familiar with this procedure, you might also want to look into
* Using [[Qemu]] to test your applications in an emulated environment
** Ubuntu users might prefer to look at [[Automatic_emulation_in_Ubuntu]]
* Using [[Host-based_development_with_Xoo_and_Xephyr|host-based development]] to improve your efficiency
* Using [[OpenEmbedded]] to customize your Openmoko distribution image

=Advanced topics=
==Building Openmoko Kernel from git repo using Toolchain==

You may build the newest 2.6.28 kernel with these commands:

git clone git://git.openmoko.org/git/kernel.git linux-2.6
cd linux-2.6
git checkout -b mystable origin/andy-tracking
mkdir GTA02
cp arch/arm/configs/gta02-moredrivers-defconfig GTA02/.config
./build GTA02 dummy

The ''dummy'' option is required for the modules to be nicely packaged into a .tar.gz package that can be extracted on the target, in addition to flashing/installing the kernel. The "dummy" just means "some parameter given", for which there is a check in the code eventually for some reason...

You may need to edit the ./build script for the toolchain directory.

Read more information about the different branches of Openmoko's Linux kernel at: http://git.openmoko.org/?p=kernel.git;a=summary

=== Old troubleshooting information ===

If it fails with error message "arm-angstrom-linux-gnueabi-ld: unrecognized option '-Wl,-rpath-link,/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/lib'" until /usr/local/openmoko/arm/setup-env is modified. LDFLAGS should be changed from:

export LDFLAGS="-L${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-rpath-link,${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-O1"

to:

export LDFLAGS="-L${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -rpath-link ${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -O1"

I also had to change the 'build' script to hardcode the path to the compiler.

==Using toolchain provided libraries==
Add the necessary libraries to the _LDADD field in src/Makefile.am, for example:
openmoko_sample2_LDADD = @DEPENDENCIES_LIBS@ -lmokogsmd2

make sure to run om-conf again after this.

==Installing additional libraries into the toolchain==

Sooner or later you will want to compile an application that has dependencies which can't be fulfilled by the precompiled toolchain, e.g. some obscure libraries.

In that case, feel free to request the inclusion of additional libraries into the next release of the Openmoko toolchain. Until then, here is how you enhance your already installed toolchain. Say, we want to add the library called liburiparse:

cd ~/source
wget http://downloads.sourceforge.net/uriparser/uriparser-0.6.0.tar.bz2
tar xjf uriparser-0.6.0.tar.bz2
cd uriparser-0.6.0
./configure --host=arm-angstrom-linux-gnueabi \
--prefix=/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr
make
make install

That's it.

==Getting your application packaged by OE==

If you have written a cool application which you want to share with others, the best way to do that is to

# upload your application source code to a public location
# submit a [[BitBake]] recipe to [[OpenEmbedded]], preferably via the [http://bugzilla.openembedded.org OpenEmbedded bugtracker].

See also [[Customizing the Openmoko Distribution]].

==Troubleshooting==

* Some Versions of the Toolchain have corrupt .la files. If you compile an application using the Toolchain and you receive a '/space/fic/openmoko-daily/neo1973/work/armv4t-angstrom-linux-gnueabi/pango-1.18.3-r0/pango-1.18.3/pango/libpangoft2-1.0.la' error, you are affected. To fix that you should go to your "/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/lib" directory and open the affected .la files and change "/space/fic..." to "/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/lib". You have to fix more than one .la file. For the pango error you have to change "libpangocairo-1.0.la", but there are more corrupt .la files.

Attached is a beta fix for the .la problem. Untar the .tar.bz2 as root, and execute the following bash script as root:

#!/bin/sh
DIR=/usr/local/openmoko/arm
for la in `find $DIR -iname \*.la`; do
dependency_libs=
. $la
for lib in $dependency_libs ; do
delib=`echo $lib | grep -E .la$`
if [ -z $delib ] ; then
echo -n
elif [ -f $delib ]; then
echo -n
else
basedelib=`basename $delib`
replacedelibs=`find $DIR -iname $basedelib`
found=0
for replacedelib in $replacedelibs ; do
if [ $replacedelib == $delib ]; then
found=1
fi
done
if [ $found -gt 0 ] ; then
echo -n
else
sed_delib=`echo $delib | sed 's/\//\\\\\//g'`
sed_replacedelib=`echo $replacedelib | sed 's/\//\\\\\//g'`
# A bit slow, we could chain expressions for speed. :)
cp $la $la.old
cat $la | sed "s/$sed_delib/$sed_replacedelib/g" > $la.new
mv $la.new $la
rm $la.old
fi
fi
done
done

* If you can't get the toolchain working in your distro (for example if you keep bumping into strange autotools issues), you can set up the toolchain inside a Debian chroot, which should provide reasonably standard environment. There's a guide for it: http://linux.fjfi.cvut.cz/~zub/debian-chroot-toolchain.txt
* If you get something similar:
../libtool: X--tag=CC: command not found

under Ubuntu 8.10. Try do this:

sudo apt-get remove libtool

wget http://ftp.sjtu.edu.cn/ubuntu/pool/main/libt/libtool/libtool_1.5.26-1ubuntu1_i386.deb
or
wget http://ftp.sjtu.edu.cn/ubuntu/pool/main/libt/libtool/libtool_1.5.26-1ubuntu1_amd64.deb

sudo dpkg -i libtool_1.5.26-1ubuntu1_i386.deb

The original message [http://lists.openmoko.org/pipermail/devel/2008-December/003530.html here]

* Please use the [http://lists.openmoko.org/mailman/listinfo/openmoko-devel Openmoko-Devel] mailing list.

[[Category:Application Developer]]

[[Category:Application Developer]]

OpenmokoFramework/Status Update 6

2009-02-11T13:08:12Z

Mickey: /* What's new since Milestone IV */

<div style="text-align: center; font-weight: bold; font-size: x-large; margin-bottom:1em">Openmoko Framework Team Status Report 2009.2.2</div>

Hi guys! This is the sixth Openmoko Framework Team Status update, featuring our fifth milestone release and more.

For the general motivation, the goals, and the way we are doing our work, please see [[OpenmokoFramework]].

{{FSO}}

== People & Organization ==

No changes here. Current team still consists of Mickey, Jan, Daniel, and Stefan.

== DBus APIs ==

All the public DBus API are documented on the official [http://docs.freesmartphone.org freesmartphone.org API reference] site. XML-API files for generating language bindings are available from the [http://git.freesmartphone.org/?p=specs.git;a=tree;f=xml git tree].

* The GSM API (org.freesmartphone.GSM.*) has received minor updates and is now considered version 0.9. One notable addition is [http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.GSM.Monitor.html org.freesmartphone.GSM.Monitor], which is an interface for GSM monitoring, i.e. gathering diagnostic information over the serving cell and the neighbour cells.

* The Device API (org.freesmartphone.Device.*) has received minor updates and is now considered 0.8. One notably addition is [http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Device.Audio.html#PlaySound org.freesmartphone.Device.Audio.PlaySound] which gained parameters for looping and length.

* The Usage API got the new signal [http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Usage.html;hb=HEAD#SystemAction org.freesmartphone.Usage.SystemAction] which is sent on suspend, resume, shutdown, etc.

* org.freesmartphone.Objects.ListObjectsByInterface has been generalized, it gained an additional bus name parameter and is now called org.freesmartphone.DBus.ListObjectsByInterface. It's now useful also outside FSO.

* org.freesmartphone.Network has been added with the call [http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Network.html;hb=HEAD#StartConnectionSharingWithInterface org.freesmartphone.StartConnectionSharingWithInterface]. NOTE: This will not be a full fledged networking interface, but rather a high level API complementing org.moblin.connman.

* The opim API has reached this milestone, although it's still too much in flux to document it. Instead, please give it a try and join our discussions at the smartphones-standards list.

* [http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Time.Alarm.html;hb=HEAD org.freesmartphone.Time.Alarm] has made its debut as an interface for registering / clearing wake up alarms.

== Implementations ==

'''Freesmartphone.org Framework Image -- 'Calling All Stations' (Milestone V)'''

This is the fifth milestone release of the framework and the diagnostic application 'Zhone'. While we announced that we are going to phase Zhone out as phone application, it found new life as a diagnostic application, i.e. for GPS and GSM monitoring. There might be more to come, depending on our spare time...

Framework milestones currently ship in three forms:

# fso-console-image: An FSO-compliant image featuring no user interface manager.
# fso-illume-image: An FSO-compliant image featuring the X-Window system with the Enlightenment-based Illume window manager.
# fso-image: An FSO-compliant image featuring the X-Window system with the Enlightenment-based Illume and additional applications.

===Purpose===

A flashable image that implements the freesmartphone.org APIs, serving as the basis for mobile application development.

===Thanks===

Thanks to all our contributors, especially the testers and the people who build stuff on top of the freesmartphone.org APIs. Thanks, guys: You Rock!

=== What's new since Milestone IV ===

'''Note: These are only the highlights. See the [http://git.freesmartphone.org gitweb] commit logs for the gory details...'''

* General:
** We now register one dbus connection per subsystem to prevent objects appearing on all bus names. If you previously only used the bus name <tt>org.freesmartphone.frameworkd</tt>, you have to adjust your code.

* ogsmd
** TI-Calypso specific tweaks, such as DSP handling, and monitoring.
** Additional device support for the
*** Freescale Neptune,
*** the Cinterion mc75[i],
*** and the Qualcomm MSM,
*** Ericsson F3507g modem,
*** Option UMTS cards.
** Backported the state-based call handling from TI Calypso and Freescale Neptune to the generic module.
** Completely revamped ppp handling to feature more stable connection setup and teardown and better handover to pppd.
** Added a database with mobile network providers and additional country-information.
** Implemented (yet officially undocumented) org.freesmartphone.GSM.Phone.[Start|Stop]AutoRegister() and its signal org.freesmartphone.GSM.Phone.ServiceStatus() as a convenient way to ensure that ogsmd always tries to unlock the SIM and register with a provider, if necessary. (Corresponding functionality for Gprs is under discussion).

* ogpsd
** Add support for debugging via UDP

* odeviced
** Misc. device-specific tweaks for Openmoko kernels and devices.
** Added two new resources: 'CPU' and 'Display': Requesting the CPU resource will prevent the idle notifier from falling into the 'suspend' state, requesting the Display resource will prevent the idle notifier from falling into the 'idle_dim' (and following) state(s). With these two resource, it now takes only one additional rule to prevent the system from suspending while on a call or a musicplayer is playing.
** WiFi is now really turned off/on. This improves power consumption a lot. Remember to use org.freesmartphone.Usage before talking to WiFi.

* oeventsd
** Fixed a major bug in the RingToneAction. This (and removing a race in the RingToneAction) fixes problems with neverending vibration and audio ringtone on short calls.

* ousaged
** Improved resource handling, resources are properly handled on shutdown and bootup.
** Implemented the new semantics for org.freesmartphone.Usage.Suspend() and the new system actions.
** Check resume reason and launch emergency shutdown, if we woke up due to low battery. NOTE: This is only supported on Openmoko devices now. As there is no standard infrastructure for that in the kernel, we have to deal with device-specific solutions in lowlevel.py

* opimd
** Misc. fixes to make it work with the current state of the framework implementation.

* onetworkd
** Simple connection sharing now works.

* otimed
** Add simple automatic timesync to NTP and GPS.
** Add configuration options for time and zone sources. Set to "NONE" to disable these features.

* zhone
** Add gettext support
** Add russian translation
** Send and receive USSD messages
** Show error/warning when SIM is full
** Simple GSM cell monitor
** Revamped GPS monitor
** Display current timezone
** Try unlocking the screen on incoming calls
** Show the name from the phonebook during call

===Installation===

# Grab a uImage and a .jffs2 for your device from freesmartphone.org's download [http://downloads.freesmartphone.org/fso-stable/milestone5/ section].
# Flash it to your [[Flashing the Neo 1973|Neo 1973 (om-gta01)]] or [[Flashing the Neo Freerunner|Neo FreeRunner (om-gta02)]] with [[Dfu-util| dfu-util]].
# Boot and wait until the Zhone main window appears.
# ''If the [[Zhone]] main window does not appear on first boot or stays with "connecting to dbus..." longer than 1 minute, then please reboot. The base system still has some problems with dbus starting for the first time''
# Read the [[FSO UI Tutorial]] and have fun. Note though that this has not been updated yet for milestone 5 (which looks a bit differently and has more features).

===Feedback===

* Please provide feedback and comments for the dbus APIs. This is your chance to take an active role into shaping the application programming interface for all your forthcoming cool applications.

* Focus on using the services. Zhone is a diagnostic utility and not a phone application.

* The best way to interact with the framework is by exploring the dbus APIs. For this, you can use these two tools, which are already installed:
** [[OpenmokoFramework/mdbus|mdbus]] -- a dbus introspection and interaction utility,
** [[OpenmokoFramework/cli|cli-framework]] -- a python dbus command line interface.

* Before reporting bugs against the framework, please try with cli-framework to see whether it's really a problem of the framework or rather the UI (which gets much less attention from us).

* If you want to interact with the GSM modem, while the frameworkd is running, you can use [[OpenmokoFramework/mickeyterm|mickeyterm]] -- a MUXer-aware minimal terminal emulator.

===Best way to hand us debug logs===
# log in via ssh
# killall python
# edit /etc/frameworkd.conf and add to the frameworkd section:
## log_level = DEBUG
## log_to = file
## log_destination = /somewhere/where/you/have/space (preferably SD or NFS, etc.)
# Read our [http://git.freesmartphone.org/?p=framework.git;a=blob;f=conf/example/frameworkd.conf documented frameworkd.conf] configuration file to learn about the other options.
# relaunch frameworkd (/etc/init.d/frameworkd stop; /etc/init.d/frameworkd start)
# log in via ssh (yes, again)
# export DISPLAY=:0.0
# run your favourite client (SHR, zhone, cli-framework, ...)

Attach the logs to the tickets, please.

==What's next==

* More work on opimd.
* Connman integration.
* Bluetooth4 Networking.
* Unit Tests
* High Level Documentation
* More Device Support (GTA03, HTC)

==The Team==

Mickey, Jan, Daniel, Stefan.

[[Category:Community Update]]
[[Category:Framework]]

OpenmokoFramework/Status Update 6

2009-02-02T20:28:45Z

Mickey:

<div style="text-align: center; font-weight: bold; font-size: x-large; margin-bottom:1em">Openmoko Framework Team Status Report 2009.2.2</div>

Hi guys! This is the sixth Openmoko Framework Team Status update, featuring our fifth milestone release and more.

For the general motivation, the goals, and the way we are doing our work, please see [[OpenmokoFramework]].

{{FSO}}

== People & Organization ==

No changes here. Current team still consists of Mickey, Jan, Daniel, and Stefan.

== DBus APIs ==

All the public DBus API are documented on the official [http://docs.freesmartphone.org freesmartphone.org API reference] site. XML-API files for generating language bindings are available from the [http://git.freesmartphone.org/?p=specs.git;a=tree;f=xml git tree].

* The GSM API (org.freesmartphone.GSM.*) has received minor updates and is now considered version 0.9. One notable addition is [http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.GSM.Monitor.html org.freesmartphone.GSM.Monitor], which is an interface for GSM monitoring, i.e. gathering diagnostic information over the serving cell and the neighbour cells.

* The Device API (org.freesmartphone.Device.*) has received minor updates and is now considered 0.8. One notably addition is [http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Device.Audio.html#PlaySound org.freesmartphone.Device.Audio.PlaySound] which gained parameters for looping and length.

* The Usage API got the new signal [http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Usage.html;hb=HEAD#SystemAction org.freesmartphone.Usage.SystemAction] which is sent on suspend, resume, shutdown, etc.

* org.freesmartphone.Objects.ListObjectsByInterface has been generalized, it gained an additional bus name parameter and is now called org.freesmartphone.DBus.ListObjectsByInterface. It's now useful also outside FSO.

* org.freesmartphone.Network has been added with the call [http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Network.html;hb=HEAD#StartConnectionSharingWithInterface org.freesmartphone.StartConnectionSharingWithInterface]. NOTE: This will not be a full fledged networking interface, but rather a high level API complementing org.moblin.connman.

* The opim API has reached this milestone, although it's still too much in flux to document it. Instead, please give it a try and join our discussions at the smartphones-standards list.

* [http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Time.Alarm.html;hb=HEAD org.freesmartphone.Time.Alarm] has made its debut as an interface for registering / clearing wake up alarms.

== Implementations ==

'''Freesmartphone.org Framework Image -- '' (Milestone V)'''

This is the fifth milestone release of the framework and the diagnostic application 'Zhone'. While we announced that we are going to phase Zhone out as phone application, it found new live as a diagnostic application, i.e. for GPS and GSM monitoring. There might be more to come, depending on our spare time...

Framework milestones currently ship in three forms:

# fso-console-image: An FSO-compliant image featuring no user interface manager.
# fso-illume-image: An FSO-compliant image featuring the X-Window system with the Enlightenment-based Illume window manager.
# fso-image: An FSO-compliant image featuring the X-Window system with the Enlightenment-based Illume and additional applications.

===Purpose===

A flashable image that implements the freesmartphone.org APIs, serving as the basis for mobile application development.

===Thanks===

Thanks to all our contributors, especially the testers and the people who build stuff on top of the freesmartphone.org APIs. Thanks, guys: You Rock!

=== What's new since Milestone IV ===

'''Note: These are only the highlights. See the [http://git.freesmartphone.org gitweb] commit logs for the gory details...'''

* General:
** We now register one dbus connection per subsystem to prevent objects appearing on all bus names. If you previously only used the bus name <tt>org.freesmartphone.frameworkd</tt>, you have to adjust your code.

* ogsmd
** TI-Calypso specific tweaks, such as DSP handling, and monitoring.
** Additional device support for the
*** Freescale Neptune,
*** the Cinterion mc75[i],
*** and the Qualcomm MSM,
*** Ericsson F3507g modem,
*** Option UMTS cards.
** Backported the state-based call handling from TI Calypso and Freescale Neptune to the generic module.
** Completely revamped ppp handling to feature more stable connection setup and teardown and better handover to pppd.
** Added a database with mobile network providers and additional country-information.
** Implemented (yet officially undocumented) org.freesmartphone.GSM.Phone.[Start|Stop]AutoRegister() and its signal org.freesmartphone.GSM.Phone.ServiceStatus() as a convenient way to ensure that ogsmd always tries to unlock the SIM and register with a provider, if necessary. (Corresponding functionality for Gprs is under discussion).

* ogpsd
** Add support for debugging via UDP

* odeviced
** Misc. device-specific tweaks for Openmoko kernels and devices.
** Added two new resources: 'CPU' and 'Display': Requesting the CPU resource will prevent the idle notifier from falling into the 'suspend' state, requesting the Display resource will prevent the idle notifier from falling into the 'idle_dim' (and following) state(s). With these two resource, it now takes only one additional rule to prevent the system from suspending while on a call or a musicplayer is playing.

* oeventsd
** Fixed a major bug in the RingToneAction. This (and removing a race in the RingToneAction) fixes problems with neverending vibration and audio ringtone on short calls.

* ousaged
** Improved resource handling, resources are properly handled on shutdown and bootup.
** Implemented the new semantics for org.freesmartphone.Usage.Suspend() and the new system actions.
** Check resume reason and launch emergency shutdown, if we woke up due to low battery. NOTE: This is only supported on Openmoko devices now. As there is no standard infrastructure for that in the kernel, we have to deal with device-specific solutions in lowlevel.py

* opimd
** Misc. fixes to make it work with the current state of the framework implementation.

* onetworkd
** Simple connection sharing now works.

* otimed
** Add simple automatic timesync to NTP and GPS.
** Add configuration options for time and zone sources. Set to "NONE" to disable these features.

* zhone
** Add gettext support
** Add russian translation
** Send and receive USSD messages
** Show error/warning when SIM is full
** Simple GSM cell monitor
** Revamped GPS monitor
** Display current timezone
** Try unlocking the screen on incoming calls
** Show the name from the phonebook during call

===Installation===

# Grab a uImage and a .jffs2 for your device from freesmartphone.org's download [http://downloads.freesmartphone.org/fso-stable/milestone5/ section].
# Flash it to your [[Flashing the Neo 1973|Neo 1973 (om-gta01)]] or [[Flashing the Neo Freerunner|Neo FreeRunner (om-gta02)]] with [[Dfu-util| dfu-util]].
# Boot and wait until the Zhone main window appears.
# ''If the [[Zhone]] main window does not appear on first boot or stays with "connecting to dbus..." longer than 1 minute, then please reboot. The base system still has some problems with dbus starting for the first time''
# Read the [[FSO UI Tutorial]] and have fun. Note though that this has not been updated yet for milestone 5 (which looks a bit differently and has more features).

===Feedback===

* Please provide feedback and comments for the dbus APIs. This is your chance to take an active role into shaping the application programming interface for all your forthcoming cool applications.

* Focus on using the services. Zhone is a diagnostic utility and not a phone application.

* The best way to interact with the framework is by exploring the dbus APIs. For this, you can use these two tools, which are already installed:
** [[OpenmokoFramework/mdbus|mdbus]] -- a dbus introspection and interaction utility,
** [[OpenmokoFramework/cli|cli-framework]] -- a python dbus command line interface.

* Before reporting bugs against the framework, please try with cli-framework to see whether it's really a problem of the framework or rather the UI (which gets much less attention from us).

* If you want to interact with the GSM modem, while the frameworkd is running, you can use [[OpenmokoFramework/mickeyterm|mickeyterm]] -- a MUXer-aware minimal terminal emulator.

===Best way to hand us debug logs===
# log in via ssh
# killall python
# edit /etc/frameworkd.conf and add to the frameworkd section:
## log_level = DEBUG
## log_to = file
## log_destination = /somewhere/where/you/have/space (preferably SD or NFS, etc.)
# Read our [http://git.freesmartphone.org/?p=framework.git;a=blob;f=conf/example/frameworkd.conf documented frameworkd.conf] configuration file to learn about the other options.
# relaunch frameworkd (/etc/init.d/frameworkd stop; /etc/init.d/frameworkd start)
# log in via ssh (yes, again)
# export DISPLAY=:0.0
# run your favourite client (SHR, zhone, cli-framework, ...)

Attach the logs to the tickets, please.

==What's next==

* More work on opimd.
* Connman integration.
* Bluetooth4 Networking.
* Unit Tests
* High Level Documentation
* More Device Support (GTA03, HTC)

==The Team==

Mickey, Jan, Daniel, Stefan.

[[Category:Community Update]]
[[Category:Framework]]