http://wiki.openmoko.org/api.php?action=feedcontributions&user=DanielWillmann&feedformat=atomOpenmoko - User contributions [en]2024-03-29T11:42:56ZUser contributionsMediaWiki 1.19.24http://wiki.openmoko.org/wiki/BuzzFixPartyBuzzFixParty2009-04-23T22:45:40Z<p>DanielWillmann: /* Braunschweig */</p>
<hr />
<div>= Here you can find information about upcoming buzz-fix parties =<br />
<br />
Just as a nice gesture for those putting in so much effort organising these parties:<br />
When you attend a party or send your device via post, you could bring along or include<br />
in the package some local delicacies like sweets or cookies or a small souvenir.<br />
(This part is not written by one of the organisers.)<br />
<br />
== Barcelona ==<br />
<br />
[[Image:Buzzfixpartibarcelonablog400.png|200px|thumb|Banner Buzz Fix Party Barcelona]]<br />
* '''When:''' April 18st from 10:00 to 13:00 and 16:00 to 18:00<br />
* '''Where:'''[http://www.bocanord.org/boca-nord/on-som/ LinuxLab Bocanord] Barcelona<br />
* '''What:''' Tired of that buzz? We will fix the Neo for you, and we add a free battery on each fix :)<br />
* '''How:'''Visit [http://www.tuxbrain.com/shop Tuxbrain Web shop] and reserve a ticket , read instructions carefully in the ticket description<br />
* '''Why:''' There will be a lot of friendly "Openmokers" around there sharing their experiences and some beer & chips :)<br />
* '''Contact:'''You can reach us at [http://n2.nabble.com/Openmoko-Community-f1954ef1958.html Openmoko-spain mailing list] or email me directly at david@tuxbrain.com<br />
<br />
=== Attendants & Neos Expected ===<br />
Actually 15 attendants registered (two from Norway :) ) and 21 Neos for repair<br />
Finally only 10 attendants, and 9 neos fixed in place (two of them failed) remote ones(9) are will arrive today (21/04/2009) to Rafael's Lab to be fixed.<br />
<br />
=== Remote Users === <br />
We accept remote shipping from Spain, Portugal, and Andorra. Depending on how all works in this party we can extend the area worldwide on next ones(Madrid, Caceres), read ticket instructions on how to proceed<br />
<br />
=== Pictures ===<br />
[http://www.openmoko-spain.org/tiki-view_blog_post.php?blogId=1&postId=10 Full commented pictures in Spanish] <br />
{| border="1" cellpadding="10" cellspacing="0"<br />
|-<br />
|[[Image:BFP_BCN_dscn0134.jpg|200px|thumb|Boca Nord building rear the trees ]]<br />
|[[Image:BFP_BCN_dscn0135.jpg|200px|thumb|Graffiti at Boca Nord Entry ]]<br />
|[[Image:BFP_BCN_dscn0136.jpg|200px|thumb|David Samblas from Tuxbrain.com preparing some product samples at 9:50 ]]<br />
|-<br />
|[[Image:BFP_BCN_dscn0137.jpg|200px|thumb|Rafael Campos mounting his great ironing equipment]]<br />
|[[Image:BFP_BCN_dscn0139.jpg|200px|thumb|Detail of Rafael's great ironing equipment ]]<br />
|[[Image:BFP_BCN_dscn0140.jpg|200px|thumb|First Neo in the the surgery table ]]<br />
|-<br />
|[[Image:BFP_BCN_dscn0141.jpg|200px|thumb|Demonstrating our confidence in Rafael's skills :) ]]<br />
|[[Image:BFP_BCN_dscn0146.jpg|200px|thumb|Detail of a fix trough the magnifying glass ]]<br />
|[[Image:BFP_BCN_dscn0148.jpg|200px|thumb|Looking at the most exhaustive Neos Distro collection in Miquel's laptop Miquel at left, Alberto rear center, David at the laptop, Pau at right ]]<br />
|-<br />
|[[Image:BFP_BCN_dscn0149.jpg|200px|thumb|Talking about Neo, Jose from Norway back to the camara in blue jacket, Alex talking with him, Manel at the right ]]<br />
|[[Image:BFP_BCN_dscn0150.jpg|200px|thumb|Group foto from lef to right: Jose Luis,Rafael, Manel, Alberto, Jose Antonio(, Pau, Martin, Jose, Alex, and David before dinner. ]]<br />
|[[Image:BFP_BCN_dscn0151.jpg|200px|thumb|Same photo, more fun]]<br />
|-<br />
|[[Image:BFP_BCN_dscn0152.jpg|200px|thumb|A big hug to our most far away attendant Jose from Norway]]<br />
|[[Image:BFP_BCN_dscn0160.jpg|200px|thumb|Near to close the party we still having fun ]]<br />
|<br />
|}<br />
<br />
== Braunschweig ==<br />
<br />
* '''When:''' May 1st - May 3rd, start will be 09:00<br />
* '''Where:''' Student pub "Monkey Island" at Rebenring 64 in Braunschweig, Germany. The entrance is at the south-west corner of the dormitory "Affenfelsen" (see http://informationfreeway.org/?lat=52.27432513952919&lon=10.522477178117994&zoom=17&layers=B0000F000F). From Braunschweig main station you can take the lines M1, M2 or M19 and get off at "Hamburger Straße".<br />
* '''What:''' Please indicate in the list how many devices you will bring. The rework itself will take about 40 minutes. Testing device before and after (including flashing) will take a couple of minutes, but can be parallelised. The day has 24 hours. You do the math. :-)<br />
* '''How:''' Back up all your data! We will flash a testing image into the flash and there is a possibility that the Freerunner will get damaged during the process (Though I haven't broken any device yet). Exchange devices for the ones I might break will be there.<br />
* '''Why:''' There will be other Freerunner users around. Use the time to get to know each other in person, share problems, fixes, ...<br />
* '''Contact:''' For questions, etc. please contact: buzz@totalueberwachung.de<br />
<br />
=== May 1st ===<br />
* Roland (1)<br />
* Arne (2)<br />
* Christian (1)<br />
* Fabian (1)<br />
* Matthias (1)<br />
<br />
=== May 2nd ===<br />
* YourNameHere(1)<br />
<br />
=== May 3rd ===<br />
* [[User:Avanc|Sven]] (1)<br />
* Matthias, Stephan (3)<br />
* [[User:Carcinoma|Christian]] (1)<br />
* Christoph (1)<br />
* YourNameHere(1)<br />
<br />
=== Remote users ===<br />
Note: This is NOT for users who want to mail their device directly. For that please go to: http://projects.totalueberwachung.de/buzz-mailin/ <br/><br />
Users which would like someone living nearby to take their device to the fix party or would like to mail the device with money included for having it mailed back:<br />
<br />
# <strike>Christ van Willegen (1, Eindhoven, The Netherlands) [http://wiki.openmoko.org/wiki/Special:Emailuser/ChristW Contact me here]</strike> I've sent it to Daniel myself, no need to bring it to the party for me.<br />
# <strike>Pander</strike> Mailed the device by post.<br />
# Philipp (1, Rostock, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Philmax Contact me here]<br />
# Johannes (3, Graz, Austria) [http://wiki.openmoko.org/wiki/Special:Emailuser/Flojoh Contact me here]<br />
# Stefan L. (1, Rostock, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Derlehmann Contact me here]<br />
#<strike> Axel K. (1, Stuttgart, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/axel.keller Contact me here]</strike><br />
# G. Neidisch (1, Hamburg, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Gneidisch Contact me here]<br />
# Sebastian S. (1, Hitzhofen, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/M0wlwurf Contact me here]<br />
#<strike> Joachim “nomeata” Breitner (1, Karlsruhe, Germany) [http://www.joachim-breitner.de/contact Contact me here]</strike> Done by a collegue of my brother, but thanks for the option<br />
# Bastian “gforce“ Bittorf (1, Weimar, Germany) [[User:Fries43]]<br />
# Sven 'sleipnir' Rebhan (1, Offenbach, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Sleipnir Contact me here]<br />
# Vincent M. (1, Munich, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Patou Contact me here]<br />
<br />
== Caceres (Debconf09) ==<br />
<br />
* '''When:''' Probably July 25th<br />
* '''Where:'''At [http://debconf9.debconf.org Debconf09] <br />
* '''What:''' Tired of that buzz? We will fix the Neo for you, and we add a free battery on each fix :)<br />
* '''How:''' Once once is made official by Debconf organization visit [http://www.tuxbrain.com/shop Tuxbrain Web shop] and reserve a ticket , read instructions carefully in the ticket description, stay tunned<br />
* '''Why:''' There will be a lot of friendly "Openmokers" around there sharing their experiences and some beer & food :)<br />
* '''Contact:'''You can reach us at [http://n2.nabble.com/Openmoko-Community-f1954ef1958.html Openmoko-spain mailing list] or email me directly at david@tuxbrain.com<br />
<br />
=== Attendants & Neos Expected ===<br />
will see :)<br />
<br />
=== Remote Users === <br />
We accept remote shipping from Spain, Portugal, and Andorra. Depending on how all works in Barcelona party we will extend the area worldwide, once is made official by Debconf organization read ticket instructions on how to proceed<br />
<br />
== Madrid ==<br />
<br />
* '''When:''' To be defined but probably at end of May<br />
* '''Where:'''To be defined<br />
* '''What:''' Tired of that buzz? We will fix the Neo for you, and we add a free battery on each fix :)<br />
* '''How:''' Once when and where are defined visit [http://www.tuxbrain.com/shop Tuxbrain Web shop] and reserve a ticket , read instructions carefully in the ticket description, stay tunned<br />
* '''Why:''' There will be a lot of friendly "Openmokers" around there sharing their experiences and some beer & food :)<br />
* '''Contact:'''You can reach us at [http://n2.nabble.com/Openmoko-Community-f1954ef1958.html Openmoko-spain mailing list] or email me directly at david@tuxbrain.com<br />
<br />
=== Attendants & Neos Expected ===<br />
will see :)<br />
<br />
=== Remote Users === <br />
We accept remote shipping from Spain, Portugal, and Andorra. Depending on how all works in Barcelona party we will extend the area worldwide, once when and where are defined read ticket instructions on how to proceed</div>DanielWillmannhttp://wiki.openmoko.org/wiki/BuzzFixPartyBuzzFixParty2009-04-20T20:19:17Z<p>DanielWillmann: /* Braunschweig */</p>
<hr />
<div>= Here you can find information about upcoming buzz-fix parties =<br />
<br />
Just as a nice gesture for those putting in so much effort organising these parties:<br />
When you attend a party or send your device via post, you could bring along or include<br />
in the package some local delicacies like sweets or cookies or a small souvenir.<br />
(This part is not written by one of the organisers.)<br />
<br />
== Barcelona ==<br />
<br />
[[Image:Buzzfixpartibarcelonablog400.png|200px|thumb|Banner Buzz Fix Party Barcelona]]<br />
* '''When:''' April 18st from 10:00 to 13:00 and 16:00 to 18:00<br />
* '''Where:'''[http://www.bocanord.org/boca-nord/on-som/ LinuxLab Bocanord] Barcelona<br />
* '''What:''' Tired of that buzz? We will fix the Neo for you, and we add a free battery on each fix :)<br />
* '''How:'''Visit [http://www.tuxbrain.com/shop Tuxbrain Web shop] and reserve a ticket , read instructions carefully in the ticket description<br />
* '''Why:''' There will be a lot of friendly "Openmokers" around there sharing their experiences and some beer & chips :)<br />
* '''Contact:'''You can reach us at [http://n2.nabble.com/Openmoko-Community-f1954ef1958.html Openmoko-spain mailing list] or email me directly at david@tuxbrain.com<br />
<br />
=== Attendants & Neos Expected ===<br />
Actually 15 attendants registered (two from Norway :) ) and 21 Neos for repair<br />
<br />
=== Remote Users === <br />
We accept remote shipping from Spain, Portugal, and Andorra. Depending on how all works in this party we can extend the area worldwide on next ones(Madrid, Caceres), read ticket instructions on how to proceed<br />
<br />
== Braunschweig ==<br />
<br />
* '''When:''' May 1st - May 3rd, start will be 09:00<br />
* '''Where:''' Braunschweig, Germany (exact location still unknown, most likely somewhere around http://informationfreeway.org/?lat=52.27389186224494&lon=10.524687317867564&zoom=17&layers=B0000F000F)<br />
* '''What:''' Please indicate in the list how many devices you will bring. The rework itself will take about 40 minutes. Testing device before and after (including flashing) will take a couple of minutes, but can be parallelised. The day has 24 hours. You do the math. :-)<br />
* '''How:''' Back up all your data! There is a possibility that the Freerunner will get damaged during the process (I haven't broken one device yet, but the possibility exists). If I break the devices during the buzz fix they will be replaced one way or the other. There is no need to mark all your parts. Feel free to do, though.<br />
* '''Why:''' There will be other Freerunner users around. Use the time to get to know each other in person, share problems, fixes, ...<br />
* '''Contact:''' For questions, etc. please contact: buzz@totalueberwachung.de<br />
<br />
=== May 1st ===<br />
* Roland (1)<br />
* Arne (2)<br />
* Christian (1)<br />
* Fabian (1)<br />
* Matthias (1)<br />
<br />
=== May 2nd ===<br />
* YourNameHere(1)<br />
<br />
=== May 3rd ===<br />
* [[User:Avanc|Sven]] (1)<br />
* Matthias, Stephan (3)<br />
* [[User:Carcinoma|Christian]] (1)<br />
* Christoph (1)<br />
* YourNameHere(1)<br />
<br />
=== Remote users ===<br />
Note: This is NOT for users who want to mail their device directly. For that please go to: http://projects.totalueberwachung.de/buzz-mailin/ <br/><br />
Users which would like someone living nearby to take their device to the fix party or would like to mail the device with money included for having it mailed back:<br />
<br />
# <strike>Christ van Willegen (1, Eindhoven, The Netherlands) [http://wiki.openmoko.org/wiki/Special:Emailuser/ChristW Contact me here]</strike>I've sent it to Daniel myself, no need to bring it to the party for me.<br />
# Pander (1, Utrecht, The Netherlands) [http://wiki.openmoko.org/wiki/Special:Emailuser/Pander Contact me here]<br />
# Philipp (1, Rostock, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Philmax Contact me here]<br />
# Johannes (3, Graz, Austria) [http://wiki.openmoko.org/wiki/Special:Emailuser/Flojoh Contact me here]<br />
# Stefan L. (1, Rostock, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Derlehmann Contact me here]<br />
# Axel K. (1, Stuttgart, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/axel.keller Contact me here]<br />
# G. Neidisch (1, Hamburg, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Gneidisch Contact me here]<br />
# Sebastian S. (1, Hitzhofen, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/M0wlwurf Contact me here]<br />
#<strike> Joachim “nomeata” Breitner (1, Karlsruhe, Germany) [http://www.joachim-breitner.de/contact Contact me here]</strike> Done by a collegue of my brother, but thanks for the option<br />
# Bastian “gforce“ Bittorf (1, Weimar, Germany) [[User:Fries43]]<br />
# Sven 'sleipnir' Rebhan (1, Offenbach, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Sleipnir Contact me here]<br />
# Vincent M. (1, Munich, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Patou Contact me here]<br />
<br />
== Caceres (Debconf09) ==<br />
<br />
* '''When:''' Probably July 25th<br />
* '''Where:'''At [http://debconf9.debconf.org Debconf09] <br />
* '''What:''' Tired of that buzz? We will fix the Neo for you, and we add a free battery on each fix :)<br />
* '''How:''' Once once is made official by Debconf organization visit [http://www.tuxbrain.com/shop Tuxbrain Web shop] and reserve a ticket , read instructions carefully in the ticket description, stay tunned<br />
* '''Why:''' There will be a lot of friendly "Openmokers" around there sharing their experiences and some beer & food :)<br />
* '''Contact:'''You can reach us at [http://n2.nabble.com/Openmoko-Community-f1954ef1958.html Openmoko-spain mailing list] or email me directly at david@tuxbrain.com<br />
<br />
=== Attendants & Neos Expected ===<br />
will see :)<br />
<br />
=== Remote Users === <br />
We accept remote shipping from Spain, Portugal, and Andorra. Depending on how all works in Barcelona party we will extend the area worldwide, once is made official by Debconf organization read ticket instructions on how to proceed<br />
<br />
== Madrid ==<br />
<br />
* '''When:''' To be defined but probably at end of May<br />
* '''Where:'''To be defined<br />
* '''What:''' Tired of that buzz? We will fix the Neo for you, and we add a free battery on each fix :)<br />
* '''How:''' Once when and where are defined visit [http://www.tuxbrain.com/shop Tuxbrain Web shop] and reserve a ticket , read instructions carefully in the ticket description, stay tunned<br />
* '''Why:''' There will be a lot of friendly "Openmokers" around there sharing their experiences and some beer & food :)<br />
* '''Contact:'''You can reach us at [http://n2.nabble.com/Openmoko-Community-f1954ef1958.html Openmoko-spain mailing list] or email me directly at david@tuxbrain.com<br />
<br />
=== Attendants & Neos Expected ===<br />
will see :)<br />
<br />
=== Remote Users === <br />
We accept remote shipping from Spain, Portugal, and Andorra. Depending on how all works in Barcelona party we will extend the area worldwide, once when and where are defined read ticket instructions on how to proceed</div>DanielWillmannhttp://wiki.openmoko.org/wiki/BuzzFixPartyBuzzFixParty2009-04-20T13:48:05Z<p>DanielWillmann: /* Remote users */ Clarified remote users</p>
<hr />
<div>= Here you can find information about upcoming buzz-fix parties =<br />
<br />
Just as a nice gesture for those putting in so much effort organising these parties:<br />
When you attend a party or send your device via post, you could bring along or include<br />
in the package some local delicacies like sweets or cookies or a small souvenir.<br />
(This part is not written by one of the organisers.)<br />
<br />
== Barcelona ==<br />
<br />
[[Image:Buzzfixpartibarcelonablog400.png|200px|thumb|Banner Buzz Fix Party Barcelona]]<br />
* '''When:''' April 18st from 10:00 to 13:00 and 16:00 to 18:00<br />
* '''Where:'''[http://www.bocanord.org/boca-nord/on-som/ LinuxLab Bocanord] Barcelona<br />
* '''What:''' Tired of that buzz? We will fix the Neo for you, and we add a free battery on each fix :)<br />
* '''How:'''Visit [http://www.tuxbrain.com/shop Tuxbrain Web shop] and reserve a ticket , read instructions carefully in the ticket description<br />
* '''Why:''' There will be a lot of friendly "Openmokers" around there sharing their experiences and some beer & chips :)<br />
* '''Contact:'''You can reach us at [http://n2.nabble.com/Openmoko-Community-f1954ef1958.html Openmoko-spain mailing list] or email me directly at david@tuxbrain.com<br />
<br />
=== Attendants & Neos Expected ===<br />
Actually 15 attendants registered (two from Norway :) ) and 21 Neos for repair<br />
<br />
=== Remote Users === <br />
We accept remote shipping from Spain, Portugal, and Andorra. Depending on how all works in this party we can extend the area worldwide on next ones(Madrid, Caceres), read ticket instructions on how to proceed<br />
<br />
== Braunschweig ==<br />
<br />
* '''When:''' May 1st - May 3rd, start will be 09:00<br />
* '''Where:''' Braunschweig, Germany (exact location still unknown, most likely somewhere around http://informationfreeway.org/?lat=52.27389186224494&lon=10.524687317867564&zoom=17&layers=B0000F000F)<br />
* '''What:''' Please indicate in the list how many devices you will bring. The rework itself will take about 40 minutes. Testing device before and after (including flashing) will take a couple of minutes, but can be parallelised. The day has 24 hours. You do the math. :-)<br />
* '''How:''' Back up all your data! There is a possibility that the Freerunner will get damaged during the process (I haven't broken one device yet, but the possibility exists). Openmoko has promised me replacement devices for this case, but they are '''not''' here yet. So until further notice I will '''not''' guarantee that you will walk away from this with a working Freerunner. Mark all the parts (battery, main and cover) with your full name. Use labels which leave no glue residue and remove labels afterward, especially from your battery! One could use [http://en.wikipedia.org/wiki/Masking_tape painting/masking tape], especially the blue version that sticks as less as possible.<br />
* '''Why:''' There will be other Freerunner users around. Use the time to get to know each other in person, share problems, fixes, ...<br />
* '''Contact:''' For questions, etc. please contact: buzz@totalueberwachung.de<br />
<br />
=== May 1st ===<br />
* Roland (1)<br />
* Arne (2)<br />
* Christian (1)<br />
* Fabian (1)<br />
* Matthias (1)<br />
<br />
=== May 2nd ===<br />
* YourNameHere(1)<br />
<br />
=== May 3rd ===<br />
* [[User:Avanc|Sven]] (1)<br />
* Matthias, Stephan (3)<br />
* [[User:Carcinoma|Christian]] (1)<br />
* Christoph (1)<br />
* YourNameHere(1)<br />
<br />
=== Remote users ===<br />
Note: This is NOT for users who want to mail their device directly. For that please go to: http://projects.totalueberwachung.de/buzz-mailin/ <br/><br />
Users which would like someone living nearby to take their device to the fix party or would like to mail the device with money included for having it mailed back:<br />
<br />
# <strike>Christ van Willegen (1, Eindhoven, The Netherlands) [http://wiki.openmoko.org/wiki/Special:Emailuser/ChristW Contact me here]</strike>I've sent it to Daniel myself, no need to bring it to the party for me.<br />
# <strike>Johannes K. (1, Stuttgart, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Aragorn Contact me here]</strike> same here<br />
# Pander (1, Utrecht, The Netherlands) [http://wiki.openmoko.org/wiki/Special:Emailuser/Pander Contact me here]<br />
# Philipp (1, Rostock, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Philmax Contact me here]<br />
# Johannes (3, Graz, Austria) [http://wiki.openmoko.org/wiki/Special:Emailuser/Flojoh Contact me here]<br />
# Stefan L. (1, Rostock, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Derlehmann Contact me here]<br />
# Axel K. (1, Stuttgart, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/axel.keller Contact me here]<br />
# G. Neidisch (1, Hamburg, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Gneidisch Contact me here]<br />
# Sebastian S. (1, Hitzhofen, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/M0wlwurf Contact me here]<br />
#<strike> Joachim “nomeata” Breitner (1, Karlsruhe, Germany) [http://www.joachim-breitner.de/contact Contact me here]</strike> Done by a collegue of my brother, but thanks for the option<br />
# Bastian “gforce“ Bittorf (1, Weimar, Germany) [[User:Fries43]]<br />
# Sven 'sleipnir' Rebhan (1, Offenbach, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Sleipnir Contact me here]<br />
# Vincent M. (1, Munich, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Patou Contact me here]<br />
<br />
== Caceres (Debconf09) ==<br />
<br />
* '''When:''' Probably July 25th<br />
* '''Where:'''At [http://debconf9.debconf.org Debconf09] <br />
* '''What:''' Tired of that buzz? We will fix the Neo for you, and we add a free battery on each fix :)<br />
* '''How:''' Once once is made official by Debconf organization visit [http://www.tuxbrain.com/shop Tuxbrain Web shop] and reserve a ticket , read instructions carefully in the ticket description, stay tunned<br />
* '''Why:''' There will be a lot of friendly "Openmokers" around there sharing their experiences and some beer & food :)<br />
* '''Contact:'''You can reach us at [http://n2.nabble.com/Openmoko-Community-f1954ef1958.html Openmoko-spain mailing list] or email me directly at david@tuxbrain.com<br />
<br />
=== Attendants & Neos Expected ===<br />
will see :)<br />
<br />
=== Remote Users === <br />
We accept remote shipping from Spain, Portugal, and Andorra. Depending on how all works in Barcelona party we will extend the area worldwide, once is made official by Debconf organization read ticket instructions on how to proceed<br />
<br />
== Madrid ==<br />
<br />
* '''When:''' To be defined but probably at end of May<br />
* '''Where:'''To be defined<br />
* '''What:''' Tired of that buzz? We will fix the Neo for you, and we add a free battery on each fix :)<br />
* '''How:''' Once when and where are defined visit [http://www.tuxbrain.com/shop Tuxbrain Web shop] and reserve a ticket , read instructions carefully in the ticket description, stay tunned<br />
* '''Why:''' There will be a lot of friendly "Openmokers" around there sharing their experiences and some beer & food :)<br />
* '''Contact:'''You can reach us at [http://n2.nabble.com/Openmoko-Community-f1954ef1958.html Openmoko-spain mailing list] or email me directly at david@tuxbrain.com<br />
<br />
=== Attendants & Neos Expected ===<br />
will see :)<br />
<br />
=== Remote Users === <br />
We accept remote shipping from Spain, Portugal, and Andorra. Depending on how all works in Barcelona party we will extend the area worldwide, once when and where are defined read ticket instructions on how to proceed</div>DanielWillmannhttp://wiki.openmoko.org/wiki/BuzzFixPartyBuzzFixParty2009-04-11T11:52:07Z<p>DanielWillmann: /* Braunschweig */</p>
<hr />
<div>= Here you can find information about upcoming buzz-fix parties =<br />
<br />
== Braunschweig ==<br />
<br />
* '''When:''' May 1st - May 3rd, start will be 09:00<br />
* '''Where:''' Braunschweig, Germany (exact location still unknown, most likely somewhere around http://informationfreeway.org/?lat=52.27389186224494&lon=10.524687317867564&zoom=17&layers=B0000F000F)<br />
* '''What:''' Please indicate in the list how many devices you will bring. The rework itself will take about 40 minutes. Testing device before and after (including flashing) will take a couple of minutes, but can be parallelised. The day has 24 hours. You do the math. :-)<br />
* '''How:''' Back up all your data! There is a possibility that the Freerunner will get damaged during the process (I haven't broken one device yet, but the possibility exists). Openmoko has promised me replacement devices for this case, but they are '''not''' here yet. So until further notice I will '''not''' guarantee that you will walk away from this with a working Freerunner. Mark all the parts (battery, main and cover) with your full name. Use labels which leave no glue residue and remove labels afterward, especially from your battery! One could use [http://en.wikipedia.org/wiki/Masking_tape painting/masking tape], especially the blue version that sticks as less as possible.<br />
* '''Why:''' There will be other Freerunner users around. Use the time to get to know each other in person, share problems, fixes, ...<br />
* '''Contact:''' For questions, etc. please contact: buzz@totalueberwachung.de<br />
<br />
=== May 1st ===<br />
* Roland (1)<br />
* Arne (2)<br />
<br />
=== May 2nd ===<br />
* YourNameHere(1)<br />
<br />
=== May 3rd ===<br />
* [[User:Avanc|Sven]] (1)<br />
* YourNameHere(1)<br />
<br />
=== Remote users ===<br />
Users which would like someone living nearby to take their device to the fix party or would like to mail the device with money included for having it mailed back:<br />
<br />
# <strike>Christ van Willegen (1, Eindhoven, The Netherlands) [http://wiki.openmoko.org/wiki/Special:Emailuser/ChristW Contact me here]</strike>I've sent it to Daniel myself, no need to bring it to the party for me.<br />
# <strike>Johannes K. (1, Stuttgart, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Aragorn Contact me here]</strike> same here<br />
# Pander (1, Utrecht, The Netherlands) [http://wiki.openmoko.org/wiki/Special:Emailuser/Pander Contact me here]<br />
# Philipp (1, Rostock, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Philmax Contact me here]<br />
# Johannes (3, Graz, Austria) [http://wiki.openmoko.org/wiki/Special:Emailuser/Flojoh Contact me here]<br />
# Stefan L. (1, Rostock, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Derlehmann Contact me here]<br />
# Axel K. (1, Stuttgart, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/axel.keller Contact me here]<br />
# G. Neidisch (1, Hamburg, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Gneidisch Contact me here]<br />
# Joachim “nomeata” Breitner (1, Karlsruhe, Germany) [http://www.joachim-breitner.de/contact Contact me here]<br />
# Bastian “gforce“ Bittorf (1, Weimar, Germany) [[User:Fries43]]</div>DanielWillmannhttp://wiki.openmoko.org/wiki/BuzzFixPartyBuzzFixParty2009-04-09T11:10:32Z<p>DanielWillmann: /* May 1st */</p>
<hr />
<div>= Here you can find information about upcoming buzz-fix parties =<br />
<br />
== Braunschweig ==<br />
<br />
* '''When:''' May 1st - May 3rd, start will be 09:00<br />
* '''Where:''' Braunschweig, Germany (exact location still unknown, most likely somewhere around http://informationfreeway.org/?lat=52.27389186224494&lon=10.524687317867564&zoom=17&layers=B0000F000F)<br />
* '''What:''' Please indicate in the list how many devices you will bring. The rework itself will take about 40 minutes. Testing device before and after (including flashing) will take a couple of minutes, but can be parallelised. The day has 24 hours. You do the math. :-)<br />
* '''How:''' Back up all your data! There is a possibility that the Freerunner will get damaged during the process (I haven't broken one device yet, but the possibility exists). Openmoko has promised me replacement devices for this case, but they are '''not''' here yet. So until further notice I will '''not''' guarantee that you will walk away from this with a working Freerunner. Mark all the parts (battery, main and cover) with your full name. Use labels which leave no glue residue and remove labels afterward, especially from your battery! One could use [http://en.wikipedia.org/wiki/Masking_tape painting/masking tape], especially the blue version that sticks as less as possible.<br />
* '''Why:''' There will be other Freerunner users around. Use the time to get to know each other in person, share problems, fixes, ...<br />
<br />
<br />
=== May 1st ===<br />
* Roland (1)<br />
* Arne (2)<br />
<br />
=== May 2nd ===<br />
* YourNameHere(1)<br />
<br />
=== May 3rd ===<br />
* [[User:Avanc|Sven]] (1)<br />
* YourNameHere(1)<br />
<br />
=== Remote users ===<br />
Users which would like someone living nearby to take their device to the fix party or would like to mail the device with money included for having it mailed back:<br />
<br />
* <strike>Christ van Willegen (1, Eindhoven, The Netherlands) [http://wiki.openmoko.org/wiki/Special:Emailuser/ChristW Contact me here]</strike>I've sent it to Daniel myself, no need to bring it to the party for me.<br />
* Pander (1, Utrecht, The Netherlands) [http://wiki.openmoko.org/wiki/Special:Emailuser/Pander Contact me here]<br />
* Philipp (1, Rostock, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Philmax Contact me here]<br />
* Johannes (3, Graz, Austria) [http://wiki.openmoko.org/wiki/Special:Emailuser/Flojoh Contact me here]<br />
* Johannes K. (1, Stuttgart, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Aragorn Contact me here]<br />
* Stefan L. (1, Rostock, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Derlehmann Contact me here]<br />
* Axel K. (1, Stuttgart, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/axel.keller Contact me here]<br />
* G. Neidisch (1, Hamburg, Germany) [http://wiki.openmoko.org/wiki/Special:Emailuser/Gneidisch Contact me here]</div>DanielWillmannhttp://wiki.openmoko.org/wiki/BuzzFixPartyBuzzFixParty2009-04-05T23:35:37Z<p>DanielWillmann: /* Braunschweig */ Added info about replacement devices</p>
<hr />
<div>= Here you can find information about upcoming buzz-fix parties =<br />
<br />
== Braunschweig ==<br />
<br />
* '''When:''' May 1st - May 3rd, start will be 09:00<br />
* '''Where:''' Braunschweig, Germany (exact location still unknown, most likely somewhere around http://informationfreeway.org/?lat=52.27389186224494&lon=10.524687317867564&zoom=17&layers=B0000F000F)<br />
* '''What:''' Please indicate in the list how many devices you will bring. The rework itself will take about 40 minutes. Testing device before and after (including flashing) will take a couple of minutes, but can be parallelised. The day has 24 hours. You do the math. :-)<br />
* '''How:''' Back up all your data! There is a possibility that the Freerunner will get damaged during the process (I haven't broken one device yet, but the possibility exists). Openmoko has promised me replacement devices for this case, but they are '''not''' here yet. So until further notice I will '''not''' guarantee that you will walk away from this with a working Freerunner. <br />
* '''Why:''' There will be other Freerunner users around. Use the time to get to know each other in person, share problems, fixes, ...<br />
<br />
<br />
=== May 1st ===<br />
* YourNameHere(2)<br />
<br />
=== May 2nd ===<br />
* YourNameHere(1)<br />
<br />
=== May 3rd ===<br />
* YourNameHere(1)</div>DanielWillmannhttp://wiki.openmoko.org/wiki/BuzzFixPartyBuzzFixParty2009-04-05T23:06:25Z<p>DanielWillmann: New page: = Here you can find information about upcoming buzz-fix parties = == Braunschweig == * '''When:''' May 1st - May 3rd, start will be 09:00 * '''Where:''' Braunschweig, Germany (exact loca...</p>
<hr />
<div>= Here you can find information about upcoming buzz-fix parties =<br />
<br />
== Braunschweig ==<br />
<br />
* '''When:''' May 1st - May 3rd, start will be 09:00<br />
* '''Where:''' Braunschweig, Germany (exact location still unknown, most likely somewhere around http://informationfreeway.org/?lat=52.27389186224494&lon=10.524687317867564&zoom=17&layers=B0000F000F)<br />
* '''What:''' Please indicate in the list how many devices you will bring. The rework itself will take about 40 minutes. Testing device before and after (including flashing) will take a couple of minutes, but can be parallelised. The day has 24 hours. You do the math. :-)<br />
* '''How:''' Back up all your data! We will flash a different image for testing.<br />
* '''Why:''' There will be other Freerunner users around. Use the time to get to know each other in person, share problems, fixes, ...<br />
<br />
<br />
=== May 1st ===<br />
* YourNameHere(2)<br />
<br />
=== May 2nd ===<br />
* YourNameHere(1)<br />
<br />
=== May 3rd ===<br />
* YourNameHere(1)</div>DanielWillmannhttp://wiki.openmoko.org/wiki/OpenmokoFramework/Status_Update_5OpenmokoFramework/Status Update 52008-11-11T01:25:49Z<p>DanielWillmann: /* What's new since Milestone III */</p>
<hr />
<div><div style="text-align: center; font-weight: bold; font-size: x-large; margin-bottom:1em">Openmoko Framework Team Status Report 2008.11.1</div><br />
<br />
Hi guys! This is the fifth Openmoko Framework Team Status update, featuring our fourth milestone release and more.<br />
<br />
For the general motivation, the goals, and the way we are doing our work, please see [[OpenmokoFramework]].<br />
<br />
{{FSO}}<br />
<br />
<br />
== People & Organization ==<br />
<br />
* Charlie <charlie@openmoko.org> has left the Framework team to embrace new challenges in lower software levels. He'll be around for maintenance work on his code though. Thanks for all your work and good luck with the bare metal :)<br />
<br />
* John <john_lee@openmoko.org> has shifted focus to lead the new long-awaited Openmoko software optimization team. We will surely interface with his team. Good speed, John!<br />
<br />
* As the Openmoko weekly engineering news already told, the freesmartphone.org team has been more "formally" established as an independent team funded by Openmoko Inc. to support defragementing the mobile system services world.<br />
<br />
* More details with regards to the new organization and forthcoming roadmap will come soon<br />
<br />
== DBus APIs ==<br />
<br />
All the public DBus API is documented on the official [http://docs.freesmartphone.org freesmartphone.org API reference] site.<br />
<br />
* The GSM API (org.freesmartphone.GSM.*) has proven very solid and will be tagged 0.9 before the next milestone.<br />
<br />
* The Device API (org.freesmartphone.Device.*) has received some additions for power management and starts stabilizing.<br />
<br />
* The Usage API (http://docs.freesmartphone.org/org.freesmartphone.Usage.html) which was merely a reference counting wrapper over the Device API has gained two companions:<br />
** The Resource API (http://docs.freesmartphone.org/org.freesmartphone.Resource.html) turns this into a full-blown resource management system with choosable policies etc.<br />
** The [http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Usage.html;hb=HEAD#Suspend Suspend] call is resource-aware and gives all resources a chance to prepare for a suspend and to recover after a suspend.<br />
<br />
* org.freesmartphone.Objects.ListObjectsByInterface is using DBus-introspection now.<br />
<br />
* The Events subsystem has gained an experimental [http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Events.html;hb=HEAD DBus interface] to add and remove rules and to test triggers.<br />
<br />
== Implementations ==<br />
<br />
'''Freesmartphone.org Framework Image -- 'Homework' (Milestone IV)'''<br />
<br />
This is the fourth milestone release of the framework and the framework testing application 'Zhone'. With the forthcoming release of other FSO API consumers, Zhone is going to be faded out. Further framework milestone releases will ship in two forms:<br />
# fso-console-image: An FSO-compliant image featuring no user interface manager.<br />
# fso-illume-image: An FSO-compliant image featuring the X-Window system with the Enlightenment-based Illume window manager.<br />
<br />
===Thanks===<br />
<br />
Thanks to all our contributors, especially the testers and the people who build stuff on top of the freesmartphone.org APIs -- notably the [http://shr.bearstech.com/trac/wiki SHR team] who found literally thousands of bugs in the framework that we had to fix for this milestone release. Thanks, guys!<br />
<br />
===Purpose===<br />
<br />
A lightweight image that turns an Openmoko phone into a featurephone and that serves as the basis for further application development using the freesmartphone.org dbus APIs.<br />
<br />
=== What's new since Milestone III ===<br />
<br />
'''Note: These are only the highlights. See the [http://git.freesmartphone.org gitweb] commit logs for the gory details...'''<br />
<br />
* ogsmd<br />
** Lots of bug and stability fixes based on feedback (and debug logs) from people<br />
** SMS API now includes an a{sv} parameter with optional SMS properties<br />
** Phonebook API now supports multiple phonebooks (dialed, missed, answered)<br />
** PDU mode has been improved to handle the 7-bit reference GSM charset, UCS-2 and binary messages<br />
** Workaround for http://docs.openmoko.org/trac/ticket/1024 Change the behaviour with 'ti_calypso_deep_sleep' option in [ogsmd] section (valid options are always, never and adaptive)<br />
** Implemented the org.freesmartphone.GSM.SMS.interface to send and receive SMS without going through the SIM and org.freesmartphone.GSM.Device.SetSimBuffersSms() to switch between SIM buffered mode and not.<br />
<br />
* opgsd<br />
** Improved GTA01 support even with suspend/resume (if gllin v1.1 is installed)<br />
** Various warmstart fixes<br />
** Enabled SBAS by default on ubx chips<br />
<br />
* odeviced<br />
** Use ioctl based screen blanking which saves a lot of power<br />
<br />
* oeventsd<br />
** The rules system has been improved<br />
** New triggers, filters<br />
<br />
* misc<br />
** Much cleaner and improved resource interface with working power management (enable, disable, suspend, resume)<br />
** A persistence module that stores persistent data for subsystems<br />
<br />
* zhone<br />
** New default theme contributed by o_toby<br />
** Show timestamps in incoming SMS<br />
** Support for Chinese and other characters (Unicode support)<br />
** Display more GPS information if available (ephemeris, almanac available, signal status)<br />
<br />
* illume<br />
** GSM module doesn't segfault any more<br />
<br />
===Download / Installation===<br />
<br />
# Grab a uImage and a .jffs2 for your device from http://downloads.openmoko.org/framework/milestone4/.<br />
# 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]].<br />
# Boot and wait until the Zhone main window appears.<br />
# ''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''<br />
# Read the [[FSO UI Tutorial]] and have fun. Note though that this has not been updated yet for milestone 4 (which looks a bit differently and has more features).<br />
<br />
===What you can expect from this release===<br />
<br />
* Telephony<br />
* Phonebook<br />
* SMS<br />
* Messagebook<br />
* GPS<br />
* frameworkd implementing the following dbus APIs:<br />
** org.freesmartphone.GSM.*<br />
** org.freesmartphone.Device.*<br />
** org.freesmartphone.Usage<br />
** org.freesmartphone.Resource<br />
** org.freesmartphone.Events<br />
** org.freedesktop.Gypsy<br />
<br />
===What we expect from you===<br />
<br />
* 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.<br />
<br />
* Focus on using the services. Zhone is just our testing-UI and bears little functionality. It's the services that matter.<br />
<br />
* The best way to interact with the framework is by exploring the dbus APIs. For that you can use these two tools, which are already installed:<br />
** [[OpenmokoFramework/mdbus|mdbus]] -- a dbus introspection and interaction utility,<br />
** [[OpenmokoFramework/cli|cli-framework]] -- a python dbus command line interface.<br />
<br />
* 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).<br />
<br />
* 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.<br />
<br />
===Best way to hand us debug logs===<br />
# log in via ssh<br />
# killall python<br />
# edit /etc/frameworkd.conf and add to the frameworkd section:<br />
## log_level = DEBUG<br />
## log_to = file<br />
## log_destination = /somewhere/where/you/have/space (preferably SD or NFS, etc.)<br />
# 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.<br />
# relaunch frameworkd (/etc/init.d/frameworkd stop; /etc/init.d/frameworkd start)<br />
# log in via ssh (yes, again)<br />
# export DISPLAY=:0.0<br />
# run your favourite client (zhone, cli-framework, ...)<br />
<br />
Attach the logs to the tickets, please.<br />
<br />
==What's next==<br />
<br />
* PIM<br />
* Networking<br />
* Unit Tests<br />
* High Level Documentation<br />
* More Device Support (GTA03, HTC, EZX)<br />
<br />
==The Team==<br />
<br />
Mickey, Jan, Daniel, Guillaume, John, Stefan.</div>DanielWillmannhttp://wiki.openmoko.org/wiki/OpenmokoFramework/Status_Update_5OpenmokoFramework/Status Update 52008-11-11T00:30:59Z<p>DanielWillmann: /* Implementations */ Add release name</p>
<hr />
<div><div style="text-align: center; font-weight: bold; font-size: x-large; margin-bottom:1em">Openmoko Framework Team Status Report 2008.11.1</div><br />
<br />
Hi guys! This is the fifth Openmoko Framework Team Status update, featuring our fourth milestone release and more.<br />
<br />
For the general motivation, the goals, and the way we are doing our work, please see [[OpenmokoFramework]].<br />
<br />
{{FSO}}<br />
<br />
== People & Organization ==<br />
<br />
* Charlie <charlie@openmoko.org> has left the Framework team to embrace new challenges in lower software levels. He'll be around for maintenance work on his code though. Thanks for all your work and good luck with the bare metal :)<br />
<br />
* John <john_lee@openmoko.org> has shifted focus to lead the new long-awaited Openmoko software optimization team. We will surely interface with his team. Good speed, John!<br />
<br />
* As the Openmoko weekly engineering news already told, the freesmartphone.org team has been more "formally" established as an independent team funded by Openmoko Inc. to support defragementing the mobile system services world.<br />
<br />
* More details to come soon<br />
<br />
== DBus APIs ==<br />
<br />
All the public DBus API is documented on the official [http://docs.freesmartphone.org freesmartphone.org API reference] site.<br />
<br />
* The GSM API (org.freesmartphone.GSM.*) has proven very solid and will be tagged 0.9 before the next milestone.<br />
<br />
* The Device API (org.freesmartphone.Device.*) has received some additions for power management and starts stabilizing.<br />
<br />
* The Usage API (http://docs.freesmartphone.org/org.freesmartphone.Usage.html) which was merely a reference counting wrapper over the Device API has gained two companions:<br />
** The Resource API (http://docs.freesmartphone.org/org.freesmartphone.Resource.html) turns this into a full-blown resource management system with choosable policies etc.<br />
** The [http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Usage.html;hb=HEAD#Suspend Suspend] call is resource-aware and gives all resources a chance to prepare for a suspend and to recover after a suspend.<br />
<br />
* org.freesmartphone.Objects.ListObjectsByInterface is using DBus-introspection now.<br />
<br />
* The Events subsystem has gained an experimental [http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Events.html;hb=HEAD DBus interface] to add and remove rules and to test triggers.<br />
<br />
== Implementations ==<br />
<br />
'''Freesmartphone.org Framework Image -- 'Homework' (Milestone IV)'''<br />
<br />
This is the fourth milestone release of the framework and the framework testing application 'Zhone'. With the forthcoming release of other FSO API consumers, Zhone is going to be faded out. Further framework milestone releases will ship in two forms:<br />
# fso-console-image: An FSO-compliant image featuring no user interface manager.<br />
# fso-illume-image: An FSO-compliant image featuring the X-Window system with the Enlightenment-based Illume window manager.<br />
<br />
===Purpose===<br />
<br />
A lightweight image that turns an Openmoko phone into a featurephone and that serves as the basis for further application development using the freesmartphone.org dbus APIs.<br />
<br />
=== What's new since Milestone III ===<br />
<br />
'''Note: These are only the highlights. See the [http://git.freesmartphone.org gitweb] commit logs for the gory details...'''<br />
<br />
insert release news here...<br />
<br />
===Download / Installation===<br />
<br />
# Grab a uImage and a .jffs2 for your device from http://downloads.openmoko.org/framework/milestone4/.<br />
# 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]].<br />
# Boot and wait until the Zhone main window appears.<br />
# ''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''<br />
# Read the [[FSO UI Tutorial]] and have fun. Note though that this has not been updated yet for milestone 4 (which looks a bit differently and has more features).<br />
<br />
===What you can expect from this release===<br />
<br />
* Telephony<br />
* Phonebook<br />
* SMS<br />
* Messagebook<br />
* GPS<br />
* frameworkd implementing the following dbus APIs:<br />
** org.freesmartphone.GSM.*<br />
** org.freesmartphone.Device.*<br />
** org.freesmartphone.Usage<br />
** org.freesmartphone.Resource<br />
** org.freesmartphone.Events<br />
** org.freedesktop.Gypsy<br />
<br />
===What we expect from you===<br />
<br />
* 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.<br />
<br />
* Focus on using the services. Zhone is just our testing-UI and bears little functionality. It's the services that matter.<br />
<br />
* The best way to interact with the framework is by exploring the dbus APIs. For that you can use these two tools, which are already installed:<br />
** [[OpenmokoFramework/mdbus|mdbus]] -- a dbus introspection and interaction utility,<br />
** [[OpenmokoFramework/cli|cli-framework]] -- a python dbus command line interface.<br />
<br />
* 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).<br />
<br />
* 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.<br />
<br />
===Best way to hand us debug logs===<br />
# log in via ssh<br />
# killall python<br />
# edit /etc/frameworkd.conf and add to the frameworkd section:<br />
## log_level = DEBUG<br />
## log_to = file<br />
## log_destination = /somewhere/where/you/have/space (preferably SD or NFS, etc.)<br />
# 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.<br />
# relaunch frameworkd (/etc/init.d/frameworkd stop; /etc/init.d/frameworkd start)<br />
# log in via ssh (yes, again)<br />
# export DISPLAY=:0.0<br />
# run your favourite client (zhone, cli-framework, ...)<br />
<br />
Attach the logs to the tickets, please.<br />
<br />
==The Team==<br />
<br />
Mickey, Jan, Daniel, Guillaume, John, Stefan.</div>DanielWillmannhttp://wiki.openmoko.org/wiki/OpenmokoFramework/Status_Update_3OpenmokoFramework/Status Update 32008-07-30T12:13:48Z<p>DanielWillmann: /* DBus APIs */</p>
<hr />
<div>=Openmoko Framework Team Status Report 2008.7.1=<br />
<br />
Hi guys! This is the third Openmoko Framework Team Status update, featuring our second milestone release and more.<br />
<br />
For the general motivation, the goals, and the way we are doing our work, please see http://wiki.openmoko.org/wiki/OpenmokoFramework.<br />
<br />
== What happened since the last report ==<br />
<br />
=== People ===<br />
<br />
* John Lee <john_lee@openmoko.com> joined the framework team and will help us part time -- welcome on board, John!<br />
<br />
=== DBus APIs ===<br />
<br />
* org.freesmartphone.GSM is almost complete now and stable. We did only minor corrections and enhancements based on client feedback.<br />
* Preliminary versions of org.freesmartphone.Device.Audio and .Accelerometer have been added.<br />
* org.freedesktop.Gypsy has been implemented and org.freesmartphone.GPS will be used to configure more obscure GPS features<br />
* Still brainstorming about org.freesmartphone.Preferences and org.freesmartphone.Context.<br />
<br />
=== Implementations ===<br />
<br />
'''Openmoko Framework Image -- 'All good things' (Milestone II)'''<br />
<br />
This is the second milestone release of the framework and the framework testing application 'Zhone'.<br />
<br />
====Purpose====<br />
<br />
A lightweight image that turns an Openmoko phone into a featurephone and that can serve as the basis for further application development using the freesmartphone.org dbus APIs.<br />
<br />
==== What's new since Milestone I ====<br />
<br />
'''Note: These are only the highlights. See the [http://git.freesmartphone.org gitweb] commit logs for the gory details...'''<br />
<br />
* General<br />
** Merged individual daemons into one daemon with multiple subsystems<br />
** Converted to python logging for debugging<br />
** Enhanced tests and API documentation<br />
<br />
* odevice<br />
** Implements org.freesmartphone.Device.Audio (GStreamer Playback engine and alsa scenario control)<br />
** Implements org.freesmartphone.Device.Input (button switches / headphones insertion etc.)<br />
** Accellerator support (raw data, gestures coming soon)<br />
<br />
* ogsmd (''renamed from ophoned'')<br />
** Implements org.freesmartphone.GSM.PDP (GPRS handling)<br />
** Implements org.freesmartphone.GSM.CB (Cell Broadcast handling)<br />
** Implements org.freesmartphone.GSM.HZ (O2/Genion Home Zone handling)<br />
** Multiparty call handling for TI Calypso<br />
** Initial support for Freescale Neptune Modem and Sierra Modem<br />
** Call forwarding<br />
** DTMF<br />
<br />
* opgsd (''new subsystem'')<br />
** Implements the org.freedesktop.Gypsy DBus API<br />
** Supports U-Blox binary protocol<br />
<br />
* ophoned (''new subsystem'')<br />
** Prepare combined telephony API for VoIP and GSM<br />
<br />
* zhone<br />
** Add phonebook<br />
** Add messagebook<br />
** Add basic GPS viewer<br />
** Integrate Illume launcher and keyboard<br />
** Ship additional programs<br />
<br />
====Download / Installation====<br />
<br />
# Grab a uImage and a .jffs2 for your device from http://downloads.openmoko.org/framework/milestone2/.<br />
# Flash it to your Neo1973 (om-gta01) or NeoFreerunner (om-gta02) with dfu-util.<br />
# Boot and wait until the Zhone main window appears.<br />
# Have fun.<br />
<br />
====What you can expect from this release====<br />
<br />
* Telephony<br />
* Phonebook<br />
* Messagebook (SMS)<br />
* GPS<br />
* frameworkd implementing the following dbus APIs:<br />
** org.freesmartphone.Device.{Audio|Input|IdleNotifier|PowerSupply|Display|LED}<br />
** org.freesmartphone.Usage<br />
** org.freesmartphone.Event<br />
** org.freesmartphone.GSM.{Device|SIM|Network|PDP|CB|HZ}<br />
** org.freedesktop.Gypsy<br />
<br />
====What we expect from you====<br />
<br />
* 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 cool applications.<br />
<br />
===What's next===<br />
<br />
* SMS PDU Handling<br />
* GTA01 GPS integration, cold and warm start improvements<br />
* Preferences integration<br />
* More tutorials and high level documentation<br />
* Work towards Milestone 3 (see [http://trac.openmoko.org Roadmap and Issue Tracker])<br />
<br />
==The Team==<br />
<br />
Mickey, Jan, Daniel, Guillaume, John. <br />
<br />
[[Category:Framework]]</div>DanielWillmannhttp://wiki.openmoko.org/wiki/OpenmokoFramework/Status_Update_3OpenmokoFramework/Status Update 32008-07-30T12:10:17Z<p>DanielWillmann: /* What's new since Milestone I */ NMEA support is experimental and incomplete</p>
<hr />
<div>=Openmoko Framework Team Status Report 2008.7.1=<br />
<br />
Hi guys! This is the third Openmoko Framework Team Status update, featuring our second milestone release and more.<br />
<br />
For the general motivation, the goals, and the way we are doing our work, please see http://wiki.openmoko.org/wiki/OpenmokoFramework.<br />
<br />
== What happened since the last report ==<br />
<br />
=== People ===<br />
<br />
* John Lee <john_lee@openmoko.com> joined the framework team and will help us part time -- welcome on board, John!<br />
<br />
=== DBus APIs ===<br />
<br />
* org.freesmartphone.GSM is almost complete now and stable. We did only minor corrections and enhancements based on client feedback.<br />
* Preliminary versions of org.freesmartphone.Device.Audio and .Accelerometer have been added.<br />
* org.freedesktop.Gypsy has been enhanced to serve the need of advanced GPS device control.<br />
* Still brainstorming about org.freesmartphone.Preferences and org.freesmartphone.Context.<br />
<br />
=== Implementations ===<br />
<br />
'''Openmoko Framework Image -- 'All good things' (Milestone II)'''<br />
<br />
This is the second milestone release of the framework and the framework testing application 'Zhone'.<br />
<br />
====Purpose====<br />
<br />
A lightweight image that turns an Openmoko phone into a featurephone and that can serve as the basis for further application development using the freesmartphone.org dbus APIs.<br />
<br />
==== What's new since Milestone I ====<br />
<br />
'''Note: These are only the highlights. See the [http://git.freesmartphone.org gitweb] commit logs for the gory details...'''<br />
<br />
* General<br />
** Merged individual daemons into one daemon with multiple subsystems<br />
** Converted to python logging for debugging<br />
** Enhanced tests and API documentation<br />
<br />
* odevice<br />
** Implements org.freesmartphone.Device.Audio (GStreamer Playback engine and alsa scenario control)<br />
** Implements org.freesmartphone.Device.Input (button switches / headphones insertion etc.)<br />
** Accellerator support (raw data, gestures coming soon)<br />
<br />
* ogsmd (''renamed from ophoned'')<br />
** Implements org.freesmartphone.GSM.PDP (GPRS handling)<br />
** Implements org.freesmartphone.GSM.CB (Cell Broadcast handling)<br />
** Implements org.freesmartphone.GSM.HZ (O2/Genion Home Zone handling)<br />
** Multiparty call handling for TI Calypso<br />
** Initial support for Freescale Neptune Modem and Sierra Modem<br />
** Call forwarding<br />
** DTMF<br />
<br />
* opgsd (''new subsystem'')<br />
** Implements the org.freedesktop.Gypsy DBus API<br />
** Supports U-Blox binary protocol<br />
<br />
* ophoned (''new subsystem'')<br />
** Prepare combined telephony API for VoIP and GSM<br />
<br />
* zhone<br />
** Add phonebook<br />
** Add messagebook<br />
** Add basic GPS viewer<br />
** Integrate Illume launcher and keyboard<br />
** Ship additional programs<br />
<br />
====Download / Installation====<br />
<br />
# Grab a uImage and a .jffs2 for your device from http://downloads.openmoko.org/framework/milestone2/.<br />
# Flash it to your Neo1973 (om-gta01) or NeoFreerunner (om-gta02) with dfu-util.<br />
# Boot and wait until the Zhone main window appears.<br />
# Have fun.<br />
<br />
====What you can expect from this release====<br />
<br />
* Telephony<br />
* Phonebook<br />
* Messagebook (SMS)<br />
* GPS<br />
* frameworkd implementing the following dbus APIs:<br />
** org.freesmartphone.Device.{Audio|Input|IdleNotifier|PowerSupply|Display|LED}<br />
** org.freesmartphone.Usage<br />
** org.freesmartphone.Event<br />
** org.freesmartphone.GSM.{Device|SIM|Network|PDP|CB|HZ}<br />
** org.freedesktop.Gypsy<br />
<br />
====What we expect from you====<br />
<br />
* 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 cool applications.<br />
<br />
===What's next===<br />
<br />
* SMS PDU Handling<br />
* GTA01 GPS integration, cold and warm start improvements<br />
* Preferences integration<br />
* More tutorials and high level documentation<br />
* Work towards Milestone 3 (see [http://trac.openmoko.org Roadmap and Issue Tracker])<br />
<br />
==The Team==<br />
<br />
Mickey, Jan, Daniel, Guillaume, John. <br />
<br />
[[Category:Framework]]</div>DanielWillmannhttp://wiki.openmoko.org/wiki/ToolchainToolchain2008-06-27T13:32:42Z<p>DanielWillmann: /* Installing additional libraries into the toolchain */ Corrected prefix path</p>
<hr />
<div>{{Languages|Toolchain}}<br />
<br />
<br />
= Introduction =<br />
<br />
A toolchain is a set of tools that allows you to compile code. For Openmoko, we have to differentiate between the following use-cases:<br />
<br />
== Developing a single application ==<br />
<br />
For this, you should use a prebuilt toolchain from the Openmoko project. Here 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]].<br />
<br />
== System Integration and customizing a distribution ==<br />
<br />
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.<br />
<br />
=Basic toolchain usage=<br />
<br />
==Prerequisites==<br />
<br />
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.<br />
<br />
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''').<br />
<br />
A (partial) list of required packages -- please append as necessary:<br />
<br />
* For most Linux version you might only need to install the packages<br />
** autoconf, automake<br />
** binutils, gcc, gcc-c++<br />
** libtool<br />
** ccache<br />
** intltool<br />
<br />
* For Ubuntu 8.04 ( Previous versions don't support libmokoui2 ) the following is required:<br />
sudo apt-get install gcc g++ autoconf automake binutils libtool libglib2.0-dev ccache libxrender-dev intltool libmokoui2-dev libgconf2-dev mtools<br />
<br />
* For Fedora-Core the following is required:<br />
sudo yum install gcc g++ autoconf automake binutils libtool libglib2.0-dev ccache libxrender-dev intltool<br />
<br />
==Downloading and installing==<br />
<br />
The prebuilt toolchain can be downloaded from [http://downloads.openmoko.org/toolchains downloads.openmoko.org]:<br />
<br />
* Creating a destination directory can be anywhere, but for example:<br />
<br />
mkdir ~/sources<br />
cd ~/sources<br />
<br />
* Depending on your CPU type (x86_64 or i686) download the proper package:<br />
<br />
wget http://downloads.openmoko.org/toolchains/openmoko-x86_64-arm-linux-gnueabi-toolchain.tar.bz2<br />
or<br />
wget http://downloads.openmoko.org/toolchains/openmoko-i686-arm-linux-gnueabi-toolchain.tar.bz2<br />
<br />
<br />
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>.<br />
Now you have the following options:<br />
<br />
* Extract it directly as root, so use command "su" first (or prefix the tar command with "sudo" when you are using Debian/Ubuntu):<br />
<br />
cd /<br />
tar -xjvf ~/sources/openmoko-XYZ-arm-linux-gnueabi-toolchain.tar.bz2<br />
<br />
* On Debian-based systems, you can use alien(+fakeroot) to create an easy-to-uninstall package from this .tar.bz2 (install with dpkg -i <package.deb>):<br />
<br />
bunzip2 openmoko-x86_64-arm-linux-gnueabi-toolchain.tar.bz2<br />
gzip openmoko-x86_64-arm-linux-gnueabi-toolchain.tar<br />
fakeroot alien -d openmoko-x86_64-arm-linux-gnueabi-toolchain.tar.gz<br />
<br />
* The prebuilt toolchain is for x86_64 or i686. If you wanted, you could build it on your own with OE:<br />
<br />
bitbake meta-toolchain-openmoko<br />
<br />
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 source it.<br />
Note that if you are not using a "sh" or "bash" shell (check with "echo $SHELL") that you need<br />
to start "sh" or "bash" first.<br />
<br />
. /usr/local/openmoko/arm/setup-env<br />
<br />
* At last, you should add /usr/local/openmoko/arm/bin to your $PATH variable, otherwise the next steps won't work (om-conf and make).<br />
<br />
==Building a sample project==<br />
<br />
In a chosen destination directory (in this example ~/):<br />
<br />
* copy the downloaded sample application source:<br />
<br />
cp -r /usr/local/openmoko/source/openmoko-sample2 ~/<br />
<br />
* Remember to set the proper environment variables (again with "sh" or "bash") for openmoko:<br />
<br />
. /usr/local/openmoko/arm/setup-env<br />
<br />
* 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.<br />
<br />
om-conf openmoko-sample2<br />
<br />
* Optionally now you can modify the source code in openmoko-sample2/src<br />
<br />
* To build the application from the source code you only need to use "make":<br />
<br />
cd openmoko-sample2<br />
make<br />
<br />
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.<br />
<br />
om-conf --prefix=/usr/local/openmoko openmoko-sample2<br />
cd openmoko-sample2<br />
make install<br />
<br />
==How to modify the sample project==<br />
<br />
In order to build your own project by using openmoko-sample2 files, some changes are needed:<br />
<br />
* copy the downloaded sample application source<br />
<br />
cp -r /usr/local/openmoko/source/openmoko-sample2 ~/<br />
<br />
* rename the folder with the name of your project (in this example your-project-name) and delete old sample files <br />
<br />
mv openmoko-sample2 your-project-name<br />
cd your-project-name<br />
cd src<br />
rm *.c<br />
<br />
* copy your sources (in this example your-sources) into src/<br />
<br />
cp your-sources .<br />
cd ..<br />
<br />
* now in the main folder modify autogen.sh by updating the following lines<br />
<br />
PKG_NAME="your-project-name"<br />
<br />
* modify configure.ac by updating the following lines ('main.c' should be the main file in your project)<br />
<br />
AC_INIT(your-project-main, 0.0.1, http://www.openmoko.org/) <br />
AC_CONFIG_SRCDIR(src/main.c)<br />
<br />
* go into data/ folder and rename these files with the name of your project<br />
<br />
cd data<br />
mv openmoko-sample.png your-project-name.png<br />
mv openmoko-sample.desktop your-project-name.desktop<br />
<br />
* modify Makefile.am inside data/ by updating the following lines<br />
<br />
dist_desktop_DATA = your-project-name.desktop<br />
dist_appicon_DATA = your-project-name.png<br />
<br />
* modify Makefile.in inside data/ by updating the following lines<br />
<br />
dist_desktop_DATA = smart-search.desktop<br />
dist_appicon_DATA = smart-search.png<br />
<br />
* modify your-project-name.desktop by updating the following lines<br />
<br />
Name=your-project-name<br />
Encoding=UTF-8<br />
Version=0.0.1<br />
Type=Application<br />
Exec=your-project-name<br />
<br />
* and by adding the following line<br />
<br />
Icon=your-project-name<br />
<br />
* move into src/ folder<br />
<br />
cd ..<br />
cd src<br />
<br />
* modify Makefile.am by updating the following lines<br />
<br />
bin_PROGRAMS = your-project-name <br />
your_project_name_SOURCES = \ <br />
main.c <br />
your_project_name_LDADD = @DEPENDENCIES_LIBS@<br />
<br />
* be sure to put instead of main.c all your .c and .h files and modify all the '-' characters with '_' in the variable names<br />
<br />
==Packaging your application==<br />
<br />
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.<br />
<br />
om-make-ipkg openmoko-sample2<br />
<br />
Now you got openmoko-sample2_0.1_armv4t.ipk , you can `scp' it to your<br />
Neo and install it:<br />
<br />
scp openmoko-sample2_0.1_armv4t.ipk root@192.168.0.202:<br />
ssh root@192.168.0.202 ipkg install openmoko-sample2_0.1_armv4t.ipk<br />
<br />
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.<br />
<br />
You can also supply the version number, a description, and an author / contacts string in a control file:<br />
<br />
om-make-ipkg myapp myapp_control<br />
<br />
A template of myapp_control:<br />
<br />
Package: $appname<br />
Version: 0.1<br />
Description: package built by openmoko toolchain<br />
Section: openmoko/applications<br />
Priority: optional<br />
Maintainer: $USER<br />
Architecture: armv4t<br />
Homepage: http://www.openmoko.org/<br />
Depends: <br />
Source: ${SRC}<br />
<br />
==Where to go from here==<br />
<br />
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<br />
* Using [[Qemu]] to test your applications in an emulated environment<br />
** Ubuntu users might prefer to look at [[Automatic_emulation_in_Ubuntu]]<br />
* Using [[Host-based_development_with_Xoo_and_Xephyr|host-based development]] to improve your efficiency<br />
* Using [[OpenEmbedded]] to customize your Openmoko distribution image<br />
<br />
=Advanced topics=<br />
==Using toolchain provided libraries==<br />
Add the necessary libraries to the _LDADD field in src/Makefile.am, for example:<br />
openmoko_sample2_LDADD = @DEPENDENCIES_LIBS@ -lmokogsmd2<br />
<br />
make sure to run om-conf again after this.<br />
<br />
==Installing additional libraries into the toolchain==<br />
<br />
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.<br />
<br />
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:<br />
<br />
cd ~/source<br />
wget http://downloads.sourceforge.net/uriparser/uriparser-0.6.0.tar.bz2<br />
./configure --host=arm-angstrom-linux-gnueabi \<br />
--prefix=/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/<br />
make<br />
make install<br />
<br />
That's it.<br />
<br />
==Getting your application packaged by OE==<br />
<br />
If you have written a cool application which you want to share with others, the best way to do that is to<br />
<br />
# upload your application source code to a public location<br />
# submit a [[BitBake]] recipe to [[OpenEmbedded]], preferably via the [http://bugzilla.openembedded.org OpenEmbedded bugtracker].<br />
<br />
See also [[Customizing the Openmoko Distribution]].<br />
<br />
==Troubleshooting==<br />
<br />
* Please use the [http://lists.openmoko.org/mailman/listinfo/openmoko-devel Openmoko-Devel] mailing list.<br />
<br />
<br />
[[Category:Software ]]<br />
[[Category:Application Developer]]<br />
[[Category:Openmoko]]</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Community_ResourcesCommunity Resources2008-04-20T18:41:22Z<p>DanielWillmann: /* openmoko-devel@lists.openmoko.org */</p>
<hr />
<div>All resources listed here are available to the general public. Everyone is invited to participate.<br />
<br />
=== Mailing Lists ===<br />
<br />
There are a number of development related mailinglists at http://lists.openmoko.org/<br />
if you feel uncomfortable using mailing lists, you can use [http://gmane.org gmane] forum-like interface.<br />
<br />
==== announce@lists.openmoko.org ====<br />
<br />
A read-only list where the project does official announcements. We strongly recommend subscribing to this list if you want to stay up-to-date with the major project achievements.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/announce<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.announce<br />
<br />
==== buglog@lists.openmoko.org ====<br />
<br />
A read-only list where every status update to a bug (bugzilla entry) will get posted. Nice to keep updated on the bug squashing progress.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/buglog<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.buglog<br />
<br />
==== commitlog@lists.openmoko.org ====<br />
<br />
A read-only list where every source code change (commit to the subversion server) gets posted. Nice to keep posted on development progress.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/commitlog<br />
<br />
==== community@lists.openmoko.org ====<br />
<br />
This is a public mailinglist for generic discussion of our user + developer community. It acts as a place where people discuss their dreams/wishes/ideas about OpenMoko software and supported hardware, applications, and the like. It's an area of general talking and chatting. Please do ''not'' post usage or development questions here.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/community<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.community<br />
<br />
==== distro-devel@lists.openmoko.org ====<br />
<br />
This is a mailinglist on the OpenMoko Distribution. Here issues such as ipk packaging related and root fs image related topics should be discussed. Also, questions regarding the OpenEmbedded based build process go here.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/distro-devel<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.distro<br />
<br />
==== framework-devel@lists.openmoko.org ====<br />
''' NOTE: This mailing list has been closed. Discussion should continue on openmoko-devel. '''<br />
<br />
This is a mailinglist on the OpenMoko Framework. Please use this list to post questions with regard to the OpenMoko Framework, the API's, their usage, API change requests and the like.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/framework-devel<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.framework<br />
<br />
==== gsmd-devel@lists.openmoko.org ====<br />
<br />
This is a mailinglist on the OpenMoko gsmd (GSM daemon) and the corresponding libgsmd.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/gsmd-devel<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.gsmd<br />
<br />
==== openmoko-apps@lists.openmoko.org ====<br />
'''NOTE: This mailing list has been closed. Discussion should continue on openmoko-devel.'''<br />
<br />
This is a public mailinglist about the development of the "official" OpenMoko applications, e.g. openmoko-dialer2, openmoko-dates2, openmoko-contacts2, and openmoko-today2. Please do ''not'' use this list for issues related to third party applications.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/openmoko-apps/<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.apps<br />
<br />
==== openmoko-devel@lists.openmoko.org ====<br />
<br />
This is a public mailing list for discussion of development related to Openmoko in general. The mailing lists framework-devel and openmoko-apps have been merged into this one. Developers who are writing applications using the OpenMoko framework should join this.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/openmoko-devel<br />
<br />
==== openmoko-kernel@lists.openmoko.org ====<br />
<br />
This is a public mailinglist for discussion of kernel development.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/openmoko-kernel<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.kernel<br />
<br />
==== device-owners@lists.openmoko.org ====<br />
<br />
This is a public mailinglist for discussion among actual owners of an OpenMoko based device. Here you can ask for assistance, share your experiences, etc. Please keep this list clean of any philosophical debates or general openmoko related discussion. That's what ''community@lists.openmoko.org'' is for!<br />
<br />
http://lists.openmoko.org/mailman/listinfo/device-owners<br />
<br />
==== webdesign-commitlog@lists.openmoko.org ====<br />
<br />
This is a public read-only mailinglist receiving commit log messages of our web designers. Subscribe to this list if you want to get notified if some of the static content or the templates/skins of our websites change.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/webdesign-commitlog<br />
<br />
=== Wiki ===<br />
<br />
This Wiki is our public wiki, http://wiki.openmoko.org/. You're already in it, if you're reading this. Due to continued defacements/spam we were forced to limit editing in this wiki to registered users which provide a working email address. sorry for that.<br />
<br />
=== Bugzilla ===<br />
<br />
Our bug tracking system for software issues is available at http://bugzilla.openmoko.org/<br />
<br />
=== IRC ===<br />
<br />
There's a #openmoko channel on irc.freenode.net: irc://irc.freenode.net/openmoko<br />
<br />
If you experience any build problems and need help from other developers, it is important that you share your complete output log. To share your output log, just paste it to [http://www.pastebin.ca/ pastebin] or [http://celpaste.morb-design.com/ celpaste] (celpaste is especially for Openmoko) and after submitting it, paste the resulting URL to the IRC channel.<br />
<br />
Thanks to the NSLU2-Linux project, we also have the IRC logs available.<br />
Current 24h live log is always at: http://logs.nslu2-linux.org/livelogs/openmoko.txt<br />
<br />
Previous 24h log is always at: http://logs.nslu2-linux.org/livelogs/openmoko-prev.txt<br />
<br />
Archives back to 29 November 2006 at: http://logs.nslu2-linux.org/livelogs/openmoko/<br />
<br />
=== SVN ===<br />
<br />
There is a [http://subversion.tigris.org/ Subversion] server available at svn.openmoko.org. <br />
<br />
Read-only access is provided via http://svn.openmoko.org/.<br />
<br />
Read-write access for developers is provided via https://svn.openmoko.org/<br />
<br />
Web access for occasional browsing is available via http://svnweb.openmoko.org/<br />
<br />
If you need help, please read more about [[Using Subversion]].<br />
<br />
==== SVN Tree Layout ====<br />
<br />
The Subversion (svn) tree is laid out as follows:<br />
<br />
* trunk (main branch, similar to CVS "HEAD")<br />
** src (program source code)<br />
*** host (programs that work on the host PC)<br />
**** sjf2410-linux<br />
**** ...<br />
*** target (programs that work on the target device)<br />
**** dialer<br />
**** package_manager<br />
**** ...<br />
** doc (Documentation) <br />
*** ...<br />
* branches (branches, created by lead developers if required)<br />
** src<br />
*** host<br />
**** ...<br />
*** target<br />
**** ...<br />
* developers (private/experimental branches, created by individual developers)<br />
** laforge<br />
*** ...<br />
** sean<br />
** mickey<br />
*** ...<br />
** ...<br />
* releases (official 'releases' of code in 'trunk' or 'branches')<br />
** src<br />
*** host<br />
**** ...<br />
*** target<br />
**** ...<br />
<br />
=== Monotone Server ===<br />
<br />
The official [[OpenEmbedded]] repository to build the [[OpenMoko]] distribution can be found at <tt>monotone.openmoko.org</tt>. Note that this is purely a monotone server which has no web presence. See [[MonotoneServer]] for details.<br />
<br />
=== Projects ===<br />
<br />
At http://projects.openmoko.org/ we have a GForge installation. Users can use this as hosting service for their contributed applications.<br />
<br />
== Internal resources ==<br />
<br />
There are some resources which are internal. This means that they are only available for internal developers of FIC / Openmoko Inc. The reason they are internal is either because they deal with information under NDA, or about business strategy. We kindly ask for your understanding that while we really try to be as open as possible, there are some topics which we have to discuss without public participation.<br />
<br />
The internal systems have the domain ''*.internal.openmoko.org''.<br />
<br />
=== IRC ===<br />
<br />
The #openmoko-devel channel is for (paid) internal developers only, sorry.<br />
<br />
== Local Community ==<br />
<br />
See the [[OpenMoko_Local_Groups|OpenMoko Local Groups]]<br />
<br />
{{Languages|Introduction}}<br />
[[Category:Information| ]]<br />
[[Category:Openmoko| ]]</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Community_ResourcesCommunity Resources2008-04-20T18:38:09Z<p>DanielWillmann: /* openmoko-apps@lists.openmoko.org */</p>
<hr />
<div>All resources listed here are available to the general public. Everyone is invited to participate.<br />
<br />
=== Mailing Lists ===<br />
<br />
There are a number of development related mailinglists at http://lists.openmoko.org/<br />
if you feel uncomfortable using mailing lists, you can use [http://gmane.org gmane] forum-like interface.<br />
<br />
==== announce@lists.openmoko.org ====<br />
<br />
A read-only list where the project does official announcements. We strongly recommend subscribing to this list if you want to stay up-to-date with the major project achievements.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/announce<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.announce<br />
<br />
==== buglog@lists.openmoko.org ====<br />
<br />
A read-only list where every status update to a bug (bugzilla entry) will get posted. Nice to keep updated on the bug squashing progress.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/buglog<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.buglog<br />
<br />
==== commitlog@lists.openmoko.org ====<br />
<br />
A read-only list where every source code change (commit to the subversion server) gets posted. Nice to keep posted on development progress.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/commitlog<br />
<br />
==== community@lists.openmoko.org ====<br />
<br />
This is a public mailinglist for generic discussion of our user + developer community. It acts as a place where people discuss their dreams/wishes/ideas about OpenMoko software and supported hardware, applications, and the like. It's an area of general talking and chatting. Please do ''not'' post usage or development questions here.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/community<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.community<br />
<br />
==== distro-devel@lists.openmoko.org ====<br />
<br />
This is a mailinglist on the OpenMoko Distribution. Here issues such as ipk packaging related and root fs image related topics should be discussed. Also, questions regarding the OpenEmbedded based build process go here.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/distro-devel<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.distro<br />
<br />
==== framework-devel@lists.openmoko.org ====<br />
''' NOTE: This mailing list has been closed. Discussion should continue on openmoko-devel. '''<br />
<br />
This is a mailinglist on the OpenMoko Framework. Please use this list to post questions with regard to the OpenMoko Framework, the API's, their usage, API change requests and the like.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/framework-devel<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.framework<br />
<br />
==== gsmd-devel@lists.openmoko.org ====<br />
<br />
This is a mailinglist on the OpenMoko gsmd (GSM daemon) and the corresponding libgsmd.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/gsmd-devel<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.gsmd<br />
<br />
==== openmoko-apps@lists.openmoko.org ====<br />
'''NOTE: This mailing list has been closed. Discussion should continue on openmoko-devel.'''<br />
<br />
This is a public mailinglist about the development of the "official" OpenMoko applications, e.g. openmoko-dialer2, openmoko-dates2, openmoko-contacts2, and openmoko-today2. Please do ''not'' use this list for issues related to third party applications.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/openmoko-apps/<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.apps<br />
<br />
==== openmoko-devel@lists.openmoko.org ====<br />
<br />
This is a public mailinglist for discussion of development of "third party applications". Developers who are writing applications using the OpenMoko framework should join this.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/openmoko-devel<br />
<br />
==== openmoko-kernel@lists.openmoko.org ====<br />
<br />
This is a public mailinglist for discussion of kernel development.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/openmoko-kernel<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.kernel<br />
<br />
==== device-owners@lists.openmoko.org ====<br />
<br />
This is a public mailinglist for discussion among actual owners of an OpenMoko based device. Here you can ask for assistance, share your experiences, etc. Please keep this list clean of any philosophical debates or general openmoko related discussion. That's what ''community@lists.openmoko.org'' is for!<br />
<br />
http://lists.openmoko.org/mailman/listinfo/device-owners<br />
<br />
==== webdesign-commitlog@lists.openmoko.org ====<br />
<br />
This is a public read-only mailinglist receiving commit log messages of our web designers. Subscribe to this list if you want to get notified if some of the static content or the templates/skins of our websites change.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/webdesign-commitlog<br />
<br />
=== Wiki ===<br />
<br />
This Wiki is our public wiki, http://wiki.openmoko.org/. You're already in it, if you're reading this. Due to continued defacements/spam we were forced to limit editing in this wiki to registered users which provide a working email address. sorry for that.<br />
<br />
=== Bugzilla ===<br />
<br />
Our bug tracking system for software issues is available at http://bugzilla.openmoko.org/<br />
<br />
=== IRC ===<br />
<br />
There's a #openmoko channel on irc.freenode.net: irc://irc.freenode.net/openmoko<br />
<br />
If you experience any build problems and need help from other developers, it is important that you share your complete output log. To share your output log, just paste it to [http://www.pastebin.ca/ pastebin] or [http://celpaste.morb-design.com/ celpaste] (celpaste is especially for Openmoko) and after submitting it, paste the resulting URL to the IRC channel.<br />
<br />
Thanks to the NSLU2-Linux project, we also have the IRC logs available.<br />
Current 24h live log is always at: http://logs.nslu2-linux.org/livelogs/openmoko.txt<br />
<br />
Previous 24h log is always at: http://logs.nslu2-linux.org/livelogs/openmoko-prev.txt<br />
<br />
Archives back to 29 November 2006 at: http://logs.nslu2-linux.org/livelogs/openmoko/<br />
<br />
=== SVN ===<br />
<br />
There is a [http://subversion.tigris.org/ Subversion] server available at svn.openmoko.org. <br />
<br />
Read-only access is provided via http://svn.openmoko.org/.<br />
<br />
Read-write access for developers is provided via https://svn.openmoko.org/<br />
<br />
Web access for occasional browsing is available via http://svnweb.openmoko.org/<br />
<br />
If you need help, please read more about [[Using Subversion]].<br />
<br />
==== SVN Tree Layout ====<br />
<br />
The Subversion (svn) tree is laid out as follows:<br />
<br />
* trunk (main branch, similar to CVS "HEAD")<br />
** src (program source code)<br />
*** host (programs that work on the host PC)<br />
**** sjf2410-linux<br />
**** ...<br />
*** target (programs that work on the target device)<br />
**** dialer<br />
**** package_manager<br />
**** ...<br />
** doc (Documentation) <br />
*** ...<br />
* branches (branches, created by lead developers if required)<br />
** src<br />
*** host<br />
**** ...<br />
*** target<br />
**** ...<br />
* developers (private/experimental branches, created by individual developers)<br />
** laforge<br />
*** ...<br />
** sean<br />
** mickey<br />
*** ...<br />
** ...<br />
* releases (official 'releases' of code in 'trunk' or 'branches')<br />
** src<br />
*** host<br />
**** ...<br />
*** target<br />
**** ...<br />
<br />
=== Monotone Server ===<br />
<br />
The official [[OpenEmbedded]] repository to build the [[OpenMoko]] distribution can be found at <tt>monotone.openmoko.org</tt>. Note that this is purely a monotone server which has no web presence. See [[MonotoneServer]] for details.<br />
<br />
=== Projects ===<br />
<br />
At http://projects.openmoko.org/ we have a GForge installation. Users can use this as hosting service for their contributed applications.<br />
<br />
== Internal resources ==<br />
<br />
There are some resources which are internal. This means that they are only available for internal developers of FIC / Openmoko Inc. The reason they are internal is either because they deal with information under NDA, or about business strategy. We kindly ask for your understanding that while we really try to be as open as possible, there are some topics which we have to discuss without public participation.<br />
<br />
The internal systems have the domain ''*.internal.openmoko.org''.<br />
<br />
=== IRC ===<br />
<br />
The #openmoko-devel channel is for (paid) internal developers only, sorry.<br />
<br />
== Local Community ==<br />
<br />
See the [[OpenMoko_Local_Groups|OpenMoko Local Groups]]<br />
<br />
{{Languages|Introduction}}<br />
[[Category:Information| ]]<br />
[[Category:Openmoko| ]]</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Community_ResourcesCommunity Resources2008-04-20T18:37:31Z<p>DanielWillmann: /* framework-devel@lists.openmoko.org */</p>
<hr />
<div>All resources listed here are available to the general public. Everyone is invited to participate.<br />
<br />
=== Mailing Lists ===<br />
<br />
There are a number of development related mailinglists at http://lists.openmoko.org/<br />
if you feel uncomfortable using mailing lists, you can use [http://gmane.org gmane] forum-like interface.<br />
<br />
==== announce@lists.openmoko.org ====<br />
<br />
A read-only list where the project does official announcements. We strongly recommend subscribing to this list if you want to stay up-to-date with the major project achievements.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/announce<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.announce<br />
<br />
==== buglog@lists.openmoko.org ====<br />
<br />
A read-only list where every status update to a bug (bugzilla entry) will get posted. Nice to keep updated on the bug squashing progress.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/buglog<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.buglog<br />
<br />
==== commitlog@lists.openmoko.org ====<br />
<br />
A read-only list where every source code change (commit to the subversion server) gets posted. Nice to keep posted on development progress.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/commitlog<br />
<br />
==== community@lists.openmoko.org ====<br />
<br />
This is a public mailinglist for generic discussion of our user + developer community. It acts as a place where people discuss their dreams/wishes/ideas about OpenMoko software and supported hardware, applications, and the like. It's an area of general talking and chatting. Please do ''not'' post usage or development questions here.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/community<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.community<br />
<br />
==== distro-devel@lists.openmoko.org ====<br />
<br />
This is a mailinglist on the OpenMoko Distribution. Here issues such as ipk packaging related and root fs image related topics should be discussed. Also, questions regarding the OpenEmbedded based build process go here.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/distro-devel<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.distro<br />
<br />
==== framework-devel@lists.openmoko.org ====<br />
''' NOTE: This mailing list has been closed. Discussion should continue on openmoko-devel. '''<br />
<br />
This is a mailinglist on the OpenMoko Framework. Please use this list to post questions with regard to the OpenMoko Framework, the API's, their usage, API change requests and the like.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/framework-devel<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.framework<br />
<br />
==== gsmd-devel@lists.openmoko.org ====<br />
<br />
This is a mailinglist on the OpenMoko gsmd (GSM daemon) and the corresponding libgsmd.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/gsmd-devel<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.gsmd<br />
<br />
==== openmoko-apps@lists.openmoko.org ====<br />
<br />
This is a public mailinglist about the development of the "official" OpenMoko applications, e.g. openmoko-dialer2, openmoko-dates2, openmoko-contacts2, and openmoko-today2. Please do ''not'' use this list for issues related to third party applications.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/openmoko-apps/<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.apps<br />
<br />
==== openmoko-devel@lists.openmoko.org ====<br />
<br />
This is a public mailinglist for discussion of development of "third party applications". Developers who are writing applications using the OpenMoko framework should join this.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/openmoko-devel<br />
<br />
==== openmoko-kernel@lists.openmoko.org ====<br />
<br />
This is a public mailinglist for discussion of kernel development.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/openmoko-kernel<br />
<br />
Gmane: http://news.gmane.org/gmane.comp.handhelds.openmoko.kernel<br />
<br />
==== device-owners@lists.openmoko.org ====<br />
<br />
This is a public mailinglist for discussion among actual owners of an OpenMoko based device. Here you can ask for assistance, share your experiences, etc. Please keep this list clean of any philosophical debates or general openmoko related discussion. That's what ''community@lists.openmoko.org'' is for!<br />
<br />
http://lists.openmoko.org/mailman/listinfo/device-owners<br />
<br />
==== webdesign-commitlog@lists.openmoko.org ====<br />
<br />
This is a public read-only mailinglist receiving commit log messages of our web designers. Subscribe to this list if you want to get notified if some of the static content or the templates/skins of our websites change.<br />
<br />
http://lists.openmoko.org/mailman/listinfo/webdesign-commitlog<br />
<br />
=== Wiki ===<br />
<br />
This Wiki is our public wiki, http://wiki.openmoko.org/. You're already in it, if you're reading this. Due to continued defacements/spam we were forced to limit editing in this wiki to registered users which provide a working email address. sorry for that.<br />
<br />
=== Bugzilla ===<br />
<br />
Our bug tracking system for software issues is available at http://bugzilla.openmoko.org/<br />
<br />
=== IRC ===<br />
<br />
There's a #openmoko channel on irc.freenode.net: irc://irc.freenode.net/openmoko<br />
<br />
If you experience any build problems and need help from other developers, it is important that you share your complete output log. To share your output log, just paste it to [http://www.pastebin.ca/ pastebin] or [http://celpaste.morb-design.com/ celpaste] (celpaste is especially for Openmoko) and after submitting it, paste the resulting URL to the IRC channel.<br />
<br />
Thanks to the NSLU2-Linux project, we also have the IRC logs available.<br />
Current 24h live log is always at: http://logs.nslu2-linux.org/livelogs/openmoko.txt<br />
<br />
Previous 24h log is always at: http://logs.nslu2-linux.org/livelogs/openmoko-prev.txt<br />
<br />
Archives back to 29 November 2006 at: http://logs.nslu2-linux.org/livelogs/openmoko/<br />
<br />
=== SVN ===<br />
<br />
There is a [http://subversion.tigris.org/ Subversion] server available at svn.openmoko.org. <br />
<br />
Read-only access is provided via http://svn.openmoko.org/.<br />
<br />
Read-write access for developers is provided via https://svn.openmoko.org/<br />
<br />
Web access for occasional browsing is available via http://svnweb.openmoko.org/<br />
<br />
If you need help, please read more about [[Using Subversion]].<br />
<br />
==== SVN Tree Layout ====<br />
<br />
The Subversion (svn) tree is laid out as follows:<br />
<br />
* trunk (main branch, similar to CVS "HEAD")<br />
** src (program source code)<br />
*** host (programs that work on the host PC)<br />
**** sjf2410-linux<br />
**** ...<br />
*** target (programs that work on the target device)<br />
**** dialer<br />
**** package_manager<br />
**** ...<br />
** doc (Documentation) <br />
*** ...<br />
* branches (branches, created by lead developers if required)<br />
** src<br />
*** host<br />
**** ...<br />
*** target<br />
**** ...<br />
* developers (private/experimental branches, created by individual developers)<br />
** laforge<br />
*** ...<br />
** sean<br />
** mickey<br />
*** ...<br />
** ...<br />
* releases (official 'releases' of code in 'trunk' or 'branches')<br />
** src<br />
*** host<br />
**** ...<br />
*** target<br />
**** ...<br />
<br />
=== Monotone Server ===<br />
<br />
The official [[OpenEmbedded]] repository to build the [[OpenMoko]] distribution can be found at <tt>monotone.openmoko.org</tt>. Note that this is purely a monotone server which has no web presence. See [[MonotoneServer]] for details.<br />
<br />
=== Projects ===<br />
<br />
At http://projects.openmoko.org/ we have a GForge installation. Users can use this as hosting service for their contributed applications.<br />
<br />
== Internal resources ==<br />
<br />
There are some resources which are internal. This means that they are only available for internal developers of FIC / Openmoko Inc. The reason they are internal is either because they deal with information under NDA, or about business strategy. We kindly ask for your understanding that while we really try to be as open as possible, there are some topics which we have to discuss without public participation.<br />
<br />
The internal systems have the domain ''*.internal.openmoko.org''.<br />
<br />
=== IRC ===<br />
<br />
The #openmoko-devel channel is for (paid) internal developers only, sorry.<br />
<br />
== Local Community ==<br />
<br />
See the [[OpenMoko_Local_Groups|OpenMoko Local Groups]]<br />
<br />
{{Languages|Introduction}}<br />
[[Category:Information| ]]<br />
[[Category:Openmoko| ]]</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Openmoko_Local_Groups:_BraunschweigOpenmoko Local Groups: Braunschweig2007-08-28T12:38:25Z<p>DanielWillmann: /* Possible Participants */ Images for device/debug board</p>
<hr />
<div> See [[Talk:OpenMoko_Local_Groups:_Braunschweig|discussion]]<br />
<br />
=== Possible Participants ===<br />
{|border=1<br />
!Name<br />
!Level of Interest<br />
!Location<br />
!Other<br />
!Has device<br />
!Has debug board<br />
|-<br />
|[[User:DanielWillmann|Daniel]]<br />
|Openmoko Development<br />
|Braunschweig<br />
|Working for OpenMoko<br />
|[[Image: Moko.jpg|center]]<br />
|[[Image: MokoBox.jpg|center]]<br />
|-<br />
|[[User:Shoragan|Jan "Shoragan" Lübbe]]<br />
|Openmoko Development<br />
|Braunschweig<br />
|some things I do for free<br />
|[[Image: Moko.jpg|center]]<br />
|[[Image: MokoBox.jpg|center]]<br />
|-<br />
|[[User:Stefan|Stefan]]<br />
|Openmoko Development<br />
|Schöppenstedt<br />
|Working for OpenMoko<br />
|[[Image: Moko.jpg|center]]<br />
|[[Image: MokoBox.jpg|center]]<br />
|-<br />
|[[User:enodev|Jan]]<br />
|Openmoko Development<br />
|Braunschweig<br />
|<br />
|<br />
|<br />
|-<br />
|[[User:Menges|Menges]]<br />
|*,Sync Calender Address,...<br />
|Braunschweig<br />
|got my Neo today...<br />
|<br />
|<br />
|-<br />
|[[User:Wansti|Marek]]<br />
|Openmoko/Sound Development<br />
|Braunschweig<br />
|Let's make the "Braunschweig Connection" official... :-)<br />
|[[Image: Moko.jpg|center]]<br />
|<br />
|-<br />
<br />
|}<br />
<br />
=== Meetings, Events ===<br />
{|border=1<br />
!Date<br />
!Location<br />
!Topic<br />
!Who<br />
|-<br />
|8.-12. August 2007<br />
|Airport Finowfurt<br />
|[https://events.ccc.de/camp/2007/Intro/ Chaos Communication Camp 2007] and [http://events.ccc.de/camp/2007/GSM_Village GSM Village]<br />
|[[User:DanielWillmann|Daniel]],[[User:Stefan|Stefan]],[[User:Shoragan|Jan]]<br />
|-<br />
|Various<br />
|IT Zentrum Braunschweig, Hans-Sommer Str 65<br />
|See [http://www.lug-bs.de/] for more info. Usually some Neo owners are at the LUG meetings. Use the mailing list to make sure someone with a Neo is there.<br />
|...<br />
|}<br />
<br />
[[Category:OpenMoko_Local_Groups]]</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Talk:Openmoko_Local_Groups:_BraunschweigTalk:Openmoko Local Groups: Braunschweig2007-08-18T13:31:45Z<p>DanielWillmann: </p>
<hr />
<div>--[[User:Menges|Menges]] 13:51, 18 August 2007 (CEST) erde an BS: is there anybody out there??<br />
:jemand am 'spielen, arbeiten, testen, irgendwas am laufen auf dem neo? - schon mal telefoniert, was entwickelt - wer hat eines da? - Erfahrungsaustausch??<br />
<br />
--[[User:DanielWillmann|DanielWillmann]] 15:31, 18 August 2007 (CEST) Jo, alles schon mal getan. Genaueres vielleicht lieber per Mail, IRC oder Jabber. Habe meine Kontaktinformationen mal auf meiner Userseite ergänzt.</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Openmoko_Local_Groups:_BraunschweigOpenmoko Local Groups: Braunschweig2007-08-18T13:27:47Z<p>DanielWillmann: /* Possible Participants */ Changed column skills to neo owner</p>
<hr />
<div> See [[Talk:OpenMoko_Local_Groups:_Braunschweig|discussion]]<br />
<br />
=== Possible Participants ===<br />
{|border=1<br />
!Name<br />
!Neo owner<br />
!Level of Interest<br />
!Location<br />
!Other<br />
|-<br />
|[[User:DanielWillmann|Daniel]]<br />
|yes<br />
|Openmoko Development<br />
|Braunschweig<br />
|Working for OpenMoko<br />
|-<br />
|[[User:Shoragan|Jan "Shoragan" Lübbe]]<br />
|<br />
|Openmoko Development<br />
|Braunschweig<br />
|some things I do for free<br />
|-<br />
|[[User:Stefan|Stefan]]<br />
|<br />
|Openmoko Development<br />
|Schöppenstedt<br />
|Working for OpenMoko<br />
|-<br />
|[[User:enodev|Jan]]<br />
|<br />
|Openmoko Development<br />
|Braunschweig<br />
|-<br />
|[[User:Menges|Menges]]<br />
|<br />
|*,Sync Calender Address,...<br />
|Braunschweig<br />
|got my Neo today...<br />
|-<br />
|}<br />
<br />
=== Meetings, Events ===<br />
{|border=1<br />
!Date<br />
!Location<br />
!Topic<br />
!Who<br />
|-<br />
|8.-12. August 2007<br />
|Airport Finowfurt<br />
|[https://events.ccc.de/camp/2007/Intro/ Chaos Communication Camp 2007] and [http://events.ccc.de/camp/2007/GSM_Village GSM Village]<br />
|[[User:DanielWillmann|Daniel]],[[User:Stefan|Stefan]],[[User:Shoragan|Jan]]<br />
|-<br />
|Various<br />
|IT Zentrum Braunschweig, Hans-Sommer Str 65<br />
|See [http://www.lug-bs.de/] for more info. Usually some Neo owners are at the LUG meetings. Use the mailing list to make sure someone with a Neo is there.<br />
|...<br />
|}<br />
<br />
[[Category:OpenMoko_Local_Groups]]</div>DanielWillmannhttp://wiki.openmoko.org/wiki/User:DanielWillmannUser:DanielWillmann2007-08-18T13:25:22Z<p>DanielWillmann: Contact info</p>
<hr />
<div>== Contact ==<br />
;Mail/JID: daniel@totalueberwachung.de<br />
;Homepage: http://totalueberwachung.de/</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Openmoko_Local_Groups:_BraunschweigOpenmoko Local Groups: Braunschweig2007-07-26T17:56:14Z<p>DanielWillmann: </p>
<hr />
<div> See [[Talk:OpenMoko_Local_Groups:_Braunschweig|discussion]]<br />
<br />
=== Possible Participants ===<br />
{|border=1<br />
!Name<br />
!Skills<br />
!Level of Interest<br />
!Location<br />
!Other<br />
|-<br />
|[[User:DanielWillmann|Daniel]]<br />
|<br />
|Openmoko Development<br />
|Braunschweig<br />
|Working for OpenMoko<br />
|}<br />
<br />
=== Meetings, Events ===<br />
{|border=1<br />
!Date<br />
!Location<br />
!Topic<br />
!Who<br />
|-<br />
|8.-12. August 2007<br />
|Airport Finowfurt<br />
|[https://events.ccc.de/camp/2007/Intro/ Chaos Communication Camp 2007] and [http://events.ccc.de/camp/2007/GSM_Village GSM Village]<br />
|[[User:DanielWillmann|Daniel]],<br />
|-<br />
|Various<br />
|IT Zentrum Braunschweig, Hans-Sommer Str 65<br />
|See [http://www.lug-bs.de/] for more info. Usually some Neo owners are at the LUG meetings. Use the mailing list to make sure someone with a Neo is there.<br />
|...<br />
|}<br />
<br />
[[Category:OpenMoko_Local_Groups]]</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Openmoko_Local_GroupsOpenmoko Local Groups2007-07-26T17:39:20Z<p>DanielWillmann: /* EU */ Add Braunschweiger Group</p>
<hr />
<div>__TOC__<br />
'''OpenMoko Local Groups...'''<br />
<br />
* can be used for developers to meet and get to know each other<br />
* can be used for developing<br />
* may provide the room for real-life discussions away from mailinglists/wiki<br />
* can support early support handling their GTA01Bv4 and exchange experiences<br />
* fasten the community's cohesion<br />
* give motivation<br />
<br />
== EU ==<br />
<br />
* Austria<br />
** [[OpenMoko_Local_Groups: Vienna|Vienna]] <br />
<br />
* Belgium<br />
** [[OpenMoko_local_Groups: Antwerp|Antwerp]]<br />
<br />
* Finland <br />
** [[OpenMoko_Local_Groups: Helsinki|Helsinki]] <br />
<br />
* France <br />
** [[OpenMoko_Local_Groups: Toulouse|Toulouse]] <br />
<br />
* Germany <br />
** [[OpenMoko_Local_Groups: Berlin|Berlin]]<br />
** [[OpenMoko_Local_Groups: Braunschweig|Braunschweig]]<br />
** [[OpenMoko_Local_Groups: Duesseldorf|Duesseldorf]] <br />
** [[OpenMoko_Local_Groups: Frankfurt Main|Frankfurt Main]] <br />
<br />
* [[OpenMoko_Local_Groups: Netherlands|Netherlands]] <br />
** [[OpenMoko_Local_Groups: Ede|Ede]] <br />
<br />
* Italy<br />
** [[OpenMoko_Local_Groups: Milan|Milan]] <br />
<br />
* [[OpenMoko_Local_Groups:_Norway|Norway]]<br />
** [[OpenMoko_Local_Groups: Trondheim|Trondheim]] <br />
<br />
* Poland <br />
** [[OpenMoko_Local_Groups: Warsaw|Warsaw]] <br />
<br />
* Portugal <br />
** [[OpenMoko_Local_Groups: Braga|Braga]] <br />
<br />
* Romania<br />
** [[OpenMoko_Local_Groups: Bucharest|Bucharest]]<br />
<br />
* Spain <br />
** [[OpenMoko_Local_Groups: Madrid|Madrid]] <br />
<br />
* Sweden <br />
** [[OpenMoko_Local_Groups: Gothenburg|Gothenburg]] <br />
<br />
* [[OpenMoko_Local_Groups: Switzerland|Switzerland]] <br />
<br />
* UK<br />
** England<br />
*** [[OpenMoko_Local_Groups: Birmingham|Birmingham]] <br />
*** [[OpenMoko_Local_Groups: London|London]]<br />
** Scotland<br />
*** [[OpenMoko_Local_Groups: Fife|Fife]]<br />
<br />
== Oceania ==<br />
<br />
* Australia <br />
** [[OpenMoko_Local_Groups: Adelaide|Adelaide]]<br />
** [[OpenMoko_Local_Groups: Canberra|Canberra]]<br />
<br />
* New Zealand<br />
** [[OpenMoko_Local_Groups: Auckland|Auckland]]<br />
** [[OpenMoko_Local_Groups: Christchurch|Christchurch]]<br />
<br />
== Asia ==<br />
* India<br />
** [[OpenMoko_Local_Groups: Delhi|Delhi]]<br />
<br />
== USA ==<br />
* Arizona<br />
** [[OpenMoko_Local_Groups: Arizona|Arizona]]<br />
<br />
* California <br />
** [[OpenMoko_Local_Groups: San Diego|San Diego]] <br />
** [[OpenMoko_Local_Groups: San Francisco|San Francisco]] <br />
** [[OpenMoko_Local_Groups: Sacramento|Sacramento]]<br />
<br />
* Colorado<br />
** [[OpenMoko_Local_Groups: Colorado Springs|Colorado Springs]]<br />
<br />
* District of Columbia<br />
** [[OpenMoko_Local_Groups: Washington DC Metro | Washington DC Metro]]<br />
<br />
* Florida<br />
** [[OpenMoko_Local_Groups: Central Florida | Central Florida]]<br />
<br />
* Illinois <br />
** [[OpenMoko_Local_Groups: Chicago|Chicago]]<br />
<br />
* Iowa<br />
** [[OpenMoko_Local_Groups: Iowa-Ames | Iowa-Ames]] <br />
<br />
* Massachusetts<br />
** [[OpenMoko_Local_groups: Boston|Boston]]<br />
<br />
* Michigan <br />
** [[OpenMoko_Local_Groups: Detroit|Detroit]] <br />
<br />
* New Jersey<br />
** [[OpenMoko_Local_Groups: Stevens Institute of Technology, Hoboken NJ | Stevens Institute of Technology, Hoboken NJ ]]<br />
<br />
* New York<br />
** [[OpenMoko_Local_Groups: NYC Metro | NYC Metro]]<br />
<br />
* North Carolina<br />
** [[OpenMoko Local_Groups: Charlotte | Charlotte]]<br />
<br />
* Ohio <br />
** [[OpenMoko_Local_Groups: Cleveland|Cleveland]] <br />
<br />
* Oregon <br />
** [[OpenMoko_Local_Groups: Eugene|Eugene]] <br />
** [[OpenMoko_Local_Groups: Portland|Portland]] <br />
<br />
* Texas <br />
** [[OpenMoko_Local_Groups: North Texas|North Texas]]<br />
<br />
* Utah<br />
** [[OpenMoko_Local_Groups: Salt Lake|Salt Lake]]<br />
<br />
* Virginia<br />
** [[OpenMoko_Local_Groups: Virginia|Virginia]]<br />
<br />
== Canada ==<br />
* Alberta<br />
** [[OpenMoko_Local_Groups: Edmonton|Edmonton]]<br />
* British Columbia<br />
** [[OpenMoko_Local_Groups: Vancouver|Vancouver]]<br />
* Ontario<br />
** [[OpenMoko_Local_Groups: Ottawa|Ottawa]]<br />
** [[OpenMoko_Local_Groups: Toronto|Toronto]]<br />
* Quebec <br />
** [[OpenMoko_Local_Groups: Montreal|Montreal]] <br />
<br />
<br />
[[Category:Community]]<br />
[[Category:Neo1973 Phase 1 related]]</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Libgconf-bridgeLibgconf-bridge2007-04-13T23:57:58Z<p>DanielWillmann: /* Architectural Details */ Layout issue</p>
<hr />
<div>== Overview ==<br />
libgconf-bridge is a utility library for binding GObject properties to GConf keys. It is intended to save the application programmer from having to implement property synchronisation manually.<br />
<br />
<br />
== Use ==<br />
* We want to save the state of a program and restore it at the next start<br />
<br />
== Constraints ==<br />
(None)<br />
<br />
== Architectural Details ==<br />
* In case an application 'hangs' in a state we want to be able to reset the state of the application. <br> This can be be done through the context menu in mainmenu.<br />
<br />
== Implementation Recommendations ==<br />
(None)<br />
<br />
== Unresolved Issues ==<br />
* How robust is gconf in case of (disk) memory shortage or sudden power loss situations?<br />
<br />
== Questions and Answers ==<br />
(None)</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Libgconf-bridgeLibgconf-bridge2007-04-13T23:56:34Z<p>DanielWillmann: /* Unresolved Issues */ Clarified OOM issues</p>
<hr />
<div>== Overview ==<br />
libgconf-bridge is a utility library for binding GObject properties to GConf keys. It is intended to save the application programmer from having to implement property synchronisation manually.<br />
<br />
<br />
== Use ==<br />
* We want to save the state of a program and restore it at the next start<br />
<br />
== Constraints ==<br />
(None)<br />
<br />
== Architectural Details ==<br />
* In case an application 'hangs' in a state we want to be able to reset the state of the application.<br />
This can be be done through the context menu in mainmenu<br />
<br />
== Implementation Recommendations ==<br />
(None)<br />
<br />
== Unresolved Issues ==<br />
* How robust is gconf in case of (disk) memory shortage or sudden power loss situations?<br />
<br />
== Questions and Answers ==<br />
(None)</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Libgconf-bridgeLibgconf-bridge2007-04-13T20:55:45Z<p>DanielWillmann: Describe usage of libgconf-bridge</p>
<hr />
<div>== Overview ==<br />
libgconf-bridge is a utility library for binding GObject properties to GConf keys. It is intended to save the application programmer from having to implement property synchronisation manually.<br />
<br />
<br />
== Use ==<br />
* We want to save the state of a program and restore it at the next start<br />
<br />
== Constraints ==<br />
(None)<br />
<br />
== Architectural Details ==<br />
* In case an application 'hangs' in a state we want to be able to reset the state of the application.<br />
This can be be done through the context menu in mainmenu<br />
<br />
== Implementation Recommendations ==<br />
(None)<br />
<br />
== Unresolved Issues ==<br />
* How robust is gconf in case of OOM, sudden power loss situations?<br />
<br />
== Questions and Answers ==<br />
(None)</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Wishlist/Alarm_daemonWishlist/Alarm daemon2007-04-13T15:35:18Z<p>DanielWillmann: Inital thoughts on the alarm daemon</p>
<hr />
<div>== Overview ==<br />
The alarm daemon provides an interface for applications to register times at which an application needs to do a specific task.<br />
<br />
== Usage Cases ==<br />
* An alarm should turn on the phone if needed<br />
* I want to specify relative and absolute times (i.e. in 5 hours, on May 1st 2007, 2:00pm)<br />
<br />
== Constraints ==<br />
<br />
== Architectural Details ==<br />
The alarm daemon will probably be part of neod since it will need to set the RTC alarm for the next event. The interface for the applications is exposed via dbus.<br />
<br />
== Implementation Recommendations ==<br />
We should definitely look at how the maemo project is handling this and if we can modify their approach to fit our needs. We don't want to have to many different solutions to a similar problem, but rather cooperate.<br />
<br />
At start neod will have to query the next event in eds (to determine when the next wakeup has to occur). If a new event is added eds will broadcast the change through dbus.<br />
<br />
Applications will (de-)register for a specific time at which the alarm daemon (neod) will call the applikation with a special command line parameter to reflect that the application has been called for an alarm.<br />
<br />
== Unresolved Issues ==<br />
* If the device is powering down during the alarm we might miss the RTC alarm. Maybe we should just move the alarm time back a minute if we are powering down and the alarm is near?<br />
* What do we do if the application is already running?<br />
<br />
== Questions and Answers ==<br />
(None)</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Manually_using_GSMManually using GSM2007-03-20T00:15:49Z<p>DanielWillmann: /* Connecting to GSM Modem */</p>
<hr />
<div>'''When men were real men and typed their own AT commands...'''<br />
<br />
This is a short guide how to manually get GSM going.<br />
<br />
== Requirements ==<br />
<br />
* GTA01Bv2 or GTA01Bv3 with very recent u-boot bootloader, providing usbtty (serial over USB) support)<br />
* Do not connect any debug board!<br />
<br />
== Walk-Through ==<br />
<br />
=== Booting the system ===<br />
<br />
* Make sure the rootfs you use has 'auto usb0' in /etc/network/interfaces<br />
* Configure the host's usb0 interface to 192.168.0.200 netmask 255.255.255.0<br />
* ssh to root@192.168.0.201<br />
<br />
=== Disabling the getty ===<br />
<br />
Our default images all have a getty running on /dev/ttySAC0, please edit /etc/inittab and disable the getty on that port<br />
<br />
=== Reducing the loglevel ===<br />
<br />
{{note|You don't need this in kernel builds with patchset &ge; 1288}}<br />
<br />
To keep the kernel from writing to /dev/ttySAC0, you need to use <code>dmesg -n1</code>.<br />
<br />
=== Powering up the GSM Modem ===<br />
<br />
* verify there is no getty or any other app running on /dev/ttySAC0 <br />
root@fic-gta01:~$ lsof | grep ttySAC0<br />
* power-up the GSM Modem<br />
root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-gsm.0/power_on<br />
<br />
=== Connecting to GSM Modem ===<br />
<br />
* change permissions on ttySAC0<br />
root@fic-gta01:~$ chown uucp.uucp /dev/ttySAC0<br />
* setup /usr/spool/uucp<br />
root@fic-gta01:~$ mkdir /usr/spool<br />
root@fic-gta01:~$ mkdir /usr/spool/uucp<br />
root@fic-gta01:~$ chown uucp.uucp /usr/spool/uucp<br />
* enable CTS/RTS flow control<br />
root@fic-gta01:~$ stty -F /dev/ttySAC0 crtscts<br />
* access the GSM Modem UART<br />
root@fic-gta01:~$ cu -l /dev/ttySAC0<br />
Connected.<br />
AT-Command Interpreter Ready<br />
OK<br />
<br />
''If it will hang on "Connected" message then probably your device has nonworking GSM modem - check [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=256 Bug #256]''<br />
<br />
'''cu seems to have problems with the hardware flow control. The one way I always managed to get GSM working is to start cu first and then on a different console issue the stty command.'''<br />
--[[User:DanielWillmann|DanielWillmann]] 01:15, 20 March 2007 (CET)<br />
<br />
=== Using it manually ===<br />
==== Registering with the Network ====<br />
<br />
* enter the following [[Hardware:AT_Commands]]:<br />
<pre><br />
ATE1<br />
OK<br />
AT+CFUN=1<br />
ERROR<br />
AT+CPIN="...."<br />
OK<br />
AT+COPS<br />
OK<br />
</pre><br />
<br />
==== Answering an incoming call ====<br />
<pre><br />
RING<br />
ATA<br />
OK<br />
</pre><br />
<br />
==== Dialling an outgoing call ====<br />
<br />
To actually be able to talk you have to configure your audio accordingly<br />
<br />
<pre><br />
root@fic-gta01:~$ cd /etc/alsa/<br />
root@fic-gta01:/etc/alsa$ wget http://opensource.wolfsonmicro.com/~gg/gsmheadset.working.state<br />
root@fic-gta01:/etc/alsa$ alsactl -f /etc/alsa/gsmheadset.working.state restore<br />
</pre><br />
<br />
Up the "Amp right" volume to hear the speaker on both ears, then dial<br />
<br />
<pre><br />
ATD012340234;<br />
</pre><br />
<br />
==== Hanging up ====<br />
<pre><br />
ATH<br />
OK<br />
</pre><br />
<br />
=== Using [[gsmd]] ===<br />
<br />
You can use the [[gsmd]] and [[libgsmd-util]] programs to have a slightly more high-level interface to the GSM Modem. It's still console based, though.<br />
<br />
For further instructions, see [[gsmd]]<br />
<br />
=== Using tui ===<br />
<br />
Tui (available from www.sf.net/projects/tui) is able to do all this. It is still text-based, but input-rxvt can take data from touchscreen, so you can actually do the calls using your finger. It also plays wav file on incoming call, so it is theoretically usable. It even does caller id.<br />
<br />
=== Manually using GPRS ===<br />
<br />
See [[Manually using GPRS]]</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Booting_the_Neo_FreeRunner_from_SD_via_U-BootBooting the Neo FreeRunner from SD via U-Boot2007-03-14T15:28:01Z<p>DanielWillmann: /* Step 3: Add uboot boot entry */ uImage-8 vs. uImage typo</p>
<hr />
<div>Here are the steps described to boot your system from an SD card.<br />
<br />
=== Step 1: build your kernel ===<br />
Get a fresh 2.6.20.2 kernel and apply the patches from the OpenMoko projekt.<br />
alphaone@elara openmoko $ wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.20.2.tar.bz2<br />
alphaone@elara openmoko $ tar -xjf linux-2.6.20.2.tar.bz2<br />
alphaone@elara openmoko $ cd linux-2.6.20.2<br />
alphaone@elara linux-2.6.20.2 $ svn co http://svn.openmoko.org/trunk/src/target/kernel/patches<br />
alphaone@elara linux-2.6.20.2 $ quilt -a push<br />
<br />
Now download the defconfig from http://svn.openmoko.org/trunk/oe/packages/linux/linux-gta01/defconfig-2.6.20.2-fic-gta01 and tweak the kernel in any way you want (be sure to build MMC/SD card support into the kernel). When done build the kernel and follog the steps in [[Bootloader#Creating_bootable_images]].<br />
<br />
=== Step 2: populate SD card ===<br />
Mount your SD card somewhere and put your image on it<br />
<br />
elara openmoko # mount /dev/mmcblk0p1 /dev/moko<br />
elara openmoko # tar -C /mnt/moko/ -xvzf openmoko-devel-image-fic-gta01-20070313022035.rootfs.tar.gz<br />
<br />
Now we also want the kernel on there<br />
<br />
elara openmoko # cp uImage /mnt/moko/boot/<br />
<br />
=== Step 3: Add uboot boot entry ===<br />
Start uboot in bootmenu mode and add the following entry via serial console:<br />
<br />
GTA01Bv3 # setenv menu_4 Boot from SD: setenv bootargs root=/dev/mmcblk0p1 rootdelay=5 console=ttySAC0,115200 console=tty0 loglevel=8 \${mtdparts}\; mmcinit\; ext2load mmc 0 0x32000000 /boot/\${sd_image_name}\; bootm 0x32000000<br />
GTA01Bv3 # setenv sd_image_name uImage<br />
GTA01Bv3 # saveenv<br />
<br />
You can now easily boot a different kernel by changing the variable sd_image_name to the new name.<br />
<br />
=== Step 4: Boot into the new system ===<br />
Power off your device, insert the SD card and boot into the boot menu. You should have an entry called "Boot from SD" which does exactly that. :-)</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Main_PageMain Page2007-03-14T15:10:16Z<p>DanielWillmann: /* Hands-on Guides */ Add Booting from SD link</p>
<hr />
<div>{|align=right<br />
|__TOC__<br />
|}<br />
<big>'''Welcome to the OpenMoko public Wiki'''</big><br><br />
<small>For other languages see the [[#bottom|bottom]] of this page.</small> <br />
<br />
This is to be the evolving, definitive resource on [[Neo1973]] development -- the GSM+[[Hardware:AGPS|AGPS]] Smartphone running [[OpenMoko]]. The intention is to collaboratively improve and update all information on this site.<br />
<br />
== Introduction ==<br />
<br />
* [[Introduction]] - What is OpenMoko.<br />
** [[Introduction#Photos|Photos]]<br />
** [[Introduction#Videos|Videos]]<br />
* [[FAQ | Frequently Asked Questions]]<br />
* [[ChangeLog]] - Change log of most important changes of each day<br />
<br />
== Project Resources ==<br />
* [[Development resources]] - Describes the resources (lists, svn,&nbsp;...)<br />
** [[Development resources#Mailing_Lists|Mailing Lists]]<br />
** [[Development resources#Wiki|Wiki]]<br />
** [[Development resources#Bugzilla|Bugzilla]]<br />
** [[Development resources#IRC|IRC]]<br />
** [[Development resources#SVN|svn + svnweb]]<br />
** [[Development resources#Projects|projects]]<br />
** [http://buildhost-old.openmoko.org/releases releases]<br />
** [http://buildhost-old.openmoko.org/snapshots snapshots]<br />
** [http://buildhost.openmoko.org/tmp/deploy/images unstable images]<br />
<br />
== Developer's Documentation ==<br />
<br />
=== Hands-on Guides ===<br />
* [[Getting Started with your Neo1973]]<br />
* [[MokoMakefile|Building OpenMoko using the MokoMakefile]] <br />
* [[Building OpenMoko from scratch]]<br />
** Old [[Building OpenMoko from scratch (pre-BBT)]]<br />
* [[Migration to bad block tolerant builds]]<br />
* [[Getting Openmoko working on host with Xoo]]<br />
* [[Booting from SD]]<br />
<br />
=== Hardware Reference Documentation ===<br />
<br />
* All [[Hardware]] related documentation and specifications<br />
* [[Neo1973 Hardware]] - Overview about the Components we use, PCB Photographs<br />
** [[Disassembling Neo1973]] - A photo story about disassembling the hardware<br />
* [[Debug Board]] - The Debug Board for the Neo1973<br />
** [[Connecting Neo1973 with Debug Board v2]]<br />
<br />
=== Software Reference Documentation ===<br />
* Architectural<br />
** [[OpenMokoFramework]] - The OpenMoko Application Framework<br />
* Host utilities<br />
** [[dfu-util]] - A [[USB DFU]] (Device Firmware Update) host program<br />
** [[devirginator]] - A set of scripts to re-program the entire device and last-resort phone un-bricking<br />
** [[Toolchain]] - The toolchain we use for compilation<br />
** [[Neo1973 OpenOCD]] - The On-Chip Debugger we use for development<br />
** [[OpenEmbedded]] - The distribution building framework<br />
* Device Software<br />
** Low-Level<br />
*** [[u-boot]] - The bootloader we use, including docs to our modifications<br />
*** [[kernel]] - The Linux Kernel we use, including docs to our modifications<br />
** Userspace<br />
*** [[gsmd]] - the GSM daemon managing the GSM Modem<br />
*** [[gpsd]] - the AGPS (Assisted GPS) daemon<br />
*** [[OpenMoko]] - The OpenMoko distribution<br />
**** [[OpenMoko2007]] - The first intended release of it<br />
**** [[Userspace root image]]<br />
<br />
==== User Interface Related ====<br />
* [[Look & Feel]]<br />
* [[Applications]]<br />
* [[Widgets]]<br />
** [[Widget Inheritance Graph]]<br />
<br />
=== Misc. Development Related ===<br />
* [[Templates]]<br />
* [[PIM Storage]]<br />
* [[Coding Guidelines]]<br />
* [[How to run OpenMoko Apps on PC]]<br />
* [[OpenMoko#Setting_up_an_OpenMoko_SDK|How to setup the OpenMoko SDK]]<br />
* [[License]] - How we license our code<br />
* [[Development resources]] - Describes the resources (lists, svn, ...)<br />
* [[Neo1973 Phase 0]] -- Information for Phase 0 device owners<br />
<br />
== Administrative / Organizational ==<br />
<br />
* [[Shipping Notes]] - Information to help FIC how to ship products to you<br />
* [[My Account]] - Ideas for what sort of account based services FIC should provide with the phone.<br />
<br />
== Miscellaneous ==<br />
* [[Neo1973 and Windows]] - If you want to commit that offence ;) (does not work, help!)<br />
* [[Press Coverage]] - What the press says about the OpenMoko project<br />
* [[mFAQ]] - The OpenMoko Misinformation FAQ ('''mFAQ''') - What the press '''''incorrectly''''' says about the OpenMoko project<br />
* [[Wish List]] - A collection of ideas and ideals we'd like to see implemented some day<br />
* [[Wish List - Hardware]] - A collection of ideas we'd like to see in the next Neo release<br />
* [[Media Content]] - What types of media on the device can we use (that is non-software)?<br />
* [[Testimonials]] - How did you get to OpenMoko?<br />
* [[Buying Interest List]] - (Not official and not a pre-order page) Have you have put money aside for Neo1973? Put your nick here.<br />
* [[Style Sheet]] - The '''''correct''''' way to spell OpenMoko and other words<br />
* [[iPhone]] - Comparison between Apple iPhone and FIC Neo1973<br />
* [[Translation]] - Translation of OpenMoko<br />
* [[Summer of code]] - Our page with project applications for Googles Summer of Code<br />
<br />
== FIC / OpenMoko at Events ==<br />
<br />
* [http://pingwinaria.linux.org.pl/PLUG/imprezy/pingwinaria/2007/agenda Pingwinaria 2007] - Krynica, Poland - 15-18 March 2007 - Tomasz Zieliński will give a talk about OpenMoko and Marcin Juszkiewicz will talk about OpenEmbedded<br />
* [http://fostel2007.fostel.org/index.php/Main_Page FOSTEL] - Paris, France - 4-5 April 2007 - Sean Moss-Pultz will be there<br />
<br />
===Past Events===<br />
* [[FOSDEM]] - Brussels, Belgium - 23 to 25 Februari 2007<br />
* [[ETel]] - Tuesday, February 27 through Thursday, March 1, 2007, near San Francisco<br />
* [http://www.linuxforum.dk/2007/ Linux Forum] - Copenhagen Denmark. 2.-3. March 2007. [http://www.linuxforum.dk/2007/program/saturday/Martin_Hansen.shtml Presentation] about OpenMoko on Saturday by Martin Hansen and Ole Tange.<br />
<br />
== Sections by target audience ==<br />
<br />
* [[Basic End-user]] - Information for end users that want basic functionality and no surprises<br />
* [[Advanced End-user]] - Information for advanced end-users that want advanced and experimental functionality but who are not programmers<br />
* [[Application Developer]] - Information for application developers including ideas and specifications for applications, and tools to build them<br />
* [[System Developer]] - Information for the system developer including bootloader, kernel, and libraries<br />
* [[Hardware Developer]] - Information for the hardware developer including hardware specs, and debug board<br />
<br />
== Getting started with this wiki ==<br />
<br />
* Please read our [[OpenMoko Wiki Editing Guidelines]]<br />
* [http://www.mediawiki.org/wiki/Help:Configuration_settings Configuration settings list]<br />
* [http://meta.wikimedia.org/wiki/Help:Wikitext_reference MediaWiki Wikitext Reference]<br />
* [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ]<br />
<br />
<span id="bottom"></span><br />
{{Languages|Main_Page}}</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Booting_the_Neo_FreeRunner_from_SD_via_U-BootBooting the Neo FreeRunner from SD via U-Boot2007-03-14T14:36:22Z<p>DanielWillmann: /* Step 3: Add uboot boot entry */ Make image name variable</p>
<hr />
<div>Here are the steps described to boot your system from an SD card.<br />
<br />
=== Step 1: build your kernel ===<br />
Get a fresh 2.6.20.2 kernel and apply the patches from the OpenMoko projekt.<br />
alphaone@elara openmoko $ wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.20.2.tar.bz2<br />
alphaone@elara openmoko $ tar -xjf linux-2.6.20.2.tar.bz2<br />
alphaone@elara openmoko $ cd linux-2.6.20.2<br />
alphaone@elara linux-2.6.20.2 $ svn co http://svn.openmoko.org/trunk/src/target/kernel/patches<br />
alphaone@elara linux-2.6.20.2 $ quilt -a push<br />
<br />
Now download the defconfig from http://svn.openmoko.org/trunk/oe/packages/linux/linux-gta01/defconfig-2.6.20.2-fic-gta01 and tweak the kernel in any way you want (be sure to build MMC/SD card support into the kernel). When done build the kernel and follog the steps in [[Bootloader#Creating_bootable_images]].<br />
<br />
=== Step 2: populate SD card ===<br />
Mount your SD card somewhere and put your image on it<br />
<br />
elara openmoko # mount /dev/mmcblk0p1 /dev/moko<br />
elara openmoko # tar -C /mnt/moko/ -xvzf openmoko-devel-image-fic-gta01-20070313022035.rootfs.tar.gz<br />
<br />
Now we also want the kernel on there<br />
<br />
elara openmoko # cp uImage /mnt/moko/boot/<br />
<br />
=== Step 3: Add uboot boot entry ===<br />
Start uboot in bootmenu mode and add the following entry via serial console:<br />
<br />
GTA01Bv3 # setenv menu_4 Boot from SD: setenv bootargs root=/dev/mmcblk0p1 rootdelay=5 console=ttySAC0,115200 console=tty0 loglevel=8 \${mtdparts}\; mmcinit\; ext2load mmc 0 0x32000000 /boot/\${sd_image_name}\; bootm 0x32000000<br />
GTA01Bv3 # setenv sd_image_name uImage-8<br />
GTA01Bv3 # saveenv<br />
<br />
You can now easily boot a different kernel by changing the variable sd_image_name to the new name.<br />
<br />
=== Step 4: Boot into the new system ===<br />
Power off your device, insert the SD card and boot into the boot menu. You should have an entry called "Boot from SD" which does exactly that. :-)</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Booting_the_Neo_FreeRunner_from_SD_via_U-BootBooting the Neo FreeRunner from SD via U-Boot2007-03-13T13:55:11Z<p>DanielWillmann: My steps to get a complete system running from SD card</p>
<hr />
<div>Here are the steps described to boot your system from an SD card.<br />
<br />
=== Step 1: build your kernel ===<br />
Get a fresh 2.6.20.2 kernel and apply the patches from the OpenMoko projekt.<br />
alphaone@elara openmoko $ wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.20.2.tar.bz2<br />
alphaone@elara openmoko $ tar -xjf linux-2.6.20.2.tar.bz2<br />
alphaone@elara openmoko $ cd linux-2.6.20.2<br />
alphaone@elara linux-2.6.20.2 $ svn co http://svn.openmoko.org/trunk/src/target/kernel/patches<br />
alphaone@elara linux-2.6.20.2 $ quilt -a push<br />
<br />
Now download the defconfig from http://svn.openmoko.org/trunk/oe/packages/linux/linux-gta01/defconfig-2.6.20.2-fic-gta01 and tweak the kernel in any way you want (be sure to build MMC/SD card support into the kernel). When done build the kernel and follog the steps in [[Bootloader#Creating_bootable_images]].<br />
<br />
=== Step 2: populate SD card ===<br />
Mount your SD card somewhere and put your image on it<br />
<br />
elara openmoko # mount /dev/mmcblk0p1 /dev/moko<br />
elara openmoko # tar -C /mnt/moko/ -xvzf openmoko-devel-image-fic-gta01-20070313022035.rootfs.tar.gz<br />
<br />
Now we also want the kernel on there<br />
<br />
elara openmoko # cp uImage /mnt/moko/boot/<br />
<br />
=== Step 3: Add uboot boot entry ===<br />
Start uboot in bootmenu mode and add the following entry via serial console:<br />
<br />
GTA01Bv3 # setenv menu_4 Boot from SD: setenv bootargs root=/dev/mmcblk0p1 rootdelay=5 console=ttySAC,115200 console=tty0 loglevel=8 \${mtdparts}\; mmcinit\; ext2load mmc 0 0x32000000 /boot/uImage\; bootm 0x32000000<br />
GTA01Bv3 # saveenv<br />
<br />
=== Step 4: Boot into the new system ===<br />
Power off your device, insert the SD card and boot into the boot menu. You should have an entry called "Boot from SD" which does exactly that. :-)</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Manually_using_GSMManually using GSM2007-03-09T12:02:24Z<p>DanielWillmann: /* Dialling an outgoing call */ Added pointer to alsa state files</p>
<hr />
<div>'''When men were real men and typed their own AT commands...'''<br />
<br />
This is a short guide how to manually get GSM going.<br />
<br />
== Requirements ==<br />
<br />
* GTA01Bv2 or GTA01Bv3 with very recent u-boot bootloader, providing usbtty (serial over USB) support)<br />
* Do not connect any debug board!<br />
<br />
== Walk-Through ==<br />
<br />
=== Booting the system ===<br />
<br />
* Make sure the rootfs you use has 'auto usb0' in /etc/network/interfaces<br />
* Configure the host's usb0 interface to 192.168.0.200 netmask 255.255.255.0<br />
* ssh to root@192.168.0.201<br />
<br />
=== Disabling the getty ===<br />
<br />
Our default images all have a getty running on /dev/ttySAC0, please edit /etc/inittab and disable the getty on that port<br />
<br />
=== Reducing the loglevel ===<br />
<br />
{{note|You don't need this in kernel builds with patchset &ge; 1288}}<br />
<br />
To keep the kernel from writing to /dev/ttySAC0, you need to use <code>dmesg -n1</code>.<br />
<br />
=== Powering up the GSM Modem ===<br />
<br />
* verify there is no getty or any other app running on /dev/ttySAC0 <br />
root@fic-gta01:~$ lsof | grep ttySAC0<br />
* power-up the GSM Modem<br />
root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-gsm.0/power_on<br />
* change permissions on ttySAC0<br />
root@fic-gta01:~$ chown uucp.uucp /dev/ttySAC0<br />
* setup /usr/spool/uucp<br />
root@fic-gta01:~$ mkdir /usr/spool<br />
root@fic-gta01:~$ mkdir /usr/spool/uucp<br />
root@fic-gta01:~$ chown uucp.uucp /usr/spool/uucp<br />
* access the GSM Modem UART<br />
root@fic-gta01:~$ cu -l /dev/ttySAC0<br />
Connected.<br />
AT-Command Interpreter Ready<br />
OK<br />
<br />
=== Using it manually ===<br />
==== Registering with the Network ====<br />
<br />
* enter the following [[Hardware:AT_Commands]]:<br />
<pre><br />
ATE1<br />
OK<br />
AT+CFUN=1<br />
ERROR<br />
AT+CPIN="...."<br />
OK<br />
AT+COPS<br />
OK<br />
</pre><br />
<br />
==== Answering an incoming call ====<br />
<pre><br />
RING<br />
ATA<br />
OK<br />
</pre><br />
<br />
==== Dialling an outgoing call ====<br />
<br />
To actually be able to talk you have to configure your audio accordingly<br />
<br />
<pre><br />
root@fic-gta01:~$ cd /etc/alsa/<br />
root@fic-gta01:/etc/alsa$ wget http://opensource.wolfsonmicro.com/~gg/gsmheadset.working.state<br />
root@fic-gta01:/etc/alsa$ alsactl -f /etc/alsa/gsmheadset.working.state restore<br />
</pre><br />
<br />
Up the "Amp right" volume to hear the speaker on both ears, then dial<br />
<br />
<pre><br />
ATD012340234;<br />
</pre><br />
<br />
==== Hanging up ====<br />
<pre><br />
ATH<br />
OK<br />
</pre><br />
<br />
=== Using [[gsmd]] ===<br />
<br />
You can use the [[gsmd]] and [[libgsmd-util]] programs to have a slightly more high-level interface to the GSM Modem. It's still console based, though.<br />
<br />
For further instructions, see [[gsmd]]</div>DanielWillmannhttp://wiki.openmoko.org/wiki/FAQFAQ2007-03-09T01:56:11Z<p>DanielWillmann: /* Q: Why are there wires on the debug board that lead to no other part? */ Add 'A:' to the answer</p>
<hr />
<div>Questions and Answers that don't seem to fit elsewhere<br />
<br />
==Introduction== <br />
<br />
=== Q: What is OpenMoko and Neo1973? ===<br />
A: [[OpenMoko]] is a software platform, an attempt to create the world's first completely open mobile phone software stack. The [[FIC]] [[Neo1973]] is the first fully supported OpenMoko phone.<br />
<br />
=== Q: When can I buy a Neo1973? ===<br />
<br />
A: Late March for developers, September for mass market - See [[Neo1973]] for most up to date information. Neo1973 will be shipped worldwide. There also will be shipping from EU.<br />
To be informed when it is available, subscribe to [http://lists.openmoko.org/mailman/listinfo/announce the mailing list announce].<br />
<br />
=== Q: How much? === <br />
<br />
A: $350 for the Developer's Kit - Phase 1. Includes:<br />
<ul><br />
<li>Neo1973 phone</li><br />
<li>Battery</li><br />
<li>Headset</li><br />
<li>Compact charger</li><br />
<li>Carrying case</li><br />
<li>Stylus</li><br />
<li>Lanyard</li><br />
<li>512 MB MicroSD card</li><br />
<li>USB connectivity cable</li><br />
<li>Instruction manual and warranty</li><br />
</ul><br />
<br />
$75 for the Car Kit. Includes:<br />
<ul><br />
<li>Windshield mount and device holder</li><br />
<li>Car charger</li><br />
<li>External antenna</li><br />
</ul><br />
<br />
$200 for the Hacker's Lunchbox. Includes:<br />
<ul><br />
<li>Development/[[Debug Board]]</li><br />
<li>Battery</li><br />
<li>Compact charger for development board</li><br />
<li>FPC (to connect to the jtag port)</li><br />
<li>Shoulder strap</li><br />
<li>Debug cable (USB)</li><br />
</ul><br />
<br />
=== Q: What will it do? ===<br />
<br />
A: The Phase 1 phone available in late March is for developers only. It is not suitable for end users, it will have basic functionality as a touchscreen phone. Little else will work, software development will continue till mass market release.<br />
<br />
Those interested should:<br />
<br />
* Know that there will be a device with faster cpu, gsm system etc. 6 months later<br />
* Have fun hacking devices.<br />
* Be able to find their way through prototype software and hardware without much documentation.<br />
* Share the dream of a device powered by free software.<br />
* Not expect a consumer-level device.<br />
* Come up with new ideas for exploring the age of mobile computing.<br />
* Have $350.<br />
<br />
Ideally they also:<br />
<br />
* Can spot bugs and submit patches.<br />
* Love to cooperate with a community improving the software.<br />
<br />
==Software==<br />
<br />
=== Q: Is there description and list of OpenMoko software? ===<br />
<br />
A: See [[OpenMoko]]<br />
<br />
=== Q: How do I install and manage software on OpenMoko? ===<br />
<br />
A: ipkg: http://handhelds.org/moin/moin.cgi/Ipkg<br />
<br />
=== Q: How can I compile programs for the Neo1973? ===<br />
<br />
A: See [[Toolchain]].<br />
<br />
=== Q: Is there an emulator available for OpenMoko? ===<br />
<br />
*XorA guesses that if your first question is "is there an emulator"<br />
then you're not actually ever going to do dev work :-)<br />
<br />
====QEMU====<br />
QEMU is a good place to start, and we should be able to run almost all OpenMoko<br />
apps with it. For a good start with the QEMU emulator visit:<br />
http://www.aurel32.net/info/debian_arm_qemu.php<br />
<br />
[[User:Jebba|Jeff]] put together an image you can test under [http://fabrice.bellard.free.fr/qemu/ qemu], if you so desire:<br />
ftp://ftp.blagblagblag.org/pub/BLAG/developers/jebba/openmoko/<br />
<br />
OpenMoko has longer term plans to port the FIC machines to QEMU. For now MACHINE="qemuarm" can be used.<br />
<br />
====Xoo====<br />
Another is [http://projects.o-hand.com/xoo Xoo]. Koen says: "Xoo should be enough for most apps people will develop, since most don't need access to the gsm uart directly. If you're hardcore you could use qemu + xoo, but that still doesn't emulate all the hardware quirks (e.g. unaligned access)".<br />
<br />
Update: Stefan Schmidt has resized the Neo1973 Mock-up and written a small description for xoo. In his words:<br />
<br />
It's not really useable at all, as you need a really high screen resolution to fit the whole picture on your screen. And of course the dpi are wrong. Even no buttons because I can't remember where they are at the case.<br />
<br />
http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2<br />
<br />
Start with 'xoo --device /path/to/neo1973.xml'<br />
<br />
Some more details [[Getting_Openmoko_working_on_host_with_Xoo|here]].<br />
<br />
====Xephyr====<br />
Or use Xephyr directly with locally compiled programs (e.g. matchbox svn + openmoko):<br />
Xephyr -screen 480x640 -nolisten tcp -ac :1 &<br />
export DISPLAY=:1<br />
export LD_LIBRARY_PATH=/usr/local/lib<br />
matchbox-window-manager -display $DISPLAY -use_titlebar no \<br />
-use_super_modal yes -use_lowlight yes -use_dialog_mode static \<br />
-use_cursor yes &<br />
matchbox-panel --geometry=480x44 --end-applets=clock &<br />
openmoko-footer &<br />
openmoko-taskmanager &<br />
<br />
=== Q: Where can I find some type of tutorial for a 'Hello, world' on OpenMoko? ===<br />
<br />
A: This should get you started:<br />
http://www.gtk.org/tutorial/<br />
<br />
=== Q: Can PalmOS apps applications be ported to run on OpenMoko? ===<br />
<br />
A: Making legacy apps written for the "Garnet" OS (née "Palm OS") run on Linux<br />
is decidedly non-trivial. An emulator for this is going to be part of the<br />
ACCESS Linux Platform.<br />
<br />
PalmOS uses a very different model from Linux: it doesn't really have a concept of a file, ''per se''; instead, all memory is seen as a "soup" of records to access and manipulate (this isn't strictly true, as files had to be grafted on when removable flash was supported, but it's close enough, from a developer's standpoint). Also, the GUI toolkit looks very, very different from GTK. The result is that a very well-written, modular program that carefully separates its core algorithms from its user interface and data input and output can be ported by replacing those components. A program written by a mere mortal programmer is likely to have all these components intertwined to a point that a port will be challenging to say the least.<br />
<br />
The ACCESS Linux Platform will include POSE, an emulator that simulates a Palm device on a Linux host. This emulator has been around a long time; one expects that it will also run on OpenMoko, but this has to be considered a short-term bandaid rather than a long-term solution.<br />
<br />
=== Q: Does it have Java? ===<br />
A: It will have eventually, if you help us to get it working. Some good places to keep track of would be [http://projects.openmoko.org/projects/java-pkg/ projects.openmoko.org] and [https://phoneme.dev.java.net/ PhoneME].<br />
<br />
=== Q: What are the relevant X11 details? ===<br />
<br />
A: See [http://lists.openmoko.org/pipermail/community/2007-January/001353.html xdpyinfo output].<br />
<br />
=== Q: Does OpenMoko run on any other hardware? ===<br />
<br />
You can run it on your [[How_to_run_OpenMoko_Apps_on_PC|PC]]. There is work going on with [http://www.datenfreihafen.org/~stefan/weblog//archives/2007/02/#e2007-02-18T15_27_07.txt OpenEZX and HTC]. It's running on [http://dominion.kabel.utwente.nl/koen/cms/openmoko-running-on-an-ipaq iPaq hx4700].<br />
<br />
==Neo1973 Hardware== <br />
<br />
=== Q: What are the dimensions? ===<br />
<br />
A: 120.7 x 62 x 18.5 mm, It would fit entirely in a coke can. (4.75 * 2.4 * 0.72 ")<br />
<br />
=== Q: How heavy is it? ===<br />
<br />
A: 185g, (6.5 ounces).<br />
<br />
=== Q: Does it have a camera? ===<br />
<br />
A: No, see [[Neo1973 Hardware]] for details on what it does include (and [[Wish List - Hardware]] for what some want in the future.) See also [[FAQ#USB]].<br />
<br />
=== Q: What is the rationale behind the exclusion of WiFi? ===<br />
<br />
A: No suitable low power open source WiFi device was available when the Neo1973 was designed. A closed source WiFi device would have been restrictive for developers and users alike. See also [[FAQ#USB]].<br />
<br />
See also:<br />
[[Sean Moss-Pultz]]'s [http://lists.openmoko.org/pipermail/community/2006-November/000050.html comment on this]<br />
<br />
=== Q: Does it have bluetooth? ===<br />
<br />
A: Yes!<br />
<br />
=== Q: Does it come with a stylus? ===<br />
<br />
A: Yes, but there's no holder for it on the phone.<br />
<br />
=== Q: How do I input text? ===<br />
<br />
A: Use provided keyboard app.<br />
<br />
A: Use Bluetooth keyboard.<br />
<br />
A: For more methods and ideas see [[Wishlist:Text_Input]].<br />
<br />
=== Q: Can I record calls and/or play audio files in calls? ===<br />
<br />
A: Yes, audio path from GSM to/from mic and speakers is completely controllable by user. For example recording calls (both sides) and implementing answering machine is possible. Also using text->speech should be possible or modifying outgoing voice. Currently there is no software bundled in phone to do this.<br />
<br />
=== Q: What is the battery life? ===<br />
<br />
A: There has been no word on this so far, but see [[Neo1973 Power Management#Approximate_power_draw_of_various_subsystems|these estimates]] for a rough idea. More information about the battery [[Neo1973 Battery|here]].<br />
<br />
=== USB ===<br />
<br />
==== Q: What can I do with the USB port on the Neo1973? ====<br />
A: Charge the phone, communicate with it over USB-serial, or USB-networking.<br />
<br />
A: Plug external devices, such as wifi, cameras, or mass-storage devices in.<br />
<br />
==== Q: What can't I do with the USB? ====<br />
<br />
The USB on the neo has no power output. This means that you cannot use USB bus powered devices without some sort of powered hub or cable.<br />
This is due to the fact that adding a 5V power supply into the device would have added complexity, volume and cost.<br />
<br />
==== Q: Why is only USB 1.1 provided? ====<br />
<br />
A: The processor has USB 1.1 built in. One with USB2 built in would have been more expensive.<br />
<br />
==== Q: Can the Neo charge and use devices on a USB hub at the same time? ====<br />
<br />
A: <br />
*When the Neo is connected to a device port on a USB hub, it will start charging. If the hub is a powered hub, then it will charge fast (3h), otherwise around 12h.<br />
<br />
*If you plug the Neo into the host port of a USB hub you can use devices on that hub but the Neo will not charge. (Some/many USB hubs will not accept an unpowered host as valid, hence the need for the below cable.)<br />
*This is because the host socket on USB hubs is not powered.<br />
<br />
FIC product development is looking into providing something that<br />
conveniently solves this problem.<br />
<br />
The USB port on the Neo is not a properly compliant USB host port, all USB host ports must provide 5V - though powered devices or hubs may not draw any current from this, they may refuse to work. (The Belkin Tetrahub is an example of a hub that will not work.)<br />
<br />
One solution is a three headed cable.<br />
<br />
One end plugs into the Neo. One end plugs into a device port of a powered hub, or the Neo charger. One end plugs into the host port of a hub.<br />
<br />
The Charger/USB device plug only has +5V and 0V connected in the simple cable, which are connected to the other ends.<br />
<br />
For a more complex cable, when the host socket is not plugged in, the cable acts as a simple USB cable.<br />
<br />
==== Q: What are the details of the USB port on the Neo1973? How does it compare to USB On-The-Go? ====<br />
<br />
A: The Neo1973 will have mini-USB-B, and will be able to function as either a host or a device. It will NOT be USB On-The-Go. OTG is a complex specification, and it comprises way more than just<br />
a AB socket, but also electrical and software components which cannot be provide by the S3C2410.<br />
<br />
You will need a special Mini-B to regular-B cable (note that this won't actually comply with the USB standard: a compliant cable has to have an A or Mini-A plug on one end, and B or Mini-B on the other).<br />
<br />
=== Q: Are there any LEDs on the Neo 1973? ===<br />
<br />
A: The Neo1973 v1 will have no LEDs besides the screen backlight.<br />
<br />
=== Q: Will a JTAG port be made available? ===<br />
<br />
A: The "Hacker's Lunchbox" will make this kind of stuff easy. <br />
<br />
It is currently assumed that the "Hacker's Lunchbox" will contain the [[Debug Board]]. [[Connecting Neo1973 with Debug Board v2]] explains how to connect it to the phone.<br />
<br />
=== Q: What can we expect in future versions? ===<br />
<br />
A: A faster CPU, faster GSM (EDGE?) perhaps even powered USB port, USB2, wifi, and camera. None of the details have been released yet. More details of hardware upgrades should be available sometime in May. There will also be 5 more OpenMoko devices - some not phones in the traditional sense announced by FIC in September.<br />
<br />
==Networking/Connectivity==<br />
<br />
=== Q: Can I bridge to an Ethernet (wired or unwired) network via a suitable Bluetooth enabled router? ===<br />
<br />
A: Yes - see [http://gentoo-wiki.com/HOWTO_Configure_a_bluetooth_network_access_point this howto for how to configure a linux computer to act as such a router] and [[Bluetooth Support]].<br />
<br />
=== Q: What providers in the USA provide the GSM required for Neo 1973? ===<br />
<br />
A: Wikipedia has a list of providers and technologies [http://en.wikipedia.org/wiki/List_of_United_States_mobile_phone_companies here]. A brief look gives the impression that [http://www.t-mobile.com T-Mobile] and [http://www.cingular.com Cingular] (which is<br />
renaming itself AT&T) seem to be the only major ones.<br />
<br />
=== Q: Will OpenMoko "Just Work" with Mac OS X? ===<br />
<br />
A: There has been some discussion of this on the mailing list. There is motivation, and there are interested developers. <br />
Not being a Mac OS X user, I don't know enough<br />
to summarize the discussion to answer this question. Can someone please fill in?<br />
<br />
A: For IP over USB cable connectivity, it is planned to improve/adapt the AJZaurusUSB driver, allowing ssh into the OpenMoko.<br />
<br />
A: It is expected that (Bluetooth/UB) SyncML based interoperation for<br />
contacts and events can easily be achieved by a patch<br />
to the Apple iSync configuration tables.<br />
<br />
A: There is an open source implementation of Cocoa (GNUstep) that aims to run MacOS X compatible applications (sort of<br />
PPC/x86/ARM universal binaries) on OpenMoko devices: mySTEP.<br />
<br />
==Misc==<br />
<br />
=== Q: On the lists on lists.openmoko.org, should replies be added above or below the original text? ===<br />
<br />
A: Please reply UNDER post.<br />
<br />
=== Q: How can I find out if a question or topic has already been discussed on the mailing lists? ===<br />
<br />
A: By searching the mailing list archives. For example, using Google searches:<br />
<br />
site:openmoko.org text<br />
<br />
For example, to search for accelerometer:<br />
<br />
site:openmoko.org accelerometer<br />
<br />
If you only want to read the "official" mails from FIC people or from OpenMoko people:<br />
<br />
site:openmoko.org text "at fic.com.tw"<br />
site:openmoko.org text "at openmoko.org"<br />
<br />
For example to search for "release date" from FIC people:<br />
<br />
site:openmoko.org "release date" "at fic.com.tw"<br />
<br />
Alternatively you can use the [http://www.google.com/coop/cse?cx=017507431580478583395%3Astsl7lhxzbc custom OpenMoko search engine] which has been created using [http://www.google.com/coop/ Google Co-op].<br />
<br />
=== Q: Why are there wires on the debug board that lead to no other part? ===<br />
<br />
A: They are for capacitance/inductance measurements to verify the dielectric constant of the PCB material.<br />
<br />
<br />
{{Languages|FAQ}}</div>DanielWillmannhttp://wiki.openmoko.org/wiki/FAQFAQ2007-03-09T01:55:00Z<p>DanielWillmann: /* Q: Why are there wires on the debug board that lead to no other part? */ Add answer from LaF0rge</p>
<hr />
<div>Questions and Answers that don't seem to fit elsewhere<br />
<br />
==Introduction== <br />
<br />
=== Q: What is OpenMoko and Neo1973? ===<br />
A: [[OpenMoko]] is a software platform, an attempt to create the world's first completely open mobile phone software stack. The [[FIC]] [[Neo1973]] is the first fully supported OpenMoko phone.<br />
<br />
=== Q: When can I buy a Neo1973? ===<br />
<br />
A: Late March for developers, September for mass market - See [[Neo1973]] for most up to date information. Neo1973 will be shipped worldwide. There also will be shipping from EU.<br />
To be informed when it is available, subscribe to [http://lists.openmoko.org/mailman/listinfo/announce the mailing list announce].<br />
<br />
=== Q: How much? === <br />
<br />
A: $350 for the Developer's Kit - Phase 1. Includes:<br />
<ul><br />
<li>Neo1973 phone</li><br />
<li>Battery</li><br />
<li>Headset</li><br />
<li>Compact charger</li><br />
<li>Carrying case</li><br />
<li>Stylus</li><br />
<li>Lanyard</li><br />
<li>512 MB MicroSD card</li><br />
<li>USB connectivity cable</li><br />
<li>Instruction manual and warranty</li><br />
</ul><br />
<br />
$75 for the Car Kit. Includes:<br />
<ul><br />
<li>Windshield mount and device holder</li><br />
<li>Car charger</li><br />
<li>External antenna</li><br />
</ul><br />
<br />
$200 for the Hacker's Lunchbox. Includes:<br />
<ul><br />
<li>Development/[[Debug Board]]</li><br />
<li>Battery</li><br />
<li>Compact charger for development board</li><br />
<li>FPC (to connect to the jtag port)</li><br />
<li>Shoulder strap</li><br />
<li>Debug cable (USB)</li><br />
</ul><br />
<br />
=== Q: What will it do? ===<br />
<br />
A: The Phase 1 phone available in late March is for developers only. It is not suitable for end users, it will have basic functionality as a touchscreen phone. Little else will work, software development will continue till mass market release.<br />
<br />
Those interested should:<br />
<br />
* Know that there will be a device with faster cpu, gsm system etc. 6 months later<br />
* Have fun hacking devices.<br />
* Be able to find their way through prototype software and hardware without much documentation.<br />
* Share the dream of a device powered by free software.<br />
* Not expect a consumer-level device.<br />
* Come up with new ideas for exploring the age of mobile computing.<br />
* Have $350.<br />
<br />
Ideally they also:<br />
<br />
* Can spot bugs and submit patches.<br />
* Love to cooperate with a community improving the software.<br />
<br />
==Software==<br />
<br />
=== Q: Is there description and list of OpenMoko software? ===<br />
<br />
A: See [[OpenMoko]]<br />
<br />
=== Q: How do I install and manage software on OpenMoko? ===<br />
<br />
A: ipkg: http://handhelds.org/moin/moin.cgi/Ipkg<br />
<br />
=== Q: How can I compile programs for the Neo1973? ===<br />
<br />
A: See [[Toolchain]].<br />
<br />
=== Q: Is there an emulator available for OpenMoko? ===<br />
<br />
*XorA guesses that if your first question is "is there an emulator"<br />
then you're not actually ever going to do dev work :-)<br />
<br />
====QEMU====<br />
QEMU is a good place to start, and we should be able to run almost all OpenMoko<br />
apps with it. For a good start with the QEMU emulator visit:<br />
http://www.aurel32.net/info/debian_arm_qemu.php<br />
<br />
[[User:Jebba|Jeff]] put together an image you can test under [http://fabrice.bellard.free.fr/qemu/ qemu], if you so desire:<br />
ftp://ftp.blagblagblag.org/pub/BLAG/developers/jebba/openmoko/<br />
<br />
OpenMoko has longer term plans to port the FIC machines to QEMU. For now MACHINE="qemuarm" can be used.<br />
<br />
====Xoo====<br />
Another is [http://projects.o-hand.com/xoo Xoo]. Koen says: "Xoo should be enough for most apps people will develop, since most don't need access to the gsm uart directly. If you're hardcore you could use qemu + xoo, but that still doesn't emulate all the hardware quirks (e.g. unaligned access)".<br />
<br />
Update: Stefan Schmidt has resized the Neo1973 Mock-up and written a small description for xoo. In his words:<br />
<br />
It's not really useable at all, as you need a really high screen resolution to fit the whole picture on your screen. And of course the dpi are wrong. Even no buttons because I can't remember where they are at the case.<br />
<br />
http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2<br />
<br />
Start with 'xoo --device /path/to/neo1973.xml'<br />
<br />
Some more details [[Getting_Openmoko_working_on_host_with_Xoo|here]].<br />
<br />
====Xephyr====<br />
Or use Xephyr directly with locally compiled programs (e.g. matchbox svn + openmoko):<br />
Xephyr -screen 480x640 -nolisten tcp -ac :1 &<br />
export DISPLAY=:1<br />
export LD_LIBRARY_PATH=/usr/local/lib<br />
matchbox-window-manager -display $DISPLAY -use_titlebar no \<br />
-use_super_modal yes -use_lowlight yes -use_dialog_mode static \<br />
-use_cursor yes &<br />
matchbox-panel --geometry=480x44 --end-applets=clock &<br />
openmoko-footer &<br />
openmoko-taskmanager &<br />
<br />
=== Q: Where can I find some type of tutorial for a 'Hello, world' on OpenMoko? ===<br />
<br />
A: This should get you started:<br />
http://www.gtk.org/tutorial/<br />
<br />
=== Q: Can PalmOS apps applications be ported to run on OpenMoko? ===<br />
<br />
A: Making legacy apps written for the "Garnet" OS (née "Palm OS") run on Linux<br />
is decidedly non-trivial. An emulator for this is going to be part of the<br />
ACCESS Linux Platform.<br />
<br />
PalmOS uses a very different model from Linux: it doesn't really have a concept of a file, ''per se''; instead, all memory is seen as a "soup" of records to access and manipulate (this isn't strictly true, as files had to be grafted on when removable flash was supported, but it's close enough, from a developer's standpoint). Also, the GUI toolkit looks very, very different from GTK. The result is that a very well-written, modular program that carefully separates its core algorithms from its user interface and data input and output can be ported by replacing those components. A program written by a mere mortal programmer is likely to have all these components intertwined to a point that a port will be challenging to say the least.<br />
<br />
The ACCESS Linux Platform will include POSE, an emulator that simulates a Palm device on a Linux host. This emulator has been around a long time; one expects that it will also run on OpenMoko, but this has to be considered a short-term bandaid rather than a long-term solution.<br />
<br />
=== Q: Does it have Java? ===<br />
A: It will have eventually, if you help us to get it working. Some good places to keep track of would be [http://projects.openmoko.org/projects/java-pkg/ projects.openmoko.org] and [https://phoneme.dev.java.net/ PhoneME].<br />
<br />
=== Q: What are the relevant X11 details? ===<br />
<br />
A: See [http://lists.openmoko.org/pipermail/community/2007-January/001353.html xdpyinfo output].<br />
<br />
=== Q: Does OpenMoko run on any other hardware? ===<br />
<br />
You can run it on your [[How_to_run_OpenMoko_Apps_on_PC|PC]]. There is work going on with [http://www.datenfreihafen.org/~stefan/weblog//archives/2007/02/#e2007-02-18T15_27_07.txt OpenEZX and HTC]. It's running on [http://dominion.kabel.utwente.nl/koen/cms/openmoko-running-on-an-ipaq iPaq hx4700].<br />
<br />
==Neo1973 Hardware== <br />
<br />
=== Q: What are the dimensions? ===<br />
<br />
A: 120.7 x 62 x 18.5 mm, It would fit entirely in a coke can. (4.75 * 2.4 * 0.72 ")<br />
<br />
=== Q: How heavy is it? ===<br />
<br />
A: 185g, (6.5 ounces).<br />
<br />
=== Q: Does it have a camera? ===<br />
<br />
A: No, see [[Neo1973 Hardware]] for details on what it does include (and [[Wish List - Hardware]] for what some want in the future.) See also [[FAQ#USB]].<br />
<br />
=== Q: What is the rationale behind the exclusion of WiFi? ===<br />
<br />
A: No suitable low power open source WiFi device was available when the Neo1973 was designed. A closed source WiFi device would have been restrictive for developers and users alike. See also [[FAQ#USB]].<br />
<br />
See also:<br />
[[Sean Moss-Pultz]]'s [http://lists.openmoko.org/pipermail/community/2006-November/000050.html comment on this]<br />
<br />
=== Q: Does it have bluetooth? ===<br />
<br />
A: Yes!<br />
<br />
=== Q: Does it come with a stylus? ===<br />
<br />
A: Yes, but there's no holder for it on the phone.<br />
<br />
=== Q: How do I input text? ===<br />
<br />
A: Use provided keyboard app.<br />
<br />
A: Use Bluetooth keyboard.<br />
<br />
A: For more methods and ideas see [[Wishlist:Text_Input]].<br />
<br />
=== Q: Can I record calls and/or play audio files in calls? ===<br />
<br />
A: Yes, audio path from GSM to/from mic and speakers is completely controllable by user. For example recording calls (both sides) and implementing answering machine is possible. Also using text->speech should be possible or modifying outgoing voice. Currently there is no software bundled in phone to do this.<br />
<br />
=== Q: What is the battery life? ===<br />
<br />
A: There has been no word on this so far, but see [[Neo1973 Power Management#Approximate_power_draw_of_various_subsystems|these estimates]] for a rough idea. More information about the battery [[Neo1973 Battery|here]].<br />
<br />
=== USB ===<br />
<br />
==== Q: What can I do with the USB port on the Neo1973? ====<br />
A: Charge the phone, communicate with it over USB-serial, or USB-networking.<br />
<br />
A: Plug external devices, such as wifi, cameras, or mass-storage devices in.<br />
<br />
==== Q: What can't I do with the USB? ====<br />
<br />
The USB on the neo has no power output. This means that you cannot use USB bus powered devices without some sort of powered hub or cable.<br />
This is due to the fact that adding a 5V power supply into the device would have added complexity, volume and cost.<br />
<br />
==== Q: Why is only USB 1.1 provided? ====<br />
<br />
A: The processor has USB 1.1 built in. One with USB2 built in would have been more expensive.<br />
<br />
==== Q: Can the Neo charge and use devices on a USB hub at the same time? ====<br />
<br />
A: <br />
*When the Neo is connected to a device port on a USB hub, it will start charging. If the hub is a powered hub, then it will charge fast (3h), otherwise around 12h.<br />
<br />
*If you plug the Neo into the host port of a USB hub you can use devices on that hub but the Neo will not charge. (Some/many USB hubs will not accept an unpowered host as valid, hence the need for the below cable.)<br />
*This is because the host socket on USB hubs is not powered.<br />
<br />
FIC product development is looking into providing something that<br />
conveniently solves this problem.<br />
<br />
The USB port on the Neo is not a properly compliant USB host port, all USB host ports must provide 5V - though powered devices or hubs may not draw any current from this, they may refuse to work. (The Belkin Tetrahub is an example of a hub that will not work.)<br />
<br />
One solution is a three headed cable.<br />
<br />
One end plugs into the Neo. One end plugs into a device port of a powered hub, or the Neo charger. One end plugs into the host port of a hub.<br />
<br />
The Charger/USB device plug only has +5V and 0V connected in the simple cable, which are connected to the other ends.<br />
<br />
For a more complex cable, when the host socket is not plugged in, the cable acts as a simple USB cable.<br />
<br />
==== Q: What are the details of the USB port on the Neo1973? How does it compare to USB On-The-Go? ====<br />
<br />
A: The Neo1973 will have mini-USB-B, and will be able to function as either a host or a device. It will NOT be USB On-The-Go. OTG is a complex specification, and it comprises way more than just<br />
a AB socket, but also electrical and software components which cannot be provide by the S3C2410.<br />
<br />
You will need a special Mini-B to regular-B cable (note that this won't actually comply with the USB standard: a compliant cable has to have an A or Mini-A plug on one end, and B or Mini-B on the other).<br />
<br />
=== Q: Are there any LEDs on the Neo 1973? ===<br />
<br />
A: The Neo1973 v1 will have no LEDs besides the screen backlight.<br />
<br />
=== Q: Will a JTAG port be made available? ===<br />
<br />
A: The "Hacker's Lunchbox" will make this kind of stuff easy. <br />
<br />
It is currently assumed that the "Hacker's Lunchbox" will contain the [[Debug Board]]. [[Connecting Neo1973 with Debug Board v2]] explains how to connect it to the phone.<br />
<br />
=== Q: What can we expect in future versions? ===<br />
<br />
A: A faster CPU, faster GSM (EDGE?) perhaps even powered USB port, USB2, wifi, and camera. None of the details have been released yet. More details of hardware upgrades should be available sometime in May. There will also be 5 more OpenMoko devices - some not phones in the traditional sense announced by FIC in September.<br />
<br />
==Networking/Connectivity==<br />
<br />
=== Q: Can I bridge to an Ethernet (wired or unwired) network via a suitable Bluetooth enabled router? ===<br />
<br />
A: Yes - see [http://gentoo-wiki.com/HOWTO_Configure_a_bluetooth_network_access_point this howto for how to configure a linux computer to act as such a router] and [[Bluetooth Support]].<br />
<br />
=== Q: What providers in the USA provide the GSM required for Neo 1973? ===<br />
<br />
A: Wikipedia has a list of providers and technologies [http://en.wikipedia.org/wiki/List_of_United_States_mobile_phone_companies here]. A brief look gives the impression that [http://www.t-mobile.com T-Mobile] and [http://www.cingular.com Cingular] (which is<br />
renaming itself AT&T) seem to be the only major ones.<br />
<br />
=== Q: Will OpenMoko "Just Work" with Mac OS X? ===<br />
<br />
A: There has been some discussion of this on the mailing list. There is motivation, and there are interested developers. <br />
Not being a Mac OS X user, I don't know enough<br />
to summarize the discussion to answer this question. Can someone please fill in?<br />
<br />
A: For IP over USB cable connectivity, it is planned to improve/adapt the AJZaurusUSB driver, allowing ssh into the OpenMoko.<br />
<br />
A: It is expected that (Bluetooth/UB) SyncML based interoperation for<br />
contacts and events can easily be achieved by a patch<br />
to the Apple iSync configuration tables.<br />
<br />
A: There is an open source implementation of Cocoa (GNUstep) that aims to run MacOS X compatible applications (sort of<br />
PPC/x86/ARM universal binaries) on OpenMoko devices: mySTEP.<br />
<br />
==Misc==<br />
<br />
=== Q: On the lists on lists.openmoko.org, should replies be added above or below the original text? ===<br />
<br />
A: Please reply UNDER post.<br />
<br />
=== Q: How can I find out if a question or topic has already been discussed on the mailing lists? ===<br />
<br />
A: By searching the mailing list archives. For example, using Google searches:<br />
<br />
site:openmoko.org text<br />
<br />
For example, to search for accelerometer:<br />
<br />
site:openmoko.org accelerometer<br />
<br />
If you only want to read the "official" mails from FIC people or from OpenMoko people:<br />
<br />
site:openmoko.org text "at fic.com.tw"<br />
site:openmoko.org text "at openmoko.org"<br />
<br />
For example to search for "release date" from FIC people:<br />
<br />
site:openmoko.org "release date" "at fic.com.tw"<br />
<br />
Alternatively you can use the [http://www.google.com/coop/cse?cx=017507431580478583395%3Astsl7lhxzbc custom OpenMoko search engine] which has been created using [http://www.google.com/coop/ Google Co-op].<br />
<br />
=== Q: Why are there wires on the debug board that lead to no other part? ===<br />
<br />
They are for capacitance/inductance measurements to verify the dielectric constant of the PCB material.<br />
<br />
<br />
{{Languages|FAQ}}</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Manually_using_BluetoothManually using Bluetooth2007-03-07T23:26:01Z<p>DanielWillmann: /* Networking */ Detailled description</p>
<hr />
<div>At the moment, we've just started to introduce Bluetooth into our [[Neo1973 Hardware]].<br />
<br />
We have quite a lot of plans about what exactly Bluetooth should be used for.<br />
<br />
== Bluetooth Functions ==<br />
<br />
=== HID (Human Input Device) ===<br />
<br />
==== Being able to use HID devices ====<br />
<br />
We want to be able to use a bluetooth keyboard to type into the various applications of our Neo1973.<br />
<br />
<br />
==== Acting as HID device ====<br />
<br />
We want to be able to use the Neo1973 as a HID device, being able to use it as controller for presentations.<br />
<br />
=== OBEX ===<br />
<br />
=== Networking ===<br />
<br />
Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.<br />
<br />
On the laptop:<br />
* Start bluetooth<br />
elara /home/alphaone # /etc/init.d/bluetooth start<br />
<br />
* Start pand as server<br />
elara /home/alphaone # pand -s<br />
<br />
* As soon as pand is started on the phone configure your IP address<br />
elara /home/alphaone # ip a add 10.0.0.1/24 dev bnep0<br />
elara /home/alphaone # ip l set bnep0 up<br />
<br />
* Configure IP forwarding and masquerading to your liking<br />
<br />
On the phone:<br />
* Insert the module and power up bluetooth<br />
root@fic-gta01:~$ modprobe gta01-pm-bt<br />
root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on <br />
<br />
* Scan for the laptop<br />
root@fic-gta01:~$ hcitool scan<br />
Scanning ...<br />
00:0E:6D:C0:0l:6A Sho<br />
00:20:E0:5A:FE:C8 BlueZ (0)<br />
<br />
* Connect to the laptop pand<br />
root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8<br />
<br />
* Configure your IP address<br />
ip a add 10.0.0.2/24 dev bnep0<br />
ip r add default via 10.0.0.1<br />
<br />
* Enjoy<br />
root@fic-gta01:~$ wget http://www-public.tu-bs.de:8080/~y0019680/tmp/thereisnophone.mp3 <br />
Connecting to www-public.tu-bs.de[134.169.9.108]:8080<br />
thereisnophone.mp3 100****************************************************| 266 KB 00:00:00 ETA<br />
root@fic-gta01:~$ madplay thereisnophone.mp3 <br />
MPEG Audio Decoder 0.15.2 (beta) - Copyright (C) 2000-2004 Robert Leslie et al.<br />
630 frames decoded (0:00:22.6), -0.9 dB peak amplitude, 0 clipped samples<br />
<br />
=== A2DP ===<br />
<br />
<br />
== Further reading ==<br />
<br />
http://www.holtmann.org/papers/bluetooth/ols2006_slides.pdf<br />
http://wiki.bluez.org/wiki/Audio#org.bluez.Audio</div>DanielWillmannhttp://wiki.openmoko.org/wiki/FAQFAQ2007-03-07T22:56:30Z<p>DanielWillmann: /* Misc */</p>
<hr />
<div>Questions and Answers that don't seem to fit elsewhere<br />
<br />
==Introduction== <br />
<br />
=== Q: What is OpenMoko and Neo1973? ===<br />
A: [[OpenMoko]] is a software platform, an attempt to create the world's first completely open mobile phone software stack. The [[FIC]] [[Neo1973]] is the first fully supported OpenMoko phone.<br />
<br />
=== Q: When can I buy a Neo1973? ===<br />
<br />
A: Late March for developers, September for mass market - See [[Neo1973]] for most up to date information. <br />
To be informed when it is available, subscribe to [http://lists.openmoko.org/mailman/listinfo/announce the mailing list announce].<br />
<br />
=== Q: How much? === <br />
<br />
A: $350 for the Developer's Kit - Phase 1. Includes:<br />
<ul><br />
<li>Neo1973 phone</li><br />
<li>Battery</li><br />
<li>Headset</li><br />
<li>Compact charger</li><br />
<li>Carrying case</li><br />
<li>Stylus</li><br />
<li>Lanyard</li><br />
<li>512 MB MicroSD card</li><br />
<li>USB connectivity cable</li><br />
<li>Instruction manual and warranty</li><br />
</ul><br />
<br />
$75 for the Car Kit. Includes:<br />
<ul><br />
<li>Windshield mount and device holder</li><br />
<li>Car charger</li><br />
<li>External antenna</li><br />
</ul><br />
<br />
$200 for the Hacker's Lunchbox. Includes:<br />
<ul><br />
<li>Development board</li><br />
<li>Battery</li><br />
<li>Compact charger for development board</li><br />
<li>FPC (to connect to the jtag port)</li><br />
<li>Shoulder strap</li><br />
<li>Debug cable (USB)</li><br />
</ul><br />
<br />
=== Q: What will it do? ===<br />
<br />
A: The Phase 1 phone available in late March is for developers only. It is not suitable for end users, it will have basic functionality as a touchscreen phone. Little else will work, software development will continue till mass market release.<br />
<br />
Those interested should:<br />
<br />
* Know that there will be a device with faster cpu, gsm system etc. 6 months later<br />
* Have fun hacking devices.<br />
* Be able to find their way through prototype software and hardware without much documentation.<br />
* Share the dream of a device powered by free software.<br />
* Not expect a consumer-level device.<br />
* Come up with new ideas for exploring the age of mobile computing.<br />
* Have $350.<br />
<br />
Ideally they also:<br />
<br />
* Can spot bugs and submit patches.<br />
* Love to cooperate with a community improving the software.<br />
<br />
==Software==<br />
<br />
=== Q: Is there description and list of OpenMoko software? ===<br />
<br />
A: See [[OpenMoko]]<br />
<br />
=== Q: How do I install and manage software on OpenMoko? ===<br />
<br />
A: ipkg: http://handhelds.org/moin/moin.cgi/Ipkg<br />
<br />
=== Q: How can I compile programs for the Neo1973? ===<br />
<br />
A: See [[Toolchain]].<br />
<br />
=== Q: Is there an emulator available for OpenMoko? ===<br />
<br />
*XorA guesses that if your first question is "is there an emulator"<br />
then you're not actually ever going to do dev work :-)<br />
<br />
====QEMU====<br />
QEMU is a good place to start, and we should be able to run almost all OpenMoko<br />
apps with it. For a good start with the QEMU emulator visit:<br />
http://www.aurel32.net/info/debian_arm_qemu.php<br />
<br />
[[User:Jebba|Jeff]] put together an image you can test under [http://fabrice.bellard.free.fr/qemu/ qemu], if you so desire:<br />
ftp://ftp.blagblagblag.org/pub/BLAG/developers/jebba/openmoko/<br />
<br />
OpenMoko has longer term plans to port the FIC machines to QEMU. For now MACHINE="qemuarm" can be used.<br />
<br />
====Xoo====<br />
Another is [http://projects.o-hand.com/xoo Xoo]. Koen says: "Xoo should be enough for most apps people will develop, since most don't need access to the gsm uart directly. If you're hardcore you could use qemu + xoo, but that still doesn't emulate all the hardware quirks (e.g. unaligned access)".<br />
<br />
Update: Stefan Schmidt has resized the Neo1973 Mock-up and written a small description for xoo. In his words:<br />
<br />
It's not really useable at all, as you need a really high screen resolution to fit the whole picture on your screen. And of course the dpi are wrong. Even no buttons because I can't remember where they are at the case.<br />
<br />
http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2<br />
<br />
Start with 'xoo --device /path/to/neo1973.xml'<br />
<br />
Some more details [[Getting_Openmoko_working_on_host_with_Xoo|here]].<br />
<br />
====Xephyr====<br />
Or use Xephyr directly with locally compiled programs (e.g. matchbox svn + openmoko):<br />
Xephyr -screen 480x640 -nolisten tcp -ac :1 &<br />
export DISPLAY=:1<br />
export LD_LIBRARY_PATH=/usr/local/lib<br />
matchbox-window-manager -display $DISPLAY -use_titlebar no \<br />
-use_super_modal yes -use_lowlight yes -use_dialog_mode static \<br />
-use_cursor yes &<br />
matchbox-panel --geometry=480x44 --end-applets=clock &<br />
openmoko-footer &<br />
openmoko-taskmanager &<br />
<br />
=== Q: Where can I find some type of tutorial for a 'Hello, world' on OpenMoko? ===<br />
<br />
A: This should get you started:<br />
http://www.gtk.org/tutorial/<br />
<br />
=== Q: Can PalmOS apps applications be ported to run on OpenMoko? ===<br />
<br />
A: Making legacy apps written for the "Garnet" OS (née "Palm OS") run on Linux<br />
is decidedly non-trivial. An emulator for this is going to be part of the<br />
ACCESS Linux Platform.<br />
<br />
PalmOS uses a very different model from Linux: it doesn't really have a concept of a file, ''per se''; instead, all memory is seen as a "soup" of records to access and manipulate (this isn't strictly true, as files had to be grafted on when removable flash was supported, but it's close enough, from a developer's standpoint). Also, the GUI toolkit looks very, very different from GTK. The result is that a very well-written, modular program that carefully separates its core algorithms from its user interface and data input and output can be ported by replacing those components. A program written by a mere mortal programmer is likely to have all these components intertwined to a point that a port will be challenging to say the least.<br />
<br />
The ACCESS Linux Platform will include POSE, an emulator that simulates a Palm device on a Linux host. This emulator has been around a long time; one expects that it will also run on OpenMoko, but this has to be considered a short-term bandaid rather than a long-term solution.<br />
<br />
=== Q: Does it have Java? ===<br />
A: It will have eventually, if you help us to get it working. Some good places to keep track of would be [http://projects.openmoko.org/projects/java-pkg/ projects.openmoko.org] and [https://phoneme.dev.java.net/ PhoneME].<br />
<br />
=== Q: What are the relevant X11 details? ===<br />
<br />
A: See [http://lists.openmoko.org/pipermail/community/2007-January/001353.html xdpyinfo output].<br />
<br />
=== Q: Does OpenMoko run on any other hardware? ===<br />
<br />
You can run it on your [[How_to_run_OpenMoko_Apps_on_PC|PC]]. There is work going on with [http://www.datenfreihafen.org/~stefan/weblog//archives/2007/02/#e2007-02-18T15_27_07.txt OpenEZX and HTC]. It's running on [http://dominion.kabel.utwente.nl/koen/cms/openmoko-running-on-an-ipaq iPaq hx4700].<br />
<br />
==Neo1973 Hardware== <br />
<br />
=== Q: What are the dimensions? ===<br />
<br />
A: 120.7 x 62 x 18.5 mm, It would fit entirely in a coke can. (4.75 * 2.4 * 0.72 ")<br />
<br />
=== Q: How heavy is it? ===<br />
<br />
A: 185g, (6.5 ounces).<br />
<br />
=== Q: Does it have a camera? ===<br />
<br />
A: No, see [[Neo1973 Hardware]] for details on what it does include (and [[Wish List - Hardware]] for what some want in the future.) See also [[FAQ#USB]].<br />
<br />
=== Q: What is the rationale behind the exclusion of WiFi? ===<br />
<br />
A: No suitable low power open source WiFi device was available when the Neo1973 was designed. A closed source WiFi device would have been restrictive for developers and users alike. See also [[FAQ#USB]].<br />
<br />
See also:<br />
[[Sean Moss-Pultz]]'s [http://lists.openmoko.org/pipermail/community/2006-November/000050.html comment on this]<br />
<br />
=== Q: Does it have bluetooth? ===<br />
<br />
A: Yes!<br />
<br />
=== Q: Does it come with a stylus? ===<br />
<br />
A: Yes, but there's no holder for it on the phone.<br />
<br />
=== Q: What is the battery life? ===<br />
<br />
A: There has been no word on this so far, but see [[Neo1973 Power Management#Approximate_power_draw_of_various_subsystems|these estimates]] for a rough idea. More information about the battery [[Neo1973 Battery|here]].<br />
<br />
=== USB ===<br />
<br />
==== Q: What can I do with the USB port on the Neo1973? ====<br />
A: Charge the phone, communicate with it over USB-serial, or USB-networking.<br />
<br />
A: Plug external devices, such as wifi, cameras, or mass-storage devices in.<br />
<br />
==== Q: What can't I do with the USB? ====<br />
<br />
The USB on the neo has no power output. This means that you cannot use USB bus powered devices without some sort of powered hub or cable.<br />
This is due to the fact that adding a 5V power supply into the device would have added complexity, volume and cost.<br />
<br />
==== Q: Why is only USB 1.1 provided? ====<br />
<br />
A: The processor has USB 1.1 built in. One with USB2 built in would have been more expensive.<br />
<br />
==== Q: Can the Neo charge and use devices on a USB hub at the same time? ====<br />
<br />
A: <br />
*When the Neo is connected to a device port on a USB hub, it will start charging. If the hub is a powered hub, then it will charge fast (3h), otherwise around 12h.<br />
<br />
*If you plug the Neo into the host port of a USB hub you can use devices on that hub but the Neo will not charge. (Some/many USB hubs will not accept an unpowered host as valid, hence the need for the below cable.)<br />
*This is because the host socket on USB hubs is not powered.<br />
<br />
FIC product development is looking into providing something that<br />
conveniently solves this problem.<br />
<br />
The USB port on the Neo is not a properly compliant USB host port, all USB host ports must provide 5V - though powered devices or hubs may not draw any current from this, they may refuse to work. (The Belkin Tetrahub is an example of a hub that will not work.)<br />
<br />
One solution is a three headed cable.<br />
<br />
One end plugs into the Neo. One end plugs into a device port of a powered hub, or the Neo charger. One end plugs into the host port of a hub.<br />
<br />
The Charger/USB device plug only has +5V and 0V connected in the simple cable, which are connected to the other ends.<br />
<br />
For a more complex cable, when the host socket is not plugged in, the cable acts as a simple USB cable.<br />
<br />
==== Q: What are the details of the USB port on the Neo1973? How does it compare to USB On-The-Go? ====<br />
<br />
A: The Neo1973 will have mini-USB-B, and will be able to function as either a host or a device. It will NOT be USB On-The-Go. OTG is a complex specification, and it comprises way more than just<br />
a AB socket, but also electrical and software components which cannot be provide by the S3C2410.<br />
<br />
You will need a special Mini-B to regular-B cable (note that this won't actually comply with the USB standard: a compliant cable has to have an A or Mini-A plug on one end, and B or Mini-B on the other).<br />
<br />
=== Q: Are there any LEDs on the Neo 1973? ===<br />
<br />
A: The Neo1973 v1 will have no LEDs besides the screen backlight.<br />
<br />
=== Q: Will a JTAG port be made available? ===<br />
<br />
A: The "Hacker's Lunchbox" will make this kind of stuff easy. <br />
<br />
It is currently assumed that the "Hacker's Lunchbox" will contain the [[Debug Board]]. [[Connecting Neo1973 with Debug Board v2]] explains how to connect it to the phone.<br />
<br />
=== Q: What can we expect in future versions? ===<br />
<br />
A: A faster CPU, faster GSM (EDGE?) perhaps even powered USB port, USB2, wifi, and camera. None of the details have been released yet. More details of hardware upgrades should be available sometime in May. There will also be 5 more OpenMoko devices - some not phones in the traditional sense announced by FIC in September.<br />
<br />
==Networking/Connectivity==<br />
<br />
=== Q: Can I bridge to an Ethernet (wired or unwired) network via a suitable Bluetooth enabled router? ===<br />
<br />
A: Yes - see [http://gentoo-wiki.com/HOWTO_Configure_a_bluetooth_network_access_point this howto for how to configure a linux computer to act as such a router] and [[Bluetooth Support]].<br />
<br />
=== Q: What providers in the USA provide the GSM required for Neo 1973? ===<br />
<br />
A: Wikipedia has a list of providers and technologies [http://en.wikipedia.org/wiki/List_of_United_States_mobile_phone_companies here]. A brief look gives the impression that [http://www.t-mobile.com T-Mobile] and [http://www.cingular.com Cingular] (which is<br />
renaming itself AT&T) seem to be the only major ones.<br />
<br />
=== Q: Will OpenMoko "Just Work" with Mac OS X? ===<br />
<br />
A: There has been some discussion of this on the mailing list. There is motivation, and there are interested developers. <br />
Not being a Mac OS X user, I don't know enough<br />
to summarize the discussion to answer this question. Can someone please fill in?<br />
<br />
A: For IP over USB cable connectivity, it is planned to improve/adapt the AJZaurusUSB driver, allowing ssh into the OpenMoko.<br />
<br />
A: It is expected that (Bluetooth/UB) SyncML based interoperation for<br />
contacts and events can easily be achieved by a patch<br />
to the Apple iSync configuration tables.<br />
<br />
A: There is an open source implementation of Cocoa (GNUstep) that aims to run MacOS X compatible applications (sort of<br />
PPC/x86/ARM universal binaries) on OpenMoko devices: mySTEP.<br />
<br />
==Misc==<br />
<br />
=== Q: On the lists on lists.openmoko.org, should replies be added above or below the original text? ===<br />
<br />
A: Please reply UNDER post.<br />
<br />
=== Q: How can I find out if a question or topic has already been discussed on the mailing lists? ===<br />
<br />
A: By searching the mailing list archives. For example, using Google searches:<br />
<br />
site:openmoko.org text<br />
<br />
For example, to search for accelerometer:<br />
<br />
site:openmoko.org accelerometer<br />
<br />
If you only want to read the "official" mails from FIC people or from OpenMoko people:<br />
<br />
site:openmoko.org text "at fic.com.tw"<br />
site:openmoko.org text "at openmoko.org"<br />
<br />
For example to search for "release date" from FIC people:<br />
<br />
site:openmoko.org "release date" "at fic.com.tw"<br />
<br />
Alternatively you can use the [http://www.google.com/coop/cse?cx=017507431580478583395%3Astsl7lhxzbc custom OpenMoko search engine] which has been created using [http://www.google.com/coop/ Google Co-op].<br />
<br />
=== Q: Why are there wires on the debug board that lead to no other part? ===<br />
<br />
{{Languages|FAQ}}</div>DanielWillmannhttp://wiki.openmoko.org/wiki/Manually_using_GSMManually using GSM2007-03-07T16:00:17Z<p>DanielWillmann: /* Powering up the GSM Modem */</p>
<hr />
<div><br />
This is a short guide how to manually get GSM going.<br />
<br />
== Requirements ==<br />
<br />
* GTA01Bv2 or GTA01Bv3 with very recent u-boot bootloader, providing usbtty (serial over USB) support)<br />
* Do not connect any debug board!<br />
<br />
<br />
== Walk-Through ==<br />
<br />
=== Booting the system ===<br />
<br />
* Make sure the rootfs you use has 'auto usb0' in /etc/network/interfaces<br />
* Configure the host's usb0 interface to 192.168.0.200 netmask 255.255.255.0<br />
* ssh to root@192.168.0.201<br />
<br />
=== Disabling the getty ===<br />
<br />
Our default images all have a getty running on /dev/ttySAC0, please edit /etc/inittab and disable the getty on that port <br />
<br />
=== Powering up the GSM Modem ===<br />
<br />
* load the "gta01_pm_gsm.ko" kernel module<br />
root@fic-gta01:~$ modprobe gta01_pm_gsm<br />
* verify there is no getty or any other app running on /dev/ttySAC0 <br />
root@fic-gta01:~$ lsof | grep ttySAC0<br />
* power-up the GSM Modem<br />
root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-gsm.0/power_on<br />
* change permissions on ttySAC0<br />
root@fic-gta01:~$ chown uucp.uucp /dev/ttySAC0<br />
* access the GSM Modem UART<br />
<pre><br />
root@fic-gta01:~$ cu -l /dev/ttySAC0<br />
Connected.<br />
AT-Command Interpreter Ready<br />
OK<br />
</pre><br />
<br />
=== Registering with the Network ===<br />
<br />
* enter the following commands:<br />
<pre><br />
ATE1<br />
OK<br />
AT+CFUN=1<br />
ERROR<br />
AT+CPIN="...."<br />
OK<br />
AT+COPS<br />
OK<br />
</pre><br />
<br />
=== Anwering an incoming call ===<br />
<pre><br />
RING<br />
ATA<br />
OK<br />
</pre><br />
<br />
=== Dialling an outgoing call ===<br />
<br />
<pre><br />
ATD012340234;<br />
</pre><br />
<br />
=== Hanging up ===<br />
<pre><br />
ATH<br />
OK<br />
</pre></div>DanielWillmannhttp://wiki.openmoko.org/wiki/Manually_using_GSMManually using GSM2007-03-07T15:07:29Z<p>DanielWillmann: /* Powering up the GSM Modem */ no .ko on modprobe</p>
<hr />
<div><br />
This is a short guide how to manually get GSM going.<br />
<br />
== Requirements ==<br />
<br />
* GTA01Bv2 or GTA01Bv3 with very recent u-boot bootloader, providing usbtty (serial over USB) support)<br />
* Do not connect any debug board!<br />
<br />
<br />
== Walk-Through ==<br />
<br />
=== Booting the system ===<br />
<br />
* Make sure the rootfs you use has 'auto usb0' in /etc/network/interfaces<br />
* Configure the host's usb0 interface to 192.168.0.200 netmask 255.255.255.0<br />
* ssh to root@192.168.0.201<br />
<br />
=== Disabling the getty ===<br />
<br />
Our default images all have a getty running on /dev/ttySAC0, please edit /etc/inittab and disable the getty on that port <br />
<br />
=== Powering up the GSM Modem ===<br />
<br />
* load the "gta01_pm_gsm.ko" kernel module<br />
root@fic-gta01:~$ modprobe gta01_pm_gsm<br />
* verify there is no getty or any other app running on /dev/ttySAC0 <br />
root@fic-gta01:~$ lsof | grep ttySAC0<br />
* power-up the GSM Modem<br />
root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-gsm.0/power_on<br />
* access the GSM Modem UART<br />
<pre><br />
root@fic-gta01:~$ cu -l /dev/ttySAC0<br />
Connected.<br />
AT-Command Interpreter Ready<br />
OK<br />
</pre><br />
<br />
=== Registering with the Network ===<br />
<br />
* enter the following commands:<br />
<pre><br />
ATE1<br />
OK<br />
AT+CFUN=1<br />
ERROR<br />
AT+CPIN="...."<br />
OK<br />
AT+COPS<br />
OK<br />
</pre><br />
<br />
=== Anwering an incoming call ===<br />
<pre><br />
RING<br />
ATA<br />
OK<br />
</pre><br />
<br />
=== Dialling an outgoing call ===<br />
<br />
<pre><br />
ATD012340234;<br />
</pre><br />
<br />
=== Hanging up ===<br />
<pre><br />
ATH<br />
OK<br />
</pre></div>DanielWillmannhttp://wiki.openmoko.org/wiki/Getting_Started_with_your_Neo_1973Getting Started with your Neo 19732007-02-27T22:06:01Z<p>DanielWillmann: /* By using ethernet over a USB cable */ SSH login to the local machine?</p>
<hr />
<div>FIXME: Some first steps guide for our phase-0 recipients.<br />
<br />
The software install I have on a phone right now is several months old -- until I upgrade it, these instructions might not all be relevant.<br />
<br />
Just hitting the power button should get the phone booted and running X/GPE. From this point, there are a few ways to hack on the phone:<br />
<br />
== By using the terminal emulator and on-screen keyboard ==<br />
<br />
"Click" (using a stylus) the top-left arrow icon to get a drop-down menu with "Media", "Settings", "Utilities" and "Desktop". Choose "Utilities->Panel->Input Manager", and a keyboard icon will appear on the top bar. You can get an on-screen keyboard at any time by choosing it.<br />
<br />
From the desktop, choose "Active tasks->rxvt" to get a root shell.<br />
<br />
== By using ethernet over a USB cable ==<br />
<br />
You can run `ifconfig` in the terminal to see which IP the phone has taken. If you plug a USB cable into a laptop running Linux, you'll likely see the "cdc_ether" kernel module being loaded and a usb0 network interface appear. The IP the phone I have was set to use is 192.168.2.2; on my Linux machine, I did:<br />
<br />
ifconfig usb0 192.168.2.2 netmask 255.255.255.0 <br />
ssh root@192.168.2.2<br />
<hit enter when asked for a password> <br />
<br />
You should now have a root login.<br />
<br />
* One of these IPs should probably be 192.168.2.1 <br />
<br />
* [[User:DanielWillmann|DanielWillmann]] 23:06, 27 February 2007 (CET)<br />
<br />
== By using the debug board/serial/JTAG ==<br />
<br />
I don't have a debug board yet; this will be added later.<br />
<br />
[[User:Cjb|Cjb]] 23:14, 23 February 2007 (CET)</div>DanielWillmann