Openmoko - User contributions [en]

Call Recorder

2012-09-12T20:08:05Z

Glenn: +Web archive backup: SVN source code at 20100813124921

This project is a gtk application to record calls on the openmoko.
It backups the current state files and puts it's owns (will soon backup and patch instead).

To start recording, just initiate a call, open the app and start recording.
The files are saved at the user's home dir and they are of the type: call_MMDDYY_HHMMSS.wav.
It's a two channels wave, one channel is the you, the second is the other side of the call, so you can split them when ever you like.

Please note that trying to record while not in a call is not defined, won't crash or anything though will probably will record silence.

* Web archive backup: SVN source code at 20100813124921: [http://web.archive.org/web/20100813124921/projects.openmoko.org/scm/?group_id=282 callrec] (follow link "Download The Nightly SVN Tree Snapshot")
* project page: [http://projects.openmoko.org/projects/callrec/ callrec]

'''Notice:''' Recording a phone conversation without notifying the other party is illegal in some jurisdictions!

= Package =
* author: Tom Hacohen <available_at_profile>
* Distros: tested on SHR should work on all.
* Source code: SVN at [http://projects.openmoko.org/projects/callrec/ project page]
* available at [http://projects.openmoko.org/projects/callrec/ project page].

= How To Use =
== Recording ==
Press the recording button.
== Playback ==
Press the playback button.

= Screenshots =
[[Image:Callrecorder.png]]

[[Category:Telephony]]
[[Category:Audio Applications]]

Openmoko Local Groups: Peru

2012-08-29T16:54:02Z

Glenn: +Category:Openmoko Local Groups

Hi every one, My name is Billy Rondón i'm from Perú and I want to join force and learn of this open smartphone pioneer.

[[Category:Openmoko Local Groups]]

Category:Pages with broken file links

2012-06-30T16:09:18Z

Glenn: Created page with "Category:Wiki Editing"

[[Category:Wiki Editing]]

Press Coverage/nl

2012-03-09T03:30:19Z

Glenn: catchg

{|align=right
|__TOC__
|}
[http://www.google.com/trends?q=openmoko%2Cneo1973&ctab=1&geo=all&date=all Openmoko en Neo1973 op Google trends.]

Deze pagina bevat links naar verschillende artikelen van de pers die gaan over Openmoko en de Neo1973. De artikelen zijn gesorteerd op taal en maand van publicatie.

== Talen ==

=== Engels ===

==== December 2007 ====
* DigiTimes: Freeing your phone: Q&A with Sean Moss-Pultz, president of Openmoko [http://209.85.135.104/search?q=cache:Wu4YfufkOYMJ:www.digitimes.com/news/a20071204VL200.html+http://www.digitimes.com/news/a20071204VL200.html&hl=de&ct=clnk&cd=1&gl=de&client=opera Part I (cache)] [http://www.digitimes.com/telecom/a20071204VL202.html Part II]

* The Linux Link Tech Show: Interview with Michael Shiloh, Openmoko Developer Relations Manager. Audio Files:[http://www.tllts.org/audio/tllts_221-11-28-07.ogg][http://www.tllts.org/audio/tllts_221-11-28-07.mp3]

==== Oktober 2007 ====
* [http://www.news.com/Trolltech-axes-the-Greenphone/2100-1037_3-6214641.html Trolltech axes the Greenphone and recommends the Neo1973 device]
* Wired preview called [http://www.wired.com/gadgets/wireless/news/2007/10/openmoko_firstlook?currentPage=all A First Tussle With Linux's iPhone Killer: The Openmoko Neo1973]
* [http://radar.oreilly.com/archives/2007/10/dash_web2summit_openmoko.html Dash and Openmoko] Tim O'Reilly comments on [http://dash.net/ Dash, the connected GPS] and notes that it is based on the Openmoko software stack and derived from the Neo1973 hardware.
* [http://www.wired.com/gadgets/gadgetreviews/magazine/test2007/st_essay Why Wireless Carriers Cripple Your Cell Phone] on [http://www.wired.com Wired Test] reports what we already know, that wireless carriers put more priority into protecting their "antediluvian business" model than into innovation. Of the Openmoko project it carries few details, but says "That's pretty cool"
* [http://www.linuxjournal.com/article/9768#mpart4 Ten Questions for Sean Moss-Pultz], Program Manager of Openmoko

==== September 2007 ====
* [http://abclocal.go.com/kgo/story?section=drive_to_discover&id=5671823 ABC News] Building A Cell Phone From Scratch ([http://yamato.hyte.de/moko/openmoko_gumstix_neo_abcnews_h264_mp3.avi avi])
* [http://www.phoronix.com/scan.php?page=news_item&px=NjA0NQ phoronix.com] Openmoko Schedule Revised, For X-Mas
* [http://www.tectonic.co.za/view.php?src=rss&id=1739 tectonic.co.za] Linux picks up pace on cellphones

==== Augustus 2007 ====
* [http://lwn.net/Articles/247187/ LWN] A first look at the Openmoko Neo 1973
* [http://www.roughlydrafted.com/RD/RDM.Tech.Q3.07/B10AE668-EAD3-46DC-A042-5EF3461D63EF.html roughlydrafted.com] Apple iPhone vs the FIC Neo1973 Openmoko Linux Smartphone
* [http://www.macworld.com/news/2007/08/02/openmoko/index.php Macworld] Portrait of a Linux iPhone-killer wannabe
* [http://www.phoronix.com/?page=news_item&px=NTk1Mw Phoronix] Google Using Openmoko For gPhone?

==== Juli 2007 ====
* [http://www.pcworld.com/article/id,134987-pg,1/article.html PCWorld] Insider Info on the First Fully Open-Source Cell Phone
* [http://blog.wired.com/monkeybites/2007/07/hands-on-with-t.html Wired Blog] Hands On with Openmoko: An early look at the hardware and software.
* [http://www.economist.com/science/displaystory.cfm?story_id=9531007 Economist.com] Hello world: Avoiding punitive roaming charges abroad
* [http://linuxdevices.com/news/NS7355980470.html linuxdevices.com] iPhone-like Linux phone ready for hackers
* [http://www.heise.de/english/newsticker/news/92473 heise.de] "Free your phone": The Openmoko Project's Linux Smartphone now available
* [http://blogs.zdnet.com/open-source/?p=1194 zdnet.com] Can Openmoko break the wireless monopoly?
* [http://developers.slashdot.org/developers/07/07/09/0049249.shtml Slashdot] Open Source Linux Phone Goes On Sale
* [http://www.engadget.com/2007/07/09/openmoko-neo-1973-and-advanced-dev-kit-finally-for-sale/ engadget.com] Openmoko Neo 1973 and Advanced dev kit finally for sale
* [http://www.theglobeandmail.com/servlet/story/RTGAM.20070703.WBcyberia20070703161759/WBStory/WBcyberia/ Globe and Mail, Toronto] The Next Big Thing? (good overview; some favorable comparisons with iPhone).
* [http://arstechnica.com/news.ars/post/20070710-developer-models-of-openmoko-open-source-smartphone-released.html arstechnica.com] Developer models of Openmoko open-source smartphone released
* [http://www.boingboing.net/2007/07/09/openmoko_linuxbased_.html boingboing (Cory Doctorow)] Openmoko: Linux-based $300 open smartphone
* [http://www.channelweb.co.uk/vnunet/news/2192036/first-open-source-mobile-phone channelweb.co.uk / CRN] Openmoko preps first open source mobile
* [http://www.makezine.com/blog/archive/2007/07/openmoko_300_linuxpowered.html?CMP=OTC-0D6B48984890 MAKE:] blogged about it.
* [http://www.theregister.co.uk/2007/07/09/neo_1973_launch/ The Register] Is your phone free?
* [http://www.theinquirer.net/default.aspx?article=41147 The Inquirer] Linux phone goes on sale

==== Juni 2007 ====
* [http://fakesteve.blogspot.com/2007/06/freetards-are-trying-to-make-iphone.html Secret Diary of Steve Jobs] Freetards are trying to make an iPhone clone
* [http://www.eweek.com/article2/0,1895,2152759,00.asp eweek.com] Openmoko: An iPhone Alternative for Developers?
* [http://www.linuxdevices.com/news/NS8509737406.html&cid=0 linuxdevices.com] iPhone-like Linux phone delayed
* [http://www.itweek.co.uk/vnunet/news/2192036/first-open-source-mobile-phone IT Week] "Openmoko preps first open source mobile" Confuses Phase 1 and Phase 2 features.
* [http://www.vnunet.com/vnunet/news/2192036/first-open-source-mobile-phone vnunet.com] First open source mobile phone
* [http://www.techeblog.com/index.php/tech-gadget/feature-5-cool-linux-powered-phones TechEBlog.com] A brief line-up of the 5 coolest Linux-powered phones.
* [http://www.tectonic.co.za/view.php?id=1574 Tectonic.co.za] Open source phone plans September launch
* [http://www.hothardware.com/image_popup.aspx?image=big_fic2.jpg&articleid=979&t=a hothardware.com] Openmoko
* [http://www.texyt.com/FIC+Openmoko+$350+open+Linux+mobile+phone+launch+00100 Texyt.com] $350 open Linux mobile phone on target for September launch

==== Mei 2007 ====
* [http://blogs.sun.com/brewin/entry/fic_and_openmoko_thank_you blogs.SUN.com] "FIC and Openmoko - Thank You" Mentions the FIC phone used in the exciting JavaFX Mobile announcement, and says that "in most cases the Neo 1973 phone performed better" than other handsets.
* [http://www.pikesoft.com/blog/index.php?itemid=174 PikeSoft.com] JavaFX Mobile: a new smartphone OS contender
* [http://www.sfgate.com/cgi-bin/blogs/sfgate/detail?blogid=19&entry_id=16310 SFGate.com] Here comes the Sun Conference
* [http://www.linuxdevices.com/news/NS7539760574.html LinuxDevices.com] Sun beams Linux/Java at mobile phones

==== April 2007 ====
* [http://www.palminfocenter.com/news/9371/openmoko-running-on-a-palm-tx/ Palm Infocenter] Openmoko running on a palm TX
* [http://jaidev.info/home/blog/archives/2007/04/13/openmoko.html JaidevInfo] Openmoko
* [http://www.wirelessweek.com/newsletter.aspx?id=137388 Wirelessweek.com] Democracy Hits the Mobile Phone
* [http://elearner.edublogs.org/2007/04/11/technologies-is-that-a-word/ Edublogs.org] Technologies is that a word?
* [http://www.linuxdevices.com/news/NS4777580627.html Linuxdevices.com] 200 million Linux phones to ship by 2012
* [http://arstechnica.com/news.ars/post/20070415-palm-embracing-linux-in-the-hopes-of-being-relevant-again.html Ars Technica] Palm embracing Linux in the hopes of being relevant again] (Mentions Neo1973 in passing)

==== Maart 2007 ====
* [http://www.smartdevicecentral.com/article/Openmokos+Open+Source+Phone/202546_1.aspx smartdevicecentral.com] Openmoko's open source phone
* [http://www.zdnetasia.com/news/communications/0,39044192,61996003,00.htm zdnet asia] Passing mention in an article on the Iphone.
* [http://www.wikio.com/news/Sean+Moss-Pultz wikio.com] Sean Moss-Pultz News
* [http://www.edparsons.com/?p=438 edparsons.com] iPhone chipping away at the walls
* [http://blogs.pcworld.co.nz/pcworld/techsploder/2007/03/openmoko_makes_total_sense.html blogs.pcworld.co.nz] Openmoko makes total sense
* [http://www.totalueberwachung.de/blog/articles/2007/03/08/neo1973-arrived totalueberwachung.de] Neo1973 arrived
* [http://www.makuchaku.info/blog/im-gonna-get-this-one makuchaku.info] I'm gonna get this one
* [http://www.kitenet.net/~joey/blog/entry/openmoko_and_n800.html kitenet.net] Openmoko and n800
* [http://dominion.kabel.utwente.nl/koen/cms/the-neo1973-unboxed dominion.kabel.utwente.nl] The Neo1973 unboxed
* [http://atulchitnis.net/diary/showentry/421 atulchitnis.net] An Openmoko Phone arrives
* [http://blog.matthewgast.com/2007/03/03/good-luck-openmoko blog.matthewgast.com] Good luck Openmoko
* [http://vaandoo.blogspot.com/2007/03/openmoko-neo1973-opensource-software.html vaandoo.blogspot.com] Openmoko Neo1973 opensource software
* [http://www.linuxdevices.com/news/NS7653749655.html linuxdevices.com] Openmoko update; Neo1973 on sale in March
* [http://www.ministryoftech.com/2007/03/05/the-5-hottest-phones-for-linux-fanatics/ ministryoftech.com] Brief line-up of the 5 hottest phones for Linux fans
* [http://voxilla.com/soapvox/2007/03/01/industry-disruption-really-168 voxilla.com] Article about ETel Sean Moss-Pultz presentation
* [http://blog.wired.com/gadgets/2007/03/eight_great_lin.html blog.wired.com] Gadget Lab: Eight Great Linux Smartphones
* [http://gigaom.com/2007/03/01/openmoko-phone/ gigaom.com] Openmoko Open-Source Mobile, coming soon - Interview with Sean Moss-Pultz
* [http://www.oreillynet.com/etel/blog/2007/03/openmoko_1.html www.oreillynet.com] ETel coverage
* [http://gordoncook.net/wp/?p=146 gordoncook.net] Short history of Neo1973 and other stuff
* [http://www.engadget.com/2007/03/03/openmoko-details-pricing-availability-for-neo1973/ engadget.com] Openmoko details pricing, availability for Neo1973
* [http://www.uberpulse.com/us/2007/03/fic_wants_to_rewrite_the_rules_with_open_moko_mobile_phone.php www.uberpulse.com] Some images from ETel

==== Februari 2007 ====
* [http://www.scullen.ca/2007/02/15/forget-about-the-iphone-neo1973-is-far-more-exciting/ scullen.ca] Forget about the iPone, Neo1973 is far more exciting
* [http://www.mobileread.com/forums/showpost.php?p=59124&postcount=4 mobileread.com] Show post
* [http://www.pdasnews.com/articles/2568/1/ pdasnews.com] Linux-powered iPhone killer available online in March
* [http://www.belutz.net/2007/02/05/openmoko/ belutz.net] Openmoko
* [http://www.mail-archive.com/community@lists.openmoko.org/msg03686.html mail-archive.com] Openmoko community mail archive
* [http://www.maclife.com/article/is_three_a_crowd_in_the_touch_screen_phone_arena maclife.com] Is there a crowd in the touch screen phone arena
* [http://gopaultech.com/2007/02/fic-neo1973-linux-smartphone/ gopaultech.com] FIC Neo1973 Linux smartphone
* [http://www.volweb.cz/horvitz/os-info/news-feb07-014.html volweb.cz] Open-source smartphone, with WiFi in version 2
* [http://www.oreillynet.com/etel/blog/2007/02/etel_coverage_openmoko_opens_t.html oreillynet.com] ETel coverage Openmoko opens
* [http://www.mobilewhack.com/openmoko-neo1973-open-source-phone/ mobilewhack.com] Openmoko Neo1973 open source phone
* [http://www.engadget.com/2007/02/19/what-tech-would-the-presidents-rock-in-2007/ engadget.com] What tech would the presidents rock in 2007
* [http://www.tuxmachines.org/node/13602 tuxmachines.org] What participation culture
* [http://www.vanille-media.de/site/index.php/category/opensource/openmoko/ vanille-media.de] Opensource Openmoko
* [http://www.joetech.com/2007/02/15/openmoko-open-source-cell-phone/ joetech.com] Openmoko open source cell phone
* [http://www.makezine.com/blog/archive/2007/02/openmoko_open_s.html makezine.com] Openmoko open
* [http://www.linuxdevices.com/news/NS9706477996.html linuxdevices.com] Announce of the Openembedded booth at FOSDEM in Brussels.
* [http://www.linuxdevices.com/news/NS2657814070.html linuxdevices.com] Quick interview with Sean and some pictures
* [http://gizmodo.com/gadgets/smartphones/first-look-the-antiiphone-openmokos-neo1973-236841.php gizmodo.com] Photos and comments on hardware and software
* [http://www.onecompare.com/mobile-news/article-asp~aid~244~pub~56321102~story~openmoko-launch-the-official-portal-for-development-of-the-openmoko-platform onecompare.com] Short news article
* [http://crunchgear.com/2007/02/15/openmokos-open-source-mobile-os crunchgear.com] Holding the phone upside down
* [http://www.slashgear.com/openmoko-and-fic-neo1973-updates-153926.php slashgear.com] Video interview and many pictures
* [http://www.djlosch.com/article_Comparison%3A_iPhone_vs_A1200_vs_Neo1973 djlosch.com] Article comparing the Neo to the iPhone and A1200
* [http://popsci.typepad.com/popsci/2007/02/up_close_and_pe.html popsci.typepad.com] Screenshot of Linux booting on the Neo
* [http://video.google.de/videoplay?docid=-3742589179435830945&q=Openmoko video.google.com] Presentation of Openmoko at the FOSDEM
* [http://www.manilastandardtoday.com/?page=business6_feb27_2007 manilastandardtoday.com] Tale of two phones
* [http://blog.printf.net/articles/2007/02/22/unboxing-the-openmoko-phone blog.printf.net] OLPC and older Neo1973.
* [http://mako.cc/copyrighteous/freesoftware/20070228-00.html mako.cc] OLPC and older Neo1973 again.
* [http://www.maclife.com/article/is_three_a_crowd_in_the_touch_screen_phone_arena MacLife] Is Three a Crowd among Touch-Screen Phones?
* [http://www.linuxjournal.com/article/9489#mpart5 Linux Journal] A White Box Phone

==== Januari 2007 ====
* [http://blogs.ft.com/techblog/2007/01/openmoko_harks_.html blogs.ft.com] Openmoko harks back to hello moto
* [http://opensource.sfsu.edu/node/258 opensource.sfsu.edu] Can you hear me now?
* [http://losca.blogspot.com/2007/01/maemo-nokia-n800-has-competitor-in.html losca.blogspot.com] Maemo Nokia n800 has competitor in openness - Openmoko
* [http://21talks.net/voip/openmoko 21talks.net] Openmoko: Not as sexy as the iPhone, but it’s a Linux phone
* [http://www.linuxinfusion.com/openmoko-schedule-announced linuxinfusion.com] Openmoko schedule announced
* [http://users.livejournal.com/_paladine_/tag/smartphone users.livjournal.com] The Worlds First Opensource Linux Smartphone
* [http://www.nungee.com/2007/01/25/openmoko/ nungee.com] Openmoko
* [http://www.sda-asia.com/sda/features/psecom,id,880,srn,2,channel,developer,nodeid,21,_language,Singapore.html sda-asia.com] Openmoko Offers Open-source Smart phone T
* [http://www.regdeveloper.co.uk/2007/01/15/open_phone/ regdeveloper.co.uk] Open Phone
* [http://www.product-reviews.net/2007/01/17/fic-neo1973-smartphone-open-source-phone/ product-reviews.net] FIC Neo1973 smartphone open source phone
* [http://gizmodo.com/gadgets/smartphones/openmoko-smartphone-did-they-have-a-time-machine-or-what-229243.php gizmodo.com] Openmoko smartphone did they have a time machine or what
* [http://www.oreillynet.com/conferences/blog/2007/01/openmoko_workshop_added_to_ete.html oreillynet.com] Openmoko workshop added to ETel
* [http://www.gadgetell.com/2007/01/openmoko-gets-interviewed-about-new-open-source-fic-neo1973/ gadgetell.com] Openmoko gets interviewed about new open source FIC Neo1973
* [http://www.slashgear.com/openmoko-interface-im-loving-it-173496.php slashgear.com] Openmoko interface I'm loving it
* [http://www.gadgetorama.com/news/news_details.php?gorid=2008 gadgetorama.com] Openmoko news details
* [http://tech.cybernetnews.com/2007/01/17/openmoko-vs-iphone-did-apple-copy/ tech.cybernetnews.com] Openmoko vs iPhone did Apple copy
* [http://techtrails.blogspot.com/2007/01/open-phones-with-open-moko-while.html techtrails.blogspot.com] Open phones with Openmoko while
* [http://blogger.xs4all.nl/jurjen1/archive/2007/01/17/174341.aspx bloger.xs4all.nl] Openmoko open source mobile phone
* [http://www.ringnokia.com/2007/01/i_am_highly_cur.html ringnokia.com] I'm highly curious
* [http://www.oreillynet.com/etel/blog/2007/01/iclone_1.html oreillynet.com] iClone
* [http://forums.scotsnewsletter.com/index.php?showtopic=17685 forums.scotsnewsletter.com] Show topic
* [http://understandinglimited.com/2007/01/15/iphone/ understandinglimited.com] iPhone and Openmoko
* [http://robertogaloppini.net/2007/01/12/openmoko-the-integrated-os-mobile-communications-platform-2/ robertogaloppini.net] Openmoko the intergrated OS mobile communications platform
* [http://www.funambol.com/blog/capo/2007/01/apple-please-do-not-forget-developers.html funambol.com] Apple please do not forget developers
* [http://chopey.blogspot.com/2007/01/iphone-or-not-to-iphone.html chopey.blogspot.com] iPhone or not to iPhone
* [http://opendotdotdot.blogspot.com/2007/01/openmoko.html opendotdotdot.blogspot.com] Openmoko
* [http://www.e-pcmag.gr/forum/index.php?showtopic=19505 e-pcmag.gr] Show topic
* [http://www.costpernews.com/2007/01/12/anything-you-can-do-we-can-do-better/ costpernews.com] Anything you can do we can do better
* [http://www.tectonic.co.za/view.php?id=1321 tectonic.co.za] iPhone vs Openmoko - the Open Alternative
* [http://lwn.net/Articles/217020/rss lwn.net] An Openmoko update
* [http://www.networkworld.com/news/2007/010907-moss-pultz.html networkworld.com] Q&A Building a new open source phone platform
* [http://www.networkcomputing.com/showArticle.jhtml?articleID=196802226 networkcomputing.com] Startup Promises First Linux Smartphone Based On Open Standards
* [http://www.osweekly.com/index.php?option=com_content&task=view&id=2420&Itemid=449 osweekly.com] Mobile Devices Adopt Open Source
* [http://www.linuxdevices.com/news/NS8591201260.html linuxdevices.com] Linux phone market open up?
* [http://www.pcmag.com/article2/0,1895,2080727,00.asp pcmag.com] Cell phone open up
* [http://sonyericssonz558i.blogurple.com/2007/01/06/23/ sonyericssonz558i.blogurple.com] Sony Ericsson Z558i
* [http://www.sannes.org/?p=5 sannes.org] An Open mobile phone that does what you want
* [http://popsci.typepad.com/ces2007/2007/01/opensource_stri.html Popsci.com] Open Source Strikes Again
* [http://gizmodo.com/gadgets/smartphones/openmoko-smartphone-did-they-have-a-time-machine-or-what-229243.php Gizmodo.com] Openmoko interface compared to iPhone
* [http://www.linuxjournal.com/xstatic/abstracts/upfront Linux Journal] Doc Searls in the feb 2007 issue
* [http://www.osdir.com/Article9642.phtml OSDir.com] Mobile Linux for the Mobile Fan] -> [http://www.madpenguin.org/cms/?m=show&id=7710 MadPenguin] Mobile Linux for the Mobile Fan
* [http://www.usnews.com/usnews/biztech/davesdownload/archive/070112/a_populist_challenge_to_apples.htm US News] A Populist Challenge to Apple's iPhone
* [http://www.tectonic.co.za/view.php?id=1321 tectonic.co.za] iPhone vs Openmoko: The open alternative
* [http://www.informationweek.com/news/showArticle.jhtml?articleID=196802206&subSection=All+Stories InformationWeek] Startup Promises First Linux Smartphone Based On Open Standards
* [http://www.theregister.co.uk/2007/01/15/open_phone/ The Register] Open Phones with Open Moko
* [http://techreport.com/onearticle.x/11589 The Tech Report] Openmoko offers open-source smart phone
* [http://blogs.ft.com/techblog/2007/01/openmoko_harks_.html Financial Times] Openmoko harks back to Hello Moto
* [http://hardware.slashdot.org/article.pl?sid=07/01/20/1551200 Slashdot] Openmoko Schedule Announced
* [http://www.youtube.com/watch?v=jRvtAAXTIlg Youtube] Interview with Sean Moss-Pultz ([http://www.monoploid.be/dl/openmoko_sean_interview.ogm mirror in Ogg format])
* [http://www.libervis.com/article/forget_iphone_hail_openmoko_the_true_revolution Libervis.com] Forget iPhone, hail Openmoko, the true revolution
* [http://gizmodo.com/gadgets/smartphones/sizemodo-iphone-vs-openmoko-neo1073-229294.php Gizmodo]iPhone vs. Openmoko Neo1973] (please, don't mind the typo i n the title)

==== December 2006 ====
* [http://www.pikesoft.com/blog/index.php?itemid=133 pikesoft.com] Cheap, totally open Linux phone will ship next month
* [http://www.cdrinfo.com/Sections/News/Details.aspx?NewsId=19254 cdrinfo.com] FIC to release Linux based Smartphone

==== November 2006 ====
* [http://www.ministryoftech.com/2006/11/09/fic-neo1973-smartphone-with-linux-based-openmoko-open-source-platform/ ministryoftech.com] FIC Neo1973 smartphone with linux-based Openmoko open source platform
* [http://www.mobiletechnews.com/info/2006/11/09/124614.html mobiletechnews.com] Openmoko Linux mobile platform and Neo1973 smartphone announced
* [http://news.softpedia.com/news/FIC-Neo1973-for-all-the-Linux-Lovers-out-There-40344.shtml news.softpedia.com] FIC Neo1973 for all the Linux lovers out there
* [http://www.openembedded.org/openmoko-fic-choosing-openembedded openembedded.org] Openmoko FIC choosing openembedded
* [http://news.com.com/2300-1037_3-6134795-1.html news.com.com] FIC's Linux handset
* [http://www.slashphone.com/77/5784.html slashphone.com] Openmoko Announces Open Source Mobile Communications Platform
* [http://www.arm.com/iqonline/news/marketnews/15616.html arm.com] Open Linux Based, ARM Powered Mobile In Wings
* [http://news.com.com/Second+open+Linux+handset+unveiled/2100-1039_3-6133974.html news.com.tw] Second open Linux handset unveiled
* [http://www.infoworld.com/article/06/11/08/HNlinuxphone_1.html?COMMERCIAL%20LINUX infoworld.com] FIC debuts open Linux-based smartphone
* [http://www.michaeldolan.com/431 michaeldolan.com] A must have: Openmoko cell phone with GPS and...apt-get
* [http://nandz.blogspot.com/2006/11/my-dream-phone.html nandz.blogspot.com] My dream phone
* [http://www.linuxdevices.com/news/NS2986976174.html linuxdevices.com] Cheap, hackable Linux smartphone due soon
* [http://www.linuxdevices.com/news/NS7056478804.html linuxdevices.com] First OpenMoKo phone taps dual-licensed SyncML stack
* [http://lwn.net/Articles/208298/ lwn.net] The Openmoko open phone
* [http://www.theinquirer.net/default.aspx?article=35590 theinquirer.net] A truly open Linux phone with GPS debuts

=== Duits ===
==== November ====
* [http://www.heise.de/newsticker/meldung/98489 heise.de: Das GPhone ist ein Android] GPhone System "wildert in den Gefilden vergleichbarer Initiativen wie Openmoko"

==== September ====
* [http://futurezone.orf.at/produkte/stories/219038/ futurzone@orf.at] "Und jetzt: Befreien Sie Ihr Handy."
* [http://www.pro-linux.de/news/2007/11704.html Pro-Linux] Openmoko für den Massenmarkt erst an Weihnachten

==== Augustus 2007 ====
* [http://www.golem.de/0708/54256.html golem.de] - Neues GUI für Open-Source-Handy Neo1973
* [http://www.heise.de/mobil/newsticker/meldung/94724 heise mobil] - Offene Smartphone-Plattform mit neuem Look

==== Juli 2007 ====
* [http://lists.openmoko.org/pipermail/community/attachments/20070721/be55235c/CIMG1129_small-0001.jpg Kurier] - Handy Individuell
* [http://futurezone.orf.at/produkte/stories/206048/ futurezone.ORF.at] - Anti-iPhone geht an den Start
* [http://www.zdnet.de/news/hardware/0,39023109,39156101,00.htm zdnet.de] - Open-Source-Iphone wird mit Hackertools ausgeliefert
* [http://www.heise.de/newsticker/meldung/92393 heise.de] - "Free your phone": Linux-Smartphone des Openmoko-Projekts verfügbar
* [http://www.spiegel.de/netzwelt/mobil/0,1518,493595,00.html spiegel.de] - Linux statt iPhone: Freiheit fürs Handy

==== Juni 2007 ====
* [http://www.golem.de/0706/53172.html golem.de] - Linux-Smartphone Openmoko ab Juli 2007 zu haben
* [http://www.heise.de/newsticker/meldung/91868 heise.de] - Offenes Linux-Smartphone Neo 1973 macht Fortschritte
* [http://www.winfuture.de/news,32641.html winfuture.de] - Open-Source-Handy Neo1973 ab Juli bzw. Oktober
* [http://www.pro-linux.de/news/2007/11385.html pro-linux.de] - Openmoko wird zum Unternehmen
* [http://de.theinquirer.net/2007/06/14/das_erste_openmoko_kommt.html the inquirer] - Das erste OpenMOKO kommt

==== April 2007 ====
* [http://www.pro-linux.de/news/2007/11133.html pro-linux] - Openmoko produziert erste Muster
* [http://www.golem.de/0704/51970.html golem.de] - Open-Source-Handy vor Produktionsbeginn

==== Maart 2007 ====
* [http://chaosradio.ccc.de/cre042.html Chaosradio Express] - Das neue Projekt zur Entwicklung eines Telefons mit freier Software
* [http://www.pro-linux.de/news/2007/10966.html pro-linux] - Openmoko sucht Unterstützung

==== Februari 2007 ====
* [http://www.digital-living-magazin.de/index.php?pid=17&art=2050&cid=DLnewsletter digital-living-magazin.de] - Linux erobert Mobilfunkmarkt
* [http://www.heise.de/tr/artikel/85138 Technology Review] - Open-Source-Handy, nächster Versuch
* [http://www.pro-linux.de/news/2007/10833.html pro-linux] - Openmoko-Quellcode angekündigt
* [http://www.heise.de/newsticker/meldung/85354 heise online] - Openmoko: Linux-Plattform für Handys freigegeben
* [http://www.mobile2day.de/news/news_details.html?nd_ref=6870&n_multi=0&nf_id=0&nt_id=0&f_date_m=01&f_date_y=2007&t_date_m=04&t_date_y=2007&from=archive Mobile2Day] - Openmoko bringt Details zum Neo1973

==== November 2006 ====

* [http://golem.de/0611/48824.html golem.de] - Openmoko kündigt Open-Source-Handy an
* [http://www.heise.de/newsticker/meldung/80714 heise online] - Smartphone mit offener Linux-Plattform
* [http://www.pro-linux.de/news/2006/10448.html pro-linux] - Offenes Linux-Smartphone »Openmoko« für Januar 2007 angekündigt

=== Scandinavië ===

* [http://www.amobil.no/artikkel/mobiltelefoner/antikrist-mobilen_blir_heftigere/41042 Amobil.no] Antikrist-mobilen blir heftigere
* [http://www.amobil.no/sniktitt/mobiltelefoner/den_folsomme_linux-mobilen/40176 Amobil.no] Sniktitt: Den følsomme Linux-mobilen
* [http://www.amobil.no/artikkel/markedsutvikling/linux-mobilen_er_i_rute/40138 Amobil.no] Linux-mobilen er i rute
* [http://www.amobil.no/nyhet/mobiltelefoner/openmoko_klart_for_verden/36554 Amobil.no] Openmoko klart for verden
* [http://www.nyteknik.se/art/48697 NyTeknik] Snart är den öppna Linuxtelefonen här (Swedish) (Translation: this article states free release to selected developers Feb 11, commercial release to developers March 11, and main release to market Sep 11. See also [http://lists.openmoko.org/pipermail/announce/2007-January/000000.html])

=== Frans ===
* [http://linuxfr.org/2006/11/08/21596.html LinuxFR] Openmoko : sortie en janvier d'un téléphone-GPS enfin libre!

=== Chinees ===

* [http://marrtw.blogspot.com/2007/11/intro-to-openmoko.html Marr's Weblog] Intro to Openmoko. Also mention OpenLab.
* [http://1-apple.com.tw/apple/index.cfm?Fuseaction=Article&Sec_ID=8&ShowDate=20071119&NewsType=twapple&Loc=TP&Art_ID=4009959 1-Apple Daily News] FIC/Openmoko provide 100% open source mobile communication platform.
* [http://www.pconline.com.cn/mobile/news/hgxz/0711/1157957.html PConline China] Neo 1973 test report.
* [http://news.sina.com.tw/tech/sinacn/cn/2007-11-16/110338206084.shtml Sina Taiwan] Neo 1973 test report.
* [http://news.oss.tw/node/6363 News.Oss.Tw] Openmoko OpenLab Opening
* [http://www.digitimes.com.tw/n/article.asp?id=0000072911_B8M11RL8U70UDGF2BY10X DigitTimes Taiwan] News about Openmoko OpenLab Opening and Neo1973.
* [http://openmoko.wordpress.com/2007/06/21/openmoko-%E8%88%87-iphone-%E6%AF%94%E8%BC%83%E4%B8%80/ wordpress.com] Comparison between Openmoko and iPhone
* [http://chinese.engadget.com/2007/06/11/computex-2007-openmoko-neo-1973-linux/ chinese engadget.com] Openmoko Neo1973 Linux Smartphone
* [http://people.debian.org.tw/~chihchun/2007/05/25/talk-of-openmoko-is-online/ debian.org.tw] Video of Openmoko at TOSSUG in Taipei
* [http://people.debian.org.tw/~chihchun/2007/05/17/openmoko-at-tossug/ debian.org.tw] Openmoko at TOSSUG
* [http://magicdesign.blogspot.com/2007/05/free-your-phoneopenmoko.html MagicDesign] Free your phone Openmoko
* [http://people.debian.org.tw/~chihchun/2007/04/30/have-fun-with-openmokoneo1973/ Debian.org.tw] Have fun with Openmoko Neo1973
* [http://orzlab.blogspot.com/ Orzlab] When Java meets Openmoko
* [http://blog.footoo.org/?p=115 FooToo.org] Install Openmoko Emulator
* [http://www.jollen.org/blog/2007/01/openmoko_announce.html Jollen.org] Openmoko Kick-Off
* [http://zh.wikipedia.org/wiki/Openmoko Wikipedia.org] Openmoko Chinese Wiki
* [http://tw.myblog.yahoo.com/champ_yen/article?mid=211&prev=212&next=-1 Yahoo.com.tw] Forget about iPhone, Hail Openmoko
* [http://www.jollen.org/blog/2006/11/mobile_20_openmoko_linux_smart.html Jollen.org] Openmoko Linux Smartphone
* [http://blog.roodo.com/ystuan/archives/2733869.html Roodo.com] Openmoko

=== Pools ===

==== Mei 2007 ====
* [http://www.studencka.pl/artykuly.php?AID=770 Gazeta Studencka] (Students Newspaper) "Cellphones of all shapes, unite!" - Openmoko overview by Krzysztof Kajkowski, "free software" not mentioned in the text.

=== Japans ===

* [http://blog.pasonatech.co.jp/hibi/4079.html pasonatech.co.jp] iPhoneキラー？：オープンソース精神なopenmoko携帯がUSで発売
* [http://journal.mycom.co.jp/articles/2007/06/06/computex04/index.html journal. mycom.com.jp] Computex Taipei 2007

=== Italiaans ===

==== Juli 2007 ====
* [http://www.corriere.it/Primo_Piano/Scienze_e_Tecnologie/2007/07_Luglio/10/neo1973_telefonino.shtml corriere.it] L'anti iPhone: Neo 1973, il cellulare fai da te
* [http://punto-informatico.it/p.aspx?id=2035879 Punto Informatico] Lo smartphone touch-screen è open source

=== Nederlands ===

==== September 2007 ====
*[http://www.pocketinfo.nl/nieuws/smartphones/9073/de-stand-van-zaken-rond-openmoko.html pocketinfo.nl] De stand van zaken rond Openmoko.
*[http://life.tweakers.net/nieuws/49288/Productieversie-Openmoko-telefoon-nog-dit-jaar-leverbaar.html tweakers.net] Productieversie Openmoko-telefoon nog dit jaar

==== Juli 2007 ====
*[http://www.techzine.nl/nieuws/12929/Opensource-OS-voor-telefoons-geintroduceerd.html techzine.nl] Opensource OS voor telefoons geïntroduceerd
*[http://core.tweakers.net/nieuws/48335/Open-Linux-smartphone-in-de-verkoop.html tweakers.net] Open Linux-smartphone in de verkoop
*[http://www.opensourcenieuws.nl/index.php/content/view/4148/54/ opensourcenieuws.nl] Openmoko platform en de Openmoko Neo1973 gelanceerd.
*[http://www.gadgetgarden.nl/archives/2007/07/fic_linux_openm.php] FIC Linux Openmoko Smartphone: zoals jij wilt!

==== Maart 2007 ====
*[http://www.bits-chips.nl/artikel/art_view.asp?ac=view&art_id=9682 bits-chips.nl]Open-source-ontwikkelaars snakken naar open mobieltje.

==== Februari 2007 ====
*[http://www.telecomwereld.nl/n0001717.htm telecomwereld.nl] Neo1973 eerste smartphone voor Openmoko Linux
*[http://www.opensourcenieuws.nl/index.php/content/view/3914/54/ opensourcenieuws.nl] Openmoko Iphone met Linux
*[http://www.zdnet.nl/news.cfm?id=65618&mxp=201 zdnet.nl] iPhone-concurrent draait Linux
*[http://www.bits-chips.nl/artikel/art_view.asp?ac=view&art_id=9210 bits-chips.nl] Mobieltjesmakers zoeken openheid

==== November 2006 ====
*[http://www.hollandopen.nl/article.jsp?nr=3554 hollandopen.nl] Openmoko: Open source platform voor mobiele telefoons
*[http://www.bits-chips.nl/artikel/art_view.asp?ac=view&art_id=8540 bits-chips.nl] Openmoko moet mobieltjes openen voor ontwikkelaars

{{Languages|Press_Coverage}}

[[Category:Community/nl]]
[[Category:Openmoko Inc/nl]]

Introduction/nl

2012-03-09T03:30:04Z

Glenn: catchg

{{Languages|Introduction}}

Openmoko is een poging om 's werelds eerste totaal open mobiele telefoon software te creëren.

Wij geloven in omgekeerde standaardisatie (gedefinieerd en geïmplementeerd door de gemeenschap), in plaats van boven naar beneden standaardisatie (gedefinieerd door een bedrijf).

Voor een uitgebreidere introductie, zie:
[http://lists.openmoko.org/pipermail/announce/2007-January/000000.html this announcement]

Openmoko zou op verschillende toestellen moeten kunnen draaien die ook linux kunnen draaien. De eerste volledig ondersteunde Openmoko telefoon is de Neo1973 van FIC.

De grote motors achter dit project zijn [[FIC/nl|FIC Inc.]] en [http://www.openmoko.com Openmoko, Inc.]

== Audio ==
* [http://chaosradio.ccc.de/cre042.html Chaosradio Express met Tim Pritlove en Harald Welte (duits)]

== Video's ==
* [http://www.youtube.com/watch?v=jRvtAAXTIlg Wereld debuut: de eerste compleet vrije mobiele telefoon]
* [http://www.youtube.com/watch?v=tQPjfUqp-dk&mode=related&search= Neo1973 promotie video {kort hardware/software overzicht}]
* [http://people.openmoko.org/mickey/videos/dialer-xvid.avi Neo1973 telefonerend. Video courtesy Daniel 'alphaone' Willmann]
* [http://video.google.co.uk/videoplay?docid=-3742589179435830945&hl=en-GB Google Video van de talk about Openmoko by Sean Moss Pultz at FOSdem on 23rd Feb 2007.]
* [http://rapidshare.com/files/18781887/rect.avi Versie van het filmpje hierboven in hogere resolutie, met gezoomd scherm en op het projectorscherm getoond. Tekst is hier zichtbaar, in tegenstelling tot bovenstaande versies.
* [http://video.google.com/videoplay?docid=-8574715471341709984 Openmoko bij Tossug], gepresenteerd door Sean Moss Pultz en Harald Welte bij de Taipei Open Source Software User Group (TOSSUG)
* [http://people.openmoko.org/ninjutsu/NinjutsuVol1pt1.mp4 MokoNinja infiltrates FIC] Featuring Mickey, Harald, The Neo, en meer...
* [http://people.openmoko.org/ninjutsu/NinjutsuVol1pt2.mp4 Video playback on Neo1973 (soort van..)] By Dr. Michael 'Mickey' Lauer
* [http://www.youtube.com/watch?v=5D6i6vLlhGA AGPS Demo on the Neo1973] By mokoNinja on YouTube
* [http://people.openmoko.org/ninjutsu/AGPS_Neo1973.mp4 AGPS Demo and Drop Test (downloadable version)] Performed By Lil' Sean

== Foto's ==

=== Buitenkant ===
[[Image:FIC-neo1973_small.jpg|200px|frontside]]
[[Image:Neo1973_uboot_splash.jpg|200px|bootloader splash screen]]
[[Image:Gta01b v3 case back white.jpg|200px|backside]]

Externe link [http://blog.printf.net/articles/2007/02/22/unboxing-the-openmoko-phone werkend, om de helderheid van het scherm te tonen.]

Zie ook [[Wishlist:Neo1973 P0 Review]]

=== Binnenkant ===
[[Image:Gta01b v3 top.jpg|200px|display (top) side]]
[[Image:Gta01b v3 bottom.jpg|200px|component (back) side]]
[[Image:Gta01b v3 case top open pcb lifted.jpg|200px|case top open pcb lifted]]
[[Image:Gta01b v3 case top open pcb lift white.jpg|200px|case top open pcb lift white]]
[[Image:Gta01b v3 case top open white.jpg|200px|case top open white]]

[[Category:Openmoko Inc/nl]]

Thank You green card/fr

2012-03-09T03:29:39Z

Glenn: catchg

Cette carte présente le texte suivant côté face :

Merci de vos efforts pour nous aider à libérer le téléphone portable.

Et côté pile, la citation de Lao Tseu suivante :

Trente rayons s'attachent au moyeu de la roue 
Mais c'est le trou central qui la rend utile 
Construisez un navire 
C'est l'espace intérieur qui le rend utile 
Enlevez portes et fenêtres d'une pièce 
Ce sont les trous qui la rendent utile 
Les profits viennent de ce qui se voit 
L'utilité de ce qui ne se voit 

Lao Tseu

[[category:Openmoko Inc/fr]]

Press Coverage/fr

2012-03-09T03:29:26Z

Glenn: catchg

{|align=right
|__TOC__
|}
[http://www.google.com/trends?q=openmoko%2Cneo1973&ctab=1&geo=all&date=all Openmoko et Neo1973 sur google trends.]

Ce site contient les références presse relatives à Openmoko triées par langue et date. Les dernières sont en haut.

== Langues ==

=== Anglais ===

==== Juillet 2007 ====
* [http://www.economist.com/science/displaystory.cfm?story_id=9531007 Economist.com] Hello world: Avoiding punitive roaming charges abroad
* [http://linuxdevices.com/news/NS7355980470.html linuxdevices.com] iPhone-like Linux phone ready for hackers
* [http://www.heise.de/english/newsticker/news/92473 heise.de] "Free your phone": The Openmoko Project's Linux Smartphone now available
* [http://blogs.zdnet.com/open-source/?p=1194 zdnet.com] Can Openmoko break the wireless monopoly?
* [http://developers.slashdot.org/developers/07/07/09/0049249.shtml Slashdot] Open Source Linux Phone Goes On Sale
* [http://www.engadget.com/2007/07/09/openmoko-neo-1973-and-advanced-dev-kit-finally-for-sale/ engadget.com] Openmoko Neo 1973 and Advanced dev kit finally for sale
* [http://www.theglobeandmail.com/servlet/story/RTGAM.20070703.WBcyberia20070703161759/WBStory/WBcyberia/ Globe and Mail, Toronto] The Next Big Thing? (good overview; some favorable comparisons with iPhone).
* [http://arstechnica.com/news.ars/post/20070710-developer-models-of-openmoko-open-source-smartphone-released.html arstechnica.com] Developer models of Openmoko open-source smartphone released
* [http://www.boingboing.net/2007/07/09/openmoko_linuxbased_.html boingboing (Cory Doctorow)] Openmoko: Linux-based $300 open smartphone
* [http://www.channelweb.co.uk/vnunet/news/2192036/first-open-source-mobile-phone channelweb.co.uk / CRN] Openmoko preps first open source mobile
* [http://www.makezine.com/blog/archive/2007/07/openmoko_300_linuxpowered.html?CMP=OTC-0D6B48984890 MAKE:] blogged about it.
* [http://www.theregister.co.uk/2007/07/09/neo_1973_launch/ The Register] Is your phone free?

==== June 2007 ====
* [http://fakesteve.blogspot.com/2007/06/freetards-are-trying-to-make-iphone.html Secret Diary of Steve Jobs] Les fous du libre tentent de faire un clone d'iphone
* [http://www.eweek.com/article2/0,1895,2152759,00.asp eweek.com] Openmoko: une alternative à l'Iphone pour les développeurs?
* [http://www.linuxdevices.com/news/NS8509737406.html&cid=0 linuxdevices.com] iPhone-like Linux phone delayed
* [http://www.itweek.co.uk/vnunet/news/2192036/first-open-source-mobile-phone IT Week] "Openmoko preps first open source mobile" Confuses Phase 1 and Phase 2 features.
* [http://www.vnunet.com/vnunet/news/2192036/first-open-source-mobile-phone vnunet.com] First open source mobile phone
* [http://www.techeblog.com/index.php/tech-gadget/feature-5-cool-linux-powered-phones TechEBlog.com] A brief line-up of the 5 coolest Linux-powered phones.
* [http://www.tectonic.co.za/view.php?id=1574 Tectonic.co.za] Open source phone plans September launch
* [http://www.hothardware.com/image_popup.aspx?image=big_fic2.jpg&articleid=979&t=a hothardware.com] Openmoko
* [http://www.texyt.com/FIC+Openmoko+$350+open+Linux+mobile+phone+launch+00100 Texyt.com] $350 open Linux mobile phone on target for September launch

==== May 2007 ====
* [http://blogs.sun.com/brewin/entry/fic_and_openmoko_thank_you blogs.SUN.com] FIC and Openmoko - Thank You
* [http://www.pikesoft.com/blog/index.php?itemid=174 PikeSoft.com] JavaFX Mobile: a new smartphone OS contender
* [http://www.sfgate.com/cgi-bin/blogs/sfgate/detail?blogid=19&entry_id=16310 SFGate.com] Here comes the Sun Conference
* [http://www.linuxdevices.com/news/NS7539760574.html LinuxDevices.com] Sun beams Linux/Java at mobile phones

==== April 2007 ====
* [http://www.palminfocenter.com/news/9371/openmoko-running-on-a-palm-tx/ Palm Infocenter] Openmoko running on a palm TX
* [http://jaidev.info/home/blog/archives/2007/04/13/openmoko.html JaidevInfo] Openmoko
* [http://www.wirelessweek.com/newsletter.aspx?id=137388 Wirelessweek.com] Democracy Hits the Mobile Phone
* [http://elearner.edublogs.org/2007/04/11/technologies-is-that-a-word/ Edublogs.org] Technologies is that a word?
* [http://www.linuxdevices.com/news/NS4777580627.html Linuxdevices.com] 200 million Linux phones to ship by 2012
* [http://arstechnica.com/news.ars/post/20070415-palm-embracing-linux-in-the-hopes-of-being-relevant-again.html Ars Technica] Palm embracing Linux in the hopes of being relevant again] (Mentions Neo1973 in passing)

==== March 2007 ====
* [http://www.smartdevicecentral.com/article/Openmokos+Open+Source+Phone/202546_1.aspx smartdevicecentral.com] Openmoko's open source phone
* [http://www.zdnetasia.com/news/communications/0,39044192,61996003,00.htm zdnet asia] Passing mention in an article on the Iphone.
* [http://www.wikio.com/news/Sean+Moss-Pultz wikio.com] Sean Moss-Pultz News
* [http://www.edparsons.com/?p=438 edparsons.com] iPhone chipping away at the walls
* [http://blogs.pcworld.co.nz/pcworld/techsploder/2007/03/openmoko_makes_total_sense.html blogs.pcworld.co.nz] Openmoko makes total sense
* [http://www.totalueberwachung.de/blog/articles/2007/03/08/neo1973-arrived totalueberwachung.de] Neo1973 arrived
* [http://www.makuchaku.info/blog/im-gonna-get-this-one makuchaku.info] I'm gonna get this one
* [http://www.kitenet.net/~joey/blog/entry/openmoko_and_n800.html kitenet.net] Openmoko and n800
* [http://dominion.kabel.utwente.nl/koen/cms/the-neo1973-unboxed dominion.kabel.utwente.nl] The Neo1973 unboxed
* [http://atulchitnis.net/diary/showentry/421 atulchitnis.net] An Openmoko Phone arrives
* [http://blog.matthewgast.com/2007/03/03/good-luck-openmoko blog.matthewgast.com] Good luck Openmoko
* [http://vaandoo.blogspot.com/2007/03/openmoko-neo1973-opensource-software.html vaandoo.blogspot.com] Openmoko Neo1973 opensource software
* [http://www.linuxdevices.com/news/NS7653749655.html linuxdevices.com] Openmoko update; Neo1973 on sale in March
* [http://www.ministryoftech.com/2007/03/05/the-5-hottest-phones-for-linux-fanatics/ ministryoftech.com] Brief line-up of the 5 hottest phones for Linux fans
* [http://voxilla.com/soapvox/2007/03/01/industry-disruption-really-168 voxilla.com] Article about ETel Sean Moss-Pultz presentation
* [http://blog.wired.com/gadgets/2007/03/eight_great_lin.html blog.wired.com] Gadget Lab: Eight Great Linux Smartphones
* [http://gigaom.com/2007/03/01/openmoko-phone/ gigaom.com] Openmoko Open-Source Mobile, coming soon - Interview with Sean Moss-Pultz
* [http://www.oreillynet.com/etel/blog/2007/03/openmoko_1.html www.oreillynet.com] ETel coverage
* [http://gordoncook.net/wp/?p=146 gordoncook.net] Short history of Neo1973 and other stuff
* [http://www.engadget.com/2007/03/03/openmoko-details-pricing-availability-for-neo1973/ engadget.com] Openmoko details pricing, availability for Neo1973
* [http://www.uberpulse.com/us/2007/03/fic_wants_to_rewrite_the_rules_with_open_moko_mobile_phone.php www.uberpulse.com] Some images from ETel

==== February 2007 ====
* [http://www.scullen.ca/2007/02/15/forget-about-the-iphone-neo1973-is-far-more-exciting/ scullen.ca] Forget about the iPone, Neo1973 is far more exciting
* [http://www.mobileread.com/forums/showpost.php?p=59124&postcount=4 mobileread.com] Show post
* [http://www.pdasnews.com/articles/2568/1/ pdasnews.com] Linux-powered iPhone killer available online in March
* [http://www.belutz.net/2007/02/05/openmoko/ belutz.net] Openmoko
* [http://www.mail-archive.com/community@lists.openmoko.org/msg03686.html mail-archive.com] Openmoko community mail archive
* [http://www.maclife.com/article/is_three_a_crowd_in_the_touch_screen_phone_arena maclife.com] Is there a crowd in the touch screen phone arena
* [http://gopaultech.com/2007/02/fic-neo1973-linux-smartphone/ gopaultech.com] FIC Neo1973 Linux smartphone
* [http://www.volweb.cz/horvitz/os-info/news-feb07-014.html volweb.cz] Open-source smartphone, with WiFi in version 2
* [http://www.oreillynet.com/etel/blog/2007/02/etel_coverage_openmoko_opens_t.html oreillynet.com] ETel coverage Openmoko opens
* [http://www.mobilewhack.com/openmoko-neo1973-open-source-phone/ mobilewhack.com] Openmoko Neo1973 open source phone
* [http://www.engadget.com/2007/02/19/what-tech-would-the-presidents-rock-in-2007/ engadget.com] What tech would the presidents rock in 2007
* [http://www.tuxmachines.org/node/13602 tuxmachines.org] What participation culture
* [http://www.vanille-media.de/site/index.php/category/opensource/openmoko/ vanille-media.de] Opensource Openmoko
* [http://www.joetech.com/2007/02/15/openmoko-open-source-cell-phone/ joetech.com] Openmoko open source cell phone
* [http://www.makezine.com/blog/archive/2007/02/openmoko_open_s.html makezine.com] Openmoko open
* [http://www.linuxdevices.com/news/NS9706477996.html linuxdevices.com] Announce of the Openembedded booth at FOSDEM in Brussels.
* [http://www.linuxdevices.com/news/NS2657814070.html linuxdevices.com] Quick interview with Sean and some pictures
* [http://gizmodo.com/gadgets/smartphones/first-look-the-antiiphone-openmokos-neo1973-236841.php gizmodo.com] Photos and comments on hardware and software
* [http://www.onecompare.com/mobile-news/article-asp~aid~244~pub~56321102~story~openmoko-launch-the-official-portal-for-development-of-the-openmoko-platform onecompare.com] Short news article
* [http://crunchgear.com/2007/02/15/openmokos-open-source-mobile-os crunchgear.com] Holding the phone upside down
* [http://www.slashgear.com/openmoko-and-fic-neo1973-updates-153926.php slashgear.com] Video interview and many pictures
* [http://www.djlosch.com/article_Comparison%3A_iPhone_vs_A1200_vs_Neo1973 djlosch.com] Article comparing the Neo to the iPhone and A1200
* [http://popsci.typepad.com/popsci/2007/02/up_close_and_pe.html popsci.typepad.com] Screenshot of Linux booting on the Neo
* [http://video.google.de/videoplay?docid=-3742589179435830945&q=Openmoko video.google.com] Presentation of Openmoko at the FOSDEM
* [http://www.manilastandardtoday.com/?page=business6_feb27_2007 manilastandardtoday.com] Tale of two phones
* [http://blog.printf.net/articles/2007/02/22/unboxing-the-openmoko-phone blog.printf.net] OLPC and older Neo1973.
* [http://mako.cc/copyrighteous/freesoftware/20070228-00.html mako.cc] OLPC and older Neo1973 again.
* [http://www.maclife.com/article/is_three_a_crowd_in_the_touch_screen_phone_arena MacLife] Is Three a Crowd among Touch-Screen Phones?

==== January 2007 ====
* [http://blogs.ft.com/techblog/2007/01/openmoko_harks_.html blogs.ft.com] Openmoko harks back to hello moto
* [http://opensource.sfsu.edu/node/258 opensource.sfsu.edu] Can you hear me now?
* [http://losca.blogspot.com/2007/01/maemo-nokia-n800-has-competitor-in.html losca.blogspot.com] Maemo Nokia n800 has competitor in openness - Openmoko
* [http://21talks.net/voip/openmoko 21talks.net] Openmoko: Not as sexy as the iPhone, but it’s a Linux phone
* [http://www.linuxinfusion.com/openmoko-schedule-announced linuxinfusion.com] Openmoko schedule announced
* [http://users.livejournal.com/_paladine_/tag/smartphone users.livjournal.com] The Worlds First Opensource Linux Smartphone
* [http://www.nungee.com/2007/01/25/openmoko/ nungee.com] Openmoko
* [http://www.sda-asia.com/sda/features/psecom,id,880,srn,2,channel,developer,nodeid,21,_language,Singapore.html sda-asia.com] Openmoko Offers Open-source Smart phone T
* [http://www.regdeveloper.co.uk/2007/01/15/open_phone/ regdeveloper.co.uk] Open Phone
* [http://www.product-reviews.net/2007/01/17/fic-neo1973-smartphone-open-source-phone/ product-reviews.net] FIC Neo1973 smartphone open source phone
* [http://gizmodo.com/gadgets/smartphones/openmoko-smartphone-did-they-have-a-time-machine-or-what-229243.php gizmodo.com] Openmoko smartphone did they have a time machine or what
* [http://www.oreillynet.com/conferences/blog/2007/01/openmoko_workshop_added_to_ete.html oreillynet.com] Openmoko workshop added to ETel
* [http://www.gadgetell.com/2007/01/openmoko-gets-interviewed-about-new-open-source-fic-neo1973/ gadgetell.com] Openmoko gets interviewed about new open source FIC Neo1973
* [http://www.slashgear.com/openmoko-interface-im-loving-it-173496.php slashgear.com] Openmoko interface I'm loving it
* [http://www.gadgetorama.com/news/news_details.php?gorid=2008 gadgetorama.com] Openmoko news details
* [http://tech.cybernetnews.com/2007/01/17/openmoko-vs-iphone-did-apple-copy/ tech.cybernetnews.com] Openmoko vs iPhone did Apple copy
* [http://techtrails.blogspot.com/2007/01/open-phones-with-open-moko-while.html techtrails.blogspot.com] Open phones with Openmoko while
* [http://blogger.xs4all.nl/jurjen1/archive/2007/01/17/174341.aspx bloger.xs4all.nl] Openmoko open source mobile phone
* [http://www.ringnokia.com/2007/01/i_am_highly_cur.html ringnokia.com] I'm highly curious
* [http://www.oreillynet.com/etel/blog/2007/01/iclone_1.html oreillynet.com] iClone
* [http://forums.scotsnewsletter.com/index.php?showtopic=17685 forums.scotsnewsletter.com] Show topic
* [http://understandinglimited.com/2007/01/15/iphone/ understandinglimited.com] iPhone and Openmoko
* [http://robertogaloppini.net/2007/01/12/openmoko-the-integrated-os-mobile-communications-platform-2/ robertogaloppini.net] Openmoko the intergrated OS mobile communications platform
* [http://www.funambol.com/blog/capo/2007/01/apple-please-do-not-forget-developers.html funambol.com] Apple please do not forget developers
* [http://chopey.blogspot.com/2007/01/iphone-or-not-to-iphone.html chopey.blogspot.com] iPhone or not to iPhone
* [http://opendotdotdot.blogspot.com/2007/01/openmoko.html opendotdotdot.blogspot.com] Openmoko
* [http://www.e-pcmag.gr/forum/index.php?showtopic=19505 e-pcmag.gr] Show topic
* [http://www.costpernews.com/2007/01/12/anything-you-can-do-we-can-do-better/ costpernews.com] Anything you can do we can do better
* [http://www.tectonic.co.za/view.php?id=1321 tectonic.co.za] iPhone vs Openmoko - the Open Alternative
* [http://lwn.net/Articles/217020/rss lwn.net] An Openmoko update
* [http://www.networkworld.com/news/2007/010907-moss-pultz.html networkworld.com] Q&A Building a new open source phone platform
* [http://www.networkcomputing.com/showArticle.jhtml?articleID=196802226 networkcomputing.com] Startup Promises First Linux Smartphone Based On Open Standards
* [http://www.osweekly.com/index.php?option=com_content&task=view&id=2420&Itemid=449 osweekly.com] Mobile Devices Adopt Open Source
* [http://www.linuxdevices.com/news/NS8591201260.html linuxdevices.com] Linux phone market open up?
* [http://www.pcmag.com/article2/0,1895,2080727,00.asp pcmag.com] Cell phone open up
* [http://sonyericssonz558i.blogurple.com/2007/01/06/23/ sonyericssonz558i.blogurple.com] Sony Ericsson Z558i
* [http://www.sannes.org/?p=5 sannes.org] An Open mobile phone that does what you want
* [http://popsci.typepad.com/ces2007/2007/01/opensource_stri.html Popsci.com] Open Source Strikes Again
* [http://gizmodo.com/gadgets/smartphones/openmoko-smartphone-did-they-have-a-time-machine-or-what-229243.php Gizmodo.com] Openmoko interface compared to iPhone
* [http://www.linuxjournal.com/xstatic/abstracts/upfront Linux Journal] Doc Searls in the feb 2007 issue
* [http://www.osdir.com/Article9642.phtml OSDir.com] Mobile Linux for the Mobile Fan] -> [http://www.madpenguin.org/cms/?m=show&id=7710 MadPenguin] Mobile Linux for the Mobile Fan
* [http://www.usnews.com/usnews/biztech/davesdownload/archive/070112/a_populist_challenge_to_apples.htm US News] A Populist Challenge to Apple's iPhone
* [http://www.tectonic.co.za/view.php?id=1321 tectonic.co.za] iPhone vs Openmoko: The open alternative
* [http://www.informationweek.com/news/showArticle.jhtml?articleID=196802206&subSection=All+Stories InformationWeek] Startup Promises First Linux Smartphone Based On Open Standards
* [http://www.theregister.co.uk/2007/01/15/open_phone/ The Register] Open Phones with Open Moko
* [http://techreport.com/onearticle.x/11589 The Tech Report] Openmoko offers open-source smart phone
* [http://blogs.ft.com/techblog/2007/01/openmoko_harks_.html Financial Times] Openmoko harks back to Hello Moto
* [http://hardware.slashdot.org/article.pl?sid=07/01/20/1551200 Slashdot] Openmoko Schedule Announced
* [http://www.youtube.com/watch?v=jRvtAAXTIlg Youtube] Interview with Sean Moss-Pultz ([http://www.monoploid.be/dl/openmoko_sean_interview.ogm mirror in Ogg format])
* [http://www.libervis.com/article/forget_iphone_hail_openmoko_the_true_revolution Libervis.com] Forget iPhone, hail Openmoko, the true revolution
* [http://gizmodo.com/gadgets/smartphones/sizemodo-iphone-vs-openmoko-neo1073-229294.php Gizmodo]iPhone vs. Openmoko Neo1973] (please, don't mind the typo i n the title)

==== December 2006 ====
* [http://www.pikesoft.com/blog/index.php?itemid=133 pikesoft.com] Cheap, totally open Linux phone will ship next month
* [http://www.cdrinfo.com/Sections/News/Details.aspx?NewsId=19254 cdrinfo.com] FIC to release Linux based Smartphone

==== November 2006 ====
* [http://www.ministryoftech.com/2006/11/09/fic-neo1973-smartphone-with-linux-based-openmoko-open-source-platform/ ministryoftech.com] FIC Neo1973 smartphone with linux-based Openmoko open source platform
* [http://www.mobiletechnews.com/info/2006/11/09/124614.html mobiletechnews.com] Openmoko Linux mobile platform and Neo1973 smartphone announced
* [http://news.softpedia.com/news/FIC-Neo1973-for-all-the-Linux-Lovers-out-There-40344.shtml news.softpedia.com] FIC Neo1973 for all the Linux lovers out there
* [http://www.openembedded.org/openmoko-fic-choosing-openembedded openembedded.org] Openmoko FIC choosing openembedded
* [http://news.com.com/2300-1037_3-6134795-1.html news.com.com] FIC's Linux handset
* [http://www.slashphone.com/77/5784.html slashphone.com] Openmoko Announces Open Source Mobile Communications Platform
* [http://www.arm.com/iqonline/news/marketnews/15616.html arm.com] Open Linux Based, ARM Powered Mobile In Wings
* [http://news.com.com/Second+open+Linux+handset+unveiled/2100-1039_3-6133974.html news.com.tw] Second open Linux handset unveiled
* [http://www.infoworld.com/article/06/11/08/HNlinuxphone_1.html?COMMERCIAL%20LINUX infoworld.com] FIC debuts open Linux-based smartphone
* [http://www.michaeldolan.com/431 michaeldolan.com] A must have: Openmoko cell phone with GPS and...apt-get
* [http://nandz.blogspot.com/2006/11/my-dream-phone.html nandz.blogspot.com] My dream phone
* [http://www.linuxdevices.com/news/NS2986976174.html linuxdevices.com] Cheap, hackable Linux smartphone due soon
* [http://www.linuxdevices.com/news/NS7056478804.html linuxdevices.com] First OpenMoKo phone taps dual-licensed SyncML stack
* [http://lwn.net/Articles/208298/ lwn.net] The Openmoko open phone
* [http://www.theinquirer.net/default.aspx?article=35590 theinquirer.net] A truly open Linux phone with GPS debuts

=== German ===
==== July 2007 ====
* [http://lists.openmoko.org/pipermail/community/attachments/20070721/be55235c/CIMG1129_small-0001.jpg Kurier] Handy Individuell
* [http://futurezone.orf.at/produkte/stories/206048/ futurezone.ORF.at] Anti-iPhone geht an den Start
* [http://www.zdnet.de/news/hardware/0,39023109,39156101,00.htm zdnet.de] Open-Source-Iphone wird mit Hackertools ausgeliefert
* [http://www.heise.de/newsticker/meldung/92393 heise.de] "Free your phone": Linux-Smartphone des Openmoko-Projekts verfügbar
* [http://www.spiegel.de/netzwelt/mobil/0,1518,493595,00.html spiegel.de] Linux statt iPhone: Freiheit fürs Handy

==== June 2007 ====
* [http://www.golem.de/0706/53172.html golem.de] - Linux-Smartphone Openmoko ab Juli 2007 zu haben
* [http://www.heise.de/newsticker/meldung/91868 heise.de] - Offenes Linux-Smartphone Neo 1973 macht Fortschritte
* [http://www.winfuture.de/news,32641.html winfuture.de] - Open-Source-Handy Neo1973 ab Juli bzw. Oktober
* [http://www.pro-linux.de/news/2007/11385.html pro-linux.de] - Openmoko wird zum Unternehmen
* [http://de.theinquirer.net/2007/06/14/das_erste_openmoko_kommt.html the inquirer] - Das erste OpenMOKO kommt

==== April 2007 ====
* [http://www.pro-linux.de/news/2007/11133.html pro-linux] - Openmoko produziert erste Muster
* [http://www.golem.de/0704/51970.html golem.de] - Open-Source-Handy vor Produktionsbeginn

==== March 2007 ====
* [http://chaosradio.ccc.de/cre042.html Chaosradio Express] - Das neue Projekt zur Entwicklung eines Telefons mit freier Software
* [http://www.pro-linux.de/news/2007/10966.html pro-linux] - Openmoko sucht Unterstützung

==== February 2007 ====
* [http://www.digital-living-magazin.de/index.php?pid=17&art=2050&cid=DLnewsletter digital-living-magazin.de] - Linux erobert Mobilfunkmarkt
* [http://www.heise.de/tr/artikel/85138 Technology Review] - Open-Source-Handy, nächster Versuch
* [http://www.pro-linux.de/news/2007/10833.html pro-linux] - Openmoko-Quellcode angekündigt
* [http://www.heise.de/newsticker/meldung/85354 heise online] - Openmoko: Linux-Plattform für Handys freigegeben
* [http://www.mobile2day.de/news/news_details.html?nd_ref=6870&n_multi=0&nf_id=0&nt_id=0&f_date_m=01&f_date_y=2007&t_date_m=04&t_date_y=2007&from=archive Mobile2Day] - Openmoko bringt Details zum Neo1973

==== November 2006 ====

* [http://golem.de/0611/48824.html golem.de] - Openmoko kündigt Open-Source-Handy an
* [http://www.heise.de/newsticker/meldung/80714 heise online] - Smartphone mit offener Linux-Plattform
* [http://www.pro-linux.de/news/2006/10448.html pro-linux] - Offenes Linux-Smartphone »Openmoko« für Januar 2007 angekündigt

=== Scandinavian ===

* [http://www.amobil.no/artikkel/mobiltelefoner/antikrist-mobilen_blir_heftigere/41042 Amobil.no] Antikrist-mobilen blir heftigere
* [http://www.amobil.no/sniktitt/mobiltelefoner/den_folsomme_linux-mobilen/40176 Amobil.no] Sniktitt: Den følsomme Linux-mobilen
* [http://www.amobil.no/artikkel/markedsutvikling/linux-mobilen_er_i_rute/40138 Amobil.no] Linux-mobilen er i rute
* [http://www.amobil.no/nyhet/mobiltelefoner/openmoko_klart_for_verden/36554 Amobil.no] Openmoko klart for verden
* [http://www.nyteknik.se/art/48697 NyTeknik] Snart är den öppna Linuxtelefonen här (Swedish) (Translation: this article states free release to selected developers Feb 11, commercial release to developers March 11, and main release to market Sep 11. See also [http://lists.openmoko.org/pipermail/announce/2007-January/000000.html])

=== French ===
* [http://linuxfr.org/2006/11/08/21596.html LinuxFR] Openmoko : sortie en janvier d'un téléphone-GPS enfin libre!

=== Chinese ===

* [http://openmoko.wordpress.com/2007/06/21/openmoko-%E8%88%87-iphone-%E6%AF%94%E8%BC%83%E4%B8%80/ wordpress.com] Comparison between Openmoko and iPhone
* [http://chinese.engadget.com/2007/06/11/computex-2007-openmoko-neo-1973-linux/ chinese engadget.com] Openmoko Neo1973 Linux Smartphone
* [http://people.debian.org.tw/~chihchun/2007/05/25/talk-of-openmoko-is-online/ debian.org.tw] Video of Openmoko at TOSSUG in Taipei
* [http://people.debian.org.tw/~chihchun/2007/05/17/openmoko-at-tossug/ debian.org.tw] Openmoko at TOSSUG
* [http://magicdesign.blogspot.com/2007/05/free-your-phoneopenmoko.html MagicDesign] Free your phone Openmoko
* [http://people.debian.org.tw/~chihchun/2007/04/30/have-fun-with-openmokoneo1973/ Debian.org.tw] Have fun with Openmoko Neo1973
* [http://orzlab.blogspot.com/ Orzlab] When Java meets Openmoko
* [http://blog.footoo.org/?p=115 FooToo.org] Install Openmoko Emulator
* [http://www.jollen.org/blog/2007/01/openmoko_announce.html Jollen.org] Openmoko Kick-Off
* [http://zh.wikipedia.org/wiki/Openmoko Wikipedia.org] Openmoko Chinese Wiki
* [http://tw.myblog.yahoo.com/champ_yen/article?mid=211&prev=212&next=-1 Yahoo.com.tw] Forget about iPhone, Hail Openmoko
* [http://www.jollen.org/blog/2006/11/mobile_20_openmoko_linux_smart.html Jollen.org] Openmoko Linux Smartphone
* [http://blog.roodo.com/ystuan/archives/2733869.html Roodo.com] Openmoko

=== Polish ===
==== May 2007 ====
* [http://www.studencka.pl/artykuly.php?AID=770 Gazeta Studencka] (Students Newspaper) "Cellphones of all shapes, unite!" - Openmoko overview by Krzysztof Kajkowski, "free software" not mentioned in the text.

=== Japanese ===

* [http://blog.pasonatech.co.jp/hibi/4079.html pasonatech.co.jp] iPhoneキラー？：オープンソース精神なopenmoko携帯がUSで発売
* [http://journal.mycom.co.jp/articles/2007/06/06/computex04/index.html journal. mycom.com.jp] Computex Taipei 2007

=== Italian ===

==== July 2007 ====
* [http://www.corriere.it/Primo_Piano/Scienze_e_Tecnologie/2007/07_Luglio/10/neo1973_telefonino.shtml corriere.it] L'anti iPhone: Neo 1973, il cellulare fai da te
* [http://punto-informatico.it/p.aspx?id=2035879 Punto Informatico] Lo smartphone touch-screen è open source

{{Languages|Press_Coverage}}

[[Category:Community/fr]]
[[Category:Openmoko Inc/fr]]

News Archive/fr

2012-03-09T03:29:10Z

Glenn: catchg

News de la page d'accueil du Wiki Openmoko

== 2008 ==

=== 2008-09 ===

* 2008-09-17: [[Community_Updates/2008-09-17|Community update]] - Activity since launch
* 2008-09-02: Trolltech [http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=83 released] Qtopia 4.3.3-snapshot.

=== 2008-08 ===

* 2008-08-28: Trolltech [http://n2.nabble.com/qtopia-4.3.2-release-tp789148p789148.html released] Qtopia 4.3.2.
* 2008-08-26: Openmoko [http://lists.openmoko.org/pipermail/community/2008-August/027997.html updates] [[Om 2008.8]] distribution.
* 2008-08-15: [[Debian]] on the FreeRunner [http://n2.nabble.com/Debian-on-the-FreeRunner----now-official-td726410.html announced] (instructions for [http://wiki.debian.org/DebianOnFreeRunner FreeRunner] and [http://wiki.debian.org/DebianOnNeo1973 Neo1973]).
* 2008-08-08: Openmoko team [http://lists.openmoko.org/pipermail/community/2008-August/025602.html releases] distribution formerly called ASU as [[Om 2008.8]] .
* 2008-08-4/5: Openmoko is at Linuxworld, San Francisco

=== 2008-07 ===

* 2008-07-25: Community helps, [[GPS Problems]] fixed
* 2008-07-20: [http://wiki.openmoko.org/wiki/Debian Debian] added to the Distributions page

=== 2008-06 ===

* 2008-06-27: Neo FreeRunner shipping in the [http://lists.openmoko.org/pipermail/community/2008-June/019943.html material world]

[[Category:Community Update]]
[[Category:Openmoko Inc/fr]]

Introduction/fr

2012-03-09T03:28:57Z

Glenn: catchg

{{Languages|Introduction}}

{{Introbox}}

Openmoko est en train de créer le premier framework au monde complétement libre pour téléphone portable.

Nous imaginons une standardisation ascendante(définie et implémentée par la communauté), plutot que descendante(définie par un consortium).

Pour une introduction plus complète voyez [http://lists.openmoko.org/pipermail/announce/2007-January/000000.html cette annonce]

'''Production matérielle Openmoko Inc''': des téléphones portables compatibles avec les distributions logicielles libres. Le premier téléphone Openmoko fut le FIC [[Neo1973]], suivi par le modèle actuel, le [[Neo FreeRunner/fr|Neo FreeRunner]]. Les utilisateurs peuvent librement choisir d'utiliser un autre système d'exploitation qu'Openmoko sur leur smartphone Openmoko -- voir [[Distributions]] pour les connaître.

'''Production logicielle Openmoko Inc''': Le système d'exploitation et les applications pour les téléphones Openmoko. La distribution logicielle actuelle est la [[Om 2008.8]]. Attention, les téléphones Neo FreeRunners achetés récemment sont toujours livrés avec la [[Om 2007.2]]. Openmoko est supportée par toute sorte de [[Supported Hardware|Téléphones mobiles compatibles Linux]] ou [[Openmoko_under_QEMU/fr|émulateur]].

Cette initiative a été lancée par '''FIC Inc'''. et [http://www.openmoko.com Openmoko, Inc.]

== Téléphones ==

{|
| [[Image:GTA02.gif|170px]] || [[Image:FIC-neo1973_small.jpg|200px]]
|-
| [[Neo FreeRunner]] || [[Neo 1973]]
|}

== Logiciel ==

{|
| [[Image:Om2008 home.png|200px]] || [[Image:Main.png|200px]]
|}

[[Om 2008.8]] Copies d'écrans du logiciel.

== Audio ==
* [http://chaosradio.ccc.de/cre042.html Chaosradio Express avec Tim Pritlove et Harald Welte (en allemand)]

== Videos ==
* [http://www.youtube.com/watch?v=jRvtAAXTIlg World Debut: Le premier téléphone portable complétement libre]
* [http://www.youtube.com/watch?v=tQPjfUqp-dk&mode=related&search= Neo1973 Vidéo promotionnelle (rapide aperçu du matériel et du logiciel)]
* [http://people.openmoko.org/mickey/videos/dialer-xvid.avi Neo1973 effectuant un appel. Video courtesy Daniel 'alphaone' Willmann]
* [http://video.google.co.uk/videoplay?docid=-3742589179435830945&hl=en-GB Video Google sur la présentation de Openmoko par Sean Moss Pultz au FOSdem le 23 Fevrier 2007.]
* [http://rapidshare.com/files/18781887/rect.avi Même version que ci-dessus, en meilleure résolution, zoomé, et rétroprojeté.]
* [http://video.google.com/videoplay?docid=-8574715471341709984 Openmoko à Tossug], Présenté par Sean Moss Pultz et Harald Welte à Taipei Open Source Software User Group (TOSSUG)
* [http://people.openmoko.org/ninjutsu/NinjutsuVol1pt1.mp4 MokoNinja infiltre FIC] Avec Mickey, Harald, The Neo, et bien d'autres..
* [http://people.openmoko.org/ninjutsu/NinjutsuVol1pt2.mp4 Video playback on Neo1973 (sort of..)] Par Dr. Michael 'Mickey' Lauer
* [http://www.youtube.com/watch?v=5D6i6vLlhGA Demonstration de l'A-GPS sur le Neo1973] par mokoNinja sur YouTube
* [http://people.openmoko.org/ninjutsu/AGPS_Neo1973.mp4 Demonstration de l'A-GPS (version téléchargeable)] Faite par Lil' Sean
* [http://people.openmoko.org/ninjutsu/PhoneCall.MPG Neo1973 Phone Call] Depuis le dernier développement de l'interface utilisateur
* [http://people.openmoko.org/ninjutsu/Contacts.MPG Contacts] Développement de l'IHM depuis OpenedHand
* [http://people.openmoko.org/ninjutsu/RssFeed.mpg RSS FeedReader] Développement de l'IHM depuis OpenedHand
* [http://www.youtube.com/watch?v=hn7wuxlTNvs TangoGPS] at YouTube

== Photos ==

=== Extérieur ===
[[Image:FIC-neo1973_small.jpg|200px|frontside]]
[[Image:Neo1973_uboot_splash.jpg|200px|bootloader splash screen]]
[[Image:Gta01b v3 case back white.jpg|200px|backside]]

Liens externes [http://blog.printf.net/articles/2007/02/22/unboxing-the-openmoko-phone In operation to see screen clarity]

Voir aussi [[Wishlist:Neo1973 P0 Review]]

=== Intérieur ===
[[Image:Gta01b v3 top.jpg|200px|display (top) side]]
[[Image:Gta01b v3 bottom.jpg|200px|component (back) side]]
[[Image:Gta01b v3 case top open pcb lifted.jpg|200px|case top open pcb lifted]]
[[Image:Gta01b v3 case top open pcb lift white.jpg|200px|case top open pcb lift white]]
[[Image:Gta01b v3 case top open white.jpg|200px|case top open white]]

[[Category:Openmoko Inc/fr]]

Category:Categories/fr

2012-03-09T03:28:25Z

Glenn: new

Category:Openmoko Inc/nl

2012-03-09T03:27:56Z

Glenn: new

{{Languages|:Category:Openmoko Inc}}

[[Image:Openmoko-logo2.png|right]]

[[Category:Categories/nl]]

Category:Openmoko Inc/fr

2012-03-09T03:27:35Z

Glenn: new

{{Languages|:Category:Openmoko Inc}}

[[Image:Openmoko-logo2.png|right]]

[[Category:Categories/fr]]

Introduction old/cs

2012-03-09T03:26:38Z

Glenn: catchg

{{Languages|Introduction}}

{{Warning|this page is only for archive}}

Openmoko je projekt, který si klade za cíl vytvořit první zcela svobodné programové vybavení pro mobilní telefony na světě.

We believe in standardization bottom-up (defined and implemented by the community), instead of top-down (defined by a consortium).

Věříme v přístup zdola nahoru (bottom-up), tedy v definici a implementaci projektu komunitou, místo přístupu shora dolů (top-down), tedy definicí společností.

Pro získání více informací můžete shlédnout [http://lists.openmoko.org/pipermail/announce/2007-January/000000.html následující ohlášení] (v angličtině).

Openmoko je vyvíjené tak, aby běželo na všech druzích zařízení schopných běhu operačního systému Linux. První takto podporovaným Openmoko telefonem je FIC Neo1973.

Tento projekt byl započat společnostmi [[FIC|FIC, Inc.]] a [http://www.openmoko.com Openmoko, Inc.]

== Zvukové záznamy ==
* [http://chaosradio.ccc.de/cre042.html Chaosradio Express s Timem Pritlovem a Haraldem Weltem (německo)]

== Videa ==
* [http://people.openmoko.org/mickey/videos/dialer-xvid.avi Telefonní hovor na Neo1973. Video od Daniela 'alphaone' Willmanna]
* [http://video.google.co.uk/videoplay?docid=-3742589179435830945&hl=en-GB Google Video s výkladem o Openmoko od Seana Mosse Pultze na FOSdemu, 23. února 2007.]
* [http://rapidshare.com/files/18781887/rect.avi Kvalitnější verze výše zmíněného výkladu.] S čitelným textem.
* [http://video.google.com/videoplay?docid=-8574715471341709984 Openmoko v Tossugu], Předvedené Seanem Mossem Pultzem a Haralde Weltem na Taipei Open Source Software User Group (TOSSUG)
* [http://people.openmoko.org/ninjutsu/NinjutsuVol1pt1.mp4 MokoNinja infilturuje FIC] Hrají Mickey, Harald, The Neo, a další..
* [http://people.openmoko.org/ninjutsu/NinjutsuVol1pt2.mp4 Přehrávání videa na Neo1973 (pokus..)] ByOd Dr. Michaela 'Mickey' Lauera
* [http://www.youtube.com/watch?v=5D6i6vLlhGA AGPS Demo na Neo1973] Od mokoNinji na YouTube
* [http://people.openmoko.org/ninjutsu/AGPS_Neo1973.mp4 AGPS Demo a test výdrže při pádu (ke stažení)] POd Lil' Seana

== Fotografie ==

=== Zevnějšek ===
[[Image:FIC-neo1973_small.jpg|200px|Pohled zepředu]]
[[Image:Neo1973_uboot_splash.jpg|200px|Úvodní obrazovka]]
[[Image:Gta01b v3 case back white.jpg|200px|Pohled zezadu]]

Odkaz na Internet [http://blog.printf.net/articles/2007/02/22/unboxing-the-openmoko-phone V provozu pro posouzení kvality displeje].

Mrkněte také na [[Wishlist:Neo1973 P0 Review | P0 recenzi]].

=== Vnitřek ===
[[Image:Gta01b v3 top.jpg|200px|Displej]]
[[Image:Gta01b v3 bottom.jpg|200px|Deska komponent]]
[[Image:Gta01b v3 case top open pcb lifted.jpg|200px|case top open pcb lifted]]
[[Image:Gta01b v3 case top open pcb lift white.jpg|200px|case top open pcb lift white]]
[[Image:Gta01b v3 case top open white.jpg|200px|case top open white]]

[[Category:Openmoko Inc/cs]]

Introduction/it

2012-03-09T03:24:30Z

Glenn: catchg

{{Languages|Introduction}}

Openmoko è un progetto dedito a creare smartphones con uno stack completamente Opensource.

'''Hardware rilasciato da Openmoko Inc''': Sono telefoni rilasciati da Openmoko Inc, pienamente compatibili con lo stack Opensource di Openmoko. Il primo telefono è stato il [[Neo 1973/it|Neo 1973]], seguito dal modello corrente, il [[Neo Freerunner/it|Neo Freerunner]]. Gli utenti sono liberi di installare ed eseguire un altro sistema operativo sul loro terminale -- Guardare [[Distributions/it|Distribuzioni]] per sapere di più.

'''Software rilasciato da Openmoko Inc''': Il sistema operativo e le applicazioni disponibili per i cellulari Openmoko. Lo stack corrente è [[Om 2008.12]], ma è tuttora sotto sviluppo [[Om 2009]].

Quest'iniziativa è stata ideata da FIC Inc. e Openmoko, Inc.

Lo stack Openmoko, che include un server X completo, consente a utenti e sviluppatori di trasformare piattaforme hardware mobile in prodotti unici. La nostra licenza fornisce a sviluppatori ed utenti la libertà di personalizzare esternamente i propri dispositivi o ricostruirli modificandoli radicalmente, di trasformare il telefono, per esempio, in un dispositivo medico, o in un dispositivo di vendita, o la libertà di installare semplicemente il proprio software preferito. Oltre a rendere libero il software sui nostri dispositivi, sono stati anche rilasciati i file CAD sotto licenza Creative Commons. Liberando il codice sotto GPL, si è data alla community degli sviluppatori FOSS la possibilità di "rifarlo da capo". Liberando i file CAD si è data a designer industriali e ingegneri la medesima opportunità.

== Telefoni ==

{|
| [[Image:Neo.jpg|170px]] || [[Image:FIC-neo1973_small.jpg|200px]]
|-
| [[Neo FreeRunner]] || [[Neo 1973]]
|}

== Software ==

{|
| [[Image:Om2008 home.png|200px]] || [[Image:Main.png|200px]]
|}

[[Om 2008.12]] screenshots.

{|
| [[Image:Paroli-bubble.png|200px]] || [[Image:Paroli-rail.png|200px]]
|}

[[Om 2009]] screenshots

== Video ==
* [http://www.youtube.com/watch?v=jRvtAAXTIlg World Debut: The First Completely Open Mobile Phone] Interview with Sean Moss Pultz.
* [http://video.google.co.uk/videoplay?docid=-3742589179435830945&hl=en-GB Talk about Openmoko by Sean Moss Pultz at FOSdem] on 23rd Feb 2007. [http://rapidshare.com/files/18781887/rect.avi High resolution version] with the screen zoomed and transformed to the projector screen, text readable.
* [http://video.google.com/videoplay?docid=-8574715471341709984 Openmoko at Tossug], Presented by Sean Moss Pultz and Harald Welte at Taipei Open Source Software User Group (TOSSUG)
* [http://www.youtube.com/watch?v=hn7wuxlTNvs TangoGPS] presentation.

== Guarda anche ==

* [http://lists.openmoko.org/pipermail/announce/2007-January/000000.html Openmoko announcement]
* [http://blog.printf.net/articles/2007/02/22/unboxing-the-openmoko-phone Neo 1973 in operation to see screen clarity]
* [http://www.youtube.com/user/mokoNinja mokoNinja's videos on YouTube]

[[Category:Openmoko Inc/it| ]]

Category:Community/no

2012-03-09T03:22:48Z

Glenn: catchg

{{Languages|:Category:Community}}

[[Category:Categories/no]]

Category:Community/no

2012-03-09T03:16:22Z

Glenn: new

{{Languages|:Category:Community}}

[[Category:Categories]]

Category:Categories/no

2012-03-09T03:15:48Z

Glenn: -text (not translated)

Main Page/no

2012-03-09T03:15:07Z

Glenn: catchg

{{DISPLAYTITLE:Hovedsiden}} 

{{Languages|Main Page}}__NOTOC__

<pre style="color:red">This page is not completed or fully translated.</pre>

__NOEDITSECTION__[[Image:Neo front 3.gif|right]]
<div style="padding: 2.5ex; text-align: center; font: bold x-large sans">Openmoko™ - Åpen. Mobil. Fri.</div>
'''Openmoko™''' er ett prosjekt som arbeider med å levere mobiltelefoner med åpen kildekode. Openmoko var tidligere mer tilknyttet Openmoko Inc, men er nåtildags en sammenkomst av mennesker under slagordet "Free The Phone". Distributører selger nå oppdaterte utgaver av Openmoko Inc sin mobiltelefon som ble lansert i 2008, [[Neo FreeRunner]], for mer avanserte brukere, samtidig som programvaren(e) til FreeRunner og fremtidige telefoner er under utvikling av openmoko-samfunnet. En moderne 3G / OMAP3 oppgradering til FreeRunner, [http://projects.goldelico.com/p/gta04-main/ GTA04], kan forhåndsbestilles frem til Februar 2012, se under.

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

[[More Information|Mer Informasjon]]

===Bli Med===
Openmoko er ett prosjekt drevet av ett community bestående av lidenskapelige og intelligente frivillige personer. Om du har mulighet ville det være fint om du kunne bidra. Openmoko's ambitions far exceed the resources available.

* [[Community Resources|Community Ressurser]]
* [[Gta02-core|Create a new hardware revision of the gta02 hardware]] with completely free software tools for the hardware creation
* [[GTA04|Follow the ”GTA04” project by Golden Delicious Computers]]
* [[Create User Manuals|Skriv Bruker Manualer]] for [[Distributions|Distribusjoner]] and [[Applications|Applikasjoner]]
* Enhance the multi-device multi-vendor [[FSO]] middleware.

===Hvor Kan Jeg Kjøpe?===
Neo FreeRunner telefonen er til salgs hos diverse [[distributors|distributører]] rundtom i verden.

Dersom du allerede har en FreeRunner mobil, [http://www.handheld-linux.com/wiki.php?page=GTA04 GTA04 pre-order page is open!] - ''only'' if enough people will pre-order, mass-market GTA04 will become reality. Please spread the world to your FreeRunner owning friends.

See [[Getting Openmoko|Kjøpe Openmoko]] for more information.

----

====Nyhete====

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

----
Problems with this Site or a List? http://admin-trac.openmoko.org/trac
----

[[Category:Community/no| ]]
[[Category:Categories/no| ]]

Category:Categories/no

2012-03-09T03:14:38Z

Glenn: new

{{Languages|:Category:Categories}}

'''This is the root category,''' the starting point to navigate the wiki by browsing. We try to have a flat category/subcategory system. Both category names and subcategory names are allowable tags. It's also okay to give multiple tags to a page.

* '''[[:Category:Hardware|Hardware]]''' category tags describe pages according to functional subsystems: [[:Category:GPS|GPS]], [[:Category:USB|USB]], [[:Category:GSM|GSM]]...
* '''[[:Category:Applications|Applications]]''' category tag end-uses topics: [[:Category:Settings|Settings]], [[:Category:Networking|Networking]]...
* '''[[:Category:Distributions|Distributions]]''': [[:Category:Om 2008.8|2008.8]], [[Om 2008.12 Update]], [[:Category:Om 2009|Om 2009]] ([[:Category:FSO|FSO]] based), [[:Category:Debian|Debian]]...
* '''[[:Category:Maturity Level|Maturity Level]]''': from [[:Category:Ideas|Ideas]] (pre-alpha) to [[:Category:Implemented|Implemented]] (mostly β actually).
* '''[[:Category:Community|Community]]''' is about the social aspects of the Openmoko scene: [[:Category:Openmoko Local Groups|Local user groups]], [[:Category:Event|Events]]...

You can also see the [[Category overview|Categories overview Page]] for a general overview, [[Special:CategoryTree| search]] the categories, or see the complete [[Special:Categories| alphabetical listing]]. In the list below, the <nowiki>[+]</nowiki> sign opens subcategories.

GTA04 Group Tour Donations Hub

2012-03-06T18:50:16Z

Glenn: +Category:Community

= Background =
There is a GTA04 Group Tour (http://www.handheld-linux.com/wiki.php?page=GTA04%20Group%20Tour) to get enough units to reduce the price from currently 666 EUR to 479/499 EUR.
Unfortunately this is still too high for some members of the community, while others are willing to donate some money to make the group tour a success, but don't need two or more units.

= Idea =
To bring both parties together, please add yourself to this list if you are seeking a subsidy from a helpful donator.

= How to use this list =
Since you should also give something to the community, please formulate a project what you would like to work out.
Donators should scan this list and directly contact the project owner. If you agree, arrange for a single order in the online shop.

= Project List - seeking for donations =
-----

* Project: <please describe briefly what you want to contribute to the community if you had a GTA04>
* How much you could afford yourself: <e.g. 200 EUR>
* Date added: 6 mar 2012
* Your contact data: <email address>
-----

* Project: I want to improve the example driver of the 3.2 kernel and bring it upstream
* How much you could afford yourself: 200 EUR
* Date added: 6 mar 2012
* Your contact data: me@example.anywhere
-----

= Wish list - what potential donators would like to see =
* camera driver ported to Linux 3.2 and made working
* improved suspend
* FM transceiver
* <please add>

[[Category:Community]]

U-boot-gena2x

2012-02-23T05:33:57Z

Glenn: /* List of changes */ + (Solved problem?: )

{{Bootloader}}
I decided to put '''U-boot-gena2x''' - my version of [[U-Boot]] [[bootloader]] here, along with a short FAQ and list of known bugs. Please feel free to add your bugs or questions here.

The current version of U-Boot ([[U-Boot]] or U-boot-gena2x?) fully supports uploading and downloading via dfu, booting any known distro, is fully configurable, and has no known grave bugs.

== List of changes ==

This version of U-Boot is based on openmoko's stable branch of U-Boot. Git can be viewed [http://www.bsdmn.com/cgit/cgit/u-boot/ here].

Significant patches are:

Version 2:
* + (Solved problem?: ) [[GPS]] is not powered up on boot
* + Leave all serial ports setup to kernel
Version 1:
* + [[Smedia_Glamo_3362#Timing_settings|2-4-2 timings]]
* + GPS should work after resume

== Binaries ==
Public freerunners should have the same bootloader (board v5 and later).
Latest binary version is here:
* http://www.bsdmn.com/openmoko/uboot/binary/

to use U-Boot as NAND bootloader, you should flash the binary to the special partition:
sudo dfu-util -a u-boot -D u-boot_g2x_2.udfu

== How to setup ==
NAND U-Boot occupies 2 partitions on NAND, one partition for U-Boot itself and one for it's configuration.

To setup U-Boot, the easiest way is to edit the simple text file on your computer and then upload it to your phone with dfu-util.

Sample text config may be found [http://www.bsdmn.com/openmoko/uboot/config/environment.in here]. This version supports various kinds of boot options in the menu. You may use it as a sample for your config.

If you are switching from bootloader [[Qi]], just boot your distro with Qi, then do <code>cat /proc/cmdline</code> and compare/update the parameters in your config file.

Then you can edit the config file to fit your needs, you should prepare it (this adds crc):

get envedit.pl and crc32.pl from [http://svn.openmoko.org/trunk/src/host/devirginator/] and run:
./envedit.pl -s 262144 -f environment.in > u-boot_env.in
then flash resulting file to configuration partition:
sudo dfu-util -a u-boot_env -D u-boot_env.in

== Useful kernel options ==
{| class="standard"
|-
! option || description
|-
|root=/dev/mmcblk0p2|| rootfs is second partition on SD card
|-
|root=/dev/mtdblock6|| rootfs is on usual location on NAND
|-
|rootwait|| needed for booting from SD. force kernel to delay boot until sd card is ready. better than older rootdelay=
|-
|panic=20|| on kernel crash, reboot automatically after 20 second delay. useful for lindi's ramconsole patch
|-
|hardware_ecc=1|| use hardware ecc support for NAND, this is not default option use only if your rootfs NAND is flashed not with dfu-util, but with direct copy from sd. this speeds up NAND read on zlib-compressed ubi by 8%.
|-
|rootfstype=XX|| needed if your rootfs is ext2 to force kernel to use ext2 driver not ext3. use if kernel can't detect partition type
|-
|ubi.mtd=6,2048|| claim 6th mtd partition as ubi layer with 2048 page align
|-
|rootflags=compr=zlib,no_chk_data_crc|| mount options of rootfs, use no_chk_data_crc to speed up ubifs by 8%
|-
|mem=127M|| reserve 1Mb if you using lindi's ramcomsole patch
|}

== How to use ==

By default, if you press the 'power' button, the "bootcmd" from your config is executed, so set it up accordingly for your default distribution.

To see the boot menu and select desired boot method, hold 'power', wait 1 second and then hold 'aux', wait 1 more second and release both.

== Known bugs ==
I am working to fix these bugs now:
*sd reads correct data only 50% of times, so sd boot
*NAND hw ecc is not supported
*U-Boot can't boot system if battery is fully discharged (workaround exist)

== Booting without battery/with completely discharged battery ==

To workaround the bug that it's not possible boot with discharged/without battery, use following 'trick': insert charger cable and in same moment press 'power' button, add up 'aux' later for menu.

== Some setup examples ==
==== qtmoko v31 on NAND (ubifs) ====
<pre>
menu_3=
Boot NAND/ubi-zlib:
setenv bootargs ${bootargs_base} ${mtdparts} rootfstype=ubifs
ubi.mtd=6,2048 ubi.comp root=ubi0:om-gta02-rootfs
rootflags=compr=zlib,no_chk_data_crc;
nand read.e 0x32000000 kernel 0x300000;
bootm 0x32000000
</pre>
==== µSD (FAT+ext2) ====
<pre>
menu_2=
Boot from microSD (FAT+ext2):
setenv bootargs
${bootargs_base}
root=/dev/mmcblk0p1 rootwait
${mtdparts} ro;
mmcinit;
fatload mmc MMC_NUM 0x32000000 ${sd_image_name} 0x300000;
bootm 0x32000000
</pre>

==== µSD (ext2+ext3) ====
<pre>
menu_2=
Boot from microSD (ext2+ext3):
setenv bootargs
${bootargs_base}
root=/dev/mmcblk0p1 rootwait
${mtdparts} ro;
mmcinit;
ext2load mmc MMC_NUM 0x32000000 ${sd_image_name} 0x300000;
bootm 0x32000000
</pre>

[[Category:Bootloaders]]

U-boot-gena2x

2012-02-23T05:31:41Z

Glenn: /* List of changes */ chg

{{Bootloader}}
I decided to put '''U-boot-gena2x''' - my version of [[U-Boot]] [[bootloader]] here, along with a short FAQ and list of known bugs. Please feel free to add your bugs or questions here.

The current version of U-Boot ([[U-Boot]] or U-boot-gena2x?) fully supports uploading and downloading via dfu, booting any known distro, is fully configurable, and has no known grave bugs.

== List of changes ==

This version of U-Boot is based on openmoko's stable branch of U-Boot. Git can be viewed [http://www.bsdmn.com/cgit/cgit/u-boot/ here].

Significant patches are:

Version 2:
* + [[GPS]] is not powered up on boot
* + Leave all serial ports setup to kernel
Version 1:
* + [[Smedia_Glamo_3362#Timing_settings|2-4-2 timings]]
* + GPS should work after resume

== Binaries ==
Public freerunners should have the same bootloader (board v5 and later).
Latest binary version is here:
* http://www.bsdmn.com/openmoko/uboot/binary/

to use U-Boot as NAND bootloader, you should flash the binary to the special partition:
sudo dfu-util -a u-boot -D u-boot_g2x_2.udfu

== How to setup ==
NAND U-Boot occupies 2 partitions on NAND, one partition for U-Boot itself and one for it's configuration.

To setup U-Boot, the easiest way is to edit the simple text file on your computer and then upload it to your phone with dfu-util.

Sample text config may be found [http://www.bsdmn.com/openmoko/uboot/config/environment.in here]. This version supports various kinds of boot options in the menu. You may use it as a sample for your config.

If you are switching from bootloader [[Qi]], just boot your distro with Qi, then do <code>cat /proc/cmdline</code> and compare/update the parameters in your config file.

Then you can edit the config file to fit your needs, you should prepare it (this adds crc):

get envedit.pl and crc32.pl from [http://svn.openmoko.org/trunk/src/host/devirginator/] and run:
./envedit.pl -s 262144 -f environment.in > u-boot_env.in
then flash resulting file to configuration partition:
sudo dfu-util -a u-boot_env -D u-boot_env.in

== Useful kernel options ==
{| class="standard"
|-
! option || description
|-
|root=/dev/mmcblk0p2|| rootfs is second partition on SD card
|-
|root=/dev/mtdblock6|| rootfs is on usual location on NAND
|-
|rootwait|| needed for booting from SD. force kernel to delay boot until sd card is ready. better than older rootdelay=
|-
|panic=20|| on kernel crash, reboot automatically after 20 second delay. useful for lindi's ramconsole patch
|-
|hardware_ecc=1|| use hardware ecc support for NAND, this is not default option use only if your rootfs NAND is flashed not with dfu-util, but with direct copy from sd. this speeds up NAND read on zlib-compressed ubi by 8%.
|-
|rootfstype=XX|| needed if your rootfs is ext2 to force kernel to use ext2 driver not ext3. use if kernel can't detect partition type
|-
|ubi.mtd=6,2048|| claim 6th mtd partition as ubi layer with 2048 page align
|-
|rootflags=compr=zlib,no_chk_data_crc|| mount options of rootfs, use no_chk_data_crc to speed up ubifs by 8%
|-
|mem=127M|| reserve 1Mb if you using lindi's ramcomsole patch
|}

== How to use ==

By default, if you press the 'power' button, the "bootcmd" from your config is executed, so set it up accordingly for your default distribution.

To see the boot menu and select desired boot method, hold 'power', wait 1 second and then hold 'aux', wait 1 more second and release both.

== Known bugs ==
I am working to fix these bugs now:
*sd reads correct data only 50% of times, so sd boot
*NAND hw ecc is not supported
*U-Boot can't boot system if battery is fully discharged (workaround exist)

== Booting without battery/with completely discharged battery ==

To workaround the bug that it's not possible boot with discharged/without battery, use following 'trick': insert charger cable and in same moment press 'power' button, add up 'aux' later for menu.

== Some setup examples ==
==== qtmoko v31 on NAND (ubifs) ====
<pre>
menu_3=
Boot NAND/ubi-zlib:
setenv bootargs ${bootargs_base} ${mtdparts} rootfstype=ubifs
ubi.mtd=6,2048 ubi.comp root=ubi0:om-gta02-rootfs
rootflags=compr=zlib,no_chk_data_crc;
nand read.e 0x32000000 kernel 0x300000;
bootm 0x32000000
</pre>
==== µSD (FAT+ext2) ====
<pre>
menu_2=
Boot from microSD (FAT+ext2):
setenv bootargs
${bootargs_base}
root=/dev/mmcblk0p1 rootwait
${mtdparts} ro;
mmcinit;
fatload mmc MMC_NUM 0x32000000 ${sd_image_name} 0x300000;
bootm 0x32000000
</pre>

==== µSD (ext2+ext3) ====
<pre>
menu_2=
Boot from microSD (ext2+ext3):
setenv bootargs
${bootargs_base}
root=/dev/mmcblk0p1 rootwait
${mtdparts} ro;
mmcinit;
ext2load mmc MMC_NUM 0x32000000 ${sd_image_name} 0x300000;
bootm 0x32000000
</pre>

[[Category:Bootloaders]]

Repository

2012-02-13T17:30:56Z

Glenn: Redirecting to Category:Software repositories

#REDIRECT [[:Category:Software repositories]]

Repositories

2012-02-13T17:30:45Z

Glenn: Redirecting to Category:Software repositories

#REDIRECT [[:Category:Software repositories]]

Mac OS X

2012-02-13T17:29:05Z

Glenn: /* Graphical Flashing with Openmoko Flasher */ update

Being primarily a Linux based project, the host platform of choice is Linux. However, it is entirely possible to work with Openmoko and Neo handsets using MacOS X, as you'll soon see.

There are actually two ways of working with Openmoko and MacOS X. One is simply to run a virtual machine in which case you would then follow the instructions for Linux.

On the other hand, if you wish to use MacOS X directly, please continue:

= Flashing to your device =
To operate the Phase 1 devices (Neo 1973), you need to flash a root file system first.

== Graphical Flashing with Openmoko Flasher ==
Here are detailed Mac OS X instructions:
# download Version 1.5 or later of Openmoko Flasher from http://www.handheld-linux.com/wiki.php?page=Openmoko%20Flasher
# select the repository
# press the Refresh button (which loads the list of packages on the server)
# select and load the rootfs (takes some minutes for approx. 40 MByte)
# Now, on your Openmoko, hold the AUX button while pressing the Power button for 5 seconds
# the BOOT menu should appear
# connect the USB cable
# Press the Flash button
# the BOOT menu screen on the OM should show an indication that it has been switched to DFU mode
# (if it fails, unplug the Openmoko shortly and replug and try again (experience shows that it is needed up to three times)
# if it successfully flashed, you should be able to boot the Openmoko and continue configuring AJZaurusUSB

A Universal Binary version of dfu-utils tool (and libusb) is included in the Openmoko Flasher application bundle. You can access it as ''Openmoko Flasher.app/Contents/MacOS/dfu-util''.

To flash from Terminal (which is sometimes required), see the directions below or in [[Flashing_the_Neo_FreeRunner|Flashing the Neo]]

===GTA02===
To flash the kernel:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage
To flash the root filesystem:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D rootfs_filename.jffs2
To flash the boot loader to NAND
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a u-boot -R -D uboot.bin

===GTA01===
To flash the kernel:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a kernel -R -D uImage
To flash the root filesystem:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a rootfs -R -D rootfs_filename.jffs2
To flash the boot loader to NAND
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a u-boot -R -D uboot.bin

When flashing succeeds (in any of the above cases) the following should be shown:
status(0) = No error condition is present
Done!

{{Note|If you get an error: ''Cannot set alternate interface: usb_set_altinterface: could not set alternate interface''. You have to unplug and replug it again. '''Make sure it stays in the Boot menu during that!''' After you have replugged your openmoko you should see ''DFU: Switching to DFU Mode'' on the openmoko screen. Now you can execute the command again and this time it should work.

If somebody has a solution for this problem please contact me. - [[User: Anakron|Anakron]]}}

== Beginners Guide to Flashing Interfaces to the Neo Freerunner ==
In this guide I will be going over the steps to flash an interface onto the Freerunner.

# Download the openmoko flasher from http://www.handheld-linux.com/wiki.php?page=Openmoko%20Flasher . With this you will be able to flash the desired software to your device.
# You must find the repository for the specific interface you are going to flash. The Qtopia repository is located at http://other.lastnetwork.net/OpenMoko/ . The OM2008.9 repository is located at http://downloads.openmoko.org/distro/releases/Om2008.9/ . And the Android repository is located at http://people.openmoko.org/sean_mcneil/ .
# Now open the openmoko flasher and enter the URL for the repository of the desired interface. Next to where you entered the URL, you must click the drop down menu and choose Root File System. At the bottom of the flasher program click refresh. The Root File system file show appear. Once it appears, click Load and it will be loaded into the openmoko flasher.
# Now, with your Freerunner unplugged hold the AUX button while holding the power button (for about 5 seconds) until the BOOT menu appears. Now connect the Freerunner to your computer and click Flash. You may have to disconnect and reconnect the phone a few times until to goes into DFU mode. Once it is in DFU mode, flashing will work.
# Once the flashing is successful, the Freerunner will shut down. Now press the power button while holding the AUX button for 7-10 seconds until the NAND BOOT menu appears. From here, select Boot and you phone should boot to the new interface. (The AUX/Power button combination puts the phone into the NOR BOOT menu, which must be used for flashing. The Power/AUX button combination puts the phone into the NAND BOOT menu, which is usually used for booting after a flash. After the phone is booted once from the NAND menu, it can be booted normally in the future.)

Most of the time, only the rootfs has to be flashed in order for the interface to work, but sometimes the kernel has to be flashed along with the rootfs. In this case, before you flash the rootfs you should select kernel in the drop down menu on the openmoko flasher and follow the same directions.

== Compiling dfu-util ==
Alternatively, you can compile dfu-util manually as described at [[User:SNMoore]] but you need libusb (e.g. through MacPorts).

= Connecting a Mac and an Openmoko device =

== USB Serial ==

It is possible to access the [[U-Boot]] [[bootloader]] serial console from a Mac. You can use the Terminal application on Mac OS X, or <tt>minicom</tt> from [http://finkproject.org/ Fink] or [http://www.macports.org/ MacPorts] (formerly Darwin Ports.)

The USB driver creates cu and tty character devices, for example
$ ls -la /dev/tty.usb*
crw-rw-rw- 1 root wheel 10, 18 Aug 23 14:10 /dev/tty.usbmodem00000001
$ ls -la /dev/cu.usb*
crw-rw-rw- 1 root wheel 10, 19 Aug 23 14:10 /dev/cu.usbmodem00000001

=== USB Serial with screen ===
{{Main|GNU screen}}
The <code>GNU screen</code> program is included with Mac OS X, and can be used from the terminal command line to connect to the serial console. To do this, simply get to a shell prompt in the terminal and invoke <code>screen</code> as follows:
<pre>
% screen /dev/tty.usbmodem0000001
</pre>

You should find yourself at the U-boot serial console prompt. To get out, type <code>control+a</code> followed by <code>control+backslash</code>.

=== USB Serial with minicom ===
:''Possible Mac OS X .pkg download: [http://turin.nss.udel.edu/programming/ Dr. Jeffrey T. Frey: Minicom download and info; at the bottom]''
:''PL2303 USB serial driver (untested): [http://sourceforge.net/projects/osx-pl2303/ PL2303 USB to Serial Driver for Mac OS X]''
The <tt>minicom</tt> program from the [http://www.macports.org/ MacPorts] collection can be used to access the USB serial port <tt>/dev/cu.usbmodem0000001</tt> (numbering may vary.)

First install the program (assuming you already have MacPorts installed):

sudo port install minicom

Then launch it in configuration mode (the -s flag):

sudo minicom -s

Under "Serial Port Setup", set the Device to "/dev/cu.usbmodem0000001" and set Bps to "115200 8N1". Under "Modem and Dialing", enter empty strings for "Init string", "Reset string", and "Hang-up string". Save the setup as default ("dfl") then Exit.

You should now be able to access the U-Boot console. You should exit from Minicom before disconnecting the smartphone, or else you will get an error about unplugging a USB device while it is in use.

=== USB Serial with Terminal ===

The built in Mac Terminal application <tt>Terminal.app</tt> can be used to access the USB serial port <tt>/dev/tty.usbmodem0000001</tt> (numbering may vary.)

An easy way to do this is to configure the terminal with Script Editor, as described in the short article, [http://www.macosxhints.com/article.php?story=20061109133825654 ''Use '(GNU) screen' as a serial terminal emulator''](macosxhints.com). Then,

# Press and hold {{aux}} and then press and hold {{power}} for 5 seconds
# Press {{aux}} to select <tt>Set console to USB</tt> in the U-Boot menu, and {{power}} to execute it
# Start the serial terminal application. You should see a U-Boot command line prompt, such as
In: usbtty
Out: usbtty
Err: usbtty
DEVICE_CONFIGURED: 1
Enabling automatic fast charge
GTA01Bv4 #
When you boot Linux on the smartphone, or if the smartphone powers down, Mac OS X will show a USB Device Unplug Notice, "The USB device has been unplugged while an application was still active. This can result in loss of data." This error is probably harmless.

== USB Networking ==

There are several drivers you can use to talk to the RNDIS/Ethernet Gadget that the Linux kernel presents when connected as a USB client.

=== AJZaurusUSB driver ===

You can use the open source driver from [http://projects.goldelico.com/p/AJZaurusUSB]. It was originally developed for handheld devices like iPAQ, Sharp Zaurus and Motorola A760, but works for Openmoko as well. Download and install according to the manual found inside the package. The code is GPL'd (source available) and runs on both Intel and PPC Macs with 10.4 to 10.6.

After rebooting or loading the kernel extension by hand, you should have a new Ethernet interface in your System Preferences/Network.

Note: This driver does not have the same problem as the Apple driver does, where it constantly adds to the list of interfaces each time you reboot the Openmoko, because the driver provides a constant Ethernet address independently what the Openmoko says. Only flashing a new kernel version might force you to update.

=== Apple CDC Ethernet driver 10.4.10 ===
MacOS X 10.4.10 and later includes a driver for RNDIS/Ethernet Gadget devices. Launch System Preferences -> Network and you should see "new interface detected enXX".

Issue: Each time you reboot the Neo, the interface will get a different Ethernet address. This in turn makes Mac OS X create a new configuration record. After a while you'll end up with a load of unusable enXX devices - if you don't periodically clean them out. Open System Preferences and go to Network -> Show(Network Port Configurations) -> Select an enXX -> Delete.

Note: this is not a problem to blame Mac OS X for, because it tries to simplify network configuration based on the assumption of stable Ethernet addresses.

=== Apple CDC Ethernet driver 10.5.x ===

Issue:10.5 (Leopard) doesn't show a new ethernet interface for a Neo1973 running 2007.11. You'll only get the serial port, which is detected as a modem. The Ethernet device will show up in ifconfig though. If it doesn't, try the other driver below.

It turns out that the AppleUSBCDC driver prefers to use the CDC-ACM interface of USB networking devices instead of CDC-ECM with the exception of a broadcom network card. You can download a patched AppleUSBCDC driver that will recognize the usb id/vendor pair of g_ether and force it to use CDC-ECM. You can obtain the OS X 10.5.X patched driver from: http://bugcommunity.com/downloads/usbcdc-g_ether.zip. [Do not work? Openmoko 2009 16-june-2009 showed up as a modem (MacOS X.5.7) with this driver (ndis/ethernet) [[User:Glenn|Glenn]] 10:54, 16 June 2009 (UTC)] Source code: http://bugcommunity.com/downloads/files/AppleUSBCDCDriver-g_ether.326.4.1.zip

The issue of multiple network interfaces showing up whenever the Neo is rebooted/power-cycled is due to the g_ether driver randomly setting the host and device mac addresses. This problem is remedied by passing the same host and device mac addresses during the modprobe of g_ether. [Not needed with MacOS X.5.7 and Openmoko 2009 16-june-2009. Simply reboot the Mac (again) and Openmoko appear again without changing network settings --[[User:Glenn|Glenn]] 08:30, 17 June 2009 (UTC)]

For example:

modprobe g_ether host_addr=46:0d:9e:67:69:eb dev_addr=46:0d:9e:67:69:ec

=== Network Settings ===
Open System Preferences and go to Network and you should see "new interface detected enXX". In the Show list box select the new interface - Ethernet Adapter enXX.

Use this configuration on the new interface with SHR-CORE images after 110822:
<pre>
IP-V4: manual
IP-Addr: 192.168.7.2 (you can use anything in 192.168.7.* but OM is configured by default to use 192.168.7.2 as the external gateway)
Subnet: 255.255.255.0 (should be the default - see tip below if have issue with these settings)
Router: 192.168.7.1 (not actually needed, OS X can figure this out for itself, unless you have other conflicting configurations)
</pre>

Use this configuration on the new interface with SHR images before 110822:
<pre>
IP-V4: manual
IP-Addr: 192.168.0.200 (you can use anything in 192.168.0.* but OM is configured by default to use 192.168.0.200 as the external gateway)
Subnet: 255.255.255.0 (should be the default - see tip below if have issue with these settings)
Router: 192.168.0.202 (not actually needed, OS X can figure this out for itself, unless you have other conflicting configurations)
</pre>

Tip: If your Internet connection is also in the range 192.168.0.x then instead you might want/need to use:
<pre>
Subnet: 255.255.255.248
</pre>
However if you are running Leopard it may not let you set the subnet claiming that the IP 192.168.0.200 is an invalid address for that subnet. To get round this run the following from the OSX terminal (replacing en11 as appropriate):
<pre>
sudo ifconfig en11 192.168.0.200 netmask 255.255.255.248
</pre>

=== Testing Your Connection ===
You should be able to connect to your Openmoko! Try using Terminal (Applications->Utilities->Terminal) to ping the Neo at 192.168.0.202 and the roundtrip time should be between 1 and 2 ms.
ping 192.168.7.2 # SHR-CORE images after 110822
ping 192.168.0.202 # SHR images before 110822

Then log into your Openmoko using ssh:
ssh root@192.168.7.2 # SHR-CORE images after 110822
ssh root@192.168.0.202 # SHR images before 110822
The default password is blank (depending on the distribution you have on the Openmoko).

You can also [[scp]] files back and forth or share displays with X11. Additional software and configuration could allow telnet, SMB, or many other possibilities using the TCP/IP network over your USB connection.

Try pinging your Mac PC from the Openmoko
ping 192.168.7.1 # SHR-CORE images after 110822
ping 192.168.0.200 # SHR images before 110822

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
If that works then your Mac is routing the neo globally--if not see [[MacOS_X#Enabling_the_Mac_as_an_Internet_Router | Sharing Internet Connection with Mac]].

Lastly, verify that DNS is correctly configured between the Openmoko & Network:
ping www.google.com
If that doesn't work then see [[USB_Networking#Configure_Default_Neo_DNS | Configuring Default Neo DNS]] to try and resolve the issue.

Congratulations!!! The Neo is networked together with the Mac and sharing the Mac's interweb connection.

== Bluetooth Networking ==
{{InProgress}}

This approach is based on:
*[[Bluetooth_Support#Networking]]
*http://www.macosxhints.com/article.php?story=20051220221237711

Unfortunately we can't use the pand (PAN daemon for BNEP) or dund (Dial Up Networking daemon for LAP) since neither service is available for the Mac.

So, we configure a RFCOMM connection and a PPP gateway on the Mac. Finally, we connect the OM as a ppp client to the Mac.

The reversed direction (OM as the Access Point and the Mac as the client) is described shortly in [[Manually_using_Bluetooth#PPP_Networking]]

=== Making the Mac a PPP over Bluetooth Access Point ===

In the Bluetooth System Preferences (10.4.11)
* go to the Sharing pane
* add a new service "BluetoothAccessPoint" of type RS-232
* Enable that it is shown in the network preferences pane
* Apply

In the Network System Preferences
* activate the new network configuration (BluetoothAccessPoint)
* go tot the Modem tab and change the modem to "Null Modem 115200"
* Apply

In a Terminal, enter the following:
$ sudo /usr/sbin/pppd /dev/tty.BluetoothAccessPoint 115200 noauth local passive proxyarp asyncmap 0 silent persist :172.16.140.14

Here you see the 172.16.140.14 address, which makes it possible not to use natd, since it's in the same network as the Mac is. So the firewall knows where to sent it to -- no routing problems etc. Pick any free address in your private range. For instance, if you are using the following ... firewall: 192.168.1.1, Mac: 192.168.1.2, you can enter 192.168.1.3, assuming it's not used elsewhere on your network.

If you want to be sure you did it right, open the system.log file on the Mac (tail -f /var/log/system.log), and you should see something like this:
Jun 25 10:33:57 hostname pppd[679]: pppd 2.4.2 (Apple version 229) started by username, uid 0
Jun 25 10:33:57 hostname pppd[679]: Connect: ppp0 <--> /dev/tty.BluetoothAccessPoint

In Terminal, write
sudo sysctl -w net.inet.ip.forwarding=1
which should give the following feedback:
net.inet.ip.forwarding: 0 -> 1

In Terminal, write
sudo ifconfig ppp0 up.

=== Connecting the Openmoko as a Client to the Mac ===

On the Openmoko do the following

* Power on bluetooth

root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on

* Scan for the Mac
root@fic-gta01:~$ hcitool scan
Scanning ...
00:0E:6D:C0:0l:6A Sho
00:20:E0:5A:FE:C8 MacBook

* start the PPP client

pppd 115000 192.168.1.202:192.168.1.200 local defaultroute pty 'rfcomm connect 0 00:16:CB:2F:A0:46 1'

* Enjoy

== WiFi Networking ==
{{InProgress}}

To Be Done.

== Neo1973 as a Bluetooth GPRS modem ==
{{InProgress}}

To Be Done.

= Enabling the Mac as an Internet Router =

Here is described how to enable your Mac to serve as a Internet Router for your Openmoko device.

Note: you have to open all services you want to use from the Openmoko in the Mac Firewall.

== USB connection ==

In the Sharing System Preferences
* click the Internet tab
* Check all the ethernet (en) interfaces you want to enable Internet access for (i.e. the USB connection)

SSH into your Neo and create /etc/resolv.conf, specify your Internet router IP address as the name server. You can simply copy the /etc/resolv.conf from your Mac.
scp /etc/resolv.conf root@192.168.0.202:/etc/resolv.conf

Example:
nameserver 192.168.1.200 # replace by your real nameserver address

Make sure your Neo routing table has entries so that all internet traffic is sent to your Mac (which will forward it to the outside world)

root@fic-gta01:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 usb0
default 192.168.0.200 0.0.0.0 UG 0 0 0 usb0

Don't forget to enable your USB interface for Internet Sharing!

== Bluetooth connection ==
{{InProgress}}

= Accessing data and services on your device =

== ssh ==

After making the USB connection work, start ssh:

ssh -l root 192.168.0.202

If you don't have installed the key, it will ask for a "yes" on the first connection. The root password is blank unless you change it.

MacBook-hns:~ hns$ ssh -l root 192.168.0.202
root@192.168.0.202's password:
root@fic-gta01:~$ hostname
fic-gta01
root@fic-gta01:~$

NOTE: the ssh daemon (dropbear 0.49) on the Openmoko appears to have a bug when sending the exit status back to the client. From time to time you receive an exit status of 255.

== SMB ==
{{InProgress}}

To Be Done.

== X11 ==
Launch Apple X11.
xhost +192.168.0.202.
On the Neo:
export DISPLAY=192.168.0.200:0.0

== Synchronizing ==
{{InProgress}}

This is not done yet. Possible solutions are SyncML or ZMacSync http://www.dsitri.de/wiki.php?page=ZMacSync

ZMacSync does not yet synchronize but allows more easy access to the Openmoko through Terminal/ssh.

= Developing Openmoko software on a Mac =

== Using virtualization software and MokoMakefile/OpenEmbedded ==

You can use VirtualBox, Parallels or VMWare to install your favourite Linux distribution and then develop just as on Linux.

There are some drawback since AFAIK dfu-util may not work correctly in such environments.

=== Parallels ===

Don't bother with Parallels Desktop for Mac (<=3), the current USB support is terrible and USB storage keys don't even work so there was no way I would try dfu-util. USB keys work under VMWare Fusion for Mac though I have yet to try dfu-util in an VM under VMWare Fusion as there is Openmoko Flasher for Mac. -- [[User: Eric|Eric]]

=== VMware Fusion ===

There is currently no vmplayer for OS X. But the Qtopia image (see [[Developing_with_C++_and_Qt#Use_pre-built_SDK]]) will work with VMware fusion. The script will search for vmplayer and complain. Just answer <tt>YES</tt> when asked if you have the vmplayer installed (I know, it's a lie, but...), and the script will run through. Afterwards open the directory where the files were installed and click on <tt>Qtopia.vmx</tt>.

In VMware Fusion USB Networking is working properly, just plug in the device and connect it to your virtual machine.

Unfortunately dfu-util is currently not working. In fact if you get dfu-util working via unplug/replug method on Mac OS X it works inside VMware too.

=== VirtualBox ===

dfu-util is not working, has some problems with getting exclusive access to the USB device.

== Natively ==
{{InProgress}}

There are some efforts to get through process of compiling OE and Openmoko under mac: [[Openmoko_under_QEMU_on_MacOSX]]

== GNUstep/mySTEP SDK ==

There is a [[QuantumSTEP]]/mySTEP project to port GNUstep to the Openmoko/Neo: [http://www.quantum-step.com/wiki.php?page=Openmoko-Edition More Info]
An SDK for Xcode/Interface Builder is also available: [http://www.versiontracker.com/dyn/moreinfo/macosx/20581 Entry at Version Tracker] [http://www.quantum-step.com/wiki.php?page=SDK More Info]

== Tools for Developers ==

Some tools that run on MacOS X

=== mkfs.jffs2 ===
[http://www.quantum-step.com/download/Openmoko-Edition/mkfs.jffs2.tgz mkfs.jffs2] - make JFFS2 (root) file system (Universal Binary). Package includes sources and Xcode 2.4 project file to rebuild on MacOS X 10.4.11. NOT TESTED DEEPLY.

mkfs.jffs2 --pad=0x700000 -o rootfs.jffs2 -e 0x4000 -n -d/tmp/jffsroot/

=== Crosscompiler Toolchain ===

[http://www.quantum-step.com/wiki.php?page=Compiler gcc 2.95.3] - OABI cross compiler toolchain (C, C++, Obj-C) with Linux headers (PPC and Intel Macs)

If someone has a newer one that works, please provide as an installable OSX Package.

Will the ones from MacPorts work? [http://www.macports.org/ports.php?by=name&substr=gnueabi] I'm still trying to get QEMU to work and haven't had a chance to test it yet.

= Other Resources =

== Search Software Repositories ==

[http://www.versiontracker.com/php/qs.php?action=search&str=openmoko&srchArea=macosx Keyword Openmoko] at VersionTracker

== Discussion Fora ==

[http://www.oesf.org/forums/index.php?showforum=63 Mac Issues Forum] at Open Embedded Software Foundation (was Zaurus User Group)

[[Category:Flashing Openmoko]]
[[Category:Host OSes]]

[http://www.mac-how.net/ Mac How] for discussion questions about Mac

Mac OS X

2012-02-13T17:28:47Z

Glenn: /* Graphical Flashing with Openmoko Flasher */ more

Being primarily a Linux based project, the host platform of choice is Linux. However, it is entirely possible to work with Openmoko and Neo handsets using MacOS X, as you'll soon see.

There are actually two ways of working with Openmoko and MacOS X. One is simply to run a virtual machine in which case you would then follow the instructions for Linux.

On the other hand, if you wish to use MacOS X directly, please continue:

= Flashing to your device =
To operate the Phase 1 devices (Neo 1973), you need to flash a root file system first.

== Graphical Flashing with Openmoko Flasher ==
Here are detailed Mac OS X instructions:
# download Version 1.4 or later of Openmoko Flasher from http://www.handheld-linux.com/wiki.php?page=Openmoko%20Flasher
# select the repository
# press the Refresh button (which loads the list of packages on the server)
# select and load the rootfs (takes some minutes for approx. 40 MByte)
# Now, on your Openmoko, hold the AUX button while pressing the Power button for 5 seconds
# the BOOT menu should appear
# connect the USB cable
# Press the Flash button
# the BOOT menu screen on the OM should show an indication that it has been switched to DFU mode
# (if it fails, unplug the Openmoko shortly and replug and try again (experience shows that it is needed up to three times)
# if it successfully flashed, you should be able to boot the Openmoko and continue configuring AJZaurusUSB

A Universal Binary version of dfu-utils tool (and libusb) is included in the Openmoko Flasher application bundle. You can access it as ''Openmoko Flasher.app/Contents/MacOS/dfu-util''.

To flash from Terminal (which is sometimes required), see the directions below or in [[Flashing_the_Neo_FreeRunner|Flashing the Neo]]

===GTA02===
To flash the kernel:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage
To flash the root filesystem:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D rootfs_filename.jffs2
To flash the boot loader to NAND
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a u-boot -R -D uboot.bin

===GTA01===
To flash the kernel:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a kernel -R -D uImage
To flash the root filesystem:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a rootfs -R -D rootfs_filename.jffs2
To flash the boot loader to NAND
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a u-boot -R -D uboot.bin

When flashing succeeds (in any of the above cases) the following should be shown:
status(0) = No error condition is present
Done!

{{Note|If you get an error: ''Cannot set alternate interface: usb_set_altinterface: could not set alternate interface''. You have to unplug and replug it again. '''Make sure it stays in the Boot menu during that!''' After you have replugged your openmoko you should see ''DFU: Switching to DFU Mode'' on the openmoko screen. Now you can execute the command again and this time it should work.

If somebody has a solution for this problem please contact me. - [[User: Anakron|Anakron]]}}

== Beginners Guide to Flashing Interfaces to the Neo Freerunner ==
In this guide I will be going over the steps to flash an interface onto the Freerunner.

# Download the openmoko flasher from http://www.handheld-linux.com/wiki.php?page=Openmoko%20Flasher . With this you will be able to flash the desired software to your device.
# You must find the repository for the specific interface you are going to flash. The Qtopia repository is located at http://other.lastnetwork.net/OpenMoko/ . The OM2008.9 repository is located at http://downloads.openmoko.org/distro/releases/Om2008.9/ . And the Android repository is located at http://people.openmoko.org/sean_mcneil/ .
# Now open the openmoko flasher and enter the URL for the repository of the desired interface. Next to where you entered the URL, you must click the drop down menu and choose Root File System. At the bottom of the flasher program click refresh. The Root File system file show appear. Once it appears, click Load and it will be loaded into the openmoko flasher.
# Now, with your Freerunner unplugged hold the AUX button while holding the power button (for about 5 seconds) until the BOOT menu appears. Now connect the Freerunner to your computer and click Flash. You may have to disconnect and reconnect the phone a few times until to goes into DFU mode. Once it is in DFU mode, flashing will work.
# Once the flashing is successful, the Freerunner will shut down. Now press the power button while holding the AUX button for 7-10 seconds until the NAND BOOT menu appears. From here, select Boot and you phone should boot to the new interface. (The AUX/Power button combination puts the phone into the NOR BOOT menu, which must be used for flashing. The Power/AUX button combination puts the phone into the NAND BOOT menu, which is usually used for booting after a flash. After the phone is booted once from the NAND menu, it can be booted normally in the future.)

Most of the time, only the rootfs has to be flashed in order for the interface to work, but sometimes the kernel has to be flashed along with the rootfs. In this case, before you flash the rootfs you should select kernel in the drop down menu on the openmoko flasher and follow the same directions.

== Compiling dfu-util ==
Alternatively, you can compile dfu-util manually as described at [[User:SNMoore]] but you need libusb (e.g. through MacPorts).

= Connecting a Mac and an Openmoko device =

== USB Serial ==

It is possible to access the [[U-Boot]] [[bootloader]] serial console from a Mac. You can use the Terminal application on Mac OS X, or <tt>minicom</tt> from [http://finkproject.org/ Fink] or [http://www.macports.org/ MacPorts] (formerly Darwin Ports.)

The USB driver creates cu and tty character devices, for example
$ ls -la /dev/tty.usb*
crw-rw-rw- 1 root wheel 10, 18 Aug 23 14:10 /dev/tty.usbmodem00000001
$ ls -la /dev/cu.usb*
crw-rw-rw- 1 root wheel 10, 19 Aug 23 14:10 /dev/cu.usbmodem00000001

=== USB Serial with screen ===
{{Main|GNU screen}}
The <code>GNU screen</code> program is included with Mac OS X, and can be used from the terminal command line to connect to the serial console. To do this, simply get to a shell prompt in the terminal and invoke <code>screen</code> as follows:
<pre>
% screen /dev/tty.usbmodem0000001
</pre>

You should find yourself at the U-boot serial console prompt. To get out, type <code>control+a</code> followed by <code>control+backslash</code>.

=== USB Serial with minicom ===
:''Possible Mac OS X .pkg download: [http://turin.nss.udel.edu/programming/ Dr. Jeffrey T. Frey: Minicom download and info; at the bottom]''
:''PL2303 USB serial driver (untested): [http://sourceforge.net/projects/osx-pl2303/ PL2303 USB to Serial Driver for Mac OS X]''
The <tt>minicom</tt> program from the [http://www.macports.org/ MacPorts] collection can be used to access the USB serial port <tt>/dev/cu.usbmodem0000001</tt> (numbering may vary.)

First install the program (assuming you already have MacPorts installed):

sudo port install minicom

Then launch it in configuration mode (the -s flag):

sudo minicom -s

Under "Serial Port Setup", set the Device to "/dev/cu.usbmodem0000001" and set Bps to "115200 8N1". Under "Modem and Dialing", enter empty strings for "Init string", "Reset string", and "Hang-up string". Save the setup as default ("dfl") then Exit.

You should now be able to access the U-Boot console. You should exit from Minicom before disconnecting the smartphone, or else you will get an error about unplugging a USB device while it is in use.

=== USB Serial with Terminal ===

The built in Mac Terminal application <tt>Terminal.app</tt> can be used to access the USB serial port <tt>/dev/tty.usbmodem0000001</tt> (numbering may vary.)

An easy way to do this is to configure the terminal with Script Editor, as described in the short article, [http://www.macosxhints.com/article.php?story=20061109133825654 ''Use '(GNU) screen' as a serial terminal emulator''](macosxhints.com). Then,

# Press and hold {{aux}} and then press and hold {{power}} for 5 seconds
# Press {{aux}} to select <tt>Set console to USB</tt> in the U-Boot menu, and {{power}} to execute it
# Start the serial terminal application. You should see a U-Boot command line prompt, such as
In: usbtty
Out: usbtty
Err: usbtty
DEVICE_CONFIGURED: 1
Enabling automatic fast charge
GTA01Bv4 #
When you boot Linux on the smartphone, or if the smartphone powers down, Mac OS X will show a USB Device Unplug Notice, "The USB device has been unplugged while an application was still active. This can result in loss of data." This error is probably harmless.

== USB Networking ==

There are several drivers you can use to talk to the RNDIS/Ethernet Gadget that the Linux kernel presents when connected as a USB client.

=== AJZaurusUSB driver ===

You can use the open source driver from [http://projects.goldelico.com/p/AJZaurusUSB]. It was originally developed for handheld devices like iPAQ, Sharp Zaurus and Motorola A760, but works for Openmoko as well. Download and install according to the manual found inside the package. The code is GPL'd (source available) and runs on both Intel and PPC Macs with 10.4 to 10.6.

After rebooting or loading the kernel extension by hand, you should have a new Ethernet interface in your System Preferences/Network.

Note: This driver does not have the same problem as the Apple driver does, where it constantly adds to the list of interfaces each time you reboot the Openmoko, because the driver provides a constant Ethernet address independently what the Openmoko says. Only flashing a new kernel version might force you to update.

=== Apple CDC Ethernet driver 10.4.10 ===
MacOS X 10.4.10 and later includes a driver for RNDIS/Ethernet Gadget devices. Launch System Preferences -> Network and you should see "new interface detected enXX".

Issue: Each time you reboot the Neo, the interface will get a different Ethernet address. This in turn makes Mac OS X create a new configuration record. After a while you'll end up with a load of unusable enXX devices - if you don't periodically clean them out. Open System Preferences and go to Network -> Show(Network Port Configurations) -> Select an enXX -> Delete.

Note: this is not a problem to blame Mac OS X for, because it tries to simplify network configuration based on the assumption of stable Ethernet addresses.

=== Apple CDC Ethernet driver 10.5.x ===

Issue:10.5 (Leopard) doesn't show a new ethernet interface for a Neo1973 running 2007.11. You'll only get the serial port, which is detected as a modem. The Ethernet device will show up in ifconfig though. If it doesn't, try the other driver below.

It turns out that the AppleUSBCDC driver prefers to use the CDC-ACM interface of USB networking devices instead of CDC-ECM with the exception of a broadcom network card. You can download a patched AppleUSBCDC driver that will recognize the usb id/vendor pair of g_ether and force it to use CDC-ECM. You can obtain the OS X 10.5.X patched driver from: http://bugcommunity.com/downloads/usbcdc-g_ether.zip. [Do not work? Openmoko 2009 16-june-2009 showed up as a modem (MacOS X.5.7) with this driver (ndis/ethernet) [[User:Glenn|Glenn]] 10:54, 16 June 2009 (UTC)] Source code: http://bugcommunity.com/downloads/files/AppleUSBCDCDriver-g_ether.326.4.1.zip

The issue of multiple network interfaces showing up whenever the Neo is rebooted/power-cycled is due to the g_ether driver randomly setting the host and device mac addresses. This problem is remedied by passing the same host and device mac addresses during the modprobe of g_ether. [Not needed with MacOS X.5.7 and Openmoko 2009 16-june-2009. Simply reboot the Mac (again) and Openmoko appear again without changing network settings --[[User:Glenn|Glenn]] 08:30, 17 June 2009 (UTC)]

For example:

modprobe g_ether host_addr=46:0d:9e:67:69:eb dev_addr=46:0d:9e:67:69:ec

=== Network Settings ===
Open System Preferences and go to Network and you should see "new interface detected enXX". In the Show list box select the new interface - Ethernet Adapter enXX.

Use this configuration on the new interface with SHR-CORE images after 110822:
<pre>
IP-V4: manual
IP-Addr: 192.168.7.2 (you can use anything in 192.168.7.* but OM is configured by default to use 192.168.7.2 as the external gateway)
Subnet: 255.255.255.0 (should be the default - see tip below if have issue with these settings)
Router: 192.168.7.1 (not actually needed, OS X can figure this out for itself, unless you have other conflicting configurations)
</pre>

Use this configuration on the new interface with SHR images before 110822:
<pre>
IP-V4: manual
IP-Addr: 192.168.0.200 (you can use anything in 192.168.0.* but OM is configured by default to use 192.168.0.200 as the external gateway)
Subnet: 255.255.255.0 (should be the default - see tip below if have issue with these settings)
Router: 192.168.0.202 (not actually needed, OS X can figure this out for itself, unless you have other conflicting configurations)
</pre>

Tip: If your Internet connection is also in the range 192.168.0.x then instead you might want/need to use:
<pre>
Subnet: 255.255.255.248
</pre>
However if you are running Leopard it may not let you set the subnet claiming that the IP 192.168.0.200 is an invalid address for that subnet. To get round this run the following from the OSX terminal (replacing en11 as appropriate):
<pre>
sudo ifconfig en11 192.168.0.200 netmask 255.255.255.248
</pre>

=== Testing Your Connection ===
You should be able to connect to your Openmoko! Try using Terminal (Applications->Utilities->Terminal) to ping the Neo at 192.168.0.202 and the roundtrip time should be between 1 and 2 ms.
ping 192.168.7.2 # SHR-CORE images after 110822
ping 192.168.0.202 # SHR images before 110822

Then log into your Openmoko using ssh:
ssh root@192.168.7.2 # SHR-CORE images after 110822
ssh root@192.168.0.202 # SHR images before 110822
The default password is blank (depending on the distribution you have on the Openmoko).

You can also [[scp]] files back and forth or share displays with X11. Additional software and configuration could allow telnet, SMB, or many other possibilities using the TCP/IP network over your USB connection.

Try pinging your Mac PC from the Openmoko
ping 192.168.7.1 # SHR-CORE images after 110822
ping 192.168.0.200 # SHR images before 110822

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
If that works then your Mac is routing the neo globally--if not see [[MacOS_X#Enabling_the_Mac_as_an_Internet_Router | Sharing Internet Connection with Mac]].

Lastly, verify that DNS is correctly configured between the Openmoko & Network:
ping www.google.com
If that doesn't work then see [[USB_Networking#Configure_Default_Neo_DNS | Configuring Default Neo DNS]] to try and resolve the issue.

Congratulations!!! The Neo is networked together with the Mac and sharing the Mac's interweb connection.

== Bluetooth Networking ==
{{InProgress}}

This approach is based on:
*[[Bluetooth_Support#Networking]]
*http://www.macosxhints.com/article.php?story=20051220221237711

Unfortunately we can't use the pand (PAN daemon for BNEP) or dund (Dial Up Networking daemon for LAP) since neither service is available for the Mac.

So, we configure a RFCOMM connection and a PPP gateway on the Mac. Finally, we connect the OM as a ppp client to the Mac.

The reversed direction (OM as the Access Point and the Mac as the client) is described shortly in [[Manually_using_Bluetooth#PPP_Networking]]

=== Making the Mac a PPP over Bluetooth Access Point ===

In the Bluetooth System Preferences (10.4.11)
* go to the Sharing pane
* add a new service "BluetoothAccessPoint" of type RS-232
* Enable that it is shown in the network preferences pane
* Apply

In the Network System Preferences
* activate the new network configuration (BluetoothAccessPoint)
* go tot the Modem tab and change the modem to "Null Modem 115200"
* Apply

In a Terminal, enter the following:
$ sudo /usr/sbin/pppd /dev/tty.BluetoothAccessPoint 115200 noauth local passive proxyarp asyncmap 0 silent persist :172.16.140.14

Here you see the 172.16.140.14 address, which makes it possible not to use natd, since it's in the same network as the Mac is. So the firewall knows where to sent it to -- no routing problems etc. Pick any free address in your private range. For instance, if you are using the following ... firewall: 192.168.1.1, Mac: 192.168.1.2, you can enter 192.168.1.3, assuming it's not used elsewhere on your network.

If you want to be sure you did it right, open the system.log file on the Mac (tail -f /var/log/system.log), and you should see something like this:
Jun 25 10:33:57 hostname pppd[679]: pppd 2.4.2 (Apple version 229) started by username, uid 0
Jun 25 10:33:57 hostname pppd[679]: Connect: ppp0 <--> /dev/tty.BluetoothAccessPoint

In Terminal, write
sudo sysctl -w net.inet.ip.forwarding=1
which should give the following feedback:
net.inet.ip.forwarding: 0 -> 1

In Terminal, write
sudo ifconfig ppp0 up.

=== Connecting the Openmoko as a Client to the Mac ===

On the Openmoko do the following

* Power on bluetooth

root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on

* Scan for the Mac
root@fic-gta01:~$ hcitool scan
Scanning ...
00:0E:6D:C0:0l:6A Sho
00:20:E0:5A:FE:C8 MacBook

* start the PPP client

pppd 115000 192.168.1.202:192.168.1.200 local defaultroute pty 'rfcomm connect 0 00:16:CB:2F:A0:46 1'

* Enjoy

== WiFi Networking ==
{{InProgress}}

To Be Done.

== Neo1973 as a Bluetooth GPRS modem ==
{{InProgress}}

To Be Done.

= Enabling the Mac as an Internet Router =

Here is described how to enable your Mac to serve as a Internet Router for your Openmoko device.

Note: you have to open all services you want to use from the Openmoko in the Mac Firewall.

== USB connection ==

In the Sharing System Preferences
* click the Internet tab
* Check all the ethernet (en) interfaces you want to enable Internet access for (i.e. the USB connection)

SSH into your Neo and create /etc/resolv.conf, specify your Internet router IP address as the name server. You can simply copy the /etc/resolv.conf from your Mac.
scp /etc/resolv.conf root@192.168.0.202:/etc/resolv.conf

Example:
nameserver 192.168.1.200 # replace by your real nameserver address

Make sure your Neo routing table has entries so that all internet traffic is sent to your Mac (which will forward it to the outside world)

root@fic-gta01:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 usb0
default 192.168.0.200 0.0.0.0 UG 0 0 0 usb0

Don't forget to enable your USB interface for Internet Sharing!

== Bluetooth connection ==
{{InProgress}}

= Accessing data and services on your device =

== ssh ==

After making the USB connection work, start ssh:

ssh -l root 192.168.0.202

If you don't have installed the key, it will ask for a "yes" on the first connection. The root password is blank unless you change it.

MacBook-hns:~ hns$ ssh -l root 192.168.0.202
root@192.168.0.202's password:
root@fic-gta01:~$ hostname
fic-gta01
root@fic-gta01:~$

NOTE: the ssh daemon (dropbear 0.49) on the Openmoko appears to have a bug when sending the exit status back to the client. From time to time you receive an exit status of 255.

== SMB ==
{{InProgress}}

To Be Done.

== X11 ==
Launch Apple X11.
xhost +192.168.0.202.
On the Neo:
export DISPLAY=192.168.0.200:0.0

== Synchronizing ==
{{InProgress}}

This is not done yet. Possible solutions are SyncML or ZMacSync http://www.dsitri.de/wiki.php?page=ZMacSync

ZMacSync does not yet synchronize but allows more easy access to the Openmoko through Terminal/ssh.

= Developing Openmoko software on a Mac =

== Using virtualization software and MokoMakefile/OpenEmbedded ==

You can use VirtualBox, Parallels or VMWare to install your favourite Linux distribution and then develop just as on Linux.

There are some drawback since AFAIK dfu-util may not work correctly in such environments.

=== Parallels ===

Don't bother with Parallels Desktop for Mac (<=3), the current USB support is terrible and USB storage keys don't even work so there was no way I would try dfu-util. USB keys work under VMWare Fusion for Mac though I have yet to try dfu-util in an VM under VMWare Fusion as there is Openmoko Flasher for Mac. -- [[User: Eric|Eric]]

=== VMware Fusion ===

There is currently no vmplayer for OS X. But the Qtopia image (see [[Developing_with_C++_and_Qt#Use_pre-built_SDK]]) will work with VMware fusion. The script will search for vmplayer and complain. Just answer <tt>YES</tt> when asked if you have the vmplayer installed (I know, it's a lie, but...), and the script will run through. Afterwards open the directory where the files were installed and click on <tt>Qtopia.vmx</tt>.

In VMware Fusion USB Networking is working properly, just plug in the device and connect it to your virtual machine.

Unfortunately dfu-util is currently not working. In fact if you get dfu-util working via unplug/replug method on Mac OS X it works inside VMware too.

=== VirtualBox ===

dfu-util is not working, has some problems with getting exclusive access to the USB device.

== Natively ==
{{InProgress}}

There are some efforts to get through process of compiling OE and Openmoko under mac: [[Openmoko_under_QEMU_on_MacOSX]]

== GNUstep/mySTEP SDK ==

There is a [[QuantumSTEP]]/mySTEP project to port GNUstep to the Openmoko/Neo: [http://www.quantum-step.com/wiki.php?page=Openmoko-Edition More Info]
An SDK for Xcode/Interface Builder is also available: [http://www.versiontracker.com/dyn/moreinfo/macosx/20581 Entry at Version Tracker] [http://www.quantum-step.com/wiki.php?page=SDK More Info]

== Tools for Developers ==

Some tools that run on MacOS X

=== mkfs.jffs2 ===
[http://www.quantum-step.com/download/Openmoko-Edition/mkfs.jffs2.tgz mkfs.jffs2] - make JFFS2 (root) file system (Universal Binary). Package includes sources and Xcode 2.4 project file to rebuild on MacOS X 10.4.11. NOT TESTED DEEPLY.

mkfs.jffs2 --pad=0x700000 -o rootfs.jffs2 -e 0x4000 -n -d/tmp/jffsroot/

=== Crosscompiler Toolchain ===

[http://www.quantum-step.com/wiki.php?page=Compiler gcc 2.95.3] - OABI cross compiler toolchain (C, C++, Obj-C) with Linux headers (PPC and Intel Macs)

If someone has a newer one that works, please provide as an installable OSX Package.

Will the ones from MacPorts work? [http://www.macports.org/ports.php?by=name&substr=gnueabi] I'm still trying to get QEMU to work and haven't had a chance to test it yet.

= Other Resources =

== Search Software Repositories ==

[http://www.versiontracker.com/php/qs.php?action=search&str=openmoko&srchArea=macosx Keyword Openmoko] at VersionTracker

== Discussion Fora ==

[http://www.oesf.org/forums/index.php?showforum=63 Mac Issues Forum] at Open Embedded Software Foundation (was Zaurus User Group)

[[Category:Flashing Openmoko]]
[[Category:Host OSes]]

[http://www.mac-how.net/ Mac How] for discussion questions about Mac

Openmoko Flasher

2012-02-13T17:27:48Z

Glenn: +Category:Flashing Openmoko

#redirect [[Mac_OS_X#Graphical_Flashing_with_Openmoko_Flasher]]
[[Category:Flashing Openmoko]]

Openmoko flasher

2012-02-13T17:25:53Z

Glenn: Redirecting to Mac OS X#Graphical Flashing with Openmoko Flasher

#redirect [[Mac_OS_X#Graphical_Flashing_with_Openmoko_Flasher]]

Openmoko Flasher

2012-02-13T17:25:45Z

Glenn: Redirecting to Mac OS X#Graphical Flashing with Openmoko Flasher

#redirect [[Mac_OS_X#Graphical_Flashing_with_Openmoko_Flasher]]

Openmoko flasher

2012-02-13T17:24:45Z

Glenn: Redirecting to MacOS X#Graphical Flashing with Openmoko Flasher

#redirect [[MacOS_X#Graphical_Flashing_with_Openmoko_Flasher]]

Openmoko Flasher

2012-02-13T17:24:35Z

Glenn: Redirecting to MacOS X#Graphical Flashing with Openmoko Flasher

#redirect [[MacOS_X#Graphical_Flashing_with_Openmoko_Flasher]]

Dfu-util

2012-02-13T17:24:21Z

Glenn: /* Mac */ linkchg

{{Languages|Dfu-util}}

dfu-util is a program that implements the Host (PC) side of the [[USB DFU]] (Universal Serial Bus Device Firmware Upgrade) protocol.

In the Openmoko project, we use this program to communicate with our specially enhanced [[U-Boot]], which implements the DFU device side.

Using dfu-util and your smartphone, you can
* transfer and flash [[Partitions|partitions]] in internal [[NAND Flash]].
* transfer anything into RAM
** this can be used for fast development cycles of low-level code such as kernels without flashing them
* read out the current internal NAND [[Partitions|partitions]]
** this is an easy and efficient way of doing full backups of your phone

== Source Code ==
Dfu-util is currently maintained at http://dfu-util.gnumonks.org/.

On Debian and Ubuntu, you'll need libusb-dev:
sudo apt-get install libusb-dev autogen pkg-config autotools-dev autoconf automake

On Fedora you'll need libusb-devel and libusb-static:
yum install libusb-devel libusb-static

On Gentoo you can:
emerge -va openmoko-dfu-util

You can check out and build the latest version of dfu-util using the following git command: 
git clone git://git.openezx.org/dfu-util.git
 
cd dfu-util 
./autogen.sh 
./configure 
make

The resulting binary is dfu-util/src/dfu-util.

== Binaries ==

Binary packages will be [http://downloads.openmoko.org/distro/releases/Om2008.9/dfu-util made available] as part of the regular Openmoko builds. Currently, there is a dfu-util for Linux/i386.

You need to make the downloaded file (dfu-util) executable with:
<pre>
chmod +x dfu-util
</pre>
you can then run it with
<pre>
./dfu-util
</pre>
see below for full instructions.

=== Debian ===
[http://packages.debian.org/dfu-util dfu-util 0.0+r4880-1 is packaged] for Debian ''>= lenny'', so can be installed with: <tt>apt-get install dfu-util</tt>

=== Ubuntu ===
[http://packages.ubuntu.com/dfu-util dfu-util 0.0+r4067-3.1 is packaged] for Ubuntu ''>= intrepid (8.10)'', so can be installed with: <tt>apt-get install dfu-util</tt>

=== Slackware ===
[http://downloads.sourceforge.net/slackfr-packs/dfu-util-svn4686-i686-1cfdev12.1.tgz dfu-util is packaged] for '''Slackware''' (12.1), so can be installed with: <tt>pkgtool</tt>

A newer SlackBuild is also available on [http://slackbuilds.org/repository/13.1/system/dfu-util/ slackbuilds.org]

=== Arch Linux ===
[http://aur.archlinux.org/packages.php?ID=21385 dfu-util is packaged] for Arch Linux, so can be installed with makepkg

=== openSuSE ===
The links below install rpm packaged dfu-util in (open)SuSE :

[http://software.opensuse.org/ymp/home:worldcitizen/SLE_10/dfu-util.ymp 1-Click Install for SLE 10]

[http://software.opensuse.org/ymp/home:worldcitizen/SLE_11/dfu-util.ymp 1-Click Install for SLE 11]

[http://software.opensuse.org/ymp/home:worldcitizen/openSUSE_10.3/dfu-util.ymp 1-Click Install for openSuSE 10.3]

[http://software.opensuse.org/ymp/home:worldcitizen/openSUSE_11.0/dfu-util.ymp 1-Click Install for openSuSE 11.0]

[http://software.opensuse.org/ymp/home:worldcitizen/openSUSE_11.1/dfu-util.ymp 1-Click Install for openSuSE 11.1]

[http://software.opensuse.org/ymp/home:worldcitizen/openSUSE_Factory/dfu-util.ymp 1-Click Install for openSuSE Factory]

=== CentOS ===
[http://download.opensuse.org/repositories/home:/worldcitizen/CentOS_5/ Centos 5]

=== Fedora ===
[http://download.opensuse.org/repositories/home:/worldcitizen/Fedora_10/ Fedora 9]

[http://download.opensuse.org/repositories/home:/worldcitizen/Fedora_10/ Fedora 10]

=== Mandriva ===
[http://download.opensuse.org/repositories/home:/worldcitizen/Mandriva_2008/ Mandriva 2008]

[http://download.opensuse.org/repositories/home:/worldcitizen/Mandriva_2009/ Mandriva 2009]

=== RHEL ===
[http://download.opensuse.org/repositories/home:/worldcitizen/RHEL_5/ RHEL 5]

=== Gentoo ===
DFU-Util is in the main tree under the name [http://packages.gentoo.org/package/app-mobilephone/openmoko-dfu-util openmoko-dfu-util].

=== Windows ===
Currently, there is a largely untested binary for Win32 (see [[Dfu-util-windows]]). Windows users can refer to [[No_Linux]] for a more tested approach.

=== Mac ===
Compiling dfu-util on Mac:
* http://lists.openmoko.org/pipermail/community/2007-July/008438.html
* [[User:SNMoore]]
* [[MacOS_X#Flashing_to_your_device]]
* [[Openmoko Flasher]] has a precompiled binary in the App bundle

== Manual ==

See [[Manuals/Dfu-util]]

== See also ==
*[[Flashing the Neo 1973]]
*[[Flashing the Neo FreeRunner]]

[[Category:Flashing Openmoko]]

Flash

2012-02-13T17:20:21Z

Glenn: more

*[[Flashing]] Neo phones
*[[Adobe Flash]]

Flash

2012-02-13T17:19:58Z

Glenn: new

*[[Flashing]]
*[[Adobe Flash]]

Flashing

2012-02-13T17:19:34Z

Glenn: -link

*[[Flashing the Neo FreeRunner]]
*[[Flashing the Neo 1973]]

[[Category:Flashing Openmoko]]

Flashing

2012-02-13T17:18:54Z

Glenn: +adobe flash

*[[Flashing the Neo FreeRunner]]
*[[Flashing the Neo 1973]]
*[[Adobe Flash]]

[[Category:Flashing Openmoko]]

Flash

2012-02-13T17:18:36Z

Glenn: Redirecting to Flashing

#REDIRECT [[Flashing]]

Open GSM Radio

2012-02-12T12:53:21Z

Glenn: Open GSM Radio moved to Open GSM modem

#REDIRECT [[Open GSM modem]]

Open GSM modem

2012-02-12T12:53:21Z

Glenn: Open GSM Radio moved to Open GSM modem

[http://en.wikipedia.org/wiki/GSM GSM] is the mobile standard supported by the Neo1973.

The modem in the phone is not open source, it is talked to over a serial interface.

A number of applications could be made possible if the source was available to the modem.
These include:
*Moving some policy inside the modem, so that it could take a list of numbers to wake the CPU on, and a list of numbers to ignore. To reduce battery use.
*Access to packet by packet signal strengths and timings to aid with positioning.

Unfortunately.

There is a fundamental problem.

GSM works so well because the towers are carefully planned.
They are designed so they don't interfere with each other.

If nobody does anything bad, this all 'just works'.

However, if someone wrote a 'free local data' transmitter, which simply used the modem to send direct to another modem, it would jam a GSM channel.
If you are not much further away from the tower than people making phone-calls, then your signal strength will be strong enough to knock 8-16 phone users off the channel.

These users may simply be able to redial, and they will get through.

On the other hand, it would only take a few users using this sort of software to completely prevent anyone from making phone calls in the area unless they were significantly closer to the tower than the users of this software.

This can be tens, or hundreds of square kilometers in rural areas.

Some of these calls will be emergency calls.

In addition http://www.cellular-news.com/story/8970.php and http://www.google.co.uk/url?sa=t&ct=res&cd=7&url=http%3A%2F%2Fwww.parliament.uk%2Fcommons%2Flib%2Fresearch%2Frp2002%2Frp02-047.pdf&ei=RpenRou1GZSoxAGe9fDQBw&usg=AFQjCNF7EpgFaUwd76UJnDYE2k8aOPUpqg&sig2=xfCyHIkKrhw4y7XyDcyv_g are examples of legislation, which makes sale of equipment able to change IMEI illegal. This would make it illegal to sell phones of this sort once the first one is misused.

==See also==
* [[Osmocom on TI Calypso]]

[[Category:GSM]]

GTA04

2012-02-12T10:41:01Z

Glenn: /* GTA04A4 */ spelling

'''News:'''
* There is a new mailing list dedicated to the early adopters of this project: http://lists.goldelico.com/mailman/listinfo/gta04-owner
* general discussions should be continued on the Openmoko Community lists: http://lists.openmoko.org/mailman/listinfo/community

----

The codename '''GTA04''' was picked up in 2010 by Golden Delicious Computers to develop a new motherboard for our open smartphone that follows the original idea and goals.

There is a new project page: http://www.gta04.org, which houses the wiki specific to the GTA04 project at Golden Delicious.

== GTA04A4 ==

GTA04A4 is a new motherboard, that replaces the one inside your Neo 1973 ([[GTA01]]) or Neo Freerunner ([[GTA02]]). It reuses the case, the battery, the display, the antenna and speaker(s). GTA04 [http://projects.goldelico.com/p/gta04-main/page/FeatureList/ hardware features is here].

The GTA04A4 motherboard PCB layout development is based on GTA04A3 and its start was announced at [http://lists.goldelico.com/pipermail/gta04-owner/2011-October/000385.html 7 October 2011].

The replacement, populated GTA04, motherboard is available at [http://www.handheld-linux.com/wiki.php?page=GTA04 Golden Delicious]. A complete [http://www.handheld-linux.com/wiki.php?page=GTA04%20Complete OpenPhoenux aka GTA04 Complete can be bought here]

On [http://lists.goldelico.com/pipermail/gta04-owner/2011-November/000679.html 14th November 2011] GTA04A4 boards became available for (pre)order. [http://lists.goldelico.com/pipermail/gta04-owner/2012-January/001379.html First batch started shipment 31 January 2012].

== History ==

=== Year 2011: GTA04A3 (Early Adopter) ===
The GTA04A3 was released and shipped 10. october 2011.

The GTA04A3 milestone was announced 7. october 2011.([http://lists.goldelico.com/pipermail/gta04-owner/2011-October/000385.html source])

GTA04A3 is a new motherboard, that replaces the one inside your Neo Freerunner ([[GTA02]]). It reuses the case, the battery and the display.

Video:
* [http://www.youtube.com/watch?v=PgZzxmHzWtg GTA04A3 in a homemade box with Qtmoko installed]
* [http://www.youtube.com/watch?v=gCjM48BqfYo GTA04-Tester] Quote: "...This video shows the first 3 fresh GTA04A3 boards and how they are tested..."

The early adopter program [http://www.handheld-linux.com/wiki.php?page=GTA04-Early-Adopter was available here].

==== Specifications ====
GTA04A3 features ([http://projects.goldelico.com/p/gta04-main/page/Old-GTA04-revisions/ source]):

* [http://focus.ti.com/lit/ds/symlink/dm3730.pdf TI OMAP 3730] DCBB (800 MHz) (compatible to [http://www.beagleboard.org])
** integrated graphics - POWERVR SGX Graphics Accelerator of OMAP3730
* 512MB RAM/512MB NAND ([http://www.micron.com/products/ProductDetails.html?product=products/mcp/multichip_packages/MT29C4G96MAZAPCJG-5+IT Micron 8Gb DDR/NAND PoP Memory])
* Wi2Wi WLAN/Bluetooth module + antenna
* GTM601W UMTS module
* GPS module + antenna switch
* Option:
** LSM303 (compass and accelerometer)
** ITG3200 (gyroscope)
** BMP085 (barometric altimeter)
** BMA180 (LIS302 on a few) (accelerometer)
** Si4721 or Si4705 (FM transceiver/receiver)

=== Year 2010: GTA04A2 ===

The GTA04A2 was the result of integrating GTA04A1/[[Openmoko Beagle Hybrid]] all onto a single PCB.

GTA04A2 was presented at [http://en.wikipedia.org/wiki/FOSDEM FOSDEM] 2011.

Videos:
* [http://www.youtube.com/watch?v=3KnJc7eImQ4 booting GTA04A2].
* [http://www.youtube.com/watch?v=wG31rCHZXh4 Boot Speed Comparison] Quote: "...This video shows a comparison of a Openmoko GTA02 (with OM2009.05), a GTA04 board with Debian Squeeze/LXDE and a iPhone 3G..."

=== Year 2010: Openmoko Beagle Hybrid GTA04A1 ===
Golden Delicious Computers has been secretly working on a OMAP3530 based project that apparently has the same target as Openmoko's GTA04 did have. The first result was announced in 2010 [[Openmoko Beagle Hybrid]] aka GTA04A1.

Videos:
* [http://www.youtube.com/watch?v=Wuarto_s4F0 Openmoko Beagle Hybrid in operation]

=== Year 2008: Openmoko Inc. GTA04 ===
'''GTA04''' was the codename of a phone that was whose development was canceled (within Openmoko, Inc.). For more information about other phones in development, visit [[Phone Development]]. This phone would have been based on a different system-on-a-chip.

==== Specifications ====
The GTA04 would have been a [[GTA03]] but with a major hardware revision

New:
* USB 2.0 would be added on the GTA04 at the earliest
* 3G would be added on the GTA04 at the earliest
* Based on a more advanced SoC
* maybe based on the samsung 6400 or 6410
* integrated graphics
* Sean put a hiring on the community and devel list, see [http://lists.openmoko.org/pipermail/community/2008-September/029710.html here] so there will be OpenGL Es and the 6410 eventually
* there had been meetings in April 2008 within Openmoko - see [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-April/002310.html]

[[Category:GTA04| ]]

USB Networking

2012-02-12T08:20:54Z

Glenn: /* Openmoko Networking Setup */ update

[[Category:USB software]]
[[Category:Implemented]]

{{Languages|USB_Networking}}

{|align=left
|__TOC__
|}

= Openmoko Networking Setup =

In order to communicate via TCP/IP to your FreeRunner, a basic understanding of the networking expectations is required. Each end of the USB connection forms a LAN (local area network) segment, with the FreeRunner's USB networking device at one end (default 192.168.0.202) and your laptop or desktop at the other end (192.168.0.200 in this guide).

{{Note|IP adresses are changed in new SHR-CORE images after 110822, phone 192.168.7.2 host: 192.168.7.1}}

Normally, your desktop machine will know how to reach the Internet, having had its gateway (the IP address of the machine or device which knows how to send packets to machines beyond your subnet) configured via DHCP or statically (probably via a router). For the FreeRunner to reach the Internet, your desktop will have to be configured to route and masquerade (NAT) packets from it.

Normally, none of this is an issue, but problems can arise when the subnet between the FreeRunner and your desktop overlap with the desktop to the router (which forms a second LAN), since your desktop might not know how to route traffic properly.

In other words: if your existing router and desktop have addresses 192.168.0.(something) changing them to e.g. 192.168.1.(something) might save you a lot of troubleshooting later. A discussion of this is [http://lists.openmoko.org/pipermail/support/2008-August/thread.html#1277 here].

== Things to keep in mind ==

=== Suspend ===

When the FreeRunner suspends it disables its USB networking interface. Therefore it is a good idea to turn off the FreeRunners suspend function when using USB networking.

=== So is it "usb0" or is it "eth1"? ===

* The documentation below refers to the network interface name on the host side as "usb0". However, the actual name is determined by your host system, and many host systems will rename the interface based on the mac (or hardware) address presented by the Neo or Freerunner. Use the <code>ifconfig -a</code> command, or use <code>dmesg</code> to examine the output from your host's kernel, to find which interface name was actually assigned to your device. If it wasn't "usb0", it will almost always be the next available "eth''n''" name.

In all the steps below where you see the interface referred to as "usb0", you may need to substitute the interface name that your host assigned.

For those interested in the technical details, the "usb0" interface name is used on the host system when the mac (hardware) address presented by the Freerunner or Neo is a locally-generated (random) address. Because the address is random, the ability to easily manage the interface with network managment tools is somewhat compromised. In fact, the Freerunner has been assigned official mac addresses, including addresses for the USB network interface. When these addresses are correctly used on the Freerunner (which is the case with the Qi bootloader, and with certain of the distros for the Freerunner), then the host system sees official mac addresses, and responds by configuring a permanent network interface for that device. By convention, this permanent interface is one of the "eth" interfaces. The specific interface name chosen will be remembered, and will be used each time that specific Freerunner is connected, and used only for that Freerunner. This is a particularly useful feature for users who have multiple USB-networked devices.

As of the time of this writing, the Android and SHR distros will correctly pass the official mac address to the host, and will appear as "eth''n''" interfaces on the host.

=== My distro ===

There are many differences between distributions, both on the phone and on the desktop. Also within a single distribution there can be big changes over time, so remember that solutions provided here might not always exactly match your situation.

If all your approaches fail, you might want to consider using [http://knopper.net/knoppix/index-en.html Knoppix] (6.3 WorkedForMe(tm)) or another [http://distrowatch.com/dwres.php?resource=cd live distribution].

{{Note|IP adresses are changed in new SHR-CORE images, phone 192.168.7.2 host: 192.168.7.1 so use theses adresses if you use the manual}}

= Simple Manual Linux Configuration =
Try this first (as root on your desktop, with FreeRunner attached via USB cable and booted properly, not at the Boot Menu). If it works, then you can add permanent configuration or use more sophisticated setups below.
=== The shortest way ===
This simple way has been tested with many Linux distributions (Fedora, SuSE, Red Hat, Debian and others) and network configurations. It was even successfully applied to connect another Linux based handhelds like TDS Nomad and surely can be recommended as the first attempt. The way assumes that you have the recent Linux distribution with USB networking enabled and also rather typical network setup.

With the device connected configure usb0 interface (as root or via sudo like in this example):
<pre>
sudo ip address add 192.168.0.200/24 dev usb0
sudo ip link set dev usb0 up
</pre>
or (deprecated)
<pre>
sudo ifconfig usb0 192.168.0.200 netmask 255.255.255.0 up
</pre>
If your eth0 interface is also in the same 'range' (e.g. 192.168.0.105) then you can do the following:
<pre>
sudo route add -host 192.168.0.202 dev usb0
</pre>

=== The login ===

Log in to the Neo (you do not need to be a root on the desktop host just to log in).
$ ssh root@192.168.0.202

On some SHR Version the default root password is blank.

'''If you get an error like: "Permission denied, please try again." try to set a new password on the phone:'''

open a terminal on the phone and type:

passwd

then enter a new password and establish a new ssh connection.

Note that an '''empty passwords''' won't work on some SHR releases!

Do not forget to allow ssh (open the port 22) on your firewall so that you can connect to the device. If you suspect any firewall issues, the simplest way is to unplug the main Internet cable leaving only Neo connected and then temporary turn the firewall off.

Also, some old or narrowly configured Linux distributions may not have USB networking support. For such cases the simple way might be just to upgrade.

=== The more advanced way ===
If the previously described simple approach does not work, you may try the more complex one.

<pre>
sudo iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sudo sysctl -w net.ipv4.ip_forward=1
sudo ip addr add 192.168.0.200/24 dev usb0
</pre>

If your Internet connection is also in the range 192.168.0.x then instead you might want to use only:

<pre>sudo ip addr add 192.168.0.200/28 dev usb0</pre>

(This will just map the net from 192.168.0.192 to 192.168.0.207 onto usb0. If you get the error 'Cannot find device "usb0"', double-check that your FreeRunner is turned on and connected by USB. Ensure also that the uhci_hcd module is loaded on your PC. If that doesn't work, try unplugging and replugging the USB cable.)

And in this case you should enable ARP proxy on internet facing interface INSTEAD of using iptables:

<pre>sudo sysctl net.ipv4.conf.eth2.proxy_arp=1</pre>

This assuming that eth2 is connected to ISP.

Then
<pre>sudo ip link set usb0 up</pre>
or (deprecated)
<pre>sudo ifconfig usb0 up</pre>

Then (ideally, not as root):

<pre>ssh root@192.168.0.202</pre>

The default password is blank.

Due to the fact that in most cases your Neo will use the same dns servers as your computer uses, you can automate the process of writing dns servers to your phone:

<pre>#!/bin/sh
/sbin/route add -host 192.168.0.202/32 dev usb0
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
iptables -P FORWARD ACCEPT
sysctl -w net.ipv4.ip_forward=1
scp /etc/resolv.conf root@192.168.0.202:/etc/resolv.conf</pre>

Again if your net already is 192.168.0.0, replace the POSTROUTING statement with
<pre>iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/28</pre>

This simple script will set up routing for your Freerunner and than copy resolv.conf with dns addresses straight to the phone.
All you have to do is connect phone to the computer, run the script and enjoy internet connection from your phone.

=== Changing the Neo IP address ===

Like mentioned above, if the default Neo subnet 192.168.0.X is already used, it might be necessary to change the
Neo [http://en.wikipedia.org/wiki/IP_address IP adress] and subnet.
To achieve this, edit /etc/network/interfaces on the Neo (and do "/etc/init.d/networking restart").
In the following example the Neo will use the IP address 192.168.100.1 (instead of the default 192.168.0.202)
within the network 192.168.100.X (instead of 192.168.0.X),
another [http://en.wikipedia.org/wiki/Private_network private] class C network.
(The [http://en.wikipedia.org/wiki/Subnetwork#Binary_subnet_masks netmask] indicates that the first 3 bytes (all bits set) are used to determine the subnet
and the last byte (no bits set) to determine the machine.)
The gateway (the computer, the Neo is attached to) also has to be part of the subnet and is expected to be 192.168.100.200 (instead of 192.168.0.200) here.

Modifications for /etc/network/interfaces:

<pre>
auto usb0
iface usb0 inet static
address 192.168.100.1
netmask 255.255.255.0
network 192.168.100.0
gateway 192.168.100.200
</pre>

(The network entry seems to be redundant information, since it can be derived from address and netmask?)
Note that wiki articles usually expect default settings and you have to adjust the IP adress, gateway, etc entries according to your changes.

= Linux Kernel Support =

Your Linux desktop/laptop needs to have suitable support. In particular you will need to have enabled USB networking and masquerading support in the kernel. For default kernels in many Linux distributions this will already be the case.

== USB Networking support ==

The following options need to be enabled:

* CONFIG_USB_USBNET (''Multi-purpose USB Networking Framework''. Module will be called <tt>usbnet</tt>)
* CONFIG_USB_NET_CDCETHER (''CDC Ethernet support''. Module will be called <tt>cdc_ether</tt>)

These options are available in ''Device Drivers -> USB support -> USB Network Adapters'' or ''Device Drivers -> Network Device Support -> USB Network Adapters.

In order for USB networking to work you need to load the <tt>cdc_ether</tt> module (when loading <tt>cdc_ether</tt> the module <tt>usbnet</tt> will be loaded automatically). For more info see the [http://www.linux-usb.org/usbnet/ usbnet driver homepage].

Olamba

== Masquerading support ==

Masquerading options are found in ''Networking ---> Networking options --->'' (tested on Linux 2.6.26.3).

To enable the needed options you first have to enable:

* CONFIG_NETFILTER (''Network packet filtering framework (Netfilter)'')

Then, from

''Networking --->
Networking options --->
[*] Network packet filtering framework (Netfilter) --->
Core Netfilter Configuration --->''

You need at least following options enabled as modules:

* CONFIG_NF_CONNTRACK (''Netfilter connection tracking support'')
* CONFIG_NF_CONNTRACK_FTP (''FTP protocol support'')
* CONFIG_NETFILTER_XTABLES (''Netfilter Xtables support'')

Rest of the needed options are found from

''Networking --->
Networking options --->
[*] Network packet filtering framework (Netfilter) --->
IP: Netfilter Configuration --->''

You need to enable (again, as modules is fine):

* CONFIG_NF_CONNTRACK_IPV4 (''IPv4 connection tracking support (required for NAT)'')
* CONFIG_IP_NF_IPTABLES (''IP tables support (required for filtering/masq/NAT)'')
* CONFIG_NF_NAT (''Full NAT'')
* CONFIG_IP_NF_TARGET_MASQUERADE (''MASQUERADE target support'')

= Firewall Issues =

On some systems, you may have firewall rules which prevent this working - such as added by the iptables service on Fedora. You may care to stop these, and/or review any rules or policies you think might cause issues.

The most relevant table is the nat table, which controls translation of addresses:

iptables -L -t nat -v -n

Unless you have a special setup, you'll want to see only the MASQUERADE rule that you apply below, and ACCEPT as the default policy. Also look at the filter table:

iptables -L -t filter -v -n

If this contains anything in the FORWARD chain, then this may prevent passing packets. It can be flushed with:

iptables -t filter -F FORWARD

= Other Issues =

In case the Freerunner was recognized and you could assign the IP address to the device, but you get after trying to connect with 'ssh root@192.168.0.202' an error like:

<pre> ssh: connect to host 192.168.0.202 port 22: No route to host </pre>

Then your USB cable could be broken. Try to connect with another cable.

== Regular drop-outs ==
If you've connected, and your connection keeps dropping and then coming back up, make sure that you don't have automatic wireless network connections - in some distros, the the wireless connection scripts automatically disable the usb network interface.

= DNS =

In addition to routing issues, to be practical, DNS will need to work. In some cases, you might already be running a DNS server on your desktop such as dnsmasq or bind9, which is the default assumption the FreeRunner makes. In other cases, you'll need to configure DNS to that of your router, or a DNS server further out on the internet such as that provided by your ISP.

== Configure Default Neo DNS ==

DNS is configured in /etc/resolv.conf on your FreeRunner.

You should add the IP address of the DNS servers as provided by your ISP. Check your router's or PC's network status for the nameserver IP addresses.

<pre>echo nameserver xxx.xxx.xxx.xxx > /etc/resolv.conf</pre>

You can also add the public DNS server called openDNS:
<pre>echo nameserver 208.67.222.222 > /etc/resolv.conf
echo nameserver 208.67.220.220 >> /etc/resolv.conf</pre>

These settings will be lost on reboot. You can set the DNS for the next connect, by adding the following to the end of the usb0 setting in /etc/network/interfaces, right above the bluetooth networking section:
<pre>up echo nameserver 208.67.222.222 > /etc/resolv.conf
up echo nameserver 208.67.220.220 >> /etc/resolv.conf</pre>

== Proxying DNS from Desktop/Laptop ==

If you move about, making assumptions about the network may not be convenient, and it is possible to proxy DNS requests via your host laptop (which you are also taking with you), without running or installing a DNS server. There are a number of ways to do this:

=== Proxying with dnrd ===

The script is designed to use [http://dnrd.sourceforge.net/ dnrd] as the DNS proxy. The [http://buildhost.automated.it/gta01 script] and a copy of [http://buildhost.automated.it/dnrd-2.20.3.tar.gz dnrd] are available. The script also performs the initial setup of the connection as per the [[USB_Networking#Manual_method]] above.

=== Proxying with a UDP forwarder ===

Another easy setup is using a UDP forwarder like the one from ('''BROKEN LINK REMOVED''') - use it with the command"

<pre>udpf-elf -p=53-f=`awk '$1 == "nameserver"{print $2; exit(0);}' /etc/resolv.conf`:53</pre>

=== Proxying with iptables ===

It is possible to forward DNS requests with iptables using the DNAT target:

<pre>iptables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200 --dport domain -j DNAT --to-destination 192.168.0.1</pre>

Where <tt>192.168.0.1</tt> is the IP of your router.

Test if it works:
<pre>ping www.google.com</pre>

If so, then this is sufficient for most internet access. But manual changes to resolv.conf are usually lost later if for example one uses DHCP, especially for WiFi, and so may not be convenient to configure manually.

= Testing Your Connection =
You should be able to connect to your Neo! Make sure you can ping your Neo to be sure.
ping 192.168.0.202

Then log into your Neo using ssh:
ssh root@192.168.0.202
The default password is blank (press enter).

You can also [[scp]] files back and forth. You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

Now, make sure you can ping back to your desktop
ping 192.168.0.200
(Note that some systems like Vista, don't respond to ICMP ping by default)

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
This demonstrates that masquerading is working - your desktop is sending/receiving packets to the wider internet.

Lastly, verify that DNS is correctly configured between the Neo & Network:
ping www.google.com

== Connection script ==
With the contents of this page [[User:Cristianpark|I]] made [http://www.mediafire.com/download.php?zm0gtz2tyjq this script] to easily get your FreeRunner connected with your PC.

All you have to do is run the script (after connect the FR to the PC):
<pre>sudo sh usb_networking.sh</pre>
You have to:
# Disconnect FreeRunner
# Connect it again
# Re-run the script and voila the connection is there!

; Notes
* It needs root privileges to be executed for the iptables and sysctl commands (if you don't like sudo, login as root instead)
* It uses the eth1 interface so on OM and other distros different from SHR, you have to put usb0
* Thanks to Tony Berth: if the first time you run the script you can't ping/access 192.168.0.202.

= OS or Distro Specific & Automatic Configuration =

Based on Hotplugging usbnet ('''BROKEN LINK REMOVED''') by Marcin 'Hrw' Juszkiewicz.
These instructions should keep you from having to run the Simple Manual Linux Configuration every time you plug in and want to connect to an Openmoko device. One run and then you're done!

If the Simple Manual Linux Configuration does not work for your OS or Distro (MacOS X, MS Windows, etc) there may be instructions here that work for you.

== MacOS X ==
See [[MacOS_X#USB_Networking|MacOS X USB Networking]].

== Windows ==
See [[Neo1973_and_Windows#USB_Ethernet_emulation|Windows USB Ethernet emulation for Neo1973]].

There is also a very helpful tutorial for connecting with Vista at [http://sam.curren.ws/index.cfm/2008/7/14/Using-the-Neo-FreeRunner-with-Windows-XPVista].

== FreeBSD ==
You need to load the cdce kernel module (if it is not already linked into your kernel). As root do:

# kldload cdce

The Neo should then show up as cdce0 interface and you can handle the cdce0 interface just like the usb0 device under Linux. For more information see the cdce manpage. An easy way to assign the IP address to the cdce0 interface is using the devd(8) daemon. Create the following two files,

<tt>/usr/local/etc/devd/cdce.conf</tt> as:

<pre>
notify 1 {
match "system" "IFNET";
match "subsystem" "cdce0";
match "type" "ATTACH";
action "/usr/local/etc/devd/cdce.sh $subsystem $type";
};
</pre>

and <tt>/usr/local/etc/devd/cdce.sh</tt> as:

<pre>
#!/bin/sh
case $2 in
'ATTACH')
ifconfig cdce0 192.168.0.200 netmask 255.255.255.0
exit 0 ;
;;
esac
exit 0
</pre>

Then restart the devd(8) daemon with:

# /etc/rc.d/devd restart

If you now plugin the FreeRunner into the USB port the cdce0 interface gets created and the IP addr will be assigned.

== FreeBSD8 ==
If your kernel report
kernel: ugen5.2: <Linux 2.6.29-20100118.gita15608> at usbus5

add to /etc/devd.conf:
<pre>
attach 100 {
device-name "ugen[0-9]+";
match "vendor" "0x1457";
match "product" "0x5122";
action "perl /usr/local/etc/neo_if.pl /dev/$device-name";
};
</pre>

If your kernel report
kernel: ugen1.2: <Linux 2.6.34.x.y.z> at usbus5 (it happens for QtMokov28)

add to /etc/devd.conf:
<pre>
attach 100 {
device-name "ugen[0-9]+";
match "vendor" "0x0525";
match "product" "0xa4a2";
action "perl /usr/local/etc/neo_if.pl /dev/$device-name";
};
</pre>
The two entryes in /etc/devd.con can coexists, so it's a good idea to have both inserted.
Anyway you can collect all the required information for your actual distribution with usbconfig. For example:
<pre>
# usbconfig | grep -i linux
ugen1.2: <RNDIS/Ethernet Gadget Linux 2.6.34.2-v28 with s3c2410_udc> at usbus1, cfg=1 md=HOST spd=FULL (12Mbps) pwr=ON

#usbconfig -d ugen1.2 dump_device_desc
ugen1.2: <RNDIS/Ethernet gadget Linux 2.6.34.2-v28 with s3c2410_udc> at usbus1, cfg=1 md=HOST spd=FULL (12Mbps) pwr=ON

bLength = 0x0012
bDescriptorType = 0x0001
bcdUSB = 0x0200
bDeviceClass = 0x0002
bDeviceSubClass = 0x0000
bDeviceProtocol = 0x0000
bMaxPacketSize0 = 0x0008
idVendor = 0x0525
idProduct = 0xa4a2
bcdDevice = 0x0312
iManufacturer = 0x0001 <Linux 2.6.34.2-v28 with s3c2410_udc>
iProduct = 0x0002 <RNDIS/Ethernet Gadget>
iSerialNumber = 0x0000 <no string>
bNumConfigurations = 0x0002
</pre>

Create /usr/local/etc/neo_if.pl:
<pre>
#!/usr/bin/perl
my ($u, $ad) = $ARGV[0] =~ /(\d+)\.(\d+)$/;
print ("usage: $0 /dev/ugen4.2\n"), exit unless (length $u and length $ad);
print `usbconfig -u $u -a $ad set_config 1
#ifconfig ue0 link 00:1f:11:01:71:62 # uncomment if moko reports: usb0: duplicate address detected!
ifconfig ue0 192.168.0.200/24`;
</pre>

== Debian, Ubuntu and others ==

There are two systems which deal with hotplugginng devices, which is what you do when you plug in Freerunner in an USB port. '''udev''' and the older '''Hotplug''' system.

=== Systems using '''udev''' ===

There are 2 common ways the USB networking device can be handled by your systems.

If there is a definition for the USB networking device in /etc/network/interfaces, it is handled by the '''ifupdown''' system. If not, it is handled by '''NetworkManager'''.

It is possible to use network-manager to automatically connect to the Freerunner using udev. The process uses udev to run a script when the Freerunner is plugged in.

==== For devices showing as usb0 ====

The script uses the ip command to set the mac address of the usb network interface.

To begin, create /etc/udev/rules.d/80-freerunner.rules :

<pre>
# This file causes programs to be run on device insertion.
# See udev(7) for syntax.
# rule to assign a fixed mac address specified in /
KERNEL=="usb[0-9]*", DRIVERS=="cdc_ether", ACTION=="add", RUN+="/usr/local/sbin/freerunner-usb-add.sh %k"
</pre>

Next, create the /usr/local/sbin/freerunner-usb-add.sh :

<pre>
#!/bin/sh
(
busNum=$( printf %.2d $( expr match "$1" "usb$[0-9]*$") )
ip link set "$1" address 00:00:22:55:bb:$busNum &> /dev/null
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -P FORWARD ACCEPT
) &
exit 0
</pre>

==== For devices showing as eth1 ====

This script allows ipforwarding so your device can access the internet through your pc.

To begin, create /etc/udev/rules.d/80-freerunner.rules replacing the mac address with the one from your device (run ifconfig on the pc, or use udevinfo, note that it must match udev's case):

<pre>
# This file causes programs to be run on device insertion.
# See udev(7) for syntax.
# http://www.reactivated.net/writing_udev_rules.html#example-netif
KERNEL=="eth*", ATTR{address}=="00:1f:11:01:28:d6", RUN+="/usr/local/sbin/freerunner-usb-add.sh"
</pre>

Next, create the /usr/local/sbin/freerunner-usb-add.sh :

<pre>
#!/bin/sh
(
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -P FORWARD ACCEPT
) &
exit 0
</pre>

==== For all devices ====
Finally run
chmod +x /usr/local/sbin/freerunner-usb-add.sh
to make it executable. Now you can use network-manager with '''mac-address specific settings''' and get it to automatically connect.

* Plug your phone into your computer's usb port.
* Note the mac address from "ifconfig usb0" (or eth1)
* Right-click the network manager icon in the panel.
* Click "Edit Connections..."
* Delete the "Auto usb0" entry. (or eth1)
* Add a new connection named 'freerunner' (or whatever you fancy)
* Tick "System setting"
* Enter the mac address from above.
* Click the "IPv4 Settings" tab.
* Change "Method" to "Manual"
* Add an address of 192.168.0.200, 255.255.255.0 (address and netmask respectively).
* Click "Ok"
* Enter your system password (if prompted) to allow changing of this system setting.

(watch out for this bug: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/284298 )

You should now be able to ping/ssh your phone.

===Systems using''' hotplug''' - Using the interfaces file ===
Edit /etc/network/interfaces and add:

<pre>
# freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
up iptables -A POSTROUTING -t nat -s 192.168.0.0/24 -j MASQUERADE
up echo 1 > /proc/sys/net/ipv4/ip_forward
down iptables -D POSTROUTING -t nat -s 192.168.0.0/24 -j MASQUERADE
</pre>

This is more sophisticated than the manual setup. The 'auto usb' stanza ties into the Linux hotplug system so that when the device appears and vanishes, as happens when the FreeRunner is connected via USB, this is run.

In addition, the desktop-side netmask is limited to a much smaller range, so that overlapping subnets are less of a problem - Linux will use more specific routes first when deciding where to send packets.

Another possible configuration that adds DNS forward and removes
the iptables changes after unplugging:

in /etc/network/interfaces add
<pre>
# freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.192
post-up /etc/network/freerunner start
pre-down /etc/network/freerunner stop
</pre>

create file /etc/network/freerunner
<pre>
#!/bin/sh
#
# configures the freerunner for internet
#
#

DEVICE=usb0
IPADDR=192.168.0.200
REMOTE_IPADDR=192.168.0.202
NETMASK=255.255.255.0

# get first ip for dns
DNSIP=$(awk '$1 == "nameserver"{print $2; exit(0);}' /etc/resolv.conf)

case "$1" in
start)
iptables -A POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -A PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -A PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ "$(cat /proc/sys/net/ipv4/ip_forward)" = "0" ]; then
echo "temoprarely allow ip_forward for openmoko" > /var/run/openmoko.ip_forward
echo 1 > /proc/sys/net/ipv4/ip_forward
fi
;;
stop)
iptables -D POSTROUTING -t nat -j MASQUERADE -s $REMOTE_IPADDR
iptables -D PREROUTING -t nat -p tcp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP
iptables -D PREROUTING -t nat -p udp -s $REMOTE_IPADDR -d $IPADDR --dport domain -j DNAT --to-destination $DNSIP

if [ -f /var/run/openmoko.ip_forward ]; then
rm /var/run/openmoko.ip_forward
echo 0 > /proc/sys/net/ipv4/ip_forward
fi
;;
esac
</pre>

Make /etc/network/freerunner executable with
chmod +x /etc/network/freerunner

=== Ubuntu 9.10 - the Karmic Koala ===

Karmic has a bug in one of the upstart scripts, that makes it fail to properly bring down an unplugged network device (not just USB networking).

Edit <tt>/etc/init/network-interface.conf</tt> and replace this line

<pre>stop on net-device-removed INTERFACE=$INTERFACE</pre>

... with this

<pre>stop on net-device-remove INTERFACE=$INTERFACE</pre>

If you use <tt>/etc/network/interfaces</tt>, make sure the device is marked 'auto'. Plugging and unplugging will then work automatically.

('allow-hotplug' doesn't work, because upstart on ubuntu doesn't support 'allow-hotplug' defined devices)

=== Ubuntu 9.04 - the Jaunty Jackalope ===

One can see /etc/udev/rules.d that a device plugged in on USB will be called '''eth1''' (or '''eth2''' etc.). Go to System->Administration->Network (or edit /etc/network/interfaces) and add the parameters for eth1; static ip 192.168.0.200, netmask 255.255.255.192

=== Ubuntu 8.10 - Easy Way ===

:1. Connect Neo to PC and wait about a minute when NetworkManager stops scanning usb for dhcp (wait when icon in the tray switches to normal).

:2. Open "nm-connection-editor", select "Auto usb0", click "Edit", then "IPv4 Settings". Set "Method" - "Manual", click "Add". In the "Address" field write "192.168.0.200", "Netmask" - "255.255.255.0", leave "Gateway" field empty (or 0.0.0.0). Change the "Connection name" and click "Apply", then "Close".

:3. Now you can connect via ssh to 192.168.0.202

Note: After reflashing the Neo you have to copy the "MAC Address" from "Auto usb0" into your new connection.

Then, based on these instructions ('''BROKEN LINK REMOVED'''), you should be able to setup masquerading by running the following commands on your Ubuntu PC:

<pre>sudo iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
sudo iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
sudo iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sudo bash -c 'echo 1 > /proc/sys/net/ipv4/ip_forward'</pre>

=== Ubuntu Issues ===

Ubuntu 8.10 doesn't work as expected if you used /etc/network/interfaces to automate the connection. 
Network manager likes to latch onto the network device and add a default route through 192.168.0.202, breaking your network connection.
Network manager also says you can't edit or remove this connection from its list. I'm going back to making the connection manually. 
Using the /usr/local/sbin/freerunner-usb-add.sh script for some automatism can be a workaround:
<pre>
#!/bin/sh
(
ip address add 192.168.0.200/26 netmask dev usb0 > /dev/null
ip link set usb0 up > /dev/null
/etc/network/freerunner start
) &
exit 0
</pre>

Ubuntu Feisty, Gutsy and Hardy reportedly have a bug where ifdown is not run when the interface is unplugged, meaning this only works once after the system is booted. This is mentioned at https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/130437

One can patch /etc/udev/rules.d/85-ifupdown.rules. Moving the DRIVERS=="*?" out of the top GOTO, to ACTION=="add" line fixes the problem.

<pre>
SUBSYSTEM=="net", GOTO="net_start"
GOTO="net_end"

LABEL="net_start"

# Bring devices up and down only if they're marked auto.
# Use start-stop-daemon so we don't wait on dhcp
ACTION=="add", DRIVERS=="?*", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifup -- --allow auto $env{INTERFACE}"
ck
ACTION=="remove", RUN+="/sbin/start-stop-daemon --start --background --pidfile /var/run/network/bogus --startas /sbin/ifdown -- --allow auto $env{INTERFACE}"

LABEL="net_end"
</pre>

The bug is that the DRIVERS variable isn't set at all when the device is unplugged.

This appears to be fixed in Ubuntu 8.04 [[User:Mattt|Mattt]] 11:38, 30 July 2008 (UTC)
:Actually it appears that it's not fixed, but patching that file and disconnecting and reconnecting the phone works perfectly. --[[User:Johndoesacc|Johndoesacc]] 18:37, 20 August 2008 (UTC)
:Well, yes, it must be fixed because it worked for me out-of-the-box without tweaking the udev rule on 8.04 --[[User:EtienneG|EtienneG]] November 26th, 2008
:It wasn't solved in my case, as of 3. February 2009 in 8.04 (AMD64), the patch above solved my problem thou. --[[User:VilleWitt|VilleWitt]] February 3td, 2009.

====Iptables Configuration with GUI====

Firestarter can be used to allow the freerunner to connect to the internet without manually running iptables commands. Firestarter is in the ubuntu repositories and can be installed with a
<pre>sudo aptitude install firestarter</pre>
Once installed, the firestarter go to
* Edit > preferences dialog > network setting section,
* choose internet connection device (e.g. <tt>eth0</tt>)
* choose loacl area network device your Freerunner (generally <tt>usb0</tt>). You can select the device with a drop-down box, which is labeled "Local network connected device." Select the freerunner, generally "Unknown device(usb0)"
* check the "Enable internet connection sharing" box. Uncheck local network DHCP and the freerunner should be able to access the internet.
Tested in
* Ubuntu 8.10--[[User:makito|Makito]] February 26, 2009
* Ubuntu 9:04--[[User:chrestomanci|David]] September 2009
* Ubuntu 10.04 LTS, [[User:Niebert|Niebert]] July 2010
{{Note|Firestarter needs to run as root. Be aware that when firestarter is running it by default blocks all incoming connections, so if you where using your linux box as a mail-server, web-server or whatever those connections will be blocked. It is quick and easy to add exceptions for whatever protocol you are using in the policy tab of firestarter.}}

=== Ubuntu Workaround ===
Use [http://wicd.sourceforge.net/ wicd] instead of networkmanager:
It is much further in development than networkmanager yet and doesn't make any problems with USB networking. You can use the "normal" settings in /network/interfaces.
;Note: Because of it's dependencies it deinstalls networkmanager.

=== Ubuntu and QI ===
If you have trouble connecting to the freerunner after installing qi, check to see if the address has changed to eth<n>. Many host systems will assign eth<n> addresses when they detect an official (non-locally-generated) mac address on the usb network connection. Qi passes in the official Openmoko USB mac address; u-boot does not.

== Mandriva ==

This first file configures the network system for the usb0 interface. Any time you plug in the FreeRunner the interface will be configured.

<tt>/etc/sysconfig/network-scripts/ifcfg-usb0</tt>:

<pre>
DEVICE=usb0
BOOTPROTO=static
IPADDR=192.168.0.200
NETMASK=255.255.255.0
NETWORK=192.168.0.0
BROADCAST=192.168.0.255
ONBOOT=yes
METRIC=10
MII_NOT_SUPPORTED=no
USERCTL=yes
</pre>

This next file configures the static routes that we need to communicate to the subnet. Since it has "usb0" in the name, the system will automatically apply these static routes any time that the usb0 interface is configured. (i.e. when you connect the FreeRunner)

<tt>/etc/sysconfig/network-scripts/usb0-routes</tt>:

<pre>
ADDRESS0=192.168.0.200
NETMASK0=255.255.255.0
</pre>

Now we need to restart the network system to pick up the changes.

service network restart

This didn't work for me (Mandriva 2008.1), giving errors from Shorewall. However, simply using MCC, Network->Sharing Internet Access worked fine. You need to connect Neo when starting it. --[[User:Alih|Alih]] 18:50, 22 September 2008 (UTC)

== SuSE ==

/etc/sysconfig/network/ifcfg-usb0:

# USB configuration for PDAs (openmoko)
IPADDR=192.168.0.200
NETMASK=255.255.255.0
STARTMODE=onboot

For more information on getting USB networking up using YaST, see [[USB Networking with openSUSE]].

== Fedora ==

=== Option A - Tested with FC9, FC8 & FC5 ===

edit file <tt>/etc/sysconfig/network-scripts/ifcfg-usb0</tt> to look like this:

# USB configuration for PDAs (openmoko)
# from <nowiki>http://www.handhelds.org/moin/moin.cgi/UsbNet</nowiki>
DEVICE=usb0
BOOTPROTO=none
IPADDR=192.168.0.200
NETMASK=255.255.255.0
ONBOOT=yes

and restart networking service by typing:

service network restart

if your '''openmoko''' is connected when you restart network you should see system message:

<code>Bringing up interface usb0 [OK]</code>

=== Option B ===

This setup is probably over-complex:

/etc/sysconfig/network-scripts/ifcfg-usb0:

DEVICE=usb0
IPADDR=192.168.0.200
NETMASK=255.255.255.0

/etc/sysconfig/network-scripts/ifup-usb:

#!/bin/bash
./etc/init.d/functions
cd /etc/sysconfig/network-scripts
../network-functions
[ -f ../network ] && . ../network
CONFIG=${1}
need_config ${CONFIG}
source_config
NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`
/sbin/ip addr flush dev ${DEVICE} 2>/dev/null
/sbin/ip link set dev ${DEVICE} up
/sbin/ip addr add dev ${DEVICE} ${IPADDR}/${NETBITS}
/sbin/iptables -I POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}
/sbin/sysctl net.ipv4.ip_forward=1
/sbin/iptables -I FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -I FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT

Set /etc/sysconfig/network-scripts/ifdown-usb:

#!/bin/bash
./etc/init.d/functions
cd /etc/sysconfig/network-scripts
../network-functions
[ -f ../network ] && . ../network
CONFIG=${1}
need_config ${CONFIG}
source_config
NETBITS=`ipcalc -p ${IPADDR} ${NETMASK} | awk -F'=' '{print $2;}'`
/sbin/iptables -D FORWARD -d ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/iptables -D FORWARD -s ${IPADDR}/${NETBITS} -j ACCEPT
/sbin/sysctl net.ipv4.ip_forward=0
/sbin/iptables -D POSTROUTING -t nat -j MASQUERADE -s ${IPADDR}/${NETBITS}
/sbin/ip link set dev ${DEVICE} down
/sbin/ip addr flush dev ${DEVICE} 2>/dev/null

If you are using NetworkManager, restart it and enable the usb device from its menu, otherwise it will disable your connection shortly after you enable it.

/sbin/service NetworkManager restart

=== Option C - tested on FC8, FC9 and F10 ===

Plug in the usb cable. NetworkManager should detect the phone automatically but you should ignore it.
Open Network Configuration tool (System -> Administration -> Network) and perform following steps:
# Click '''New''' button on top bar
# Click '''Forward'''
# Select OpenMoko from device list
# Click '''Forward'''
# Select 'Statically set IP address:' and enter address: 192.168.0.200, netmask 255.255.255.0 (or use 255.255.255.240 if you want only route ip range 192.168.0.192-192.168.0.207). Leave gateway empty.
# Click '''Forward'''
# Click '''Apply''' to close add dialog
# Select newly added usb0 device from the device list.
# Click '''Edit''' button on top bar
# You might want to remove a tick from 'Activate device when computer starts' check box.
# Click '''Ok''' to close window dialog.
Save settings and close the window.

Open Firewall Configuration (System -> Administration -> Firewall) and enable masquerading:
# Select '''Masquerading''' from left panel
# Check device(s) which you'd like to share internet connection. Typically eth0 or wlan0.
# Click '''Apply''' and close application

Open terminal and perform (as root user):
# ifdown usb0
# ifup usb0
The first command will remove any existing settings given by the NetworkManager and second command brings the device up with appropriate settings.

Now you should be able to ping e.g. 74.125.39.99 [www.google.com] from OpenMoko. Configure /etc/resolv.conf and you should have full a internet access.

==== Troubleshooting ====
If Network Configuration tool cannot see the the usb0 try to unplug the usb cable for a few seconds and wait until the NetworkManager finds it again.

NetworkManager will assign a new ip address for the OpenMoko if link goes down for a while. You can fix this by issuing '''ifup usb0''' again.

=== Option D - tested on Fedora 11 (Leonidas), Fedora 12 (Unite) and Fedora 13 (Goddard) ===

Plug in the usb cable. NetworkManager should detect the phone automatically. Perform following steps:
# Rightclick NetworkManager Icon
## Click '''Edit Connections ...'''
## Type root password when requested
## Select first entry in List (eg. Auto eth1)
## Click '''Edit'''
## Change '''Connectionname''' to '''neo freerunner'''
## Chose tab '''IPv4 Properties'''
## Choose '''manual''' in Drop-Down-Box '''Method'''
## Click '''Add''' at '''Adresses'''
## Enter this values:
### Address: 192.168.0.200
### Netmask: 255.255.255.0
### Gateway: 0.0.0.0
## Click '''Apply'''
## Click '''Close''' on dialog "network connections"
# Open Shell (as root)
## Enter '''iptables -I FORWARD -j ACCEPT -d 192.168.0.202/32'''
## Enter '''iptables -I FORWARD -j ACCEPT -s 192.168.0.202/32'''
## Enter '''iptables -I POSTROUTING -t nat -j MASQUERADE -s 192.168.0.202/32'''
## Enter '''/etc/init.d/iptables save'''
## Enter '''chkconfig iptables on'''
## Enter '''sed -i -e 's/net.ipv4.ip_forward =.*/net.ipv4.ip_forward = 1/' /etc/sysctl.conf'''
## Enter '''sysctl -p'''
Done!

== Red Hat or Similar (tested with Workstation 5) ==

Edit /etc/sysconfig/network-scripts/net.hotplug:

After this command:

<pre>
case $INTERFACE in
# interfaces that are registered after being "up" (?)
</pre>

add

<pre>
usb0)
ifconfig usb0 192.168.0.200 netmask 255.255.255.0
route add 192.168.0.202 usb0
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
echo 1 > /proc/sys/net/ipv4/ip_forward
exit 0
;;
</pre>

== Gentoo ==

Open /etc/conf.d/net and add:

<pre>
# Neo
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )
routes_usb0=( "192.168.0.202/32 via 192.168.0.200" )
</pre>

Create a new init script:

<pre>
cd /etc/init.d
ln -s net.lo net.usb0
</pre>

=== Manual Configuration ===

Put iptables into use:

<pre>
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
</pre>

Store them:

/etc/init.d/iptables save

If you want the routing by default:

rc-update add iptables default

You must also inform the kernel, to start forwarding.

echo 1 > /proc/sys/net/ipv4/ip_forward

=== Automatic Configuration ===
One way to automate all this is to create /etc/conf.d/net.usb0 as follows. It sets IP forwarding and the iptables rules all in one go. It removes the iptables rules and disables ip forwarding when the FreeRunner is unplugged.
Therefore the net.usb0 service must be hotpluggable (/etc/rc.conf or /etc/conf.d/rc).

<pre>
preup() {
echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}

postdown() {
echo 0 > /proc/sys/net/ipv4/ip_forward
iptables -D INPUT -s 192.168.0.202 -j ACCEPT
iptables -D OUTPUT -s 192.168.0.200 -j ACCEPT
iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
return 0
}
</pre>

== Slackware (tested with 12.1) ==

Following is based on Enrico Zini's solution ('''404 LINK REMOVED''').

Create a new udev rules file <tt>/etc/udev/rules.d/91-openmoko.rules</tt>:

<pre>
SUBSYSTEM=="net", ACTION=="add", ATTRS{idVendor}=="1457", ATTRS{idProduct}=="5122", RUN+="/sbin/om-usb $env{INTERFACE} start"
SUBSYSTEM=="net", ACTION=="remove", ENV{INTERFACE}=="usb[0-9]", RUN+="/sbin/om-usb $env{INTERFACE} stop"
</pre>

Then create the script <tt>/sbin/om-usb</tt>:

<pre>
#!/bin/sh
INTERFACE=$1
ACTION=$2

# udev fails silently when the script fails, e.g. due to commands not
# being found
PATH=/usr/sbin:/sbin:/usr/bin:/bin

case $ACTION in
'start')
# Put all your setup here
;;
'stop')
# Put all your tear down here
;;
*)
echo "Usage: $0 {start|stop}"
exit 1
;;
esac
</pre>

The <tt>INTERFACE</tt> will be <tt>usb0</tt> in most cases.

== Archlinux ==
Following is based on [http://xenos.altervista.org/blogs/index.php?blog=3&title=openmoko-usb-networking-su-archlinux furester's solution].

Install package [http://aur.archlinux.org/packages.php?ID=20220 openmoko-usb-networking] from AUR:

$ yaourt -S openmoko-usb-networking

= SSH Extras =

Reportedly, the ssh daemon (dropbear 0.49) on the FreeRunner appears to have a bug when sending the exit status back to the client. From time to time you receive an exit status of 255.

To avoid ssh adding a new line for every ssh host-key to your known_hosts you can add the following to the phone section in ~/.ssh/config (or see the snippet at : [[USB Networking#Changing_host_keys]] bellow)

UserKnownHostsFile /dev/null

You might want to use keys to bypass the login prompt too.

== SSH Keys ==

== From desktop to FreeRunner ==

To generate ssh keys for use as a login mechanism type:

user@host$ ssh-keygen -t rsa

When prompted for a password either hit enter for no password (''not really a good idea'') or enter a password for this key. ssh into the phone and create ~/.ssh:

root@phone# mkdir ~/.ssh

Then from your desktop copy the '''.pub''' file to the phone.

user@host$ scp ~/.ssh/id_rsa.pub root@phone:~/.ssh/authorized_keys

You should now be able to ssh directly into the phone without a password prompt using a command like 'ssh root@phone' from the account user@host because the public key in the file user@host:~/.ssh/id_rsa.pub is contained in the list of keys which have access in the file root@phone:~/.ssh/authorized_keys (since scp is used, only one key exists, but you can grant access to the phone from more than one account, for example user@host, user@laptop).

To make ssh login as root by default, add the following lines to ~/.ssh/config:

Host phone
User root

Replace ''phone'' with the hostname or ip of your phone. You should now be able to ssh into the phone without having to type ''root@'' every time.

To disable password logins ('''after setting up key access''') edit /etc/init.d/dropbear and change the following line:

DROPBEAR_EXTRA_ARGS=

to

DROPBEAR_EXTRA_ARGS="-s"

You will need to restart dropbear for this to take effect.

=== From FreeRunner to Desktop ===

Generate the key:

dropbearkey -t rsa -f id_rsa

The output will look something like this:

Will output 1024 bit rsa secret key to 'id_rsa'
Generating key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3Nza[...]
Fingerprint: md5 ca:e8:f0:b7:f6:7b:c2:b6:b9:71:e4:45:86:a9:ff:b8

Copy and paste the one line (in this example, starting with 'ssh-rsa' onto the end of the host's authorized_keys file (often in ~/.ssh/).

From the phone, ssh with -i:

ssh -i id_rsa user@host

=== Changing host keys ===

If you reflash, your hosts keys will change. Try this ~/.ssh/config snippet:

Host moko
HostName 192.168.0.202
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
User root

This is suggested because ssh on your desktop may complain if the key matching a certain IP changes (stored in .ssh/known_hosts). Now you have set this, you can issue the following command to connect to your moko (the usual "root@" isn't required as it's set by the user section in the config file) :

ssh moko

== GUI on desktop through SSH ==

To get the GUI on the FreeRunner onto the desktop via USB, you can use ssh as follows (execute on desktop):

xhost +
ssh -l root -X -v 192.168.0.202

Using this, run openmoko-finger-demo for example, and it will open up on the desktop. To get landscape view, just resize the GUI window on the desktop.

If you get an error like this:

<tt>
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to
autolaunch D-Bus session: Autolaunch requested, but X11 support not compiled in.
</tt>

you need to set the DBUS_SESSION_BUS_ADDRESS environment variable to the value on the FreeRunner before launching the process from your desktop. You can find the value of this variable by using a command such as

ps auxwwwwe | grep -m 1 DBUS_SESSION_BUS_ADDRESS

Note that you must run that command on the FreeRunner. Back on your desktop, run the process you want with the ''env'' command like this:

env DBUS_SESSION_BUS_ADDRESS=''dbus_address'' ''process'' #(isn't the "env" redundant here?)

==Display Remote Applications on FreeRunner==

To get desktop apps to show up on your FreeRunner, first log in:

ssh -l root 192.168.0.202

Then run:

DISPLAY=:0 xhost +192.168.0.200

After this you can close the ssh session. Back on the desktop computer, run:

DISPLAY=openmoko:0 xclock

Note that the xhost command will allow remote applications on 192.168.0.200 to access the X server. It will allow anyone on the desktop machine to access the X server of the neo, including snooping anything you type on it. To disallow remote applications again, run this in the neo:

DISPLAY=:0 xhost -192.168.0.200

== sftp ==
After you get the SSH connection working, it is possible to use Konqueror, Nautilus or another sftp - enabled tool to browse the phone filesystem and deploy the test applications. Just enter sftp://root@192.168.0.202 into address bar.

== sshfs ==
You can use sshfs to mount the phones filesystem into the hosts filesystem. Make sure that fuse-sshfs is installed and that you are allowed to use fuse. Now run:

sshfs 192.168.0.202:REMOTE_PATH LOCAL_MOUNT_POINT

REMOTE_PATH can now be accessed through LOCAL_PATH.

E.g. you create copy audio files to SD card create a directory on your desktop computer and mount the card via sshfs
desktop# mkdir /mnt/freerunner
desktop# mkdir /mnt/freerunner/card
desktop# sshfs 192.168.0.202:/media/card /mnt/freerunner/card
No the content of card of your FR can be access via /mnt/freerunner/card.

==Automated setup network and mounting partitions==

See [https://bugs.launchpad.net/ubuntu/+bug/289548 Ubuntu bug report in launchpad].

== other similar tutorials ==
* http://left.subtree.org/category/freerunner/

Mac OS X

2012-02-12T08:19:15Z

Glenn: /* Network Settings */ update

Being primarily a Linux based project, the host platform of choice is Linux. However, it is entirely possible to work with Openmoko and Neo handsets using MacOS X, as you'll soon see.

There are actually two ways of working with Openmoko and MacOS X. One is simply to run a virtual machine in which case you would then follow the instructions for Linux.

On the other hand, if you wish to use MacOS X directly, please continue:

= Flashing to your device =
To operate the Phase 1 devices (Neo 1973), you need to flash a root file system first.

== Graphical Flashing with Openmoko Flasher ==
Here are detailed instructions:
# download Version 1.4 or later of Openmoko Flasher from http://www.handheld-linux.com/wiki.php?page=Openmoko%20Flasher
# select the repository
# press the Refresh button (which loads the list of packages on the server)
# select and load the rootfs (takes some minutes for approx. 40 MByte)
# Now, on your Openmoko, hold the AUX button while pressing the Power button for 5 seconds
# the BOOT menu should appear
# connect the USB cable
# Press the Flash button
# the BOOT menu screen on the OM should show an indication that it has been switched to DFU mode
# (if it fails, unplug the Openmoko shortly and replug and try again (experience shows that it is needed up to three times)
# if it successfully flashed, you should be able to boot the Openmoko and continue configuring AJZaurusUSB

A Universal Binary version of dfu-utils tool (and libusb) is included in the Openmoko Flasher application bundle. You can access it as ''Openmoko Flasher.app/Contents/MacOS/dfu-util''.

To flash from Terminal (which is sometimes required), see the directions below or in [[Flashing_the_Neo_FreeRunner|Flashing the Neo]]

===GTA02===
To flash the kernel:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage
To flash the root filesystem:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D rootfs_filename.jffs2
To flash the boot loader to NAND
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a u-boot -R -D uboot.bin

===GTA01===
To flash the kernel:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a kernel -R -D uImage
To flash the root filesystem:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a rootfs -R -D rootfs_filename.jffs2
To flash the boot loader to NAND
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a u-boot -R -D uboot.bin

When flashing succeeds (in any of the above cases) the following should be shown:
status(0) = No error condition is present
Done!

{{Note|If you get an error: ''Cannot set alternate interface: usb_set_altinterface: could not set alternate interface''. You have to unplug and replug it again. '''Make sure it stays in the Boot menu during that!''' After you have replugged your openmoko you should see ''DFU: Switching to DFU Mode'' on the openmoko screen. Now you can execute the command again and this time it should work.

If somebody has a solution for this problem please contact me. - [[User: Anakron|Anakron]]}}

== Beginners Guide to Flashing Interfaces to the Neo Freerunner ==
In this guide I will be going over the steps to flash an interface onto the Freerunner.

# Download the openmoko flasher from http://www.handheld-linux.com/wiki.php?page=Openmoko%20Flasher . With this you will be able to flash the desired software to your device.
# You must find the repository for the specific interface you are going to flash. The Qtopia repository is located at http://other.lastnetwork.net/OpenMoko/ . The OM2008.9 repository is located at http://downloads.openmoko.org/distro/releases/Om2008.9/ . And the Android repository is located at http://people.openmoko.org/sean_mcneil/ .
# Now open the openmoko flasher and enter the URL for the repository of the desired interface. Next to where you entered the URL, you must click the drop down menu and choose Root File System. At the bottom of the flasher program click refresh. The Root File system file show appear. Once it appears, click Load and it will be loaded into the openmoko flasher.
# Now, with your Freerunner unplugged hold the AUX button while holding the power button (for about 5 seconds) until the BOOT menu appears. Now connect the Freerunner to your computer and click Flash. You may have to disconnect and reconnect the phone a few times until to goes into DFU mode. Once it is in DFU mode, flashing will work.
# Once the flashing is successful, the Freerunner will shut down. Now press the power button while holding the AUX button for 7-10 seconds until the NAND BOOT menu appears. From here, select Boot and you phone should boot to the new interface. (The AUX/Power button combination puts the phone into the NOR BOOT menu, which must be used for flashing. The Power/AUX button combination puts the phone into the NAND BOOT menu, which is usually used for booting after a flash. After the phone is booted once from the NAND menu, it can be booted normally in the future.)

Most of the time, only the rootfs has to be flashed in order for the interface to work, but sometimes the kernel has to be flashed along with the rootfs. In this case, before you flash the rootfs you should select kernel in the drop down menu on the openmoko flasher and follow the same directions.

== Compiling dfu-util ==
Alternatively, you can compile dfu-util manually as described at [[User:SNMoore]] but you need libusb (e.g. through MacPorts).

= Connecting a Mac and an Openmoko device =

== USB Serial ==

It is possible to access the [[U-Boot]] [[bootloader]] serial console from a Mac. You can use the Terminal application on Mac OS X, or <tt>minicom</tt> from [http://finkproject.org/ Fink] or [http://www.macports.org/ MacPorts] (formerly Darwin Ports.)

The USB driver creates cu and tty character devices, for example
$ ls -la /dev/tty.usb*
crw-rw-rw- 1 root wheel 10, 18 Aug 23 14:10 /dev/tty.usbmodem00000001
$ ls -la /dev/cu.usb*
crw-rw-rw- 1 root wheel 10, 19 Aug 23 14:10 /dev/cu.usbmodem00000001

=== USB Serial with screen ===
{{Main|GNU screen}}
The <code>GNU screen</code> program is included with Mac OS X, and can be used from the terminal command line to connect to the serial console. To do this, simply get to a shell prompt in the terminal and invoke <code>screen</code> as follows:
<pre>
% screen /dev/tty.usbmodem0000001
</pre>

You should find yourself at the U-boot serial console prompt. To get out, type <code>control+a</code> followed by <code>control+backslash</code>.

=== USB Serial with minicom ===
:''Possible Mac OS X .pkg download: [http://turin.nss.udel.edu/programming/ Dr. Jeffrey T. Frey: Minicom download and info; at the bottom]''
:''PL2303 USB serial driver (untested): [http://sourceforge.net/projects/osx-pl2303/ PL2303 USB to Serial Driver for Mac OS X]''
The <tt>minicom</tt> program from the [http://www.macports.org/ MacPorts] collection can be used to access the USB serial port <tt>/dev/cu.usbmodem0000001</tt> (numbering may vary.)

First install the program (assuming you already have MacPorts installed):

sudo port install minicom

Then launch it in configuration mode (the -s flag):

sudo minicom -s

Under "Serial Port Setup", set the Device to "/dev/cu.usbmodem0000001" and set Bps to "115200 8N1". Under "Modem and Dialing", enter empty strings for "Init string", "Reset string", and "Hang-up string". Save the setup as default ("dfl") then Exit.

You should now be able to access the U-Boot console. You should exit from Minicom before disconnecting the smartphone, or else you will get an error about unplugging a USB device while it is in use.

=== USB Serial with Terminal ===

The built in Mac Terminal application <tt>Terminal.app</tt> can be used to access the USB serial port <tt>/dev/tty.usbmodem0000001</tt> (numbering may vary.)

An easy way to do this is to configure the terminal with Script Editor, as described in the short article, [http://www.macosxhints.com/article.php?story=20061109133825654 ''Use '(GNU) screen' as a serial terminal emulator''](macosxhints.com). Then,

# Press and hold {{aux}} and then press and hold {{power}} for 5 seconds
# Press {{aux}} to select <tt>Set console to USB</tt> in the U-Boot menu, and {{power}} to execute it
# Start the serial terminal application. You should see a U-Boot command line prompt, such as
In: usbtty
Out: usbtty
Err: usbtty
DEVICE_CONFIGURED: 1
Enabling automatic fast charge
GTA01Bv4 #
When you boot Linux on the smartphone, or if the smartphone powers down, Mac OS X will show a USB Device Unplug Notice, "The USB device has been unplugged while an application was still active. This can result in loss of data." This error is probably harmless.

== USB Networking ==

There are several drivers you can use to talk to the RNDIS/Ethernet Gadget that the Linux kernel presents when connected as a USB client.

=== AJZaurusUSB driver ===

You can use the open source driver from [http://projects.goldelico.com/p/AJZaurusUSB]. It was originally developed for handheld devices like iPAQ, Sharp Zaurus and Motorola A760, but works for Openmoko as well. Download and install according to the manual found inside the package. The code is GPL'd (source available) and runs on both Intel and PPC Macs with 10.4 to 10.6.

After rebooting or loading the kernel extension by hand, you should have a new Ethernet interface in your System Preferences/Network.

Note: This driver does not have the same problem as the Apple driver does, where it constantly adds to the list of interfaces each time you reboot the Openmoko, because the driver provides a constant Ethernet address independently what the Openmoko says. Only flashing a new kernel version might force you to update.

=== Apple CDC Ethernet driver 10.4.10 ===
MacOS X 10.4.10 and later includes a driver for RNDIS/Ethernet Gadget devices. Launch System Preferences -> Network and you should see "new interface detected enXX".

Issue: Each time you reboot the Neo, the interface will get a different Ethernet address. This in turn makes Mac OS X create a new configuration record. After a while you'll end up with a load of unusable enXX devices - if you don't periodically clean them out. Open System Preferences and go to Network -> Show(Network Port Configurations) -> Select an enXX -> Delete.

Note: this is not a problem to blame Mac OS X for, because it tries to simplify network configuration based on the assumption of stable Ethernet addresses.

=== Apple CDC Ethernet driver 10.5.x ===

Issue:10.5 (Leopard) doesn't show a new ethernet interface for a Neo1973 running 2007.11. You'll only get the serial port, which is detected as a modem. The Ethernet device will show up in ifconfig though. If it doesn't, try the other driver below.

It turns out that the AppleUSBCDC driver prefers to use the CDC-ACM interface of USB networking devices instead of CDC-ECM with the exception of a broadcom network card. You can download a patched AppleUSBCDC driver that will recognize the usb id/vendor pair of g_ether and force it to use CDC-ECM. You can obtain the OS X 10.5.X patched driver from: http://bugcommunity.com/downloads/usbcdc-g_ether.zip. [Do not work? Openmoko 2009 16-june-2009 showed up as a modem (MacOS X.5.7) with this driver (ndis/ethernet) [[User:Glenn|Glenn]] 10:54, 16 June 2009 (UTC)] Source code: http://bugcommunity.com/downloads/files/AppleUSBCDCDriver-g_ether.326.4.1.zip

The issue of multiple network interfaces showing up whenever the Neo is rebooted/power-cycled is due to the g_ether driver randomly setting the host and device mac addresses. This problem is remedied by passing the same host and device mac addresses during the modprobe of g_ether. [Not needed with MacOS X.5.7 and Openmoko 2009 16-june-2009. Simply reboot the Mac (again) and Openmoko appear again without changing network settings --[[User:Glenn|Glenn]] 08:30, 17 June 2009 (UTC)]

For example:

modprobe g_ether host_addr=46:0d:9e:67:69:eb dev_addr=46:0d:9e:67:69:ec

=== Network Settings ===
Open System Preferences and go to Network and you should see "new interface detected enXX". In the Show list box select the new interface - Ethernet Adapter enXX.

Use this configuration on the new interface with SHR-CORE images after 110822:
<pre>
IP-V4: manual
IP-Addr: 192.168.7.2 (you can use anything in 192.168.7.* but OM is configured by default to use 192.168.7.2 as the external gateway)
Subnet: 255.255.255.0 (should be the default - see tip below if have issue with these settings)
Router: 192.168.7.1 (not actually needed, OS X can figure this out for itself, unless you have other conflicting configurations)
</pre>

Use this configuration on the new interface with SHR images before 110822:
<pre>
IP-V4: manual
IP-Addr: 192.168.0.200 (you can use anything in 192.168.0.* but OM is configured by default to use 192.168.0.200 as the external gateway)
Subnet: 255.255.255.0 (should be the default - see tip below if have issue with these settings)
Router: 192.168.0.202 (not actually needed, OS X can figure this out for itself, unless you have other conflicting configurations)
</pre>

Tip: If your Internet connection is also in the range 192.168.0.x then instead you might want/need to use:
<pre>
Subnet: 255.255.255.248
</pre>
However if you are running Leopard it may not let you set the subnet claiming that the IP 192.168.0.200 is an invalid address for that subnet. To get round this run the following from the OSX terminal (replacing en11 as appropriate):
<pre>
sudo ifconfig en11 192.168.0.200 netmask 255.255.255.248
</pre>

=== Testing Your Connection ===
You should be able to connect to your Openmoko! Try using Terminal (Applications->Utilities->Terminal) to ping the Neo at 192.168.0.202 and the roundtrip time should be between 1 and 2 ms.
ping 192.168.7.2 # SHR-CORE images after 110822
ping 192.168.0.202 # SHR images before 110822

Then log into your Openmoko using ssh:
ssh root@192.168.7.2 # SHR-CORE images after 110822
ssh root@192.168.0.202 # SHR images before 110822
The default password is blank (depending on the distribution you have on the Openmoko).

You can also [[scp]] files back and forth or share displays with X11. Additional software and configuration could allow telnet, SMB, or many other possibilities using the TCP/IP network over your USB connection.

Try pinging your Mac PC from the Openmoko
ping 192.168.7.1 # SHR-CORE images after 110822
ping 192.168.0.200 # SHR images before 110822

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
If that works then your Mac is routing the neo globally--if not see [[MacOS_X#Enabling_the_Mac_as_an_Internet_Router | Sharing Internet Connection with Mac]].

Lastly, verify that DNS is correctly configured between the Openmoko & Network:
ping www.google.com
If that doesn't work then see [[USB_Networking#Configure_Default_Neo_DNS | Configuring Default Neo DNS]] to try and resolve the issue.

Congratulations!!! The Neo is networked together with the Mac and sharing the Mac's interweb connection.

== Bluetooth Networking ==
{{InProgress}}

This approach is based on:
*[[Bluetooth_Support#Networking]]
*http://www.macosxhints.com/article.php?story=20051220221237711

Unfortunately we can't use the pand (PAN daemon for BNEP) or dund (Dial Up Networking daemon for LAP) since neither service is available for the Mac.

So, we configure a RFCOMM connection and a PPP gateway on the Mac. Finally, we connect the OM as a ppp client to the Mac.

The reversed direction (OM as the Access Point and the Mac as the client) is described shortly in [[Manually_using_Bluetooth#PPP_Networking]]

=== Making the Mac a PPP over Bluetooth Access Point ===

In the Bluetooth System Preferences (10.4.11)
* go to the Sharing pane
* add a new service "BluetoothAccessPoint" of type RS-232
* Enable that it is shown in the network preferences pane
* Apply

In the Network System Preferences
* activate the new network configuration (BluetoothAccessPoint)
* go tot the Modem tab and change the modem to "Null Modem 115200"
* Apply

In a Terminal, enter the following:
$ sudo /usr/sbin/pppd /dev/tty.BluetoothAccessPoint 115200 noauth local passive proxyarp asyncmap 0 silent persist :172.16.140.14

Here you see the 172.16.140.14 address, which makes it possible not to use natd, since it's in the same network as the Mac is. So the firewall knows where to sent it to -- no routing problems etc. Pick any free address in your private range. For instance, if you are using the following ... firewall: 192.168.1.1, Mac: 192.168.1.2, you can enter 192.168.1.3, assuming it's not used elsewhere on your network.

If you want to be sure you did it right, open the system.log file on the Mac (tail -f /var/log/system.log), and you should see something like this:
Jun 25 10:33:57 hostname pppd[679]: pppd 2.4.2 (Apple version 229) started by username, uid 0
Jun 25 10:33:57 hostname pppd[679]: Connect: ppp0 <--> /dev/tty.BluetoothAccessPoint

In Terminal, write
sudo sysctl -w net.inet.ip.forwarding=1
which should give the following feedback:
net.inet.ip.forwarding: 0 -> 1

In Terminal, write
sudo ifconfig ppp0 up.

=== Connecting the Openmoko as a Client to the Mac ===

On the Openmoko do the following

* Power on bluetooth

root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on

* Scan for the Mac
root@fic-gta01:~$ hcitool scan
Scanning ...
00:0E:6D:C0:0l:6A Sho
00:20:E0:5A:FE:C8 MacBook

* start the PPP client

pppd 115000 192.168.1.202:192.168.1.200 local defaultroute pty 'rfcomm connect 0 00:16:CB:2F:A0:46 1'

* Enjoy

== WiFi Networking ==
{{InProgress}}

To Be Done.

== Neo1973 as a Bluetooth GPRS modem ==
{{InProgress}}

To Be Done.

= Enabling the Mac as an Internet Router =

Here is described how to enable your Mac to serve as a Internet Router for your Openmoko device.

Note: you have to open all services you want to use from the Openmoko in the Mac Firewall.

== USB connection ==

In the Sharing System Preferences
* click the Internet tab
* Check all the ethernet (en) interfaces you want to enable Internet access for (i.e. the USB connection)

SSH into your Neo and create /etc/resolv.conf, specify your Internet router IP address as the name server. You can simply copy the /etc/resolv.conf from your Mac.
scp /etc/resolv.conf root@192.168.0.202:/etc/resolv.conf

Example:
nameserver 192.168.1.200 # replace by your real nameserver address

Make sure your Neo routing table has entries so that all internet traffic is sent to your Mac (which will forward it to the outside world)

root@fic-gta01:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 usb0
default 192.168.0.200 0.0.0.0 UG 0 0 0 usb0

Don't forget to enable your USB interface for Internet Sharing!

== Bluetooth connection ==
{{InProgress}}

= Accessing data and services on your device =

== ssh ==

After making the USB connection work, start ssh:

ssh -l root 192.168.0.202

If you don't have installed the key, it will ask for a "yes" on the first connection. The root password is blank unless you change it.

MacBook-hns:~ hns$ ssh -l root 192.168.0.202
root@192.168.0.202's password:
root@fic-gta01:~$ hostname
fic-gta01
root@fic-gta01:~$

NOTE: the ssh daemon (dropbear 0.49) on the Openmoko appears to have a bug when sending the exit status back to the client. From time to time you receive an exit status of 255.

== SMB ==
{{InProgress}}

To Be Done.

== X11 ==
Launch Apple X11.
xhost +192.168.0.202.
On the Neo:
export DISPLAY=192.168.0.200:0.0

== Synchronizing ==
{{InProgress}}

This is not done yet. Possible solutions are SyncML or ZMacSync http://www.dsitri.de/wiki.php?page=ZMacSync

ZMacSync does not yet synchronize but allows more easy access to the Openmoko through Terminal/ssh.

= Developing Openmoko software on a Mac =

== Using virtualization software and MokoMakefile/OpenEmbedded ==

You can use VirtualBox, Parallels or VMWare to install your favourite Linux distribution and then develop just as on Linux.

There are some drawback since AFAIK dfu-util may not work correctly in such environments.

=== Parallels ===

Don't bother with Parallels Desktop for Mac (<=3), the current USB support is terrible and USB storage keys don't even work so there was no way I would try dfu-util. USB keys work under VMWare Fusion for Mac though I have yet to try dfu-util in an VM under VMWare Fusion as there is Openmoko Flasher for Mac. -- [[User: Eric|Eric]]

=== VMware Fusion ===

There is currently no vmplayer for OS X. But the Qtopia image (see [[Developing_with_C++_and_Qt#Use_pre-built_SDK]]) will work with VMware fusion. The script will search for vmplayer and complain. Just answer <tt>YES</tt> when asked if you have the vmplayer installed (I know, it's a lie, but...), and the script will run through. Afterwards open the directory where the files were installed and click on <tt>Qtopia.vmx</tt>.

In VMware Fusion USB Networking is working properly, just plug in the device and connect it to your virtual machine.

Unfortunately dfu-util is currently not working. In fact if you get dfu-util working via unplug/replug method on Mac OS X it works inside VMware too.

=== VirtualBox ===

dfu-util is not working, has some problems with getting exclusive access to the USB device.

== Natively ==
{{InProgress}}

There are some efforts to get through process of compiling OE and Openmoko under mac: [[Openmoko_under_QEMU_on_MacOSX]]

== GNUstep/mySTEP SDK ==

There is a [[QuantumSTEP]]/mySTEP project to port GNUstep to the Openmoko/Neo: [http://www.quantum-step.com/wiki.php?page=Openmoko-Edition More Info]
An SDK for Xcode/Interface Builder is also available: [http://www.versiontracker.com/dyn/moreinfo/macosx/20581 Entry at Version Tracker] [http://www.quantum-step.com/wiki.php?page=SDK More Info]

== Tools for Developers ==

Some tools that run on MacOS X

=== mkfs.jffs2 ===
[http://www.quantum-step.com/download/Openmoko-Edition/mkfs.jffs2.tgz mkfs.jffs2] - make JFFS2 (root) file system (Universal Binary). Package includes sources and Xcode 2.4 project file to rebuild on MacOS X 10.4.11. NOT TESTED DEEPLY.

mkfs.jffs2 --pad=0x700000 -o rootfs.jffs2 -e 0x4000 -n -d/tmp/jffsroot/

=== Crosscompiler Toolchain ===

[http://www.quantum-step.com/wiki.php?page=Compiler gcc 2.95.3] - OABI cross compiler toolchain (C, C++, Obj-C) with Linux headers (PPC and Intel Macs)

If someone has a newer one that works, please provide as an installable OSX Package.

Will the ones from MacPorts work? [http://www.macports.org/ports.php?by=name&substr=gnueabi] I'm still trying to get QEMU to work and haven't had a chance to test it yet.

= Other Resources =

== Search Software Repositories ==

[http://www.versiontracker.com/php/qs.php?action=search&str=openmoko&srchArea=macosx Keyword Openmoko] at VersionTracker

== Discussion Fora ==

[http://www.oesf.org/forums/index.php?showforum=63 Mac Issues Forum] at Open Embedded Software Foundation (was Zaurus User Group)

[[Category:Flashing Openmoko]]
[[Category:Host OSes]]

[http://www.mac-how.net/ Mac How] for discussion questions about Mac

Mac OS X

2012-02-12T08:17:59Z

Glenn: /* Testing Your Connection */ update

Being primarily a Linux based project, the host platform of choice is Linux. However, it is entirely possible to work with Openmoko and Neo handsets using MacOS X, as you'll soon see.

There are actually two ways of working with Openmoko and MacOS X. One is simply to run a virtual machine in which case you would then follow the instructions for Linux.

On the other hand, if you wish to use MacOS X directly, please continue:

= Flashing to your device =
To operate the Phase 1 devices (Neo 1973), you need to flash a root file system first.

== Graphical Flashing with Openmoko Flasher ==
Here are detailed instructions:
# download Version 1.4 or later of Openmoko Flasher from http://www.handheld-linux.com/wiki.php?page=Openmoko%20Flasher
# select the repository
# press the Refresh button (which loads the list of packages on the server)
# select and load the rootfs (takes some minutes for approx. 40 MByte)
# Now, on your Openmoko, hold the AUX button while pressing the Power button for 5 seconds
# the BOOT menu should appear
# connect the USB cable
# Press the Flash button
# the BOOT menu screen on the OM should show an indication that it has been switched to DFU mode
# (if it fails, unplug the Openmoko shortly and replug and try again (experience shows that it is needed up to three times)
# if it successfully flashed, you should be able to boot the Openmoko and continue configuring AJZaurusUSB

A Universal Binary version of dfu-utils tool (and libusb) is included in the Openmoko Flasher application bundle. You can access it as ''Openmoko Flasher.app/Contents/MacOS/dfu-util''.

To flash from Terminal (which is sometimes required), see the directions below or in [[Flashing_the_Neo_FreeRunner|Flashing the Neo]]

===GTA02===
To flash the kernel:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage
To flash the root filesystem:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D rootfs_filename.jffs2
To flash the boot loader to NAND
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a u-boot -R -D uboot.bin

===GTA01===
To flash the kernel:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a kernel -R -D uImage
To flash the root filesystem:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a rootfs -R -D rootfs_filename.jffs2
To flash the boot loader to NAND
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a u-boot -R -D uboot.bin

When flashing succeeds (in any of the above cases) the following should be shown:
status(0) = No error condition is present
Done!

{{Note|If you get an error: ''Cannot set alternate interface: usb_set_altinterface: could not set alternate interface''. You have to unplug and replug it again. '''Make sure it stays in the Boot menu during that!''' After you have replugged your openmoko you should see ''DFU: Switching to DFU Mode'' on the openmoko screen. Now you can execute the command again and this time it should work.

If somebody has a solution for this problem please contact me. - [[User: Anakron|Anakron]]}}

== Beginners Guide to Flashing Interfaces to the Neo Freerunner ==
In this guide I will be going over the steps to flash an interface onto the Freerunner.

# Download the openmoko flasher from http://www.handheld-linux.com/wiki.php?page=Openmoko%20Flasher . With this you will be able to flash the desired software to your device.
# You must find the repository for the specific interface you are going to flash. The Qtopia repository is located at http://other.lastnetwork.net/OpenMoko/ . The OM2008.9 repository is located at http://downloads.openmoko.org/distro/releases/Om2008.9/ . And the Android repository is located at http://people.openmoko.org/sean_mcneil/ .
# Now open the openmoko flasher and enter the URL for the repository of the desired interface. Next to where you entered the URL, you must click the drop down menu and choose Root File System. At the bottom of the flasher program click refresh. The Root File system file show appear. Once it appears, click Load and it will be loaded into the openmoko flasher.
# Now, with your Freerunner unplugged hold the AUX button while holding the power button (for about 5 seconds) until the BOOT menu appears. Now connect the Freerunner to your computer and click Flash. You may have to disconnect and reconnect the phone a few times until to goes into DFU mode. Once it is in DFU mode, flashing will work.
# Once the flashing is successful, the Freerunner will shut down. Now press the power button while holding the AUX button for 7-10 seconds until the NAND BOOT menu appears. From here, select Boot and you phone should boot to the new interface. (The AUX/Power button combination puts the phone into the NOR BOOT menu, which must be used for flashing. The Power/AUX button combination puts the phone into the NAND BOOT menu, which is usually used for booting after a flash. After the phone is booted once from the NAND menu, it can be booted normally in the future.)

Most of the time, only the rootfs has to be flashed in order for the interface to work, but sometimes the kernel has to be flashed along with the rootfs. In this case, before you flash the rootfs you should select kernel in the drop down menu on the openmoko flasher and follow the same directions.

== Compiling dfu-util ==
Alternatively, you can compile dfu-util manually as described at [[User:SNMoore]] but you need libusb (e.g. through MacPorts).

= Connecting a Mac and an Openmoko device =

== USB Serial ==

It is possible to access the [[U-Boot]] [[bootloader]] serial console from a Mac. You can use the Terminal application on Mac OS X, or <tt>minicom</tt> from [http://finkproject.org/ Fink] or [http://www.macports.org/ MacPorts] (formerly Darwin Ports.)

The USB driver creates cu and tty character devices, for example
$ ls -la /dev/tty.usb*
crw-rw-rw- 1 root wheel 10, 18 Aug 23 14:10 /dev/tty.usbmodem00000001
$ ls -la /dev/cu.usb*
crw-rw-rw- 1 root wheel 10, 19 Aug 23 14:10 /dev/cu.usbmodem00000001

=== USB Serial with screen ===
{{Main|GNU screen}}
The <code>GNU screen</code> program is included with Mac OS X, and can be used from the terminal command line to connect to the serial console. To do this, simply get to a shell prompt in the terminal and invoke <code>screen</code> as follows:
<pre>
% screen /dev/tty.usbmodem0000001
</pre>

You should find yourself at the U-boot serial console prompt. To get out, type <code>control+a</code> followed by <code>control+backslash</code>.

=== USB Serial with minicom ===
:''Possible Mac OS X .pkg download: [http://turin.nss.udel.edu/programming/ Dr. Jeffrey T. Frey: Minicom download and info; at the bottom]''
:''PL2303 USB serial driver (untested): [http://sourceforge.net/projects/osx-pl2303/ PL2303 USB to Serial Driver for Mac OS X]''
The <tt>minicom</tt> program from the [http://www.macports.org/ MacPorts] collection can be used to access the USB serial port <tt>/dev/cu.usbmodem0000001</tt> (numbering may vary.)

First install the program (assuming you already have MacPorts installed):

sudo port install minicom

Then launch it in configuration mode (the -s flag):

sudo minicom -s

Under "Serial Port Setup", set the Device to "/dev/cu.usbmodem0000001" and set Bps to "115200 8N1". Under "Modem and Dialing", enter empty strings for "Init string", "Reset string", and "Hang-up string". Save the setup as default ("dfl") then Exit.

You should now be able to access the U-Boot console. You should exit from Minicom before disconnecting the smartphone, or else you will get an error about unplugging a USB device while it is in use.

=== USB Serial with Terminal ===

The built in Mac Terminal application <tt>Terminal.app</tt> can be used to access the USB serial port <tt>/dev/tty.usbmodem0000001</tt> (numbering may vary.)

An easy way to do this is to configure the terminal with Script Editor, as described in the short article, [http://www.macosxhints.com/article.php?story=20061109133825654 ''Use '(GNU) screen' as a serial terminal emulator''](macosxhints.com). Then,

# Press and hold {{aux}} and then press and hold {{power}} for 5 seconds
# Press {{aux}} to select <tt>Set console to USB</tt> in the U-Boot menu, and {{power}} to execute it
# Start the serial terminal application. You should see a U-Boot command line prompt, such as
In: usbtty
Out: usbtty
Err: usbtty
DEVICE_CONFIGURED: 1
Enabling automatic fast charge
GTA01Bv4 #
When you boot Linux on the smartphone, or if the smartphone powers down, Mac OS X will show a USB Device Unplug Notice, "The USB device has been unplugged while an application was still active. This can result in loss of data." This error is probably harmless.

== USB Networking ==

There are several drivers you can use to talk to the RNDIS/Ethernet Gadget that the Linux kernel presents when connected as a USB client.

=== AJZaurusUSB driver ===

You can use the open source driver from [http://projects.goldelico.com/p/AJZaurusUSB]. It was originally developed for handheld devices like iPAQ, Sharp Zaurus and Motorola A760, but works for Openmoko as well. Download and install according to the manual found inside the package. The code is GPL'd (source available) and runs on both Intel and PPC Macs with 10.4 to 10.6.

After rebooting or loading the kernel extension by hand, you should have a new Ethernet interface in your System Preferences/Network.

Note: This driver does not have the same problem as the Apple driver does, where it constantly adds to the list of interfaces each time you reboot the Openmoko, because the driver provides a constant Ethernet address independently what the Openmoko says. Only flashing a new kernel version might force you to update.

=== Apple CDC Ethernet driver 10.4.10 ===
MacOS X 10.4.10 and later includes a driver for RNDIS/Ethernet Gadget devices. Launch System Preferences -> Network and you should see "new interface detected enXX".

Issue: Each time you reboot the Neo, the interface will get a different Ethernet address. This in turn makes Mac OS X create a new configuration record. After a while you'll end up with a load of unusable enXX devices - if you don't periodically clean them out. Open System Preferences and go to Network -> Show(Network Port Configurations) -> Select an enXX -> Delete.

Note: this is not a problem to blame Mac OS X for, because it tries to simplify network configuration based on the assumption of stable Ethernet addresses.

=== Apple CDC Ethernet driver 10.5.x ===

Issue:10.5 (Leopard) doesn't show a new ethernet interface for a Neo1973 running 2007.11. You'll only get the serial port, which is detected as a modem. The Ethernet device will show up in ifconfig though. If it doesn't, try the other driver below.

It turns out that the AppleUSBCDC driver prefers to use the CDC-ACM interface of USB networking devices instead of CDC-ECM with the exception of a broadcom network card. You can download a patched AppleUSBCDC driver that will recognize the usb id/vendor pair of g_ether and force it to use CDC-ECM. You can obtain the OS X 10.5.X patched driver from: http://bugcommunity.com/downloads/usbcdc-g_ether.zip. [Do not work? Openmoko 2009 16-june-2009 showed up as a modem (MacOS X.5.7) with this driver (ndis/ethernet) [[User:Glenn|Glenn]] 10:54, 16 June 2009 (UTC)] Source code: http://bugcommunity.com/downloads/files/AppleUSBCDCDriver-g_ether.326.4.1.zip

The issue of multiple network interfaces showing up whenever the Neo is rebooted/power-cycled is due to the g_ether driver randomly setting the host and device mac addresses. This problem is remedied by passing the same host and device mac addresses during the modprobe of g_ether. [Not needed with MacOS X.5.7 and Openmoko 2009 16-june-2009. Simply reboot the Mac (again) and Openmoko appear again without changing network settings --[[User:Glenn|Glenn]] 08:30, 17 June 2009 (UTC)]

For example:

modprobe g_ether host_addr=46:0d:9e:67:69:eb dev_addr=46:0d:9e:67:69:ec

=== Network Settings ===
Open System Preferences and go to Network and you should see "new interface detected enXX". In the Show list box select the new interface - Ethernet Adapter enXX.

Use this configuration on the new interface after 110822-SHR-CORE-images:
<pre>
IP-V4: manual
IP-Addr: 192.168.7.2 (you can use anything in 192.168.7.* but OM is configured by default to use 192.168.7.2 as the external gateway)
Subnet: 255.255.255.0 (should be the default - see tip below if have issue with these settings)
Router: 192.168.7.1 (not actually needed, OS X can figure this out for itself, unless you have other conflicting configurations)
</pre>

Use this configuration on the new interface before 110822-SHR-images:
<pre>
IP-V4: manual
IP-Addr: 192.168.0.200 (you can use anything in 192.168.0.* but OM is configured by default to use 192.168.0.200 as the external gateway)
Subnet: 255.255.255.0 (should be the default - see tip below if have issue with these settings)
Router: 192.168.0.202 (not actually needed, OS X can figure this out for itself, unless you have other conflicting configurations)
</pre>

Tip: If your Internet connection is also in the range 192.168.0.x then instead you might want/need to use:
<pre>
Subnet: 255.255.255.248
</pre>
However if you are running Leopard it may not let you set the subnet claiming that the IP 192.168.0.200 is an invalid address for that subnet. To get round this run the following from the OSX terminal (replacing en11 as appropriate):
<pre>
sudo ifconfig en11 192.168.0.200 netmask 255.255.255.248
</pre>

=== Testing Your Connection ===
You should be able to connect to your Openmoko! Try using Terminal (Applications->Utilities->Terminal) to ping the Neo at 192.168.0.202 and the roundtrip time should be between 1 and 2 ms.
ping 192.168.7.2 # SHR-CORE images after 110822
ping 192.168.0.202 # SHR images before 110822

Then log into your Openmoko using ssh:
ssh root@192.168.7.2 # SHR-CORE images after 110822
ssh root@192.168.0.202 # SHR images before 110822
The default password is blank (depending on the distribution you have on the Openmoko).

You can also [[scp]] files back and forth or share displays with X11. Additional software and configuration could allow telnet, SMB, or many other possibilities using the TCP/IP network over your USB connection.

Try pinging your Mac PC from the Openmoko
ping 192.168.7.1 # SHR-CORE images after 110822
ping 192.168.0.200 # SHR images before 110822

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
If that works then your Mac is routing the neo globally--if not see [[MacOS_X#Enabling_the_Mac_as_an_Internet_Router | Sharing Internet Connection with Mac]].

Lastly, verify that DNS is correctly configured between the Openmoko & Network:
ping www.google.com
If that doesn't work then see [[USB_Networking#Configure_Default_Neo_DNS | Configuring Default Neo DNS]] to try and resolve the issue.

Congratulations!!! The Neo is networked together with the Mac and sharing the Mac's interweb connection.

== Bluetooth Networking ==
{{InProgress}}

This approach is based on:
*[[Bluetooth_Support#Networking]]
*http://www.macosxhints.com/article.php?story=20051220221237711

Unfortunately we can't use the pand (PAN daemon for BNEP) or dund (Dial Up Networking daemon for LAP) since neither service is available for the Mac.

So, we configure a RFCOMM connection and a PPP gateway on the Mac. Finally, we connect the OM as a ppp client to the Mac.

The reversed direction (OM as the Access Point and the Mac as the client) is described shortly in [[Manually_using_Bluetooth#PPP_Networking]]

=== Making the Mac a PPP over Bluetooth Access Point ===

In the Bluetooth System Preferences (10.4.11)
* go to the Sharing pane
* add a new service "BluetoothAccessPoint" of type RS-232
* Enable that it is shown in the network preferences pane
* Apply

In the Network System Preferences
* activate the new network configuration (BluetoothAccessPoint)
* go tot the Modem tab and change the modem to "Null Modem 115200"
* Apply

In a Terminal, enter the following:
$ sudo /usr/sbin/pppd /dev/tty.BluetoothAccessPoint 115200 noauth local passive proxyarp asyncmap 0 silent persist :172.16.140.14

Here you see the 172.16.140.14 address, which makes it possible not to use natd, since it's in the same network as the Mac is. So the firewall knows where to sent it to -- no routing problems etc. Pick any free address in your private range. For instance, if you are using the following ... firewall: 192.168.1.1, Mac: 192.168.1.2, you can enter 192.168.1.3, assuming it's not used elsewhere on your network.

If you want to be sure you did it right, open the system.log file on the Mac (tail -f /var/log/system.log), and you should see something like this:
Jun 25 10:33:57 hostname pppd[679]: pppd 2.4.2 (Apple version 229) started by username, uid 0
Jun 25 10:33:57 hostname pppd[679]: Connect: ppp0 <--> /dev/tty.BluetoothAccessPoint

In Terminal, write
sudo sysctl -w net.inet.ip.forwarding=1
which should give the following feedback:
net.inet.ip.forwarding: 0 -> 1

In Terminal, write
sudo ifconfig ppp0 up.

=== Connecting the Openmoko as a Client to the Mac ===

On the Openmoko do the following

* Power on bluetooth

root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on

* Scan for the Mac
root@fic-gta01:~$ hcitool scan
Scanning ...
00:0E:6D:C0:0l:6A Sho
00:20:E0:5A:FE:C8 MacBook

* start the PPP client

pppd 115000 192.168.1.202:192.168.1.200 local defaultroute pty 'rfcomm connect 0 00:16:CB:2F:A0:46 1'

* Enjoy

== WiFi Networking ==
{{InProgress}}

To Be Done.

== Neo1973 as a Bluetooth GPRS modem ==
{{InProgress}}

To Be Done.

= Enabling the Mac as an Internet Router =

Here is described how to enable your Mac to serve as a Internet Router for your Openmoko device.

Note: you have to open all services you want to use from the Openmoko in the Mac Firewall.

== USB connection ==

In the Sharing System Preferences
* click the Internet tab
* Check all the ethernet (en) interfaces you want to enable Internet access for (i.e. the USB connection)

SSH into your Neo and create /etc/resolv.conf, specify your Internet router IP address as the name server. You can simply copy the /etc/resolv.conf from your Mac.
scp /etc/resolv.conf root@192.168.0.202:/etc/resolv.conf

Example:
nameserver 192.168.1.200 # replace by your real nameserver address

Make sure your Neo routing table has entries so that all internet traffic is sent to your Mac (which will forward it to the outside world)

root@fic-gta01:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 usb0
default 192.168.0.200 0.0.0.0 UG 0 0 0 usb0

Don't forget to enable your USB interface for Internet Sharing!

== Bluetooth connection ==
{{InProgress}}

= Accessing data and services on your device =

== ssh ==

After making the USB connection work, start ssh:

ssh -l root 192.168.0.202

If you don't have installed the key, it will ask for a "yes" on the first connection. The root password is blank unless you change it.

MacBook-hns:~ hns$ ssh -l root 192.168.0.202
root@192.168.0.202's password:
root@fic-gta01:~$ hostname
fic-gta01
root@fic-gta01:~$

NOTE: the ssh daemon (dropbear 0.49) on the Openmoko appears to have a bug when sending the exit status back to the client. From time to time you receive an exit status of 255.

== SMB ==
{{InProgress}}

To Be Done.

== X11 ==
Launch Apple X11.
xhost +192.168.0.202.
On the Neo:
export DISPLAY=192.168.0.200:0.0

== Synchronizing ==
{{InProgress}}

This is not done yet. Possible solutions are SyncML or ZMacSync http://www.dsitri.de/wiki.php?page=ZMacSync

ZMacSync does not yet synchronize but allows more easy access to the Openmoko through Terminal/ssh.

= Developing Openmoko software on a Mac =

== Using virtualization software and MokoMakefile/OpenEmbedded ==

You can use VirtualBox, Parallels or VMWare to install your favourite Linux distribution and then develop just as on Linux.

There are some drawback since AFAIK dfu-util may not work correctly in such environments.

=== Parallels ===

Don't bother with Parallels Desktop for Mac (<=3), the current USB support is terrible and USB storage keys don't even work so there was no way I would try dfu-util. USB keys work under VMWare Fusion for Mac though I have yet to try dfu-util in an VM under VMWare Fusion as there is Openmoko Flasher for Mac. -- [[User: Eric|Eric]]

=== VMware Fusion ===

There is currently no vmplayer for OS X. But the Qtopia image (see [[Developing_with_C++_and_Qt#Use_pre-built_SDK]]) will work with VMware fusion. The script will search for vmplayer and complain. Just answer <tt>YES</tt> when asked if you have the vmplayer installed (I know, it's a lie, but...), and the script will run through. Afterwards open the directory where the files were installed and click on <tt>Qtopia.vmx</tt>.

In VMware Fusion USB Networking is working properly, just plug in the device and connect it to your virtual machine.

Unfortunately dfu-util is currently not working. In fact if you get dfu-util working via unplug/replug method on Mac OS X it works inside VMware too.

=== VirtualBox ===

dfu-util is not working, has some problems with getting exclusive access to the USB device.

== Natively ==
{{InProgress}}

There are some efforts to get through process of compiling OE and Openmoko under mac: [[Openmoko_under_QEMU_on_MacOSX]]

== GNUstep/mySTEP SDK ==

There is a [[QuantumSTEP]]/mySTEP project to port GNUstep to the Openmoko/Neo: [http://www.quantum-step.com/wiki.php?page=Openmoko-Edition More Info]
An SDK for Xcode/Interface Builder is also available: [http://www.versiontracker.com/dyn/moreinfo/macosx/20581 Entry at Version Tracker] [http://www.quantum-step.com/wiki.php?page=SDK More Info]

== Tools for Developers ==

Some tools that run on MacOS X

=== mkfs.jffs2 ===
[http://www.quantum-step.com/download/Openmoko-Edition/mkfs.jffs2.tgz mkfs.jffs2] - make JFFS2 (root) file system (Universal Binary). Package includes sources and Xcode 2.4 project file to rebuild on MacOS X 10.4.11. NOT TESTED DEEPLY.

mkfs.jffs2 --pad=0x700000 -o rootfs.jffs2 -e 0x4000 -n -d/tmp/jffsroot/

=== Crosscompiler Toolchain ===

[http://www.quantum-step.com/wiki.php?page=Compiler gcc 2.95.3] - OABI cross compiler toolchain (C, C++, Obj-C) with Linux headers (PPC and Intel Macs)

If someone has a newer one that works, please provide as an installable OSX Package.

Will the ones from MacPorts work? [http://www.macports.org/ports.php?by=name&substr=gnueabi] I'm still trying to get QEMU to work and haven't had a chance to test it yet.

= Other Resources =

== Search Software Repositories ==

[http://www.versiontracker.com/php/qs.php?action=search&str=openmoko&srchArea=macosx Keyword Openmoko] at VersionTracker

== Discussion Fora ==

[http://www.oesf.org/forums/index.php?showforum=63 Mac Issues Forum] at Open Embedded Software Foundation (was Zaurus User Group)

[[Category:Flashing Openmoko]]
[[Category:Host OSes]]

[http://www.mac-how.net/ Mac How] for discussion questions about Mac

Mac OS X

2012-02-12T08:17:10Z

Glenn: /* Testing Your Connection */ update

Being primarily a Linux based project, the host platform of choice is Linux. However, it is entirely possible to work with Openmoko and Neo handsets using MacOS X, as you'll soon see.

There are actually two ways of working with Openmoko and MacOS X. One is simply to run a virtual machine in which case you would then follow the instructions for Linux.

On the other hand, if you wish to use MacOS X directly, please continue:

= Flashing to your device =
To operate the Phase 1 devices (Neo 1973), you need to flash a root file system first.

== Graphical Flashing with Openmoko Flasher ==
Here are detailed instructions:
# download Version 1.4 or later of Openmoko Flasher from http://www.handheld-linux.com/wiki.php?page=Openmoko%20Flasher
# select the repository
# press the Refresh button (which loads the list of packages on the server)
# select and load the rootfs (takes some minutes for approx. 40 MByte)
# Now, on your Openmoko, hold the AUX button while pressing the Power button for 5 seconds
# the BOOT menu should appear
# connect the USB cable
# Press the Flash button
# the BOOT menu screen on the OM should show an indication that it has been switched to DFU mode
# (if it fails, unplug the Openmoko shortly and replug and try again (experience shows that it is needed up to three times)
# if it successfully flashed, you should be able to boot the Openmoko and continue configuring AJZaurusUSB

A Universal Binary version of dfu-utils tool (and libusb) is included in the Openmoko Flasher application bundle. You can access it as ''Openmoko Flasher.app/Contents/MacOS/dfu-util''.

To flash from Terminal (which is sometimes required), see the directions below or in [[Flashing_the_Neo_FreeRunner|Flashing the Neo]]

===GTA02===
To flash the kernel:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage
To flash the root filesystem:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D rootfs_filename.jffs2
To flash the boot loader to NAND
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a u-boot -R -D uboot.bin

===GTA01===
To flash the kernel:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a kernel -R -D uImage
To flash the root filesystem:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a rootfs -R -D rootfs_filename.jffs2
To flash the boot loader to NAND
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a u-boot -R -D uboot.bin

When flashing succeeds (in any of the above cases) the following should be shown:
status(0) = No error condition is present
Done!

{{Note|If you get an error: ''Cannot set alternate interface: usb_set_altinterface: could not set alternate interface''. You have to unplug and replug it again. '''Make sure it stays in the Boot menu during that!''' After you have replugged your openmoko you should see ''DFU: Switching to DFU Mode'' on the openmoko screen. Now you can execute the command again and this time it should work.

If somebody has a solution for this problem please contact me. - [[User: Anakron|Anakron]]}}

== Beginners Guide to Flashing Interfaces to the Neo Freerunner ==
In this guide I will be going over the steps to flash an interface onto the Freerunner.

# Download the openmoko flasher from http://www.handheld-linux.com/wiki.php?page=Openmoko%20Flasher . With this you will be able to flash the desired software to your device.
# You must find the repository for the specific interface you are going to flash. The Qtopia repository is located at http://other.lastnetwork.net/OpenMoko/ . The OM2008.9 repository is located at http://downloads.openmoko.org/distro/releases/Om2008.9/ . And the Android repository is located at http://people.openmoko.org/sean_mcneil/ .
# Now open the openmoko flasher and enter the URL for the repository of the desired interface. Next to where you entered the URL, you must click the drop down menu and choose Root File System. At the bottom of the flasher program click refresh. The Root File system file show appear. Once it appears, click Load and it will be loaded into the openmoko flasher.
# Now, with your Freerunner unplugged hold the AUX button while holding the power button (for about 5 seconds) until the BOOT menu appears. Now connect the Freerunner to your computer and click Flash. You may have to disconnect and reconnect the phone a few times until to goes into DFU mode. Once it is in DFU mode, flashing will work.
# Once the flashing is successful, the Freerunner will shut down. Now press the power button while holding the AUX button for 7-10 seconds until the NAND BOOT menu appears. From here, select Boot and you phone should boot to the new interface. (The AUX/Power button combination puts the phone into the NOR BOOT menu, which must be used for flashing. The Power/AUX button combination puts the phone into the NAND BOOT menu, which is usually used for booting after a flash. After the phone is booted once from the NAND menu, it can be booted normally in the future.)

Most of the time, only the rootfs has to be flashed in order for the interface to work, but sometimes the kernel has to be flashed along with the rootfs. In this case, before you flash the rootfs you should select kernel in the drop down menu on the openmoko flasher and follow the same directions.

== Compiling dfu-util ==
Alternatively, you can compile dfu-util manually as described at [[User:SNMoore]] but you need libusb (e.g. through MacPorts).

= Connecting a Mac and an Openmoko device =

== USB Serial ==

It is possible to access the [[U-Boot]] [[bootloader]] serial console from a Mac. You can use the Terminal application on Mac OS X, or <tt>minicom</tt> from [http://finkproject.org/ Fink] or [http://www.macports.org/ MacPorts] (formerly Darwin Ports.)

The USB driver creates cu and tty character devices, for example
$ ls -la /dev/tty.usb*
crw-rw-rw- 1 root wheel 10, 18 Aug 23 14:10 /dev/tty.usbmodem00000001
$ ls -la /dev/cu.usb*
crw-rw-rw- 1 root wheel 10, 19 Aug 23 14:10 /dev/cu.usbmodem00000001

=== USB Serial with screen ===
{{Main|GNU screen}}
The <code>GNU screen</code> program is included with Mac OS X, and can be used from the terminal command line to connect to the serial console. To do this, simply get to a shell prompt in the terminal and invoke <code>screen</code> as follows:
<pre>
% screen /dev/tty.usbmodem0000001
</pre>

You should find yourself at the U-boot serial console prompt. To get out, type <code>control+a</code> followed by <code>control+backslash</code>.

=== USB Serial with minicom ===
:''Possible Mac OS X .pkg download: [http://turin.nss.udel.edu/programming/ Dr. Jeffrey T. Frey: Minicom download and info; at the bottom]''
:''PL2303 USB serial driver (untested): [http://sourceforge.net/projects/osx-pl2303/ PL2303 USB to Serial Driver for Mac OS X]''
The <tt>minicom</tt> program from the [http://www.macports.org/ MacPorts] collection can be used to access the USB serial port <tt>/dev/cu.usbmodem0000001</tt> (numbering may vary.)

First install the program (assuming you already have MacPorts installed):

sudo port install minicom

Then launch it in configuration mode (the -s flag):

sudo minicom -s

Under "Serial Port Setup", set the Device to "/dev/cu.usbmodem0000001" and set Bps to "115200 8N1". Under "Modem and Dialing", enter empty strings for "Init string", "Reset string", and "Hang-up string". Save the setup as default ("dfl") then Exit.

You should now be able to access the U-Boot console. You should exit from Minicom before disconnecting the smartphone, or else you will get an error about unplugging a USB device while it is in use.

=== USB Serial with Terminal ===

The built in Mac Terminal application <tt>Terminal.app</tt> can be used to access the USB serial port <tt>/dev/tty.usbmodem0000001</tt> (numbering may vary.)

An easy way to do this is to configure the terminal with Script Editor, as described in the short article, [http://www.macosxhints.com/article.php?story=20061109133825654 ''Use '(GNU) screen' as a serial terminal emulator''](macosxhints.com). Then,

# Press and hold {{aux}} and then press and hold {{power}} for 5 seconds
# Press {{aux}} to select <tt>Set console to USB</tt> in the U-Boot menu, and {{power}} to execute it
# Start the serial terminal application. You should see a U-Boot command line prompt, such as
In: usbtty
Out: usbtty
Err: usbtty
DEVICE_CONFIGURED: 1
Enabling automatic fast charge
GTA01Bv4 #
When you boot Linux on the smartphone, or if the smartphone powers down, Mac OS X will show a USB Device Unplug Notice, "The USB device has been unplugged while an application was still active. This can result in loss of data." This error is probably harmless.

== USB Networking ==

There are several drivers you can use to talk to the RNDIS/Ethernet Gadget that the Linux kernel presents when connected as a USB client.

=== AJZaurusUSB driver ===

You can use the open source driver from [http://projects.goldelico.com/p/AJZaurusUSB]. It was originally developed for handheld devices like iPAQ, Sharp Zaurus and Motorola A760, but works for Openmoko as well. Download and install according to the manual found inside the package. The code is GPL'd (source available) and runs on both Intel and PPC Macs with 10.4 to 10.6.

After rebooting or loading the kernel extension by hand, you should have a new Ethernet interface in your System Preferences/Network.

Note: This driver does not have the same problem as the Apple driver does, where it constantly adds to the list of interfaces each time you reboot the Openmoko, because the driver provides a constant Ethernet address independently what the Openmoko says. Only flashing a new kernel version might force you to update.

=== Apple CDC Ethernet driver 10.4.10 ===
MacOS X 10.4.10 and later includes a driver for RNDIS/Ethernet Gadget devices. Launch System Preferences -> Network and you should see "new interface detected enXX".

Issue: Each time you reboot the Neo, the interface will get a different Ethernet address. This in turn makes Mac OS X create a new configuration record. After a while you'll end up with a load of unusable enXX devices - if you don't periodically clean them out. Open System Preferences and go to Network -> Show(Network Port Configurations) -> Select an enXX -> Delete.

Note: this is not a problem to blame Mac OS X for, because it tries to simplify network configuration based on the assumption of stable Ethernet addresses.

=== Apple CDC Ethernet driver 10.5.x ===

Issue:10.5 (Leopard) doesn't show a new ethernet interface for a Neo1973 running 2007.11. You'll only get the serial port, which is detected as a modem. The Ethernet device will show up in ifconfig though. If it doesn't, try the other driver below.

It turns out that the AppleUSBCDC driver prefers to use the CDC-ACM interface of USB networking devices instead of CDC-ECM with the exception of a broadcom network card. You can download a patched AppleUSBCDC driver that will recognize the usb id/vendor pair of g_ether and force it to use CDC-ECM. You can obtain the OS X 10.5.X patched driver from: http://bugcommunity.com/downloads/usbcdc-g_ether.zip. [Do not work? Openmoko 2009 16-june-2009 showed up as a modem (MacOS X.5.7) with this driver (ndis/ethernet) [[User:Glenn|Glenn]] 10:54, 16 June 2009 (UTC)] Source code: http://bugcommunity.com/downloads/files/AppleUSBCDCDriver-g_ether.326.4.1.zip

The issue of multiple network interfaces showing up whenever the Neo is rebooted/power-cycled is due to the g_ether driver randomly setting the host and device mac addresses. This problem is remedied by passing the same host and device mac addresses during the modprobe of g_ether. [Not needed with MacOS X.5.7 and Openmoko 2009 16-june-2009. Simply reboot the Mac (again) and Openmoko appear again without changing network settings --[[User:Glenn|Glenn]] 08:30, 17 June 2009 (UTC)]

For example:

modprobe g_ether host_addr=46:0d:9e:67:69:eb dev_addr=46:0d:9e:67:69:ec

=== Network Settings ===
Open System Preferences and go to Network and you should see "new interface detected enXX". In the Show list box select the new interface - Ethernet Adapter enXX.

Use this configuration on the new interface after 110822-SHR-CORE-images:
<pre>
IP-V4: manual
IP-Addr: 192.168.7.2 (you can use anything in 192.168.7.* but OM is configured by default to use 192.168.7.2 as the external gateway)
Subnet: 255.255.255.0 (should be the default - see tip below if have issue with these settings)
Router: 192.168.7.1 (not actually needed, OS X can figure this out for itself, unless you have other conflicting configurations)
</pre>

Use this configuration on the new interface before 110822-SHR-images:
<pre>
IP-V4: manual
IP-Addr: 192.168.0.200 (you can use anything in 192.168.0.* but OM is configured by default to use 192.168.0.200 as the external gateway)
Subnet: 255.255.255.0 (should be the default - see tip below if have issue with these settings)
Router: 192.168.0.202 (not actually needed, OS X can figure this out for itself, unless you have other conflicting configurations)
</pre>

Tip: If your Internet connection is also in the range 192.168.0.x then instead you might want/need to use:
<pre>
Subnet: 255.255.255.248
</pre>
However if you are running Leopard it may not let you set the subnet claiming that the IP 192.168.0.200 is an invalid address for that subnet. To get round this run the following from the OSX terminal (replacing en11 as appropriate):
<pre>
sudo ifconfig en11 192.168.0.200 netmask 255.255.255.248
</pre>

=== Testing Your Connection ===
You should be able to connect to your Openmoko! Try using Terminal (Applications->Utilities->Terminal) to ping the Neo at 192.168.0.202 and the roundtrip time should be between 1 and 2 ms.
ping 192.168.0.202

Then log into your Openmoko using ssh:
ssh root@192.168.7.2 # SHR-CORE images after 110822
ssh root@192.168.0.202 # SHR images before 110822
The default password is blank (depending on the distribution you have on the Openmoko).

You can also [[scp]] files back and forth or share displays with X11. Additional software and configuration could allow telnet, SMB, or many other possibilities using the TCP/IP network over your USB connection.

Try pinging your Mac PC from the Openmoko
ping 192.168.7.2 # SHR-CORE images after 110822
ping 192.168.0.200 # SHR images before 110822

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
If that works then your Mac is routing the neo globally--if not see [[MacOS_X#Enabling_the_Mac_as_an_Internet_Router | Sharing Internet Connection with Mac]].

Lastly, verify that DNS is correctly configured between the Openmoko & Network:
ping www.google.com
If that doesn't work then see [[USB_Networking#Configure_Default_Neo_DNS | Configuring Default Neo DNS]] to try and resolve the issue.

Congratulations!!! The Neo is networked together with the Mac and sharing the Mac's interweb connection.

== Bluetooth Networking ==
{{InProgress}}

This approach is based on:
*[[Bluetooth_Support#Networking]]
*http://www.macosxhints.com/article.php?story=20051220221237711

Unfortunately we can't use the pand (PAN daemon for BNEP) or dund (Dial Up Networking daemon for LAP) since neither service is available for the Mac.

So, we configure a RFCOMM connection and a PPP gateway on the Mac. Finally, we connect the OM as a ppp client to the Mac.

The reversed direction (OM as the Access Point and the Mac as the client) is described shortly in [[Manually_using_Bluetooth#PPP_Networking]]

=== Making the Mac a PPP over Bluetooth Access Point ===

In the Bluetooth System Preferences (10.4.11)
* go to the Sharing pane
* add a new service "BluetoothAccessPoint" of type RS-232
* Enable that it is shown in the network preferences pane
* Apply

In the Network System Preferences
* activate the new network configuration (BluetoothAccessPoint)
* go tot the Modem tab and change the modem to "Null Modem 115200"
* Apply

In a Terminal, enter the following:
$ sudo /usr/sbin/pppd /dev/tty.BluetoothAccessPoint 115200 noauth local passive proxyarp asyncmap 0 silent persist :172.16.140.14

Here you see the 172.16.140.14 address, which makes it possible not to use natd, since it's in the same network as the Mac is. So the firewall knows where to sent it to -- no routing problems etc. Pick any free address in your private range. For instance, if you are using the following ... firewall: 192.168.1.1, Mac: 192.168.1.2, you can enter 192.168.1.3, assuming it's not used elsewhere on your network.

If you want to be sure you did it right, open the system.log file on the Mac (tail -f /var/log/system.log), and you should see something like this:
Jun 25 10:33:57 hostname pppd[679]: pppd 2.4.2 (Apple version 229) started by username, uid 0
Jun 25 10:33:57 hostname pppd[679]: Connect: ppp0 <--> /dev/tty.BluetoothAccessPoint

In Terminal, write
sudo sysctl -w net.inet.ip.forwarding=1
which should give the following feedback:
net.inet.ip.forwarding: 0 -> 1

In Terminal, write
sudo ifconfig ppp0 up.

=== Connecting the Openmoko as a Client to the Mac ===

On the Openmoko do the following

* Power on bluetooth

root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on

* Scan for the Mac
root@fic-gta01:~$ hcitool scan
Scanning ...
00:0E:6D:C0:0l:6A Sho
00:20:E0:5A:FE:C8 MacBook

* start the PPP client

pppd 115000 192.168.1.202:192.168.1.200 local defaultroute pty 'rfcomm connect 0 00:16:CB:2F:A0:46 1'

* Enjoy

== WiFi Networking ==
{{InProgress}}

To Be Done.

== Neo1973 as a Bluetooth GPRS modem ==
{{InProgress}}

To Be Done.

= Enabling the Mac as an Internet Router =

Here is described how to enable your Mac to serve as a Internet Router for your Openmoko device.

Note: you have to open all services you want to use from the Openmoko in the Mac Firewall.

== USB connection ==

In the Sharing System Preferences
* click the Internet tab
* Check all the ethernet (en) interfaces you want to enable Internet access for (i.e. the USB connection)

SSH into your Neo and create /etc/resolv.conf, specify your Internet router IP address as the name server. You can simply copy the /etc/resolv.conf from your Mac.
scp /etc/resolv.conf root@192.168.0.202:/etc/resolv.conf

Example:
nameserver 192.168.1.200 # replace by your real nameserver address

Make sure your Neo routing table has entries so that all internet traffic is sent to your Mac (which will forward it to the outside world)

root@fic-gta01:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 usb0
default 192.168.0.200 0.0.0.0 UG 0 0 0 usb0

Don't forget to enable your USB interface for Internet Sharing!

== Bluetooth connection ==
{{InProgress}}

= Accessing data and services on your device =

== ssh ==

After making the USB connection work, start ssh:

ssh -l root 192.168.0.202

If you don't have installed the key, it will ask for a "yes" on the first connection. The root password is blank unless you change it.

MacBook-hns:~ hns$ ssh -l root 192.168.0.202
root@192.168.0.202's password:
root@fic-gta01:~$ hostname
fic-gta01
root@fic-gta01:~$

NOTE: the ssh daemon (dropbear 0.49) on the Openmoko appears to have a bug when sending the exit status back to the client. From time to time you receive an exit status of 255.

== SMB ==
{{InProgress}}

To Be Done.

== X11 ==
Launch Apple X11.
xhost +192.168.0.202.
On the Neo:
export DISPLAY=192.168.0.200:0.0

== Synchronizing ==
{{InProgress}}

This is not done yet. Possible solutions are SyncML or ZMacSync http://www.dsitri.de/wiki.php?page=ZMacSync

ZMacSync does not yet synchronize but allows more easy access to the Openmoko through Terminal/ssh.

= Developing Openmoko software on a Mac =

== Using virtualization software and MokoMakefile/OpenEmbedded ==

You can use VirtualBox, Parallels or VMWare to install your favourite Linux distribution and then develop just as on Linux.

There are some drawback since AFAIK dfu-util may not work correctly in such environments.

=== Parallels ===

Don't bother with Parallels Desktop for Mac (<=3), the current USB support is terrible and USB storage keys don't even work so there was no way I would try dfu-util. USB keys work under VMWare Fusion for Mac though I have yet to try dfu-util in an VM under VMWare Fusion as there is Openmoko Flasher for Mac. -- [[User: Eric|Eric]]

=== VMware Fusion ===

There is currently no vmplayer for OS X. But the Qtopia image (see [[Developing_with_C++_and_Qt#Use_pre-built_SDK]]) will work with VMware fusion. The script will search for vmplayer and complain. Just answer <tt>YES</tt> when asked if you have the vmplayer installed (I know, it's a lie, but...), and the script will run through. Afterwards open the directory where the files were installed and click on <tt>Qtopia.vmx</tt>.

In VMware Fusion USB Networking is working properly, just plug in the device and connect it to your virtual machine.

Unfortunately dfu-util is currently not working. In fact if you get dfu-util working via unplug/replug method on Mac OS X it works inside VMware too.

=== VirtualBox ===

dfu-util is not working, has some problems with getting exclusive access to the USB device.

== Natively ==
{{InProgress}}

There are some efforts to get through process of compiling OE and Openmoko under mac: [[Openmoko_under_QEMU_on_MacOSX]]

== GNUstep/mySTEP SDK ==

There is a [[QuantumSTEP]]/mySTEP project to port GNUstep to the Openmoko/Neo: [http://www.quantum-step.com/wiki.php?page=Openmoko-Edition More Info]
An SDK for Xcode/Interface Builder is also available: [http://www.versiontracker.com/dyn/moreinfo/macosx/20581 Entry at Version Tracker] [http://www.quantum-step.com/wiki.php?page=SDK More Info]

== Tools for Developers ==

Some tools that run on MacOS X

=== mkfs.jffs2 ===
[http://www.quantum-step.com/download/Openmoko-Edition/mkfs.jffs2.tgz mkfs.jffs2] - make JFFS2 (root) file system (Universal Binary). Package includes sources and Xcode 2.4 project file to rebuild on MacOS X 10.4.11. NOT TESTED DEEPLY.

mkfs.jffs2 --pad=0x700000 -o rootfs.jffs2 -e 0x4000 -n -d/tmp/jffsroot/

=== Crosscompiler Toolchain ===

[http://www.quantum-step.com/wiki.php?page=Compiler gcc 2.95.3] - OABI cross compiler toolchain (C, C++, Obj-C) with Linux headers (PPC and Intel Macs)

If someone has a newer one that works, please provide as an installable OSX Package.

Will the ones from MacPorts work? [http://www.macports.org/ports.php?by=name&substr=gnueabi] I'm still trying to get QEMU to work and haven't had a chance to test it yet.

= Other Resources =

== Search Software Repositories ==

[http://www.versiontracker.com/php/qs.php?action=search&str=openmoko&srchArea=macosx Keyword Openmoko] at VersionTracker

== Discussion Fora ==

[http://www.oesf.org/forums/index.php?showforum=63 Mac Issues Forum] at Open Embedded Software Foundation (was Zaurus User Group)

[[Category:Flashing Openmoko]]
[[Category:Host OSes]]

[http://www.mac-how.net/ Mac How] for discussion questions about Mac

Mac OS X

2012-02-12T08:14:05Z

Glenn: /* Network Settings */ +about shr-core new ip-settings

Being primarily a Linux based project, the host platform of choice is Linux. However, it is entirely possible to work with Openmoko and Neo handsets using MacOS X, as you'll soon see.

There are actually two ways of working with Openmoko and MacOS X. One is simply to run a virtual machine in which case you would then follow the instructions for Linux.

On the other hand, if you wish to use MacOS X directly, please continue:

= Flashing to your device =
To operate the Phase 1 devices (Neo 1973), you need to flash a root file system first.

== Graphical Flashing with Openmoko Flasher ==
Here are detailed instructions:
# download Version 1.4 or later of Openmoko Flasher from http://www.handheld-linux.com/wiki.php?page=Openmoko%20Flasher
# select the repository
# press the Refresh button (which loads the list of packages on the server)
# select and load the rootfs (takes some minutes for approx. 40 MByte)
# Now, on your Openmoko, hold the AUX button while pressing the Power button for 5 seconds
# the BOOT menu should appear
# connect the USB cable
# Press the Flash button
# the BOOT menu screen on the OM should show an indication that it has been switched to DFU mode
# (if it fails, unplug the Openmoko shortly and replug and try again (experience shows that it is needed up to three times)
# if it successfully flashed, you should be able to boot the Openmoko and continue configuring AJZaurusUSB

A Universal Binary version of dfu-utils tool (and libusb) is included in the Openmoko Flasher application bundle. You can access it as ''Openmoko Flasher.app/Contents/MacOS/dfu-util''.

To flash from Terminal (which is sometimes required), see the directions below or in [[Flashing_the_Neo_FreeRunner|Flashing the Neo]]

===GTA02===
To flash the kernel:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage
To flash the root filesystem:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D rootfs_filename.jffs2
To flash the boot loader to NAND
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a u-boot -R -D uboot.bin

===GTA01===
To flash the kernel:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a kernel -R -D uImage
To flash the root filesystem:
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a rootfs -R -D rootfs_filename.jffs2
To flash the boot loader to NAND
Openmoko\ Flasher.app/Contents/MacOS/dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a u-boot -R -D uboot.bin

When flashing succeeds (in any of the above cases) the following should be shown:
status(0) = No error condition is present
Done!

{{Note|If you get an error: ''Cannot set alternate interface: usb_set_altinterface: could not set alternate interface''. You have to unplug and replug it again. '''Make sure it stays in the Boot menu during that!''' After you have replugged your openmoko you should see ''DFU: Switching to DFU Mode'' on the openmoko screen. Now you can execute the command again and this time it should work.

If somebody has a solution for this problem please contact me. - [[User: Anakron|Anakron]]}}

== Beginners Guide to Flashing Interfaces to the Neo Freerunner ==
In this guide I will be going over the steps to flash an interface onto the Freerunner.

# Download the openmoko flasher from http://www.handheld-linux.com/wiki.php?page=Openmoko%20Flasher . With this you will be able to flash the desired software to your device.
# You must find the repository for the specific interface you are going to flash. The Qtopia repository is located at http://other.lastnetwork.net/OpenMoko/ . The OM2008.9 repository is located at http://downloads.openmoko.org/distro/releases/Om2008.9/ . And the Android repository is located at http://people.openmoko.org/sean_mcneil/ .
# Now open the openmoko flasher and enter the URL for the repository of the desired interface. Next to where you entered the URL, you must click the drop down menu and choose Root File System. At the bottom of the flasher program click refresh. The Root File system file show appear. Once it appears, click Load and it will be loaded into the openmoko flasher.
# Now, with your Freerunner unplugged hold the AUX button while holding the power button (for about 5 seconds) until the BOOT menu appears. Now connect the Freerunner to your computer and click Flash. You may have to disconnect and reconnect the phone a few times until to goes into DFU mode. Once it is in DFU mode, flashing will work.
# Once the flashing is successful, the Freerunner will shut down. Now press the power button while holding the AUX button for 7-10 seconds until the NAND BOOT menu appears. From here, select Boot and you phone should boot to the new interface. (The AUX/Power button combination puts the phone into the NOR BOOT menu, which must be used for flashing. The Power/AUX button combination puts the phone into the NAND BOOT menu, which is usually used for booting after a flash. After the phone is booted once from the NAND menu, it can be booted normally in the future.)

Most of the time, only the rootfs has to be flashed in order for the interface to work, but sometimes the kernel has to be flashed along with the rootfs. In this case, before you flash the rootfs you should select kernel in the drop down menu on the openmoko flasher and follow the same directions.

== Compiling dfu-util ==
Alternatively, you can compile dfu-util manually as described at [[User:SNMoore]] but you need libusb (e.g. through MacPorts).

= Connecting a Mac and an Openmoko device =

== USB Serial ==

It is possible to access the [[U-Boot]] [[bootloader]] serial console from a Mac. You can use the Terminal application on Mac OS X, or <tt>minicom</tt> from [http://finkproject.org/ Fink] or [http://www.macports.org/ MacPorts] (formerly Darwin Ports.)

The USB driver creates cu and tty character devices, for example
$ ls -la /dev/tty.usb*
crw-rw-rw- 1 root wheel 10, 18 Aug 23 14:10 /dev/tty.usbmodem00000001
$ ls -la /dev/cu.usb*
crw-rw-rw- 1 root wheel 10, 19 Aug 23 14:10 /dev/cu.usbmodem00000001

=== USB Serial with screen ===
{{Main|GNU screen}}
The <code>GNU screen</code> program is included with Mac OS X, and can be used from the terminal command line to connect to the serial console. To do this, simply get to a shell prompt in the terminal and invoke <code>screen</code> as follows:
<pre>
% screen /dev/tty.usbmodem0000001
</pre>

You should find yourself at the U-boot serial console prompt. To get out, type <code>control+a</code> followed by <code>control+backslash</code>.

=== USB Serial with minicom ===
:''Possible Mac OS X .pkg download: [http://turin.nss.udel.edu/programming/ Dr. Jeffrey T. Frey: Minicom download and info; at the bottom]''
:''PL2303 USB serial driver (untested): [http://sourceforge.net/projects/osx-pl2303/ PL2303 USB to Serial Driver for Mac OS X]''
The <tt>minicom</tt> program from the [http://www.macports.org/ MacPorts] collection can be used to access the USB serial port <tt>/dev/cu.usbmodem0000001</tt> (numbering may vary.)

First install the program (assuming you already have MacPorts installed):

sudo port install minicom

Then launch it in configuration mode (the -s flag):

sudo minicom -s

Under "Serial Port Setup", set the Device to "/dev/cu.usbmodem0000001" and set Bps to "115200 8N1". Under "Modem and Dialing", enter empty strings for "Init string", "Reset string", and "Hang-up string". Save the setup as default ("dfl") then Exit.

You should now be able to access the U-Boot console. You should exit from Minicom before disconnecting the smartphone, or else you will get an error about unplugging a USB device while it is in use.

=== USB Serial with Terminal ===

The built in Mac Terminal application <tt>Terminal.app</tt> can be used to access the USB serial port <tt>/dev/tty.usbmodem0000001</tt> (numbering may vary.)

An easy way to do this is to configure the terminal with Script Editor, as described in the short article, [http://www.macosxhints.com/article.php?story=20061109133825654 ''Use '(GNU) screen' as a serial terminal emulator''](macosxhints.com). Then,

# Press and hold {{aux}} and then press and hold {{power}} for 5 seconds
# Press {{aux}} to select <tt>Set console to USB</tt> in the U-Boot menu, and {{power}} to execute it
# Start the serial terminal application. You should see a U-Boot command line prompt, such as
In: usbtty
Out: usbtty
Err: usbtty
DEVICE_CONFIGURED: 1
Enabling automatic fast charge
GTA01Bv4 #
When you boot Linux on the smartphone, or if the smartphone powers down, Mac OS X will show a USB Device Unplug Notice, "The USB device has been unplugged while an application was still active. This can result in loss of data." This error is probably harmless.

== USB Networking ==

There are several drivers you can use to talk to the RNDIS/Ethernet Gadget that the Linux kernel presents when connected as a USB client.

=== AJZaurusUSB driver ===

You can use the open source driver from [http://projects.goldelico.com/p/AJZaurusUSB]. It was originally developed for handheld devices like iPAQ, Sharp Zaurus and Motorola A760, but works for Openmoko as well. Download and install according to the manual found inside the package. The code is GPL'd (source available) and runs on both Intel and PPC Macs with 10.4 to 10.6.

After rebooting or loading the kernel extension by hand, you should have a new Ethernet interface in your System Preferences/Network.

Note: This driver does not have the same problem as the Apple driver does, where it constantly adds to the list of interfaces each time you reboot the Openmoko, because the driver provides a constant Ethernet address independently what the Openmoko says. Only flashing a new kernel version might force you to update.

=== Apple CDC Ethernet driver 10.4.10 ===
MacOS X 10.4.10 and later includes a driver for RNDIS/Ethernet Gadget devices. Launch System Preferences -> Network and you should see "new interface detected enXX".

Issue: Each time you reboot the Neo, the interface will get a different Ethernet address. This in turn makes Mac OS X create a new configuration record. After a while you'll end up with a load of unusable enXX devices - if you don't periodically clean them out. Open System Preferences and go to Network -> Show(Network Port Configurations) -> Select an enXX -> Delete.

Note: this is not a problem to blame Mac OS X for, because it tries to simplify network configuration based on the assumption of stable Ethernet addresses.

=== Apple CDC Ethernet driver 10.5.x ===

Issue:10.5 (Leopard) doesn't show a new ethernet interface for a Neo1973 running 2007.11. You'll only get the serial port, which is detected as a modem. The Ethernet device will show up in ifconfig though. If it doesn't, try the other driver below.

It turns out that the AppleUSBCDC driver prefers to use the CDC-ACM interface of USB networking devices instead of CDC-ECM with the exception of a broadcom network card. You can download a patched AppleUSBCDC driver that will recognize the usb id/vendor pair of g_ether and force it to use CDC-ECM. You can obtain the OS X 10.5.X patched driver from: http://bugcommunity.com/downloads/usbcdc-g_ether.zip. [Do not work? Openmoko 2009 16-june-2009 showed up as a modem (MacOS X.5.7) with this driver (ndis/ethernet) [[User:Glenn|Glenn]] 10:54, 16 June 2009 (UTC)] Source code: http://bugcommunity.com/downloads/files/AppleUSBCDCDriver-g_ether.326.4.1.zip

The issue of multiple network interfaces showing up whenever the Neo is rebooted/power-cycled is due to the g_ether driver randomly setting the host and device mac addresses. This problem is remedied by passing the same host and device mac addresses during the modprobe of g_ether. [Not needed with MacOS X.5.7 and Openmoko 2009 16-june-2009. Simply reboot the Mac (again) and Openmoko appear again without changing network settings --[[User:Glenn|Glenn]] 08:30, 17 June 2009 (UTC)]

For example:

modprobe g_ether host_addr=46:0d:9e:67:69:eb dev_addr=46:0d:9e:67:69:ec

=== Network Settings ===
Open System Preferences and go to Network and you should see "new interface detected enXX". In the Show list box select the new interface - Ethernet Adapter enXX.

Use this configuration on the new interface after 110822-SHR-CORE-images:
<pre>
IP-V4: manual
IP-Addr: 192.168.7.2 (you can use anything in 192.168.7.* but OM is configured by default to use 192.168.7.2 as the external gateway)
Subnet: 255.255.255.0 (should be the default - see tip below if have issue with these settings)
Router: 192.168.7.1 (not actually needed, OS X can figure this out for itself, unless you have other conflicting configurations)
</pre>

Use this configuration on the new interface before 110822-SHR-images:
<pre>
IP-V4: manual
IP-Addr: 192.168.0.200 (you can use anything in 192.168.0.* but OM is configured by default to use 192.168.0.200 as the external gateway)
Subnet: 255.255.255.0 (should be the default - see tip below if have issue with these settings)
Router: 192.168.0.202 (not actually needed, OS X can figure this out for itself, unless you have other conflicting configurations)
</pre>

Tip: If your Internet connection is also in the range 192.168.0.x then instead you might want/need to use:
<pre>
Subnet: 255.255.255.248
</pre>
However if you are running Leopard it may not let you set the subnet claiming that the IP 192.168.0.200 is an invalid address for that subnet. To get round this run the following from the OSX terminal (replacing en11 as appropriate):
<pre>
sudo ifconfig en11 192.168.0.200 netmask 255.255.255.248
</pre>

=== Testing Your Connection ===
You should be able to connect to your Openmoko! Try using Terminal (Applications->Utilities->Terminal) to ping the Neo at 192.168.0.202 and the roundtrip time should be between 1 and 2 ms.
ping 192.168.0.202

Then log into your Openmoko using ssh:
ssh root@192.168.0.202
The default password is blank (depending on the distribution you have on the Openmoko).

You can also [[scp]] files back and forth or share displays with X11. Additional software and configuration could allow telnet, SMB, or many other possibilities using the TCP/IP network over your USB connection.

Try pinging your Mac PC from the Openmoko
ping 192.168.0.200

Try pinging the outside world (a Google IP address)
ping 74.125.19.147
If that works then your Mac is routing the neo globally--if not see [[MacOS_X#Enabling_the_Mac_as_an_Internet_Router | Sharing Internet Connection with Mac]].

Lastly, verify that DNS is correctly configured between the Openmoko & Network:
ping www.google.com
If that doesn't work then see [[USB_Networking#Configure_Default_Neo_DNS | Configuring Default Neo DNS]] to try and resolve the issue.

Congratulations!!! The Neo is networked together with the Mac and sharing the Mac's interweb connection.

== Bluetooth Networking ==
{{InProgress}}

This approach is based on:
*[[Bluetooth_Support#Networking]]
*http://www.macosxhints.com/article.php?story=20051220221237711

Unfortunately we can't use the pand (PAN daemon for BNEP) or dund (Dial Up Networking daemon for LAP) since neither service is available for the Mac.

So, we configure a RFCOMM connection and a PPP gateway on the Mac. Finally, we connect the OM as a ppp client to the Mac.

The reversed direction (OM as the Access Point and the Mac as the client) is described shortly in [[Manually_using_Bluetooth#PPP_Networking]]

=== Making the Mac a PPP over Bluetooth Access Point ===

In the Bluetooth System Preferences (10.4.11)
* go to the Sharing pane
* add a new service "BluetoothAccessPoint" of type RS-232
* Enable that it is shown in the network preferences pane
* Apply

In the Network System Preferences
* activate the new network configuration (BluetoothAccessPoint)
* go tot the Modem tab and change the modem to "Null Modem 115200"
* Apply

In a Terminal, enter the following:
$ sudo /usr/sbin/pppd /dev/tty.BluetoothAccessPoint 115200 noauth local passive proxyarp asyncmap 0 silent persist :172.16.140.14

Here you see the 172.16.140.14 address, which makes it possible not to use natd, since it's in the same network as the Mac is. So the firewall knows where to sent it to -- no routing problems etc. Pick any free address in your private range. For instance, if you are using the following ... firewall: 192.168.1.1, Mac: 192.168.1.2, you can enter 192.168.1.3, assuming it's not used elsewhere on your network.

If you want to be sure you did it right, open the system.log file on the Mac (tail -f /var/log/system.log), and you should see something like this:
Jun 25 10:33:57 hostname pppd[679]: pppd 2.4.2 (Apple version 229) started by username, uid 0
Jun 25 10:33:57 hostname pppd[679]: Connect: ppp0 <--> /dev/tty.BluetoothAccessPoint

In Terminal, write
sudo sysctl -w net.inet.ip.forwarding=1
which should give the following feedback:
net.inet.ip.forwarding: 0 -> 1

In Terminal, write
sudo ifconfig ppp0 up.

=== Connecting the Openmoko as a Client to the Mac ===

On the Openmoko do the following

* Power on bluetooth

root@fic-gta01:~$ echo "1" > /sys/bus/platform/devices/gta01-pm-bt.0/power_on

* Scan for the Mac
root@fic-gta01:~$ hcitool scan
Scanning ...
00:0E:6D:C0:0l:6A Sho
00:20:E0:5A:FE:C8 MacBook

* start the PPP client

pppd 115000 192.168.1.202:192.168.1.200 local defaultroute pty 'rfcomm connect 0 00:16:CB:2F:A0:46 1'

* Enjoy

== WiFi Networking ==
{{InProgress}}

To Be Done.

== Neo1973 as a Bluetooth GPRS modem ==
{{InProgress}}

To Be Done.

= Enabling the Mac as an Internet Router =

Here is described how to enable your Mac to serve as a Internet Router for your Openmoko device.

Note: you have to open all services you want to use from the Openmoko in the Mac Firewall.

== USB connection ==

In the Sharing System Preferences
* click the Internet tab
* Check all the ethernet (en) interfaces you want to enable Internet access for (i.e. the USB connection)

SSH into your Neo and create /etc/resolv.conf, specify your Internet router IP address as the name server. You can simply copy the /etc/resolv.conf from your Mac.
scp /etc/resolv.conf root@192.168.0.202:/etc/resolv.conf

Example:
nameserver 192.168.1.200 # replace by your real nameserver address

Make sure your Neo routing table has entries so that all internet traffic is sent to your Mac (which will forward it to the outside world)

root@fic-gta01:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 usb0
default 192.168.0.200 0.0.0.0 UG 0 0 0 usb0

Don't forget to enable your USB interface for Internet Sharing!

== Bluetooth connection ==
{{InProgress}}

= Accessing data and services on your device =

== ssh ==

After making the USB connection work, start ssh:

ssh -l root 192.168.0.202

If you don't have installed the key, it will ask for a "yes" on the first connection. The root password is blank unless you change it.

MacBook-hns:~ hns$ ssh -l root 192.168.0.202
root@192.168.0.202's password:
root@fic-gta01:~$ hostname
fic-gta01
root@fic-gta01:~$

NOTE: the ssh daemon (dropbear 0.49) on the Openmoko appears to have a bug when sending the exit status back to the client. From time to time you receive an exit status of 255.

== SMB ==
{{InProgress}}

To Be Done.

== X11 ==
Launch Apple X11.
xhost +192.168.0.202.
On the Neo:
export DISPLAY=192.168.0.200:0.0

== Synchronizing ==
{{InProgress}}

This is not done yet. Possible solutions are SyncML or ZMacSync http://www.dsitri.de/wiki.php?page=ZMacSync

ZMacSync does not yet synchronize but allows more easy access to the Openmoko through Terminal/ssh.

= Developing Openmoko software on a Mac =

== Using virtualization software and MokoMakefile/OpenEmbedded ==

You can use VirtualBox, Parallels or VMWare to install your favourite Linux distribution and then develop just as on Linux.

There are some drawback since AFAIK dfu-util may not work correctly in such environments.

=== Parallels ===

Don't bother with Parallels Desktop for Mac (<=3), the current USB support is terrible and USB storage keys don't even work so there was no way I would try dfu-util. USB keys work under VMWare Fusion for Mac though I have yet to try dfu-util in an VM under VMWare Fusion as there is Openmoko Flasher for Mac. -- [[User: Eric|Eric]]

=== VMware Fusion ===

There is currently no vmplayer for OS X. But the Qtopia image (see [[Developing_with_C++_and_Qt#Use_pre-built_SDK]]) will work with VMware fusion. The script will search for vmplayer and complain. Just answer <tt>YES</tt> when asked if you have the vmplayer installed (I know, it's a lie, but...), and the script will run through. Afterwards open the directory where the files were installed and click on <tt>Qtopia.vmx</tt>.

In VMware Fusion USB Networking is working properly, just plug in the device and connect it to your virtual machine.

Unfortunately dfu-util is currently not working. In fact if you get dfu-util working via unplug/replug method on Mac OS X it works inside VMware too.

=== VirtualBox ===

dfu-util is not working, has some problems with getting exclusive access to the USB device.

== Natively ==
{{InProgress}}

There are some efforts to get through process of compiling OE and Openmoko under mac: [[Openmoko_under_QEMU_on_MacOSX]]

== GNUstep/mySTEP SDK ==

There is a [[QuantumSTEP]]/mySTEP project to port GNUstep to the Openmoko/Neo: [http://www.quantum-step.com/wiki.php?page=Openmoko-Edition More Info]
An SDK for Xcode/Interface Builder is also available: [http://www.versiontracker.com/dyn/moreinfo/macosx/20581 Entry at Version Tracker] [http://www.quantum-step.com/wiki.php?page=SDK More Info]

== Tools for Developers ==

Some tools that run on MacOS X

=== mkfs.jffs2 ===
[http://www.quantum-step.com/download/Openmoko-Edition/mkfs.jffs2.tgz mkfs.jffs2] - make JFFS2 (root) file system (Universal Binary). Package includes sources and Xcode 2.4 project file to rebuild on MacOS X 10.4.11. NOT TESTED DEEPLY.

mkfs.jffs2 --pad=0x700000 -o rootfs.jffs2 -e 0x4000 -n -d/tmp/jffsroot/

=== Crosscompiler Toolchain ===

[http://www.quantum-step.com/wiki.php?page=Compiler gcc 2.95.3] - OABI cross compiler toolchain (C, C++, Obj-C) with Linux headers (PPC and Intel Macs)

If someone has a newer one that works, please provide as an installable OSX Package.

Will the ones from MacPorts work? [http://www.macports.org/ports.php?by=name&substr=gnueabi] I'm still trying to get QEMU to work and haven't had a chance to test it yet.

= Other Resources =

== Search Software Repositories ==

[http://www.versiontracker.com/php/qs.php?action=search&str=openmoko&srchArea=macosx Keyword Openmoko] at VersionTracker

== Discussion Fora ==

[http://www.oesf.org/forums/index.php?showforum=63 Mac Issues Forum] at Open Embedded Software Foundation (was Zaurus User Group)

[[Category:Flashing Openmoko]]
[[Category:Host OSes]]

[http://www.mac-how.net/ Mac How] for discussion questions about Mac

Manuals/SHR

2012-02-12T08:13:34Z

Glenn: /* USB */ +date

{{Languages|Manuals/SHR}}
{| align="right"
| __TOC__
|}

==SHR Introduction==

Welcome to '''[[SHR]]''', a community driven distribution for (not only) Openmoko, HTC Dream, PalmPré and Nokia n900 phones.

[[Image:SHR-Logo.png|200px|thumb|center|SHR]]

'''SHR''' (Stable Hybrid Release) is here to provide you with Root FileSystem images that you can easily install into your device to use as a daily phone and PDA. There are many prepackaged programs available that can be installed upon demand by users, it can also be used by developers as a base image for customized and flavored distribution or release.

'''SHR unstable (SHR-U)''' is a testing environment before software gets stabilized and it is the main testing ground for [[FSO]] releases. '''SHR testing (SHR-T)''' images provide as much stability as possible for day-to-day usage. Some users find the SHR-U releases preferable for everyday use. [http://lists.shr-project.org/pipermail/shr-user/2010-September/006187.html]

{{Note|In meanwhile '''SHR-U''' and '''SHR-T''' are no longer supported. '''SHR-CORE''' is now the official distribution and is developed by the same developers which developed SHR-U and SHR-T. So please use the new SHR-CORE images.}}

==Installation==
Use [[Qi]] as bootloader to avoid [[GPS]] problems on suspend/resume.
Switch off you freerunner (if necessary) and start NOR uBoot by pressing AUX and Power-On at the same time and then start [[dfu-util]] on your computer with the following parameters for GTA2:
# dfu-util -a u-boot -R -D [http://wiki.openmoko.org/wiki/Qi#Download qi-s3c2442-master-hist_3b8513d8b3d9615e.udfu]
See [[Flashing the Neo FreeRunner]] or [[Flashing the Neo 1973]] for more details on flashing your phone.

===Getting SHR===

You need to download two files for your version as above: kernel and root filesystem. Depending whether you will be installing into the internal [[NAND memory]] or on the [[microSD]] card, you need to either get .jffs2 file for NAND or .tar.gz file for microSD.

- Get the latest kernel from the below linkpages. Starts with uImage-...

- Get the root filesystem:
* After 110822:
** for NAND [[jffs2]]: .rootfs.jffs2
** for NAND [[ubifs]]: .rootfs.ubi
** for µSD tar.gz: .rootfs.tar.gz
** for µSD ubifs (ubi or ubifs?): .rootfs.?
* Before 110822. (Those are '''full''' images. You can also choose images with less packages, marked as '''lite'''):
** for NAND [[jffs2]]: full-om-gta0_.jffs2
** for NAND [[ubifs]]: full-om-gta0_.ubi
** for µSD tar.gz: full-om-gta0_.tar.gz
** for µSD ubifs (ubi or ubifs?): full-om-gta0_.?

;GTA02 Neo FreeRunner
* SHR-CORE after 110822 - additionally choose phone catalog e.g. om-gta02 (For more information of staging images read http://shr-project.org/trac/wiki/Stabilizing ):
** Line (preferred): http://build.shr-project.org/shr-core/images/
** Staging line (useful for testers, choose version or latest catalog): http://build.shr-project.org/shr-core-staging/
* Before 110822:
** testing line: http://build.shr-project.org/shr-testing/images/om-gta02/
** unstable line (before 110822): http://build.shr-project.org/shr-unstable/images/om-gta02/

;GTA01 Neo 1973:
* testing line: http://build.shr-project.org/shr-testing/images/om-gta01/
* unstable line: http://build.shr-project.org/shr-unstable/images/om-gta01/

;Image lite to image full
If you flashed a '''lite''' image and want to upgrade to the '''full''' image run:

opkg update
opkg install task-shr-apps task-shr-games task-shr-gtk

;Kernel modules
The images of the filesystems mentioned above (.jffs2, .tar.gz), already contain the newest kernel modules.

Get the new kernel modules if you only want to flash a new kernel, but not a whole new file system. From the same page as the kernel download the modules to match your kernel (their dates should be the same). Use sftp to put that file on the FreeRunner via the usb connection. Run gzip to unwrap the modules:
# gzip -dc modules-...tar.gz | tar -xf - -C /

===Installation on Flash===

In order to install your SHR distribution directly to your FreeRunner Flash memory (NAND), you need to get the desired filesystem file ( <tt>.jffs2</tt> ) as described above and flash your device using the <tt>dfu-util</tt> tool.

Please visit [[Flashing the Neo FreeRunner]] for more details about flashing and see [[Dfu-util]] for detailed information about the dfu-util.

{{Note|Your battery must be charged (sufficiently) before NAND flashing. Symptom of insufficient charge: Your progress bar "####" stops while flashing. If so, you must charge, and later you should be able to make the complete flash.}}
Commands to flash the filesystem and the kernel:

for the GTA02 Neo FreeRunner (jffs2 filesystem):

# dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D full-om-gta02.jffs2
# dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-om-gta02-latest.bin

for the GTA02 Neo FreeRunner (ubi filesystem):
# dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a u-boot -R -D qi-ubi-s3c2442.udfu (only first time)
# dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-om-gta02-latest.bin
# dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D full-om-gta02.ubi
# make shure that Qi is booting the NAND ( remove sd card or touch /boot/noboot-GTA02 )

for the GTA01 Neo 1973:

# dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a rootfs -R -D full-om-gta01.jffs2
# dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a kernel -R -D uImage-om-gta01-latest.bin

{{Note|If you get the error message while flashing:

Starting download: [##############################dfu_download error -84 Error during download

It is most likely caused by trying to flash an image that is too large.}}

===Installation on the microSD Card===

Installing SHR on your microSD Card depends on the Bootloader you are using, ''uBoot'' or ''Qi''.

In simple words, the difference between both systems resides on how you must prepare your microSD Card and files you use to fill them:
==== uBoot and SHR on microSD Card ====
If you use ''uBoot'', you need to create two partitions. First partition, not so big, in FAT16 or ext2 where you have to place the kernel file (<tt>uImage-om-gta02-latest.bin</tt>) and second partition in ext2 or ext3 where you have to uncompress the filesystem file (<tt>shr-image-om-gta02.tar.gz</tt>).

==== Qi and SHR on microSD Card ====
If you use ''[[Qi]]'', you only need an ext2 partition (e.g. with [[fdisk]]) into your µSD Card.
# mkfs.ext2 /dev/sde1
If your µSD Card drive has the device name <tt>/dev/sde1</tt>.
Download <tt>[http://build.shr-project.org/shr-testing/images/om-gta02/ shr-image-om-gta02.tar.gz]</tt>.
Uncompress the filesystem image file (<tt>[http://build.shr-project.org/shr-testing/images/om-gta02/ shr-image-om-gta02.tar.gz]</tt>) on the µSD Card (e.g. with a µSD-SD-Card-Adapter on your Linux Desktop Computer. Insert the µSD Card back into your Freerunner and boot your Neo.

In this case Qi Bootloader is going to look for the kernel image into the <tt>/boot</tt> directory for file named <tt>uImage-GTA02.bin</tt> .

===Bootloaders===

Make sure you have recent and correct versions of [[Booting_from_SD | uBoot]] or [[Qi]] installed, please visit the links for detailed information and tips. For example [[Android]] uses modified [[Qi]] which can cause you troubles when using SHR.

===SHR version===

Should you ever later wonder what version of SHR you have actually installed, please run

timestamp of image creation:
cat /etc/timestamp

latest shr version from opkg upgrade (this version is changed everytime someone builds task-base on shr buildhost):
cat /etc/shr-version

{{Note|Please note that this is true only for shr-u, with shr-t running opkg update;opkg upgrade does not change the SHR version. Only flashing or a new image download can change the SHR version. But this will be also merged to shr-t later.}}

==Running SHR==

===First boot===
[[Image:Shr-boot-preview.png|200px|thumb|center|SHR Boot Splash screen]]

First boot usually takes a bit longer as your phone's new software needs to do some initial setting up. It is recommended to reboot after this first boot (and after the initial setup), to make sure that all packages get initialized properly. The application switching shelve (shr_elm_softkey) doesn't show up during first boot when the initial wizards are at work, [http://shr-project.org/trac/ticket/1105 reboot is required] and then application switching works as expected.

====Initial Setup====

During the first run, Setup is automatically initiated to walk the user through basic setup of the Enlightenment desktop environment. These steps vary as both Enlightenment desktop and SHR evolve, at this point preferred language and desktop profile options are available. The Profile offers to choose a preconfigured way of displaying the desktop. Illume2-SHR (with continuous development) and Illume-SHR (discontinued) profiles are available. '''Illume2-SHR''' is the recommended Profile.

{| class="wikitable"
| [[Image:SHR-Setup-Language.png|200px|thumb|language selection]]
| [[Image:SHR-Setup-Profile.png|200px|thumb|theme selection]]
| [[Image:SHR-Wizard.png|200px|thumb|SHR Wizard]]

|}

Note, you may need to ssh into the device and run /usr/bin/xinput_calibrator_once.sh if calibration is wrong. I found this using a Neo1973 and SHR images from around May 2010.

====SHR Wizard====
After the initial Setup, SHR Setting Wizard is launched to allow setting up your local phone settings and setting up root password. Sometimes a '''Please wait''' message is displayed for a long time, as the wizzard is waiting for the SIM card to be initialized.

===First look===
[[Image:SHR-First-Look.png|200px|thumb|Desktop screen]]
[[Image:SHR-Task-Buttons.png|200px|thumb|Task switch buttons]]
====Illume desktop====
Illume desktop is the default home screen of the SHR desktop.

Application definition files located in /usr/share/applications are displayed here as icons. All applications are ran fullscreen and you can switch between them by using the the '''< left''' or '''right >''' arrows on sliding shelve available by tapping Top Shelf on any empty space. To close applications, choose '''X''' from the same sliding shelve.

If tapping Top Shelf on an empty space the sliding shelve doesn't appear then you can activate it opening a Terminal and giving this command:

killall shr_elm_softkey ; shr_elm_softkey &

Several icons (e-gadgets) are placed in the Top Shelve:

The '''L''' icon is to switch between left/right mouse click. By taping this icon the icon gets changed to R and next tap will be as right click. After the click, the behavior is automatically switched back to Left click so any following taps are left click again.

'''Mode Switch Icon''' allows to split the screen horizontally or vertically, thus allowing to display two applications at the same time.

'''Keyboard icon''' pops up or hides the Keyboard.

'''Illume Settings''' icon (represented by SHR logo) invokes the [[#Illume_settings | Illume desktop settings]].

'''Home Icon''' allows quick go to the home desktop/application.

'''GSM''' and '''Battery''' status icons, as well as '''time''' are displayed by default, Bluetooth and WiFi status icons available in the setting of the Top Shelve content.

To '''reconfigure the Top Shelve''' itself, use the L/R click icon to Right click on the Top Panel and choose: Illume Indicator->Set Content to add or remove items from the Top Panel. Or, upon right click on the Top Panel you can also choose Illume Indicator->Begin Move/Resize to move your icons around. To escape this mode, you must click on the L/R gadget's edge, it will switch to L, then choose R again, right click on the Top Panel and select Illume Indicator->Stop Move/Resize.

====Keyboard====

Keyboard comes up automagically when a text field is tapped or you can also toggle the keyboard by it's icon in the Top Shelve. In the Keyboard, dictionary switcher is the arrow-up on left side, alternative keyboard layouts are under the ABC button on the right. The Default keyboard has English dictionary enabled. For Space quick slide left-to-right, for Enter, quick slide up-down, to quick change keyboard layout quick slide down-up. While typing with a dictionary enabled keyboard, possible word options start appearing in the keyboard's upper part or more word options are available under the arrow-up on the left. When happy with the word, tap it, it will be pasted into the text field with a space attached. The Keyboard and dictionary can [[#Illume_keyboard_and_dictionaries | easily be localized]].

Problem with external USB keyboard mapping (arrows keys doesn't work) can be solved with [http://wiki.openmoko.org/wiki/Usb_keyboard#Arrow_keys_disfunction this little script].

====Copy and Paste====

In '''E based''' applications, for example the phone suite (contacts, messages...), by tapping and holding down for over two seconds the Select-Paste menu will pop up. By pressing Select, you can now swipe through the text to select desirable part. Tap and hold down again, Copy-Cut-Cancel menu will appear to Copy to clipboard. Another long tap will provide Select-Paste for Paste.

In '''Gtk''' based application, you can use keyboard for Ctrl-C (Copy) and Ctrl-V (Paste) or items in Menu if provided.

In the Vala '''Terminal''', you can select simply by swiping through the text and for Paste there is an icon in the menu bar of this application.

Copy & Paste between different toolkits has some limitations. See the table below. In Ventura, select is possible, but copy/paste doesn't seem to work at all.

{| cellspacing="0" class="wikitable" border="1" style="font-size: 85%; text-align: left;width="100%"
|-
! From -> To
! to GTK
! to E
! to Terminal
|-
| from GTK
|style="background:#88FF88;"|Works
|style="background:#88FF88;"|Works
|style="background:red"|Doesn't work
|-
| from E
|style="background:red"|Doesn't work
|style="background:#88FF88;"|Works
|style="background:#88FF88;"|Works
|-
| from Terminal
|style="background:red"|Doesn't work
|style="background:#88FF88;"|Works
|style="background:#88FF88;"|Works
|-
|}

====Alarm====

The Alarms application (installed by default) allows alarm presetting for single or repeatable alarms. If you set an alarm and turn your Openmoko FreeRunner off, at the time of the alarm the phone will be powered up and alarm will sound.

====Phone applications====

Besides other software, SHR comes with 4 main phone applications: ''Dialer'', ''Contacts'', ''Messages'' and ''Phone log''.

{|
| [[Image:SHR-Dialer.png|200px|thumb|Dialer]]
| [[Image:SHR-Contacts.png|200px|thumb|Contacts]]
| [[Image:SHR-Mesages.png|200px|thumb|Messages]]
| [[Image:SHR-Phonelog.png|200px|thumb|Phone log]]
|}

=====PIM data=====

======Storage======
PIM data (contacts, messages etc.) are stored through internal opimd storage mechanism into

/etc/freesmartphone/opim/pim.db

This database can easily be copied from one SHR installation to another, for example due to a need for reflashing. The Contacts application can display a picture of the contact. As the pim.db database contains a path to the picture files only but not the pictures themselves, therefore, in case of PIM data backup or transfer, these picture files '''need to be copied too'''.

======SIM Contacts======

SHR phone applications do not read SIM contacts by default but you can use SIM Manager to access your SIM contacts '''SHR Settings -> Others -> SIM Manager''', which allows you to edit and import the SIM contacts into the internal storage. You can also use Pisi to import your SIM contacts into opimd.

======Synchronization======

'''[[Pisi]]''' is an application for synchronizing PIM data and can be used for import and export your contacts, calendar entries etc. between various sources, like VCF, LDAP, Google and more. To install Pisi:

opkg install pisi

After installation, edit Pisi configuration in '''.pisi/conf''' in your home directory. To have a correct opimd fields support, make sure '''field_support=TRUE''' is enabled in opimd section.

With the installed package you have a well-documented sample that is placed at
/usr/share/doc/pisi/conf.example
You may copy the file and rename this file to
/home/root/.pisi/conf
as a starting point - then edit this file in order to configure your PIM synchronization data sources. Look at section

[opimd]
description=OPIMD Contacts
module=contacts_opimd
field_support=TRUE

=====Idle screen=====
[[Image:SHR-Idle_Screen.png|200px|thumb|Idle Screen with GSM operator strength and name. GPS, WiFi, Display and CPU are requested, Battery status.]]
Upon press of the AUX button Idle Screens locks up the display. AUX press or a finger slide on the Slider unlocks the screen.

At the top, status icons are shown to indicate what is going on in the phone:

From left to right:
GSM strength and operator. Requested Resources (GPS, Display etc., when for example Display is requested, the screen will not dim). Battery capacity.

====Hardware Buttons====

=====Power Button=====

[[Image:SHR-Quick-Settings.png|200px|thumb|Quick Settings]]

The '''PWR''' (Power) button is mapped to start [[#quick_settings | Quick Settings]] screen (Illume System menu in older versions) on a short press.

Mapping of the PWR button be configured via the '''Illume Settings-> Input -> Key Bindings'''.

Pressing the Power button for longer then 8 seconds will force a complete power down of the device. This is hardconfigured in the kernel.
<div id="quick_settings"> </div>
The '''Quick Settings''' screen provides several toggles: Airplane mode, Phone profiles, Power settings and Power buttons.

=====Auxiliary Button=====
The '''AUX''' (Auxiliary) button is mapped to toggle on/off the SHR Idle screen. Mapping of this button is configured in /etc/phonefsod.conf

idle_screen = aux,lock

You can configure the [[#idle_screen | Idle Screen]] to come up even during active phone call by adding '''phone''' to the setting:

idle_screen = aux,lock, phone

<div id="idle_screen"> </div>
The '''Idle Screen''' shows current date and time, missed calls and messages and also what [[#FSO_Resources | FSO resources]] are currently being requested - used.

======Replacing idle screen======

If you wish to use the E simple LOCKED screen instead of the SHR Idle Screen, edit '''/etc/phonefsod.conf''' to this:

# when to show idle screen
# ...
# idle_screen = aux,lock
idle_screen =

You need to restart phonefsod to make the change happen.

Also, change key mapping for the AUX button by setting '''Illume Settings''' -> '''Input''' -> '''Key Bindings''', bind the key '''XF86Phone''' to '''Desktop Simple Lock'''

====Settings applications====

Many desktop and phone settings are possible to do via graphical interface. [[#SHR_Settings | SHR Settings]] provides access to most common phone personality settings and is accessible by tapping Settings icon on the desktop. [[#Illume_settings | Illume settings]] (and Enlightenment desktop settings) are accessible on Top shelve by tapping the "SHR Logo" icon. Also, FSO and SHR phoneui applications have configuration files in /etc where some of the above mentioned apps write and that can be edited manually.

===First steps===

Right after installation and first boot you might want to do a few initial steps like adjusting the call volume and some other tasks.

====Audio - Call Volume====

During the first phone call please use the Volume and Mic sliders on the Active Call Screen and adjust them to fit your preferences. The new improved settings will be used for all in/out-going calls thereafter.

====Network Connection====

[[#Networking|Establish network connection]] and SSH into your phone. You can establish connection either via USB to your desktop and enable NAT or you can connect through Wifi.

====Initializing the opkg database====
''Initialize the opkg database'' in order to install some applications from SHR repositories or from other sources, for example [http://opkg.org opkg.org]. While being online, you need to run

opkg update

Searching in the opkg database can take a long time. You can speed things up by dumping the database into a file and grepping it through. Do this only once or after every opkg update:

opkg list > packages.txt

Then you can search quickly for package name, for example for [[Navit|navit]]:

grep navit packages.txt

====SwapSpace====

When the RAM is used up, applications get killed. This is particularly bad while doing opkg upgrade. Therefore you might want to create a swap space. Read [[SwapSpace]] article or the [http://shr-project.org/trac/wiki/swap swap article on the SHR wiki].

==Settings==
===SHR Settings===
[[Image:SHR-Settings-main.png|200px|thumb|SHR Settings]]

SHR Settings is the main setting application of SHR. It provides an easy way of setting up your phone to your liking - from phone related settings, to requesting resources in order to prevent screen dim or suspend (for example while using GPS).

Please refer to [[#FSO_Resources | this section]] about a better way to manage preventing screen dim or suspend.

While some settings are persistent over reboots, others are not.

====Main Screen====
The main screen is divided into eight categories, which contain several modules. Every SHR Settings module has a specified task - for example controlling the GSM antenna power, setting the time etc.

====Phone====
Here you can set if the GSM antenna is on and if your phone number is shown when you call someone.

'''GSM'''
In GSM settings you can turn off and on GSM module. After turning off antenna, whole GSM modem is turned off.

To list available providers, click on Operators button. Scanning can take some time. After a while, a list of operators should pop up.

You can't connect to operators marked [forbidden].

Selecting an operator from the list also changes modem registration mode to manual. It won't register to other network, even if some is available and has better signal strengh. To return to automatic mode, click "Automatic" button in operator list.

'''Call'''
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Phone.png|200px|thumb|Phone settings]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-List-providers.png|200px|thumb|List providers]]

|}

You can set if your phone number should be displayed to other party. You can either depend on network decision ("By network") or force it manually ("Manual")

'''Phoneutils'''

For the default SHR phone applications to be able to correctly parse incoming calls/messages and match them with your contacts, you will need to set the right country code for your location. (for example 420 for Czech republic) for more info, please go to: http://wiki.openmoko.org/wiki/Phone_Prefixes

'''SIM'''

Here you can view some informations about your SIM card and clean phone and messagebooks.

====Profiles====

Here you can select the current profile, which the device should use to determine ring tone etc.

'''Current profile'''

Here you can adjust properties of the currently used profile.

To change the ring tone, click the "Change" button.

To use your own ring tone, place it in /usr/share/sounds directory.

After selecting a sid tune as the ring tone, there are available controls to select tune number from the file.

If you like to test a .sid you can play it using this command on the FR:

gst-launch filesrc location=Arkanoid_PSID.sid ! siddec tune=2 ! alsasink

Note that it's a ! used and not a | to construct the gstreamer pipe command.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Profiles.png|200px|thumb|Profiles]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Profiles-Ringtones.png|200px|thumb|Ringtones]]

|}

====Connectivity====

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Connectivity.png |200px|thumb|Connectivity top]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Connectivity2.png |200px|thumb|Connectivity bottom]]
|}

'''WiFi'''

With the "WiFi radio" toggle you can set, if the wifi module is powered. WiFi radio has to be turned on before trying to connect to a WiFi network, unless you try to connect through [[Mokonnect]] which is capable of powering it up.

'''GPRS'''

To enter APN, login and password fields, just click on the actual value (default: "internet"). Your phone provider can provide the required configuration options.

{{Note|You can also use Mokonnect to manage your GPRS connection}}

'''USB'''

With this toggle you can switch USB port between device (Neo to PC) or host (device to Neo) modes.

'''Bluetooth'''

To power up Bluetooth module, switch the "Bluetooth radio" toggle to "On". After that, the "Visibility" toggle should arrive - set it to "On" if you want your FR to be visible by other Bluetooth devices on scanning.

====Power====

'''Battery'''

This module displays informations about battery state - charge, voltage, remaining time etc. To update the data, click the "Update" button.

Here you can also force enable 500mA charging.

'''Display'''

With this slider you can easily set the backlight brightness.

{{Note|This setting isn't permanent over sessions. At boot backlight is set back to 80%.}}

'''Power'''

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Power.png |200px|thumb|Power]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Timeouts.png |200px|thumb|Timeouts]]
|}

'''Timeouts'''

Timeouts are reached in this order: Busy state -> idle -> idle dim -> idle prelock -> lock -> suspend.

{{Note|Storing of this setting via D-bus calls is not supported in the new API of Vala rewrite of FSO2 and therefore SHR Settings doesn't have a functional setting for this.}}

You can set values of idle timeouts manually. The default parameters are stored in '''/etc/freesmartphone/conf/GTA02/fsodeviced.conf''' but customized '''.fsodeviced.conf''' file in your home directory will take precedence (if it exists, the one in /etc/... will be ignored, so you have to copy the whole file and tweak it):

[fsodevice.kernel_idle]
suspend = 20
lock = 2
idle_prelock = 12
idle = 10
idle_dim = 20

To turn off a timeout, set it to -1.

====Appearance====

'''Theming'''
[[Image:SHR-Neo-Theme.png|200px|thumb|Neo theme]]

The Apperance section allows you to change between installed themes. To install more themes, see also [[#Installing themes | Installing themes]].

You can change finger size - this will mainly effect vertical spacing between widgets.

Switching between engines:

E can be switched to use different engines. The default engine is x11. Alternative engine x11-16 is not supported and results in buggy behavior of several applications, for example the phone suite or Ventura browser. It's usage is not recommended.

Changing system boot Splash screen is also possible in this module. To install more splash screens, see also [[#Installing splash screen themes|Installing splash themes]].

====Position====

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-GPS.png |200px|thumb|center|GPS]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-GPS-Satelites.png |200px|thumb|GPS Satelite details]]
|}

'''GPS'''

By default, GPS is turned on only when requested by an application. That state corresponds to "Auto" setting. After changing to "Manual", you can force set it to on or off.

'''GPS information'''

This page can be used to monitor GPS status. You either have to turn GPS on manually or start another application to enable the GPS.

You can also view information about every visible satellite and check, which are used for getting a fix. To do that, click "Satellite details".

'''Remove AGPS data'''
If you experience problems with GPS, turn it off, click "Remove AGPS data" and reboot your Neo.
Assisted GPS ([[aGPS]]) support GPS receiver to find position by non-satellite information.

====Date/time====

[[Image:SHR-Settings-Date-Time.png |200px|thumb|Date & Time]]

'''Time'''

Here you can view and set the time. By default, the time is just displayed, To adjust it, click on "Set time".

After finishing adjusting, click the "OK" button.

'''Date'''

This module displays the current date.

====Others====

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

[[Image:SHR-Settings-Others.png |200px|thumb|Others]]

'''PIM'''

Pim data are stored in opimd domains. Every opimd domain has different backends to store its data to. The domain reads data from every backend and writes data to the default backend. This elector allows you to choose the backend that stores newly generated data, it doesn't copy or move existing data to a different backend.

'''Services'''

The services selector is listing scripts from /etc/init.d/ directory.

After clicking on a servis, you can either start, restart or stop the service and view the result.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Settings-Services.png |200px|thumb|center|Services]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |

[[Image:SHR-Service-restart.png |200px|thumb|Services debug screen]]
|}

'''Userspace backups'''

Here you can either archive or restore your files and configurations.

=== Illume settings ===

The Illume desktop can be easily customized - tap the Settings icon (SHR Logo) on the Top Shelve.

'''Illume settings''' provides various options to alter the desktop environment. You can change sizes of elements, single or double click, wallpaper. To access all the various options, open Illume Settings and slide the visible icons to the left, to view more options on the right hand side.

Some setting screens are not resized properly to fit the phone's display - for example the Wallpapper setting. This is a known bug already reported upstream.



==Localization==

=== Localize SHR manually ===

[[Image:SHR-Illume-Settings-Languages.png|200px|thumb|Setting Language]]

====Desktop environment====

You can change the language of the SHR desktop environment by using the Settings of Illume. For Example, for Czech language: in the Illume top shelf go to Settings (SHR Logo) -> Language -> Language Settings -> and choose: Čeština. If your language is not in the menu you can install by using opkg.

You can list all available languages by running:

opkg list | grep eglibc-locale-

And install the language of your choice (for example czech):

opkg install eglibc-locale-cs

After this, the Language Settings of Illume will offer Czech.

This will localize the Illume environment and will also set correct lang environment variable of your desktop.

====Applications====

If you wish to have other applications localized, you need to install translation for each of them (presuming it is available):

This will install czech localization for SHR phone applications, SHR Settings and TangoGps:

opkg install libframeworkd-phonegui-efl-locale-cs shr-settings-locale-cs tangogps-locale-cs

====Terminal environment====

For localized terminal environment (ssh login) set lang variables in /etc/profile.d/locale.sh, example for Czech language:

export LANG=cs_CZ
export LC_ALL=cs_CZ

====Illume keyboard and dictionaries====
[[Image:Illume-keyboards-terminal-dutch-nl-screenshot.png| Dutch terminal virtual keyboard|256px|thumb]]
→ more details on page [[Illume keyboard]]

Unlike other input methods for mobile devices, the Illume keyboard is corrective rather than predictive. It detects what you mean, even if some letters mistyped. If you accidently hit some keys next to the correct one Illume still recognizes the word. This kind of input method compensates for the small size of the keys. Keep a key pressed for a longer time to affirm you really mean it.

An English dictionary is used by default. A few dictionaries for other languages are included in the SHR distribution. In addition, every dictionary for [http://en.wikipedia.org/wiki/MySpell myspell] can be used.

You can install a different keyboard with a layout which fits your language or alternatives for the default keyboards like the numerical one. The localized [[Illume keyboard]]s are available in the SHR repository under the name ''illume-keyboard-LANG''.

==== German (and Austria) Language ====

See [[Configure_SHR_for_German-speaking_use]] for detailed customization for german speaking.

===Date and time===
{{Note|This needs a complete and correct rewrite.}}

Date and time are automatically set from GPS or Network. The easiest way of setting the time for the first time is to run TangoGps (GPS & Map icon) and obtaining GPS fix. Time will then be set automatically.

The local timezone is automatically retrieved from the GSM network.

It is possible to instruct framework on how to set the time and timezone in /etc/frameworkd.conf :

[otimed]
# a list of time/zone sources to use or NONE
timesources = GPS,NTP
zonesources = GSM
# use an ip address here, otherwise DNS resolution will block
ntpserver = 134.169.172.1

To disable automatic date/zone settings, simply create an empty [otimed] section in /etc/frameworkd.conf

Timezone change

Create a symlink named /etc/localtime which points to the appropriate file in /usr/share/zoneinfo. For example, if you're in France., the following command will link the correct zoneinfo file to your /etc/localtime, giving you the correct time:

ln -sf /usr/share/zoneinfo/Europe/Paris /etc/localtime

Afterwards, edit /etc/timezone if necessary [?]

Local timezone work instantly for the current boot when:

TZ="Europe/Paris"
export TZ

For a permanent timezone change edit /etc/profile and change to:

TZ="Europe/Paris"

If you use UTC time, set '''UTC=yes''' in '''/etc/default/rcS'''.

Adjusting time manually:

Via SHR-Settings -> Date/time -> Set time

From the Freerunner console:

date -s "YYYY-MM-DD hh:mm"

From linux based desktop:

ssh root@192.168.0.202 "date -u -s `date -u +%m%d%H%M%Y.%S`"

The above does NOT work from Ubuntu as of 4/2/2010, the proper format is:

ssh root@192.168.0.202 "date -u -s `date -u +%Y.%m.%d-%H:%M:%S`"

Set the hardware clock to the system time:

hwclock --systohc

Is this better?:

hwclock --utc --systohc

==FSO Resources==

[[FSO]] is in control of each device. These are called ''resources''. If the software wanting to use the device is capable of requesting this resource via <tt>d-bus</tt>, FSO will do this, otherwise you might need to power the device manually. After the requested resource is released, FSO will power it down. Manual resource request can be done through ''SHR Setting'' or you can use <tt>fsoraw</tt> command. (Using fsoraw is faster and better than running dbus commands)

opkg install fsoraw

Example of usage fsoraw:

fsoraw -r Display mokomaze

See [[FSO Resources]] for more details on using the following resources:

'''Wifi'''

Unless this resource is enabled you've no eth0 and wifi module is completely un-powered. Use the [[Mokonnect]] network manager to set up networks, it will power Wifi up automatically when needed.

'''Bluetooth'''

You need to have this resource requested to have bluetooth module powered.

'''GPS'''

The fso-gpsd is a daemon waiting for gsmd connections, automatically powering the device on and off. When a connection exists, it powers up the GSM. In SHR Settings you can switch GPS completely off SHR Settings -> GPS -> Manual > Off

'''GSM'''

You need to have this resource requested to have GSM module powered.

'''Display'''

While this resource is requested the display won't be blanked and suspend is disabled.

'''CPU'''

While this resource is requested then suspend is disabled. Display will blank as normal.

'''Test'''

A test resource.

'''UsbHost'''

While this resource is requested the USB is turned into powered USB Host mode.

'''Accelerometer'''

You need to have this resource requested to have the Accelerometer module powered.

==Networking==

There are several ways of networking - Wifi, USB, Bluetooth and Gprs:

===USB===

By default, USB networking is enabled in <tt>/etc/network/interfaces</tt>, where enhanced configuration can be direct edited. The phone default IP address is 192.168.0.202. Some setup is required on the desktop side, please read [[USB Networking]].

{{Note|IP adresses are changed in new SHR-CORE images (after 110822), phone 192.168.7.2 host: 192.168.7.1}}

===WiFi===

WiFi manager [[iliwi]] is available by default for search/connect/making default a wifi connection. ''iliwi'' uses key only in hex format. The Wifi device is not required to be manually turned on via SHR-Settings as ''iliwi'' will automatically enable the device when needed and disable it after use. iliwi needs to stay running to keep the WiFi connection enabled.

When WiFi is connected, the Idle screen show the icon of the WiFi resource being occupied.

===GPRS===

GPRS Credentials are set during the first run in SHR Wizard and you may edit them at any time via SHR settings or direct editing of /etc/phonefsod.conf. GPRS connection can then be established/closed via SHR Settings or through SHR Quick Settings (available under the Power button). SHR Quick Settings - Network tab allows also connection sharing - this will share the GPRS connection with USB network and run DHCP server to provide the client with an IP address.

When GPRS is connected, the idle screen shows a small G above the signal strength indicator.

{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |
[[Image:SHR-Gprs-Share.png|200px|thumb|GPRS + Connection sharing]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |
[[Image:SHR-Iliwi-Scan.png|200px|thumb|Iliwi WiFi scanning]]

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |

[[Image:SHR-Iliwi-Connect.png|200px|thumb|Iliwi WiFi connecting]]

|}

==Bluetooth==

Bluetooth can be used for several different applications - file transfer (OBEX), networking, input devices (HIDD), music playing (A2DP), calling etc. In some occasions, the devices need to be authorized - paired. At the moment, support for some bluetooth functions is better than for others - it is possible to do all mentioned above with the notice that phone calls with bluetooth headset are always routed to the bluetooth even if the bluetooth headset is not around, making it quite difficult to use.

In the SHR repositories are applications ready to be installed (by opkg) that already do provide bluetooth support. This means that they request the bluetooth resource automatically, can search bluetooth devices around, help you with pairing and can perhaps even reconnect bluetooth headset upon resume from suspend. From applications that have some bluetooth support some are for example [[Launcher]] (home screen launcher and phone suite), [[Podboy]] (podcast player), [[Emtooth]] (bluetooth manager). In order to set up bluetooth for phone calls, some manual setup from [[#GSM_phone_calls_with_bluetooth_headset | bellow]] is still required.

===Bluez3 - the manual non D-Bus way===

If you want to use the bluetooth device directly, you need to turn the bluetooth radio on in SHR Settings -> Connectivity -> Bluetooth Radio: On. You can also make the bluetooth device visible here.

====OBEX file transfer====

There are several obex programs allowing file transfer, all in console at the moment. Obexpush installs obextool, and opd daemon:

opkg install obexpush

Default receiving path (editable in /etc/default/opd_args ) does not exist, so create it

mkdir /var/obexpush

Files are then received automatically, no notice, no confirmation... they just silently appear in /var/obexpush

To send some files, first scan for devices:

hcitool scan
Scanning ...
00:16:41:F5:A5:BC laptop

Then send the file onto bluetooth address found in the scan:

obextool push image.jpg 00:16:41:F5:A5:BC 10

====Connect Bluetooth keyboard====

hidd --search

Editors note: This is the old bluez3 way, but it works. New bluez4 way will replace this.

===Bluez4 - D-Bus based way===

SHR uses bluez4 which is completely different from bluez3. The bluetoothd is taking care of most of the bluetooth now. Please see [[Manually using Bluetooth]] for detailed information about using bluetooth and also for a list of supported devices.

====Pairing====

[[Emtooth]] is a bluetooth manager. It provides setting up bluetooth device name, pairing/unpairing, visibility setting and more. Install Emtooth:

opkg install emtooth2

It will discover nearby devices, double tapping on found device will initiate pairing process.

====GSM with bluetooth headset====

In order to use bluetooth headset for phone calls, several simple steps need to be done.

1). Your bluetooth headset device must be [[#Pairing | paired]] first.

2). [[#Configuring_FSO | Add]] your bluetooth headset into FSO configuration.

Please note: phonecalls are now always routed to the bluetooth headset.
After startup and after every resume, the headset needs to be [[#Re-Connecting_the_bluetooth_headset |reconnected]].

=====Configuring FSO=====

Now we must tell frameworkd that you have a bluetooth headset. Headset parameters should be set in

/etc/freesmartphone/opreferences/conf/phone/default.yaml

Parameters bt-headset-enabled and bt-headset-address (see opreferences/schema/phone.yaml for semantics).

You need to restart FSO for the changes to take effect.

# /etc/init.d/frameworkd restart

example of my /etc/freesmartphone/opreferences/conf/phone/default.yaml:

message-length: 7
message-tone: notify_message.wav
message-vibration: 1
message-volume: 10
ring-loop: 1
ring-tone: ringtone_ringnroll.wav
ring-vibration: 1
ring-volume: 10
bt-headset-enabled: 1
bt-headset-address: 00:09:DD:31:92:98

=====Re-Connecting the headset=====

You might need to get the bluetooth headset connected manually on the beginning and also after suspend:

mdbus -s org.bluez $BTADAPTER/dev_xx_xx_xx_xx_xx_xx org.bluez.Headset.Connect

where xx_xx_xx_xx_xx_xx is address of the device, for example:

mdbus -s org.bluez $BTADAPTER/dev_00_09_DD_31_92_98 org.bluez.Headset.Connect

Hopefully, your bluetooth headset now works. Good luck!

==System Customizing==

===Command scheduling===

The traditional ''at'' command in ''SHR'' is modified to work over dbus. This modified ''at_over_dbus'' will run scheduled task at required time - actually it will even automatically wake up the phone from suspend or start it if the phone was switched off.

To schedule a command to be executed at a particular time, one must:

Place commands in a script in ''/var/spool/at'' and name it like

TIMESTAMP.NAME.NUMBER

where

where TIMESTAMP is the seconds since 1970-01-01 00:00:00 UTC when the command should be run.
The rest (NAME, NUMBER) is up to you. Finally you have to:

touch /var/spool/at/trigger

Also, make sure to have atd running. You are responsible to remove the script when unnecessary. It will run once more if you/other program write to the trigger file during the execution, so you may consider removing the
executable flag of the script (if it is long running) or rename the script from within for example like this:

mv "$0" "x$0.$$"

===Installing splash screen themes===

List available splash screen themes

opkg list | grep splash-theme

Install one of the available themes

opkg install shr-splash-theme-dontpanic

Then go to '''SHR Settings -> Appearance -> Splash settings'''. Here you can preview installed themes and change the default one.

===Installing themes===

Every theme is made of several components (a theme for illume, theme for the phone applications, theme for etk and so on). There is a SHR metapackage for each theme that allows installing the complete theme in one go.

List available SHR theme metapackages:

opkg list | grep shr-theme

Install one of the available themes

opkg install shr-theme-gry

Then go to '''SHR Settings -> Appearance -> Elementary Settings'''. Here you can preview installed themes and choose the preferred one.

The Illume screen requires to change theme via '''Settings (SHR Logo) -> Look -> Theme'''. Here you can preview installed themes and choose the preferred one.

===Enable mouse cursor===

edit line 143 of /etc/X11/Xserver and erase '''-nocursor'''

ARGS="$ARGS"

===Random errors===
No icons, no GSM functions etc. happen mostly due to '''errors on your µSD''' card. Remove your card and fix it in card reader or by booting to another partition (nand) or by reboot and mount read only, then run fsck.

For reboot into nand and fix 1st partition of ext2 on your card

fsck.ext2 /dev/mmcblk0p1

===GSM modem 1024 suspend bug===

The calypso GSM modem suffers a known [[1024]] hardware bug that causes unreliable GSM function. To work around it, SHR by default doesn't suspend the modem completely. If you have undertaken a fix for this bug you can extend your battery time by enabling the modem to fully suspend when possible.

Edit the following in file:

For the new FSO2 edit /etc/freesmartphone/conf/GTA02/fsogsmd.conf

deep_sleep == "always"

Then kill fsogsmd and restart fsodeviced - or reboot the phone.

For old FSO (frameworks) edit /etc/frameworkd.conf

ti_calypso_deep_sleep = always

Then restart framework or reboot the phone.

==Reporting bugs==

SHR is a work in progress. If you experience issues, please report them back to SHR. With your report provide relevant logs from

/var/log/

To report a bug, please go to http://shr-project.org/trac/report

Check if the bug is already reported. If not, add a ticket, be as much precise as you can in the title and the description, in what circumstances the issue happened and so on. If bug already exists, see if you can help fixing it by providing some fresh info.

==More information==

For SHR home page, source code and other resources, visit:

* [http://trac.shr-project.org SHR Project Homepage]
* [http://blog.shr-project.org SHR Blog]
* [http://trac.shr-project.org Trac Bugtracker]
* [http://git.shr-project.org Git Sourcecode-repository]
* [http://build.shr-project.org Downloads on buildhost]
* [http://lists.shr-project.org SHR User and Development Mailing Lists]

==About this manual==

This manual makes use of the updated SHR-Unstable distribution which means that for example SHR-Testing or not updated SHR-Unstable might behave differently then stated in this manual.

Please help extending this manual by correcting typos or discussing proposals on the talk page or email <tt>vanous @ penguin . cz</tt>. Thank you.

[[Category:SHR]]
[[Category:Manuals]]

GTA04

2012-02-12T07:43:28Z

Glenn: /* GTA04A4 */ more about hardware

'''News:'''
* There is a new mailing list dedicated to the early adopters of this project: http://lists.goldelico.com/mailman/listinfo/gta04-owner
* general discussions should be continued on the Openmoko Community lists: http://lists.openmoko.org/mailman/listinfo/community

----

The codename '''GTA04''' was picked up in 2010 by Golden Delicious Computers to develop a new motherboard for our open smartphone that follows the original idea and goals.

There is a new project page: http://www.gta04.org, which houses the wiki specific to the GTA04 project at Golden Delicious.

== GTA04A4 ==

GTA04A4 is a new motherboard, that replaces the one inside your Neo 1971 ([[GTA01]]) or Neo Freerunner ([[GTA02]]). It reuses the case, the battery, the display, the antenna and speaker(s). GTA04 [http://projects.goldelico.com/p/gta04-main/page/FeatureList/ hardware features is here].

The GTA04A4 motherboard PCB layout development is based on GTA04A3 and its start was announced at [http://lists.goldelico.com/pipermail/gta04-owner/2011-October/000385.html 7 October 2011].

The replacement, populated GTA04, motherboard is available at [http://www.handheld-linux.com/wiki.php?page=GTA04 Golden Delicious]. A complete [http://www.handheld-linux.com/wiki.php?page=GTA04%20Complete OpenPhoenux aka GTA04 Complete can be bought here]

On [http://lists.goldelico.com/pipermail/gta04-owner/2011-November/000679.html 14th November 2011] GTA04A4 boards became available for (pre)order. [http://lists.goldelico.com/pipermail/gta04-owner/2012-January/001379.html First batch started shipment 31 January 2012].

== History ==

=== Year 2011: GTA04A3 (Early Adopter) ===
The GTA04A3 was released and shipped 10. october 2011.

The GTA04A3 milestone was announced 7. october 2011.([http://lists.goldelico.com/pipermail/gta04-owner/2011-October/000385.html source])

GTA04A3 is a new motherboard, that replaces the one inside your Neo Freerunner ([[GTA02]]). It reuses the case, the battery and the display.

Video:
* [http://www.youtube.com/watch?v=PgZzxmHzWtg GTA04A3 in a homemade box with Qtmoko installed]
* [http://www.youtube.com/watch?v=gCjM48BqfYo GTA04-Tester] Quote: "...This video shows the first 3 fresh GTA04A3 boards and how they are tested..."

The early adopter program [http://www.handheld-linux.com/wiki.php?page=GTA04-Early-Adopter was available here].

==== Specifications ====
GTA04A3 features ([http://projects.goldelico.com/p/gta04-main/page/Old-GTA04-revisions/ source]):

* [http://focus.ti.com/lit/ds/symlink/dm3730.pdf TI OMAP 3730] DCBB (800 MHz) (compatible to [http://www.beagleboard.org])
** integrated graphics - POWERVR SGX Graphics Accelerator of OMAP3730
* 512MB RAM/512MB NAND ([http://www.micron.com/products/ProductDetails.html?product=products/mcp/multichip_packages/MT29C4G96MAZAPCJG-5+IT Micron 8Gb DDR/NAND PoP Memory])
* Wi2Wi WLAN/Bluetooth module + antenna
* GTM601W UMTS module
* GPS module + antenna switch
* Option:
** LSM303 (compass and accelerometer)
** ITG3200 (gyroscope)
** BMP085 (barometric altimeter)
** BMA180 (LIS302 on a few) (accelerometer)
** Si4721 or Si4705 (FM transceiver/receiver)

=== Year 2010: GTA04A2 ===

The GTA04A2 was the result of integrating GTA04A1/[[Openmoko Beagle Hybrid]] all onto a single PCB.

GTA04A2 was presented at [http://en.wikipedia.org/wiki/FOSDEM FOSDEM] 2011.

Videos:
* [http://www.youtube.com/watch?v=3KnJc7eImQ4 booting GTA04A2].
* [http://www.youtube.com/watch?v=wG31rCHZXh4 Boot Speed Comparison] Quote: "...This video shows a comparison of a Openmoko GTA02 (with OM2009.05), a GTA04 board with Debian Squeeze/LXDE and a iPhone 3G..."

=== Year 2010: Openmoko Beagle Hybrid GTA04A1 ===
Golden Delicious Computers has been secretly working on a OMAP3530 based project that apparently has the same target as Openmoko's GTA04 did have. The first result was announced in 2010 [[Openmoko Beagle Hybrid]] aka GTA04A1.

Videos:
* [http://www.youtube.com/watch?v=Wuarto_s4F0 Openmoko Beagle Hybrid in operation]

=== Year 2008: Openmoko Inc. GTA04 ===
'''GTA04''' was the codename of a phone that was whose development was canceled (within Openmoko, Inc.). For more information about other phones in development, visit [[Phone Development]]. This phone would have been based on a different system-on-a-chip.

==== Specifications ====
The GTA04 would have been a [[GTA03]] but with a major hardware revision

New:
* USB 2.0 would be added on the GTA04 at the earliest
* 3G would be added on the GTA04 at the earliest
* Based on a more advanced SoC
* maybe based on the samsung 6400 or 6410
* integrated graphics
* Sean put a hiring on the community and devel list, see [http://lists.openmoko.org/pipermail/community/2008-September/029710.html here] so there will be OpenGL Es and the 6410 eventually
* there had been meetings in April 2008 within Openmoko - see [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-April/002310.html]

[[Category:GTA04| ]]

Community Updates/Draft

2012-02-12T06:47:51Z

Glenn: /* Firmware */ chg

{{Improve}}
{{Note|
*Take a moment and look at [[Talk:Community_Updates/Draft|this page]] to get a clue on how to contribute to Community Updates while following OM wiki editing guidelines please.
*I you are planning longer edition, please use <nowiki>{{Editing|your_username_here|date_here|editing_summary_here}}tag. Remember to remove/comment out it right after you save your work.</nowiki>
*Please fill in everything you think the community should know.
*On YYYY-MM-DD this content should be _moved_ to http://wiki.openmoko.org/wiki/Community_Updates/YYYY-MM-DD, feel free to do it.
*Post the CU release also on the community mailing list, since some people prefer to read news directly there. Regarding this, it helps copy-pasting from browser page to mailing list post if relevant URLs are included as is in addition to having linked parts of text (if in hurry you can also just post a note that CU is readable on web page).
}}



[[Image:Freethephone.png|right|250px]]
====='''Period YYYY-MM-DD to YYYY-MM-DD'''=====

Welcome to the YYYY-MM-DD edition of the Free The Phone / Openmoko Community Updates. We are a loosely bound group of people originating from the developers and users of the pioneering Neo1973 and Neo FreeRunner products from Openmoko Inc. Nowadays most efforts are around free software distributions for a range of mobile phones, including the original Neo products. There are also several spin-off companies inspired by the Openmoko Inc's work.

== Hardware ==

== Distributions ==

Distributions lists releases and other significant updates in distributions that have some support for the Openmoko devices.

{{DistributionBox|
Name=Distro Name [version]|
Description=Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.|
Screenshot=System_boot.png|
Codename='codename'|
Homepage=http://www.homepage.org|
Image=[http://www.homepage.org/path/to/ images]|
Works={{Works}}
}}

==Applications==

===New Applications===

{{ApplicationBox|
Name=Exampleapp 0.0.1|
Description=Exampleapp 0.0.1 is an application to do some stuff..|
Screenshot=System_boot.png|
Homepage=http://wiki.openmoko.org/|
TestedOn=SHR-Unstable,Om2009T5|
PackageName=[http:// www.some.srv/path_to/Exampleapp.ipk Exampleapp]
}}

===Application Updates===

{{ApplicationBox|
Name=Barom 0.8|
Description=Barom uses the BMP085 barometric pressures sensor to give altitude and weather info...
* now includes a configuration option to change the location of the pressure_input file (needed for GTA04)
* Fixed an intermittent segfault that led to crashes after 6-30 hours
* Program now starts if the BMP085 cannot be found
* Moved files around so it works with shr-core|
Screenshot=WeatherView.png|
Homepage=http://www.jeepingben.net/barom/|
TestedOn=SHR-Core|
PackageName=[http://www.jeepingben.net/barom/barom_0.8_all.ipk latest_package]
}}

{{ApplicationBox|
Name=Exampleapp 0.0.1|
Description=Exampleapp 0.0.1 is an application to do some stuff...
* new example feature 1
* new example feature 2|
Screenshot=System_boot.png|
Homepage=http://wiki.openmoko.org/|
TestedOn=SHR-Unstable,Om2009T5|
PackageName=[http:// www.some.srv/path_to/Exampleapp.ipk Exampleapp]
}}

==Firmware==
The Free Software / Open Source [[Osmocom on TI Calypso|Osmocom]] firmware has been ported to the TI Calypso GSM/GPRS modem. The TI Calypso, is among others, used in [[Neo 1973]] and [[Neo FreeRunner]].

==General News==

Most important and change making mails on the mailing lists, blogs etc.. Coolest hacks, screenshots, themes etc..

==Event News==

* '''2011-mm-dd''' [http://example.url.xom Example event] | add your event here

[[Category:Community Update]]

Community Updates/Draft

2012-02-12T06:47:23Z

Glenn: /* Firmware */ more

{{Improve}}
{{Note|
*Take a moment and look at [[Talk:Community_Updates/Draft|this page]] to get a clue on how to contribute to Community Updates while following OM wiki editing guidelines please.
*I you are planning longer edition, please use <nowiki>{{Editing|your_username_here|date_here|editing_summary_here}}tag. Remember to remove/comment out it right after you save your work.</nowiki>
*Please fill in everything you think the community should know.
*On YYYY-MM-DD this content should be _moved_ to http://wiki.openmoko.org/wiki/Community_Updates/YYYY-MM-DD, feel free to do it.
*Post the CU release also on the community mailing list, since some people prefer to read news directly there. Regarding this, it helps copy-pasting from browser page to mailing list post if relevant URLs are included as is in addition to having linked parts of text (if in hurry you can also just post a note that CU is readable on web page).
}}



[[Image:Freethephone.png|right|250px]]
====='''Period YYYY-MM-DD to YYYY-MM-DD'''=====

Welcome to the YYYY-MM-DD edition of the Free The Phone / Openmoko Community Updates. We are a loosely bound group of people originating from the developers and users of the pioneering Neo1973 and Neo FreeRunner products from Openmoko Inc. Nowadays most efforts are around free software distributions for a range of mobile phones, including the original Neo products. There are also several spin-off companies inspired by the Openmoko Inc's work.

== Hardware ==

== Distributions ==

Distributions lists releases and other significant updates in distributions that have some support for the Openmoko devices.

{{DistributionBox|
Name=Distro Name [version]|
Description=Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.|
Screenshot=System_boot.png|
Codename='codename'|
Homepage=http://www.homepage.org|
Image=[http://www.homepage.org/path/to/ images]|
Works={{Works}}
}}

==Applications==

===New Applications===

{{ApplicationBox|
Name=Exampleapp 0.0.1|
Description=Exampleapp 0.0.1 is an application to do some stuff..|
Screenshot=System_boot.png|
Homepage=http://wiki.openmoko.org/|
TestedOn=SHR-Unstable,Om2009T5|
PackageName=[http:// www.some.srv/path_to/Exampleapp.ipk Exampleapp]
}}

===Application Updates===

{{ApplicationBox|
Name=Barom 0.8|
Description=Barom uses the BMP085 barometric pressures sensor to give altitude and weather info...
* now includes a configuration option to change the location of the pressure_input file (needed for GTA04)
* Fixed an intermittent segfault that led to crashes after 6-30 hours
* Program now starts if the BMP085 cannot be found
* Moved files around so it works with shr-core|
Screenshot=WeatherView.png|
Homepage=http://www.jeepingben.net/barom/|
TestedOn=SHR-Core|
PackageName=[http://www.jeepingben.net/barom/barom_0.8_all.ipk latest_package]
}}

{{ApplicationBox|
Name=Exampleapp 0.0.1|
Description=Exampleapp 0.0.1 is an application to do some stuff...
* new example feature 1
* new example feature 2|
Screenshot=System_boot.png|
Homepage=http://wiki.openmoko.org/|
TestedOn=SHR-Unstable,Om2009T5|
PackageName=[http:// www.some.srv/path_to/Exampleapp.ipk Exampleapp]
}}

==Firmware==
The Free Software / Open Source [[Osmocom on TI Calypso|Osmocom]] firmware has been ported to TI Calypso GSM/GPRS modem. The TI Calypso, is among others, used in [[Neo 1973]] and [[Neo FreeRunner]].

==General News==

Most important and change making mails on the mailing lists, blogs etc.. Coolest hacks, screenshots, themes etc..

==Event News==

* '''2011-mm-dd''' [http://example.url.xom Example event] | add your event here

[[Category:Community Update]]

Osmocom on TI Calypso

2012-02-12T06:46:45Z

Glenn: more

The Free Software / Open Source '''Osmocom firmware''' has been ported/made for the [[TI Calypso D751992AZHH|TI Calypso GSM/GPRS modem]]. The TI Calypso, is among others, used in [[Neo 1973]] and [[Neo FreeRunner]].

More information:
* http://bb.osmocom.org/trac/wiki/OpenMoko
* http://bb.osmocom.org/trac/wiki/WikiStart
* Main page: http://osmocom.org/

[[Category:GSM]]

Community Updates/Draft

2012-02-12T06:39:40Z

Glenn: +about Osmocom on TI Calypso (Neo 1973, Neo FreeRunner)

{{Improve}}
{{Note|
*Take a moment and look at [[Talk:Community_Updates/Draft|this page]] to get a clue on how to contribute to Community Updates while following OM wiki editing guidelines please.
*I you are planning longer edition, please use <nowiki>{{Editing|your_username_here|date_here|editing_summary_here}}tag. Remember to remove/comment out it right after you save your work.</nowiki>
*Please fill in everything you think the community should know.
*On YYYY-MM-DD this content should be _moved_ to http://wiki.openmoko.org/wiki/Community_Updates/YYYY-MM-DD, feel free to do it.
*Post the CU release also on the community mailing list, since some people prefer to read news directly there. Regarding this, it helps copy-pasting from browser page to mailing list post if relevant URLs are included as is in addition to having linked parts of text (if in hurry you can also just post a note that CU is readable on web page).
}}



[[Image:Freethephone.png|right|250px]]
====='''Period YYYY-MM-DD to YYYY-MM-DD'''=====

Welcome to the YYYY-MM-DD edition of the Free The Phone / Openmoko Community Updates. We are a loosely bound group of people originating from the developers and users of the pioneering Neo1973 and Neo FreeRunner products from Openmoko Inc. Nowadays most efforts are around free software distributions for a range of mobile phones, including the original Neo products. There are also several spin-off companies inspired by the Openmoko Inc's work.

== Hardware ==

== Distributions ==

Distributions lists releases and other significant updates in distributions that have some support for the Openmoko devices.

{{DistributionBox|
Name=Distro Name [version]|
Description=Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.|
Screenshot=System_boot.png|
Codename='codename'|
Homepage=http://www.homepage.org|
Image=[http://www.homepage.org/path/to/ images]|
Works={{Works}}
}}

==Applications==

===New Applications===

{{ApplicationBox|
Name=Exampleapp 0.0.1|
Description=Exampleapp 0.0.1 is an application to do some stuff..|
Screenshot=System_boot.png|
Homepage=http://wiki.openmoko.org/|
TestedOn=SHR-Unstable,Om2009T5|
PackageName=[http:// www.some.srv/path_to/Exampleapp.ipk Exampleapp]
}}

===Application Updates===

{{ApplicationBox|
Name=Barom 0.8|
Description=Barom uses the BMP085 barometric pressures sensor to give altitude and weather info...
* now includes a configuration option to change the location of the pressure_input file (needed for GTA04)
* Fixed an intermittent segfault that led to crashes after 6-30 hours
* Program now starts if the BMP085 cannot be found
* Moved files around so it works with shr-core|
Screenshot=WeatherView.png|
Homepage=http://www.jeepingben.net/barom/|
TestedOn=SHR-Core|
PackageName=[http://www.jeepingben.net/barom/barom_0.8_all.ipk latest_package]
}}

{{ApplicationBox|
Name=Exampleapp 0.0.1|
Description=Exampleapp 0.0.1 is an application to do some stuff...
* new example feature 1
* new example feature 2|
Screenshot=System_boot.png|
Homepage=http://wiki.openmoko.org/|
TestedOn=SHR-Unstable,Om2009T5|
PackageName=[http:// www.some.srv/path_to/Exampleapp.ipk Exampleapp]
}}

==Firmware==
[[Osmocom on TI Calypso|Osmocom]] has been ported to TI Calypso GSM/GPRS modem. The TI Calypso, is among others, used in [[Neo 1973]] and [[Neo FreeRunner]].

==General News==

Most important and change making mails on the mailing lists, blogs etc.. Coolest hacks, screenshots, themes etc..

==Event News==

* '''2011-mm-dd''' [http://example.url.xom Example event] | add your event here

[[Category:Community Update]]