Openmoko - User contributions [en]

QtMoko/eu

2010-06-14T22:19:08Z

Joseba:

{{Languages|QtMoko}}
QtMoko [[Neo FreeRunner]] gailuarentzat sortutako eta [[Debian]]en oinarritutakobanaketa da. Erabiltzailearen interfazea eta telefonoa [[Qt Extended Improved]] edota [[Qtopia / Qt Extended on FreeRunner|Qtopia]] banaketan oinarrituta dago. Bere [http://qtmoko.org/ wikia] ikus dezakezu.

===Download===
Hasteko, zure mahaigaineko ordenagailura eraman fitxategiak, [https://sourceforge.net/projects/qtmoko/files/ radekp download] gunean aurkituko dituzu:
* azkena
** https://sourceforge.net/projects/qtmoko/files/

===Instalazioa===
QtMokoren irudia FreeRunnerraren memorian ezarri (flasheatu) nahi baduzu, bi gauza flasheatu behar dituzu, alde batetik sistemaren kernela, eta bestetik, fitxategi sistema nagusia. Abiarazle moduan [[Qi]] sistema instalatuta baldin badaukazu, QtMoko banaketa mikroSD txartel batean ere instala daiteke. Horrela, aurreko sistema mantenduz sistema berria ere eskura eduki dezakezu. Edota, SD txartela aldatuz sistema asko eduki daitezke. Instalazioa hasteko, banaketa flasheatzeko asmoa baduzu, U-boot menua atera behar da, alegia, FreeRunnerra era berezian piztu behar da, horretarako, lehendabizi itzali FreeRunnerra, eta ondoren AUX botoia sakatuta daukazun bitartean pizteko botoia sakatu behar duzu. FreeRunnerrak honako U-Boot menua aterako du:

*** BOOT MENU (NOR) ***

Boot
Boot from Mirco SD (FAT/ext2)
Set Console to USB
Set Console to Serial
Reboot
Power Off

Egoera horretan 30 segundu iraungo du, Ezer egiten ez baduzu ohi bezala abiatuko da. Menuko aukera bat ala bestea hartzeko AUX botoia erabil daiteke. Egin beharrekoa honakoa da, hasteko, Set Console to USB aukeratu behar da, horrela, USB konexioa erabiliz mahaigaineko ordenagailu batetik FreeRunnerra kontrolatu ahal izango duzu. Mahaigaineko ordenagailuan root eskubideak beharko dituzu, eta gainera, <tt>dfu-util</tt> aplikazioa instalatuta eduki behar duzu. Gainera, ordenagailuan bertan eduki behar dituzu kernela (uImage-bertsioa.bin) eta root fitxategi sistema (qtmoko-debian-bertsioa.jffs2). 30 segundu horietan <tt>dfu-util</tt> agindua exekutatu behar duzu, eta hainbat parametro pasa behar zaizkio. Neo FreeRunner batean kernela flasheatu nahi baduzu honako agindua exekutatu behar duzu ordenagailuan (betiere FreeRunnerrak USB bidez konektatuta egon behar du ordenagailura):

sudo dfu-util -a kernel -R -D uImage-bertsioa.bin

Agindu horren ordez osotuagoa ere erabili daiteke, izan ere gailua ere zehaztu baitezakegu aginduan, gure kasuan NeoFreeRunnerra denez:

sudo dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-bertsioa.bin

Ondoren fitxategi sistemaren erroa ere flasheatu beharko dugu, eta horretarako, honako agindua behar dugu:

sudo dfu-util -a rootfs -R -D qtmoko-debian-bertsioa.jffs2

Berriz ere, gailua adierazi nahi izan ezkero beste aukera hau erabil daiteke:

sudo dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D qtmoko-debian-bertsioa.jffs2

===Lehenengo abiaraztea===
Instalazioaren ondoren (errorerik gabeko instalazioaren ondoren) FreeRunnerra abiarazi behar da. Abiarazitakoan pantaila taktila kalibratzeko eskatuko du. Diana modukoa batzuen gaineak ukitzeko eskatuko digu, eta azkenik instalatu duzun QtMoko banaketa ikusiko duzu zure gailuan.
[[Image:qtmokomain.png|200px|thumb|QtMoko instalatu berria]]

===Login===
FreeRunnerrean login bidez konektatzeko, USB-kable bidezko sare-konexioa erabil daiteke (ikusi [[USB Networking|USB sare konexioa]]), horrela zure ordenagailutik ssh bidez konexioa ezer dezakezu freeRunnerrera honako agindua erabiliz:

desktop# ssh -X -l root 192.168.0.202

FreeRunnerreko root erabiltzaileak ez dauka pasahitzik, beraz, ez dizu pasahitzik eskatuko. Baina, segurtasunagatik komeni da root erabiltzaileari pasahitza jartzea, batez ere WLAN sare interfazean ssh-deabrua abiarazten duzunean. Pasahitza ezartzeko, ssh konexioa egin ondoren, edozein linux makinetan bezala,<tt> passwd</tt> agindua exekutatu behar da:
neo# passwd
USB kablearen bidez internet konexioa ezarri baduzu biltegietako datuak eguneratzea komeni da, horretarako:
neo# apt-get update
Internet konexioa ba ote dabilen ikusteko, zure FreeRunnerretik OpenMoko web zerbitzariari ping egin diezaiokezu:
neo# ping 88.198.93.221
neo# ping wiki.openmoko.org
Lehenengoa ondo badabil baina bigarrena ez, orduan DNS zerbitzaria gaizki dabilkizu.(ikusi [[USB Networking]]).

===Ordua eta data ezartzea===
Zure ordenagailutik ezar ditzakezu ordua eta data, horretarako:
<pre>
ssh root@openmoko "date -fr @`date -u +%s`"
</pre>
NTP Bezero baten bidez ezarri nahi badituzu, instalatu ondoko paketea (sare konexioa edukiz gero, jakina) (ikusi [[USB Networking]])
<pre>
# apt-get install ntpdate
# ntpdate-debian
</pre>
Informazio gehiago [[Setting Date and Time|data eta orduaren ezarpena]].

[[Category:Qt Moko| ]]

QtMoko/eu

2010-06-14T22:16:40Z

Joseba:

{{Languages|QtMoko}}
QtMoko [[Neo FreeRunner]] gailuarentzat sortutako eta [[Debian]]en oinarritutakobanaketa da. Erabiltzailearen interfazea eta telefonoa [[Qt Extended Improved]] edota [[Qtopia / Qt Extended on FreeRunner|Qtopia]] banaketan oinarrituta dago. Bere [http://qtmoko.org/ wikia] ikus dezakezu.

===Download===
Hasteko, zure mahaigaineko ordenagailura eraman fitxategiak, [https://sourceforge.net/projects/qtmoko/files/ radekp download] gunean aurkituko dituzu:
* azkena
** https://sourceforge.net/projects/qtmoko/files/

===Instalazioa===
QtMokoren irudia FreeRunnerraren memorian ezarri (flasheatu) nahi baduzu, bi gauza flasheatu behar dituzu, alde batetik sistemaren kernela, eta bestetik, fitxategi sistema nagusia. Abiarazle moduan [[Qi]] sistema instalatuta baldin badaukazu, QtMoko banaketa mikroSD txartel batean ere instala daiteke. Horrela, aurreko sistema mantenduz sistema berria ere eskura eduki dezakezu. Edota, SD txartela aldatuz sistema asko eduki daitezke. Instalazioa hasteko, banaketa flasheatzeko asmoa baduzu, U-boot menua atera behar da, alegia, FreeRunnerra era berezian piztu behar da, horretarako, lehendabizi itzali FreeRunnerra, eta ondoren AUX botoia sakatuta daukazun bitartean pizteko botoia sakatu behar duzu. FreeRunnerrak honako U-Boot menua aterako du:

*** BOOT MENU (NOR) ***

Boot
Boot from Mirco SD (FAT/ext2)
Set Console to USB
Set Console to Serial
Reboot
Power Off

Egoera horretan 30 segundu iraungo du, Ezer egiten ez baduzu ohi bezala abiatuko da. Menuko aukera bat ala bestea hartzeko AUX botoia erabil daiteke. Egin beharrekoa honakoa da, hasteko, Set Console to USB aukeratu behar da, horrela, USB konexioa erabiliz mahaigaineko ordenagailu batetik FreeRunnerra kontrolatu ahal izango duzu. Mahaigaineko ordenagailuan root eskubideak beharko dituzu, eta gainera, <tt>dfu-util</tt> aplikazioa instalatuta eduki behar duzu. Gainera, ordenagailuan bertan eduki behar dituzu kernela (uImage-bertsioa.bin) eta root fitxategi sistema (qtmoko-debian-bertsioa.jffs2). 30 segundu horietan <tt>dfu-util</tt> agindua exekutatu behar duzu, eta hainbat parametro pasa behar zaizkio. Neo FreeRunner batean kernela flasheatu nahi baduzu honako agindua exekutatu behar duzu ordenagailuan (betiere FreeRunnerrak USB bidez konektatuta egon behar du ordenagailura):

sudo dfu-util -a kernel -R -D uImage-bertsioa.bin

Agindu horren ordez osotuagoa ere erabili daiteke, izan ere gailua ere zehaztu baitezakegu aginduan, gure kasuan NeoFreeRunnerra denez:

sudo dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-bertsioa.bin

Ondoren fitxategi sistemaren erroa ere flasheatu beharko dugu, eta horretarako, honako agindua behar dugu:

sudo dfu-util -a rootfs -R -D qtmoko-debian-bertsioa.jffs2

Berriz ere, gailua adierazi nahi izan ezkero beste aukera hau erabil daiteke:

sudo dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D qtmoko-debian-bertsioa.jffs2

===Lehenengo abiaraztea===
Instalazioaren ondoren (errorerik gabeko instalazioaren ondoren) FreeRunnerra abiarazi behar da. Abiarazitakoan pantaila taktila kalibratzeko eskatuko du. Diana modukoa batzuen gaineak ukitzeko eskatuko digu, eta azkenik instalatu duzun QtMoko banaketa ikusiko duzu zure gailuan.
[[Image:qtmokomain.png|200px|thumb|QtMoko after first boot]]

===Login===
FreeRunnerrean login bidez konektatzeko, USB-kable bidezko sare-konexioa erabil daiteke (ikusi [[USB Networking|USB sare konexioa]]), horrela zure ordenagailutik ssh bidez konexioa ezer dezakezu freeRunnerrera honako agindua erabiliz:

desktop# ssh -X -l root 192.168.0.202

FreeRunnerreko root erabiltzaileak ez dauka pasahitzik, beraz, ez dizu pasahitzik eskatuko. Baina, segurtasunagatik komeni da root erabiltzaileari pasahitza jartzea, batez ere WLAN sare interfazean ssh-deabrua abiarazten duzunean. Pasahitza ezartzeko, ssh konexioa egin ondoren, edozein linux makinetan bezala,<tt> passwd</tt> agindua exekutatu behar da:
neo# passwd
USB kablearen bidez internet konexioa ezarri baduzu biltegietako datuak eguneratzea komeni da, horretarako:
neo# apt-get update
Internet konexioa ba ote dabilen ikusteko, zure FreeRunnerretik OpenMoko web zerbitzariari ping egin diezaiokezu:
neo# ping 88.198.93.221
neo# ping wiki.openmoko.org
Lehenengoa ondo badabil baina bigarrena ez, orduan DNS zerbitzaria gaizki dabilkizu.(ikusi [[USB Networking]]).

===Ordua eta data ezartzea===
Zure ordenagailutik ezar ditzakezu ordua eta data, horretarako:
<pre>
ssh root@openmoko "date -fr @`date -u +%s`"
</pre>
NTP Bezero baten bidez ezarri nahi badituzu, instalatu ondoko paketea (sare konexioa edukiz gero, jakina) (ikusi [[USB Networking]])
<pre>
# apt-get install ntpdate
# ntpdate-debian
</pre>
Informazio gehiago [[Setting Date and Time|data eta orduaren ezarpena]].

[[Category:Qt Moko| ]]

QtMoko/eu

2010-06-14T22:13:06Z

Joseba:

{{Languages|QtMoko}}
QtMoko [[Neo FreeRunner]] gailuarentzat sortutako eta [[Debian]]en oinarritutakobanaketa da. Erabiltzailearen interfazea eta telefonoa [[Qt Extended Improved]] edota [[Qtopia / Qt Extended on FreeRunner|Qtopia]] banaketan oinarrituta dago. Bere [http://qtmoko.org/ wikia] ikus dezakezu.

===Download===
Hasteko, zure mahaigaineko ordenagailura eraman fitxategiak, [https://sourceforge.net/projects/qtmoko/files/ radekp download] gunean aurkituko dituzu:
* azkena
** https://sourceforge.net/projects/qtmoko/files/

===Instalazioa===
QtMokoren irudia FreeRunnerraren memorian ezarri (flasheatu) nahi baduzu, bi gauza flasheatu behar dituzu, alde batetik sistemaren kernela, eta bestetik, fitxategi sistema nagusia. Abiarazle moduan [[Qi]] sistema instalatuta baldin badaukazu, QtMoko banaketa mikroSD txartel batean ere instala daiteke. Horrela, aurreko sistema mantenduz sistema berria ere eskura eduki dezakezu. Edota, SD txartela aldatuz sistema asko eduki daitezke. Instalazioa hasteko, banaketa flasheatzeko asmoa baduzu, U-boot menua atera behar da, alegia, FreeRunnerra era berezian piztu behar da, horretarako, lehendabizi itzali FreeRunnerra, eta ondoren AUX botoia sakatuta daukazun bitartean pizteko botoia sakatu behar duzu. FreeRunnerrak honako U-Boot menua aterako du:

*** BOOT MENU (NOR) ***

Boot
Boot from Mirco SD (FAT/ext2)
Set Console to USB
Set Console to Serial
Reboot
Power Off

Egoera horretan 30 segundu iraungo du, Ezer egiten ez baduzu ohi bezala abiatuko da. Menuko aukera bat ala bestea hartzeko AUX botoia erabil daiteke. Egin beharrekoa honakoa da, hasteko, Set Console to USB aukeratu behar da, horrela, USB konexioa erabiliz mahaigaineko ordenagailu batetik FreeRunnerra kontrolatu ahal izango duzu. Mahaigaineko ordenagailuan root eskubideak beharko dituzu, eta gainera, <tt>dfu-util</tt> aplikazioa instalatuta eduki behar duzu. Gainera, ordenagailuan bertan eduki behar dituzu kernela (uImage-bertsioa.bin) eta root fitxategi sistema (qtmoko-debian-bertsioa.jffs2). 30 segundu horietan <tt>dfu-util</tt> agindua exekutatu behar duzu, eta hainbat parametro pasa behar zaizkio. Neo FreeRunner batean kernela flasheatu nahi baduzu honako agindua exekutatu behar duzu ordenagailuan (betiere FreeRunnerrak USB bidez konektatuta egon behar du ordenagailura):

sudo dfu-util -a kernel -R -D uImage-bertsioa.bin

Agindu horren ordez osotuagoa ere erabili daiteke, izan ere gailua ere zehaztu baitezakegu aginduan, gure kasuan NeoFreeRunnerra denez:

sudo dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-bertsioa.bin

Ondoren fitxategi sistemaren erroa ere flasheatu beharko dugu, eta horretarako, honako agindua behar dugu:

sudo dfu-util -a rootfs -R -D qtmoko-debian-bertsioa.jffs2

Berriz ere, gailua adierazi nahi izan ezkero beste aukera hau erabil daiteke:

sudo dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D qtmoko-debian-bertsioa.jffs2

===Lehenengo abiaraztea===
Instalazioaren ondoren (errorerik gabeko instalazioaren ondoren) FreeRunnerra abiarazi behar da. Abiarazitakoan pantaila taktila kalibratzeko eskatuko du. Diana modukoa batzuen gaineak ukitzeko eskatuko digu, eta azkenik instalatu duzun QtMoko banaketa ikusiko duzu zure gailuan.
[[Image:qtmokomain.png|200px|thumb|QtMoko after first boot]]

===Login===
FreeRunnerrean login bidez konektatzeko, USB-kable bidezko sare-konexioa erabil daiteke (ikusi [[USB Networking|USB sare konexioa]]), horrela zure ordenagailutik ssh bidez konexioa ezer dezakezu freeRunnerrera honako agindua erabiliz:

desktop# ssh -X -l root 192.168.0.202

FreeRunnerrko root erabiltzaileak ez dauka pasahitzik, beraz, ez dizu pasahitzik eskatuko. Baina, segurtasunagatik komeni da root erabiltzaileari pasahitza jartzea, batez ere WLAN sare interfazean ssh-deabrua abiarazten duzunean. Pasahitza ezartzeko, ssh konexioa egin ondoren, edozein linuxe makinetan bezala,<tt> passwd</tt> agindua exekutatu behar da:
neo# passwd
USB kablearen bidez internet konexioa ezarri baduzu biltegietako datuak eguneratzea komeni da, horretarako:
neo# apt-get update
Internet konexioa ba ote dabilen ikusteko, zure FreeRunnerreanOpenMoko web zerbitzariari ping egin diezaiokezu:
neo# ping 88.198.93.221
neo# ping wiki.openmoko.org
Lehenengoa ondo badabil baina bigarrena ez, orduan DNS zerbitzaria gaizki dabilkizu.(ikusi [[USB Networking]]).

===Ordua eta data ezartzea===
Zure ordenagailutik ezar ditzakezu ordua eta data, horretarako:
<pre>
ssh root@openmoko "date -fr @`date -u +%s`"
</pre>
NTP Bezero baten bidez ezarri nahi badituzu, instalatu ondoko paketea (sare konexioa edukiz gero, jakina) (ikusi [[USB Networking]])
<pre>
# apt-get install ntpdate
# ntpdate-debian
</pre>
Informazio gehiago [[Setting Date and Time|data eta orduaren ezarpena]].

[[Category:Qt Moko| ]]

QtMoko/eu

2010-06-14T22:04:06Z

Joseba:

{{Languages}}
QtMoko [[Neo FreeRunner]] gailuarentzat sortutako eta [[Debian]]en oinarritutakobanaketa da. Erabiltzailearen interfazea eta telefonoa [[Qt Extended Improved]] edota [[Qtopia / Qt Extended on FreeRunner|Qtopia]] banaketan oinarrituta dago. Bere [http://qtmoko.org/ wikia] ikus dezakezu.

===Download===
Hasteko, zure mahaigaineko ordenagailura eraman fitxategiak, [https://sourceforge.net/projects/qtmoko/files/ radekp download] gunean aurkituko dituzu:
* azkena
** https://sourceforge.net/projects/qtmoko/files/

===Instalazioa===
QtMokoren irudia FreeRunnerraren memorian ezarri (flasheatu) nahi baduzu, bi gauza flasheatu behar dituzu, alde batetik sistemaren kernela, eta bestetik, fitxategi sistema nagusia. Abiarazle moduan [[Qi]] sistema instalatuta baldin badaukazu, QtMoko banaketa mikroSD txartel batean ere instala daiteke. Horrela, aurreko sistema mantenduz sistema berria ere eskura eduki dezakezu. Edota, SD txartela aldatuz sistema asko eduki daitezke. Instalazioa hasteko, banaketa flasheatzeko asmoa baduzu, U-boot menua atera behar da, alegia, FreeRunnerra era berezian piztu behar da, horretarako, lehendabizi itzali FreeRunnerra, eta ondoren AUX botoia sakatuta daukazun bitartean pizteko botoia sakatu behar duzu. FreeRunnerrak honako U-Boot menua aterako du:

*** BOOT MENU (NOR) ***

Boot
Boot from Mirco SD (FAT/ext2)
Set Console to USB
Set Console to Serial
Reboot
Power Off

Egoera horretan 30 segundu iraungo du, Ezer egiten ez baduzu ohi bezala abiatuko da. Menuko aukera bat ala bestea hartzeko AUX botoia erabil daiteke. Egin beharrekoa honakoa da, hasteko, Set Console to USB aukeratu behar da, horrela, USB konexioa erabiliz mahaigaineko ordenagailu batetik FreeRunnerra kontrolatu ahal izango duzu. Mahaigaineko ordenagailuan root eskubideak beharko dituzu, eta gainera, <tt>dfu-util</tt> aplikazioa instalatuta eduki behar duzu. Gainera, ordenagailuan bertan eduki behar dituzu kernela (uImage-bertsioa.bin) eta root fitxategi sistema (qtmoko-debian-bertsioa.jffs2). 30 segundu horietan <tt>dfu-util</tt> agindua exekutatu behar duzu, eta hainbat parametro pasa behar zaizkio. Neo FreeRunner batean kernela flasheatu nahi baduzu honako agindua exekutatu behar duzu ordenagailuan (betiere FreeRunnerrak USB bidez konektatuta egon behar du ordenagailura):

sudo dfu-util -a kernel -R -D uImage-bertsioa.bin

Agindu horren ordez osotuagoa ere erabili daiteke, izan ere gailua ere zehaztu baitezakegu aginduan, gure kasuan NeoFreeRunnerra denez:

sudo dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-bertsioa.bin

Ondoren fitxategi sistemaren erroa ere flasheatu beharko dugu, eta horretarako, honako agindua behar dugu:

sudo dfu-util -a rootfs -R -D qtmoko-debian-bertsioa.jffs2

Berriz ere, gailua adierazi nahi izan ezkero beste aukera hau erabil daiteke:

sudo dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D qtmoko-debian-bertsioa.jffs2

===Lehenengo abiaraztea===
Instalazioaren ondoren (errorerik gabeko instalazioaren ondoren) FreeRunnerra abiarazi behar da. Abiarazitakoan pantaila taktila kalibratzeko eskatuko du. Diana modukoa batzuen gaineak ukitzeko eskatuko digu, eta azkenik instalatu duzun QtMoko banaketa ikusiko duzu zure gailuan.
[[Image:qtmokomain.png|200px|thumb|QtMoko after first boot]]

===Login===
FreeRunnerrean login bidez konektatzeko, USB-kable bidezko sare-konexioa erabil daiteke (ikusi [[USB Networking|USB sare konexioa]]), horrela zure ordenagailutik ssh bidez konexioa ezer dezakezu freeRunnerrera honako agindua erabiliz:

desktop# ssh -X -l root 192.168.0.202

FreeRunnerrko root erabiltzaileak ez dauka pasahitzik, beraz, ez dizu pasahitzik eskatuko. Baina, segurtasunagatik komeni da root erabiltzaileari pasahitza jartzea, batez ere WLAN sare interfazean ssh-deabrua abiarazten duzunean. Pasahitza ezartzeko, ssh konexioa egin ondoren, edozein linuxe makinetan bezala,<tt> passwd</tt> agindua exekutatu behar da:
neo# passwd
USB kablearen bidez internet konexioa ezarri baduzu biltegietako datuak eguneratzea komeni da, horretarako:
neo# apt-get update
Internet konexioa ba ote dabilen ikusteko, zure FreeRunnerreanOpenMoko web zerbitzariari ping egin diezaiokezu:
neo# ping 88.198.93.221
neo# ping wiki.openmoko.org
Lehenengoa ondo badabil baina bigarrena ez, orduan DNS zerbitzaria gaizki dabilkizu.(ikusi [[USB Networking]]).

===Ordua eta data ezartzea===
Zure ordenagailutik ezar ditzakezu ordua eta data, horretarako:
<pre>
ssh root@openmoko "date -fr @`date -u +%s`"
</pre>
NTP Bezero baten bidez ezarri nahi badituzu, instalatu ondoko paketea (sare konexioa edukiz gero, jakina) (ikusi [[USB Networking]])
<pre>
# apt-get install ntpdate
# ntpdate-debian
</pre>
Informazio gehiago [[Setting Date and Time|data eta orduaren ezarpena]].

[[Category:Qt Moko| ]]

QtMoko/eu

2010-06-14T21:18:32Z

Joseba:

{{Languages}}
QtMoko [[Neo FreeRunner]] gailuarentzat sortutako eta [[Debian]]en oinarritutakobanaketa da. Erabiltzailearen interfazea eta telefonoa [[Qt Extended Improved]] edota [[Qtopia / Qt Extended on FreeRunner|Qtopia]] banaketan oinarrituta dago. Bere [http://qtmoko.org/ wikia] ikus dezakezu.

===Download===
Hasteko, zure mahaigaineko ordenagailura eraman fitxategiak, [https://sourceforge.net/projects/qtmoko/files/ radekp download] gunean aurkituko dituzu:
* azkena
** https://sourceforge.net/projects/qtmoko/files/

===Instalazioa===
QtMokoren irudia FreeRunnerraren memorian ezarri (flasheatu) nahi baduzu, bi gauza flasheatu behar dituzu, alde batetik sistemaren kernela, eta bestetik, fitxategi sistema nagusia. Abiarazle moduan [[Qi]] sistema instalatuta baldin badaukazu, QtMoko banaketa mikroSD txartel batean ere instala daiteke. Horrela, aurreko sistema mantenduz sistema berria ere eskura eduki dezakezu. Edota, SD txartela aldatuz sistema asko eduki daitezke. Instalazioa hasteko, banaketa flasheatzeko asmoa baduzu, U-boot menua atera behar da, alegia, FreeRunnerra era berezian piztu behar da, horretarako, lehendabizi itzali FreeRunnerra, eta ondoren AUX botoia sakatuta daukazun bitartean pizteko botoia sakatu behar duzu. FreeRunnerrak honako U-Boot menua aterako du:

*** BOOT MENU (NOR) ***

Boot
Boot from Mirco SD (FAT/ext2)
Set Console to USB
Set Console to Serial
Reboot
Power Off

Egoera horretan 30 segundu iraungo du, Ezer egiten ez baduzu ohiko abiaratzea egingo du. Menuko aukera bat ala bestea hartzeko AUX botoia erabil daiteke. The FreeRunner will stay in this mode for only 30 sec. Within this time you have to start <tt>dfu-util</tt>. If you want to flash the kernel image (you will need to be root on your PC) then you have to start the following command in the 30sec your see the BOOT MENU:

# for the Neo FreeRunner:
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-v13.bin

and finally the root fs with this one:

# for the Neo FreeRunner:
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D qtmoko-debian-v13.jffs2

===First Boot===
After finishing the installation without errors you have to start the FreeRunner and calibrate the touch screen. The you see the installed ''QtMoko'' on your device.
[[Image:qtmokomain.png|200px|thumb|QtMoko after first boot]]

===Login===
If you want to login to your FreeRunner set up a network connection (see [[USB Networking]]) with USB cable and start:
desktop# ssh -X -l root 192.168.0.202

The root password is empty so set it for security reason especially when you open the ssh-daemon on the WLAN network interface. Define root password as usual on a linux box with
neo# passwd
If you have established the internet connection via USB cable then update the repository data:
neo# apt-get update
If you want to check if the internet connection is available on your freerunner ping the OpenMoko web server with:
neo# ping 88.198.93.221
neo# ping wiki.openmoko.org
If the first ping works and the second doesn't then check the DNS server settings (see [[USB Networking]]).

===Setting Time and Date===
Set the time and date on from your linux box with
<pre>
ssh root@openmoko "date -us @`date -u +%s`"
</pre>
If you want to set the time with a NTP Client install the following package, if you have a network connection available (see [[USB Networking]])
<pre>
# apt-get install ntpdate
# ntpdate-debian
</pre>
For further detail see [[Setting Date and Time]].

[[Category:Qt Moko| ]]

QtMoko/eu

2010-06-11T18:20:53Z

Joseba: New page: {{Languages}} QtMoko Neo FreeRunner gailuarentzat sortutako eta Debianen oinarritutakobanaketa da. Erabiltzailearen interfazea eta telefonoa Qt Extended Improved edota [[Qtopi...

Distributions/eu

2010-06-11T18:07:23Z

Joseba:

{{Languages|Distributions}}

{|align=right
|__TOC__
|}
{| class="wikitable" style="float:left;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|<font color=white>Distributions</font>
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* <font color='#BBBBBB'>Openmoko (official)</font>
** [[Om 2009]]
** [[Om 2008]]
** [[Om 2007.2]]
* <font color='#BBBBBB'>Om Community</font>
** [[Android]]
** [[Debian]]
** [[Qt Extended Improved]]
** [[QtMoko]]
** [[Gentoo]]
** [[Hackable:1]]
** [[Mer]]
** [[Neovento]]
** [[OpenWrt]]
** [[SHR]]
</div>
|-
|}
== Banaketei buruz ==
Openmoko banaketak hainbat mobiletan erabiltzeko diseinatu dira, baina helburu nagusia Openmoko Inc. proiektuaren [[GTA01:Neo 1973|Neo 1973]] eta [[Neo FreeRunner]] telefono mugikorretan funtzionatzea dute. GNU/Linux banaketak dira, alegia, Linux sistema eragilea eta erabilera zabaleko hainbat aplikazioz osatutako aplikazio multzoak dira. Zeure telefonoan banaketa horietako edozein instala zenezake, edo nahi izanez gero, banaketa bat baino gehiago eduki ditzakezu eta pizterakoan aukeratu zein banaketarekin abiarazi nahi duzun. Banaketaren bat deskargatzeko ikusi [[Download]], instalaziorako argibideak [[Flashing the Neo FreeRunner|FreeRunnerrean banaketen instalazioa]] orrian aurkituko dituzu.

Horrez gain, Openmoko banaketak [[Supported devices|beste]] mobil batzuetan ere instala daitezke, eta, era berean, beste banaketa batzuek ere instala daitezke Openmoko proiektuaren mobiletan.

=== Banaketa egokiaren aukera ===

2009ko abuztuaz geroztik egindako inkesta baten arabera [[SHR]] da gehien erabiltzen den banaketa, eta horri openmokoren banaketek jarraitzen diote ([[Om 2007]], [[Om 2008]] eta [[Om 2009]] hirurak bakar baten moduan hartuz gero beti ere), beste hainbat aukera ere badaude: [[Debian]], Debianen oinarritutako [[Hackable:1]], [[Qt Extended Improved]], [[Android]], Qtmoko eta abar.[http://doodle.com/sd2c8d8snr23eeqq] Om 2009 banaketaren garapena geratu egin da ordea, eta beraz bere erabiltzaileek beste banaketaren batera pasa beharko dute.

=== Kontuan izan ===

* Egonkorra hitzak FreeRunnerraren munduan ez du Debianen munduko esanahi bera.
* Banaketa gehienek abiatzaile, kernel, driver eta hardware berak erabiltzen dituzte. Ondorioz, behe mailako hutsegite berdinak agertzen dira banaketa gehienetan. Azken aplikazio zirraragarriek akats zaharrak konponduta edukiko dituzte, baina berriak bertan azalduko dira...
* Banaketa hauek aplikazioen biltegiak ere eduki ohi dituzte. bertatik instalatu aplikazio berriak, beste batetik instalatzea ideia '''TXARRA''' da. Ikusi [[installing alien package|beste banaketen aplikazioen instalazioa]].
* Banaketa hauen artean batetik besterako maila igoerak (upgradeak) ez dira ondo probatuta egoten, ondorioz, eguneraketak biltegiak aldatuz eginez gero, aplikazioeak apurtzea ekar dezake, edo okerragoa dena, abiarazi ezin den sistemarekin bukatu daiteke. Egin behar dena sistema FreeRunnerraren Flash memorian instalatzea da, horretarako [[dfu-util]] erabiliz, horrela, banaketa ezberdinen artean aukeratu ahal izango duzu. Abiaratze bikoitza ezar daiteke [[Booting from SD|MikroSD]] edo [[Booting from NFS|NFS]]) erabiliz.
* [[Marketing Mistakes|merkaturatze akatsak]] eta aurreinstalatutako banaketak

== Gainbegirada ==

=== Android ===
{{Template:Works on Android}}
[http://code.google.com/android/ Android] gailu mobilentzat garatutako software metaketa bat da, bere arduraduna [http://www.openhandsetalliance.com/ The Open Handset Alliance] da. Openmokok guztiz sostengatzen eta babesten du FreeRunnerrean Android banaketaren erabilera.

Android dagoenekoz Freerunnerra eguneroko mobil gisa erabiltzeko garapen mailara iritsia da, dena den, kontua eta arreta eskatzen duten gaiak daude oraindik. Informazio gehiago edukitzkeo, Wikiko Androiden atal nagusia aztertzea gomendatzen dizut.

{{Main|Android}} Bestalde, [http://wiki.openmoko.org/wiki/User:Seanmcneil3 Sean McNeil] erabiltzailearen web orria ere gomendagarria da informazio gehiago nahi baduzu.

=== Debian ===
{{Template:Works on Debian}}
[[Debian]] "sistema eragile unibertsala" da. Milaka paketa eta aplikazio dauzka (gehenak mahai gaineko ordenadoreetarako edota zerbitzarietarako paketeak dira). Joachim "nomeata" Breitner [http://wiki.debian.org/Teams/DebianFSO pkg-fso] taldeko kidearen hitzetan, Debian, Openmokoren zentzuan, ez da banaketa bat, horren ordez, Openmokoren beste banaketentzat azpiegitura edota oinarri-sistematzat har daiteke. Oraingoz,alatzeko beste bide bat bezala har daiteke, baina bide honek leku gehiago hartzen du eta askoz programa gehiago eskaintzen ditu.

{{Main|Debian}}

=== Qt Extended Improved ===
Hainbat izen jaso ditu Qt Extended banaketak. Azkenetakoa <b>Qt Extended Improved</b> da. Openmoko-n oinarritutako komunitateak software libreko proiektu moduan garatua izan da. Qt Extended Improved banaketak telefoniako aplikazio multzo sendoa eskaintzen du, internet nabigatzailea eta telefono adimendunen hainbat ezaugarri ere bai.

209ko martxoaren 5.ean Qt Software-k Qt Extended 4.4.3 atera zuen. 2009ko martxoaren 3an Qt Software-k esan zuen hori izango zela bere azken bertsioa, ez zituela gehiago landuko. Qt Extended beste izen batez ezagutzen zen, hau da, Qtopia izena zen garai batean bere izena.

{{Main|Qt Extended Improved}}

=== QtMoko ===
{{Template:Works on QtMoko}}
Qt Extended-etik ateratako adarra da [http://activationrecord.net/radekp/qtmoko/ QT Moko]. Hainbat ezaugarri ditu:
* QTMokok X sistema onartzen du (X4 baino azkarragoa da)
* QTMokon AUX botoiak X aplikazioen menua atera dezake.
* QTMokok X terminala eskaintzen du, teklatu birtualarekin.
* QTMokon X-Server bidez X aplikazioak erabil daitezke, esate baterako [http://www.tangogps.org/gps/articles/7-Installation.html#extended TangoGPS] erabil daiteke GPS applikazio moduan.

{{Main|QT Moko}}

=== Gentoo ===
{{Template:Works on Gentoo}}
[[Gentoo]] banaketa aukeratzearen banaketa da. Gentoo instalatzerakoan erraz ulertuko duzu horren esanahia: zer konpilatu nahi duzun eta zer ez aukeratu ahal izango duzu, nola instalatu nahi duzun ere bai, zein log-sistema nahi duzun... Gentoo azkarra da, modernoa eta diseinu argia du, eta egokitzeko aukera eskaintzen du. Software librez egina dago, eta ez du ezkutatzen bere barnean dagoena. Paketeen mantenurako Portage aplikazioa erabiltzen du, Python hizkuntzan idatzita dago, beraz, erraz ikus eta alda daiteke jatorrizko kodea. Paketeen kudeaketa-sistemak jatorrizko kodea (iturburu-kodea) erabiltzen du (nahiz eta konpilatutakoak ere erabil ditzakeen) eta Gentoo-ren konfigurazioa ere testu fitxategien bidez egiten da. Ikus dezakezunez, dena irekia eta aldagarria.

{{Main|Gentoo}}

=== Hackable:1 ===
{{Template:Works on Hackable:1}}
Komunitateak landutako banaketa da Hackable1, gailu hackeagarrientzako sortutako banaketa da, eta jakina NeoFreerunnerra hackeagarria da. Debian eta 2007.2 banaketak daude bere oinarrian eta GNOMEren plataforma mugikorra jarraitzen du.
{{Main|Hackable:1}}
<br style="clear: both">
=== Mer ===
{{Template:Works on Mer}}
[[Mer]] banaketa [[Maemo]]-n oinarritzen da.
<br style="clear: both">
=== Mokotouch ===
{{Template:Works on Mokotouch}}
[[MokoTouch]] banaketak OM banaketen ordezkoa izan nahi du. Sistemaren konfiguraziorako aplikazioak, eta beste hainbat aplikazio erabilgarri edukiko ditu, horien artean daude posta bezeroa, argazki eta mapen bistaraketarako aplikazioak eta antzekoak. C++ kodeketan garatu da osorik, Qt 4.5 Embeded erabiltzen du eta Framebufferra erabiltzen du grafikoetarako, beraz ez du X11 behar. http://th30z.netsons.org/mokotouch/index.html

[http://www.youtube.com/watch?v=yr821OgnvYc Video]
<br style="clear: both">
=== neovento ===
{{Template:Works on noevento}}
[[neovento]] (ex FYP) is a [[Debian|Debian on Freerunner]] based [[Distributions|distribution]] which uses [http://lxde.org/ LXDE] and [[Zhone]] on top. It is a [http://freeyourphone.de FreeYourPhone.de] community project.

{{Main|neovento}}
<br style="clear: both">

=== OpenWrt ===
{{Template:Works on OpenWrt}}
[[OpenWrt]] is described as a Linux distribution for embedded devices.

Instead of trying to create a single, static firmware, [[OpenWrt]] provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developer, [[OpenWrt]] is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.

[[OpenWrt]] development trunk now supports s3c24xx, CPU used in [[Freerunner]].

Mainly due to the usage of uClibc instead of glibc as libc implementation, OpenWrt can boot from NAND with enlightenment window manager within 1 minute 7 seconds using u-boot (NOR) bootloader.

* [http://www.openwrt.org OpenWrt website]
* [http://dev.openwrt.org OpenWrt development site]

{{Main|OpenWrt}}

=== Qalee ===
{{Works on Qalee}}
[[Qalee]] is a phone environment developed in Qt4 above the fso stack. It works on the freerunner under any distribution that supports Qt4. It's not finished yet but you can test a preview version with the official Qalee distributon. This release includes no new features, but many fixes for things that didn’t work or were incomplete in 0.0.2. You can read full [http://think-free.homelinux.org/wordpress/ announcement], or take a look at some of changes:
* Qalee is now based on shr instead of debian.
* clock widget now shows a calendar when clicked.
* status panel widget shows gsm network name and power and internet connection status while on wifi or gprs.
* screen menu : you can now choose the background picture with a cover-flow effect, letting the backlight always on now works.
* network menu : all entries work, gsm one is a little buggy though.
* Wifi works despite the the bug in the kernel 2.6.29 opened for 4 month.
* application menu : to launch application just click on it :) when launched the button becomes green, to close it, press the close button which becomes red and click on the application you want to close
* power button supports suspend on short press, or menu on longer press.
* phone application is now litephone modified to use Qalee’s buttons.
* GorshPlayer is broken, if you have Qt4.5.2 librairies with phonon working on shr, tell me (?)//FIXME
* keyboard is still literky.
* Themable interface allows you to change some colours of the interface.
<br>WARNING :<br>
Qalee is in pre-alpha stage, a lot of thinks are not coded yet, other are broken, some may be changed. It's just a preview version of the current work!
http://www.qalee.org

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

{{Main|SHR}}

=== Slackware ===
{{Template:Works on Slackware}}
As of release 12.2, Slackware is now officially supported on the Neo Freerunner
[http://armedslack.org/]
--[[User:Djdas|djdas]] 15:54, 13 June 2009 (UTC)There aren't any confirmations of ArmedSlack running on Freerunner either on the website or the official ML, do you have any link pointing on that?
<br style="clear: both">
=== Abandoned ===

==== FDOM (FAT and Dirty Openmoko) ====
{{Template:Works on FDOM}}
[[FDOM]] was a distribution based on [[Om 2008]], updated with many ready-to-use applications and with fixes posted in the mailing lists.

{{Main|FDOM}}
<br style="clear: both">

==== Om series ====
* '''[[Om 2009]]''' was intended to be the new distro; it is not a simple follow-on from [[Om 2008]]. It is based on the [http://freesmartphone.org freesmartphone.org] milestone 5.5 framework. Development of Om 2009 was ended and developers moved on to work on other distros instead.

{{Main|Om2009}}

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

{{Main|Om 2008}}

* '''[[Om 2007.2]]''' was the first distribution created by Openmoko. The interface was totally finger-oriented, optimized for 285ppi, and very orange. It used the GTK+ stack, which is part of the [http://www.gnome.org/mobile/ GNOME Mobile] platform. This distribution is now considered obsolete and not being worked on by Openmoko Inc or by OpenedHand.

{{Main|Om 2007.2}}

=== Others / unreleased ===
* The [http://www.neopwn.com/software.php NeoPwn] network auditng system's core is a modified Linux 2.6.24 kernel, with cross-compiled module driver support for the numerous compatible addon devices running on a FULL Debian (ARMEL) operating system. The filesystem has been optimized for performance and size and includes the NeoPwn menu system and several GUI dialogs for hardware control and attack automation. ''Status: Unknown, the GPL requires source code to be distributed only to customers''.
* [http://runningbear.org/trac RunningBear] is an innovative, yet free and open-source Operating System for hackable devices driven by Bearstech. Lightweight, Portable, Secure, Friendly and Useful. ''Status: In development''.
* [http://pokylinux.org/ Poky] and Sato, by OpenedHand/Intel. An open source platform build tool derived from OE. It is a complete software development environment for the creation of Linux devices. It enables you to design, develop, build, debug, and test a complete, modern, software stack using Linux, the X Window System and GNOME Mobile based application frameworks for both ARM and x86 based platforms. ''Status: The "Nightly Build" Image works fine on Neo Freerunner, but phone functionality doesn't.''
* [http://pyneo.org/ PyNeo] pyneo is a stack for mobile devices excessivly using dbus, glib and evas. Pyneo is NO distribution but a middleware or framework like FSO which itself developed from a very early version of pyneo. Current pyneo images are entirely based on debian instead of oe. ''Status: still active and in development! ask around on #pyneo.org ''
* [http://www.quantum-step.com/ mySTEP] by Openmoko distributor Golden Delicious Computers is based on GNUstep and brings a Objective-C API to the Neo. Core GUI frameworks are "Foundation" & "AppKit". It has been shown on FOSDEM 2008, LinuxTag 2008 and SYSTEMS 2008 to run on the Neo 1973. If someone reengineers UIKit, (open) source code compatibility to iPhone apps appears achievable. ''Status: slow progress behind the scenes''
* [http://www.archmobile.org/ Archlinux] is a distribution that follows the KISS principle.

== Features by distribution/release target ==

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

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

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

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

=== User Interaction ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=8%|[[Om 2009]] !! width=8%|[[Om 2008]] !! width=8%|Om 2007.2 !! width=8%|[[SHR]] !! width=8%|[[Qt Extended Improved]] !! width=8%|[[Debian]] !! width=8%|[[Gentoo]] !! width=8%|[[Android]]
|-
| Finger friendly || {{Yes}} || Partially || Partially || {{Yes}} || {{Yes}} || {{Yes}} [[Illume|(1)]] || {{Yes}} || {{Yes}}
|-
| Accelerometer || {{Yes}} (1) || {{Yes}} [[Rotate|(1)]][[Gestures|(1)]] || {{No}} || {{Yes}} || {{No}} || {{Yes}} || ?? || {{Yes}}
|-
|}

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

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

Footnotes:

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

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

(*) unstable

==Quick download page==

[[Download]]

== See also ==

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

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

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

[[Category:Distributions| ]]

Distributions/eu

2010-06-11T18:05:55Z

Joseba:

{{Languages|Distributions}}

{|align=right
|__TOC__
|}
{| class="wikitable" style="float:left;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|<font color=white>Distributions</font>
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* <font color='#BBBBBB'>Openmoko (official)</font>
** [[Om 2009]]
** [[Om 2008]]
** [[Om 2007.2]]
* <font color='#BBBBBB'>Om Community</font>
** [[Android]]
** [[Debian]]
** [[Qt Extended Improved]]
** [[QtMoko]]
** [[Gentoo]]
** [[Hackable:1]]
** [[Mer]]
** [[Neovento]]
** [[OpenWrt]]
** [[SHR]]
</div>
|-
|}
== Banaketei buruz ==
Openmoko banaketak hainbat mobiletan erabiltzeko diseinatu dira, baina helburu nagusia Openmoko Inc. proiektuaren [[GTA01:Neo 1973|Neo 1973]] eta [[Neo FreeRunner]] telefono mugikorretan funtzionatzea dute. GNU/Linux banaketak dira, alegia, Linux sistema eragilea eta erabilera zabaleko hainbat aplikazioz osatutako aplikazio multzoak dira. Zeure telefonoan banaketa horietako edozein instala zenezake, edo nahi izanez gero, banaketa bat baino gehiago eduki ditzakezu eta pizterakoan aukeratu zein banaketarekin abiarazi nahi duzun. Banaketaren bat deskargatzeko ikusi [[Download]], instalaziorako argibideak [[Flashing the Neo FreeRunner|FreeRunnerrean banaketen instalazioa]] orrian aurkituko dituzu.

Horrez gain, Openmoko banaketak [[Supported devices|beste]] mobil batzuetan ere instala daitezke, eta, era berean, beste banaketa batzuek ere instala daitezke Openmoko proiektuaren mobiletan.

=== Banaketa egokiaren aukera ===

2009ko abuztuaz geroztik egindako inkesta baten arabera [[SHR]] da gehien erabiltzen den banaketa, eta horri openmokoren banaketek jarraitzen diote ([[Om 2007]], [[Om 2008]] eta [[Om 2009]] hirurak bakar baten moduan hartuz gero beti ere), beste hainbat aukera ere badaude: [[Debian]], Debianen oinarritutako [[Hackable:1]], [[Qt Extended Improved]], [[Android]], Qtmoko eta abar.[http://doodle.com/sd2c8d8snr23eeqq] Om 2009 banaketaren garapena geratu egin da ordea, eta beraz bere erabiltzaileek beste banaketaren batera pasa beharko dute.

=== Kontuan izan ===

* Egonkorra hitzak FreeRunnerraren munduan ez du Debianen munduko esanahi bera.
* Banaketa gehienek abiatzaile, kernel, driver eta hardware berak erabiltzen dituzte. Ondorioz, behe mailako hutsegite berdinak agertzen dira banaketa gehienetan. Azken aplikazio zirraragarriek akats zaharrak konponduta edukiko dituzte, baina berriak bertan azalduko dira...
* Banaketa hauek aplikazioen biltegiak ere eduki ohi dituzte. bertatik instalatu aplikazio berriak, beste batetik instalatzea ideia '''TXARRA''' da. Ikusi [[installing alien package|beste banaketen aplikazioen instalazioa]].
* Banaketa hauen artean batetik besterako maila igoerak (upgradeak) ez dira ondo probatuta egoten, ondorioz, eguneraketak biltegiak aldatuz eginez gero, aplikazioeak apurtzea ekar dezake, edo okerragoa dena, abiarazi ezin den sistemarekin bukatu daiteke. Egin behar dena sistema FreeRunnerraren Flash memorian instalatzea da, horretarako [[dfu-util]] erabiliz, horrela, banaketa ezberdinen artean aukeratu ahal izango duzu. Abiaratze bikoitza ezar daiteke [[Booting from SD|MikroSD]] edo [[Booting from NFS|NFS]]) erabiliz.
* [[Marketing Mistakes|merkaturatze akatsak]] eta aurreinstalatutako banaketak

== Gainbegirada ==

=== Android ===
{{Template:Works on Android}}
[http://code.google.com/android/ Android] gailu mobilentzat garatutako software metaketa bat da, bere arduraduna [http://www.openhandsetalliance.com/ The Open Handset Alliance] da. Openmokok guztiz sostengatzen eta babesten du FreeRunnerrean Android banaketaren erabilera.

Android dagoenekoz Freerunnerra eguneroko mobil gisa erabiltzeko garapen mailara iritsia da, dena den, kontua eta arreta eskatzen duten gaiak daude oraindik. Informazio gehiago edukitzkeo, Wikiko Androiden atal nagusia aztertzea gomendatzen dizut.

{{Main|Android}} Bestalde, [http://wiki.openmoko.org/wiki/User:Seanmcneil3 Sean McNeil] erabiltzailearen web orria ere gomendagarria da informazio gehiago nahi baduzu.

=== Debian ===
{{Template:Works on Debian}}
[[Debian]] "sistema eragile unibertsala" da. Milaka paketa eta aplikazio dauzka (gehenak mahai gaineko ordenadoreetarako edota zerbitzarietarako paketeak dira). Joachim "nomeata" Breitner [http://wiki.debian.org/Teams/DebianFSO pkg-fso] taldeko kidearen hitzetan, Debian, Openmokoren zentzuan, ez da banaketa bat, horren ordez, Openmokoren beste banaketentzat azpiegitura edota oinarri-sistematzat har daiteke. Oraingoz,alatzeko beste bide bat bezala har daiteke, baina bide honek leku gehiago hartzen du eta askoz programa gehiago eskaintzen ditu.

{{Main|Debian}}

=== Qt Extended Improved ===
Hainbat izen jaso ditu Qt Extended banaketak. Azkenetakoa <b>Qt Extended Improved</b> da. Openmoko-n oinarritutako komunitateak software libreko proiektu moduan garatua izan da. Qt Extended Improved banaketak telefoniako aplikazio multzo sendoa eskaintzen du, internet nabigatzailea eta telefono adimendunen hainbat ezaugarri ere bai.

209ko martxoaren 5.ean Qt Software-k Qt Extended 4.4.3 atera zuen. 2009ko martxoaren 3an Qt Software-k esan zuen hori izango zela bere azken bertsioa, ez zituela gehiago landuko. Qt Extended beste izen batez ezagutzen zen, hau da, Qtopia izena zen garai batean bere izena.

{{Main|Qt Extended Improved}}

=== QtMoko ===
{{Template:Works on QtMoko}}
Qt Extended-etik ateratako adarra da [http://activationrecord.net/radekp/qtmoko/ QT Moko]. Hainbat ezaugarri ditu:
* QTMokok X sistema onartzen du (X4 baino azkarragoa da)
* QTMokon AUX botoiak X aplikazioen menua atera dezake.
* QTMokok X terminala eskaintzen du, teklatu birtualarekin.
* QTMokon X-Server bidez X aplikazioak erabil daitezke, esate baterako [http://www.tangogps.org/gps/articles/7-Installation.html#extended TangoGPS] erabil daiteke GPS applikazio moduan.

{{Main|QTMoko}}

=== Gentoo ===
{{Template:Works on Gentoo}}
[[Gentoo]] banaketa aukeratzearen banaketa da. Gentoo instalatzerakoan erraz ulertuko duzu horren esanahia: zer konpilatu nahi duzun eta zer ez aukeratu ahal izango duzu, nola instalatu nahi duzun ere bai, zein log-sistema nahi duzun... Gentoo azkarra da, modernoa eta diseinu argia du, eta egokitzeko aukera eskaintzen du. Software librez egina dago, eta ez du ezkutatzen bere barnean dagoena. Paketeen mantenurako Portage aplikazioa erabiltzen du, Python hizkuntzan idatzita dago, beraz, erraz ikus eta alda daiteke jatorrizko kodea. Paketeen kudeaketa-sistemak jatorrizko kodea (iturburu-kodea) erabiltzen du (nahiz eta konpilatutakoak ere erabil ditzakeen) eta Gentoo-ren konfigurazioa ere testu fitxategien bidez egiten da. Ikus dezakezunez, dena irekia eta aldagarria.

{{Main|Gentoo}}

=== Hackable:1 ===
{{Template:Works on Hackable:1}}
Komunitateak landutako banaketa da Hackable1, gailu hackeagarrientzako sortutako banaketa da, eta jakina NeoFreerunnerra hackeagarria da. Debian eta 2007.2 banaketak daude bere oinarrian eta GNOMEren plataforma mugikorra jarraitzen du.
{{Main|Hackable:1}}
<br style="clear: both">
=== Mer ===
{{Template:Works on Mer}}
[[Mer]] banaketa [[Maemo]]-n oinarritzen da.
<br style="clear: both">
=== Mokotouch ===
{{Template:Works on Mokotouch}}
[[MokoTouch]] banaketak OM banaketen ordezkoa izan nahi du. Sistemaren konfiguraziorako aplikazioak, eta beste hainbat aplikazio erabilgarri edukiko ditu, horien artean daude posta bezeroa, argazki eta mapen bistaraketarako aplikazioak eta antzekoak. C++ kodeketan garatu da osorik, Qt 4.5 Embeded erabiltzen du eta Framebufferra erabiltzen du grafikoetarako, beraz ez du X11 behar. http://th30z.netsons.org/mokotouch/index.html

[http://www.youtube.com/watch?v=yr821OgnvYc Video]
<br style="clear: both">
=== neovento ===
{{Template:Works on noevento}}
[[neovento]] (ex FYP) is a [[Debian|Debian on Freerunner]] based [[Distributions|distribution]] which uses [http://lxde.org/ LXDE] and [[Zhone]] on top. It is a [http://freeyourphone.de FreeYourPhone.de] community project.

{{Main|neovento}}
<br style="clear: both">

=== OpenWrt ===
{{Template:Works on OpenWrt}}
[[OpenWrt]] is described as a Linux distribution for embedded devices.

Instead of trying to create a single, static firmware, [[OpenWrt]] provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developer, [[OpenWrt]] is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.

[[OpenWrt]] development trunk now supports s3c24xx, CPU used in [[Freerunner]].

Mainly due to the usage of uClibc instead of glibc as libc implementation, OpenWrt can boot from NAND with enlightenment window manager within 1 minute 7 seconds using u-boot (NOR) bootloader.

* [http://www.openwrt.org OpenWrt website]
* [http://dev.openwrt.org OpenWrt development site]

{{Main|OpenWrt}}

=== Qalee ===
{{Works on Qalee}}
[[Qalee]] is a phone environment developed in Qt4 above the fso stack. It works on the freerunner under any distribution that supports Qt4. It's not finished yet but you can test a preview version with the official Qalee distributon. This release includes no new features, but many fixes for things that didn’t work or were incomplete in 0.0.2. You can read full [http://think-free.homelinux.org/wordpress/ announcement], or take a look at some of changes:
* Qalee is now based on shr instead of debian.
* clock widget now shows a calendar when clicked.
* status panel widget shows gsm network name and power and internet connection status while on wifi or gprs.
* screen menu : you can now choose the background picture with a cover-flow effect, letting the backlight always on now works.
* network menu : all entries work, gsm one is a little buggy though.
* Wifi works despite the the bug in the kernel 2.6.29 opened for 4 month.
* application menu : to launch application just click on it :) when launched the button becomes green, to close it, press the close button which becomes red and click on the application you want to close
* power button supports suspend on short press, or menu on longer press.
* phone application is now litephone modified to use Qalee’s buttons.
* GorshPlayer is broken, if you have Qt4.5.2 librairies with phonon working on shr, tell me (?)//FIXME
* keyboard is still literky.
* Themable interface allows you to change some colours of the interface.
<br>WARNING :<br>
Qalee is in pre-alpha stage, a lot of thinks are not coded yet, other are broken, some may be changed. It's just a preview version of the current work!
http://www.qalee.org

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

{{Main|SHR}}

=== Slackware ===
{{Template:Works on Slackware}}
As of release 12.2, Slackware is now officially supported on the Neo Freerunner
[http://armedslack.org/]
--[[User:Djdas|djdas]] 15:54, 13 June 2009 (UTC)There aren't any confirmations of ArmedSlack running on Freerunner either on the website or the official ML, do you have any link pointing on that?
<br style="clear: both">
=== Abandoned ===

==== FDOM (FAT and Dirty Openmoko) ====
{{Template:Works on FDOM}}
[[FDOM]] was a distribution based on [[Om 2008]], updated with many ready-to-use applications and with fixes posted in the mailing lists.

{{Main|FDOM}}
<br style="clear: both">

==== Om series ====
* '''[[Om 2009]]''' was intended to be the new distro; it is not a simple follow-on from [[Om 2008]]. It is based on the [http://freesmartphone.org freesmartphone.org] milestone 5.5 framework. Development of Om 2009 was ended and developers moved on to work on other distros instead.

{{Main|Om2009}}

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

{{Main|Om 2008}}

* '''[[Om 2007.2]]''' was the first distribution created by Openmoko. The interface was totally finger-oriented, optimized for 285ppi, and very orange. It used the GTK+ stack, which is part of the [http://www.gnome.org/mobile/ GNOME Mobile] platform. This distribution is now considered obsolete and not being worked on by Openmoko Inc or by OpenedHand.

{{Main|Om 2007.2}}

=== Others / unreleased ===
* The [http://www.neopwn.com/software.php NeoPwn] network auditng system's core is a modified Linux 2.6.24 kernel, with cross-compiled module driver support for the numerous compatible addon devices running on a FULL Debian (ARMEL) operating system. The filesystem has been optimized for performance and size and includes the NeoPwn menu system and several GUI dialogs for hardware control and attack automation. ''Status: Unknown, the GPL requires source code to be distributed only to customers''.
* [http://runningbear.org/trac RunningBear] is an innovative, yet free and open-source Operating System for hackable devices driven by Bearstech. Lightweight, Portable, Secure, Friendly and Useful. ''Status: In development''.
* [http://pokylinux.org/ Poky] and Sato, by OpenedHand/Intel. An open source platform build tool derived from OE. It is a complete software development environment for the creation of Linux devices. It enables you to design, develop, build, debug, and test a complete, modern, software stack using Linux, the X Window System and GNOME Mobile based application frameworks for both ARM and x86 based platforms. ''Status: The "Nightly Build" Image works fine on Neo Freerunner, but phone functionality doesn't.''
* [http://pyneo.org/ PyNeo] pyneo is a stack for mobile devices excessivly using dbus, glib and evas. Pyneo is NO distribution but a middleware or framework like FSO which itself developed from a very early version of pyneo. Current pyneo images are entirely based on debian instead of oe. ''Status: still active and in development! ask around on #pyneo.org ''
* [http://www.quantum-step.com/ mySTEP] by Openmoko distributor Golden Delicious Computers is based on GNUstep and brings a Objective-C API to the Neo. Core GUI frameworks are "Foundation" & "AppKit". It has been shown on FOSDEM 2008, LinuxTag 2008 and SYSTEMS 2008 to run on the Neo 1973. If someone reengineers UIKit, (open) source code compatibility to iPhone apps appears achievable. ''Status: slow progress behind the scenes''
* [http://www.archmobile.org/ Archlinux] is a distribution that follows the KISS principle.

== Features by distribution/release target ==

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

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

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

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

=== User Interaction ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=8%|[[Om 2009]] !! width=8%|[[Om 2008]] !! width=8%|Om 2007.2 !! width=8%|[[SHR]] !! width=8%|[[Qt Extended Improved]] !! width=8%|[[Debian]] !! width=8%|[[Gentoo]] !! width=8%|[[Android]]
|-
| Finger friendly || {{Yes}} || Partially || Partially || {{Yes}} || {{Yes}} || {{Yes}} [[Illume|(1)]] || {{Yes}} || {{Yes}}
|-
| Accelerometer || {{Yes}} (1) || {{Yes}} [[Rotate|(1)]][[Gestures|(1)]] || {{No}} || {{Yes}} || {{No}} || {{Yes}} || ?? || {{Yes}}
|-
|}

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

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

Footnotes:

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

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

(*) unstable

==Quick download page==

[[Download]]

== See also ==

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

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

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

[[Category:Distributions| ]]

Distributions/eu

2010-03-15T20:55:01Z

Joseba:

{{Languages|Distributions}}

{|align=right
|__TOC__
|}
{| class="wikitable" style="float:left;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|<font color=white>Distributions</font>
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* <font color='#BBBBBB'>Openmoko (official)</font>
** [[Om 2009]]
** [[Om 2008]]
** [[Om 2007.2]]
* <font color='#BBBBBB'>Om Community</font>
** [[Android]]
** [[Debian]]
** [[Gentoo]]
** [[Hackable:1]]
** [[Mer]]
** [[Neovento]]
** [[OpenWrt]]
** [[Qt Extended Improved]]
** [[SHR]]
</div>
|-
|}
== Banaketei buruz ==
Openmoko banaketak hainbat mobiletan erabiltzeko diseinatu dira, baina helburu nagusia Openmoko Inc. proiektuaren [[GTA01:Neo 1973|Neo 1973]] eta [[Neo FreeRunner]] telefono mugikorretan funtzionatzea dute. GNU/Linux banaketak dira, alegia, Linux sistema eragilea eta erabilera zabaleko hainbat aplikazioz osatutako aplikazio multzoak dira. Zeure telefonoan banaketa horietako edozein instala zenezake, edo nahi izanez gero, banaketa bat baino gehiago eduki ditzakezu eta pizterakoan aukeratu zein banaketarekin abiarazi nahi duzun. Banaketaren bat deskargatzeko ikusi [[Download]], instalaziorako argibideak [[Flashing the Neo FreeRunner|FreeRunnerrean banaketen instalazioa]] orrian aurkituko dituzu.

Horrez gain, Openmoko banaketak [[Supported devices|beste]] mobil batzuetan ere instala daitezke, eta, era berean, beste banaketa batzuek ere instala daitezke Openmoko proiektuaren mobiletan.

=== Banaketa egokiaren aukera ===

2009ko abuztuaz geroztik egindako inkesta baten arabera [[SHR]] da gehien erabiltzen den banaketa, eta horri openmokoren banaketek jarraitzen diote ([[Om 2007]], [[Om 2008]] eta [[Om 2009]] hirurak bakar baten moduan hartuz gero beti ere), beste hainbat aukera ere badaude: [[Debian]], Debianen oinarritutako [[Hackable:1]], [[Qt Extended Improved]], [[Android]], Qtmoko eta abar.[http://doodle.com/sd2c8d8snr23eeqq] Om 2009 banaketaren garapena geratu egin da ordea, eta beraz bere erabiltzaileek beste banaketaren batera pasa beharko dute.

=== Kontuan izan ===

* Egonkorra hitzak FreeRunnerraren munduan ez du Debianen munduko esanahi bera.
* Banaketa gehienek abiatzaile, kernel, driver eta hardware berak erabiltzen dituzte. Ondorioz, behe mailako hutsegite berdinak agertzen dira banaketa gehienetan. Azken aplikazio zirraragarriek akats zaharrak konponduta edukiko dituzte, baina berriak bertan azalduko dira...
* Banaketa hauek aplikazioen biltegiak ere eduki ohi dituzte. bertatik instalatu aplikazio berriak, beste batetik instalatzea ideia '''TXARRA''' da. Ikusi [[installing alien package|beste banaketen aplikazioen instalazioa]].
* Banaketa hauen artean batetik besterako maila igoerak (upgradeak) ez dira ondo probatuta egoten, ondorioz, eguneraketak biltegiak aldatuz eginez gero, aplikazioeak apurtzea ekar dezake, edo okerragoa dena, abiarazi ezin den sistemarekin bukatu daiteke. Egin behar dena sistema FreeRunnerraren Flash memorian instalatzea da, horretarako [[dfu-util]] erabiliz, horrela, banaketa ezberdinen artean aukeratu ahal izango duzu. Abiaratze bikoitza ezar daiteke [[Booting from SD|MikroSD]] edo [[Booting from NFS|NFS]]) erabiliz.
* [[Marketing Mistakes|merkaturatze akatsak]] eta aurreinstalatutako banaketak

== Gainbegirada ==

=== Android ===
{{Template:Works on Android}}
[http://code.google.com/android/ Android] gailu mobilentzat garatutako software metaketa bat da, bere arduraduna [http://www.openhandsetalliance.com/ The Open Handset Alliance] da. Openmokok guztiz sostengatzen eta babesten du FreeRunnerrean Android banaketaren erabilera.

Android dagoenekoz Freerunnerra eguneroko mobil gisa erabiltzeko garapen mailara iritsia da, dena den, kontua eta arreta eskatzen duten gaiak daude oraindik. Informazio gehiago edukitzkeo, Wikiko Androiden atal nagusia aztertzea gomendatzen dizut.

{{Main|Android}} Bestalde, [http://wiki.openmoko.org/wiki/User:Seanmcneil3 Sean McNeil] erabiltzailearen web orria ere gomendagarria da informazio gehiago nahi baduzu.

=== Debian ===
{{Template:Works on Debian}}
[[Debian]] "sistema eragile unibertsala" da. Milaka paketa eta aplikazio dauzka (gehenak mahai gaineko ordenadoreetarako edota zerbitzarietarako paketeak dira). Joachim "nomeata" Breitner [http://wiki.debian.org/Teams/DebianFSO pkg-fso] taldeko kidearen hitzetan, Debian, Openmokoren zentzuan, ez da banaketa bat, horren ordez, Openmokoren beste banaketentzat azpiegitura edota oinarri-sistematzat har daiteke. Oraingoz,alatzeko beste bide bat bezala har daiteke, baina bide honek leku gehiago hartzen du eta askoz programa gehiago eskaintzen ditu.

{{Main|Debian}}

=== Gentoo ===
{{Template:Works on Gentoo}}
[[Gentoo]] banaketa aukeratzearen banaketa da. Gentoo instalatzerakoan erraz ulertuko duzu horren esanahia: zer konpilatu nahi duzun eta zer ez aukeratu ahal izango duzu, nola instalatu nahi duzun ere bai, zein log-sistema nahi duzun... Gentoo azkarra da, modernoa eta diseinu argia du, eta egokitzeko aukera eskaintzen du. Software librez egina dago, eta ez du ezkutatzen bere barnean dagoena. Paketeen mantenurako Portage aplikazioa erabiltzen du, Python hizkuntzan idatzita dago, beraz, erraz ikus eta alda daiteke jatorrizko kodea. Paketeen kudeaketa-sistemak jatorrizko kodea (iturburu-kodea) erabiltzen du (nahiz eta konpilatutakoak ere erabil ditzakeen) eta Gentoo-ren konfigurazioa ere testu fitxategien bidez egiten da. Ikus dezakezunez, dena irekia eta aldagarria.

{{Main|Gentoo}}

=== Hackable:1 ===
{{Template:Works on Hackable:1}}
Komunitateak landutako banaketa da Hackable1, gailu hackeagarrientzako sortutako banaketa da, eta jakina NeoFreerunnerra hackeagarria da. Debian eta 2007.2 banaketak daude bere oinarrian eta GNOMEren plataforma mugikorra jarraitzen du.
{{Main|Hackable:1}}
<br style="clear: both">
=== Mer ===
{{Template:Works on Mer}}
[[Mer]] banaketa [[Maemo]]-n oinarritzen da.
<br style="clear: both">
=== Mokotouch ===
{{Template:Works on Mokotouch}}
[[MokoTouch]] banaketak OM banaketen ordezkoa izan nahi du. Sistemaren konfiguraziorako aplikazioak, eta beste hainbat aplikazio erabilgarri edukiko ditu, horien artean daude posta bezeroa, argazki eta mapen bistaraketarako aplikazioak eta antzekoak. C++ kodeketan garatu da osorik, Qt 4.5 Embeded erabiltzen du eta Framebufferra erabiltzen du grafikoetarako, beraz ez du X11 behar. http://th30z.netsons.org/mokotouch/index.html

[http://www.youtube.com/watch?v=yr821OgnvYc Video]
<br style="clear: both">
=== neovento ===
{{Template:Works on noevento}}
[[neovento]] (ex FYP) is a [[Debian|Debian on Freerunner]] based [[Distributions|distribution]] which uses [http://lxde.org/ LXDE] and [[Zhone]] on top. It is a [http://freeyourphone.de FreeYourPhone.de] community project.

{{Main|neovento}}
<br style="clear: both">

=== OpenWrt ===
{{Template:Works on OpenWrt}}
[[OpenWrt]] is described as a Linux distribution for embedded devices.

Instead of trying to create a single, static firmware, [[OpenWrt]] provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developer, [[OpenWrt]] is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.

[[OpenWrt]] development trunk now supports s3c24xx, CPU used in [[Freerunner]].

Mainly due to the usage of uClibc instead of glibc as libc implementation, OpenWrt can boot from NAND with enlightenment window manager within 1 minute 7 seconds using u-boot (NOR) bootloader.

* [http://www.openwrt.org OpenWrt website]
* [http://dev.openwrt.org OpenWrt development site]

{{Main|OpenWrt}}

=== Qalee ===
{{Works on Qalee}}
[[Qalee]] is a phone environment developed in Qt4 above the fso stack. It works on the freerunner under any distribution that supports Qt4. It's not finished yet but you can test a preview version with the official Qalee distributon. This release includes no new features, but many fixes for things that didn’t work or were incomplete in 0.0.2. You can read full [http://think-free.homelinux.org/wordpress/ announcement], or take a look at some of changes:
* Qalee is now based on shr instead of debian.
* clock widget now shows a calendar when clicked.
* status panel widget shows gsm network name and power and internet connection status while on wifi or gprs.
* screen menu : you can now choose the background picture with a cover-flow effect, letting the backlight always on now works.
* network menu : all entries work, gsm one is a little buggy though.
* Wifi works despite the the bug in the kernel 2.6.29 opened for 4 month.
* application menu : to launch application just click on it :) when launched the button becomes green, to close it, press the close button which becomes red and click on the application you want to close
* power button supports suspend on short press, or menu on longer press.
* phone application is now litephone modified to use Qalee’s buttons.
* GorshPlayer is broken, if you have Qt4.5.2 librairies with phonon working on shr, tell me (?)//FIXME
* keyboard is still literky.
* Themable interface allows you to change some colours of the interface.
<br>WARNING :<br>
Qalee is in pre-alpha stage, a lot of thinks are not coded yet, other are broken, some may be changed. It's just a preview version of the current work!
http://www.qalee.org

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

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

{{Main|Qt Extended Improved}}

{{Template:Works on QtMoko}}
Another branch of development after discontinued Qt Extended is [http://activationrecord.net/radekp/qtmoko/ QT Moko]. Special feature are:
* QT Moko has better X support, which is much faster then X4,
* in QT Moko the AUX can bring menu for X application,
* QT Moko includes an X terminal with virtual keyboard and matchbox window manager
* in QT Moko with the X-Server support you can use X application like [http://www.tangogps.org/gps/articles/7-Installation.html#extended TangoGPS] as GPS application.

{{Main|QT Moko}}

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

{{Main|SHR}}

=== Slackware ===
{{Template:Works on Slackware}}
As of release 12.2, Slackware is now officially supported on the Neo Freerunner
[http://armedslack.org/]
--[[User:Djdas|djdas]] 15:54, 13 June 2009 (UTC)There aren't any confirmations of ArmedSlack running on Freerunner either on the website or the official ML, do you have any link pointing on that?
<br style="clear: both">
=== Abandoned ===

==== FDOM (FAT and Dirty Openmoko) ====
{{Template:Works on FDOM}}
[[FDOM]] was a distribution based on [[Om 2008]], updated with many ready-to-use applications and with fixes posted in the mailing lists.

{{Main|FDOM}}
<br style="clear: both">

==== Om series ====
* '''[[Om 2009]]''' was intended to be the new distro; it is not a simple follow-on from [[Om 2008]]. It is based on the [http://freesmartphone.org freesmartphone.org] milestone 5.5 framework. Development of Om 2009 was ended and developers moved on to work on other distros instead.

{{Main|Om2009}}

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

{{Main|Om 2008}}

* '''[[Om 2007.2]]''' was the first distribution created by Openmoko. The interface was totally finger-oriented, optimized for 285ppi, and very orange. It used the GTK+ stack, which is part of the [http://www.gnome.org/mobile/ GNOME Mobile] platform. This distribution is now considered obsolete and not being worked on by Openmoko Inc or by OpenedHand.

{{Main|Om 2007.2}}

=== Others / unreleased ===
* The [http://www.neopwn.com/software.php NeoPwn] network auditng system's core is a modified Linux 2.6.24 kernel, with cross-compiled module driver support for the numerous compatible addon devices running on a FULL Debian (ARMEL) operating system. The filesystem has been optimized for performance and size and includes the NeoPwn menu system and several GUI dialogs for hardware control and attack automation. ''Status: Unknown, the GPL requires source code to be distributed only to customers''.
* [http://runningbear.org/trac RunningBear] is an innovative, yet free and open-source Operating System for hackable devices driven by Bearstech. Lightweight, Portable, Secure, Friendly and Useful. ''Status: In development''.
* [http://pokylinux.org/ Poky] and Sato, by OpenedHand/Intel. An open source platform build tool derived from OE. It is a complete software development environment for the creation of Linux devices. It enables you to design, develop, build, debug, and test a complete, modern, software stack using Linux, the X Window System and GNOME Mobile based application frameworks for both ARM and x86 based platforms. ''Status: The "Nightly Build" Image works fine on Neo Freerunner, but phone functionality doesn't.''
* [http://pyneo.org/ PyNeo] pyneo is a stack for mobile devices excessivly using dbus, glib and evas. Pyneo is NO distribution but a middleware or framework like FSO which itself developed from a very early version of pyneo. Current pyneo images are entirely based on debian instead of oe. ''Status: still active and in development! ask around on #pyneo.org ''
* [http://www.quantum-step.com/ mySTEP] by Openmoko distributor Golden Delicious Computers is based on GNUstep and brings a Objective-C API to the Neo. Core GUI frameworks are "Foundation" & "AppKit". It has been shown on FOSDEM 2008, LinuxTag 2008 and SYSTEMS 2008 to run on the Neo 1973. If someone reengineers UIKit, (open) source code compatibility to iPhone apps appears achievable. ''Status: slow progress behind the scenes''
* [http://www.archmobile.org/ Archlinux] is a distribution that follows the KISS principle.

== Features by distribution/release target ==

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

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

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

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

=== User Interaction ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=8%|[[Om 2009]] !! width=8%|[[Om 2008]] !! width=8%|Om 2007.2 !! width=8%|[[SHR]] !! width=8%|[[Qt Extended Improved]] !! width=8%|[[Debian]] !! width=8%|[[Gentoo]] !! width=8%|[[Android]]
|-
| Finger friendly || {{Yes}} || Partially || Partially || {{Yes}} || {{Yes}} || {{Yes}} [[Illume|(1)]] || {{Yes}} || {{Yes}}
|-
| Accelerometer || {{Yes}} (1) || {{Yes}} [[Rotate|(1)]][[Gestures|(1)]] || {{No}} || {{Yes}} || {{No}} || {{Yes}} || ?? || {{Yes}}
|-
|}

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

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

Footnotes:

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

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

(*) unstable

==Quick download page==

[[Download]]

== See also ==

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

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

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

[[Category:Distributions| ]]

USB Networking/eu

2010-03-03T13:04:22Z

Joseba:

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

{{Languages|USB_Networking}}

{|align=left
|__TOC__
|}

= FreeRunnerra sarean USB konexio bidez erabiltzeko ezarpenak =

Zure FreeRunnerrera TCP/IP bidez komunikazioa ezarri ahal izateko oinarrizko ezaguera batzuek behar dira. Ez pentsa zaila denik, alderantziz, kasu gehienetan automatikoki funtzionatuko dizu. Hasteko FreeRunnerra eta PCa USB kablearen bidez lotu behar dira, USB kablearen mutur bakoitzean dagoen makina bakoitza (FreeRunnerra eta PCa) sare lokal (LAN) bateko bi makina dira. Alde batean FreeRunnerraren USB konexiodun sare txartela daukagu (besterik ezean 192.168.0.202 IP zenbakia izango duena) eta beste aldean PCa bera daukagu, honek ere USB bidezko sare lokalean IP bat edukiko du (besterik ezean 192.168.0.200).

Ohiko egoera batean, zure PCak badaki nola joan internetera, horretarako irteera atea dauka (gateway) eta bere IP zenbakia zein den badaki, azken finean gateway hori izango baita interneterako bidea emango diona. Informazio hori pizterakoan jaso du (dinamikoki DHCP bidez edo estatikoki), normalean router baten bidez (nahiz eta batzuetan zerbitzari lanak beste makina batek egiten dituen). FreeRunnerrak ere informazio hori behar du, eta zure PCak eman behar dio, gainera, zure PCak bideratu behar ditu FreeRunnerraren eskaerak. Horri route eta masquerade (NAT) izenak ematen dizkiote ingelesez.

Ez da zaila lan hori egitea, baina arazoak sor daitezke FreeRunnerra eta PCaren arteko azpisareak PCaren eta routerraren arteko azpisarearekin talka egiten badu. Azken finean PCak bi sare lokal dauzka, eta biak ongi bereizi behar ditu batera zein bestera era egokian bideratzeko informazioa.

Talka egoera ekidin behar da, horretarako PCaren eta routerraren arteko azpisarearen lehenego hiru zenbakiak FreeRunnerraren azpisarearen lehenengo hiru zenbakiekin ez dute bat etorri behar, alegia, routerraren azpisareak ez du eduki behar 192.168.0.### moduko helbiderik, eta hala baleuka aldatzea komeni da eta horren ordez 192.168.1.### moduko sarea jarri. Honi buruzko informazio gehiago [http://lists.openmoko.org/pipermail/support/2008-August/thread.html#1277 hemen] daukazu.

== Kontuan hartu beharrekoak ==

=== Suspentsioa ===

FreeRunnerra suspentsio egoeran jartzen denean (bateria aurrezteko egoeran) USB bidezko sarearen interfazea desaktibatzen du, beraz, USB bidez konektatu aurretik suspentsioa desaktibatzea komeni da, konexioa gal ez dezan.

=== Baina konexioaren izena zein da, "usb0" ala "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 "ifconfig -a" command, or use "dmesg" 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 an 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.

= 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>iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
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>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>sysctl net.ipv4.conf.eth2.proxy_arp=1</pre>

This assuming that eth2 is connected to ISP.

Then
<pre>ip link set usb0 up</pre>
or (deprecated)
<pre>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 reboot /etc/init.d/networking).
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 http://www.tapor.com/udpf/ - 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 [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] 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.

== 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 /etc/init/network-interface.conf 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 /etc/network/interfaces, make sure the device is marked 'auto'. Plugging and unplugging will then work automagically.

('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 [http://sebastian-bergmann.de/index.php?url=archives/801-OpenMoko-Freerunner-and-Ubuntu.html#feedback these instructions], 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.<br>
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.<br>
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 preferences dialog has a network section, under which a drop-down box appeasr which is labeled "Local network connected device." Select the freerunner, generally "Unknown device(usb0)" and 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

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.
-Tested in ubuntu 9:04--[[User:chrestomanci|David]] September 2009

Note: Firestarter needs to run as root.

=== 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) ===

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
## 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'''
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 [http://www.enricozini.org/2008/tips/autodock-freerunner.html Enrico Zini's solution].

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/

USB Networking/eu

2010-03-03T12:34:48Z

Joseba:

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

{{Languages|USB_Networking}}

{|align=left
|__TOC__
|}

= FreeRunnerra sarean USB konexio bidez erabiltzeko ezarpenak =

Zure FreeRunnerrera TCP/IP bidez komunikazioa ezarri ahal izateko oinarrizko ezaguera batzuek behar dira. Ez pentsa zaila denik, alderantziz, kasu gehienetan automatikoki funtzionatuko dizu. Hasteko FreeRunnerra eta PCa USB kablearen bidez lotu behar dira, USB kablearen mutur bakoitzean dagoen makina bakoitza (FreeRunnerra eta PCa) sare lokal (LAN) bateko bi makina dira. Alde batean FreeRunnerraren USB konexiodun sare txartela daukagu (besterik ezean 192.168.0.202 IP zenbakia izango duena) eta beste aldean PCa bera daukagu, honek ere USB bidezko sare lokalean IP bat edukiko du (besterik ezean 192.168.0.200).

Ohiko egoera batean, zure PCak badaki nola joan internetera, horretarako irteera atea dauka (gateway) eta bere IP zenbakia zein den badaki, azken finean gateway hori izango baita interneterako bidea emango diona. Informazio hori pizterakoan jaso du (dinamikoki DHCP bidez edo estatikoki), normalean router baten bidez (nahiz eta batzuetan zerbitzari lanak beste makina batek egiten dituen). FreeRunnerrak ere informazio hori behar du, eta zure PCak eman behar dio, gainera, zure PCak bideratu behar ditu FreeRunnerraren eskaerak. Horri route eta masquerade (NAT) izenak ematen dizkiote ingelesez.

Ez da zaila lan hori egitea, baina arazoak sor daitezke FreeRunnerra eta PCaren arteko azpisareak PCaren eta routerraren arteko azpisarearekin talka egiten badu. Azken finean PCak bi sare lokal dauzka, eta biak ongi bereizi behar ditu batera zein bestera era egokian bideratzeko informazioa.

Talka egoera ekidin behar da, horretarako PCaren eta routerraren arteko azpisarearen lehenego hiru zenbakiak FreeRunnerraren azpisarearen lehenengo hiru zenbakiekin ez dute bat etorri behar, alegia, routerraren azpisareak ez du eduki behar 192.168.0.### moduko helbiderik, eta hala baleuka aldatzea komeni da eta horren ordez 192.168.1.### moduko sarea jarri. Honi buruzko informazio gehiago [http://lists.openmoko.org/pipermail/support/2008-August/thread.html#1277 hemen] daukazu.

== 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 "ifconfig -a" command, or use "dmesg" 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 an 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.

= 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>iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
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>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>sysctl net.ipv4.conf.eth2.proxy_arp=1</pre>

This assuming that eth2 is connected to ISP.

Then
<pre>ip link set usb0 up</pre>
or (deprecated)
<pre>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 reboot /etc/init.d/networking).
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 http://www.tapor.com/udpf/ - 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 [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] 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.

== 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 /etc/init/network-interface.conf 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 /etc/network/interfaces, make sure the device is marked 'auto'. Plugging and unplugging will then work automagically.

('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 [http://sebastian-bergmann.de/index.php?url=archives/801-OpenMoko-Freerunner-and-Ubuntu.html#feedback these instructions], 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.<br>
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.<br>
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 preferences dialog has a network section, under which a drop-down box appeasr which is labeled "Local network connected device." Select the freerunner, generally "Unknown device(usb0)" and 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

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.
-Tested in ubuntu 9:04--[[User:chrestomanci|David]] September 2009

Note: Firestarter needs to run as root.

=== 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) ===

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
## 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'''
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 [http://www.enricozini.org/2008/tips/autodock-freerunner.html Enrico Zini's solution].

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/

USB Networking/eu

2010-03-03T12:25:22Z

Joseba:

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

{{Languages|USB_Networking}}

{|align=left
|__TOC__
|}

= FreeRunnerra sarean USB konexio bidez erabiltzeko ezarpenak =

Zure FreeRunnerrera TCP/IP bidez komunikazioa ezarri ahal izateko oinarrizko ezaguera batzuek behar dira. Ez pentsa zaila denik, alderantziz, kasu gehienetan automatikoki funtzionatuko dizu. Hasteko FreeRunnerra eta PCa USB kablearen bidez lotu behar dira, USB kablearen mutur bakoitzean dagoen makina bakoitza (FreeRunnerra eta PCa) sare lokal (LAN) bateko bi makina dira. Alde batean FreeRunnerraren USB konexiodun sare txartela daukagu (besterik ezean 192.168.0.202 IP zenbakia izango duena) eta beste aldean PCa bera daukagu, honek ere USB bidezko sare lokalean IP bat edukiko du (besterik ezean 192.168.0.200).

Ohiko egoera batean, zure PCak badaki nola joan internetera, horretarako irteera atea dauka (gateway) eta bere IP zenbakia zein den badaki, azken finean gateway hori izango baita interneterako bidea emango diona. Informazio hori pizterakoan jaso du (dinamikoki DHCP bidez edo estatikoki), normalean router baten bidez (nahiz eta batzuetan zerbitzari lanak beste makina batek egiten dituen). FreeRunnerrak ere informazio hori behar du, eta zure PCak eman behar dio, gainera, zure PCak bideratu behar ditu FreeRunnerraren eskaerak. Horri route eta masquerade (NAT) izenak ematen dizkiote ingelesez.

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 "ifconfig -a" command, or use "dmesg" 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 an 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.

= 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>iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
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>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>sysctl net.ipv4.conf.eth2.proxy_arp=1</pre>

This assuming that eth2 is connected to ISP.

Then
<pre>ip link set usb0 up</pre>
or (deprecated)
<pre>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 reboot /etc/init.d/networking).
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 http://www.tapor.com/udpf/ - 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 [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] 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.

== 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 /etc/init/network-interface.conf 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 /etc/network/interfaces, make sure the device is marked 'auto'. Plugging and unplugging will then work automagically.

('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 [http://sebastian-bergmann.de/index.php?url=archives/801-OpenMoko-Freerunner-and-Ubuntu.html#feedback these instructions], 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.<br>
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.<br>
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 preferences dialog has a network section, under which a drop-down box appeasr which is labeled "Local network connected device." Select the freerunner, generally "Unknown device(usb0)" and 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

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.
-Tested in ubuntu 9:04--[[User:chrestomanci|David]] September 2009

Note: Firestarter needs to run as root.

=== 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) ===

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
## 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'''
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 [http://www.enricozini.org/2008/tips/autodock-freerunner.html Enrico Zini's solution].

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/

USB Networking/eu

2010-03-03T11:42:13Z

Joseba: New page: Category:USB software Category:Implemented {{Languages|USB_Networking}} {|align=left |__TOC__ |} = FreeRunnerra sarean USB konexio bidez erabiltzeko ezarpenak = Zure FreeRunner...

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

{{Languages|USB_Networking}}

{|align=left
|__TOC__
|}

= FreeRunnerra sarean USB konexio bidez erabiltzeko ezarpenak =

Zure FreeRunnerrera TCP/IP bidez komunikazioa ezarri ahal izateko oinarrizko ezaguera batzuek behar dira. Ez pentsa zaila denik, alderantziz, kasu gehienetan automatikoki funtzionatuko dizu. Hasteko FreeRunnerra eta PCa USB kablearen bidez lotu behar dira, USB kablearen mutur bakoitzean dagoen makina bakoitza (FreeRunnerra eta PCa) sare lokal (LAN) bateko bi makina dira. Alde batean FreeRunnerraren USB konexiodun sare txartela daukagu (besterik ezean 192.168.0.202 IP zenbakia izango duena) eta beste aldean PCa bera daukagu, honek ere USB bidezko sare lokalean IP bat edukiko du (besterik ezean 192.168.0.200).

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 "ifconfig -a" command, or use "dmesg" 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 an 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.

= 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>iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
sysctl -w net.ipv4.ip_forward=1
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>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>sysctl net.ipv4.conf.eth2.proxy_arp=1</pre>

This assuming that eth2 is connected to ISP.

Then
<pre>ip link set usb0 up</pre>
or (deprecated)
<pre>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 reboot /etc/init.d/networking).
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 http://www.tapor.com/udpf/ - 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 [http://blog.haerwu.biz/2007/03/22/hotpluging-usbnet/ Hotplugging usbnet] 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.

== 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 /etc/init/network-interface.conf 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 /etc/network/interfaces, make sure the device is marked 'auto'. Plugging and unplugging will then work automagically.

('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 [http://sebastian-bergmann.de/index.php?url=archives/801-OpenMoko-Freerunner-and-Ubuntu.html#feedback these instructions], 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.<br>
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.<br>
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 preferences dialog has a network section, under which a drop-down box appeasr which is labeled "Local network connected device." Select the freerunner, generally "Unknown device(usb0)" and 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

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.
-Tested in ubuntu 9:04--[[User:chrestomanci|David]] September 2009

Note: Firestarter needs to run as root.

=== 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) ===

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
## 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'''
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 [http://www.enricozini.org/2008/tips/autodock-freerunner.html Enrico Zini's solution].

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/

Qt Moko/eu

2010-03-02T23:23:21Z

Joseba:

{{Languages|Qt_Moko}}
===Qt Moko===
Qt Moko [[Debian]]-en oinarritutako Openmokoren [[Neo Freerunner]] mugikorrerako banaketa da. Telefonoaren erabilera eta erabiltzailearen interfazea [[Qt Extended Improved]]-en oinarritzen dira, hau gehienetan [[Qtopia / Qt Extended on FreeRunner|Qtopia]] izenaz ezagutzen da. QtMokoren wikia can [http://qtmoko.org/ honakoan] aurkituko duzu.

===Deskarga===
Honako fitxategiak deskargatu zure mahaigaineko PCra [https://sourceforge.net/projects/qtmoko/files/ radekp download] gunetik:
* latest
** https://sourceforge.net/projects/qtmoko/files/

===Instalazioa===
QtMoko-tik kernel irudia zure freerunnera flassheatzen baduzu, kernela eta fitxategi sistema instalatu behar dituzu (biak). Baina [[Qi]] instalatuta baldin badaukazu, orduan mikroSD txartelean instala zenezake QtMoko. Azken bide horrek sistema batekin baino gehiagorekin lan egiteko aukera emango dizu,GRUBak ordenagailuetan sistema eragile bat baino gehiago erabiltzeko aukera ematen duenaren antzera. SD txartela aldatzearekin banaketa ezberdin bat erabil baitaiteke.

Itzali freerunnerra eta sakatu AUX eta pizteko botoia biak batera. Freerrunnerrak honako U-Boot menua erakutsiko dizu:

*** BOOT MENU (NOR) ***

Boot
Boot from Mirco SD (FAT/ext2)
Set Console to USB
Set Console to Serial
Reboot
Power Off

Egoera honetan 30 segundo besterik ez da egongo. Denbora tarte horretan <tt>dfu-util</tt> hasi beharko duzu, bestela beti bezala, betiko sistemarekin, hasiko baita freerunnerra. Kernelaren irudia flasheatu nahi baduzu (zure PCan root baimenekin egon beharko duzu) U-Boot menuak irauten dituen 30 segundo horietan honako agindua eragin beharko duzu:

# Neo FreeRunnerrerako:
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-v13.bin

Eta bigarrenik, root fitxategi sistema honakoaren bidez:

# Neo FreeRunnerrerako:
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D qtmoko-debian-v13.jffs2

===Lehendabiziko abiaratzea===
Instalazioa errorerik gabe egin ondoren FreeRunnerra berrabiarazi behar da, eta ukimenezko pantaila kalibratu behar da. Orduan ikusiko duzu instalatutako ''Qt Moko'' berria zure gailuan.
[[Image:qtmokomain.png|200px|thumb|Qt Moko lehenengo aldiz abiarazitakoan]]

===Konektatu===
FreeRunnerrera konektatu nahi baduzu, sare konexioa ezarri behar duzu (ikusi [[USB Networking]]) USB kable bidez eta honako agindua eragin zure PCko terminalean:
desktop# ssh -X -l root 192.168.0.202

root erabiltzaileak hasieran ez dauka pasahitzik, baina zeuk ezar diezaikoezu segurtasun kontuak kezkatzen bazaituzte, bereziki ssh deabrua martxan jartzen duzunean WLAN sare interfazean. Linux makinetan egin ohi den moduan ezar dezakezu pasahitza:
neo# passwd
USB kable bidezko internet konexioa ezarri baduzu, biltegi edo errepositorioko datuak eguneratzea komeni da:
neo# apt-get update
Zure FreeRunnerrean Internet konexioa daukazun edo ez jakiteko OpenMoko sare zerbitzariari ping egin diezaiokezu:I
neo# ping 88.198.93.221
neo# ping wiki.openmoko.org
Lehenengoak ondo egiten badu, baina bigarrenak gaizki, DNS zerbitzaria da ez dabilkizuna, begira ezazu [[USB Networking]].

===Ordua eta data ezarri===
Data eta ordua zeure Linuxetik ezar ditzakezu honako aginduaren bidez:
<pre>
ssh root@openmoko "date -us @`date -u +%s`"
</pre>
NTP Bezero baten bidez ezarri nahi baduzu, ondoko paketea instalatu, baldin eta sare konexioren bat baldin badaukazu (ikusi [[USB Networking]])
<pre>
# apt-get install ntpdate
# ntpdate-debian
</pre>
Gehiago jakiteko ikusi [[Setting Date and Time]].

[[Category:Qt| ]]

Main Page/eu

2010-03-02T23:18:16Z

Joseba:

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

'''Openmoko™''' proiektu bat da, bere helburua [[Source Code|software libre]] bidez funtzionatuko duen telefono mugikorra lortzea da. Gaur egun [[Neo FreeRunner]] telefonoa saltzen da erabiltzaile aurreratuentzat, eta aplikazioen garapenak aurrera egiten duen heinean edonork erosteko moduan egongo da. Dagoenekoz Gnu/linux sistema erabiltzera ohituta dauden erabiltzaileek ez dute zailtasun handirik [[Neo FreeRunner]] telefono mugikorra erabiltzeko.

* [[Introduction/eu|Sarrera]]
* [[Why Openmoko|Zergatik Openmoko?]]

[[More informations|informazio gehiago]]

===Bat egin===
Boluntarioz osatutako komunitateak gidatzen du Openmoko proiektua. Gaitasuna baldin badaukazu, gure helburuekin bat egizu eta zeure alea jar ezazu. Helburu handiak dauzkagu eta guztion laguntza beharrezkoa da.

* [[Community Resources|Komunitatearen baliabideak eta ataria]]
* [[Gta02-core|gta02 hardwarearen berrikuspena egiten lagundu]]
* [[Create User Manuals|erabiltzaileentzat eskuliburuak sortu]] bai [[Distributions|banaketentzat]] bai eta [[Applications|aplikazioentzat]] ere
* Areagotu [[OpenmokoFramework|Openmoko euskarri]] gisa erabiltzen den [http://www.freesmartphone.org FSO] bitarteko multi-saltzaile eta multi-devicea.
===Nola erosi===
Neo FreeRunner telefono mugikorra hainbat [[distributors|banatzailek]] saltzen du munduan zehar.

Jo [[Getting Openmoko|Openmokoa erosi]] orrira informazio gehiago nahi baduzu.

----

====Latest News====

{{News}}
[[News Archive|berriak...]]

----

Qt Moko/eu

2010-02-24T13:04:16Z

Joseba:

{{Languages|QtMoko}}
===Qt Moko===
Qt Moko [[Debian]]-en oinarritutako Openmokoren [[Neo Freerunner]] mugikorrerako banaketa da. Telefonoaren erabilera eta erabiltzailearen interfazea [[Qt Extended Improved]]-en oinarritzen dira, hau gehienetan [[Qtopia / Qt Extended on FreeRunner|Qtopia]] izenaz ezagutzen da. QtMokoren wikia can [http://qtmoko.org/ honakoan] aurkituko duzu.

===Deskarga===
Honako fitxategiak deskargatu zure mahaigaineko PCra [https://sourceforge.net/projects/qtmoko/files/ radekp download] gunetik:
* latest
** https://sourceforge.net/projects/qtmoko/files/

===Instalazioa===
QtMoko-tik kernel irudia zure freerunnera flassheatzen baduzu, kernela eta fitxategi sistema instalatu behar dituzu (biak). Baina [[Qi]] instalatuta baldin badaukazu, orduan mikroSD txartelean instala zenezake QtMoko. Azken bide horrek sistema batekin baino gehiagorekin lan egiteko aukera emango dizu,GRUBak ordenagailuetan sistema eragile bat baino gehiago erabiltzeko aukera ematen duenaren antzera. SD txartela aldatzearekin banaketa ezberdin bat erabil baitaiteke.

Itzali freerunnerra eta sakatu AUX eta pizteko botoia biak batera. Freerrunnerrak honako U-Boot menua erakutsiko dizu:

*** BOOT MENU (NOR) ***

Boot
Boot from Mirco SD (FAT/ext2)
Set Console to USB
Set Console to Serial
Reboot
Power Off

Egoera honetan 30 segundo besterik ez da egongo. Denbora tarte horretan <tt>dfu-util</tt> hasi beharko duzu, bestela beti bezala, betiko sistemarekin, hasiko baita freerunnerra. Kernelaren irudia flasheatu nahi baduzu (zure PCan root baimenekin egon beharko duzu) U-Boot menuak irauten dituen 30 segundo horietan honako agindua eragin beharko duzu:

# Neo FreeRunnerrerako:
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-v13.bin

Eta bigarrenik, root fitxategi sistema honakoaren bidez:

# Neo FreeRunnerrerako:
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D qtmoko-debian-v13.jffs2

===Lehendabiziko abiaratzea===
Instalazioa errorerik gabe egin ondoren FreeRunnerra berrabiarazi behar da, eta ukimenezko pantaila kalibratu behar da. Orduan ikusiko duzu instalatutako ''Qt Moko'' berria zure gailuan.
[[Image:qtmokomain.png|200px|thumb|Qt Moko lehenengo aldiz abiarazitakoan]]

===Konektatu===
FreeRunnerrera konektatu nahi baduzu, sare konexioa ezarri behar duzu (ikusi [[USB Networking]]) USB kable bidez eta honako agindua eragin zure PCko terminalean:
desktop# ssh -X -l root 192.168.0.202

root erabiltzaileak hasieran ez dauka pasahitzik, baina zeuk ezar diezaikoezu segurtasun kontuak kezkatzen bazaituzte, bereziki ssh deabrua martxan jartzen duzunean WLAN sare interfazean. Linux makinetan egin ohi den moduan ezar dezakezu pasahitza:
neo# passwd
USB kable bidezko internet konexioa ezarri baduzu, biltegi edo errepositorioko datuak eguneratzea komeni da:
neo# apt-get update
Zure FreeRunnerrean Internet konexioa daukazun edo ez jakiteko OpenMoko sare zerbitzariari ping egin diezaiokezu:I
neo# ping 88.198.93.221
neo# ping wiki.openmoko.org
Lehenengoak ondo egiten badu, baina bigarrenak gaizki, DNS zerbitzaria da ez dabilkizuna, begira ezazu [[USB Networking]].

===Ordua eta data ezarri===
Data eta ordua zeure Linuxetik ezar ditzakezu honako aginduaren bidez:
<pre>
ssh root@openmoko "date -us @`date -u +%s`"
</pre>
NTP Bezero baten bidez ezarri nahi baduzu, ondoko paketea instalatu, baldin eta sare konexioren bat baldin badaukazu (ikusi [[USB Networking]])
<pre>
# apt-get install ntpdate
# ntpdate-debian
</pre>
Gehiago jakiteko ikusi [[Setting Date and Time]].

[[Category:Qt| ]]

Qt Moko/eu

2010-02-24T13:03:22Z

Joseba:

{{Languages}}
===Qt Moko===
Qt Moko [[Debian]]-en oinarritutako Openmokoren [[Neo Freerunner]] mugikorrerako banaketa da. Telefonoaren erabilera eta erabiltzailearen interfazea [[Qt Extended Improved]]-en oinarritzen dira, hau gehienetan [[Qtopia / Qt Extended on FreeRunner|Qtopia]] izenaz ezagutzen da. QtMokoren wikia can [http://qtmoko.org/ honakoan] aurkituko duzu.

===Deskarga===
Honako fitxategiak deskargatu zure mahaigaineko PCra [https://sourceforge.net/projects/qtmoko/files/ radekp download] gunetik:
* latest
** https://sourceforge.net/projects/qtmoko/files/

===Instalazioa===
QtMoko-tik kernel irudia zure freerunnera flassheatzen baduzu, kernela eta fitxategi sistema instalatu behar dituzu (biak). Baina [[Qi]] instalatuta baldin badaukazu, orduan mikroSD txartelean instala zenezake QtMoko. Azken bide horrek sistema batekin baino gehiagorekin lan egiteko aukera emango dizu,GRUBak ordenagailuetan sistema eragile bat baino gehiago erabiltzeko aukera ematen duenaren antzera. SD txartela aldatzearekin banaketa ezberdin bat erabil baitaiteke.

Itzali freerunnerra eta sakatu AUX eta pizteko botoia biak batera. Freerrunnerrak honako U-Boot menua erakutsiko dizu:

*** BOOT MENU (NOR) ***

Boot
Boot from Mirco SD (FAT/ext2)
Set Console to USB
Set Console to Serial
Reboot
Power Off

Egoera honetan 30 segundo besterik ez da egongo. Denbora tarte horretan <tt>dfu-util</tt> hasi beharko duzu, bestela beti bezala, betiko sistemarekin, hasiko baita freerunnerra. Kernelaren irudia flasheatu nahi baduzu (zure PCan root baimenekin egon beharko duzu) U-Boot menuak irauten dituen 30 segundo horietan honako agindua eragin beharko duzu:

# Neo FreeRunnerrerako:
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-v13.bin

Eta bigarrenik, root fitxategi sistema honakoaren bidez:

# Neo FreeRunnerrerako:
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D qtmoko-debian-v13.jffs2

===Lehendabiziko abiaratzea===
Instalazioa errorerik gabe egin ondoren FreeRunnerra berrabiarazi behar da, eta ukimenezko pantaila kalibratu behar da. Orduan ikusiko duzu instalatutako ''Qt Moko'' berria zure gailuan.
[[Image:qtmokomain.png|200px|thumb|Qt Moko lehenengo aldiz abiarazitakoan]]

===Konektatu===
FreeRunnerrera konektatu nahi baduzu, sare konexioa ezarri behar duzu (ikusi [[USB Networking]]) USB kable bidez eta honako agindua eragin zure PCko terminalean:
desktop# ssh -X -l root 192.168.0.202

root erabiltzaileak hasieran ez dauka pasahitzik, baina zeuk ezar diezaikoezu segurtasun kontuak kezkatzen bazaituzte, bereziki ssh deabrua martxan jartzen duzunean WLAN sare interfazean. Linux makinetan egin ohi den moduan ezar dezakezu pasahitza:
neo# passwd
USB kable bidezko internet konexioa ezarri baduzu, biltegi edo errepositorioko datuak eguneratzea komeni da:
neo# apt-get update
Zure FreeRunnerrean Internet konexioa daukazun edo ez jakiteko OpenMoko sare zerbitzariari ping egin diezaiokezu:I
neo# ping 88.198.93.221
neo# ping wiki.openmoko.org
Lehenengoak ondo egiten badu, baina bigarrenak gaizki, DNS zerbitzaria da ez dabilkizuna, begira ezazu [[USB Networking]].

===Ordua eta data ezarri===
Data eta ordua zeure Linuxetik ezar ditzakezu honako aginduaren bidez:
<pre>
ssh root@openmoko "date -us @`date -u +%s`"
</pre>
NTP Bezero baten bidez ezarri nahi baduzu, ondoko paketea instalatu, baldin eta sare konexioren bat baldin badaukazu (ikusi [[USB Networking]])
<pre>
# apt-get install ntpdate
# ntpdate-debian
</pre>
Gehiago jakiteko ikusi [[Setting Date and Time]].

[[Category:Qt| ]]

Qt Moko/eu

2010-02-24T13:02:51Z

Joseba: New page: {{Languages|Manuals/SHR}} ===Qt Moko=== Qt Moko Debian-en oinarritutako Openmokoren Neo Freerunner mugikorrerako banaketa da. Telefonoaren erabilera eta erabiltzailearen interfazea...

{{Languages|Manuals/SHR}}
===Qt Moko===
Qt Moko [[Debian]]-en oinarritutako Openmokoren [[Neo Freerunner]] mugikorrerako banaketa da. Telefonoaren erabilera eta erabiltzailearen interfazea [[Qt Extended Improved]]-en oinarritzen dira, hau gehienetan [[Qtopia / Qt Extended on FreeRunner|Qtopia]] izenaz ezagutzen da. QtMokoren wikia can [http://qtmoko.org/ honakoan] aurkituko duzu.

===Deskarga===
Honako fitxategiak deskargatu zure mahaigaineko PCra [https://sourceforge.net/projects/qtmoko/files/ radekp download] gunetik:
* latest
** https://sourceforge.net/projects/qtmoko/files/

===Instalazioa===
QtMoko-tik kernel irudia zure freerunnera flassheatzen baduzu, kernela eta fitxategi sistema instalatu behar dituzu (biak). Baina [[Qi]] instalatuta baldin badaukazu, orduan mikroSD txartelean instala zenezake QtMoko. Azken bide horrek sistema batekin baino gehiagorekin lan egiteko aukera emango dizu,GRUBak ordenagailuetan sistema eragile bat baino gehiago erabiltzeko aukera ematen duenaren antzera. SD txartela aldatzearekin banaketa ezberdin bat erabil baitaiteke.

Itzali freerunnerra eta sakatu AUX eta pizteko botoia biak batera. Freerrunnerrak honako U-Boot menua erakutsiko dizu:

*** BOOT MENU (NOR) ***

Boot
Boot from Mirco SD (FAT/ext2)
Set Console to USB
Set Console to Serial
Reboot
Power Off

Egoera honetan 30 segundo besterik ez da egongo. Denbora tarte horretan <tt>dfu-util</tt> hasi beharko duzu, bestela beti bezala, betiko sistemarekin, hasiko baita freerunnerra. Kernelaren irudia flasheatu nahi baduzu (zure PCan root baimenekin egon beharko duzu) U-Boot menuak irauten dituen 30 segundo horietan honako agindua eragin beharko duzu:

# Neo FreeRunnerrerako:
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-v13.bin

Eta bigarrenik, root fitxategi sistema honakoaren bidez:

# Neo FreeRunnerrerako:
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D qtmoko-debian-v13.jffs2

===Lehendabiziko abiaratzea===
Instalazioa errorerik gabe egin ondoren FreeRunnerra berrabiarazi behar da, eta ukimenezko pantaila kalibratu behar da. Orduan ikusiko duzu instalatutako ''Qt Moko'' berria zure gailuan.
[[Image:qtmokomain.png|200px|thumb|Qt Moko lehenengo aldiz abiarazitakoan]]

===Konektatu===
FreeRunnerrera konektatu nahi baduzu, sare konexioa ezarri behar duzu (ikusi [[USB Networking]]) USB kable bidez eta honako agindua eragin zure PCko terminalean:
desktop# ssh -X -l root 192.168.0.202

root erabiltzaileak hasieran ez dauka pasahitzik, baina zeuk ezar diezaikoezu segurtasun kontuak kezkatzen bazaituzte, bereziki ssh deabrua martxan jartzen duzunean WLAN sare interfazean. Linux makinetan egin ohi den moduan ezar dezakezu pasahitza:
neo# passwd
USB kable bidezko internet konexioa ezarri baduzu, biltegi edo errepositorioko datuak eguneratzea komeni da:
neo# apt-get update
Zure FreeRunnerrean Internet konexioa daukazun edo ez jakiteko OpenMoko sare zerbitzariari ping egin diezaiokezu:I
neo# ping 88.198.93.221
neo# ping wiki.openmoko.org
Lehenengoak ondo egiten badu, baina bigarrenak gaizki, DNS zerbitzaria da ez dabilkizuna, begira ezazu [[USB Networking]].

===Ordua eta data ezarri===
Data eta ordua zeure Linuxetik ezar ditzakezu honako aginduaren bidez:
<pre>
ssh root@openmoko "date -us @`date -u +%s`"
</pre>
NTP Bezero baten bidez ezarri nahi baduzu, ondoko paketea instalatu, baldin eta sare konexioren bat baldin badaukazu (ikusi [[USB Networking]])
<pre>
# apt-get install ntpdate
# ntpdate-debian
</pre>
Gehiago jakiteko ikusi [[Setting Date and Time]].

[[Category:Qt| ]]

QtMoko

2010-02-24T13:02:31Z

Joseba:

{{Languages}}
===Qt Moko===
Qt Moko is [[Debian]] based distribution for Openmoko [[Neo FreeRunner]] phone. Phone and user interface is based on [[Qt Extended Improved]] formerly known as [[Qtopia / Qt Extended on FreeRunner|Qtopia]]. QtMoko wiki can be found [http://qtmoko.org/ here].

===Download===
Download the following files from [https://sourceforge.net/projects/qtmoko/files/ radekp download] to you desktop computer:
* latest
** https://sourceforge.net/projects/qtmoko/files/

===Installation===
If you flash the freerunner with a kernel image from Qt Moko, then you must install the kernel and the root file system. If you have [[Qi]] installed then you can install the Qt Moko on the SD card. This seems to be useful if you want to work with different distribution and you can change the distribution just by changing the Mirco SD card in your freerunner.

Switch off your freerunner and press AUX and Power-On button at the same time. Your freerunner is showing the following U-Boot Menu:

*** BOOT MENU (NOR) ***

Boot
Boot from Mirco SD (FAT/ext2)
Set Console to USB
Set Console to Serial
Reboot
Power Off

The freerunner will stay in this mode for only 30 sec. Within this time you have to start <tt>dfu-util</tt>. Otherwise the freerunner will start to boot the installed operating system.
If you want to flash the kernel image (you will need to be root on you PC) then you have to start the following command in the 30sec your see the BOOT MENU:

# for the Neo FreeRunner:
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-v13.bin

and finally the root fs with this one:

# for the Neo FreeRunner:
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D qtmoko-debian-v13.jffs2

===First Boot===
After finishing the installation without errors you have to start the freerunner and calibrate the touch screen. The you see the installed ''Qt Moko'' on your device.
[[Image:qtmokomain.png|200px|thumb|Qt Moko after first boot]]

===Login===
If you want to login to your freerunner set up network connection (see [[USB Networking]]) with USB cable and start:
desktop# ssh -X -l root 192.168.0.202

The root password is empty so set it for security reason especially when you open the ssh-daemon on the WLAN network interface. Define root password as usual on a linux box with
neo# passwd
If you have established the internet connection via USB cable then update the repository data:
neo# apt-get update
If you want to check if the internet connection is available on your freerunner ping the OpenMoko web server with:
neo# ping 88.198.93.221
neo# ping wiki.openmoko.org
If the first ping works and the second doesn't then check the DNS server settings (see [[USB Networking]]).

===Setting Time and Date===
Set the time and date on from your linux box with
<pre>
ssh root@openmoko "date -us @`date -u +%s`"
</pre>
If you want to set the time with a NTP Client install the following package, if you have a network connection available (see [[USB Networking]])
<pre>
# apt-get install ntpdate
# ntpdate-debian
</pre>
For further detail see [[Setting Date and Time]].

[[Category:Qt| ]]

Manuals/QtMoko/eu

2010-02-24T12:58:39Z

Joseba:

Manuals/QtMoko/eu

2010-02-24T12:54:49Z

Joseba:

{{Languages|Manuals/SHR}}
===Qt Moko===
Qt Moko [[Debian]]-en oinarritutako Openmoko [Neo Freerunner]] mugikorrerako banaketa da. Telefonoaren erabilera eta erabiltzailearen interfazea [[Qt Extended Improved]]-en oinarritzen dira, hau gehienetan [[Qtopia / Qt Extended on FreeRunner|Qtopia]] izenaz ezagutzen da. QtMokoren wikia can [http://qtmoko.org/ honakoan] aurkituko duzu.

===Deskarga===
Honako fitxategiak deskargatu zure mahaigaineko PCra [https://sourceforge.net/projects/qtmoko/files/ radekp download] gunetik:
* latest
** https://sourceforge.net/projects/qtmoko/files/

===Instalazioa===
QtMoko-tik kernel irudia zure freerunnera flassheatzen baduzu, kernela eta fitxategi sistema instalatu behar dituzu (biak). Baina [[Qi]] instalatuta baldin badaukazu, orduan mikroSD txartelean instala zenezake QtMoko. Azken bide horrek sistema batekin baino gehiagorekin lan egiteko aukera emango dizu,GRUBak ordenagailuetan sistema eragile bat baino gehiago erabiltzeko aukera ematen duenaren antzera. SD txartela aldatzearekin banaketa ezberdin bat erabil baitaiteke.

Itzali freerunnerra eta sakatu AUX eta pizteko botoia biak batera. Freerrunnerrak honako U-Boot menua erakutsiko dizu:

*** BOOT MENU (NOR) ***

Boot
Boot from Mirco SD (FAT/ext2)
Set Console to USB
Set Console to Serial
Reboot
Power Off

Egoera honetan 30 segundo besterik ez da egongo. Denbora tarte horretan <tt>dfu-util</tt> hasi beharko duzu, bestela beti bezala, betiko sistemarekin, hasiko baita freerunnerra. Kernelaren irudia flasheatu nahi baduzu (zure PCan root baimenekin egon beharko duzu) U-Boot menuak irauten dituen 30 segundo horietan honako agindua eragin beharko duzu:

# Neo FreeRunnerrerako:
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-v13.bin

Eta bigarrenik, root fitxategi sistema honakoaren bidez:

# Neo FreeRunnerrerako:
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D qtmoko-debian-v13.jffs2

===Lehendabiziko abiaratzea===
Instalazioa errorerik gabe egin ondoren FreeRunnerra berrabiarazi behar da, eta ukimenezko pantaila kalibratu behar da. Orduan ikusiko duzu instalatutako ''Qt Moko'' berria zure gailuan.
[[Image:qtmokomain.png|200px|thumb|Qt Moko lehenengo aldiz abiarazitakoan]]

===Konektatu===
FreeRunnerrera konektatu nahi baduzu, sare konexioa ezarri behar duzu (ikusi [[USB Networking]]) USB kable bidez eta honako agindua eragin zure PCko terminalean:
desktop# ssh -X -l root 192.168.0.202

root erabiltzaileak hasieran ez dauka pasahitzik, baina zeuk ezar diezaikoezu segurtasun kontuak kezkatzen bazaituzte, bereziki ssh deabrua martxan jartzen duzunean WLAN sare interfazean. Linux makinetan egin ohi den moduan ezar dezakezu pasahitza:
neo# passwd
USB kable bidezko internet konexioa ezarri baduzu, biltegi edo errepositorioko datuak eguneratzea komeni da:
neo# apt-get update
Zure FreeRunnerrean Internet konexioa daukazun edo ez jakiteko OpenMoko sare zerbitzariari ping egin diezaiokezu:I
neo# ping 88.198.93.221
neo# ping wiki.openmoko.org
Lehenengoak ondo egiten badu, baina bigarrenak gaizki, DNS zerbitzaria da ez dabilkizuna, begira ezazu [[USB Networking]].

===Setting Time and Date===
Set the time and date on from your linux box with
<pre>
ssh root@openmoko "date -us @`date -u +%s`"
</pre>
If you want to set the time with a NTP Client install the following package, if you have a network connection available (see [[USB Networking]])
<pre>
# apt-get install ntpdate
# ntpdate-debian
</pre>
For further detail see [[Setting Date and Time]].

[[Category:Qt| ]]

Manuals/QtMoko/eu

2010-02-24T11:44:07Z

Joseba: New page: {{Languages|Manuals/SHR}} ===Qt Moko=== Qt Moko Debian-en oinarritutako Openmoko [Neo Freerunner]] mugikorrerako banaketa da. Telefonoaren erabilera eta erabiltzailearen interfazea [[Q...

{{Languages|Manuals/SHR}}
===Qt Moko===
Qt Moko [[Debian]]-en oinarritutako Openmoko [Neo Freerunner]] mugikorrerako banaketa da. Telefonoaren erabilera eta erabiltzailearen interfazea [[Qt Extended Improved]]-en oinarritzen dira, hau gehienetan [[Qtopia / Qt Extended on FreeRunner|Qtopia]] izenaz ezagutzen da. QtMokoren wikia can [http://qtmoko.org/ honakoan] aurkituko duzu.

===Deskarga===
Honako fitxategiak deskargatu zure mahaigaineko konputagailura [https://sourceforge.net/projects/qtmoko/files/ radekp download] gunetik:
* latest
** https://sourceforge.net/projects/qtmoko/files/

===Instalazioa===
QtMoko-tik kernel irudia zure freerunnera flassheatzen baduzu, kernela eta fitxategi sistema instalatu behar dituzu (biak). Baina [[Qi]] instalatuta baldin badaukazu, orduan mikroSD txartelean instala zenezake QtMoko. Azken bide horrek sistema batekin baino gehiagorekin lan egiteko aukera emango dizu,GRUBak ordenagailuetan sistema eragile bat baino gehiago erabiltzeko aukera ematen duenaren antzera. SD txartela aldatzearekin banaketa ezberdin bat erabil baitaiteke.

Itzali freerunnerra eta sakatu AUX eta pizteko botoia biak batera. Freerrunnerrak honako U-Boot menua erakutsiko dizu:

*** BOOT MENU (NOR) ***

Boot
Boot from Mirco SD (FAT/ext2)
Set Console to USB
Set Console to Serial
Reboot
Power Off

Egoera honetan 30 segundo besterik ez da egongo. Denbora tarte horretan <tt>dfu-util</tt> hasi beharko duzu, bestela beti bezala, betiko sistemarekin, hasiko baita freerunnerra. Kernelaren irudia flasheatu nahi baduzu (zure PCan root baimenekin egon beharko duzu) U-Boot menuak irauten dituen 30 segundo horietan honako agindua eragin beharko duzu:

# for the Neo FreeRunner:
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-v13.bin

and finally the root fs with this one:

# for the Neo FreeRunner:
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D qtmoko-debian-v13.jffs2

===First Boot===
After finishing the installation without errors you have to start the freerunner and calibrate the touch screen. The you see the installed ''Qt Moko'' on your device.
[[Image:qtmokomain.png|200px|thumb|Qt Moko after first boot]]

===Login===
If you want to login to your freerunner set up network connection (see [[USB Networking]]) with USB cable and start:
desktop# ssh -X -l root 192.168.0.202

The root password is empty so set it for security reason especially when you open the ssh-daemon on the WLAN network interface. Define root password as usual on a linux box with
neo# passwd
If you have established the internet connection via USB cable then update the repository data:
neo# apt-get update
If you want to check if the internet connection is available on your freerunner ping the OpenMoko web server with:
neo# ping 88.198.93.221
neo# ping wiki.openmoko.org
If the first ping works and the second doesn't then check the DNS server settings (see [[USB Networking]]).

===Setting Time and Date===
Set the time and date on from your linux box with
<pre>
ssh root@openmoko "date -us @`date -u +%s`"
</pre>
If you want to set the time with a NTP Client install the following package, if you have a network connection available (see [[USB Networking]])
<pre>
# apt-get install ntpdate
# ntpdate-debian
</pre>
For further detail see [[Setting Date and Time]].

[[Category:Qt| ]]

QtMoko

2010-02-24T11:21:55Z

Joseba:

{{Languages|Manuals/SHR}}
===Qt Moko===
Qt Moko is [[Debian]] based distribution for Openmoko [[Neo FreeRunner]] phone. Phone and user interface is based on [[Qt Extended Improved]] formerly known as [[Qtopia / Qt Extended on FreeRunner|Qtopia]]. QtMoko wiki can be found [http://qtmoko.org/ here].

===Download===
Download the following files from [https://sourceforge.net/projects/qtmoko/files/ radekp download] to you desktop computer:
* latest
** https://sourceforge.net/projects/qtmoko/files/

===Installation===
If you flash the freerunner with a kernel image from Qt Moko, then you must install the kernel and the root file system. If you have [[Qi]] installed then you can install the Qt Moko on the SD card. This seems to be useful if you want to work with different distribution and you can change the distribution just by changing the Mirco SD card in your freerunner.

Switch off your freerunner and press AUX and Power-On button at the same time. Your freerunner is showing the following U-Boot Menu:

*** BOOT MENU (NOR) ***

Boot
Boot from Mirco SD (FAT/ext2)
Set Console to USB
Set Console to Serial
Reboot
Power Off

The freerunner will stay in this mode for only 30 sec. Within this time you have to start <tt>dfu-util</tt>. Otherwise the freerunner will start to boot the installed operating system.
If you want to flash the kernel image (you will need to be root on you PC) then you have to start the following command in the 30sec your see the BOOT MENU:

# for the Neo FreeRunner:
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-v13.bin

and finally the root fs with this one:

# for the Neo FreeRunner:
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D qtmoko-debian-v13.jffs2

===First Boot===
After finishing the installation without errors you have to start the freerunner and calibrate the touch screen. The you see the installed ''Qt Moko'' on your device.
[[Image:qtmokomain.png|200px|thumb|Qt Moko after first boot]]

===Login===
If you want to login to your freerunner set up network connection (see [[USB Networking]]) with USB cable and start:
desktop# ssh -X -l root 192.168.0.202

The root password is empty so set it for security reason especially when you open the ssh-daemon on the WLAN network interface. Define root password as usual on a linux box with
neo# passwd
If you have established the internet connection via USB cable then update the repository data:
neo# apt-get update
If you want to check if the internet connection is available on your freerunner ping the OpenMoko web server with:
neo# ping 88.198.93.221
neo# ping wiki.openmoko.org
If the first ping works and the second doesn't then check the DNS server settings (see [[USB Networking]]).

===Setting Time and Date===
Set the time and date on from your linux box with
<pre>
ssh root@openmoko "date -us @`date -u +%s`"
</pre>
If you want to set the time with a NTP Client install the following package, if you have a network connection available (see [[USB Networking]])
<pre>
# apt-get install ntpdate
# ntpdate-debian
</pre>
For further detail see [[Setting Date and Time]].

[[Category:Qt| ]]

Manuals/SHR/es

2010-02-24T11:20:18Z

Joseba:

{{Languages|Manuals/SHR}}
==Introducción a SHR==

'''SHR''' (Stable Hybrid Release) es una distribución llevada por su comunidad y basada en el Framework de [[FSO]]. SHR puede utilizar diferentes toolkits gráficos, por ejemplo GTK o EFL. En un cominenzo, SHR se creó para su uso con el software GTK de la [[Om 2007.2]] en combinación con el nuevo FSO, pero las cosas cambiaron, el desarrollo del software fue más alla y continua progresando.

''TODO: Text from [[SHR]], enhance.''

==Específico de SHR==

En este punto, existen algunas aplicaciones y procdimientos que son específficas de SHR y que no corren bajo otras distribuciones. Por ejemplo las aplicaciones de teléfono (Dialer, Mensajes y contactos) y configuraciones que dependen en gran medida del demonio ophonekit.

Para la parte de la telefonía el SHR se basa en [[FSO]] con lo cual cualquier aplicación que corra usando FSO puede llegar a funcionar, siempre y cuando todas las librerias necesarias esten disponibles. En el futuro, esto permitirá escoger entre diferentes GUI's de telefonía.

==Installation==

===Getting SHR===

Primero, determina el modelo de teléfono que tienes, el GTA01(neo1973) o el GTA02(FreeRunner).

Necesitas descargar dos archivos para las versiones anteriormente mencionadas, el Kernel y el Filesystem (Sistema de archivos). Dependiendo de donde desees hacer la instalación, la memoria interna NAND o la µSD card (tarjeta MicroSD), has de utilizar el archivo .jffs2 para la NAND o el archivo .tar.gz para la tarjeta µSD.

En la direción http://build.shr-project.org se pueden encontrar las diferentes versiones de la distribución, por ejemplo en http://build.shr-project.org/shr-unstable/images/om-gta02/ se encontraría la versión Unstable para el NeoFreerunner.

- Obtén el últio quernel - buscando por la fecha o diretamente cogiendo el llamado uImage-om-gta02-latest.bin

- Descarga el filesystem shr-image-om-gta02.jffs2 (para la NAND) o shr-image-om-gta02.tar.gz (para la tarjeta µSD)

Existe una versión con menos paquetes marcada comode esta '''lite'''. A partir de esta puedes ir añadiendo paquetes o actualizar a la versión completa en su totalidad utilizando:

opkg update
opkg task-shr-apps task-shr-games task-shr-gtk

TODO: confirm

{|class="wikitable" border="1" cellpadding="0" cellspacing="0" width=100%

! width=16%| !! width=42%|Full image content !! width=42%|SHR-Image LITE Content
|-
| Window Manager ||
* illume
||
* illume
|-
| Engine ||
* frameworkd
||
* frameworkd
|-
| Telephony ||
* Dialer (Call/Receive, DTMF, Speaker mode)
* SIM Contacts (Call/Modify/Create/...)
* SIM Messages (Receive/Compose/Answer/...)
* Pyphonelog (received/emitted/missed calls logging)
||
* Dialer (Call/Receive, DTMF, Speaker mode)
* SIM Contacts (Call/Modify/Create/...)
* SIM Messages (Receive/Compose/Answer/...)
* Pyphonelog (received/emitted/missed calls logging)
|-
| GPS ||
* TangoGPS
||
* TangoGPS
|-
| Utilities ||
* Calculator
* Alarm
* GPE Scap (Take screenshot)
* GPE File Manager
* GPE Sketchbook
* vala-terminal
||
* Calculator
* Alarm
* GPE File Manager
* vala-terminal

|-

| Media ||

* Vagalume
* Intone
||
* pythm

|-

| Internet ||
* Pidgin
* Midori (Browser)
||

|-

| Games ||
* Numptyphysics
||
|-
| Settings ||
* SHR Settings
* Mokonnect (Network Manager)
||
* SHR Settings

|-
|}

Las fuentes se encuentran en: http://git.shr-project.org/git/

===Instalación en la Flash (NAND)===

TBD

===Instalacción en la tarjeta µSD===

TBD

===Version de SHR===

Para saber que versión de SHR tienes instalada, por favor utiliza:

cat /etc/shr-version

O mira en SHR Settings -> Other -> Image information

Manuals/eu

2010-02-24T11:18:02Z

Joseba:

{{Languages|Manuals}}

==Gailuak==

*[[Manuals/Neo FreeRunner/eu|eskuliburuak/Neo FreeRunner]]
*[[Manuals/Neo 1973|eskuliburuak/Neo 1973]]

==Banaketak==

*[[Manuals/Om 2008|eskuliburuak/Om 2008]]
*[[Manuals/Om 2007.2|eskuliburuak/Om 2007]]
*[[Manuals/Om 2009|eskuliburuak/Om 2009]]
*[[Manuals/SHR|eskuliburuak/SHR]]

[[Category:Manuals]]

FAQ/eu

2010-02-06T18:58:17Z

Joseba:

{{Languages|FAQ}}

== Getting Started with your Neo FreeRunner == 

=== FreeRunnerra jaso berria naiz. Zerekin hasi behazr dut?===

Ikusi [[Getting_Started_with_your_Neo_FreeRunner|FreeRunnerrarekin lehen harremanak ]]

=== Arazoren bat edo galderaren bat daukat. Nora jo behar dut? ===

Lehendabizi begiratu beharreko tokia FAQ (Sarritan Egindako Galderak) hau bera da.

Hemen erantzunik aurkitzen ez baduzu, [http://lists.openmoko.org/mailman/listinfo/community komunitatearen] edo [http://lists.openmoko.org/mailman/listinfo/support laguntzaren] banaketa zerrenden artxiboetan begiratu beharko zenuke.

Ondoren, sareko bilatzaileekin ere saia zintezke (google edota antzekoak).

Hala ere erantzunik lortu ez baduzu, zerrenda egokian, [http://lists.openmoko.org/mailman/listinfo/community komunitatearenean] edo [http://lists.openmoko.org/mailman/listinfo/support laguntzarenean], zure zalantza komenta dezakezu.

Kasu horretan, bilatzen ari zaren horren informazio guztia azaldu, eta izenburu moduan arazoaren muina ondo azaltzen duen zerbait jarri. Galdera egokiak egiteko bideak [http://www.catb.org/~esr/faqs/smart-questions.html | honako honetan] aurkituko dituzu.

Zure galdera ixilpekoa bada, [mailto:michael@openmoko.org Michael Shiloh]-ri mezua bidal diezaiokezu zuzenean.

Bestalde, [[Openmoko_Local_Groups|Openmoko erabiltzaile lokalak]] begira dezakezu zure ingurukoen laguntza bilatzeko. Aurrez aurreko minutu gutxi batzuk postaz ordubetetik gora baino erabilgarriagoak izan daitezke. (Zure inguruan hgorrelakorik ez badago, oraintxe has dezakezu bat!)

=== Neurrira egindako produkto edo aplikazio bat sortu nahi dut Openmoko edota Neo FreeRunnerrerako. Nola ekin behar diot? ===

Bidali mezua michael@openmoko.org edo to steve@openmoko.com helbideetara

=== Non lor ditzaket azken bertsioak? ===

[[Download|Hementxe]].

==Openmoko==

===Zer da Openmoko?===
Openmoko bi gauza dira:

Telefono mugikorretan oinarritutako konputagailuentzat diseinatutako Linux banaketa bat da, baina ez marka jakin bakarrerako, helburu orokorrekoa baita.

Bestalde, Openmoko elkarte edo konpainia bat da, Openmoko Linux banaketaren atzean dagoena. Openmokok konputagailu mugikorrak egiten ditu, esate baterako Neo FreeRunner izenekoa.

===Zin da proiektuaren helburua?===

By providing a completely open source Linux distribution, and by opening the schematics and CAD files, Openmoko's goal is to nurture explosive innovation (such as occurred with the Personal Computer) in the field of connected mobile computing, cellphones, and ubiquitous computing.

===How do I join the Openmoko project? ===

Join one or more of the mailing lists. A great place to start is the community list.

Browse the wiki, and help improve it.

Start or join an [[http://projects.openmoko.org/ Openmoko project]].

Start or join a local group near you.

===I'm not a programmer, but I have other skills. Can I still be of use? ===

Absolutely. If you're a visual artist, you can help us with icons and other visuals. Musicians can help contribute ringtones and other sounds. Marketing? Sales? Information visualization? Join the community mailing lists, introduce yourself, and you'll soon find a place to put your skills to good use.

== Neo FreeRunner - Introductory/Overview/Conceptual Information==

=== What is the [[Neo FreeRunner]]? ===

The [[Neo FreeRunner]] is an open cellphone designed for the Openmoko Linux distribution. By open we mean that (a) all chips have been chosen to allow their drivers to be completely open sourced and (b) the schematics and the plastic (CAD) files are available as well.

For more details, see [[Neo FreeRunner|Neo FreeRunner specifications]]

=== What can I do with the Neo FreeRunner? ===

The Neo FreeRunner is designed for everyday use by end users and for continued software development and improvements by the Openmoko team and the Openmoko community.

The Openmoko software is not yet ready for everyday use.

The question is almost what can you NOT do with this phone - eventually there will be a huge range of free software applications allowing both end users and developers to get much more out of this phone than a standard "locked" mobile phone using features like the integrated GPS, bluetooth, wifi and accelerometers.

=== What are the buttons on the Neo FreeRunner for? ===
=== What are the LEDs on the Neo FreeRunner for? ===

There are two buttons on the Neo FreeRunner: One just below the USB socket, and one on the other side, near the top. Both buttons are clear, and both have LEDs behind them.

All buttons and LEDs are software-controlled; that is, their behavior depends on what the installed software implements.

See [[FreeRunner/Buttons and LEDs|here]] for more details, along with some programs which implement a variety of behaviors.

=== What are the benefits of an "open" phone over a "closed" phone? ===

In a conventional closed phone, the handset maker and the mobile network operator work together to provide a service to you that best suits their business model. The capabilities of a modern smartphone equipped with GPS, Wifi and bluetooth are amazing yet unfortunately inaccessible: many features are "locked down" because they do not suit the network operator. Up until now it has been difficult to buy a phone on which you have freedom to install sofware which is not controlled by the network operators - Openmoko changes that!

A list of examples of "closed" behaviour has been started here - [[Problems of typical "closed" phones]]

=== What can we expect in future Neos? ===

Please join one of the [http://lists.openmoko.org mailing lists] to follow and participate in this discussion.

=== Purchasing / Shipping / Versions ===

==== Where can I buy the [[Neo FreeRunner]]? How much?====

See [[distributors]]

==== On what bands does the Neo FreeRunner operate? Will it work in my area? ====

* The Neo FreeRunner is a tri-band GSM phone. It is available in a 850/1800/1900MHz version for North America and a 900/1800/1900MHz version for the rest of the world.

==== Do I need the debug board? ====

With the Neo FreeRunner and NO debug board you can do:
* Kernel development
* Application development
* U-boot updates(equivalent to PC BIOS). Neo 1973 users should only use a tested image to avoid the possibility of bricking the Neo 1973. Neo FreeRunner users do not have this concern, as a bad u-boot can always be updated using the failsafe u-boot in NOR flash
* Kernel and/or rootfs updates using [[Dfu-util]].

With a debug board you can additionally do:
* Use JTAG to debug u-boot, device drivers, or the kernel
* Use the kernel console
* Neo 1973 users can unbrick their device if they flash a wrong or non-working u-boot image.
* Neo FreeRunner users can update u-boot in NOR flash

In summary, it is rare for a Neo FreeRunner user to require a debug board.

To emphasize, the debug board is '''not''' required in order to develop applications, system software, or even kernel or device drivers. The debug board is '''not''' required in order to gain access to the source code or the development tools.

==== Where do I ask a shipping related question? ====

Visit [http://www.openmoko.com/ openmoko.com]

=== How do I find out what version of hardware I have? ===

:cat /proc/cpuinfo

Search for the line that says "Revision". There will be 4 digits, of the form "0350". The '5' in this example indicates hardware revision 5.

== Neo FreeRunner Known Issues==

=== Software issues, distribution-wise ===

Issues relating to software are in the "known issues" section for each distribution. Navigate there via the distributions page - [[Distributions]].

=== Firmware and hardware issues ===

Issues relating to firmware and hardware are in [[Neo_FreeRunner_Hardware_Issues|Neo FreeRunner Hardware Issues]].

Note that some issues might involve a combination of hardware and software.

=== Selected, commonly-encountered issues ===

Some selected known issues that are commonly encountered and reported on mailing lists are described below.

==== My FreeRunner won't register with my cellphone network. What should I do?====

Please see [[Neo_FreeRunner_Hardware_Issues#Some_SIMs_Don.27t_Work|some SIMs don't work]].

==== SIM compatibility: It looks like my SIM card is not working; how do I run diagnostics? ====

Here is how to check: follow [[Manually_using_GSM]] until you get an OK prompt.

For more detailed documentation, please refer to [[FreeRunner_unable_to_work_with_3G_SIM_cards]] and [[Carriers]].

==== I read somewhere that a GSM firmware update is available to fix this problem====

The GSM firmware update is applicable only to the Neo 1973. Any fixes in the update are already implemented in the GSM firmware in the Neo FreeRunner.

==== Why won't the FreeRunner boot even with the charger connected? ====

See [[Neo_FreeRunner_Hardware_Issues#Can.27t_boot_with_discharged_or_missing_battery|Can't boot with discharged or missing battery]].

==== Flashing (dfu-util) -- dfu-util does not find the phone. ====

In brief, you need to boot the phone into the NAND or NOR u-boot menu before dfu-util will be able to connect. dfu-util uses the USB DFU (Universal Serial Bus Device Firmware Upgrade) protocol, which is only available at the u-boot menu, and '''not''' Ethernet over USB, which is what is available when the phone has booted fully.

Tip: If you're just trying out different distributions, you don't need to flash them with dfu-util; you can try out new distributions by putting them on the microSD card and booting from the card instead. If you'd like to do this instead of flashing, see [[Booting from SD]].

To get the u-boot menu:
# Press and hold the AUX button
# Press the Power button until the phone powers on and displays the boot menu
# Release both buttons
# Press and release AUX to move the lightbar, so that the menu will not time out and boot the phone).

Also see the wiki pages/sections:
* [[Booting the Neo FreeRunner]]
* [[Bootloader#Device Firmware Upgrade]]
* [[Flashing the Neo FreeRunner]]
* [[Dfu-util]]

==== Why do I experience poor audio quality or buzzing noises during calls?====
See [http://wiki.openmoko.org/wiki/Neo_FreeRunner_Hardware_Issues#Poor_Audio_Quality this issue on the FreeRunner Hardware Issues page]

====Suspend/resume may corrupt SD card's partition table====

See [http://wiki.openmoko.org/wiki/Neo_FreeRunner_Hardware_Issues#Suspend.2Fresume_corrupts_SD_card.27s_partition_table this issue on the FreeRunner Hardware Issues page]. See ticket [https://docs.openmoko.org/trac/ticket/1802 #1802].

==Hardware and Usage-related Questions==

=== Booting ===

==== How do I boot into U-boot? How do I select NAND or NOR FLASH? ====

See [[Booting_the_Neo_FreeRunner|here]]

=== Battery and Battery Charging===

==== What is the expected battery life? ====
See [[Neo FreeRunner (GTA02) Battery#Notes_about_expected_battery_life]] and more battery information in [[Neo_FreeRunner_(GTA02)_Battery]]

==== How do I enable fast charge mode for anything but the official mains charger? ====
See [[Forcing fast charge mode]].

==== Can the Neo FreeRunner charge when turned off? When suspended? ====

The Neo FreeRunner can '''not''' charge when turned off.

The Neo FreeRunner '''can''' charge when suspended.

==== Can the Neo charge and use devices on a USB hub at the same time? ====

See [[USB_host#Providing_power_to_run_and_charge_the_Neo_while_in_host_mode|here]]

===Wireless Connectivity===

====What kind of wireless connectivity does the FreeRunner have? ====

The FreeRunner has the following connectivity options:
* Tri-band GSM (850/1800/1900 MHz in North America, and 900/1800/1900 MHz, commonly referred to as "European tri-band", for other parts of the world). For a list of compatible service providers, see [[Neo1973 compatible cellphone providers]].
* GPRS Class12/CS4 2.5G (Not EDGE)
* Bluetooth 2.0 EDR
* WiFi: Atheros AR6K in [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]]. (No 3G in year 2007 models)

==== GSM/GPRS information ====

The following pages contain very useful information:

* [[Gsmd|GSM Daemon]]

* [[GSM|General GSM page]]

* [[Hardware:AT_Commands|AT commands]]

* [http://freeyourphone.de/portal_v1/viewtopic.php?f=21&t=295#p2956 Useful script for GPRS]

==== How do I get the WLAN (802.11, Wi-Fi, wireless network) working? ====

See [[Neo FreeRunner Wifi]]

==== How do I get the GPS working? ====

See [[GTA02 GPS]]

==== It takes a long time (10min+) before the FreeRunner gets the first GPS data/readings ====

See [[GPS Problems]].

==== How do I get Bluetooth working manually? ====

See [[Manually_using_Bluetooth]]

==== How do I use an external Bluetooth keyboard with the FreeRunner ? ====
..TBA..

(It is mentioned as being a bit funky, but preliminary documentation can be found [http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#HID_.28Human_Input_Device.29 here])

====Can I bridge to an Ethernet (wired or unwired) network via a suitable Bluetooth enabled router? ====

Yes - see [http://gentoo-wiki.com/HOWTO_Configure_a_bluetooth_network_access_point this howto for how to configure a linux computer to act as such a router] and [[Bluetooth Support]].

=== USB ===

==== How do I connect a USB memory-stick etc? ====

This requires an adapter Mini-B 5-pole => Type A jack or an adapter jack => jack. See [[USB host]] for more information.

====Once I have such an adapter, can I use it to connect 2 Neos to each other?====

This question is equivalent to '''How to connect two [Unix/Linux] computers via USB cable and what sort of special cable is needed?''' -> http://www.linuxquestions.org/questions/linux-general-1/connecting-two-computers-with-a-usb-cable-data-cable-411073

It should work if one Neo is set to Host mode and the other one set to Device mode. One Neo could give power to the USB-port it the other Neo's battery is low. ''(I have to verify this)''

==== How do I use an external USB keyboard with the FreeRunner ? ====

Run:
echo "host" > /sys/devices/platform/s3c2410-ohci/usb_mode
echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode

These commands will put the FreeRunner into powered USB host mode. After this, just plug in the keyboard and it'll work. Personally, I've made a .desktop file to switch into and out of host mode.

To switch back to unpowered device mode just run:

echo "device" > /sys/devices/platform/s3c2410-ohci/usb_mode
echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode

Finally you will need a
USB Type A Female to Female adapter. For more details see
[[Specialized_USB_cables#Attaching_the_Neo_.28acting_as_a_USB_host.29_to_a_USB_device|here]]

'''The above does not work with QtExtended on mwester's kernel, it gives an invalid argument on the first command.'''

No, stable-tracking kernels give that error too but they still work. --[[User:Lindi|Lindi]]

=== Display ===

==== Can the phone play VGA video? ====

No, it can do about 20 fps QVGA with software, and something beetween QVGA and VGA playing MPEG-4 using hardware (at resonable fps). Scaling is also done with GPU hardware.

=== Storage ===

==== What microSDHC-cards are supported? ====

See [[Supported_microSD_cards|here]]

==== What is the best file system for microSDHC-cards? ====

Short answer: for OM it is ext3. Other options: ext2 and vfat. Don't use wear-aware file systems like jffs2 and ubifs.

For a longer explanation, see [[FileSystem_microSD_cards|here]].

===System-level information===

==== What hardware signals are available?====

To simplify extending the hardware, various signals of interest are brought out via the JTAG connector and can be easily accessed with the debug board:

(TBA: List of signals)

Some additional signals that did not fit on the JTAG connector are brought out to solder pads:

(TBA: List of signals)

==== Is the JTAG interface that comes with GTA01 compatible with GTA02?====

Yes

==== How do I get low-level hardware-related functions, like power up device, dump register? ====

See [[GTA02_sysfs]]

=== Miscellaneous ===

====Will Openmoko "Just Work" with Mac OS X? ====

There has been some discussion of this on the mailing list. There is motivation, and there are interested developers.
Not being a Mac OS X user, I don't know enough
to summarize the discussion to answer this question. Can someone please fill in?

For IP over USB cable connectivity, it is planned to improve/adapt the AJZaurusUSB driver, allowing ssh into the Openmoko.

It is expected that (Bluetooth/UB) SyncML based interoperation for
contacts and events can easily be achieved by a patch
to the Apple iSync configuration tables.

There is an open source implementation of Cocoa (GNUstep) that aims to run MacOS X compatible applications (sort of
PPC/x86/ARM universal binaries) on Openmoko devices: mySTEP.

====Why is resuming from suspend so slow ====
The suspend / resume speed is influenced by the kernel loglevel, i.e. how many messages are printed on the console during suspend / resume. The loglevel can be set using the kernel boot parameters. Setting 'loglevel=1' using the u-boot console for example improves resume speed drastically compared to 'loglevel=8'.

As an alternate to changing the kernel parameter from the boot loader, you can pass "-c 1" to klogd. You can add this parameter to /etc/default/klogd in debian, for example.

==Software==

===General Questions===

====Is it completely free software/open source? ====

Yes. All software that runs on the main CPU and can be updated by the user is available in source.

Firmware in "black box" hardware modules that can not be modified by users is not available in source form. Effectively, these modules are "hardware only".

This allows, for example, that the driver for the GSM module be completely open sourced without violating any FCC rules.

==== Does Openmoko run on any other hardware? ====

You can run it on your [[How_to_run_Openmoko_Apps_on_PC|PC]]. You may be able to run it on other [[Openmoko_supported_devices|mobile platforms]]

==== Can Java applications from other mobile phones run on the FreeRunner? ====

I think a lot of work must still be done, but [[Java|this]] wiki page has some information

===Distributions===

====What distributions are available for the Neo FreeRunner?====

See [[Distributions|Distributions]]

==== How do I find out what image versions are in use on the phone? ====

You can run the commands given below on the phone (in an SSH session from your host PC, or in the Terminal application on the phone itself)
{| border="1" cellspacing="0" cellpadding="5" align="left"
! To find out
! Run
|-
| Kernel version that is currently running
|
uname -a
|-
| The version of the root filesystem that you are currently using
|
cat /etc/version
or
cat /etc/om-version
|-
| The versions of u-boot on the phone (The FreeRunner has one u-boot image in NOR memory, and one in NAND - see [[Booting the Neo FreeRunner]] for more information)
|
grep Bootloader /dev/mtdblock0 (yields the NOR u-boot version)
or
grep Bootloader /dev/mtdblock1 (yields the NAND u-boot version)
|}

 

====Can the Neo FreeRunner dual boot? Multiple boot?====

Since the Neo FreeRunner can boot from the micro SD card, you can install and boot from as many distributions as will fit on your card. See [[Booting from SD]].

====How do I install Debian on the Neo FreeRunner?====

See [[Debian#Installation|Debian Installation]]

=====Are there any known issues with Debian on the Neo FreeRunner?=====

See [[Debian#Known_Issues|Debian Known Issues]]

=====How do I replace the matchbox window manager with the xfce window manager?=====

Replace the matchbox-wm line in zhone-session with xfwm4 to start the xfce-wm.

Here's my (Fox Mulder) /usr/bin/zhone-session file which works with xfwm and matchbox keyboard popup:

#!/bin/sh

#zhone &
exec startxfce4 &
matchbox-keyboard-toggle &
#exec matchbox-window-manager -use_titlebar yes
exec xfwm4

=== Applications ===

====What software is on the phone?====

At the moment, almost no 'end-user' applications are present and working in a usable state.
It is possible to make and receive calls in some software revisions, this frequently breaks though.

====What software can be installed on the phone?====

Pretty much any that can be cross-compiled for the ARM architecture.

====Will it be possible to use popular VoIP applications on the Openmoko platform? ====

Since it has WiFi the FreeRunner should be a good platform for VOIP use.

In either case please check for softphone apps ported to the Openmoko distribution at the [http://projects.openmoko.org/ projects] page. We need to focus efforts on free software. Not convincing non-free software companies to release binaries for our Neos.

====Will it be possible to use popular Instant Messaging applications ? ====

There many Open Source IM clients, many of which have a plugin architecture and so support the use of more than one IM protocol, even simultaneously. One example is [[Pidgin]], formerly called GAIM. GPRS does induce a certain amount of latency but that should not be a problem for simple, text-oriented chat between parties. And the GTA02's WiFi will make it even better.

==== Does it support Flash so can I watch YouTube? ====
You don't really need Flash to watch YouTube videos, for example, if you want to watch www.youtube.com/watch?v=k9QLdK6pFCI just install mplayer and use this command:
mplayer http://ytpocket.com/getflv.php?id=k9QLdK6pFCI
or use this small script with the video URL as the first parametre:
#!/bin/sh
vid=`echo "$1" | sed 's/.*\?.*=$.*$/\1/'`
mplayer http://ytpocket.com/getflv.php?id=$vid

If you don't want to tell ytpocket.com about every video you watch on debian you can also
sudo apt-get install youtube-dl
mplayer `youtube-dl --get-url www.youtube.com/watch?v=k9QLdK6pFCI`

=== Package Management===

==== How do I install and manage software on Openmoko? ====

See [http://handhelds.org/moin/moin.cgi/Ipkg here]

==== What about opkg? ====

See [[Opkg|here]]

==== What is the meaning of the error codes from ipkg? ====

See [[Opkg#Error_Codes|here]]

==== Does opkg support packages autocompletion ? ====

It's possible now, see [http://blog.upme.fr/?/Linux/28-Openmoko-Opkg-Autocompletion-With-Packages-Names 0pkg : The opkg autocompletion]

===Development===

====How can I compile programs for the Neo FreeRunner? ====

See [[Toolchain]].

====Is there an emulator available for Openmoko? ====

For a lot of testing and development work you can simply run Openmoko directly on your PC.

=====QEMU=====

QEMU can emulate the Neo 1973 and the Neo FreeRunner. The [[MokoMakefile]] has support for automatically building, flashing, and running [[Openmoko under QEMU|the Neo emulator]].

*Ubuntu users can follow the instructions in [[Automatic_emulation_in_Ubuntu]]

*Users of other Linux distributions can try the following:
:"make qemu” will build qemu-neo1973, download the latest official openmoko images, flash the images into the virtual NAND flash, and run the emulator.

See [[Qemu]] for more advanced information on running Openmoko in Qemu.

=====Xoo=====

[http://projects.o-hand.com/xoo Xoo]. Koen says: "Xoo should be enough for most applications people will develop, since most don't need access to the GSM uart directly. If you're hardcore you could use qemu + xoo, but that still doesn't emulate all the hardware quirks (e.g. unaligned access)".

Update: Stefan Schmidt has resized the [[Neo1973]] Mock-up and written a small description for xoo. In his words:

It's not really usable at all, as you need a really high screen resolution to fit the whole picture on your screen. And of course the dpi are wrong. Even no buttons because I can't remember where they are at the case.

http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2

Start with 'xoo --device /path/to/neo1973.xml'

Some more details [[Getting_Openmoko_working_on_host_with_Xoo|here]].

=====Xephyr=====

Or use Xephyr directly with locally compiled programs (e.g. matchbox svn + openmoko):
Xephyr -screen 480x640 -nolisten tcp -ac :1 &
export DISPLAY=:1
export LD_LIBRARY_PATH=/usr/local/lib
matchbox-window-manager -display $DISPLAY -use_titlebar no \
-use_super_modal yes -use_lowlight yes -use_dialog_mode static \
-use_cursor yes &
matchbox-panel --geometry=480x44 --end-applets=clock &
openmoko-footer &
openmoko-taskmanager &

====Where can I find some type of tutorial for a 'Hello, world' on Openmoko? ====

This should get you started:
* [[Building_a_hello_world_application]]
* http://www.gtk.org/documentation.html#Tutorials

====Can PalmOS apps applications be ported to run on Openmoko? ====

Making legacy apps written for the "Garnet" OS (née "Palm OS") run on Linux
is decidedly non-trivial.

PalmOS apps are in general very hard to simply 'port'. Particularly well-designed programs may make it possible.

The ACCESS Linux Platform will include Garnet on Host (GHost), a PalmOS emulator that will support M68000 (68k) and ARM PalmOS applications. This part (GarnetVM and the .prc loader) will however be closed-source and likely under a restrictive license (fact confirmed by ACCESS Co. employees), making it rather unusable. In addition GarnetVM depends on Hiker and other packages.

It is possible that POSE, an emulator that simulates a Palm device on a Linux host could be used to allow 68k based applications to run. This emulator has been around a long time; one expects that it will also run on Openmoko, but this has to be considered a short-term bandaid rather than a long-term solution.

Hopefully emulation will be necessary only for M68000 code (pre-PalmOS 5) while native ARM programs can run natively under Linux, provided a proper set of PalmOS libraries and a .prc executable loader.

==== Does it support Java? ====
It will have eventually, if you help us to get it working. Some good places to keep track of would be [http://projects.openmoko.org/projects/java-pkg/ projects.openmoko.org] and [https://phoneme.dev.java.net/ PhoneME].

Project [[https://wiki.evolvis.org/jalimo/index.php/Jalimo Jalimo]] is a project aiming to provide a Java stack on mobile devices. There is a [https://wiki.evolvis.org/jalimo/index.php/Openmoko port of Jalimo] for Openmoko.
The [[Debian]] distribution supports CacaoVM and JamVM through apt-get. See [[Java]] for more infos.

==== Does it support Ruby? ====

For Ruby 1.9, please refer to http://blog.sparkymat.net/2008/08/10/ruby-19-on-openmoko/

For Ruby 1.8.6, please refer to http://blog.wolfman.com/articles/2008/08/10/ruby-1-8-6-on-openmoko-freerunner

==== Does it support Python? ====

Yes, with some caveats. See [[Python]] for more information.

====How do I dump details about X11 configuration and extensions? ====

Run the command xdpyinfo. Generally, you would do this via an SSH session to the phone, so you may need to first

export DISPLAY=":0.0"

and then run

xdpyinfo

For an example invocation, see [http://lists.openmoko.org/pipermail/community/2007-January/001353.html xdpyinfo output].

== Distribution Customization ==

{{Note| Suggestion: this should be split off into a separate page, since many of the questions below aren't really overview-level but specialized; a question like "How do I customize a distribution?" could be added to the Software - Distributions part, linking to the new page. --[[User:Eddsouza|eddsouza]] 07:35, 7 September 2008 (UTC)}}

=== Compilation & packaging ===
==== What is the 'overlay' approach to bitbake development? ====
:You can create a local overlay for the bitbake build chain and develop in the overlay as described in [[Application_Development_Crash_Course| Application Development Crash Course]].

==== Which .bb files are related with the Openmoko? ====
==== Are there any configuration files for Openmoko? ====
==== How can I port an application written with autotools to Openmoko? ====
After you source the [[Toolchain|Openmoko toolchain]] variables, the Openmoko processor compiler becomes the default compiler. You can compile any GNU - like project just typing ''./configure --host i686'' and then ''make'' - it will produce libraries and executables as expected. Just these executables will not run on your i686 host - they will run on Openmoko ARM processor. Use scp to upload the executables to your phone.

==== How can I add an application written with autotools to the openmoko tree? ====

==== How can I make changes in the openmoko applications? ====
==== How can I submit my changes? ====
==== Can I use the mokomakefile in the development process? How? ====

:Yes, [[MokoMakefile]] can be used in the development process. See [[MokoMakefile#Developing_with_MokoMakefile| Developing with MokoMakefile]].

==== What's the way to include/exclude a newly added package to/from the final rootfs? ====
==== Where do the final ipk & binary files reside? ====
:ipk files are in
./build/tmp/deploy/glibc/ipk/
:binary images are in
./build/tmp/deploy/glibc/images/fic-gta01/

==== How can I add an application to the applications list? ====
==== How can I assign an image to my new application to be seen in the applications list? ====
The Openmoko project tree contains the folder 'data' where you can put any 128*128 icon. You need to mention the icon in two places in this folder:
* Makefile.am must contain the line dist_appicon_DATA = <icon_name>.png
* The <application_name>.desktop file that must be in this folder should contain the Icon=<icon_name> (without file type).

==Misc==

===On the lists on lists.openmoko.org, should replies be added above or below the original text? ===

Please reply UNDER post.

===How can I find out if a question or topic has already been discussed on the mailing lists? ===

By searching the mailing list archives. For example, using Google searches:

site:openmoko.org text

For example, to search for accelerometer:

site:openmoko.org accelerometer

If you only want to read the "official" mails from FIC people or from Openmoko people:

site:openmoko.org text "at fic.com.tw"
site:openmoko.org text "at openmoko.org"

For example to search for "release date" from FIC people:

site:openmoko.org "release date" "at fic.com.tw"

Alternatively you can use the [http://www.google.com/coop/cse?cx=018430699993342716089%3Aszsaurhronw custom Openmoko search engine] that is using [http://www.google.com/coop/ Google Co-op].

===how many dead pixels may the LCM have before calling it defect? ===

The answer for the display used in GTA01 and GTA02 is '2'

=== how many visits does this wiki have? ===
See this [[Wiki_statistic_numbers|wiki's statistics]] page.

=Historical=
The Neo1973 was last available in Febuary 2008.

==Neo1973 Hardware==

===What are the hardware specifications of Neo 1973 ? ===

See page [[Neo1973_Hardware]] and category [[:Category:Neo1973 Hardware | Neo1973 Hardware]] and [[Disassembling Neo1973]]

===How do I input text? ===

Use provided keyboard app.

Use Bluetooth keyboard.

For more methods and ideas see [[Wishlist:Text_Input]].

===Can I record calls and/or play audio files in calls? ===

Yes, audio path from GSM to/from mic and speakers is completely controllable by user. For example recording calls (both sides) and implementing an [[Answering Machine]] is possible. Also using text->speech should be possible or modifying outgoing voice. Currently there is no software bundled in phone to do this.
There are only 2 A/D inputs and three D/A outputs (one dedicated to the earpiece). This means that stereo audio playback cannot happen at the same time as the [[Answering Machine]] functionality, amongst other things. See the audio page. [[Neo1973_Audio_Subsystem|Neo1973 Audio Subsystem]]

===What is the battery life? ===

There has been no word on this so far, but see [[Neo1973 Power Management#Approximate_power_draw_of_various_subsystems|these estimates]] for a rough idea. More information about the battery [[Neo1973 Battery|here]].

=== USB ===

====What can I do with the USB port on the Neo? ====
Charge the phone, communicate with it over USB-serial, or USB-networking.

Plug external devices, such as wifi, cameras, or mass-storage devices.

====What can't I do with the USB? ====

The only limitation on current hardware seems to be no usb 2.0 support, which means slower communication with 2.0 devices.

====Why is only USB 1.1 provided? ====

The processor has USB 1.1 built in. One with USB2 built in would have been more expensive, and might not be open.

The FreeRunner has the same processor as the Neo1973.

====What are the details of the USB port on the Neo? How does it compare to USB On-The-Go? ====

The Neo will have mini-USB-B, and will be able to function as either a host or a device. It will NOT be USB On-The-Go. OTG is a complex specification, and it comprises way more than just
an AB socket, but also electrical and software components which cannot be provide by the S3C2410.

You will need a special Mini-B to regular-B cable (note that this won't actually comply with the USB standard: a compliant cable has to have an A or Mini-A plug on one end, and B or Mini-B on the other).

== Q: Can the Neo charge and use devices on a USB hub at the same time? ==

It's entirely a cabling problem.
The neo essentially has two ports in one - there is the mini-AB port, which is missing the 5V line, and the 5V charging line.

When the Neo is plugged into one of the the outputs of a USB hub, the 5V line is used to charge the battery.
The 5V line is not otherwise used in the neo.

To use peripheral devices plugged into a hub, the Neo must be plugged into the input of a powered hub, that is capable of working without 5V input (the Belkin Tetrahub for example will not recognise a host without it).

To use peripheral devices and charge at the same time, you need to make up a special cable, that plugs into the output of a powered hub - to pick up the charge current, and into the input of a powered hub at the same time - to act as a USB host.
These cables are wired together for 5V and 0V, but only the input cable has the data pins wired.
In some cases (the belkin hub mentioned above) this will also allow the hub to recognise the neo as a host, when it would not before.
In other cases - where the hub keeps the outputs unpowered until it senses a host - an external source of 5V would need to be plugged into the 'output' cable.

See [[USB host#Providing power to run and charge the Neo while in host mode]]

[[Category:FAQ]]
[[Category:Power]]

FAQ/eu

2010-02-06T18:40:25Z

Joseba:

{{Languages|FAQ}}

== Getting Started with your Neo FreeRunner == 

=== FreeRunnerra jaso berria naiz. Zerekin hasi behazr dut?===

Ikusi [[Getting_Started_with_your_Neo_FreeRunner|FreeRunnerrarekin lehen harremanak ]]

=== Arazoren bat edo galderaren bat daukat. Nora jo behar dut? ===

Lehendabizi begiratu beharreko tokia FAQ (Sarritan Egindako Galderak) hau bera da.

Hemen erantzunik aurkitzen ez baduzu, [http://lists.openmoko.org/mailman/listinfo/community komunitatearen] edo [http://lists.openmoko.org/mailman/listinfo/support laguntzaren] banaketa zerrenden artxiboetan begiratu beharko zenuke.

Ondoren, sareko bilatzaileekin ere saia zintezke (google edota antzekoak).

Hala ere erantzunik lortu ez baduzu, zerrenda egokian, [http://lists.openmoko.org/mailman/listinfo/community kpminitatean] edo [http://lists.openmoko.org/mailman/listinfo/support laguntzarenean], zure zalantza komenta dezakezu.

Kasu horretan, bilatzen ari zaren horren informazio guztia azaldu, eta izenburu moduan arazoaren muina ondo azaltzen duen zerbait jarri. Galdera egokiak egiteko bideak [[http://www.catb.org/~esr/faqs/smart-questions.html|honako honetan]] aurkituko dituzu.

If your question requires confidentiality, you are welcome to contact [mailto:michael@openmoko.org Michael Shiloh] directly.

You might also look for [[Openmoko_Local_Groups|local Openmoko users]] to find
some local support. A few minutes with a live person might solve a simple
misunderstanding that would take hours to understand via email. (If a local
club doesn't exist, this might be the perfect opportunity to start one!)

=== I'd like to develop a custom product or application based on Openmoko and/or the Neo FreeRunner. How should I proceed? ===

Send mail to michael@openmoko.org or to steve@openmoko.com

=== Where are the latest downloads? ===

Right [[Download|here]].

==Openmoko==

===What is Openmoko?===
Openmoko is two things:

Openmoko is a Linux distribution designed for open mobile computing platforms, such as, but not limited to, cellphones.

Openmoko is the company behind the Openmoko Linux distribution. Openmoko also manufactures mobile computing platforms, such as the Neo FreeRunner.

===What is the purpose of this project?===

By providing a completely open source Linux distribution, and by opening the schematics and CAD files, Openmoko's goal is to nurture explosive innovation (such as occurred with the Personal Computer) in the field of connected mobile computing, cellphones, and ubiquitous computing.

===How do I join the Openmoko project? ===

Join one or more of the mailing lists. A great place to start is the community list.

Browse the wiki, and help improve it.

Start or join an [[http://projects.openmoko.org/ Openmoko project]].

Start or join a local group near you.

===I'm not a programmer, but I have other skills. Can I still be of use? ===

Absolutely. If you're a visual artist, you can help us with icons and other visuals. Musicians can help contribute ringtones and other sounds. Marketing? Sales? Information visualization? Join the community mailing lists, introduce yourself, and you'll soon find a place to put your skills to good use.

== Neo FreeRunner - Introductory/Overview/Conceptual Information==

=== What is the [[Neo FreeRunner]]? ===

The [[Neo FreeRunner]] is an open cellphone designed for the Openmoko Linux distribution. By open we mean that (a) all chips have been chosen to allow their drivers to be completely open sourced and (b) the schematics and the plastic (CAD) files are available as well.

For more details, see [[Neo FreeRunner|Neo FreeRunner specifications]]

=== What can I do with the Neo FreeRunner? ===

The Neo FreeRunner is designed for everyday use by end users and for continued software development and improvements by the Openmoko team and the Openmoko community.

The Openmoko software is not yet ready for everyday use.

The question is almost what can you NOT do with this phone - eventually there will be a huge range of free software applications allowing both end users and developers to get much more out of this phone than a standard "locked" mobile phone using features like the integrated GPS, bluetooth, wifi and accelerometers.

=== What are the buttons on the Neo FreeRunner for? ===
=== What are the LEDs on the Neo FreeRunner for? ===

There are two buttons on the Neo FreeRunner: One just below the USB socket, and one on the other side, near the top. Both buttons are clear, and both have LEDs behind them.

All buttons and LEDs are software-controlled; that is, their behavior depends on what the installed software implements.

See [[FreeRunner/Buttons and LEDs|here]] for more details, along with some programs which implement a variety of behaviors.

=== What are the benefits of an "open" phone over a "closed" phone? ===

In a conventional closed phone, the handset maker and the mobile network operator work together to provide a service to you that best suits their business model. The capabilities of a modern smartphone equipped with GPS, Wifi and bluetooth are amazing yet unfortunately inaccessible: many features are "locked down" because they do not suit the network operator. Up until now it has been difficult to buy a phone on which you have freedom to install sofware which is not controlled by the network operators - Openmoko changes that!

A list of examples of "closed" behaviour has been started here - [[Problems of typical "closed" phones]]

=== What can we expect in future Neos? ===

Please join one of the [http://lists.openmoko.org mailing lists] to follow and participate in this discussion.

=== Purchasing / Shipping / Versions ===

==== Where can I buy the [[Neo FreeRunner]]? How much?====

See [[distributors]]

==== On what bands does the Neo FreeRunner operate? Will it work in my area? ====

* The Neo FreeRunner is a tri-band GSM phone. It is available in a 850/1800/1900MHz version for North America and a 900/1800/1900MHz version for the rest of the world.

==== Do I need the debug board? ====

With the Neo FreeRunner and NO debug board you can do:
* Kernel development
* Application development
* U-boot updates(equivalent to PC BIOS). Neo 1973 users should only use a tested image to avoid the possibility of bricking the Neo 1973. Neo FreeRunner users do not have this concern, as a bad u-boot can always be updated using the failsafe u-boot in NOR flash
* Kernel and/or rootfs updates using [[Dfu-util]].

With a debug board you can additionally do:
* Use JTAG to debug u-boot, device drivers, or the kernel
* Use the kernel console
* Neo 1973 users can unbrick their device if they flash a wrong or non-working u-boot image.
* Neo FreeRunner users can update u-boot in NOR flash

In summary, it is rare for a Neo FreeRunner user to require a debug board.

To emphasize, the debug board is '''not''' required in order to develop applications, system software, or even kernel or device drivers. The debug board is '''not''' required in order to gain access to the source code or the development tools.

==== Where do I ask a shipping related question? ====

Visit [http://www.openmoko.com/ openmoko.com]

=== How do I find out what version of hardware I have? ===

:cat /proc/cpuinfo

Search for the line that says "Revision". There will be 4 digits, of the form "0350". The '5' in this example indicates hardware revision 5.

== Neo FreeRunner Known Issues==

=== Software issues, distribution-wise ===

Issues relating to software are in the "known issues" section for each distribution. Navigate there via the distributions page - [[Distributions]].

=== Firmware and hardware issues ===

Issues relating to firmware and hardware are in [[Neo_FreeRunner_Hardware_Issues|Neo FreeRunner Hardware Issues]].

Note that some issues might involve a combination of hardware and software.

=== Selected, commonly-encountered issues ===

Some selected known issues that are commonly encountered and reported on mailing lists are described below.

==== My FreeRunner won't register with my cellphone network. What should I do?====

Please see [[Neo_FreeRunner_Hardware_Issues#Some_SIMs_Don.27t_Work|some SIMs don't work]].

==== SIM compatibility: It looks like my SIM card is not working; how do I run diagnostics? ====

Here is how to check: follow [[Manually_using_GSM]] until you get an OK prompt.

For more detailed documentation, please refer to [[FreeRunner_unable_to_work_with_3G_SIM_cards]] and [[Carriers]].

==== I read somewhere that a GSM firmware update is available to fix this problem====

The GSM firmware update is applicable only to the Neo 1973. Any fixes in the update are already implemented in the GSM firmware in the Neo FreeRunner.

==== Why won't the FreeRunner boot even with the charger connected? ====

See [[Neo_FreeRunner_Hardware_Issues#Can.27t_boot_with_discharged_or_missing_battery|Can't boot with discharged or missing battery]].

==== Flashing (dfu-util) -- dfu-util does not find the phone. ====

In brief, you need to boot the phone into the NAND or NOR u-boot menu before dfu-util will be able to connect. dfu-util uses the USB DFU (Universal Serial Bus Device Firmware Upgrade) protocol, which is only available at the u-boot menu, and '''not''' Ethernet over USB, which is what is available when the phone has booted fully.

Tip: If you're just trying out different distributions, you don't need to flash them with dfu-util; you can try out new distributions by putting them on the microSD card and booting from the card instead. If you'd like to do this instead of flashing, see [[Booting from SD]].

To get the u-boot menu:
# Press and hold the AUX button
# Press the Power button until the phone powers on and displays the boot menu
# Release both buttons
# Press and release AUX to move the lightbar, so that the menu will not time out and boot the phone).

Also see the wiki pages/sections:
* [[Booting the Neo FreeRunner]]
* [[Bootloader#Device Firmware Upgrade]]
* [[Flashing the Neo FreeRunner]]
* [[Dfu-util]]

==== Why do I experience poor audio quality or buzzing noises during calls?====
See [http://wiki.openmoko.org/wiki/Neo_FreeRunner_Hardware_Issues#Poor_Audio_Quality this issue on the FreeRunner Hardware Issues page]

====Suspend/resume may corrupt SD card's partition table====

See [http://wiki.openmoko.org/wiki/Neo_FreeRunner_Hardware_Issues#Suspend.2Fresume_corrupts_SD_card.27s_partition_table this issue on the FreeRunner Hardware Issues page]. See ticket [https://docs.openmoko.org/trac/ticket/1802 #1802].

==Hardware and Usage-related Questions==

=== Booting ===

==== How do I boot into U-boot? How do I select NAND or NOR FLASH? ====

See [[Booting_the_Neo_FreeRunner|here]]

=== Battery and Battery Charging===

==== What is the expected battery life? ====
See [[Neo FreeRunner (GTA02) Battery#Notes_about_expected_battery_life]] and more battery information in [[Neo_FreeRunner_(GTA02)_Battery]]

==== How do I enable fast charge mode for anything but the official mains charger? ====
See [[Forcing fast charge mode]].

==== Can the Neo FreeRunner charge when turned off? When suspended? ====

The Neo FreeRunner can '''not''' charge when turned off.

The Neo FreeRunner '''can''' charge when suspended.

==== Can the Neo charge and use devices on a USB hub at the same time? ====

See [[USB_host#Providing_power_to_run_and_charge_the_Neo_while_in_host_mode|here]]

===Wireless Connectivity===

====What kind of wireless connectivity does the FreeRunner have? ====

The FreeRunner has the following connectivity options:
* Tri-band GSM (850/1800/1900 MHz in North America, and 900/1800/1900 MHz, commonly referred to as "European tri-band", for other parts of the world). For a list of compatible service providers, see [[Neo1973 compatible cellphone providers]].
* GPRS Class12/CS4 2.5G (Not EDGE)
* Bluetooth 2.0 EDR
* WiFi: Atheros AR6K in [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]]. (No 3G in year 2007 models)

==== GSM/GPRS information ====

The following pages contain very useful information:

* [[Gsmd|GSM Daemon]]

* [[GSM|General GSM page]]

* [[Hardware:AT_Commands|AT commands]]

* [http://freeyourphone.de/portal_v1/viewtopic.php?f=21&t=295#p2956 Useful script for GPRS]

==== How do I get the WLAN (802.11, Wi-Fi, wireless network) working? ====

See [[Neo FreeRunner Wifi]]

==== How do I get the GPS working? ====

See [[GTA02 GPS]]

==== It takes a long time (10min+) before the FreeRunner gets the first GPS data/readings ====

See [[GPS Problems]].

==== How do I get Bluetooth working manually? ====

See [[Manually_using_Bluetooth]]

==== How do I use an external Bluetooth keyboard with the FreeRunner ? ====
..TBA..

(It is mentioned as being a bit funky, but preliminary documentation can be found [http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#HID_.28Human_Input_Device.29 here])

====Can I bridge to an Ethernet (wired or unwired) network via a suitable Bluetooth enabled router? ====

Yes - see [http://gentoo-wiki.com/HOWTO_Configure_a_bluetooth_network_access_point this howto for how to configure a linux computer to act as such a router] and [[Bluetooth Support]].

=== USB ===

==== How do I connect a USB memory-stick etc? ====

This requires an adapter Mini-B 5-pole => Type A jack or an adapter jack => jack. See [[USB host]] for more information.

====Once I have such an adapter, can I use it to connect 2 Neos to each other?====

This question is equivalent to '''How to connect two [Unix/Linux] computers via USB cable and what sort of special cable is needed?''' -> http://www.linuxquestions.org/questions/linux-general-1/connecting-two-computers-with-a-usb-cable-data-cable-411073

It should work if one Neo is set to Host mode and the other one set to Device mode. One Neo could give power to the USB-port it the other Neo's battery is low. ''(I have to verify this)''

==== How do I use an external USB keyboard with the FreeRunner ? ====

Run:
echo "host" > /sys/devices/platform/s3c2410-ohci/usb_mode
echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode

These commands will put the FreeRunner into powered USB host mode. After this, just plug in the keyboard and it'll work. Personally, I've made a .desktop file to switch into and out of host mode.

To switch back to unpowered device mode just run:

echo "device" > /sys/devices/platform/s3c2410-ohci/usb_mode
echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode

Finally you will need a
USB Type A Female to Female adapter. For more details see
[[Specialized_USB_cables#Attaching_the_Neo_.28acting_as_a_USB_host.29_to_a_USB_device|here]]

'''The above does not work with QtExtended on mwester's kernel, it gives an invalid argument on the first command.'''

No, stable-tracking kernels give that error too but they still work. --[[User:Lindi|Lindi]]

=== Display ===

==== Can the phone play VGA video? ====

No, it can do about 20 fps QVGA with software, and something beetween QVGA and VGA playing MPEG-4 using hardware (at resonable fps). Scaling is also done with GPU hardware.

=== Storage ===

==== What microSDHC-cards are supported? ====

See [[Supported_microSD_cards|here]]

==== What is the best file system for microSDHC-cards? ====

Short answer: for OM it is ext3. Other options: ext2 and vfat. Don't use wear-aware file systems like jffs2 and ubifs.

For a longer explanation, see [[FileSystem_microSD_cards|here]].

===System-level information===

==== What hardware signals are available?====

To simplify extending the hardware, various signals of interest are brought out via the JTAG connector and can be easily accessed with the debug board:

(TBA: List of signals)

Some additional signals that did not fit on the JTAG connector are brought out to solder pads:

(TBA: List of signals)

==== Is the JTAG interface that comes with GTA01 compatible with GTA02?====

Yes

==== How do I get low-level hardware-related functions, like power up device, dump register? ====

See [[GTA02_sysfs]]

=== Miscellaneous ===

====Will Openmoko "Just Work" with Mac OS X? ====

There has been some discussion of this on the mailing list. There is motivation, and there are interested developers.
Not being a Mac OS X user, I don't know enough
to summarize the discussion to answer this question. Can someone please fill in?

For IP over USB cable connectivity, it is planned to improve/adapt the AJZaurusUSB driver, allowing ssh into the Openmoko.

It is expected that (Bluetooth/UB) SyncML based interoperation for
contacts and events can easily be achieved by a patch
to the Apple iSync configuration tables.

There is an open source implementation of Cocoa (GNUstep) that aims to run MacOS X compatible applications (sort of
PPC/x86/ARM universal binaries) on Openmoko devices: mySTEP.

====Why is resuming from suspend so slow ====
The suspend / resume speed is influenced by the kernel loglevel, i.e. how many messages are printed on the console during suspend / resume. The loglevel can be set using the kernel boot parameters. Setting 'loglevel=1' using the u-boot console for example improves resume speed drastically compared to 'loglevel=8'.

As an alternate to changing the kernel parameter from the boot loader, you can pass "-c 1" to klogd. You can add this parameter to /etc/default/klogd in debian, for example.

==Software==

===General Questions===

====Is it completely free software/open source? ====

Yes. All software that runs on the main CPU and can be updated by the user is available in source.

Firmware in "black box" hardware modules that can not be modified by users is not available in source form. Effectively, these modules are "hardware only".

This allows, for example, that the driver for the GSM module be completely open sourced without violating any FCC rules.

==== Does Openmoko run on any other hardware? ====

You can run it on your [[How_to_run_Openmoko_Apps_on_PC|PC]]. You may be able to run it on other [[Openmoko_supported_devices|mobile platforms]]

==== Can Java applications from other mobile phones run on the FreeRunner? ====

I think a lot of work must still be done, but [[Java|this]] wiki page has some information

===Distributions===

====What distributions are available for the Neo FreeRunner?====

See [[Distributions|Distributions]]

==== How do I find out what image versions are in use on the phone? ====

You can run the commands given below on the phone (in an SSH session from your host PC, or in the Terminal application on the phone itself)
{| border="1" cellspacing="0" cellpadding="5" align="left"
! To find out
! Run
|-
| Kernel version that is currently running
|
uname -a
|-
| The version of the root filesystem that you are currently using
|
cat /etc/version
or
cat /etc/om-version
|-
| The versions of u-boot on the phone (The FreeRunner has one u-boot image in NOR memory, and one in NAND - see [[Booting the Neo FreeRunner]] for more information)
|
grep Bootloader /dev/mtdblock0 (yields the NOR u-boot version)
or
grep Bootloader /dev/mtdblock1 (yields the NAND u-boot version)
|}

 

====Can the Neo FreeRunner dual boot? Multiple boot?====

Since the Neo FreeRunner can boot from the micro SD card, you can install and boot from as many distributions as will fit on your card. See [[Booting from SD]].

====How do I install Debian on the Neo FreeRunner?====

See [[Debian#Installation|Debian Installation]]

=====Are there any known issues with Debian on the Neo FreeRunner?=====

See [[Debian#Known_Issues|Debian Known Issues]]

=====How do I replace the matchbox window manager with the xfce window manager?=====

Replace the matchbox-wm line in zhone-session with xfwm4 to start the xfce-wm.

Here's my (Fox Mulder) /usr/bin/zhone-session file which works with xfwm and matchbox keyboard popup:

#!/bin/sh

#zhone &
exec startxfce4 &
matchbox-keyboard-toggle &
#exec matchbox-window-manager -use_titlebar yes
exec xfwm4

=== Applications ===

====What software is on the phone?====

At the moment, almost no 'end-user' applications are present and working in a usable state.
It is possible to make and receive calls in some software revisions, this frequently breaks though.

====What software can be installed on the phone?====

Pretty much any that can be cross-compiled for the ARM architecture.

====Will it be possible to use popular VoIP applications on the Openmoko platform? ====

Since it has WiFi the FreeRunner should be a good platform for VOIP use.

In either case please check for softphone apps ported to the Openmoko distribution at the [http://projects.openmoko.org/ projects] page. We need to focus efforts on free software. Not convincing non-free software companies to release binaries for our Neos.

====Will it be possible to use popular Instant Messaging applications ? ====

There many Open Source IM clients, many of which have a plugin architecture and so support the use of more than one IM protocol, even simultaneously. One example is [[Pidgin]], formerly called GAIM. GPRS does induce a certain amount of latency but that should not be a problem for simple, text-oriented chat between parties. And the GTA02's WiFi will make it even better.

==== Does it support Flash so can I watch YouTube? ====
You don't really need Flash to watch YouTube videos, for example, if you want to watch www.youtube.com/watch?v=k9QLdK6pFCI just install mplayer and use this command:
mplayer http://ytpocket.com/getflv.php?id=k9QLdK6pFCI
or use this small script with the video URL as the first parametre:
#!/bin/sh
vid=`echo "$1" | sed 's/.*\?.*=$.*$/\1/'`
mplayer http://ytpocket.com/getflv.php?id=$vid

If you don't want to tell ytpocket.com about every video you watch on debian you can also
sudo apt-get install youtube-dl
mplayer `youtube-dl --get-url www.youtube.com/watch?v=k9QLdK6pFCI`

=== Package Management===

==== How do I install and manage software on Openmoko? ====

See [http://handhelds.org/moin/moin.cgi/Ipkg here]

==== What about opkg? ====

See [[Opkg|here]]

==== What is the meaning of the error codes from ipkg? ====

See [[Opkg#Error_Codes|here]]

==== Does opkg support packages autocompletion ? ====

It's possible now, see [http://blog.upme.fr/?/Linux/28-Openmoko-Opkg-Autocompletion-With-Packages-Names 0pkg : The opkg autocompletion]

===Development===

====How can I compile programs for the Neo FreeRunner? ====

See [[Toolchain]].

====Is there an emulator available for Openmoko? ====

For a lot of testing and development work you can simply run Openmoko directly on your PC.

=====QEMU=====

QEMU can emulate the Neo 1973 and the Neo FreeRunner. The [[MokoMakefile]] has support for automatically building, flashing, and running [[Openmoko under QEMU|the Neo emulator]].

*Ubuntu users can follow the instructions in [[Automatic_emulation_in_Ubuntu]]

*Users of other Linux distributions can try the following:
:"make qemu” will build qemu-neo1973, download the latest official openmoko images, flash the images into the virtual NAND flash, and run the emulator.

See [[Qemu]] for more advanced information on running Openmoko in Qemu.

=====Xoo=====

[http://projects.o-hand.com/xoo Xoo]. Koen says: "Xoo should be enough for most applications people will develop, since most don't need access to the GSM uart directly. If you're hardcore you could use qemu + xoo, but that still doesn't emulate all the hardware quirks (e.g. unaligned access)".

Update: Stefan Schmidt has resized the [[Neo1973]] Mock-up and written a small description for xoo. In his words:

It's not really usable at all, as you need a really high screen resolution to fit the whole picture on your screen. And of course the dpi are wrong. Even no buttons because I can't remember where they are at the case.

http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2

Start with 'xoo --device /path/to/neo1973.xml'

Some more details [[Getting_Openmoko_working_on_host_with_Xoo|here]].

=====Xephyr=====

Or use Xephyr directly with locally compiled programs (e.g. matchbox svn + openmoko):
Xephyr -screen 480x640 -nolisten tcp -ac :1 &
export DISPLAY=:1
export LD_LIBRARY_PATH=/usr/local/lib
matchbox-window-manager -display $DISPLAY -use_titlebar no \
-use_super_modal yes -use_lowlight yes -use_dialog_mode static \
-use_cursor yes &
matchbox-panel --geometry=480x44 --end-applets=clock &
openmoko-footer &
openmoko-taskmanager &

====Where can I find some type of tutorial for a 'Hello, world' on Openmoko? ====

This should get you started:
* [[Building_a_hello_world_application]]
* http://www.gtk.org/documentation.html#Tutorials

====Can PalmOS apps applications be ported to run on Openmoko? ====

Making legacy apps written for the "Garnet" OS (née "Palm OS") run on Linux
is decidedly non-trivial.

PalmOS apps are in general very hard to simply 'port'. Particularly well-designed programs may make it possible.

The ACCESS Linux Platform will include Garnet on Host (GHost), a PalmOS emulator that will support M68000 (68k) and ARM PalmOS applications. This part (GarnetVM and the .prc loader) will however be closed-source and likely under a restrictive license (fact confirmed by ACCESS Co. employees), making it rather unusable. In addition GarnetVM depends on Hiker and other packages.

It is possible that POSE, an emulator that simulates a Palm device on a Linux host could be used to allow 68k based applications to run. This emulator has been around a long time; one expects that it will also run on Openmoko, but this has to be considered a short-term bandaid rather than a long-term solution.

Hopefully emulation will be necessary only for M68000 code (pre-PalmOS 5) while native ARM programs can run natively under Linux, provided a proper set of PalmOS libraries and a .prc executable loader.

==== Does it support Java? ====
It will have eventually, if you help us to get it working. Some good places to keep track of would be [http://projects.openmoko.org/projects/java-pkg/ projects.openmoko.org] and [https://phoneme.dev.java.net/ PhoneME].

Project [[https://wiki.evolvis.org/jalimo/index.php/Jalimo Jalimo]] is a project aiming to provide a Java stack on mobile devices. There is a [https://wiki.evolvis.org/jalimo/index.php/Openmoko port of Jalimo] for Openmoko.
The [[Debian]] distribution supports CacaoVM and JamVM through apt-get. See [[Java]] for more infos.

==== Does it support Ruby? ====

For Ruby 1.9, please refer to http://blog.sparkymat.net/2008/08/10/ruby-19-on-openmoko/

For Ruby 1.8.6, please refer to http://blog.wolfman.com/articles/2008/08/10/ruby-1-8-6-on-openmoko-freerunner

==== Does it support Python? ====

Yes, with some caveats. See [[Python]] for more information.

====How do I dump details about X11 configuration and extensions? ====

Run the command xdpyinfo. Generally, you would do this via an SSH session to the phone, so you may need to first

export DISPLAY=":0.0"

and then run

xdpyinfo

For an example invocation, see [http://lists.openmoko.org/pipermail/community/2007-January/001353.html xdpyinfo output].

== Distribution Customization ==

{{Note| Suggestion: this should be split off into a separate page, since many of the questions below aren't really overview-level but specialized; a question like "How do I customize a distribution?" could be added to the Software - Distributions part, linking to the new page. --[[User:Eddsouza|eddsouza]] 07:35, 7 September 2008 (UTC)}}

=== Compilation & packaging ===
==== What is the 'overlay' approach to bitbake development? ====
:You can create a local overlay for the bitbake build chain and develop in the overlay as described in [[Application_Development_Crash_Course| Application Development Crash Course]].

==== Which .bb files are related with the Openmoko? ====
==== Are there any configuration files for Openmoko? ====
==== How can I port an application written with autotools to Openmoko? ====
After you source the [[Toolchain|Openmoko toolchain]] variables, the Openmoko processor compiler becomes the default compiler. You can compile any GNU - like project just typing ''./configure --host i686'' and then ''make'' - it will produce libraries and executables as expected. Just these executables will not run on your i686 host - they will run on Openmoko ARM processor. Use scp to upload the executables to your phone.

==== How can I add an application written with autotools to the openmoko tree? ====

==== How can I make changes in the openmoko applications? ====
==== How can I submit my changes? ====
==== Can I use the mokomakefile in the development process? How? ====

:Yes, [[MokoMakefile]] can be used in the development process. See [[MokoMakefile#Developing_with_MokoMakefile| Developing with MokoMakefile]].

==== What's the way to include/exclude a newly added package to/from the final rootfs? ====
==== Where do the final ipk & binary files reside? ====
:ipk files are in
./build/tmp/deploy/glibc/ipk/
:binary images are in
./build/tmp/deploy/glibc/images/fic-gta01/

==== How can I add an application to the applications list? ====
==== How can I assign an image to my new application to be seen in the applications list? ====
The Openmoko project tree contains the folder 'data' where you can put any 128*128 icon. You need to mention the icon in two places in this folder:
* Makefile.am must contain the line dist_appicon_DATA = <icon_name>.png
* The <application_name>.desktop file that must be in this folder should contain the Icon=<icon_name> (without file type).

==Misc==

===On the lists on lists.openmoko.org, should replies be added above or below the original text? ===

Please reply UNDER post.

===How can I find out if a question or topic has already been discussed on the mailing lists? ===

By searching the mailing list archives. For example, using Google searches:

site:openmoko.org text

For example, to search for accelerometer:

site:openmoko.org accelerometer

If you only want to read the "official" mails from FIC people or from Openmoko people:

site:openmoko.org text "at fic.com.tw"
site:openmoko.org text "at openmoko.org"

For example to search for "release date" from FIC people:

site:openmoko.org "release date" "at fic.com.tw"

Alternatively you can use the [http://www.google.com/coop/cse?cx=018430699993342716089%3Aszsaurhronw custom Openmoko search engine] that is using [http://www.google.com/coop/ Google Co-op].

===how many dead pixels may the LCM have before calling it defect? ===

The answer for the display used in GTA01 and GTA02 is '2'

=== how many visits does this wiki have? ===
See this [[Wiki_statistic_numbers|wiki's statistics]] page.

=Historical=
The Neo1973 was last available in Febuary 2008.

==Neo1973 Hardware==

===What are the hardware specifications of Neo 1973 ? ===

See page [[Neo1973_Hardware]] and category [[:Category:Neo1973 Hardware | Neo1973 Hardware]] and [[Disassembling Neo1973]]

===How do I input text? ===

Use provided keyboard app.

Use Bluetooth keyboard.

For more methods and ideas see [[Wishlist:Text_Input]].

===Can I record calls and/or play audio files in calls? ===

Yes, audio path from GSM to/from mic and speakers is completely controllable by user. For example recording calls (both sides) and implementing an [[Answering Machine]] is possible. Also using text->speech should be possible or modifying outgoing voice. Currently there is no software bundled in phone to do this.
There are only 2 A/D inputs and three D/A outputs (one dedicated to the earpiece). This means that stereo audio playback cannot happen at the same time as the [[Answering Machine]] functionality, amongst other things. See the audio page. [[Neo1973_Audio_Subsystem|Neo1973 Audio Subsystem]]

===What is the battery life? ===

There has been no word on this so far, but see [[Neo1973 Power Management#Approximate_power_draw_of_various_subsystems|these estimates]] for a rough idea. More information about the battery [[Neo1973 Battery|here]].

=== USB ===

====What can I do with the USB port on the Neo? ====
Charge the phone, communicate with it over USB-serial, or USB-networking.

Plug external devices, such as wifi, cameras, or mass-storage devices.

====What can't I do with the USB? ====

The only limitation on current hardware seems to be no usb 2.0 support, which means slower communication with 2.0 devices.

====Why is only USB 1.1 provided? ====

The processor has USB 1.1 built in. One with USB2 built in would have been more expensive, and might not be open.

The FreeRunner has the same processor as the Neo1973.

====What are the details of the USB port on the Neo? How does it compare to USB On-The-Go? ====

The Neo will have mini-USB-B, and will be able to function as either a host or a device. It will NOT be USB On-The-Go. OTG is a complex specification, and it comprises way more than just
an AB socket, but also electrical and software components which cannot be provide by the S3C2410.

You will need a special Mini-B to regular-B cable (note that this won't actually comply with the USB standard: a compliant cable has to have an A or Mini-A plug on one end, and B or Mini-B on the other).

== Q: Can the Neo charge and use devices on a USB hub at the same time? ==

It's entirely a cabling problem.
The neo essentially has two ports in one - there is the mini-AB port, which is missing the 5V line, and the 5V charging line.

When the Neo is plugged into one of the the outputs of a USB hub, the 5V line is used to charge the battery.
The 5V line is not otherwise used in the neo.

To use peripheral devices plugged into a hub, the Neo must be plugged into the input of a powered hub, that is capable of working without 5V input (the Belkin Tetrahub for example will not recognise a host without it).

To use peripheral devices and charge at the same time, you need to make up a special cable, that plugs into the output of a powered hub - to pick up the charge current, and into the input of a powered hub at the same time - to act as a USB host.
These cables are wired together for 5V and 0V, but only the input cable has the data pins wired.
In some cases (the belkin hub mentioned above) this will also allow the hub to recognise the neo as a host, when it would not before.
In other cases - where the hub keeps the outputs unpowered until it senses a host - an external source of 5V would need to be plugged into the 'output' cable.

See [[USB host#Providing power to run and charge the Neo while in host mode]]

[[Category:FAQ]]
[[Category:Power]]

FAQ/eu

2010-02-06T18:29:36Z

Joseba: New page: {{Languages|FAQ}} == Getting Started with your Neo FreeRunner ==  === I just receive...

{{Languages|FAQ}}

== Getting Started with your Neo FreeRunner == 

=== I just received my Neo FreeRunner. Where should I start? | FreeRunnerra jaso berria naiz. Zerekin hasi behazr dut?===

See [[Getting_Started_with_your_Neo_FreeRunner|Getting Started with your Neo FreeRunner]]

=== I have a problem or a question. Where should I go? ===

First place to check is this FAQ.

If your question isn't answered here, you should search the archives of the [http://lists.openmoko.org/mailman/listinfo/community community] or [http://lists.openmoko.org/mailman/listinfo/support support] mailing lists

Next, try a larger Google search.

If you still haven't found the answer to your question, post it on the appropriate list, [http://lists.openmoko.org/mailman/listinfo/community community] or [http://lists.openmoko.org/mailman/listinfo/support support].

Provide detailed information about what you are trying to find out, and use
the Subject line to summarize your question. More tips to asking effective
questions can be found
[[http://www.catb.org/~esr/faqs/smart-questions.html|here]]

If your question requires confidentiality, you are welcome to contact [mailto:michael@openmoko.org Michael Shiloh] directly.

You might also look for [[Openmoko_Local_Groups|local Openmoko users]] to find
some local support. A few minutes with a live person might solve a simple
misunderstanding that would take hours to understand via email. (If a local
club doesn't exist, this might be the perfect opportunity to start one!)

=== I'd like to develop a custom product or application based on Openmoko and/or the Neo FreeRunner. How should I proceed? ===

Send mail to michael@openmoko.org or to steve@openmoko.com

=== Where are the latest downloads? ===

Right [[Download|here]].

==Openmoko==

===What is Openmoko?===
Openmoko is two things:

Openmoko is a Linux distribution designed for open mobile computing platforms, such as, but not limited to, cellphones.

Openmoko is the company behind the Openmoko Linux distribution. Openmoko also manufactures mobile computing platforms, such as the Neo FreeRunner.

===What is the purpose of this project?===

By providing a completely open source Linux distribution, and by opening the schematics and CAD files, Openmoko's goal is to nurture explosive innovation (such as occurred with the Personal Computer) in the field of connected mobile computing, cellphones, and ubiquitous computing.

===How do I join the Openmoko project? ===

Join one or more of the mailing lists. A great place to start is the community list.

Browse the wiki, and help improve it.

Start or join an [[http://projects.openmoko.org/ Openmoko project]].

Start or join a local group near you.

===I'm not a programmer, but I have other skills. Can I still be of use? ===

Absolutely. If you're a visual artist, you can help us with icons and other visuals. Musicians can help contribute ringtones and other sounds. Marketing? Sales? Information visualization? Join the community mailing lists, introduce yourself, and you'll soon find a place to put your skills to good use.

== Neo FreeRunner - Introductory/Overview/Conceptual Information==

=== What is the [[Neo FreeRunner]]? ===

The [[Neo FreeRunner]] is an open cellphone designed for the Openmoko Linux distribution. By open we mean that (a) all chips have been chosen to allow their drivers to be completely open sourced and (b) the schematics and the plastic (CAD) files are available as well.

For more details, see [[Neo FreeRunner|Neo FreeRunner specifications]]

=== What can I do with the Neo FreeRunner? ===

The Neo FreeRunner is designed for everyday use by end users and for continued software development and improvements by the Openmoko team and the Openmoko community.

The Openmoko software is not yet ready for everyday use.

The question is almost what can you NOT do with this phone - eventually there will be a huge range of free software applications allowing both end users and developers to get much more out of this phone than a standard "locked" mobile phone using features like the integrated GPS, bluetooth, wifi and accelerometers.

=== What are the buttons on the Neo FreeRunner for? ===
=== What are the LEDs on the Neo FreeRunner for? ===

There are two buttons on the Neo FreeRunner: One just below the USB socket, and one on the other side, near the top. Both buttons are clear, and both have LEDs behind them.

All buttons and LEDs are software-controlled; that is, their behavior depends on what the installed software implements.

See [[FreeRunner/Buttons and LEDs|here]] for more details, along with some programs which implement a variety of behaviors.

=== What are the benefits of an "open" phone over a "closed" phone? ===

In a conventional closed phone, the handset maker and the mobile network operator work together to provide a service to you that best suits their business model. The capabilities of a modern smartphone equipped with GPS, Wifi and bluetooth are amazing yet unfortunately inaccessible: many features are "locked down" because they do not suit the network operator. Up until now it has been difficult to buy a phone on which you have freedom to install sofware which is not controlled by the network operators - Openmoko changes that!

A list of examples of "closed" behaviour has been started here - [[Problems of typical "closed" phones]]

=== What can we expect in future Neos? ===

Please join one of the [http://lists.openmoko.org mailing lists] to follow and participate in this discussion.

=== Purchasing / Shipping / Versions ===

==== Where can I buy the [[Neo FreeRunner]]? How much?====

See [[distributors]]

==== On what bands does the Neo FreeRunner operate? Will it work in my area? ====

* The Neo FreeRunner is a tri-band GSM phone. It is available in a 850/1800/1900MHz version for North America and a 900/1800/1900MHz version for the rest of the world.

==== Do I need the debug board? ====

With the Neo FreeRunner and NO debug board you can do:
* Kernel development
* Application development
* U-boot updates(equivalent to PC BIOS). Neo 1973 users should only use a tested image to avoid the possibility of bricking the Neo 1973. Neo FreeRunner users do not have this concern, as a bad u-boot can always be updated using the failsafe u-boot in NOR flash
* Kernel and/or rootfs updates using [[Dfu-util]].

With a debug board you can additionally do:
* Use JTAG to debug u-boot, device drivers, or the kernel
* Use the kernel console
* Neo 1973 users can unbrick their device if they flash a wrong or non-working u-boot image.
* Neo FreeRunner users can update u-boot in NOR flash

In summary, it is rare for a Neo FreeRunner user to require a debug board.

To emphasize, the debug board is '''not''' required in order to develop applications, system software, or even kernel or device drivers. The debug board is '''not''' required in order to gain access to the source code or the development tools.

==== Where do I ask a shipping related question? ====

Visit [http://www.openmoko.com/ openmoko.com]

=== How do I find out what version of hardware I have? ===

:cat /proc/cpuinfo

Search for the line that says "Revision". There will be 4 digits, of the form "0350". The '5' in this example indicates hardware revision 5.

== Neo FreeRunner Known Issues==

=== Software issues, distribution-wise ===

Issues relating to software are in the "known issues" section for each distribution. Navigate there via the distributions page - [[Distributions]].

=== Firmware and hardware issues ===

Issues relating to firmware and hardware are in [[Neo_FreeRunner_Hardware_Issues|Neo FreeRunner Hardware Issues]].

Note that some issues might involve a combination of hardware and software.

=== Selected, commonly-encountered issues ===

Some selected known issues that are commonly encountered and reported on mailing lists are described below.

==== My FreeRunner won't register with my cellphone network. What should I do?====

Please see [[Neo_FreeRunner_Hardware_Issues#Some_SIMs_Don.27t_Work|some SIMs don't work]].

==== SIM compatibility: It looks like my SIM card is not working; how do I run diagnostics? ====

Here is how to check: follow [[Manually_using_GSM]] until you get an OK prompt.

For more detailed documentation, please refer to [[FreeRunner_unable_to_work_with_3G_SIM_cards]] and [[Carriers]].

==== I read somewhere that a GSM firmware update is available to fix this problem====

The GSM firmware update is applicable only to the Neo 1973. Any fixes in the update are already implemented in the GSM firmware in the Neo FreeRunner.

==== Why won't the FreeRunner boot even with the charger connected? ====

See [[Neo_FreeRunner_Hardware_Issues#Can.27t_boot_with_discharged_or_missing_battery|Can't boot with discharged or missing battery]].

==== Flashing (dfu-util) -- dfu-util does not find the phone. ====

In brief, you need to boot the phone into the NAND or NOR u-boot menu before dfu-util will be able to connect. dfu-util uses the USB DFU (Universal Serial Bus Device Firmware Upgrade) protocol, which is only available at the u-boot menu, and '''not''' Ethernet over USB, which is what is available when the phone has booted fully.

Tip: If you're just trying out different distributions, you don't need to flash them with dfu-util; you can try out new distributions by putting them on the microSD card and booting from the card instead. If you'd like to do this instead of flashing, see [[Booting from SD]].

To get the u-boot menu:
# Press and hold the AUX button
# Press the Power button until the phone powers on and displays the boot menu
# Release both buttons
# Press and release AUX to move the lightbar, so that the menu will not time out and boot the phone).

Also see the wiki pages/sections:
* [[Booting the Neo FreeRunner]]
* [[Bootloader#Device Firmware Upgrade]]
* [[Flashing the Neo FreeRunner]]
* [[Dfu-util]]

==== Why do I experience poor audio quality or buzzing noises during calls?====
See [http://wiki.openmoko.org/wiki/Neo_FreeRunner_Hardware_Issues#Poor_Audio_Quality this issue on the FreeRunner Hardware Issues page]

====Suspend/resume may corrupt SD card's partition table====

See [http://wiki.openmoko.org/wiki/Neo_FreeRunner_Hardware_Issues#Suspend.2Fresume_corrupts_SD_card.27s_partition_table this issue on the FreeRunner Hardware Issues page]. See ticket [https://docs.openmoko.org/trac/ticket/1802 #1802].

==Hardware and Usage-related Questions==

=== Booting ===

==== How do I boot into U-boot? How do I select NAND or NOR FLASH? ====

See [[Booting_the_Neo_FreeRunner|here]]

=== Battery and Battery Charging===

==== What is the expected battery life? ====
See [[Neo FreeRunner (GTA02) Battery#Notes_about_expected_battery_life]] and more battery information in [[Neo_FreeRunner_(GTA02)_Battery]]

==== How do I enable fast charge mode for anything but the official mains charger? ====
See [[Forcing fast charge mode]].

==== Can the Neo FreeRunner charge when turned off? When suspended? ====

The Neo FreeRunner can '''not''' charge when turned off.

The Neo FreeRunner '''can''' charge when suspended.

==== Can the Neo charge and use devices on a USB hub at the same time? ====

See [[USB_host#Providing_power_to_run_and_charge_the_Neo_while_in_host_mode|here]]

===Wireless Connectivity===

====What kind of wireless connectivity does the FreeRunner have? ====

The FreeRunner has the following connectivity options:
* Tri-band GSM (850/1800/1900 MHz in North America, and 900/1800/1900 MHz, commonly referred to as "European tri-band", for other parts of the world). For a list of compatible service providers, see [[Neo1973 compatible cellphone providers]].
* GPRS Class12/CS4 2.5G (Not EDGE)
* Bluetooth 2.0 EDR
* WiFi: Atheros AR6K in [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]]. (No 3G in year 2007 models)

==== GSM/GPRS information ====

The following pages contain very useful information:

* [[Gsmd|GSM Daemon]]

* [[GSM|General GSM page]]

* [[Hardware:AT_Commands|AT commands]]

* [http://freeyourphone.de/portal_v1/viewtopic.php?f=21&t=295#p2956 Useful script for GPRS]

==== How do I get the WLAN (802.11, Wi-Fi, wireless network) working? ====

See [[Neo FreeRunner Wifi]]

==== How do I get the GPS working? ====

See [[GTA02 GPS]]

==== It takes a long time (10min+) before the FreeRunner gets the first GPS data/readings ====

See [[GPS Problems]].

==== How do I get Bluetooth working manually? ====

See [[Manually_using_Bluetooth]]

==== How do I use an external Bluetooth keyboard with the FreeRunner ? ====
..TBA..

(It is mentioned as being a bit funky, but preliminary documentation can be found [http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#HID_.28Human_Input_Device.29 here])

====Can I bridge to an Ethernet (wired or unwired) network via a suitable Bluetooth enabled router? ====

Yes - see [http://gentoo-wiki.com/HOWTO_Configure_a_bluetooth_network_access_point this howto for how to configure a linux computer to act as such a router] and [[Bluetooth Support]].

=== USB ===

==== How do I connect a USB memory-stick etc? ====

This requires an adapter Mini-B 5-pole => Type A jack or an adapter jack => jack. See [[USB host]] for more information.

====Once I have such an adapter, can I use it to connect 2 Neos to each other?====

This question is equivalent to '''How to connect two [Unix/Linux] computers via USB cable and what sort of special cable is needed?''' -> http://www.linuxquestions.org/questions/linux-general-1/connecting-two-computers-with-a-usb-cable-data-cable-411073

It should work if one Neo is set to Host mode and the other one set to Device mode. One Neo could give power to the USB-port it the other Neo's battery is low. ''(I have to verify this)''

==== How do I use an external USB keyboard with the FreeRunner ? ====

Run:
echo "host" > /sys/devices/platform/s3c2410-ohci/usb_mode
echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode

These commands will put the FreeRunner into powered USB host mode. After this, just plug in the keyboard and it'll work. Personally, I've made a .desktop file to switch into and out of host mode.

To switch back to unpowered device mode just run:

echo "device" > /sys/devices/platform/s3c2410-ohci/usb_mode
echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode

Finally you will need a
USB Type A Female to Female adapter. For more details see
[[Specialized_USB_cables#Attaching_the_Neo_.28acting_as_a_USB_host.29_to_a_USB_device|here]]

'''The above does not work with QtExtended on mwester's kernel, it gives an invalid argument on the first command.'''

No, stable-tracking kernels give that error too but they still work. --[[User:Lindi|Lindi]]

=== Display ===

==== Can the phone play VGA video? ====

No, it can do about 20 fps QVGA with software, and something beetween QVGA and VGA playing MPEG-4 using hardware (at resonable fps). Scaling is also done with GPU hardware.

=== Storage ===

==== What microSDHC-cards are supported? ====

See [[Supported_microSD_cards|here]]

==== What is the best file system for microSDHC-cards? ====

Short answer: for OM it is ext3. Other options: ext2 and vfat. Don't use wear-aware file systems like jffs2 and ubifs.

For a longer explanation, see [[FileSystem_microSD_cards|here]].

===System-level information===

==== What hardware signals are available?====

To simplify extending the hardware, various signals of interest are brought out via the JTAG connector and can be easily accessed with the debug board:

(TBA: List of signals)

Some additional signals that did not fit on the JTAG connector are brought out to solder pads:

(TBA: List of signals)

==== Is the JTAG interface that comes with GTA01 compatible with GTA02?====

Yes

==== How do I get low-level hardware-related functions, like power up device, dump register? ====

See [[GTA02_sysfs]]

=== Miscellaneous ===

====Will Openmoko "Just Work" with Mac OS X? ====

There has been some discussion of this on the mailing list. There is motivation, and there are interested developers.
Not being a Mac OS X user, I don't know enough
to summarize the discussion to answer this question. Can someone please fill in?

For IP over USB cable connectivity, it is planned to improve/adapt the AJZaurusUSB driver, allowing ssh into the Openmoko.

It is expected that (Bluetooth/UB) SyncML based interoperation for
contacts and events can easily be achieved by a patch
to the Apple iSync configuration tables.

There is an open source implementation of Cocoa (GNUstep) that aims to run MacOS X compatible applications (sort of
PPC/x86/ARM universal binaries) on Openmoko devices: mySTEP.

====Why is resuming from suspend so slow ====
The suspend / resume speed is influenced by the kernel loglevel, i.e. how many messages are printed on the console during suspend / resume. The loglevel can be set using the kernel boot parameters. Setting 'loglevel=1' using the u-boot console for example improves resume speed drastically compared to 'loglevel=8'.

As an alternate to changing the kernel parameter from the boot loader, you can pass "-c 1" to klogd. You can add this parameter to /etc/default/klogd in debian, for example.

==Software==

===General Questions===

====Is it completely free software/open source? ====

Yes. All software that runs on the main CPU and can be updated by the user is available in source.

Firmware in "black box" hardware modules that can not be modified by users is not available in source form. Effectively, these modules are "hardware only".

This allows, for example, that the driver for the GSM module be completely open sourced without violating any FCC rules.

==== Does Openmoko run on any other hardware? ====

You can run it on your [[How_to_run_Openmoko_Apps_on_PC|PC]]. You may be able to run it on other [[Openmoko_supported_devices|mobile platforms]]

==== Can Java applications from other mobile phones run on the FreeRunner? ====

I think a lot of work must still be done, but [[Java|this]] wiki page has some information

===Distributions===

====What distributions are available for the Neo FreeRunner?====

See [[Distributions|Distributions]]

==== How do I find out what image versions are in use on the phone? ====

You can run the commands given below on the phone (in an SSH session from your host PC, or in the Terminal application on the phone itself)
{| border="1" cellspacing="0" cellpadding="5" align="left"
! To find out
! Run
|-
| Kernel version that is currently running
|
uname -a
|-
| The version of the root filesystem that you are currently using
|
cat /etc/version
or
cat /etc/om-version
|-
| The versions of u-boot on the phone (The FreeRunner has one u-boot image in NOR memory, and one in NAND - see [[Booting the Neo FreeRunner]] for more information)
|
grep Bootloader /dev/mtdblock0 (yields the NOR u-boot version)
or
grep Bootloader /dev/mtdblock1 (yields the NAND u-boot version)
|}

 

====Can the Neo FreeRunner dual boot? Multiple boot?====

Since the Neo FreeRunner can boot from the micro SD card, you can install and boot from as many distributions as will fit on your card. See [[Booting from SD]].

====How do I install Debian on the Neo FreeRunner?====

See [[Debian#Installation|Debian Installation]]

=====Are there any known issues with Debian on the Neo FreeRunner?=====

See [[Debian#Known_Issues|Debian Known Issues]]

=====How do I replace the matchbox window manager with the xfce window manager?=====

Replace the matchbox-wm line in zhone-session with xfwm4 to start the xfce-wm.

Here's my (Fox Mulder) /usr/bin/zhone-session file which works with xfwm and matchbox keyboard popup:

#!/bin/sh

#zhone &
exec startxfce4 &
matchbox-keyboard-toggle &
#exec matchbox-window-manager -use_titlebar yes
exec xfwm4

=== Applications ===

====What software is on the phone?====

At the moment, almost no 'end-user' applications are present and working in a usable state.
It is possible to make and receive calls in some software revisions, this frequently breaks though.

====What software can be installed on the phone?====

Pretty much any that can be cross-compiled for the ARM architecture.

====Will it be possible to use popular VoIP applications on the Openmoko platform? ====

Since it has WiFi the FreeRunner should be a good platform for VOIP use.

In either case please check for softphone apps ported to the Openmoko distribution at the [http://projects.openmoko.org/ projects] page. We need to focus efforts on free software. Not convincing non-free software companies to release binaries for our Neos.

====Will it be possible to use popular Instant Messaging applications ? ====

There many Open Source IM clients, many of which have a plugin architecture and so support the use of more than one IM protocol, even simultaneously. One example is [[Pidgin]], formerly called GAIM. GPRS does induce a certain amount of latency but that should not be a problem for simple, text-oriented chat between parties. And the GTA02's WiFi will make it even better.

==== Does it support Flash so can I watch YouTube? ====
You don't really need Flash to watch YouTube videos, for example, if you want to watch www.youtube.com/watch?v=k9QLdK6pFCI just install mplayer and use this command:
mplayer http://ytpocket.com/getflv.php?id=k9QLdK6pFCI
or use this small script with the video URL as the first parametre:
#!/bin/sh
vid=`echo "$1" | sed 's/.*\?.*=$.*$/\1/'`
mplayer http://ytpocket.com/getflv.php?id=$vid

If you don't want to tell ytpocket.com about every video you watch on debian you can also
sudo apt-get install youtube-dl
mplayer `youtube-dl --get-url www.youtube.com/watch?v=k9QLdK6pFCI`

=== Package Management===

==== How do I install and manage software on Openmoko? ====

See [http://handhelds.org/moin/moin.cgi/Ipkg here]

==== What about opkg? ====

See [[Opkg|here]]

==== What is the meaning of the error codes from ipkg? ====

See [[Opkg#Error_Codes|here]]

==== Does opkg support packages autocompletion ? ====

It's possible now, see [http://blog.upme.fr/?/Linux/28-Openmoko-Opkg-Autocompletion-With-Packages-Names 0pkg : The opkg autocompletion]

===Development===

====How can I compile programs for the Neo FreeRunner? ====

See [[Toolchain]].

====Is there an emulator available for Openmoko? ====

For a lot of testing and development work you can simply run Openmoko directly on your PC.

=====QEMU=====

QEMU can emulate the Neo 1973 and the Neo FreeRunner. The [[MokoMakefile]] has support for automatically building, flashing, and running [[Openmoko under QEMU|the Neo emulator]].

*Ubuntu users can follow the instructions in [[Automatic_emulation_in_Ubuntu]]

*Users of other Linux distributions can try the following:
:"make qemu” will build qemu-neo1973, download the latest official openmoko images, flash the images into the virtual NAND flash, and run the emulator.

See [[Qemu]] for more advanced information on running Openmoko in Qemu.

=====Xoo=====

[http://projects.o-hand.com/xoo Xoo]. Koen says: "Xoo should be enough for most applications people will develop, since most don't need access to the GSM uart directly. If you're hardcore you could use qemu + xoo, but that still doesn't emulate all the hardware quirks (e.g. unaligned access)".

Update: Stefan Schmidt has resized the [[Neo1973]] Mock-up and written a small description for xoo. In his words:

It's not really usable at all, as you need a really high screen resolution to fit the whole picture on your screen. And of course the dpi are wrong. Even no buttons because I can't remember where they are at the case.

http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2

Start with 'xoo --device /path/to/neo1973.xml'

Some more details [[Getting_Openmoko_working_on_host_with_Xoo|here]].

=====Xephyr=====

Or use Xephyr directly with locally compiled programs (e.g. matchbox svn + openmoko):
Xephyr -screen 480x640 -nolisten tcp -ac :1 &
export DISPLAY=:1
export LD_LIBRARY_PATH=/usr/local/lib
matchbox-window-manager -display $DISPLAY -use_titlebar no \
-use_super_modal yes -use_lowlight yes -use_dialog_mode static \
-use_cursor yes &
matchbox-panel --geometry=480x44 --end-applets=clock &
openmoko-footer &
openmoko-taskmanager &

====Where can I find some type of tutorial for a 'Hello, world' on Openmoko? ====

This should get you started:
* [[Building_a_hello_world_application]]
* http://www.gtk.org/documentation.html#Tutorials

====Can PalmOS apps applications be ported to run on Openmoko? ====

Making legacy apps written for the "Garnet" OS (née "Palm OS") run on Linux
is decidedly non-trivial.

PalmOS apps are in general very hard to simply 'port'. Particularly well-designed programs may make it possible.

The ACCESS Linux Platform will include Garnet on Host (GHost), a PalmOS emulator that will support M68000 (68k) and ARM PalmOS applications. This part (GarnetVM and the .prc loader) will however be closed-source and likely under a restrictive license (fact confirmed by ACCESS Co. employees), making it rather unusable. In addition GarnetVM depends on Hiker and other packages.

It is possible that POSE, an emulator that simulates a Palm device on a Linux host could be used to allow 68k based applications to run. This emulator has been around a long time; one expects that it will also run on Openmoko, but this has to be considered a short-term bandaid rather than a long-term solution.

Hopefully emulation will be necessary only for M68000 code (pre-PalmOS 5) while native ARM programs can run natively under Linux, provided a proper set of PalmOS libraries and a .prc executable loader.

==== Does it support Java? ====
It will have eventually, if you help us to get it working. Some good places to keep track of would be [http://projects.openmoko.org/projects/java-pkg/ projects.openmoko.org] and [https://phoneme.dev.java.net/ PhoneME].

Project [[https://wiki.evolvis.org/jalimo/index.php/Jalimo Jalimo]] is a project aiming to provide a Java stack on mobile devices. There is a [https://wiki.evolvis.org/jalimo/index.php/Openmoko port of Jalimo] for Openmoko.
The [[Debian]] distribution supports CacaoVM and JamVM through apt-get. See [[Java]] for more infos.

==== Does it support Ruby? ====

For Ruby 1.9, please refer to http://blog.sparkymat.net/2008/08/10/ruby-19-on-openmoko/

For Ruby 1.8.6, please refer to http://blog.wolfman.com/articles/2008/08/10/ruby-1-8-6-on-openmoko-freerunner

==== Does it support Python? ====

Yes, with some caveats. See [[Python]] for more information.

====How do I dump details about X11 configuration and extensions? ====

Run the command xdpyinfo. Generally, you would do this via an SSH session to the phone, so you may need to first

export DISPLAY=":0.0"

and then run

xdpyinfo

For an example invocation, see [http://lists.openmoko.org/pipermail/community/2007-January/001353.html xdpyinfo output].

== Distribution Customization ==

{{Note| Suggestion: this should be split off into a separate page, since many of the questions below aren't really overview-level but specialized; a question like "How do I customize a distribution?" could be added to the Software - Distributions part, linking to the new page. --[[User:Eddsouza|eddsouza]] 07:35, 7 September 2008 (UTC)}}

=== Compilation & packaging ===
==== What is the 'overlay' approach to bitbake development? ====
:You can create a local overlay for the bitbake build chain and develop in the overlay as described in [[Application_Development_Crash_Course| Application Development Crash Course]].

==== Which .bb files are related with the Openmoko? ====
==== Are there any configuration files for Openmoko? ====
==== How can I port an application written with autotools to Openmoko? ====
After you source the [[Toolchain|Openmoko toolchain]] variables, the Openmoko processor compiler becomes the default compiler. You can compile any GNU - like project just typing ''./configure --host i686'' and then ''make'' - it will produce libraries and executables as expected. Just these executables will not run on your i686 host - they will run on Openmoko ARM processor. Use scp to upload the executables to your phone.

==== How can I add an application written with autotools to the openmoko tree? ====

==== How can I make changes in the openmoko applications? ====
==== How can I submit my changes? ====
==== Can I use the mokomakefile in the development process? How? ====

:Yes, [[MokoMakefile]] can be used in the development process. See [[MokoMakefile#Developing_with_MokoMakefile| Developing with MokoMakefile]].

==== What's the way to include/exclude a newly added package to/from the final rootfs? ====
==== Where do the final ipk & binary files reside? ====
:ipk files are in
./build/tmp/deploy/glibc/ipk/
:binary images are in
./build/tmp/deploy/glibc/images/fic-gta01/

==== How can I add an application to the applications list? ====
==== How can I assign an image to my new application to be seen in the applications list? ====
The Openmoko project tree contains the folder 'data' where you can put any 128*128 icon. You need to mention the icon in two places in this folder:
* Makefile.am must contain the line dist_appicon_DATA = <icon_name>.png
* The <application_name>.desktop file that must be in this folder should contain the Icon=<icon_name> (without file type).

==Misc==

===On the lists on lists.openmoko.org, should replies be added above or below the original text? ===

Please reply UNDER post.

===How can I find out if a question or topic has already been discussed on the mailing lists? ===

By searching the mailing list archives. For example, using Google searches:

site:openmoko.org text

For example, to search for accelerometer:

site:openmoko.org accelerometer

If you only want to read the "official" mails from FIC people or from Openmoko people:

site:openmoko.org text "at fic.com.tw"
site:openmoko.org text "at openmoko.org"

For example to search for "release date" from FIC people:

site:openmoko.org "release date" "at fic.com.tw"

Alternatively you can use the [http://www.google.com/coop/cse?cx=018430699993342716089%3Aszsaurhronw custom Openmoko search engine] that is using [http://www.google.com/coop/ Google Co-op].

===how many dead pixels may the LCM have before calling it defect? ===

The answer for the display used in GTA01 and GTA02 is '2'

=== how many visits does this wiki have? ===
See this [[Wiki_statistic_numbers|wiki's statistics]] page.

=Historical=
The Neo1973 was last available in Febuary 2008.

==Neo1973 Hardware==

===What are the hardware specifications of Neo 1973 ? ===

See page [[Neo1973_Hardware]] and category [[:Category:Neo1973 Hardware | Neo1973 Hardware]] and [[Disassembling Neo1973]]

===How do I input text? ===

Use provided keyboard app.

Use Bluetooth keyboard.

For more methods and ideas see [[Wishlist:Text_Input]].

===Can I record calls and/or play audio files in calls? ===

Yes, audio path from GSM to/from mic and speakers is completely controllable by user. For example recording calls (both sides) and implementing an [[Answering Machine]] is possible. Also using text->speech should be possible or modifying outgoing voice. Currently there is no software bundled in phone to do this.
There are only 2 A/D inputs and three D/A outputs (one dedicated to the earpiece). This means that stereo audio playback cannot happen at the same time as the [[Answering Machine]] functionality, amongst other things. See the audio page. [[Neo1973_Audio_Subsystem|Neo1973 Audio Subsystem]]

===What is the battery life? ===

There has been no word on this so far, but see [[Neo1973 Power Management#Approximate_power_draw_of_various_subsystems|these estimates]] for a rough idea. More information about the battery [[Neo1973 Battery|here]].

=== USB ===

====What can I do with the USB port on the Neo? ====
Charge the phone, communicate with it over USB-serial, or USB-networking.

Plug external devices, such as wifi, cameras, or mass-storage devices.

====What can't I do with the USB? ====

The only limitation on current hardware seems to be no usb 2.0 support, which means slower communication with 2.0 devices.

====Why is only USB 1.1 provided? ====

The processor has USB 1.1 built in. One with USB2 built in would have been more expensive, and might not be open.

The FreeRunner has the same processor as the Neo1973.

====What are the details of the USB port on the Neo? How does it compare to USB On-The-Go? ====

The Neo will have mini-USB-B, and will be able to function as either a host or a device. It will NOT be USB On-The-Go. OTG is a complex specification, and it comprises way more than just
an AB socket, but also electrical and software components which cannot be provide by the S3C2410.

You will need a special Mini-B to regular-B cable (note that this won't actually comply with the USB standard: a compliant cable has to have an A or Mini-A plug on one end, and B or Mini-B on the other).

== Q: Can the Neo charge and use devices on a USB hub at the same time? ==

It's entirely a cabling problem.
The neo essentially has two ports in one - there is the mini-AB port, which is missing the 5V line, and the 5V charging line.

When the Neo is plugged into one of the the outputs of a USB hub, the 5V line is used to charge the battery.
The 5V line is not otherwise used in the neo.

To use peripheral devices plugged into a hub, the Neo must be plugged into the input of a powered hub, that is capable of working without 5V input (the Belkin Tetrahub for example will not recognise a host without it).

To use peripheral devices and charge at the same time, you need to make up a special cable, that plugs into the output of a powered hub - to pick up the charge current, and into the input of a powered hub at the same time - to act as a USB host.
These cables are wired together for 5V and 0V, but only the input cable has the data pins wired.
In some cases (the belkin hub mentioned above) this will also allow the hub to recognise the neo as a host, when it would not before.
In other cases - where the hub keeps the outputs unpowered until it senses a host - an external source of 5V would need to be plugged into the 'output' cable.

See [[USB host#Providing power to run and charge the Neo while in host mode]]

[[Category:FAQ]]
[[Category:Power]]

Main Page/eu

2010-01-31T18:17:50Z

Joseba:

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

'''Openmoko™''' proiektu bat da, bere helburua [[Source Code|software libre]] bidez funtzionatuko duen telefono mugikorra lortzea da. Gaur egun [[Neo FreeRunner]] telefonoa saltzen da erabiltzaile aurreratuentzat, eta aplikazioen garapenak aurrera egiten duen heinean edonork erosteko moduan egongo da. Dagoenekoz Gnu/linux sistema erabiltzera ohituta dauden erabiltzaileek ez dute zailtasun handirik [[Neo FreeRunner]] telefono mugikorra erabiltzeko.

* [[Introduction/eu|Sarrera]]
* [[Why Openmoko|Zergatik Openmoko?]]

[[More informations|informazio gehiago]]

===Bat egin===
Boluntarioz osatutako komunitateak gidatzen du Openmoko proiektua. Gaitasuna baldin badaukazu, gure helburuekin bat egizu eta zeure alea jar ezazu. Helburu handiak dauzkagu eta guztion laguntza beharrezkoa da.

* [[Community Resources|Komunitatearen baliabideak eta ataria]]
* [[Gta02-core|gta02 hardwarearen berrikuspena egiten lagundu]]
* [[Create User Manuals|erabiltzaileentzat eskuliburuak sortu]] bai [[Distributions|banaketentzat]] bai eta [[Applications|aplikazioentzat]] ere
* Areagotu [[OpenmokoFramework|Openmoko euskarri]] gisa erabiltzen den [http://www.freesmartphone.org FSO] middleware multi-saltzaile eta multi-devicea.
===Nola erosi===
Neo FreeRunner telefono mugikorra hainbat [[distributors|banatzailek]] saltzen du munduan zehar.

Jo [[Getting Openmoko|Openmokoa erosi]] orrira informazio gehiago nahi baduzu.

----

====Latest News====

{{News}}
[[News Archive|berriak...]]

----

Introduction/eu

2010-01-31T18:16:23Z

Joseba: New page: {{Languages|Introduction}} Openmoko proiektu bat da, bere helburua software librez ornitutako telefono mugikorrak sortzea da. '''Openmoko Inc hardware askatzailea''': Telefono mugikorrak...

{{Languages|Introduction}}

Openmoko proiektu bat da, bere helburua software librez ornitutako telefono mugikorrak sortzea da.

'''Openmoko Inc hardware askatzailea''': Telefono mugikorrak eskaintzen ditu, bertan iturburu irekiko softwarea exekuta dadin. Lehenengo telefonoa [[Neo 1973]] izan zen, horri [[Neo FreeRunner]] modeloak jarraitu zion. Openmoko telefono mugikor dotore hauetan erabiltzaileak aukeratutako banaketa erabil daiteke. Erabiltzaileak berak aukera ditzake sistema eragilea eta aplikazioak. Ikusi [[Distributions/eu|banaketak]] gehiago ikasteko.

'''Openmoko Inc software askatzailea''': Sistema ergilea eta aplikazioak sortu eta bultzatzen ditu Openmoko telefonoentzat. Denboran zehar [[Om 2007]], [[Om 2008.12]] eta [[Om 2009]] banaketak argitaratu izan ditu. Banaketa hauek hainbat [[Supported Hardware|mugikorretan]] erabil daitezke, bai eta [[Openmoko_under_QEMU|emuladoreetan]] ere.

'''Askatu zure mugikorra''' helburuak mugikorrak erabiltzaileen beharretara egokitzeko aukera eskaintzen du. Softwarea egokitu dezakete, edo sortu eta instalatu nahi duten aplikazioa. [http://www.freesmartphone.org freesmartphone.org] eta Openmoko elkarlanean ari dira erabiltzaileentzat egokitutako aplikazio multzoa sortzeko asmotan; freesmartphone.org elkarlanerako plataforma bat da, Linuxean oinarritutako mugikorrentzat software irekia sortzeko eta eztabaidatzeko sortua, eta era berean, teknologia elkarbanatzeko eta elkarreraginkortasunean lantzea du helburu. [[OpenmokoFramework]] erabiliko da gerora ere sortuko diren Openmoko banaketetan.

- Openmokoren software multzoaren oinarria -
Openmoko proiektua hasi zutenak [http://www.fic.com.tw/ FIC Inc] eta [http://www.openmoko.com Openmoko, Inc.] dira.

Openmoko multzoak, X zerbitzaria barne, hardware mugikorren plataformak bateratzeko aukera eskaintzen die erabiltzaile eta garatzaileei. Gure lizentziak erabiltzaileei askatasuna ematen die, horrela bere gailua egokitu edota zeharo berrantolatzeko aukera izango dute; atzeko irudia alda dezakete, edota telefonoa salmetarako puntu batean bihurtu dezakete, edo medikuntzan erabiltzeko gailua edo kotxearen jarraipenerako tresna... Azken finean erabiltzaileak nahi duen softwarea instala dezake bertan. Softwarea askatzeaz gain, mugikorraren hardwarearen [http://downloads.openmoko.org/developer/CAD/ CAD] espezifikazioa ere askatu dugu. Eta LinuxWorld 2008 agindu zen bezala, [http://downloads.openmoko.org/developer/schematics/ gure produktuen eskemak] ere askatu dira..

== Telefono mugikorrak ==

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

== Softwarea ==

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

[[Om 2008.12]] banaketaren pantaila argazkiak.

== Bideoak ==
* [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 bereizmen handiko bertsioa] pantaila proiektorearen neurrietara handitu eta egokitua testua irakurtzeko moduan.
* [http://video.google.com/videoplay?docid=-8574715471341709984 Openmoko at Tossug], Sean Moss Pultz-ek eta Harald Welte-ek aurkeztua Taipei Open Source Software User Group-ean (TOSSUG)
* [http://www.youtube.com/watch?v=hn7wuxlTNvs TangoGPS] aurkezpena.

== Gehiago ikusteko ==

* [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| ]]

Distributions/eu

2010-01-30T18:18:33Z

Joseba:

{{Languages|Distributions}}

{|align=right
|__TOC__
|}
{| class="wikitable" style="float:left;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|<font color=white>Distributions</font>
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* <font color='#BBBBBB'>Openmoko (official)</font>
** [[Om 2009]]
** [[Om 2008]]
** [[Om 2007.2]]
* <font color='#BBBBBB'>Om Community</font>
** [[Android]]
** [[Debian]]
** [[Gentoo]]
** [[Hackable:1]]
** [[Mer]]
** [[Neovento]]
** [[OpenWrt]]
** [[Qt Extended Improved]]
** [[SHR]]
</div>
|-
|}
== Banaketei buruz ==
Openmoko banaketak hainbat mobiletan erabiltzeko diseinatu dira, baina helburu nagusia Openmoko Inc. proiektuaren [[GTA01:Neo 1973|Neo 1973]] eta [[Neo FreeRunner]] telefono mugikorretan funtzionatzea dute. GNU/Linux banaketak dira, alegia, Linux sistema eragilea eta erabilera zabaleko hainbat aplikazioz osatutako aplikazio multzoak dira. Zeure telefonoan banaketa horietako edozein instala zenezake, edo nahi izanez gero, banaketa bat baino gehiago eduki ditzakezu eta pizterakoan aukeratu zein banaketarekin abiarazi nahi duzun. Banaketaren bat deskargatzeko ikusi [[Download]], instalaziorako argibideak [[Flashing the Neo FreeRunner|FreeRunnerrean banaketen instalazioa]] orrian aurkituko dituzu.

Horrez gain, Openmoko banaketak [[Supported devices|beste]] mobil batzuetan ere instala daitezke, eta, era berean, beste banaketa batzuek ere instala daitezke Openmoko proiektuaren mobiletan.

=== Banaketa egokiaren aukera ===

2009ko abuztuaz geroztik egindako inkesta baten arabera [[SHR]] da gehien erabiltzen den banaketa, eta horri openmokoren banaketek jarraitzen diote ([[Om 2007]], [[Om 2008]] eta [[Om 2009]] hirurak bakar baten moduan hartuz gero beti ere), beste hainbat aukera ere badaude: [[Debian]], Debianen oinarritutako [[Hackable:1]], [[Qt Extended Improved]], [[Android]], Qtmoko eta abar.[http://doodle.com/sd2c8d8snr23eeqq] Om 2009 banaketaren garapena geratu egin da ordea, eta beraz bere erabiltzaileek beste banaketaren batera pasa beharko dute.

=== Kontuan izan ===

* Egonkorra hitzak FreeRunnerraren munduan ez du Debianen munduko esanahi bera.
* Banaketa gehienek abiatzaile, kernel, driver eta hardware berak erabiltzen dituzte. Ondorioz, behe mailako hutsegite berdinak agertzen dira banaketa gehienetan. Azken aplikazio zirraragarriek akats zaharrak konponduta edukiko dituzte, baina berriak bertan azalduko dira...
* Banaketa hauek aplikazioen biltegiak ere eduki ohi dituzte. bertatik instalatu aplikazio berriak, beste batetik instalatzea ideia '''TXARRA''' da. Ikusi [[installing alien package|beste banaketen aplikazioen instalazioa]].
* Banaketa hauen artean batetik besterako maila igoerak (upgradeak) ez dira ondo probatuta egoten, ondorioz, eguneraketak biltegiak aldatuz eginez gero, aplikazioeak apurtzea ekar dezake, edo okerragoa dena, abiarazi ezin den sistemarekin bukatu daiteke. Egin behar dena sistema FreeRunnerraren Flash memorian instalatzea da, horretarako [[dfu-util]] erabiliz, horrela, banaketa ezberdinen artean aukeratu ahal izango duzu. Abiaratze bikoitza ezar daiteke [[Booting from SD|MikroSD]] edo [[Booting from NFS|NFS]]) erabiliz.
* [[Marketing Mistakes|merkaturatze akatsak]] eta aurreinstalatutako banaketak

== Gainbegirada ==

=== Android ===
{{Template:Works on Android}}
[http://code.google.com/android/ Android] gailu mobilentzat garatutako software metaketa bat da, bere arduraduna [http://www.openhandsetalliance.com/ The Open Handset Alliance] da. Openmokok guztiz sostengatzen eta babesten du FreeRunnerrean Android banaketaren erabilera.

Android dagoenekoz Freerunnerra eguneroko mobil gisa erabiltzeko garapen mailara iritsia da, dena den, kontua eta arreta eskatzen duten gaiak daude oraindik. Informazio gehiago edukitzkeo, Wikiko Androiden atal nagusia aztertzea gomendatzen dizut.

{{Main|Android}} Bestalde, [http://wiki.openmoko.org/wiki/User:Seanmcneil3 Sean McNeil] erabiltzailearen web orria ere gomendagarria da informazio gehiago nahi baduzu.

=== Debian ===
{{Template:Works on Debian}}
[[Debian]] "sistema eragile unibertsala" da. Milaka paketa eta aplikazio dauzka (gehenak mahai gaineko ordenadoreetarako edota zerbitzarietarako paketeak dira). Joachim "nomeata" Breitner [http://wiki.debian.org/Teams/DebianFSO pkg-fso] taldeko kidearen hitzetan, Debian, Openmokoren zentzuan, ez da banaketa bat, horren ordez, Openmokoren beste banaketentzat azpiegitura edota oinarri-sistematzat har daiteke. Oraingoz,alatzeko beste bide bat bezala har daiteke, baina bide honek leku gehiago hartzen du eta askoz programa gehiago eskaintzen ditu.

{{Main|Debian}}

=== Gentoo ===
{{Template:Works on Gentoo}}
[[Gentoo]] banaketa aukeratzearen banaketa da. Gentoo instalatzerakoan erraz ulertuko duzu horren esanahia: zer konpilatu nahi duzun eta zer ez aukeratu ahal izango duzu, nola instalatu nahi duzun ere bai, zein log-sistema nahi duzun... Gentoo azkarra da, modernoa eta diseinu argia du, eta egokitzeko aukera eskaintzen du. Software librez egina dago, eta ez du ezkutatzen bere barnean dagoena. Paketeen mantenurako Portage aplikazioa erabiltzen du, Python hizkuntzan idatzita dago, beraz, erraz ikus eta alda daiteke jatorrizko kodea. Paketeen kudeaketa-sistemak jatorrizko kodea (iturburu-kodea) erabiltzen du (nahiz eta konpilatutakoak ere erabil ditzakeen) eta Gentoo-ren konfigurazioa ere testu fitxategien bidez egiten da. Ikus dezakezunez, dena irekia eta aldagarria.

{{Main|Gentoo}}

=== Hackable:1 ===
{{Template:Works on Hackable:1}}
Hackable1 is a community distribution for hackable devices like the Neo Freerunner. It is based on Debian and 2007.2 userland which has been abandoned by Openmoko. It follows the GNOME mobile platform.
{{Main|Hackable:1}}
<br style="clear: both">
=== Mer ===
{{Template:Works on Mer}}
[[Mer]] is a distribution based on [[Maemo]].
<br style="clear: both">
=== Mokotouch ===
{{Template:Works on Mokotouch}}
[[MokoTouch]] wants to be a replacement for the OM Distribution. It will contain apps for system settings and other useful apps like, mail client, Photo and Maps Viewer and maybe other fun things. It's fully written in C++ using Qt 4.5 Embedded. and it runs using Framebuffer, so no X11 Required. http://th30z.netsons.org/mokotouch/index.html

[http://www.youtube.com/watch?v=yr821OgnvYc Video]
<br style="clear: both">
=== neovento ===
{{Template:Works on noevento}}
[[neovento]] (ex FYP) is a [[Debian|Debian on Freerunner]] based [[Distributions|distribution]] which uses [http://lxde.org/ LXDE] and [[Zhone]] on top. It is a [http://freeyourphone.de FreeYourPhone.de] community project.

{{Main|neovento}}
<br style="clear: both">

=== OpenWrt ===
{{Template:Works on OpenWrt}}
[[OpenWrt]] is described as a Linux distribution for embedded devices.

Instead of trying to create a single, static firmware, [[OpenWrt]] provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developer, [[OpenWrt]] is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.

[[OpenWrt]] development trunk now supports s3c24xx, CPU used in [[Freerunner]].

Mainly due to the usage of uClibc instead of glibc as libc implementation, OpenWrt can boot from NAND with enlightenment window manager within 1 minute 7 seconds using u-boot (NOR) bootloader.

* [http://www.openwrt.org OpenWrt website]
* [http://dev.openwrt.org OpenWrt development site]

{{Main|OpenWrt}}

=== Qalee ===
{{Works on Qalee}}
[[Qalee]] is a phone environment developed in Qt4 above the fso stack. It works on the freerunner under any distribution that supports Qt4. It's not finished yet but you can test a preview version with the official Qalee distributon. This release includes no new features, but many fixes for things that didn’t work or were incomplete in 0.0.2. You can read full [http://think-free.homelinux.org/wordpress/ announcement], or take a look at some of changes:
* Qalee is now based on shr instead of debian.
* clock widget now shows a calendar when clicked.
* status panel widget shows gsm network name and power and internet connection status while on wifi or gprs.
* screen menu : you can now choose the background picture with a cover-flow effect, letting the backlight always on now works.
* network menu : all entries work, gsm one is a little buggy though.
* Wifi works despite the the bug in the kernel 2.6.29 opened for 4 month.
* application menu : to launch application just click on it :) when launched the button becomes green, to close it, press the close button which becomes red and click on the application you want to close
* power button supports suspend on short press, or menu on longer press.
* phone application is now litephone modified to use Qalee’s buttons.
* GorshPlayer is broken, if you have Qt4.5.2 librairies with phonon working on shr, tell me (?)//FIXME
* keyboard is still literky.
* Themable interface allows you to change some colours of the interface.
<br>WARNING :<br>
Qalee is in pre-alpha stage, a lot of thinks are not coded yet, other are broken, some may be changed. It's just a preview version of the current work!
http://www.qalee.org

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

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

{{Main|Qt Extended Improved}}

{{Template:Works on QtMoko}}
Another branch of development after discontinued Qt Extended is [http://activationrecord.net/radekp/qtmoko/ QT Moko]. Special feature are:
* QT Moko has better X support, which is much faster then X4,
* in QT Moko the AUX can bring menu for X application,
* QT Moko includes an X terminal with virtual keyboard and matchbox window manager
* in QT Moko with the X-Server support you can use X application like [http://www.tangogps.org/gps/articles/7-Installation.html#extended TangoGPS] as GPS application.

{{Main|QT Moko}}

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

{{Main|SHR}}

=== Slackware ===
{{Template:Works on Slackware}}
As of release 12.2, Slackware is now officially supported on the Neo Freerunner
[http://armedslack.org/]
--[[User:Djdas|djdas]] 15:54, 13 June 2009 (UTC)There aren't any confirmations of ArmedSlack running on Freerunner either on the website or the official ML, do you have any link pointing on that?
<br style="clear: both">
=== Abandoned ===

==== FDOM (FAT and Dirty Openmoko) ====
{{Template:Works on FDOM}}
[[FDOM]] was a distribution based on [[Om 2008]], updated with many ready-to-use applications and with fixes posted in the mailing lists.

{{Main|FDOM}}
<br style="clear: both">

==== Om series ====
* '''[[Om 2009]]''' was intended to be the new distro; it is not a simple follow-on from [[Om 2008]]. It is based on the [http://freesmartphone.org freesmartphone.org] milestone 5.5 framework. Development of Om 2009 was ended and developers moved on to work on other distros instead.

{{Main|Om2009}}

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

{{Main|Om 2008}}

* '''[[Om 2007.2]]''' was the first distribution created by Openmoko. The interface was totally finger-oriented, optimized for 285ppi, and very orange. It used the GTK+ stack, which is part of the [http://www.gnome.org/mobile/ GNOME Mobile] platform. This distribution is now considered obsolete and not being worked on by Openmoko Inc or by OpenedHand.

{{Main|Om 2007.2}}

=== Others / unreleased ===
* The [http://www.neopwn.com/software.php NeoPwn] network auditng system's core is a modified Linux 2.6.24 kernel, with cross-compiled module driver support for the numerous compatible addon devices running on a FULL Debian (ARMEL) operating system. The filesystem has been optimized for performance and size and includes the NeoPwn menu system and several GUI dialogs for hardware control and attack automation. ''Status: Unknown, the GPL requires source code to be distributed only to customers''.
* [http://runningbear.org/trac RunningBear] is an innovative, yet free and open-source Operating System for hackable devices driven by Bearstech. Lightweight, Portable, Secure, Friendly and Useful. ''Status: In development''.
* [http://pokylinux.org/ Poky] and Sato, by OpenedHand/Intel. An open source platform build tool derived from OE. It is a complete software development environment for the creation of Linux devices. It enables you to design, develop, build, debug, and test a complete, modern, software stack using Linux, the X Window System and GNOME Mobile based application frameworks for both ARM and x86 based platforms. ''Status: The "Nightly Build" Image works fine on Neo Freerunner, but phone functionality doesn't.''
* [http://pyneo.org/ PyNeo] pyneo is a stack for mobile devices excessivly using dbus, glib and evas. Pyneo is NO distribution but a middleware or framework like FSO which itself developed from a very early version of pyneo. Current pyneo images are entirely based on debian instead of oe. ''Status: still active and in development! ask around on #pyneo.org ''
* [http://www.quantum-step.com/ mySTEP] by Openmoko distributor Golden Delicious Computers is based on GNUstep and brings a Objective-C API to the Neo. Core GUI frameworks are "Foundation" & "AppKit". It has been shown on FOSDEM 2008, LinuxTag 2008 and SYSTEMS 2008 to run on the Neo 1973. If someone reengineers UIKit, (open) source code compatibility to iPhone apps appears achievable. ''Status: slow progress behind the scenes''
* [http://www.archmobile.org/ Archlinux] is a distribution that follows the KISS principle.

== Features by distribution/release target ==

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

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

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

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

=== User Interaction ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=8%|[[Om 2009]] !! width=8%|[[Om 2008]] !! width=8%|Om 2007.2 !! width=8%|[[SHR]] !! width=8%|[[Qt Extended Improved]] !! width=8%|[[Debian]] !! width=8%|[[Gentoo]] !! width=8%|[[Android]]
|-
| Finger friendly || {{Yes}} || Partially || Partially || {{Yes}} || {{Yes}} || {{Yes}} [[Illume|(1)]] || {{Yes}} || {{Yes}}
|-
| Accelerometer || {{Yes}} (1) || {{Yes}} [[Rotate|(1)]][[Gestures|(1)]] || {{No}} || {{Yes}} || {{No}} || {{Yes}} || ?? || {{Yes}}
|-
|}

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

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

Footnotes:

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

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

(*) unstable

==Quick download page==

[[Download]]

== See also ==

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

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

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

[[Category:Distributions| ]]

Manuals/Neo FreeRunner/eu

2010-01-30T18:06:27Z

Joseba:

{{Languages|Manuals/Neo FreeRunner}}

Mila esker Neo FreeRunner erosteagatik. [[Neo FreeRunner]] telefonoa Openmoko proiekturako sortu den bigarren hardware plataforma da. Gida honetan hasierako erabilerarako behar duzuna eta tresna berria ezagutzen ikasiko duzu.

[[Image:Freerunner box.png|200px|thumb|Neo FreeRunner Package]]

== Hardwarearen konfigurazioa, Neo Freerunnerra eta bere osagaiak ezagutzen hasi ==

=== Mikro-SD txartelaren, SIM Txartelaren eta bateriaren instalazioa ===

# Neo Freerunnerraren atzeko tapa kendu, horretarako, alboetatik heldu telefonoa, eta goian daukan arteka edo zirrikituan azkazalen laguntzaz atzerantz bultza eta atzeko tapa askatuko da.
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu13.jpg|233px|thumb|zirrikituan azkazalez bultza.|center]]</td>
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu14.jpg|250px|thumb|Atzeko estalkia askatu!|center]]</td>
</tr>
</table>
# Orain bateria jarri behar den kokagunea agerian dago, eta bere azpian telefoniako txartela eta Mikro SD txartela jartzeko guneak ere ikusiko dituzu.
# Lehendabizi SIM txartelaren estalkia askatu behar da, horretarako, beherantz (kanpoko USB entxufe alderantz) bultza metalezko klipa. Kontu handiz ibili, zati delikatua baita hau, eta indarrez eginez gero kalteak eragin daitezke. Norantza ere arretaz aztertu.
[[Image:menu11.jpg|260px|thumb|Jarri SIM eta SD txartelak hemen.|center]]
# Altxa SIM txartela eusteko klipa.
# Mikro-SD txartelak erabili aurretik begiratu [[Supported_microSD_cards |onartzen direla jakina den Mikro-SD txartelen zerrenda]].
# Mikro-SD euskarria bi aldetatik lotuta dago, Errazena alda bakoitza banaka askatzea da. Erditik tiraz bi aldeak batera askatzen saituz gero, loturak indar handiagoa egiten du, beraz, lehendabizi alde bat askatu eta gero bestea. Kontuz labanekin edota bihurkinekin! honako [http://people.openmoko.org/joerg/sdcard-handle/ argazkietan] ikus daiteke euskarria irekita eta txartelak sartuta.
# Sartu Mikro-SD txartela bere euskarrian. Kontuan izan euskarrian txartela eusteko kartolatxoak (eusteko topeak) daudela, kartola horien artetik sartu txartela (tente geratuko da txartela, kontaktuak beheko aldean) eta ondoren itxi euskarria txartela etzanda gera dadin. Txartelaren kontaktuak beheko aldean geratu beharko dute, alegia ez dira ikusiko, eta gainera telefonoaren ertzean egongo dira.
# Mikro-SD txartelaren euskarria etzan ondoren, bi lokailuak ondo itxi direla ziurtatu. Gaizki itxitako euskarriko txartela ez du ikusiko telefonoak.
# SIM txartela bere euskarrian sartu, kontu izan honek ere metalezko bi kartolatxo dauzkala, eta horien artean sartu behar dela.Berriz ere kontaktu elektrikoak beherantz geratu behar dute, eta ebakitako ertza FreeRunner gailuaren kanpo aldetik gertu geratu behar du (GPS antenaren aldean).
# Etzan SIM txartelaren euskarria eta metalezko klipa GPS antenaren aldera labaindu ondo itxita gera dadin.
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">
[[Image:FR_SIM_SD_open.jpg|457px|thumb|SIM and SD euskarriak irekita, eta txartelak beren lekuetan|center]]</td>
<td style="padding: 1px 1em 0; background: #ffffff;">
[[Image:Engchang.jpg|392px|thumb|Gailu batzuek itxura hau daukate, tanta modukoa ez da akatsa|center]]</td>
</tr>
</table>
# Sartu bateria horretarako gunean, bateriaren kontaktuak telefonoaren kontaktuekin elkartuz. Lehendabizi kontaktuen aldea sartu.
# FreeRunnerraren atzeko tapa bere tokian jarri.

{| class="wikitable" style="background#00CC00;border-left:1px solid white;border-right:1px solid white;border-top:0px solid white; border:1px solid #00CC00; float:right; margin: 0 0 1em 1em;"
! style="background:#00cc00;border-left:1px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #00CC00;" |<font color=white>Tips</font>
|-
!style="background:#ffffff;border-left:1px solid white;border-right:1px solid white;border-top:0px solid white; border:1px solid #FFFFff;" |
<div align=left>
[http://video.google.de/videoplay?docid=-8343770443102960945 Bideotxoa] ere ikus dezakezu. Neo gailuaren bertsio zaharrarekin egina den arren, antzeko prozesua da.
</div>

|}

===Neo FreeRunnerra kargatu===

Lehendabiziko erabileraren aurretik Bateria guztiz kargatu behar da. Bateria kargatzeko 1000mA-ko kargatzailea edota 500mA-ko karga eman dezakeen USB portu bat erabil daitezke. Gaur egungo konputagailuek ez daukate inolako arazorik NEO Freerunnera kargatzeko USB portuak erabiliz. '''Itzalita baldin badago, ez da kargatuko''', beraz, piztu eta interfaze grafikoa (GUI edo Graphical User Interface) agertu arte piztu dadila. USB kablea sartzen duzunean (USB kableak konputagailuari konektatuta egon behar du edota 1000mA-ko kargatzaileari, alegia, argi indarra eduki behar du) automatikoki piztuko da. Ez bada bere kabuz pizten, eskuz piztu dezakezu, horretarako, pizteko botoia sakatu (bost edo sei segundo sakatuta eduki). Botoi hau USB entxufearen azpian dago.

Nahiz eta kargatzaileak 2A-ko indarra emateko gaitasuna eduki, Neo Freerunnerraren karga-abiadura 1A-koa da, eta beraz, kargatze-abiadura kargatzailearen gaitasuna baino txikiagoa da.

Entxufeak hiru mota onartzen ditu: berez Ipar Ameriketako entxufea da, baina estalkia kendu eta Europako edota Erresuma Batuko entxufeetarako egokigailua jar daitezke entxufean. Horretarako, entxufearen estalkiaren kisketa sakatu eta estalkia kanporantz labaindu behar da. Kisketa entxufearen estalkiaren testua dagoen kontrako aldean dago. Kontuan izan Ipar Amerikako entxufearen bi konektoreak ez direla askatuko, horien gainetik sartu behar da egokigailua. Egokigailua ere antzera kentzen da.

Bateria kargatzeko denbora sarrerako indarraren araberakoa da,
# 100mA-ko indarraz 12~15 ordu behar dira (kontuan izan etete-egoeran ez badago 100mA baino gehiago behar dituela gailuak)
# sarrerako indarra 500mA-koa bada (PC-en USB konexioa) 2~3 ordu behar dira, eta
#1000mA-ko indarrez (kargatzailea) 1.5~3 ordu behar dira. (90%~100%) <br>
Gailuak 100 mA baino gehiago behar ditu lanean ari denean, beraz, USB bidezko indarra 100mAkoa baldin bada, eteteko egoeran ez badago, gailua ez da kargatuko.

{{Note|ikusi [[Neo_FreeRunner_Hardware_Issues|Neo FreeRunner Hardware arazoak]] bateria guztiz husten ez lagatzeari buruz.}}

===Botoiak eta konexioak ===

<table width="80%" style="clear: both; border-collapse: collapse" valign="top">
<tr>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu9.jpg|370px|thumb|Pizteko botoia, USBa eta kanpoko GPS Antena (ezkerretik eskuinera)|center]]</td>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu8.jpg|370px|thumb|AUX Botoia eta aurikularren jack-a (ezkerretik eskuinera)|center]]</td>
</tr>
<tr>
<td></td>
<td>'''Pizteko''' botoia
Ikututxoa edo kolpetxoa emanaz GTA02 gailua '''etete-egoeran''' jarriko da.

Sakatuta edukiz gero gailua itzali egingo da.</td>
<td></td>
<td>'''Aux''' botoia
Ikututxo bidez edo sakatuz pantaila blokeatuko da.
</td>
</tr>
</table>

'''Aurikularren Jack-a'''

Aurikularren jack-a 2.5mm dituen konektorea da, eta 4 kontaktu dauzka: stereo + MIC. Motorola smartphone (A780,A1200, ...) eta V-360 gailuek erabiltzen dutenarekin bateragarria da.

Informazio gehiago [[Headset|aurikularren]] orrian.

===Zure gailuaren aldaera zein den jakiteko===
Zure gailua zer nolakoa den jakitea komeni zaizu, hau da, gailuaren aldaera (revision) zein den zehaztea komeni da.

# Gogoan jaso data kodea, jaso duzun kutxaren azpian eranskailu batean egongo da.
# irakurri [[Finding_hardware_revision|hardware aldaeraren bila]]

Bi hauek garrantzitsuak dira, zure gailuan, fabrikan, zein irudi flasheatu (ezarri) duten jakiten lagunduko baitizute. (c.f. [[Distributions|banaketak]] eta [[GTA02_revisions | Neo FreeRunner (aka GTA02) aldaerak]]).

==Softwarea instalatu==

Freerunnerrean dagoen software ia guztia aldatu edo eguneratu daiteke, bai eta gailua pizteko beharrezkoa den '''abiarazlea''' eta GSM txipean dagoen softwarea ere.

Izatez, Neo FreeRunnerra berezko [[Distributions| banaketa]] bat barnean ezarrita duela iritsiko zaizu, beraz, hemendik aurrerakorik egin beharrik ez duzu izango. Irakurri [[Om_2008 | OM 2008]] [[Manuals/Om_2008|eskuliburua]] zure telefonoa erabiltzen hasteko. Gerora, zure gailuan [[Distributions|banaketa]] berriagoa edota erabilera zabalagoa duena edota aukera bereziak eskaintzen dituena instalatu nahi zenezake, kasu horretan irakurri ondokoa.

===Abiarazlea instalatu===

Telefonoko sistema eragilea abiarazteko beharrezkoa da bootloader edo abiarazlea. '''Qi''' da gomendatutako abiarazlea Neo FreeRunner gailuan. Horrekin, abiatzeko prozesua azkarragoa baita. Hainbat sistema eragileren artean aukeratu ahal izateko, U-Boot abiarazlea mantendu beharko zenuke, hau abiarazle zaharragoa da. Abiarazlea http://downloads.openmoko.org/distro/testing/NeoFreerunner/ helbidetik har dezakezu eta [[NeoTool]] programaren bidez zure Linux PCan instala dezakezu. (ikusi http://wiki.openmoko.org/wiki/No_Linux ez badaukazu Linuxpean dabilen PCrik, baina hobe zenuke linux banaketa zirraragarriren bat instalatuko bazenio zeure PCari)

===GSM Firmwarea eguneratu===

Gaur egungo GSM Firmwareaaren bertsioak Moko 11 izena du. Zure bertsioa zaharragoa bada bertsio berritzea egin beharko zenuke, horrela telefono gailuaren hainbat funtzionalitate-arazo konponduko baitira.



FreeRunner gailua mikroSD txartelean instalatutako sistemaren bidez abiaraziz hasi behar da, abiaratze honek automatikoki eragingo ditu beharrezkoak diren aginduak eta GSM firmwarea txipera irauliko (flasheatuko?) du. mikroSDra abiarazteko irudia kopiatzea era berezian egin behar izaten da (linuxeko dd agindua erabili beharko duzu ziurrenik) eta mikroSD irudia kopiatzerakoan mikroSDan dagoen informazioa guztiz ezabatuko da. Irudia tentuz jarri mikroSD txartelean, eta era egokian formateatu abiarazteko sistema egokia daukala ziurtatuz.
Prozedura hau fidagarria da GTA02 gailuan MOKO11 ezartzeko (flasheatzeko). Huts egiteko aukerak oso urriak dira _zehazki_ jarraitzen badituzu argibideak. Hemen azaldutako bideari jarraituz ez diozu kalterik eragingo zure gailuari.

'''Arreta berezia jarri `dd` agindua eragiterakoan nora kopiatu behar duen esaterakoan, dispositibo *fisikoa* adierazi behar da, esaterako /dev/sdm, eta *ez* partizioa (alegia ez /dev/sdmp1). Horrez gain, mikroSDko partizio guztiak desmontatuta daudela ziur egon `dd` agindua abiarazterakoan'''<br>
Aurrekoaz ziur zaudenean, ''berriz begiratu ea aurreko abisuko baldintza guztiak betetzen dituzun'', gainera, bada ez bada, ondo begiratu ea mikroSD dispositiboa den `dd` aginduari adierazitakoa, izan ere, disko gogorra adieraziz gero disko gogorreko eduki guztia ezabatuko baitu, eta oso erraza da nahastea, alegia, mikroSDa /dev/sdc izan daiteke, baina /dev/sdb disko gogorra izan daiteke. Beraz, '''arreta handiz idatzi agindua'''.

<ol>
<li>Jaitsi eta <tt>untar</tt> (desenpaketatu) http://people.openmoko.org/joerg/calypso_moko_FW/moko11/flash-moko11_uSD-image.tar.gz zeure mahai gaineko PCra. Irakurri <tt>README.tx</tt> fitxategia, untar egiterakoan paketetik aterako da fitxategia.</li>

<li>Zure PCko irakurgailuan sartu mikroSD txartela, eta automatikoki muntatutako partizioak desmuntatu (mikroSDko partizioak, noski), zZein partizio muntatu diren jakiteko <tt>mount</tt> edo <tt>df -h</tt> aginduak erabil ditzakezu. Desmuntatzeko ez erabili "era seguruan atera txartela", <tt>umount</tt> agindua erabili desmuntatzeko.</li>

<li>mikroSD txartelera <tt>flash-moko11-2.image</tt> fitxategian dagoen irudia fisikoki idazteko <tt>dd</tt> agindua erabili. Kontuz agindu honekin: non idatzi behar duen esateko mikroSD txartelaren dispositibo fisikoa zein den esan behar zaio aginduari, ez partizioren bat, baizik eta dispositiboa bera. Gainera, dispositiboan dagoen eduki guztia ezabatuko du eragiketak, beraz, dispositibo okerra esan ezkero, kalte handia sor daiteke. <tt>dd</tt> aginduari disko gogorrari dagokion dispositibo fisikoan kopiatzeko agindua emango bagenio, partizio taula eta bertako eduki guztia ezabatuko du, beraz, sistema osoa berrinstaltu beharko genuke. Eragiketa hau egiteko orduan root erabiltzailearen baimenak eduki behar dira, alegia root bezala sartu behar da sisteman edo sudo agindu erabili beharko da:</li>

% sudo dd if=flash-moko11-2.image of=/dev/mmcblk0

<li>mikroSD txartela atera aurretik <tt>sync</tt> edo <tt>eject <device></tt> aginduak erabiltzea komeni da, izan ere txartelera informazioa guztiz pasa dela ziur egon behar baitugu.</li>

<li>Sartu mikroSD txartela zeure FreeRunner mugikorrera, eta abiarazi gailua '''[[Booting_the_Neo_FreeRunner#Log_into_U-Boot_in_the_NOR_Flash|NOR-U-Boot]]''' bideari jarraituz, eta aukeratu "Boot from microSD" aukera.</li>

<li>Firmwarea flash memoriara kopiatzeko prozesua abiatuko dela ikusiko duzu, eta bukaeran, 6 minutu inguru igaro ondoren, "d_o_n_e" kolore berdez idatzita azalduko da. Une horretan pizteko/itzaltzeko botoiak ezin du Freerunnerra itzali, botoia sakatzeak eten/itzuli funtzioak beteko ditu, baina ez itzaltzekoa. Gutxienez bi eratara itzal dezakezu Freerunnerra, alde batetik, <tt>ssh</tt> aginduaren bidez FreeRunnerrera konektatu usb kable bidez lotutako PC batetik (edo wifi konexio bidez) eta itzaltzeko agindua eragin dezakezu: <br>
# shutdown -h now<br>
Itzaltzeko beste era bat ere badago, askoz ere sinpleagoa da bigarren era hau (baina ez hain dotorea): bateria kendu eta itzali egingo da, a zer erremedio!.
Firmwarea ondo kopiatu dela ikusteko, ssh konexio bidez <tt>mickeyterm</tt> erabil daiteke modemarekin komunikatzeko eta bertsioa begiratzeko</li>
</ol>
====OHARRA====

Zure PCak mikroSD txartelak irakurtzeko gailurik ez badauka, mikroSD txartelera <tt>dd</tt> agindu bidez moko11 irudiaren kopia FreeRunner gailuan bertan egin dezakezu: instalatu <tt>task-base-smbfs</tt>, mikroSD txartela desmuntatu, horretarako <tt>umount /media/card</tt> agindua erabili (partizio gehiago baleuzka eta horiek ere muntatuta baleude guztiak desmuntatu). Une honetan bi aukera dauzkazu gutxienez:
<ol>
<li> Zure PCan dagoen irudia daukan direktorioa FreeRunnerreko fitxategi sisteman muntatu dezakezu, eta ondoren, <tt>dd</tt> agindu bidez zuzenean FreeRunnerrean dagoen mikroSD txartelera kopia dezakezu. Prozesu horrek 12 minutu inguru iraun ditzake. Eragiketa hau FreeRunnerreko shell batetik egin behar da.
</li>
<li>Alderantziz ere jardun daiteke, alegia, PCko shell batean lan egin dezakezu, horretarako, lehenengo FreeRunnerrean mikroSD txartela desmuntatu:<br>
root@om-gta02 ~ $ umount /media/card<br>
Eta ondoren, PCko shell batean (usb edo wifi konexioa eskatzen du honek):<br>
scp flash-moko11-2.image root@192.168.0.202:/dev/mmcblk0
</li>
</ol>
Prozesu horiek azkartu egin daitezke, irudia gzip bidez konprimituz makinatik makinara pasa beharreko informazio-kopurua gutxitu egin daiteke, eta deskonprimitzeko aginduari zuzenean mikroSD txartelera kopiatzeko esan diezaiokegu:

% gzip -d < flash-moko11-2.image.gz > /dev/mmcblk0

Agindu honenkin, eta FreeRunnerreko fitxategi sisteman nahikoa leku libre edukiz gero, ez dogo PCa erabili beharrik, alegia, konprimitutako fitxategia FreeRunnerrean bertan jaso daiteke, eta deskonprimitu mikroSD txartelera. Baina 92MB libre behar ditu gutxi gora behera.

====BIGARREN OHARRA====

Abiorako [[Qi]] instalatuta eduki ala ez (ikusi aurrekoa), pizterakoan NOR menuraino joan behar da (horretarako AUX botoia sakatuta daukazun bitartean pizteko botoia sakatu) eta bertan "Boot from microSD (fat/ext2)" aukeratu behar duzu instalazio prozesua abiatu dadin. (per DocScrutinizer in #openmoko). '''Ez''' utzi Qi abiarazleari mikroSDko partizioa izan dadin sistemaren abioa. Antzekoa dirudien arren, berdez idatzitako "d_o_n_e" ez da azalduko eta ondorioz egin beharrekoa ez du egingo.

Firmwarearen bertsioa zein den jakiteko [[OpenmokoFramework/mickeyterm|mickeyterm]] erabil dezakezu (cmd: "AT+CGMR"). SHR banaketa baldin badaukazu, ezarpenetan (settings) "Phone/Modem Information" aukerak firmwarearen bertsio zenbakia zein den esango dizu.

===Banaketa baten instalazioa===

Atal honetan Neo FreeRunnerreko barne Flash memorian banaketa berri bat nola instalatzen den azaltzen da. mikroSD txartelean instalatu nahi baduzu, banaketaren eskuliburuetan begiratu nola egiten den hori.

Banaketa berri bat instalatzeko bi fitxategi beharko dituzu, bata fitxategi-sistema nagusiaren irudia izango da (rootfs), eta bestea, kernelaren irudia. Fitxategi-sistema nagusiaren irudia daukan fitxategiak ".jffs2" eduki ohi du bukaera gisa. eta kernelaren irudiak ".uimage.bin" bukaera edukiko du. Fitxategi hauek http://wiki.openmoko.org/wiki/Download helbidetik har ditzakezu. NeoTool programa erabili banaketa zure FreeRunnerrean instalatzeko. Barneko Flash memorian instalatzeko 70Mb-eko sistema batek 15 minutu inguru beharko ditu. Sistema Flash-eratu bitartean bateriarik gabe ez dela geratuko ziur egotea komeni da. Kontuan izan.

Flash memorian dena behar bezala dagoenean honakoa azalduko da pantailan:

<pre>
status(0) = No error condition is present
Done!
</pre>

[[Category:Manuals]]

Manuals/Neo FreeRunner/eu

2010-01-30T18:03:11Z

Joseba:

{{Languages|Manuals/Neo FreeRunner}}

Mila esker Neo FreeRunner erosteagatik. [[Neo FreeRunner]] telefonoa Openmoko proiekturako sortu den bigarren hardware plataforma da. Gida honetan hasierako erabilerarako behar duzuna eta tresna berria ezagutzen ikasiko duzu.

[[Image:Freerunner box.png|200px|thumb|Neo FreeRunner Package]]

== Hardwarearen konfigurazioa, Neo Freerunnerra eta bere osagaiak ezagutzen hasi ==

=== Mikro-SD txartelaren, SIM Txartelaren eta bateriaren instalazioa ===

# Neo Freerunnerraren atzeko tapa kendu, horretarako, alboetatik heldu telefonoa, eta goian daukan arteka edo zirrikituan azkazalen laguntzaz atzerantz bultza eta atzeko tapa askatuko da.
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu13.jpg|233px|thumb|zirrikituan azkazalez bultza.|center]]</td>
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu14.jpg|250px|thumb|Atzeko estalkia askatu!|center]]</td>
</tr>
</table>
# Orain bateria jarri behar den kokagunea agerian dago, eta bere azpian telefoniako txartela eta Mikro SD txartela jartzeko guneak ere ikusiko dituzu.
# Lehendabizi SIM txartelaren estalkia askatu behar da, horretarako, beherantz (kanpoko USB entxufe alderantz) bultza metalezko klipa. Kontu handiz ibili, zati delikatua baita hau, eta indarrez eginez gero kalteak eragin daitezke. Norantza ere arretaz aztertu.
[[Image:menu11.jpg|260px|thumb|Jarri SIM eta SD txartelak hemen.|center]]
# Altxa SIM txartela eusteko klipa.
# Mikro-SD txartelak erabili aurretik begiratu [[Supported_microSD_cards |onartzen direla jakina den Mikro-SD txartelen zerrenda]].
# Mikro-SD euskarria bi aldetatik lotuta dago, Errazena alda bakoitza banaka askatzea da. Erditik tiraz bi aldeak batera askatzen saituz gero, loturak indar handiagoa egiten du, beraz, lehendabizi alde bat askatu eta gero bestea. Kontuz labanekin edota bihurkinekin! honako [http://people.openmoko.org/joerg/sdcard-handle/ argazkietan] ikus daiteke euskarria irekita eta txartelak sartuta.
# Sartu Mikro-SD txartela bere euskarrian. Kontuan izan euskarrian txartela eusteko kartolatxoak (eusteko topeak) daudela, kartola horien artetik sartu txartela (tente geratuko da txartela, kontaktuak beheko aldean) eta ondoren itxi euskarria txartela etzanda gera dadin. Txartelaren kontaktuak beheko aldean geratu beharko dute, alegia ez dira ikusiko, eta gainera telefonoaren ertzean egongo dira.
# Mikro-SD txartelaren euskarria etzan ondoren, bi lokailuak ondo itxi direla ziurtatu. Gaizki itxitako euskarriko txartela ez du ikusiko telefonoak.
# SIM txartela bere euskarrian sartu, kontu izan honek ere metalezko bi kartolatxo dauzkala, eta horien artean sartu behar dela.Berriz ere kontaktu elektrikoak beherantz geratu behar dute, eta ebakitako ertza FreeRunner gailuaren kanpo aldetik gertu geratu behar du (GPS antenaren aldean).
# Etzan SIM txartelaren euskarria eta metalezko klipa GPS antenaren aldera labaindu ondo itxita gera dadin.
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">
[[Image:FR_SIM_SD_open.jpg|457px|thumb|SIM and SD euskarriak irekita, eta txartelak beren lekuetan|center]]</td>
<td style="padding: 1px 1em 0; background: #ffffff;">
[[Image:Engchang.jpg|392px|thumb|Gailu batzuek itxura hau daukate, tanta modukoa ez da akatsa|center]]</td>
</tr>
</table>
# Sartu bateria horretarako gunean, bateriaren kontaktuak telefonoaren kontaktuekin elkartuz. Lehendabizi kontaktuen aldea sartu.
# FreeRunnerraren atzeko tapa bere tokian jarri.

{| class="wikitable" style="background#00CC00;border-left:1px solid white;border-right:1px solid white;border-top:0px solid white; border:1px solid #00CC00; float:right; margin: 0 0 1em 1em;"
! style="background:#00cc00;border-left:1px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #00CC00;" |<font color=white>Tips</font>
|-
!style="background:#ffffff;border-left:1px solid white;border-right:1px solid white;border-top:0px solid white; border:1px solid #FFFFff;" |
<div align=left>
[http://video.google.de/videoplay?docid=-8343770443102960945 Bideotxoa] ere ikus dezakezu. Neo gailuaren bertsio zaharrarekin egina den arren, antzeko prozesua da.
</div>

|}

===Neo FreeRunnerra kargatu===

Lehendabiziko erabileraren aurretik Bateria guztiz kargatu behar da. Bateria kargatzeko 1000mA-ko kargatzailea edota 500mA-ko karga eman dezakeen USB portu bat erabil daitezke. Gaur egungo konputagailuek ez daukate inolako arazorik NEO Freerunnera kargatzeko USB portuak erabiliz. '''Itzalita baldin badago, ez da kargatuko''', beraz, piztu eta interfaze grafikoa (GUI edo Graphical User Interface) agertu arte piztu dadila. USB kablea sartzen duzunean (USB kableak konputagailuari konektatuta egon behar du edota 1000mA-ko kargatzaileari, alegia, argi indarra eduki behar du) automatikoki piztuko da. Ez bada bere kabuz pizten, eskuz piztu dezakezu, horretarako, pizteko botoia sakatu (bost edo sei segundo sakatuta eduki). Botoi hau USB entxufearen azpian dago.

Nahiz eta kargatzaileak 2A-ko indarra emateko gaitasuna eduki, Neo Freerunnerraren karga-abiadura 1A-koa da, eta beraz, kargatze-abiadura kargatzailearen gaitasuna baino txikiagoa da.

Entxufeak hiru mota onartzen ditu: berez Ipar Ameriketako entxufea da, baina estalkia kendu eta Europako edota Erresuma Batuko entxufeetarako egokigailua jar daitezke entxufean. Horretarako, entxufearen estalkiaren kisketa sakatu eta estalkia kanporantz labaindu behar da. Kisketa entxufearen estalkiaren testua dagoen kontrako aldean dago. Kontuan izan Ipar Amerikako entxufearen bi konektoreak ez direla askatuko, horien gainetik sartu behar da egokigailua. Egokigailua ere antzera kentzen da.

Bateria kargatzeko denbora sarrerako indarraren araberakoa da,
# 100mA-ko indarraz 12~15 ordu behar dira (kontuan izan etete-egoeran ez badago 100mA baino gehiago behar dituela gailuak)
# sarrerako indarra 500mA-koa bada (PC-en USB konexioa) 2~3 ordu behar dira, eta
#1000mA-ko indarrez (kargatzailea) 1.5~3 ordu behar dira. (90%~100%) <br>
Gailuak 100 mA baino gehiago behar ditu lanean ari denean, beraz, USB bidezko indarra 100mAkoa baldin bada, eteteko egoeran ez badago, gailua ez da kargatuko.

{{Note|ikusi [[Neo_FreeRunner_Hardware_Issues|Neo FreeRunner Hardware arazoak]] bateria guztiz husten ez lagatzeari buruz.}}

===Botoiak eta konexioak ===

<table width="80%" style="clear: both; border-collapse: collapse" valign="top">
<tr>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu9.jpg|370px|thumb|Pizteko botoia, USBa eta kanpoko GPS Antena (ezkerretik eskuinera)|center]]</td>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu8.jpg|370px|thumb|AUX Botoia eta aurikularren jack-a (ezkerretik eskuinera)|center]]</td>
</tr>
<tr>
<td></td>
<td>'''Pizteko''' botoia
Ikututxoa edo kolpetxoa emanaz GTA02 gailua '''etete-egoeran''' jarriko da.

Sakatuta edukiz gero gailua itzali egingo da.</td>
<td></td>
<td>'''Aux''' botoia
Ikututxo bidez edo sakatuz pantaila blokeatuko da.
</td>
</tr>
</table>

'''Aurikularren Jack-a'''

Aurikularren jack-a 2.5mm dituen konektorea da, eta 4 kontaktu dauzka: stereo + MIC. Motorola smartphone (A780,A1200, ...) eta V-360 gailuek erabiltzen dutenarekin bateragarria da.

Informazio gehiago [[Headset|aurikularren]] orrian.

===Zure gailuaren aldaera zein den jakiteko===
Zure gailua zer nolakoa den jakitea komeni zaizu, hau da, gailuaren aldaera (revision) zein den zehaztea komeni da.

# Gogoan jaso data kodea, jaso duzun kutxaren azpian eranskailu batean egongo da.
# irakurri [[Finding_hardware_revision|hardware aldaeraren bila]]

Bi hauek garrantzitsuak dira, zure gailuan, fabrikan, zein irudi flasheatu (ezarri) duten jakiten lagunduko baitizute. (c.f. [[Distributions|banaketak]] eta [[GTA02_revisions | Neo FreeRunner (aka GTA02) aldaerak]]).

==Softwarea instalatu==

Freerunnerrean dagoen software ia guztia aldatu edo eguneratu daiteke, bai eta gailua pizteko beharrezkoa den '''abiarazlea''' eta GSM txipean dagoen softwarea ere.

Izatez, Neo FreeRunnerra berezko [[Distributions| banaketa]] bat barnean ezarrita duela iritsiko zaizu, beraz, hemendik aurrerakorik egin beharrik ez duzu izango. Irakurri [[Om_2008 | OM 2008]] [[Manuals/Om_2008|eskuliburua]] zure telefonoa erabiltzen hasteko. Gerora, zure gailuan [[Distributions|banaketa]] berriagoa edota erabilera zabalagoa duena edota aukera bereziak eskaintzen dituena instalatu nahi zenezake, kasu horretan irakurri ondokoa.

===Abiarazlea instalatu===

Telefonoko sistema eragilea abiarazteko beharrezkoa da bootloader edo abiarazlea. '''Qi''' da gomendatutako abiarazlea Neo FreeRunner gailuan. Horrekin, abiatzeko prozesua azkarragoa baita. Hainbat sistema eragileren artean aukeratu ahal izateko, U-Boot abiarazlea mantendu beharko zenuke, hau abiarazle zaharragoa da. Abiarazlea http://downloads.openmoko.org/distro/testing/NeoFreerunner/ helbidetik har dezakezu eta [[NeoTool]] programaren bidez zure Linux PCan instala dezakezu. (ikusi http://wiki.openmoko.org/wiki/No_Linux ez badaukazu Linuxpean dabilen PCrik, baina hobe zenuke linux banaketa zirraragarriren bat instalatuko bazenio zeure PCari)

===GSM Firmwarea eguneratu===

Gaur egungo GSM Firmwareaaren bertsioak Moko 11 izena du. Zure bertsioa zaharragoa bada bertsio berritzea egin beharko zenuke, horrela telefono gailuaren hainbat funtzionalitate-arazo konponduko baitira.



FreeRunner gailua mikroSD txartelean instalatutako sistemaren bidez abiaraziz hasi behar da, abiaratze honek automatikoki eragingo ditu beharrezkoak diren aginduak eta GSM firmwarea txipera irauliko (flasheatuko?) du. mikroSDra abiarazteko irudia kopiatzea era berezian egin behar izaten da (linuxeko dd agindua erabili beharko duzu ziurrenik) eta mikroSD irudia kopiatzerakoan mikroSDan dagoen informazioa guztiz ezabatuko da. Irudia tentuz jarri mikroSD txartelean, eta era egokian formateatu abiarazteko sistema egokia daukala ziurtatuz.
Prozedura hau fidagarria da GTA02 gailuan MOKO11 ezartzeko (flasheatzeko). Huts egiteko aukerak oso urriak dira _zehazki_ jarraitzen badituzu argibideak. Hemen azaldutako bideari jarraituz ez diozu kalterik eragingo zure gailuari.

'''Arreta berezia jarri `dd` agindua eragiterakoan nora kopiatu behar duen esaterakoan, dispositibo *fisikoa* adierazi behar da, esaterako /dev/sdm, eta *ez* partizioa (alegia ez /dev/sdmp1). Horrez gain, mikroSDko partizio guztiak desmontatuta daudela ziur egon `dd` agindua abiarazterakoan'''<br>
Aurrekoaz ziur zaudenean, ''berriz begiratu ea aurreko abisuko baldintza guztiak betetzen dituzun'', gainera, bada ez bada, ondo begiratu ea mikroSD dispositiboa den `dd` aginduari adierazitakoa, izan ere, disko gogorra adieraziz gero disko gogorreko eduki guztia ezabatuko baitu, eta oso erraza da nahastea, alegia, mikroSDa /dev/sdc izan daiteke, baina /dev/sdb disko gogorra izan daiteke. Beraz, '''arreta handiz idatzi agindua'''.

<ol>
<li>Jaitsi eta <tt>untar</tt> (desenpaketatu) http://people.openmoko.org/joerg/calypso_moko_FW/moko11/flash-moko11_uSD-image.tar.gz zeure mahai gaineko PCra. Irakurri <tt>README.tx</tt> fitxategia, untar egiterakoan paketetik aterako da fitxategia.</li>

<li>Zure PCko irakurgailuan sartu mikroSD txartela, eta automatikoki muntatutako partizioak desmuntatu (mikroSDko partizioak, noski), zZein partizio muntatu diren jakiteko <tt>mount</tt> edo <tt>df -h</tt> aginduak erabil ditzakezu. Desmuntatzeko ez erabili "era seguruan atera txartela", <tt>umount</tt> agindua erabili desmuntatzeko.</li>

<li>mikroSD txartelera <tt>flash-moko11-2.image</tt> fitxategian dagoen irudia fisikoki idazteko <tt>dd</tt> agindua erabili. Kontuz agindu honekin: non idatzi behar duen esateko mikroSD txartelaren dispositibo fisikoa zein den esan behar zaio aginduari, ez partizioren bat, baizik eta dispositiboa bera. Gainera, dispositiboan dagoen eduki guztia ezabatuko du eragiketak, beraz, dispositibo okerra esan ezkero, kalte handia sor daiteke. <tt>dd</tt> aginduari disko gogorrari dagokion dispositibo fisikoan kopiatzeko agindua emango bagenio, partizio taula eta bertako eduki guztia ezabatuko du, beraz, sistema osoa berrinstaltu beharko genuke. Eragiketa hau egiteko orduan root erabiltzailearen baimenak eduki behar dira, alegia root bezala sartu behar da sisteman edo sudo agindu erabili beharko da:</li>

% sudo dd if=flash-moko11-2.image of=/dev/mmcblk0

<li>mikroSD txartela atera aurretik <tt>sync</tt> edo <tt>eject <device></tt> aginduak erabiltzea komeni da, izan ere txartelera informazioa guztiz pasa dela ziur egon behar baitugu.</li>

<li>Sartu mikroSD txartela zeure FreeRunner mugikorrera, eta abiarazi gailua '''[[Booting_the_Neo_FreeRunner#Log_into_U-Boot_in_the_NOR_Flash|NOR-U-Boot]]''' bideari jarraituz, eta aukeratu "Boot from microSD" aukera.</li>

<li>Firmwarea flash memoriara kopiatzeko prozesua abiatuko dela ikusiko duzu, eta bukaeran, 6 minutu inguru igaro ondoren, "d_o_n_e" kolore berdez idatzita azalduko da. Une horretan pizteko/itzaltzeko botoiak ezin du Freerunnerra itzali, botoia sakatzeak eten/itzuli funtzioak beteko ditu, baina ez itzaltzekoa. Gutxienez bi eratara itzal dezakezu Freerunnerra, alde batetik, <tt>ssh</tt> aginduaren bidez FreeRunnerrera konektatu usb kable bidez lotutako PC batetik (edo wifi konexio bidez) eta itzaltzeko agindua eragin dezakezu: <br>
# shutdown -h now<br>
Itzaltzeko beste era bat ere badago, askoz ere sinpleagoa da bigarren era hau (baina ez hain dotorea): bateria kendu eta itzali egingo da, a zer erremedio!.
Firmwarea ondo kopiatu dela ikusteko, ssh konexio bidez <tt>mickeyterm</tt> erabil daiteke modemarekin komunikatzeko eta bertsioa begiratzeko</li>
</ol>
====OHARRA====

Zure PCak mikroSD txartelak irakurtzeko gailurik ez badauka, mikroSD txartelera <tt>dd</tt> agindu bidez moko11 irudiaren kopia FreeRunner gailuan bertan egin dezakezu: instalatu <tt>task-base-smbfs</tt>, mikroSD txartela desmuntatu, horretarako <tt>umount /media/card</tt> agindua erabili (partizio gehiago baleuzka eta horiek ere muntatuta baleude guztiak desmuntatu). Une honetan bi aukera dauzkazu gutxienez:
<ol>
<li> Zure PCan dagoen irudia daukan direktorioa FreeRunnerreko fitxategi sisteman muntatu dezakezu, eta ondoren, <tt>dd</tt> agindu bidez zuzenean FreeRunnerrean dagoen mikroSD txartelera kopia dezakezu. Prozesu horrek 12 minutu inguru iraun ditzake. Eragiketa hau FreeRunnerreko shell batetik egin behar da.
</li>
<li>Alderantziz ere jardun daiteke, alegia, PCko shell batean lan egin dezakezu, horretarako, lehenengo FreeRunnerrean mikroSD txartela desmuntatu:<br>
root@om-gta02 ~ $ umount /media/card<br>
Eta ondoren, PCko shell batean (usb edo wifi konexioa eskatzen du honek):<br>
scp flash-moko11-2.image root@192.168.0.202:/dev/mmcblk0
</li>
</ol>
Prozesu horiek azkartu egin daitezke, irudia gzip bidez konprimituz makinatik makinara pasa beharreko informazio-kopurua gutxitu egin daiteke, eta deskonprimitzeko aginduari zuzenean mikroSD txartelera kopiatzeko esan diezaiokegu:

% gzip -d < flash-moko11-2.image.gz > /dev/mmcblk0

Agindu honenkin, eta FreeRunnerreko fitxategi sisteman nahikoa leku libre edukiz gero, ez dogo PCa erabili beharrik, alegia, konprimitutako fitxategia FreeRunnerrean bertan jaso daiteke, eta deskonprimitu mikroSD txartelera. Baina 92MB libre behar ditu gutxi gora behera.

====BIGARREN OHARRA====

Abiorako [[Qi]] instalatuta eduki ala ez (ikusi aurrekoa), pizterakoan NOR menuraino joan behar da (horretarako AUX botoia sakatuta daukazun bitartean pizteko botoia sakatu) eta bertan "Boot from microSD (fat/ext2)" aukeratu behar duzu instalazio prozesua abiatu dadin. (per DocScrutinizer in #openmoko). '''Ez''' utzi Qi abiarazleari mikroSDko partizioa izan dadin sistemaren abioa. Antzekoa dirudien arren, berdez idatzitako "d_o_n_e" ez da azalduko eta ondorioz egin beharrekoa ez du egingo.

Firmwarearen bertsioa zein den jakiteko [[OpenmokoFramework/mickeyterm|mickeyterm]] erabil dezakezu (cmd: "AT+CGMR"). SHR banaketa baldin badaukazu, ezarpenetan (settings) "Phone/Modem Information" aukerak firmwarearen bertsio zenbakia zein den esango dizu.

===Banaketa baen instalazioa===

Atal honetan Neo FreeRunnerreko barne Flash memorian banaketa berri bat nola instalatzen den azaltzen da. mikroSD txartelean instalatu nahi baduzu, banaketaren eskuliburuetan begiratu nola egiten den hori.

Banaketa berri bat instalatzeko bi fitxategi beharko dituzu, bata fitxategi sistema nagusiaren irudia izango da (rootfs), eta bestea, kernelaren irudia. Fitxategi sistema nagusiaren irudia daukan fitxategiak ".jffs2" eduki ohi du bukaera gisa. eta kernelaren irudiak ".uimage.bin" bukaera edukiko du. Fitxategi hauek http://wiki.openmoko.org/wiki/Download helbidetik har ditzakezu. NeoTool programa erabili banaketa zure FreeRunnerrean instalatzeko. Barneko Flash memorian instalatzeko 70Mb-eko sistema batek 15 minutu inguru beharko ditu. Sistema Flash-eratu bitartean bateriarik gabe ez dela geratuko ziur egotea komeni da. Kontuan izan.

Flash memorian dena behar bezala dagoenean honakoa azalduko da pantailan:

<pre>
status(0) = No error condition is present
Done!
</pre>

[[Category:Manuals]]

Distributions/eu

2010-01-30T17:35:33Z

Joseba:

{{Languages|Distributions}}

{|align=right
|__TOC__
|}
{| class="wikitable" style="float:left;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|<font color=white>Distributions</font>
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* <font color='#BBBBBB'>Openmoko (official)</font>
** [[Om 2009]]
** [[Om 2008]]
** [[Om 2007.2]]
* <font color='#BBBBBB'>Om Community</font>
** [[Android]]
** [[Debian]]
** [[Gentoo]]
** [[Hackable:1]]
** [[Mer]]
** [[Neovento]]
** [[OpenWrt]]
** [[Qt Extended Improved]]
** [[SHR]]
</div>
|-
|}
== Banaketei buruz ==
Openmoko banaketak hainbat mobiletan erabiltzeko diseinatu dira, baina helburu nagusia Openmoko Inc. proiektuaren [[GTA01:Neo 1973|Neo 1973]] eta [[Neo FreeRunner]] telefono mugikorretan funtzionatzea dute. GNU/Linux banaketak dira, alegia, Linux sistema eragilea eta erabilera zabaleko hainbat aplikazioz osatutako aplikazio multzoak dira. Zeure telefonoan banaketa horietako edozein instala zenezake, edo nahi izanez gero, banaketa bat baino gehiago eduki ditzakezu eta pizterakoan aukeratu zein banaketarekin abiarazi nahi duzun. Banaketaren bat deskargatzeko ikusi [[Download]], instalaziorako argibideak [[Flashing the Neo FreeRunner|FreeRunnerrean banaketen instalazioa]] orrian aurkituko dituzu.

Horrez gain, Openmoko banaketak [[Supported devices|beste]] mobil batzuetan ere instala daitezke, eta, era berean, beste banaketa batzuek ere instala daitezke Openmoko proiektuaren mobiletan.

=== Banaketa egokiaren aukera ===

2009ko abuztuaz geroztik egindako inkesta baten arabera [[SHR]] da gehien erabiltzen den banaketa, eta horri openmokoren banaketek jarraitzen diote ([[Om 2007]], [[Om 2008]] eta [[Om 2009]] hirurak bakar baten moduan hartuz gero beti ere), beste hainbat aukera ere badaude: [[Debian]], Debianen oinarritutako [[Hackable:1]], [[Qt Extended Improved]], [[Android]], Qtmoko eta abar.[http://doodle.com/sd2c8d8snr23eeqq] Om 2009 banaketaren garapena geratu egin da ordea, eta beraz bere erabiltzaileek beste banaketaren batera pasa beharko dute.

=== Kontuan izan ===

* Egonkorra hitzak FreeRunnerraren munduan ez du Debianen munduko esanahi bera.
* Banaketa gehienek abiatzaile, kernel, driver eta hardware berak erabiltzen dituzte. Ondorioz, behe mailako hutsegite berdinak agertzen dira banaketa gehienetan. Azken aplikazio zirraragarriek akats zaharrak konponduta edukiko dituzte, baina berriak bertan azalduko dira...
* Banaketa hauek aplikazioen biltegiak ere eduki ohi dituzte. bertatik instalatu aplikazio berriak, beste batetik instalatzea ideia '''TXARRA''' da. Ikusi [[installing alien package|beste banaketen aplikazioen instalazioa]].
* Banaketa hauen artean batetik besterako maila igoerak (upgradeak) ez dira ondo probatuta egoten, ondorioz, eguneraketak biltegiak aldatuz eginez gero, aplikazioeak apurtzea ekar dezake, edo okerragoa dena, abiarazi ezin den sistemarekin bukatu daiteke. Egin behar dena sistema FreeRunnerraren Flash memorian instalatzea da, horretarako [[dfu-util]] erabiliz, horrela, banaketa ezberdinen artean aukeratu ahal izango duzu. Abiaratze bikoitza ezar daiteke [[Booting from SD|MikroSD]] edo [[Booting from NFS|NFS]]) erabiliz.
* [[Marketing Mistakes|merkaturatze akatsak]] eta aurreinstalatutako banaketak

== Gainbegirada ==

=== Android ===
{{Template:Works on Android}}
[http://code.google.com/android/ Android] gailu mobilentzat garatutako software metaketa bat da, bere arduraduna [http://www.openhandsetalliance.com/ The Open Handset Alliance] da. Openmokok guztiz sostengatzen eta babesten du Android FreeRunnerrean erabilia izan dadin.

Android dagoenekoz Freerunnerra eguneroko mobil gisa erabiltzeko garapen mailara iritsia da, dena den, kontua eta arreta eskatzen duten gaiak daude oraindik. Informazio gehiago edukitzeo, Wikiko Androiden atal nagusia aztertzea gomendatzen dizut.

{{Main|Android} Bestalde, [http://wiki.openmoko.org/wiki/User:Seanmcneil3 Sean McNeil] erabiltzailearen web orria ere gomendagarria da informazio gehiago nahi baduzu.

=== Debian ===
{{Template:Works on Debian}}
[[Debian]] "sistema eragile unibertsala" da. Milaka paketa eta aplikazio dauzka (gehenak mahai gaineko ordenadoreetarako edota zerbitzarietarako paketeak dira). Joachim "nomeata" Breitner [http://wiki.debian.org/Teams/DebianFSO pkg-fso] taldeko kidearen hitzetan, Debian, Openmokoren zentzuan, ez da banaketa bat, horren ordez, Openmokoren beste banaketentzat azpiegitura edota oinarri-sistematzat har daiteke. Oraingoz,alatzeko beste bide bat bezala har daiteke, baina bide honek leku gehiago hartzen du eta askoz programa gehiago eskaintzen ditu.

{{Main|Debian}}

=== Gentoo ===
{{Template:Works on Gentoo}}
[[Gentoo]] banaketa aukeratzearen banaketa da. Gentoo instalatzerakoan erraz ulertuko duzu horren esanahia: zer konpilatu nahi duzun eta zer ez aukeratu ahal izango duzu, nola instalatu nahi duzun ere bai, zein log-sistema nahi duzun... Gentoo azkarra da, modernoa eta diseinu argia du, eta egokitzeko aukera eskaintzen du. Software librez egina dago, eta ez du ezkutatzen bere barnean dagoena. Paketeen mantenurako Portage aplikazioa erabiltzen du, Python hizkuntzan idatzita dago, beraz, erraz ikus eta alda daiteke jatorrizko kodea. Paketeen kudeaketa-sistemak jatorrizko kodea (iturburu-kodea) erabiltzen du (nahiz eta konpilatutakoak ere erabil ditzakeen) eta Gentoo-ren konfigurazioa ere testu fitxategien bidez egiten da. Ikus dezakezunez, dena irekia eta aldagarria.

{{Main|Gentoo}}

=== Hackable:1 ===
{{Template:Works on Hackable:1}}
Hackable1 is a community distribution for hackable devices like the Neo Freerunner. It is based on Debian and 2007.2 userland which has been abandoned by Openmoko. It follows the GNOME mobile platform.
{{Main|Hackable:1}}
<br style="clear: both">
=== Mer ===
{{Template:Works on Mer}}
[[Mer]] is a distribution based on [[Maemo]].
<br style="clear: both">
=== Mokotouch ===
{{Template:Works on Mokotouch}}
[[MokoTouch]] wants to be a replacement for the OM Distribution. It will contain apps for system settings and other useful apps like, mail client, Photo and Maps Viewer and maybe other fun things. It's fully written in C++ using Qt 4.5 Embedded. and it runs using Framebuffer, so no X11 Required. http://th30z.netsons.org/mokotouch/index.html

[http://www.youtube.com/watch?v=yr821OgnvYc Video]
<br style="clear: both">
=== neovento ===
{{Template:Works on noevento}}
[[neovento]] (ex FYP) is a [[Debian|Debian on Freerunner]] based [[Distributions|distribution]] which uses [http://lxde.org/ LXDE] and [[Zhone]] on top. It is a [http://freeyourphone.de FreeYourPhone.de] community project.

{{Main|neovento}}
<br style="clear: both">

=== OpenWrt ===
{{Template:Works on OpenWrt}}
[[OpenWrt]] is described as a Linux distribution for embedded devices.

Instead of trying to create a single, static firmware, [[OpenWrt]] provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developer, [[OpenWrt]] is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.

[[OpenWrt]] development trunk now supports s3c24xx, CPU used in [[Freerunner]].

Mainly due to the usage of uClibc instead of glibc as libc implementation, OpenWrt can boot from NAND with enlightenment window manager within 1 minute 7 seconds using u-boot (NOR) bootloader.

* [http://www.openwrt.org OpenWrt website]
* [http://dev.openwrt.org OpenWrt development site]

{{Main|OpenWrt}}

=== Qalee ===
{{Works on Qalee}}
[[Qalee]] is a phone environment developed in Qt4 above the fso stack. It works on the freerunner under any distribution that supports Qt4. It's not finished yet but you can test a preview version with the official Qalee distributon. This release includes no new features, but many fixes for things that didn’t work or were incomplete in 0.0.2. You can read full [http://think-free.homelinux.org/wordpress/ announcement], or take a look at some of changes:
* Qalee is now based on shr instead of debian.
* clock widget now shows a calendar when clicked.
* status panel widget shows gsm network name and power and internet connection status while on wifi or gprs.
* screen menu : you can now choose the background picture with a cover-flow effect, letting the backlight always on now works.
* network menu : all entries work, gsm one is a little buggy though.
* Wifi works despite the the bug in the kernel 2.6.29 opened for 4 month.
* application menu : to launch application just click on it :) when launched the button becomes green, to close it, press the close button which becomes red and click on the application you want to close
* power button supports suspend on short press, or menu on longer press.
* phone application is now litephone modified to use Qalee’s buttons.
* GorshPlayer is broken, if you have Qt4.5.2 librairies with phonon working on shr, tell me (?)//FIXME
* keyboard is still literky.
* Themable interface allows you to change some colours of the interface.
<br>WARNING :<br>
Qalee is in pre-alpha stage, a lot of thinks are not coded yet, other are broken, some may be changed. It's just a preview version of the current work!
http://www.qalee.org

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

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

{{Main|Qt Extended Improved}}

{{Template:Works on QtMoko}}
Another branch of development after discontinued Qt Extended is [http://activationrecord.net/radekp/qtmoko/ QT Moko]. Special feature are:
* QT Moko has better X support, which is much faster then X4,
* in QT Moko the AUX can bring menu for X application,
* QT Moko includes an X terminal with virtual keyboard and matchbox window manager
* in QT Moko with the X-Server support you can use X application like [http://www.tangogps.org/gps/articles/7-Installation.html#extended TangoGPS] as GPS application.

{{Main|QT Moko}}

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

{{Main|SHR}}

=== Slackware ===
{{Template:Works on Slackware}}
As of release 12.2, Slackware is now officially supported on the Neo Freerunner
[http://armedslack.org/]
--[[User:Djdas|djdas]] 15:54, 13 June 2009 (UTC)There aren't any confirmations of ArmedSlack running on Freerunner either on the website or the official ML, do you have any link pointing on that?
<br style="clear: both">
=== Abandoned ===

==== FDOM (FAT and Dirty Openmoko) ====
{{Template:Works on FDOM}}
[[FDOM]] was a distribution based on [[Om 2008]], updated with many ready-to-use applications and with fixes posted in the mailing lists.

{{Main|FDOM}}
<br style="clear: both">

==== Om series ====
* '''[[Om 2009]]''' was intended to be the new distro; it is not a simple follow-on from [[Om 2008]]. It is based on the [http://freesmartphone.org freesmartphone.org] milestone 5.5 framework. Development of Om 2009 was ended and developers moved on to work on other distros instead.

{{Main|Om2009}}

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

{{Main|Om 2008}}

* '''[[Om 2007.2]]''' was the first distribution created by Openmoko. The interface was totally finger-oriented, optimized for 285ppi, and very orange. It used the GTK+ stack, which is part of the [http://www.gnome.org/mobile/ GNOME Mobile] platform. This distribution is now considered obsolete and not being worked on by Openmoko Inc or by OpenedHand.

{{Main|Om 2007.2}}

=== Others / unreleased ===
* The [http://www.neopwn.com/software.php NeoPwn] network auditng system's core is a modified Linux 2.6.24 kernel, with cross-compiled module driver support for the numerous compatible addon devices running on a FULL Debian (ARMEL) operating system. The filesystem has been optimized for performance and size and includes the NeoPwn menu system and several GUI dialogs for hardware control and attack automation. ''Status: Unknown, the GPL requires source code to be distributed only to customers''.
* [http://runningbear.org/trac RunningBear] is an innovative, yet free and open-source Operating System for hackable devices driven by Bearstech. Lightweight, Portable, Secure, Friendly and Useful. ''Status: In development''.
* [http://pokylinux.org/ Poky] and Sato, by OpenedHand/Intel. An open source platform build tool derived from OE. It is a complete software development environment for the creation of Linux devices. It enables you to design, develop, build, debug, and test a complete, modern, software stack using Linux, the X Window System and GNOME Mobile based application frameworks for both ARM and x86 based platforms. ''Status: The "Nightly Build" Image works fine on Neo Freerunner, but phone functionality doesn't.''
* [http://pyneo.org/ PyNeo] pyneo is a stack for mobile devices excessivly using dbus, glib and evas. Pyneo is NO distribution but a middleware or framework like FSO which itself developed from a very early version of pyneo. Current pyneo images are entirely based on debian instead of oe. ''Status: still active and in development! ask around on #pyneo.org ''
* [http://www.quantum-step.com/ mySTEP] by Openmoko distributor Golden Delicious Computers is based on GNUstep and brings a Objective-C API to the Neo. Core GUI frameworks are "Foundation" & "AppKit". It has been shown on FOSDEM 2008, LinuxTag 2008 and SYSTEMS 2008 to run on the Neo 1973. If someone reengineers UIKit, (open) source code compatibility to iPhone apps appears achievable. ''Status: slow progress behind the scenes''
* [http://www.archmobile.org/ Archlinux] is a distribution that follows the KISS principle.

== Features by distribution/release target ==

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

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

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

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

=== User Interaction ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=8%|[[Om 2009]] !! width=8%|[[Om 2008]] !! width=8%|Om 2007.2 !! width=8%|[[SHR]] !! width=8%|[[Qt Extended Improved]] !! width=8%|[[Debian]] !! width=8%|[[Gentoo]] !! width=8%|[[Android]]
|-
| Finger friendly || {{Yes}} || Partially || Partially || {{Yes}} || {{Yes}} || {{Yes}} [[Illume|(1)]] || {{Yes}} || {{Yes}}
|-
| Accelerometer || {{Yes}} (1) || {{Yes}} [[Rotate|(1)]][[Gestures|(1)]] || {{No}} || {{Yes}} || {{No}} || {{Yes}} || ?? || {{Yes}}
|-
|}

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

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

Footnotes:

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

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

(*) unstable

==Quick download page==

[[Download]]

== See also ==

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

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

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

[[Category:Distributions| ]]

Distributions/eu

2010-01-30T16:45:46Z

Joseba:

{{Languages|Distributions}}

{|align=right
|__TOC__
|}
{| class="wikitable" style="float:left;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|<font color=white>Distributions</font>
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* <font color='#BBBBBB'>Openmoko (official)</font>
** [[Om 2009]]
** [[Om 2008]]
** [[Om 2007.2]]
* <font color='#BBBBBB'>Om Community</font>
** [[Android]]
** [[Debian]]
** [[Gentoo]]
** [[Hackable:1]]
** [[Mer]]
** [[Neovento]]
** [[OpenWrt]]
** [[Qt Extended Improved]]
** [[SHR]]
</div>
|-
|}
== Banaketei buruz ==
Openmoko banaketak hainbat mobiletan erabiltzeko diseinatu dira, baina helburu nagusia Openmoko Inc. proiektuaren [[GTA01:Neo 1973|Neo 1973]] eta [[Neo FreeRunner]] telefono mugikorretan funtzionatzea dute. GNU/Linux banaketak dira, alegia, Linux sistema eragilea eta erabilera zabaleko hainbat aplikazioz osatutako aplikazio multzoak dira. Zeure telefonoan banaketa horietako edozein instala zenezake, edo nahi izanez gero, banaketa bat baino gehiago eduki ditzakezu eta pizterakoan aukeratu zein banaketarekin abiarazi nahi duzun. Banaketaren bat deskargatzeko ikusi [[Download]], instalaziorako argibideak [[Flashing the Neo FreeRunner|FreeRunnerrean banaketen instalazioa]] orrian aurkituko dituzu.

Horrez gain, Openmoko banaketak [[Supported devices|beste]] mobil batzuetan ere instala daitezke, eta, era berean, beste banaketa batzuek ere instala daitezke Openmoko proiektuaren mobiletan.

=== Banaketa egokiaren aukera ===

2009ko abuztuaz geroztik egindako inkesta baten arabera [[SHR]] da gehien erabiltzen den banaketa, eta horri openmokoren banaketek jarraitzen diote ([[Om 2007]], [[Om 2008]] eta [[Om 2009]] hirurak bakar baten moduan hartuz gero beti ere), beste hainbat aukera ere badaude: [[Debian]], Debianen oinarritutako [[Hackable:1]], [[Qt Extended Improved]], [[Android]], Qtmoko eta abar.[http://doodle.com/sd2c8d8snr23eeqq] Om 2009 banaketaren garapena geratu egin da ordea, eta beraz bere erabiltzaileek beste banaketaren batera pasa beharko dute.

=== Kontuan izan ===

* Egonkorra hitzak FreeRunnerraren munduan ez du Debianen munduko esanahi bera.
* Banaketa gehienek abiatzaile, kernel, driver eta hardware berak erabiltzen dituzte. Ondorioz, behe mailako hutsegite berdinak agertzen dira banaketa gehienetan. Azken aplikazio zirraragarriek akats zaharrak konponduta edukiko dituzte, baina berriak bertan azalduko dira...
* Banaketa hauek aplikazioen biltegiak ere eduki ohi dituzte. bertatik instalatu aplikazio berriak, beste batetik instalatzea ideia '''TXARRA''' da. Ikusi [[installing alien package|beste banaketen aplikazioen instalazioa]].
* Banaketa hauen artean batetik besterako maila igoerak (upgradeak) ez dira ondo probatuta egoten, ondorioz, eguneraketak biltegiak aldatuz eginez gero, aplikazioeak apurtzea ekar dezake, edo okerragoa dena, abiarazi ezin den sistemarekin bukatu daiteke. Egin behar dena sistema FreeRunnerraren Flash memorian instalatzea da, horretarako [[dfu-util]] erabiliz, horrela, banaketa ezberdinen artean aukeratu ahal izango duzu. Abiaratze bikoitza ezar daiteke [[Booting from SD|MikroSD]] edo [[Booting from NFS|NFS]]) erabiliz.
* [[Marketing Mistakes|merkaturatze akatsak]] eta aurreinstalatutako banaketak

== Gainbegirada ==

=== Android ===
{{Template:Works on Android}}
[http://code.google.com/android/ Android] gailu mobilentzat garatutako software metaketa bat da, bere arduraduna [http://www.openhandsetalliance.com/ The Open Handset Alliance] da. Openmokok guztiz sostengatzen eta babesten du Android FreeRunnerrean erabilia izan dadin.

Android dagoenekoz Freerunnerra eguneroko mobil gisa erabiltzeko garapen mailara iritsia da, dena den, kontua eta arreta eskatzen duten gaiak daude oraindik. Informazio gehiago edukitzeo, Wikiko Androiden atal nagusia aztertzea gomendatzen dizut.

{{Main|Android} Bestalde, [http://wiki.openmoko.org/wiki/User:Seanmcneil3 Sean McNeil] erabiltzailearen web orria ere gomendagarria da informazio gehiago nahi baduzu.

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

{{Main|Debian}}

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

{{Main|Gentoo}}

=== Hackable:1 ===
{{Template:Works on Hackable:1}}
Hackable1 is a community distribution for hackable devices like the Neo Freerunner. It is based on Debian and 2007.2 userland which has been abandoned by Openmoko. It follows the GNOME mobile platform.
{{Main|Hackable:1}}
<br style="clear: both">
=== Mer ===
{{Template:Works on Mer}}
[[Mer]] is a distribution based on [[Maemo]].
<br style="clear: both">
=== Mokotouch ===
{{Template:Works on Mokotouch}}
[[MokoTouch]] wants to be a replacement for the OM Distribution. It will contain apps for system settings and other useful apps like, mail client, Photo and Maps Viewer and maybe other fun things. It's fully written in C++ using Qt 4.5 Embedded. and it runs using Framebuffer, so no X11 Required. http://th30z.netsons.org/mokotouch/index.html

[http://www.youtube.com/watch?v=yr821OgnvYc Video]
<br style="clear: both">
=== neovento ===
{{Template:Works on noevento}}
[[neovento]] (ex FYP) is a [[Debian|Debian on Freerunner]] based [[Distributions|distribution]] which uses [http://lxde.org/ LXDE] and [[Zhone]] on top. It is a [http://freeyourphone.de FreeYourPhone.de] community project.

{{Main|neovento}}
<br style="clear: both">

=== OpenWrt ===
{{Template:Works on OpenWrt}}
[[OpenWrt]] is described as a Linux distribution for embedded devices.

Instead of trying to create a single, static firmware, [[OpenWrt]] provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developer, [[OpenWrt]] is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.

[[OpenWrt]] development trunk now supports s3c24xx, CPU used in [[Freerunner]].

Mainly due to the usage of uClibc instead of glibc as libc implementation, OpenWrt can boot from NAND with enlightenment window manager within 1 minute 7 seconds using u-boot (NOR) bootloader.

* [http://www.openwrt.org OpenWrt website]
* [http://dev.openwrt.org OpenWrt development site]

{{Main|OpenWrt}}

=== Qalee ===
{{Works on Qalee}}
[[Qalee]] is a phone environment developed in Qt4 above the fso stack. It works on the freerunner under any distribution that supports Qt4. It's not finished yet but you can test a preview version with the official Qalee distributon. This release includes no new features, but many fixes for things that didn’t work or were incomplete in 0.0.2. You can read full [http://think-free.homelinux.org/wordpress/ announcement], or take a look at some of changes:
* Qalee is now based on shr instead of debian.
* clock widget now shows a calendar when clicked.
* status panel widget shows gsm network name and power and internet connection status while on wifi or gprs.
* screen menu : you can now choose the background picture with a cover-flow effect, letting the backlight always on now works.
* network menu : all entries work, gsm one is a little buggy though.
* Wifi works despite the the bug in the kernel 2.6.29 opened for 4 month.
* application menu : to launch application just click on it :) when launched the button becomes green, to close it, press the close button which becomes red and click on the application you want to close
* power button supports suspend on short press, or menu on longer press.
* phone application is now litephone modified to use Qalee’s buttons.
* GorshPlayer is broken, if you have Qt4.5.2 librairies with phonon working on shr, tell me (?)//FIXME
* keyboard is still literky.
* Themable interface allows you to change some colours of the interface.
<br>WARNING :<br>
Qalee is in pre-alpha stage, a lot of thinks are not coded yet, other are broken, some may be changed. It's just a preview version of the current work!
http://www.qalee.org

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

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

{{Main|Qt Extended Improved}}

{{Template:Works on QtMoko}}
Another branch of development after discontinued Qt Extended is [http://activationrecord.net/radekp/qtmoko/ QT Moko]. Special feature are:
* QT Moko has better X support, which is much faster then X4,
* in QT Moko the AUX can bring menu for X application,
* QT Moko includes an X terminal with virtual keyboard and matchbox window manager
* in QT Moko with the X-Server support you can use X application like [http://www.tangogps.org/gps/articles/7-Installation.html#extended TangoGPS] as GPS application.

{{Main|QT Moko}}

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

{{Main|SHR}}

=== Slackware ===
{{Template:Works on Slackware}}
As of release 12.2, Slackware is now officially supported on the Neo Freerunner
[http://armedslack.org/]
--[[User:Djdas|djdas]] 15:54, 13 June 2009 (UTC)There aren't any confirmations of ArmedSlack running on Freerunner either on the website or the official ML, do you have any link pointing on that?
<br style="clear: both">
=== Abandoned ===

==== FDOM (FAT and Dirty Openmoko) ====
{{Template:Works on FDOM}}
[[FDOM]] was a distribution based on [[Om 2008]], updated with many ready-to-use applications and with fixes posted in the mailing lists.

{{Main|FDOM}}
<br style="clear: both">

==== Om series ====
* '''[[Om 2009]]''' was intended to be the new distro; it is not a simple follow-on from [[Om 2008]]. It is based on the [http://freesmartphone.org freesmartphone.org] milestone 5.5 framework. Development of Om 2009 was ended and developers moved on to work on other distros instead.

{{Main|Om2009}}

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

{{Main|Om 2008}}

* '''[[Om 2007.2]]''' was the first distribution created by Openmoko. The interface was totally finger-oriented, optimized for 285ppi, and very orange. It used the GTK+ stack, which is part of the [http://www.gnome.org/mobile/ GNOME Mobile] platform. This distribution is now considered obsolete and not being worked on by Openmoko Inc or by OpenedHand.

{{Main|Om 2007.2}}

=== Others / unreleased ===
* The [http://www.neopwn.com/software.php NeoPwn] network auditng system's core is a modified Linux 2.6.24 kernel, with cross-compiled module driver support for the numerous compatible addon devices running on a FULL Debian (ARMEL) operating system. The filesystem has been optimized for performance and size and includes the NeoPwn menu system and several GUI dialogs for hardware control and attack automation. ''Status: Unknown, the GPL requires source code to be distributed only to customers''.
* [http://runningbear.org/trac RunningBear] is an innovative, yet free and open-source Operating System for hackable devices driven by Bearstech. Lightweight, Portable, Secure, Friendly and Useful. ''Status: In development''.
* [http://pokylinux.org/ Poky] and Sato, by OpenedHand/Intel. An open source platform build tool derived from OE. It is a complete software development environment for the creation of Linux devices. It enables you to design, develop, build, debug, and test a complete, modern, software stack using Linux, the X Window System and GNOME Mobile based application frameworks for both ARM and x86 based platforms. ''Status: The "Nightly Build" Image works fine on Neo Freerunner, but phone functionality doesn't.''
* [http://pyneo.org/ PyNeo] pyneo is a stack for mobile devices excessivly using dbus, glib and evas. Pyneo is NO distribution but a middleware or framework like FSO which itself developed from a very early version of pyneo. Current pyneo images are entirely based on debian instead of oe. ''Status: still active and in development! ask around on #pyneo.org ''
* [http://www.quantum-step.com/ mySTEP] by Openmoko distributor Golden Delicious Computers is based on GNUstep and brings a Objective-C API to the Neo. Core GUI frameworks are "Foundation" & "AppKit". It has been shown on FOSDEM 2008, LinuxTag 2008 and SYSTEMS 2008 to run on the Neo 1973. If someone reengineers UIKit, (open) source code compatibility to iPhone apps appears achievable. ''Status: slow progress behind the scenes''
* [http://www.archmobile.org/ Archlinux] is a distribution that follows the KISS principle.

== Features by distribution/release target ==

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

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

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

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

=== User Interaction ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=8%|[[Om 2009]] !! width=8%|[[Om 2008]] !! width=8%|Om 2007.2 !! width=8%|[[SHR]] !! width=8%|[[Qt Extended Improved]] !! width=8%|[[Debian]] !! width=8%|[[Gentoo]] !! width=8%|[[Android]]
|-
| Finger friendly || {{Yes}} || Partially || Partially || {{Yes}} || {{Yes}} || {{Yes}} [[Illume|(1)]] || {{Yes}} || {{Yes}}
|-
| Accelerometer || {{Yes}} (1) || {{Yes}} [[Rotate|(1)]][[Gestures|(1)]] || {{No}} || {{Yes}} || {{No}} || {{Yes}} || ?? || {{Yes}}
|-
|}

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

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

Footnotes:

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

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

(*) unstable

==Quick download page==

[[Download]]

== See also ==

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

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

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

[[Category:Distributions| ]]

Distributions/eu

2010-01-30T16:03:20Z

Joseba:

{{Languages|Distributions}}

{|align=right
|__TOC__
|}
{| class="wikitable" style="float:left;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|<font color=white>Distributions</font>
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* <font color='#BBBBBB'>Openmoko (official)</font>
** [[Om 2009]]
** [[Om 2008]]
** [[Om 2007.2]]
* <font color='#BBBBBB'>Om Community</font>
** [[Android]]
** [[Debian]]
** [[Gentoo]]
** [[Hackable:1]]
** [[Mer]]
** [[Neovento]]
** [[OpenWrt]]
** [[Qt Extended Improved]]
** [[SHR]]
</div>
|-
|}
== Banaketei buruz ==
Openmoko banaketak hainbat mobiletan erabiltzeko diseinatu dira, baina helburu nagusia Openmoko Inc. proiektuaren [[GTA01:Neo 1973|Neo 1973]] eta [[Neo FreeRunner]] telefono mugikorretan funtzionatzea dute. GNU/Linux banaketak dira, alegia, Linux sistema eragilea eta erabilera zabaleko hainbat aplikazioz osatutako aplikazio multzoak dira. Zeure telefonoan banaketa horietako edozein instala zenezake, edo nahi izanez gero, banaketa bat baino gehiago eduki ditzakezu eta pizterakoan aukeratu zein banaketarekin abiarazi nahi duzun. Banaketaren bat deskargatzeko ikusi [[Download]], instalaziorako argibideak [[Flashing the Neo FreeRunner|FreeRunnerrean banaketen instalazioa]] orrian aurkituko dituzu.

Horrez gain, Openmoko banaketak [[Supported devices|beste]] mobil batzuetan ere instala daitezke, eta, era berean, beste banaketa batzuek ere instala daitezke Openmoko proiektuaren mobiletan.

=== Banaketa egokiaren aukera ===

2009ko abuztuaz geroztik egindako inkesta baten arabera [[SHR]] da gehien erabiltzen den banaketa, eta horri openmokoren banaketek jarraitzen diote ([[Om 2007]], [[Om 2008]] eta [[Om 2009]] hirurak bakar baten moduan hartuz gero beti ere), beste hainbat aukera ere badaude: [[Debian]], Debianen oinarritutako [[Hackable:1]], [[Qt Extended Improved]], [[Android]], Qtmoko eta abar.[http://doodle.com/sd2c8d8snr23eeqq] Om 2009 banaketaren garapena geratu egin da ordea, eta beraz bere erabiltzaileek beste banaketaren batera pasa beharko dute.

=== Kontuan izan ===

* Egonkorra hitzak FreeRunnerraren munduan ez du Debianen munduko esanahi bera.
* Banaketa gehienek abiatzaile, kernel, driver eta hardware berak erabiltzen dituzte. Ondorioz, behe mailako hutsegite berdinak agertzen dira banaketa gehienetan. Azken aplikazio zirraragarriek akats zaharrak konponduta edukiko dituzte, baina berriak bertan azalduko dira...
* Banaketa hauek aplikazioen biltegiak ere eduki ohi dituzte. bertatik instalatu aplikazio berriak, beste batetik instalatzea ideia '''TXARRA''' da. Ikusi [[installing alien package|beste banaketen aplikazioen instalazioa]].
* Banaketa hauen artean batetik besterako maila igoerak (upgradeak) ez dira ondo probatuta egoten, ondorioz, eguneraketak biltegiak aldatuz eginez gero, aplikazioeak apurtzea ekar dezake, edo okerragoa dena, abiarazi ezin den sistemarekin bukatu daiteke. Egin behar dena sistema FreeRunnerraren Flash memorian instalatzea da, horretarako [[dfu-util]] erabiliz, horrela, banaketa ezberdinen artean aukeratu ahal izango duzu. Abiaratze bikoitza ezar daiteke [[Booting from SD|MikroSD]] edo [[Booting from NFS|NFS]]) erabiliz.
* [[Marketing Mistakes|merkaturatze akatsak]] eta aurreinstalatutako banaketak

== Overview ==

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

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

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

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

{{Main|Debian}}

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

{{Main|Gentoo}}

=== Hackable:1 ===
{{Template:Works on Hackable:1}}
Hackable1 is a community distribution for hackable devices like the Neo Freerunner. It is based on Debian and 2007.2 userland which has been abandoned by Openmoko. It follows the GNOME mobile platform.
{{Main|Hackable:1}}
<br style="clear: both">
=== Mer ===
{{Template:Works on Mer}}
[[Mer]] is a distribution based on [[Maemo]].
<br style="clear: both">
=== Mokotouch ===
{{Template:Works on Mokotouch}}
[[MokoTouch]] wants to be a replacement for the OM Distribution. It will contain apps for system settings and other useful apps like, mail client, Photo and Maps Viewer and maybe other fun things. It's fully written in C++ using Qt 4.5 Embedded. and it runs using Framebuffer, so no X11 Required. http://th30z.netsons.org/mokotouch/index.html

[http://www.youtube.com/watch?v=yr821OgnvYc Video]
<br style="clear: both">
=== neovento ===
{{Template:Works on noevento}}
[[neovento]] (ex FYP) is a [[Debian|Debian on Freerunner]] based [[Distributions|distribution]] which uses [http://lxde.org/ LXDE] and [[Zhone]] on top. It is a [http://freeyourphone.de FreeYourPhone.de] community project.

{{Main|neovento}}
<br style="clear: both">

=== OpenWrt ===
{{Template:Works on OpenWrt}}
[[OpenWrt]] is described as a Linux distribution for embedded devices.

Instead of trying to create a single, static firmware, [[OpenWrt]] provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developer, [[OpenWrt]] is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.

[[OpenWrt]] development trunk now supports s3c24xx, CPU used in [[Freerunner]].

Mainly due to the usage of uClibc instead of glibc as libc implementation, OpenWrt can boot from NAND with enlightenment window manager within 1 minute 7 seconds using u-boot (NOR) bootloader.

* [http://www.openwrt.org OpenWrt website]
* [http://dev.openwrt.org OpenWrt development site]

{{Main|OpenWrt}}

=== Qalee ===
{{Works on Qalee}}
[[Qalee]] is a phone environment developed in Qt4 above the fso stack. It works on the freerunner under any distribution that supports Qt4. It's not finished yet but you can test a preview version with the official Qalee distributon. This release includes no new features, but many fixes for things that didn’t work or were incomplete in 0.0.2. You can read full [http://think-free.homelinux.org/wordpress/ announcement], or take a look at some of changes:
* Qalee is now based on shr instead of debian.
* clock widget now shows a calendar when clicked.
* status panel widget shows gsm network name and power and internet connection status while on wifi or gprs.
* screen menu : you can now choose the background picture with a cover-flow effect, letting the backlight always on now works.
* network menu : all entries work, gsm one is a little buggy though.
* Wifi works despite the the bug in the kernel 2.6.29 opened for 4 month.
* application menu : to launch application just click on it :) when launched the button becomes green, to close it, press the close button which becomes red and click on the application you want to close
* power button supports suspend on short press, or menu on longer press.
* phone application is now litephone modified to use Qalee’s buttons.
* GorshPlayer is broken, if you have Qt4.5.2 librairies with phonon working on shr, tell me (?)//FIXME
* keyboard is still literky.
* Themable interface allows you to change some colours of the interface.
<br>WARNING :<br>
Qalee is in pre-alpha stage, a lot of thinks are not coded yet, other are broken, some may be changed. It's just a preview version of the current work!
http://www.qalee.org

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

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

{{Main|Qt Extended Improved}}

{{Template:Works on QtMoko}}
Another branch of development after discontinued Qt Extended is [http://activationrecord.net/radekp/qtmoko/ QT Moko]. Special feature are:
* QT Moko has better X support, which is much faster then X4,
* in QT Moko the AUX can bring menu for X application,
* QT Moko includes an X terminal with virtual keyboard and matchbox window manager
* in QT Moko with the X-Server support you can use X application like [http://www.tangogps.org/gps/articles/7-Installation.html#extended TangoGPS] as GPS application.

{{Main|QT Moko}}

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

{{Main|SHR}}

=== Slackware ===
{{Template:Works on Slackware}}
As of release 12.2, Slackware is now officially supported on the Neo Freerunner
[http://armedslack.org/]
--[[User:Djdas|djdas]] 15:54, 13 June 2009 (UTC)There aren't any confirmations of ArmedSlack running on Freerunner either on the website or the official ML, do you have any link pointing on that?
<br style="clear: both">
=== Abandoned ===

==== FDOM (FAT and Dirty Openmoko) ====
{{Template:Works on FDOM}}
[[FDOM]] was a distribution based on [[Om 2008]], updated with many ready-to-use applications and with fixes posted in the mailing lists.

{{Main|FDOM}}
<br style="clear: both">

==== Om series ====
* '''[[Om 2009]]''' was intended to be the new distro; it is not a simple follow-on from [[Om 2008]]. It is based on the [http://freesmartphone.org freesmartphone.org] milestone 5.5 framework. Development of Om 2009 was ended and developers moved on to work on other distros instead.

{{Main|Om2009}}

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

{{Main|Om 2008}}

* '''[[Om 2007.2]]''' was the first distribution created by Openmoko. The interface was totally finger-oriented, optimized for 285ppi, and very orange. It used the GTK+ stack, which is part of the [http://www.gnome.org/mobile/ GNOME Mobile] platform. This distribution is now considered obsolete and not being worked on by Openmoko Inc or by OpenedHand.

{{Main|Om 2007.2}}

=== Others / unreleased ===
* The [http://www.neopwn.com/software.php NeoPwn] network auditng system's core is a modified Linux 2.6.24 kernel, with cross-compiled module driver support for the numerous compatible addon devices running on a FULL Debian (ARMEL) operating system. The filesystem has been optimized for performance and size and includes the NeoPwn menu system and several GUI dialogs for hardware control and attack automation. ''Status: Unknown, the GPL requires source code to be distributed only to customers''.
* [http://runningbear.org/trac RunningBear] is an innovative, yet free and open-source Operating System for hackable devices driven by Bearstech. Lightweight, Portable, Secure, Friendly and Useful. ''Status: In development''.
* [http://pokylinux.org/ Poky] and Sato, by OpenedHand/Intel. An open source platform build tool derived from OE. It is a complete software development environment for the creation of Linux devices. It enables you to design, develop, build, debug, and test a complete, modern, software stack using Linux, the X Window System and GNOME Mobile based application frameworks for both ARM and x86 based platforms. ''Status: The "Nightly Build" Image works fine on Neo Freerunner, but phone functionality doesn't.''
* [http://pyneo.org/ PyNeo] pyneo is a stack for mobile devices excessivly using dbus, glib and evas. Pyneo is NO distribution but a middleware or framework like FSO which itself developed from a very early version of pyneo. Current pyneo images are entirely based on debian instead of oe. ''Status: still active and in development! ask around on #pyneo.org ''
* [http://www.quantum-step.com/ mySTEP] by Openmoko distributor Golden Delicious Computers is based on GNUstep and brings a Objective-C API to the Neo. Core GUI frameworks are "Foundation" & "AppKit". It has been shown on FOSDEM 2008, LinuxTag 2008 and SYSTEMS 2008 to run on the Neo 1973. If someone reengineers UIKit, (open) source code compatibility to iPhone apps appears achievable. ''Status: slow progress behind the scenes''
* [http://www.archmobile.org/ Archlinux] is a distribution that follows the KISS principle.

== Features by distribution/release target ==

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

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

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

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

=== User Interaction ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=8%|[[Om 2009]] !! width=8%|[[Om 2008]] !! width=8%|Om 2007.2 !! width=8%|[[SHR]] !! width=8%|[[Qt Extended Improved]] !! width=8%|[[Debian]] !! width=8%|[[Gentoo]] !! width=8%|[[Android]]
|-
| Finger friendly || {{Yes}} || Partially || Partially || {{Yes}} || {{Yes}} || {{Yes}} [[Illume|(1)]] || {{Yes}} || {{Yes}}
|-
| Accelerometer || {{Yes}} (1) || {{Yes}} [[Rotate|(1)]][[Gestures|(1)]] || {{No}} || {{Yes}} || {{No}} || {{Yes}} || ?? || {{Yes}}
|-
|}

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

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

Footnotes:

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

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

(*) unstable

==Quick download page==

[[Download]]

== See also ==

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

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

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

[[Category:Distributions| ]]

Distributions/eu

2010-01-30T15:29:01Z

Joseba:

{{Languages|Distributions}}

{|align=right
|__TOC__
|}
{| class="wikitable" style="float:left;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|<font color=white>Distributions</font>
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* <font color='#BBBBBB'>Openmoko (official)</font>
** [[Om 2009]]
** [[Om 2008]]
** [[Om 2007.2]]
* <font color='#BBBBBB'>Om Community</font>
** [[Android]]
** [[Debian]]
** [[Gentoo]]
** [[Hackable:1]]
** [[Mer]]
** [[Neovento]]
** [[OpenWrt]]
** [[Qt Extended Improved]]
** [[SHR]]
</div>
|-
|}
== Banaketei buruz ==
Openmoko banaketak hainbat mobiletan erabiltzeko diseinatu dira, baina helburu nagusia Openmoko Inc. proiektuaren [[GTA01:Neo 1973|Neo 1973]] eta [[Neo FreeRunner]] telefono mugikorretan funtzionatzea dute. GNU/Linux banaketak dira, alegia, Linux sistema eragilea eta erabilera zabaleko hainbat aplikazioz osatutako aplikazio multzoak dira. Zeure telefonoan banaketa horietako edozein instala zenezake, edo nahi izanez gero, banaketa bat baino gehiago eduki ditzakezu eta pizterakoan aukeratu zein banaketarekin abiarazi nahi duzun. Banaketaren bat deskargatzeko ikusi [[Download]], instalaziorako argibideak [[Flashing the Neo FreeRunner|FreeRunnerrean banaketen instalazioa]] orrian aurkituko dituzu.

Horrez gain, Openmoko banaketak [[Supported devices|beste]] mobil batzuetan ere instala daitezke, eta, era berean, beste banaketa batzuek ere instala daitezke Openmoko proiektuaren mobiletan.

=== Banaketa egokiaren aukera ===

2009ko abuztuaz geroztik egindako inkesta baten arabera [[SHR]] da gehien erabiltzen den banaketa, eta horri openmokoren banaketek jarraitzen diote ([[Om 2007]], [[Om 2008]] eta [[Om 2009]] hirurak bakar baten moduan hartuz gero beti ere), beste hainbat aukera ere badaude: [[Debian]], Debianen oinarritutako [[Hackable:1]], [[Qt Extended Improved]], [[Android]], Qtmoko eta abar.[http://doodle.com/sd2c8d8snr23eeqq] Om 2009 banaketaren garapena geratu egin da ordea, eta beraz bere erabiltzaileek beste banaketaren batera pasa beharko dute.

=== Kontuan izan ===

* Egonkorra hitzak FreeRunnerraren munduan ez du Debianen munduko esanahi bera.
* Banaketa gehienek abiatzaile, kernel, driver eta hardware berak erabiltzen dituzte. Ondorioz, behe mailako hutsegite berdinak agertzen dira banaketa gehienetan. Azken aplikazio zirraragarriek akats zaharrak konponduta edukiko dituzte, baina berriak bertan azalduko dira...
* Banaketa hauek aplikazioen biltegiak ere eduki ohi dituzte. bertatik instalatu aplikazio berriak, beste batetik instalatzea ideia '''TXARRA''' da. Ikusi [[installing alien package|beste banaketen aplikazioen instalazioa]].
* Upgrade path between these distributions are mostly not tested, thus updating by changing the feeds will most likely end in broken packages or even an unbootable system. It is advisable to reflash the whole filesystem with [[dfu-util]] to switch between the different distributions, with the reminder that a dual-boot setup (e.g. via [[Booting from SD|MicroSD]] or [[Booting from NFS|NFS]]) can be used.
* [[Marketing Mistakes]] and pre-installed distributions.

== Overview ==

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

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

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

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

{{Main|Debian}}

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

{{Main|Gentoo}}

=== Hackable:1 ===
{{Template:Works on Hackable:1}}
Hackable1 is a community distribution for hackable devices like the Neo Freerunner. It is based on Debian and 2007.2 userland which has been abandoned by Openmoko. It follows the GNOME mobile platform.
{{Main|Hackable:1}}
<br style="clear: both">
=== Mer ===
{{Template:Works on Mer}}
[[Mer]] is a distribution based on [[Maemo]].
<br style="clear: both">
=== Mokotouch ===
{{Template:Works on Mokotouch}}
[[MokoTouch]] wants to be a replacement for the OM Distribution. It will contain apps for system settings and other useful apps like, mail client, Photo and Maps Viewer and maybe other fun things. It's fully written in C++ using Qt 4.5 Embedded. and it runs using Framebuffer, so no X11 Required. http://th30z.netsons.org/mokotouch/index.html

[http://www.youtube.com/watch?v=yr821OgnvYc Video]
<br style="clear: both">
=== neovento ===
{{Template:Works on noevento}}
[[neovento]] (ex FYP) is a [[Debian|Debian on Freerunner]] based [[Distributions|distribution]] which uses [http://lxde.org/ LXDE] and [[Zhone]] on top. It is a [http://freeyourphone.de FreeYourPhone.de] community project.

{{Main|neovento}}
<br style="clear: both">

=== OpenWrt ===
{{Template:Works on OpenWrt}}
[[OpenWrt]] is described as a Linux distribution for embedded devices.

Instead of trying to create a single, static firmware, [[OpenWrt]] provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developer, [[OpenWrt]] is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.

[[OpenWrt]] development trunk now supports s3c24xx, CPU used in [[Freerunner]].

Mainly due to the usage of uClibc instead of glibc as libc implementation, OpenWrt can boot from NAND with enlightenment window manager within 1 minute 7 seconds using u-boot (NOR) bootloader.

* [http://www.openwrt.org OpenWrt website]
* [http://dev.openwrt.org OpenWrt development site]

{{Main|OpenWrt}}

=== Qalee ===
{{Works on Qalee}}
[[Qalee]] is a phone environment developed in Qt4 above the fso stack. It works on the freerunner under any distribution that supports Qt4. It's not finished yet but you can test a preview version with the official Qalee distributon. This release includes no new features, but many fixes for things that didn’t work or were incomplete in 0.0.2. You can read full [http://think-free.homelinux.org/wordpress/ announcement], or take a look at some of changes:
* Qalee is now based on shr instead of debian.
* clock widget now shows a calendar when clicked.
* status panel widget shows gsm network name and power and internet connection status while on wifi or gprs.
* screen menu : you can now choose the background picture with a cover-flow effect, letting the backlight always on now works.
* network menu : all entries work, gsm one is a little buggy though.
* Wifi works despite the the bug in the kernel 2.6.29 opened for 4 month.
* application menu : to launch application just click on it :) when launched the button becomes green, to close it, press the close button which becomes red and click on the application you want to close
* power button supports suspend on short press, or menu on longer press.
* phone application is now litephone modified to use Qalee’s buttons.
* GorshPlayer is broken, if you have Qt4.5.2 librairies with phonon working on shr, tell me (?)//FIXME
* keyboard is still literky.
* Themable interface allows you to change some colours of the interface.
<br>WARNING :<br>
Qalee is in pre-alpha stage, a lot of thinks are not coded yet, other are broken, some may be changed. It's just a preview version of the current work!
http://www.qalee.org

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

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

{{Main|Qt Extended Improved}}

{{Template:Works on QtMoko}}
Another branch of development after discontinued Qt Extended is [http://activationrecord.net/radekp/qtmoko/ QT Moko]. Special feature are:
* QT Moko has better X support, which is much faster then X4,
* in QT Moko the AUX can bring menu for X application,
* QT Moko includes an X terminal with virtual keyboard and matchbox window manager
* in QT Moko with the X-Server support you can use X application like [http://www.tangogps.org/gps/articles/7-Installation.html#extended TangoGPS] as GPS application.

{{Main|QT Moko}}

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

{{Main|SHR}}

=== Slackware ===
{{Template:Works on Slackware}}
As of release 12.2, Slackware is now officially supported on the Neo Freerunner
[http://armedslack.org/]
--[[User:Djdas|djdas]] 15:54, 13 June 2009 (UTC)There aren't any confirmations of ArmedSlack running on Freerunner either on the website or the official ML, do you have any link pointing on that?
<br style="clear: both">
=== Abandoned ===

==== FDOM (FAT and Dirty Openmoko) ====
{{Template:Works on FDOM}}
[[FDOM]] was a distribution based on [[Om 2008]], updated with many ready-to-use applications and with fixes posted in the mailing lists.

{{Main|FDOM}}
<br style="clear: both">

==== Om series ====
* '''[[Om 2009]]''' was intended to be the new distro; it is not a simple follow-on from [[Om 2008]]. It is based on the [http://freesmartphone.org freesmartphone.org] milestone 5.5 framework. Development of Om 2009 was ended and developers moved on to work on other distros instead.

{{Main|Om2009}}

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

{{Main|Om 2008}}

* '''[[Om 2007.2]]''' was the first distribution created by Openmoko. The interface was totally finger-oriented, optimized for 285ppi, and very orange. It used the GTK+ stack, which is part of the [http://www.gnome.org/mobile/ GNOME Mobile] platform. This distribution is now considered obsolete and not being worked on by Openmoko Inc or by OpenedHand.

{{Main|Om 2007.2}}

=== Others / unreleased ===
* The [http://www.neopwn.com/software.php NeoPwn] network auditng system's core is a modified Linux 2.6.24 kernel, with cross-compiled module driver support for the numerous compatible addon devices running on a FULL Debian (ARMEL) operating system. The filesystem has been optimized for performance and size and includes the NeoPwn menu system and several GUI dialogs for hardware control and attack automation. ''Status: Unknown, the GPL requires source code to be distributed only to customers''.
* [http://runningbear.org/trac RunningBear] is an innovative, yet free and open-source Operating System for hackable devices driven by Bearstech. Lightweight, Portable, Secure, Friendly and Useful. ''Status: In development''.
* [http://pokylinux.org/ Poky] and Sato, by OpenedHand/Intel. An open source platform build tool derived from OE. It is a complete software development environment for the creation of Linux devices. It enables you to design, develop, build, debug, and test a complete, modern, software stack using Linux, the X Window System and GNOME Mobile based application frameworks for both ARM and x86 based platforms. ''Status: The "Nightly Build" Image works fine on Neo Freerunner, but phone functionality doesn't.''
* [http://pyneo.org/ PyNeo] pyneo is a stack for mobile devices excessivly using dbus, glib and evas. Pyneo is NO distribution but a middleware or framework like FSO which itself developed from a very early version of pyneo. Current pyneo images are entirely based on debian instead of oe. ''Status: still active and in development! ask around on #pyneo.org ''
* [http://www.quantum-step.com/ mySTEP] by Openmoko distributor Golden Delicious Computers is based on GNUstep and brings a Objective-C API to the Neo. Core GUI frameworks are "Foundation" & "AppKit". It has been shown on FOSDEM 2008, LinuxTag 2008 and SYSTEMS 2008 to run on the Neo 1973. If someone reengineers UIKit, (open) source code compatibility to iPhone apps appears achievable. ''Status: slow progress behind the scenes''
* [http://www.archmobile.org/ Archlinux] is a distribution that follows the KISS principle.

== Features by distribution/release target ==

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

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

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

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

=== User Interaction ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=8%|[[Om 2009]] !! width=8%|[[Om 2008]] !! width=8%|Om 2007.2 !! width=8%|[[SHR]] !! width=8%|[[Qt Extended Improved]] !! width=8%|[[Debian]] !! width=8%|[[Gentoo]] !! width=8%|[[Android]]
|-
| Finger friendly || {{Yes}} || Partially || Partially || {{Yes}} || {{Yes}} || {{Yes}} [[Illume|(1)]] || {{Yes}} || {{Yes}}
|-
| Accelerometer || {{Yes}} (1) || {{Yes}} [[Rotate|(1)]][[Gestures|(1)]] || {{No}} || {{Yes}} || {{No}} || {{Yes}} || ?? || {{Yes}}
|-
|}

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

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

Footnotes:

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

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

(*) unstable

==Quick download page==

[[Download]]

== See also ==

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

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

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

[[Category:Distributions| ]]

Distributions/eu

2010-01-30T14:46:58Z

Joseba: New page: {{Languages|Distributions}} {|align=right |__TOC__ |} {| class="wikitable" style="float:left;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bo...

{{Languages|Distributions}}

{|align=right
|__TOC__
|}
{| class="wikitable" style="float:left;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|<font color=white>Distributions</font>
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* <font color='#BBBBBB'>Openmoko (official)</font>
** [[Om 2009]]
** [[Om 2008]]
** [[Om 2007.2]]
* <font color='#BBBBBB'>Om Community</font>
** [[Android]]
** [[Debian]]
** [[Gentoo]]
** [[Hackable:1]]
** [[Mer]]
** [[Neovento]]
** [[OpenWrt]]
** [[Qt Extended Improved]]
** [[SHR]]
</div>
|-
|}
== Banaketei buruz ==
Openmoko banaketak hainbat mobiletan erabiltzeko diseinatu dira, baina helburu nagusia Openmoko Inc. proiektuaren [[GTA01:Neo 1973|Neo 1973]] eta [[Neo FreeRunner]] telefono mugikorretan funtzionatzea dute. GNU/Linux banaketak dira, alegia, Linux sistema eragilea eta erabilera zabaleko hainbat aplikazioz osatutako aplikazio multzoak dira. Zeure telefonoan banaketa horietako edozein instala zenezake, edo nahi izanez gero, banaketa bat baino gehiago eduki ditzakezu eta pizterakoan aukeratu zein banaketarekin abiarazi nahi duzun. Banaketaren bat deskargatzeko ikusi [[Download]], instalaziorako argibideak [[Flashing the Neo FreeRunner|FreeRunnerrean banaketen instalazioa]] orrian aurkituko dituzu.

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

=== Choosing a distribution ===

According to a survey from August 2009 [[SHR]] is by far the most used distribution (60%), followed by Om (15%, [[Om 2007]], [[Om 2008]] and [[Om 2009]] counted as one distribution), [[Debian]] (6%), the Debian-based [[Hackable:1]] (6%), [[Qt Extended Improved]] (5%) and [[Android]] (4%).[http://doodle.com/sd2c8d8snr23eeqq] As the development of Om 2009 basically stopped after this poll even more people might switch to [[SHR]].

=== Please note ===

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

== Overview ==

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

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

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

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

{{Main|Debian}}

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

{{Main|Gentoo}}

=== Hackable:1 ===
{{Template:Works on Hackable:1}}
Hackable1 is a community distribution for hackable devices like the Neo Freerunner. It is based on Debian and 2007.2 userland which has been abandoned by Openmoko. It follows the GNOME mobile platform.
{{Main|Hackable:1}}
<br style="clear: both">
=== Mer ===
{{Template:Works on Mer}}
[[Mer]] is a distribution based on [[Maemo]].
<br style="clear: both">
=== Mokotouch ===
{{Template:Works on Mokotouch}}
[[MokoTouch]] wants to be a replacement for the OM Distribution. It will contain apps for system settings and other useful apps like, mail client, Photo and Maps Viewer and maybe other fun things. It's fully written in C++ using Qt 4.5 Embedded. and it runs using Framebuffer, so no X11 Required. http://th30z.netsons.org/mokotouch/index.html

[http://www.youtube.com/watch?v=yr821OgnvYc Video]
<br style="clear: both">
=== neovento ===
{{Template:Works on noevento}}
[[neovento]] (ex FYP) is a [[Debian|Debian on Freerunner]] based [[Distributions|distribution]] which uses [http://lxde.org/ LXDE] and [[Zhone]] on top. It is a [http://freeyourphone.de FreeYourPhone.de] community project.

{{Main|neovento}}
<br style="clear: both">

=== OpenWrt ===
{{Template:Works on OpenWrt}}
[[OpenWrt]] is described as a Linux distribution for embedded devices.

Instead of trying to create a single, static firmware, [[OpenWrt]] provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developer, [[OpenWrt]] is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.

[[OpenWrt]] development trunk now supports s3c24xx, CPU used in [[Freerunner]].

Mainly due to the usage of uClibc instead of glibc as libc implementation, OpenWrt can boot from NAND with enlightenment window manager within 1 minute 7 seconds using u-boot (NOR) bootloader.

* [http://www.openwrt.org OpenWrt website]
* [http://dev.openwrt.org OpenWrt development site]

{{Main|OpenWrt}}

=== Qalee ===
{{Works on Qalee}}
[[Qalee]] is a phone environment developed in Qt4 above the fso stack. It works on the freerunner under any distribution that supports Qt4. It's not finished yet but you can test a preview version with the official Qalee distributon. This release includes no new features, but many fixes for things that didn’t work or were incomplete in 0.0.2. You can read full [http://think-free.homelinux.org/wordpress/ announcement], or take a look at some of changes:
* Qalee is now based on shr instead of debian.
* clock widget now shows a calendar when clicked.
* status panel widget shows gsm network name and power and internet connection status while on wifi or gprs.
* screen menu : you can now choose the background picture with a cover-flow effect, letting the backlight always on now works.
* network menu : all entries work, gsm one is a little buggy though.
* Wifi works despite the the bug in the kernel 2.6.29 opened for 4 month.
* application menu : to launch application just click on it :) when launched the button becomes green, to close it, press the close button which becomes red and click on the application you want to close
* power button supports suspend on short press, or menu on longer press.
* phone application is now litephone modified to use Qalee’s buttons.
* GorshPlayer is broken, if you have Qt4.5.2 librairies with phonon working on shr, tell me (?)//FIXME
* keyboard is still literky.
* Themable interface allows you to change some colours of the interface.
<br>WARNING :<br>
Qalee is in pre-alpha stage, a lot of thinks are not coded yet, other are broken, some may be changed. It's just a preview version of the current work!
http://www.qalee.org

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

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

{{Main|Qt Extended Improved}}

{{Template:Works on QtMoko}}
Another branch of development after discontinued Qt Extended is [http://activationrecord.net/radekp/qtmoko/ QT Moko]. Special feature are:
* QT Moko has better X support, which is much faster then X4,
* in QT Moko the AUX can bring menu for X application,
* QT Moko includes an X terminal with virtual keyboard and matchbox window manager
* in QT Moko with the X-Server support you can use X application like [http://www.tangogps.org/gps/articles/7-Installation.html#extended TangoGPS] as GPS application.

{{Main|QT Moko}}

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

{{Main|SHR}}

=== Slackware ===
{{Template:Works on Slackware}}
As of release 12.2, Slackware is now officially supported on the Neo Freerunner
[http://armedslack.org/]
--[[User:Djdas|djdas]] 15:54, 13 June 2009 (UTC)There aren't any confirmations of ArmedSlack running on Freerunner either on the website or the official ML, do you have any link pointing on that?
<br style="clear: both">
=== Abandoned ===

==== FDOM (FAT and Dirty Openmoko) ====
{{Template:Works on FDOM}}
[[FDOM]] was a distribution based on [[Om 2008]], updated with many ready-to-use applications and with fixes posted in the mailing lists.

{{Main|FDOM}}
<br style="clear: both">

==== Om series ====
* '''[[Om 2009]]''' was intended to be the new distro; it is not a simple follow-on from [[Om 2008]]. It is based on the [http://freesmartphone.org freesmartphone.org] milestone 5.5 framework. Development of Om 2009 was ended and developers moved on to work on other distros instead.

{{Main|Om2009}}

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

{{Main|Om 2008}}

* '''[[Om 2007.2]]''' was the first distribution created by Openmoko. The interface was totally finger-oriented, optimized for 285ppi, and very orange. It used the GTK+ stack, which is part of the [http://www.gnome.org/mobile/ GNOME Mobile] platform. This distribution is now considered obsolete and not being worked on by Openmoko Inc or by OpenedHand.

{{Main|Om 2007.2}}

=== Others / unreleased ===
* The [http://www.neopwn.com/software.php NeoPwn] network auditng system's core is a modified Linux 2.6.24 kernel, with cross-compiled module driver support for the numerous compatible addon devices running on a FULL Debian (ARMEL) operating system. The filesystem has been optimized for performance and size and includes the NeoPwn menu system and several GUI dialogs for hardware control and attack automation. ''Status: Unknown, the GPL requires source code to be distributed only to customers''.
* [http://runningbear.org/trac RunningBear] is an innovative, yet free and open-source Operating System for hackable devices driven by Bearstech. Lightweight, Portable, Secure, Friendly and Useful. ''Status: In development''.
* [http://pokylinux.org/ Poky] and Sato, by OpenedHand/Intel. An open source platform build tool derived from OE. It is a complete software development environment for the creation of Linux devices. It enables you to design, develop, build, debug, and test a complete, modern, software stack using Linux, the X Window System and GNOME Mobile based application frameworks for both ARM and x86 based platforms. ''Status: The "Nightly Build" Image works fine on Neo Freerunner, but phone functionality doesn't.''
* [http://pyneo.org/ PyNeo] pyneo is a stack for mobile devices excessivly using dbus, glib and evas. Pyneo is NO distribution but a middleware or framework like FSO which itself developed from a very early version of pyneo. Current pyneo images are entirely based on debian instead of oe. ''Status: still active and in development! ask around on #pyneo.org ''
* [http://www.quantum-step.com/ mySTEP] by Openmoko distributor Golden Delicious Computers is based on GNUstep and brings a Objective-C API to the Neo. Core GUI frameworks are "Foundation" & "AppKit". It has been shown on FOSDEM 2008, LinuxTag 2008 and SYSTEMS 2008 to run on the Neo 1973. If someone reengineers UIKit, (open) source code compatibility to iPhone apps appears achievable. ''Status: slow progress behind the scenes''
* [http://www.archmobile.org/ Archlinux] is a distribution that follows the KISS principle.

== Features by distribution/release target ==

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

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

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

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

=== User Interaction ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=8%|[[Om 2009]] !! width=8%|[[Om 2008]] !! width=8%|Om 2007.2 !! width=8%|[[SHR]] !! width=8%|[[Qt Extended Improved]] !! width=8%|[[Debian]] !! width=8%|[[Gentoo]] !! width=8%|[[Android]]
|-
| Finger friendly || {{Yes}} || Partially || Partially || {{Yes}} || {{Yes}} || {{Yes}} [[Illume|(1)]] || {{Yes}} || {{Yes}}
|-
| Accelerometer || {{Yes}} (1) || {{Yes}} [[Rotate|(1)]][[Gestures|(1)]] || {{No}} || {{Yes}} || {{No}} || {{Yes}} || ?? || {{Yes}}
|-
|}

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

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

Footnotes:

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

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

(*) unstable

==Quick download page==

[[Download]]

== See also ==

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

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

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

[[Category:Distributions| ]]

Manuals/Neo FreeRunner/eu

2010-01-30T14:17:18Z

Joseba:

{{Languages|Manuals/Neo FreeRunner}}

Mila esker Neo FreeRunner erosteagatik. [[Neo FreeRunner]] telefonoa Openmoko proiekturako sortu den bigarren hardware plataforma da. Gida honetan hasierako erabilerarako behar duzuna eta tresna berria ezagutzen ikasiko duzu.

[[Image:Freerunner box.png|200px|thumb|Neo FreeRunner Package]]

== Hardwarearen konfigurazioa, Neo Freerunnerra eta bere osagaiak ezagutzen hasi ==

=== Mikro-SD txartelaren, SIM Txartelaren eta bateriaren instalazioa ===

# Neo Freerunnerraren atzeko tapa kendu, horretarako, alboetatik heldu telefonoa, eta goian daukan arteka edo zirrikituan azkazalen laguntzaz atzerantz bultza eta atzeko tapa askatuko da.
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu13.jpg|233px|thumb|zirrikituan azkazalez bultza.|center]]</td>
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu14.jpg|250px|thumb|Atzeko estalkia askatu!|center]]</td>
</tr>
</table>
# Orain bateria jarri behar den kokagunea agerian dago, eta bere azpian telefoniako txartela eta Mikro SD txartela jartzeko guneak ere ikusiko dituzu.
# Lehendabizi SIM txartelaren estalkia askatu behar da, horretarako, beherantz (kanpoko USB entxufe alderantz) bultza metalezko klipa. Kontu handiz ibili, zati delikatua baita hau, eta indarrez eginez gero kalteak eragin daitezke. Norantza ere arretaz aztertu.
[[Image:menu11.jpg|260px|thumb|Jarri SIM eta SD txartelak hemen.|center]]
# Altxa SIM txartela eusteko klipa.
# Mikro-SD txartelak erabili aurretik begiratu [[Supported_microSD_cards |onartzen direla jakina den Mikro-SD txartelen zerrenda]].
# Mikro-SD euskarria bi aldetatik lotuta dago, Errazena alda bakoitza banaka askatzea da. Erditik tiraz bi aldeak batera askatzen saituz gero, loturak indar handiagoa egiten du, beraz, lehendabizi alde bat askatu eta gero bestea. Kontuz labanekin edota bihurkinekin! honako [http://people.openmoko.org/joerg/sdcard-handle/ argazkietan] ikus daiteke euskarria irekita eta txartelak sartuta.
# Sartu Mikro-SD txartela bere euskarrian. Kontuan izan euskarrian txartela eusteko kartolatxoak (eusteko topeak) daudela, kartola horien artetik sartu txartela (tente geratuko da txartela, kontaktuak beheko aldean) eta ondoren itxi euskarria txartela etzanda gera dadin. Txartelaren kontaktuak beheko aldean geratu beharko dute, alegia ez dira ikusiko, eta gainera telefonoaren ertzean egongo dira.
# Mikro-SD txartelaren euskarria etzan ondoren, bi lokailuak ondo itxi direla ziurtatu. Gaizki itxitako euskarriko txartela ez du ikusiko telefonoak.
# SIM txartela bere euskarrian sartu, kontu izan honek ere metalezko bi kartolatxo dauzkala, eta horien artean sartu behar dela.Berriz ere kontaktu elektrikoak beherantz geratu behar dute, eta ebakitako ertza FreeRunner gailuaren kanpo aldetik gertu geratu behar du (GPS antenaren aldean).
# Etzan SIM txartelaren euskarria eta metalezko klipa GPS antenaren aldera labaindu ondo itxita gera dadin.
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">
[[Image:FR_SIM_SD_open.jpg|457px|thumb|SIM and SD euskarriak irekita, eta txartelak beren lekuetan|center]]</td>
<td style="padding: 1px 1em 0; background: #ffffff;">
[[Image:Engchang.jpg|392px|thumb|Gailu batzuek itxura hau daukate, tanta modukoa ez da akatsa|center]]</td>
</tr>
</table>
# Sartu bateria horretarako gunean, bateriaren kontaktuak telefonoaren kontaktuekin elkartuz. Lehendabizi kontaktuen aldea sartu.
# FreeRunnerraren atzeko tapa bere tokian jarri.

{| class="wikitable" style="background#00CC00;border-left:1px solid white;border-right:1px solid white;border-top:0px solid white; border:1px solid #00CC00; float:right; margin: 0 0 1em 1em;"
! style="background:#00cc00;border-left:1px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #00CC00;" |<font color=white>Tips</font>
|-
!style="background:#ffffff;border-left:1px solid white;border-right:1px solid white;border-top:0px solid white; border:1px solid #FFFFff;" |
<div align=left>
[http://video.google.de/videoplay?docid=-8343770443102960945 Bideotxoa] ere ikus dezakezu. Neo gailuaren bertsio zaharrarekin egina den arren, antzeko prozesua da.
</div>

|}

===Neo FreeRunnerra kargatu===

Lehendabiziko erabileraren aurretik Bateria guztiz kargatu behar da. Bateria kargatzeko 1000mA-ko kargatzailea edota 500mA-ko karga eman dezakeen USB portu bat erabil daitezke. Gaur egungo konputagailuek ez daukate inolako arazorik NEO Freerunnera kargatzeko USB portuak erabiliz. '''Itzalita baldin badago, ez da kargatuko''', beraz, piztu eta interfaze grafikoa (GUI edo Graphical User Interface) agertu arte piztu dadila. USB kablea sartzen duzunean (USB kableak konputagailuari konektatuta egon behar du edota 1000mA-ko kargatzaileari, alegia, argi indarra eduki behar du) automatikoki piztuko da. Ez bada bere kabuz pizten, eskuz piztu dezakezu, horretarako, pizteko botoia sakatu (bost edo sei segundo sakatuta eduki). Botoi hau USB entxufearen azpian dago.

Nahiz eta kargatzaileak 2A-ko indarra emateko gaitasuna eduki, Neo Freerunnerraren karga-abiadura 1A-koa da, eta beraz, kargatze-abiadura kargatzailearen gaitasuna baino txikiagoa da.

Entxufeak hiru mota onartzen ditu: berez Ipar Ameriketako entxufea da, baina estalkia kendu eta Europako edota Erresuma Batuko entxufeetarako egokigailua jar daitezke entxufean. Horretarako, entxufearen estalkiaren kisketa sakatu eta estalkia kanporantz labaindu behar da. Kisketa entxufearen estalkiaren testua dagoen kontrako aldean dago. Kontuan izan Ipar Amerikako entxufearen bi konektoreak ez direla askatuko, horien gainetik sartu behar da egokigailua. Egokigailua ere antzera kentzen da.

Bateria kargatzeko denbora sarrerako indarraren araberakoa da,
# 100mA-ko indarraz 12~15 ordu behar dira (kontuan izan etete-egoeran ez badago 100mA baino gehiago behar dituela gailuak)
# sarrerako indarra 500mA-koa bada (PC-en USB konexioa) 2~3 ordu behar dira, eta
#1000mA-ko indarrez (kargatzailea) 1.5~3 ordu behar dira. (90%~100%) <br>
Gailuak 100 mA baino gehiago behar ditu lanean ari denean, beraz, USB bidezko indarra 100mAkoa baldin bada, eteteko egoeran ez badago, gailua ez da kargatuko.

{{Note|ikusi [[Neo_FreeRunner_Hardware_Issues|Neo FreeRunner Hardware arazoak]] bateria guztiz husten ez lagatzeari buruz.}}

===Botoiak eta konexioak ===

<table width="80%" style="clear: both; border-collapse: collapse" valign="top">
<tr>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu9.jpg|370px|thumb|Pizteko botoia, USBa eta kanpoko GPS Antena (ezkerretik eskuinera)|center]]</td>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu8.jpg|370px|thumb|AUX Botoia eta aurikularren jack-a (ezkerretik eskuinera)|center]]</td>
</tr>
<tr>
<td></td>
<td>'''Pizteko''' botoia
Ikututxoa edo kolpetxoa emanaz GTA02 gailua '''etete-egoeran''' jarriko da.

Sakatuta edukiz gero gailua itzali egingo da.</td>
<td></td>
<td>'''Aux''' botoia
Ikututxo bidez edo sakatuz pantaila blokeatuko da.
</td>
</tr>
</table>

'''Aurikularren Jack-a'''

Aurikularren jack-a 2.5mm dituen konektorea da, eta 4 kontaktu dauzka: stereo + MIC. Motorola smartphone (A780,A1200, ...) eta V-360 gailuek erabiltzen dutenarekin bateragarria da.

Informazio gehiago [[Headset|aurikularren]] orrian.

===Zure gailuaren aldaera zein den jakiteko===
Zure gailua zer nolakoa den jakitea komeni zaizu, hau da, gailuaren aldaera (revision) zein den zehaztea komeni da.

# Gogoan jaso data kodea, jaso duzun kutxaren azpian eranskailu batean egongo da.
# irakurri [[Finding_hardware_revision|hardware aldaeraren bila]]

Bi hauek garrantzitsuak dira, zure gailuan, fabrikan, zein irudi flasheatu (ezarri) duten jakiten lagunduko baitizute. (c.f. [[Distributions|banaketak]] eta [[GTA02_revisions | Neo FreeRunner (aka GTA02) aldaerak]]).

==Softwarea instalatu==

Freerunnerrean dagoen software ia guztia aldatu edo eguneratu daiteke, bai eta gailua pizteko beharrezkoa den '''abiarazlea''' eta GSM txipean dagoen softwarea ere.

Izatez, Neo FreeRunnerra berezko [[Distributions| banaketa]] bat barnean ezarrita duela iritsiko zaizu, beraz, hemendik aurrerakorik egin beharrik ez duzu izango. Irakurri [[Om_2008 | OM 2008]] [[Manuals/Om_2008|eskuliburua]] zure telefonoa erabiltzen hasteko. Gerora, zure gailuan [[Distributions|banaketa]] berriagoa edota erabilera zabalagoa duena edota aukera bereziak eskaintzen dituena instalatu nahi zenezake, kasu horretan irakurri ondokoa.

===Abiarazlea instalatu===

Telefonoko sistema eragilea abiarazteko beharrezkoa da bootloader edo abiarazlea. '''Qi''' da gomendatutako abiarazlea Neo FreeRunner gailuan. Horrekin, abiatzeko prozesua azkarragoa baita. Hainbat sistema eragileren artean aukeratu ahal izateko, U-Boot abiarazlea mantendu beharko zenuke, hau abiarazle zaharragoa da. Abiarazlea http://downloads.openmoko.org/distro/testing/NeoFreerunner/ helbidetik har dezakezu eta [[NeoTool]] programaren bidez zure Linux PCan instala dezakezu. (ikusi http://wiki.openmoko.org/wiki/No_Linux ez badaukazu Linuxpean dabilen PCrik, baina hobe zenuke linux banaketa zirraragarriren bat instalatuko bazenio zeure PCari)

===GSM Firmwarea eguneratu===

Gaur egungo GSM Firmwareaaren bertsioak Moko 11 izena du. Zure bertsioa zaharragoa bada bertsio berritzea egin beharko zenuke, horrela telefono gailuaren hainbat funtzionalitate-arazo konponduko baitira.



FreeRunner gailua mikroSD txartelean instalatutako sistemaren bidez abiaraziz hasi behar da, abiaratze honek automatikoki eragingo ditu beharrezkoak diren aginduak eta GSM firmwarea txipera irauliko (flasheatuko?) du. mikroSDra abiarazteko irudia kopiatzea era berezian egin behar izaten da (linuxeko dd agindua erabili beharko duzu ziurrenik) eta mikroSD irudia kopiatzerakoan mikroSDan dagoen informazioa guztiz ezabatuko da. Irudia tentuz jarri mikroSD txartelean, eta era egokian formateatu abiarazteko sistema egokia daukala ziurtatuz.
Prozedura hau fidagarria da GTA02 gailuan MOKO11 ezartzeko (flasheatzeko). Huts egiteko aukerak oso urriak dira _zehazki_ jarraitzen badituzu argibideak. Hemen azaldutako bideari jarraituz ez diozu kalterik eragingo zure gailuari.

'''Arreta berezia jarri `dd` agindua eragiterakoan nora kopiatu behar duen esaterakoan, dispositibo *fisikoa* adierazi behar da, esaterako /dev/sdm, eta *ez* partizioa (alegia ez /dev/sdmp1). Horrez gain, mikroSDko partizio guztiak desmontatuta daudela ziur egon `dd` agindua abiarazterakoan'''<br>
Aurrekoaz ziur zaudenean, ''berriz begiratu ea aurreko abisuko baldintza guztiak betetzen dituzun'', gainera, bada ez bada, ondo begiratu ea mikroSD dispositiboa den `dd` aginduari adierazitakoa, izan ere, disko gogorra adieraziz gero disko gogorreko eduki guztia ezabatuko baitu, eta oso erraza da nahastea, alegia, mikroSDa /dev/sdc izan daiteke, baina /dev/sdb disko gogorra izan daiteke. Beraz, '''arreta handiz idatzi agindua'''.

<ol>
<li>Jaitsi eta <tt>untar</tt> (desenpaketatu) http://people.openmoko.org/joerg/calypso_moko_FW/moko11/flash-moko11_uSD-image.tar.gz zeure mahai gaineko PCra. Irakurri <tt>README.tx</tt> fitxategia, untar egiterakoan paketetik aterako da fitxategia.</li>

<li>Zure PCko irakurgailuan sartu mikroSD txartela, eta automatikoki muntatutako partizioak desmuntatu (mikroSDko partizioak, noski), zZein partizio muntatu diren jakiteko <tt>mount</tt> edo <tt>df -h</tt> aginduak erabil ditzakezu. Desmuntatzeko ez erabili "era seguruan atera txartela", <tt>umount</tt> agindua erabili desmuntatzeko.</li>

<li>mikroSD txartelera <tt>flash-moko11-2.image</tt> fitxategian dagoen irudia fisikoki idazteko <tt>dd</tt> agindua erabili. Kontuz agindu honekin: non idatzi behar duen esateko mikroSD txartelaren dispositibo fisikoa zein den esan behar zaio aginduari, ez partizioren bat, baizik eta dispositiboa bera. Gainera, dispositiboan dagoen eduki guztia ezabatuko du eragiketak, beraz, dispositibo okerra esan ezkero, kalte handia sor daiteke. <tt>dd</tt> aginduari disko gogorrari dagokion dispositibo fisikoan kopiatzeko agindua emango bagenio, partizio taula eta bertako eduki guztia ezabatuko du, beraz, sistema osoa berrinstaltu beharko genuke. Eragiketa hau egiteko orduan root erabiltzailearen baimenak eduki behar dira, alegia root bezala sartu behar da sisteman edo sudo agindu erabili beharko da:</li>

% sudo dd if=flash-moko11-2.image of=/dev/mmcblk0

<li>mikroSD txartela atera aurretik <tt>sync</tt> edo <tt>eject <device></tt> aginduak erabiltzea komeni da, izan ere txartelera informazioa guztiz pasa dela ziur egon behar baitugu.</li>

<li>Sartu mikroSD txartela zeure FreeRunner mugikorrera, eta abiarazi gailua '''[[Booting_the_Neo_FreeRunner#Log_into_U-Boot_in_the_NOR_Flash|NOR-U-Boot]]''' bideari jarraituz, eta aukeratu "Boot from microSD" aukera.</li>

<li>Firmwarea flash memoriara kopiatzeko prozesua abiatuko dela ikusiko duzu, eta bukaeran, 6 minutu inguru igaro ondoren, "d_o_n_e" kolore berdez idatzita azalduko da. Une horretan pizteko/itzaltzeko botoiak ezin du Freerunnerra itzali, botoia sakatzeak eten/itzuli funtzioak beteko ditu, baina ez itzaltzekoa. Gutxienez bi eratara itzal dezakezu Freerunnerra, alde batetik, <tt>ssh</tt> aginduaren bidez FreeRunnerrera konektatu usb kable bidez lotutako PC batetik (edo wifi konexio bidez) eta itzaltzeko agindua eragin dezakezu: <br>
# shutdown -h now<br>
Itzaltzeko beste era bat ere badago, askoz ere sinpleagoa da bigarren era hau (baina ez hain dotorea): bateria kendu eta itzali egingo da, a zer erremedio!.
Firmwarea ondo kopiatu dela ikusteko, ssh konexio bidez <tt>mickeyterm</tt> erabil daiteke modemarekin komunikatzeko eta bertsioa begiratzeko</li>
</ol>
====OHARRA====

Zure PCak mikroSD txartelak irakurtzeko gailurik ez badauka, mikroSD txartelera <tt>dd</tt> agindu bidez moko11 irudiaren kopia FreeRunner gailuan bertan egin dezakezu: instalatu <tt>task-base-smbfs</tt>, mikroSD txartela desmuntatu, horretarako <tt>umount /media/card</tt> agindua erabili (partizio gehiago baleuzka eta horiek ere muntatuta baleude guztiak desmuntatu). Une honetan bi aukera dauzkazu gutxienez:
<ol>
<li> Zure PCan dagoen irudia daukan direktorioa FreeRunnerreko fitxategi sisteman muntatu dezakezu, eta ondoren, <tt>dd</tt> agindu bidez zuzenean FreeRunnerrean dagoen mikroSD txartelera kopia dezakezu. Prozesu horrek 12 minutu inguru iraun ditzake. Eragiketa hau FreeRunnerreko shell batetik egin behar da.
</li>
<li>Alderantziz ere jardun daiteke, alegia, PCko shell batean lan egin dezakezu, horretarako, lehenengo FreeRunnerrean mikroSD txartela desmuntatu:<br>
root@om-gta02 ~ $ umount /media/card<br>
Eta ondoren, PCko shell batean (usb edo wifi konexioa eskatzen du honek):<br>
scp flash-moko11-2.image root@192.168.0.202:/dev/mmcblk0
</li>
</ol>
Prozesu horiek azkartu egin daitezke, irudia gzip bidez konprimituz makinatik makinara pasa beharreko informazio-kopurua gutxitu egin daiteke, eta deskonprimitzeko aginduari zuzenean mikroSD txartelera kopiatzeko esan diezaiokegu:

% gzip -d < flash-moko11-2.image.gz > /dev/mmcblk0

Agindu honenkin, eta FreeRunnerreko fitxategi sisteman nahikoa leku libre edukiz gero, ez dogo PCa erabili beharrik, alegia, konprimitutako fitxategia FreeRunnerrean bertan jaso daiteke, eta deskonprimitu mikroSD txartelera. Baina 92MB libre behar ditu gutxi gora behera.

====BIGARREN OHARRA====

Abiorako [[Qi]] instalatuta eduki ala ez (ikusi aurrekoa), pizterakoan NOR menuraino joan behar da (horretarako AUX botoia sakatuta daukazun bitartean pizteko botoia sakatu) eta bertan "Boot from microSD (fat/ext2)" aukeratu behar duzu instalazio prozesua abiatu dadin. (per DocScrutinizer in #openmoko). '''Ez''' utzi Qi abiarazleari mikroSDko partizioa izan dadin sistemaren abioa. Antzekoa dirudien arren, berdez idatzitako "d_o_n_e" ez da azalduko eta ondorioz egin beharrekoa ez du egingo.

You can confirm the firmware version number using the [[OpenmokoFramework/mickeyterm|mickeyterm]] (cmd: "AT+CGMR"). In SHR-Settings, Phone/Modem Information will supply the same number.

===Installing a distribution===

This section describes how to install a distribution on the internal flash memory of the Neo FreeRunner. If you want to install it on the memory card please refer to the guide provided by the distribution.

For installing a new distribution you will need two files, a root file system (rootfs) image and a kernel image. The root file system image usually ends with ".jffs2", and the kernel image ends with ".uimage.bin". You can get these files from http://wiki.openmoko.org/wiki/Download . Use the program NeoTool to install the distribution on your FreeRunner. The flashing process can take up to 15 minutes for a ~70MB image. It is also wise to make sure that your Neo has enough battery charge prior to flashing.

When flashing succeeds the following will be shown:

<pre>
status(0) = No error condition is present
Done!
</pre>

[[Category:Manuals]]

Manuals/Neo FreeRunner/eu

2010-01-30T14:09:12Z

Joseba:

{{Languages|Manuals/Neo FreeRunner}}

Mila esker Neo FreeRunner erosteagatik. [[Neo FreeRunner]] telefonoa Openmoko proiekturako pentsatutako bigarren hardware plataforma da. Gida honetan hasierako erabilerarako behar duzuna eta tresna berria ezagutzen ikasiko duzu.

[[Image:Freerunner box.png|200px|thumb|Neo FreeRunner Package]]

== Hardwarearen konfigurazioa, Neo Freerunnerra eta bere osagaiak ezagutzen hasi ==

=== Mikro-SD txartelaren, SIM Txartelaren eta bateriaren instalazioa ===

# Neo Freerunnerraren atzeko tapa kendu, horretarako, alboetatik heldu telefonoa, eta goian daukan arteka edo zirrikituan azkazalen laguntzaz atzerantz bultza eta atzeko tapa askatuko da.
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu13.jpg|233px|thumb|zirrikituan azkazalez bultza.|center]]</td>
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu14.jpg|250px|thumb|Atzeko estalkia askatu!|center]]</td>
</tr>
</table>
# Orain bateria jarri behar den kokagunea agerian dago, eta bere azpian telefoniako txartela eta Mikro SD txartela jartzeko guneak ere ikusiko dituzu.
# Lehendabizi SIM txartelaren estalkia askatu behar da, horretarako, beherantz (kanpoko USB entxufe alderantz) bultza metalezko klipa. Kontu handiz ibili, zati delikatua baita hau, eta indarrez eginez gero kalteak eragin daitezke. Norantza ere arretaz aztertu.
[[Image:menu11.jpg|260px|thumb|Jarri SIM eta SD txartelak hemen.|center]]
# Altxa SIM txartela eusteko klipa.
# Mikro-SD txartelak erabili aurretik begiratu [[Supported_microSD_cards |onartzen direla jakina den Mikro-SD txartelen zerrenda]].
# Mikro-SD euskarria bi aldetatik lotuta dago, Errazena alda bakoitza banaka askatzea da. Erditik tiraz bi aldeak batera askatzen saituz gero, loturak indar handiagoa egiten du, beraz, lehendabizi alde bat askatu eta gero bestea. Kontuz labanekin edota bihurkinekin! honako [http://people.openmoko.org/joerg/sdcard-handle/ argazkietan] ikus daiteke euskarria irekita eta txartelak sartuta.
# Sartu Mikro-SD txartela bere euskarrian. Kontuan izan euskarrian txartela eusteko kartolatxoak (eusteko topeak) daudela, kartola horien artetik sartu txartela (tente geratuko da txartela, kontaktuak beheko aldean) eta ondoren itxi euskarria txartela etzanda gera dadin. Txartelaren kontaktuak beheko aldean geratu beharko dute, alegia ez dira ikusiko, eta gainera telefonoaren ertzean egongo dira.
# Mikro-SD txartelaren euskarria etzan ondoren, bi lokailuak ondo itxi direla ziurtatu. Gaizki itxitako euskarriko txartela ez du ikusiko telefonoak.
# SIM txartela bere euskarrian sartu, kontu izan honek ere metalezko bi kartolatxo dauzkala, eta horien artean sartu behar dela.Berriz ere kontaktu elektrikoak beherantz geratu behar dute, eta ebakitako ertza FreeRunner gailuaren kanpo aldetik gertu geratu behar du (GPS antenaren aldean).
# Etzan SIM txartelaren euskarria eta metalezko klipa GPS antenaren aldera labaindu ondo itxita gera dadin.
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">
[[Image:FR_SIM_SD_open.jpg|457px|thumb|SIM and SD euskarriak irekita, eta txartelak beren lekuetan|center]]</td>
<td style="padding: 1px 1em 0; background: #ffffff;">
[[Image:Engchang.jpg|392px|thumb|Gailu batzuek itxura hau daukate, tanta modukoa ez da akatsa|center]]</td>
</tr>
</table>
# Sartu bateria horretarako gunean, bateriaren kontaktuak telefonoaren kontaktuekin elkartuz. Lehendabizi kontaktuen aldea sartu.
# FreeRunnerraren atzeko tapa bere tokian jarri.

{| class="wikitable" style="background#00CC00;border-left:1px solid white;border-right:1px solid white;border-top:0px solid white; border:1px solid #00CC00; float:right; margin: 0 0 1em 1em;"
! style="background:#00cc00;border-left:1px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #00CC00;" |<font color=white>Tips</font>
|-
!style="background:#ffffff;border-left:1px solid white;border-right:1px solid white;border-top:0px solid white; border:1px solid #FFFFff;" |
<div align=left>
[http://video.google.de/videoplay?docid=-8343770443102960945 Bideotxoa] ere ikus dezakezu. Neo gailuaren bertsio zaharrarekin egina den arren, antzeko prozesua da.
</div>

|}

===Neo FreeRunnerra kargatu===

Lehendabiziko erabileraren aurretik Bateria guztiz kargatu behar da. Bateria kargatzeko 1000mA-ko kargatzailea edota 500mA-ko karga eman dezakeen USB portu bat erabil daitezke. Gaur egungo konputagailuek ez daukate inolako arazorik NEO Freerunnera kargatzeko USB portuak erabiliz. '''Itzalita baldin badago, ez da kargatuko''', beraz, piztu eta interfaze grafikoa (GUI edo Graphical User Interface) agertu arte piztu dadila. USB kablea sartzen duzunean (USB kableak konputagailuari konektatuta egon behar du edota 1000mA-ko kargatzaileari, alegia, argi indarra eduki behar du) automatikoki piztuko da. Ez bada bere kabuz pizten, eskuz piztu dezakezu, horretarako, pizteko botoia sakatu (bost edo sei segundo sakatuta eduki). Botoi hau USB entxufearen azpian dago.

Nahiz eta kargatzaileak 2A-ko indarra emateko gaitasuna eduki, Neo Freerunnerraren karga-abiadura 1A-koa da, eta beraz, kargatze-abiadura kargatzailearen gaitasuna baino txikiagoa da.

Entxufeak hiru mota onartzen ditu: berez Ipar Ameriketako entxufea da, baina estalkia kendu eta Europako edota Erresuma Batuko entxufeetarako egokigailua jar daitezke entxufean. Horretarako, entxufearen estalkiaren kisketa sakatu eta estalkia kanporantz labaindu behar da. Kisketa entxufearen estalkiaren testua dagoen kontrako aldean dago. Kontuan izan Ipar Amerikako entxufearen bi konektoreak ez direla askatuko, horien gainetik sartu behar da egokigailua. Egokigailua ere antzera kentzen da.

Bateria kargatzeko denbora sarrerako indarraren araberakoa da,
# 100mA-ko indarraz 12~15 ordu behar dira (kontuan izan etete-egoeran ez badago 100mA baino gehiago behar dituela gailuak)
# sarrerako indarra 500mA-koa bada (PC-en USB konexioa) 2~3 ordu behar dira, eta
#1000mA-ko indarrez (kargatzailea) 1.5~3 ordu behar dira. (90%~100%) <br>
Gailuak 100 mA baino gehiago behar ditu lanean ari denean, beraz, USB bidezko indarra 100mAkoa baldin bada, eteteko egoeran ez badago, gailua ez da kargatuko.

{{Note|ikusi [[Neo_FreeRunner_Hardware_Issues|Neo FreeRunner Hardware arazoak]] bateria guztiz husten ez lagatzeari buruz.}}

===Botoiak eta konexioak ===

<table width="80%" style="clear: both; border-collapse: collapse" valign="top">
<tr>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu9.jpg|370px|thumb|Pizteko botoia, USBa eta kanpoko GPS Antena (ezkerretik eskuinera)|center]]</td>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu8.jpg|370px|thumb|AUX Botoia eta aurikularren jack-a (ezkerretik eskuinera)|center]]</td>
</tr>
<tr>
<td></td>
<td>'''Pizteko''' botoia
Ikututxoa edo kolpetxoa emanaz GTA02 gailua '''etete-egoeran''' jarriko da.

Sakatuta edukiz gero gailua itzali egingo da.</td>
<td></td>
<td>'''Aux''' botoia
Ikututxo bidez edo sakatuz pantaila blokeatuko da.
</td>
</tr>
</table>

'''Aurikularren Jack-a'''

Aurikularren jack-a 2.5mm dituen konektorea da, eta 4 kontaktu dauzka: stereo + MIC. Motorola smartphone (A780,A1200, ...) eta V-360 gailuek erabiltzen dutenarekin bateragarria da.

Informazio gehiago [[Headset|aurikularren]] orrian.

===Zure gailuaren aldaera zein den jakiteko===
Zure gailua zer nolakoa den jakitea komeni zaizu, hau da, gailuaren aldaera (revision) zein den zehaztea komeni da.

# Gogoan jaso data kodea, jaso duzun kutxaren azpian eranskailu batean egongo da.
# irakurri [[Finding_hardware_revision|hardware aldaeraren bila]]

Bi hauek garrantzitsuak dira, zure gailuan, fabrikan, zein irudi flasheatu (ezarri) duten jakiten lagunduko baitizute. (c.f. [[Distributions|banaketak]] eta [[GTA02_revisions | Neo FreeRunner (aka GTA02) aldaerak]]).

==Softwarea instalatu==

Freerunnerrean dagoen software ia guztia aldatu edo eguneratu daiteke, bai eta gailua pizteko beharrezkoa den '''abiarazlea''' eta GSM txipean dagoen softwarea ere.

Izatez, Neo FreeRunnerra berezko [[Distributions| banaketa]] bat barnean ezarrita duela iritsiko zaizu, beraz, hemendik aurrerakorik egin beharrik ez duzu izango. Irakurri [[Om_2008 | OM 2008]] [[Manuals/Om_2008|eskuliburua]] zure telefonoa erabiltzen hasteko. Gerora, zure gailuan [[Distributions|banaketa]] berriagoa edota erabilera zabalagoa duena edota aukera bereziak eskaintzen dituena instalatu nahi zenezake, kasu horretan irakurri ondokoa.

===Abiarazlea instalatu===

Telefonoko sistema eragilea abiarazteko beharrezkoa da bootloader edo abiarazlea. '''Qi''' da gomendatutako abiarazlea Neo FreeRunner gailuan. Horrekin, abiatzeko prozesua azkarragoa baita. Hainbat sistema eragileren artean aukeratu ahal izateko, U-Boot abiarazlea mantendu beharko zenuke, hau abiarazle zaharragoa da. Abiarazlea http://downloads.openmoko.org/distro/testing/NeoFreerunner/ helbidetik har dezakezu eta [[NeoTool]] programaren bidez zure Linux PCan instala dezakezu. (ikusi http://wiki.openmoko.org/wiki/No_Linux ez badaukazu Linuxpean dabilen PCrik, baina hobe zenuke linux banaketa zirraragarriren bat instalatuko bazenio zeure PCari)

===GSM Firmwarea eguneratu===

Gaur egungo GSM Firmwareaaren bertsioak Moko 11 izena du. Zure bertsioa zaharragoa bada bertsio berritzea egin beharko zenuke, horrela telefono gailuaren hainbat funtzionalitate-arazo konponduko baitira.



FreeRunner gailua mikroSD txartelean instalatutako sistemaren bidez abiaraziz hasi behar da, abiaratze honek automatikoki eragingo ditu beharrezkoak diren aginduak eta GSM firmwarea txipera irauliko (flasheatuko?) du. mikroSDra abiarazteko irudia kopiatzea era berezian egin behar izaten da (linuxeko dd agindua erabili beharko duzu ziurrenik) eta mikroSD irudia kopiatzerakoan mikroSDan dagoen informazioa guztiz ezabatuko da. Irudia tentuz jarri mikroSD txartelean, eta era egokian formateatu abiarazteko sistema egokia daukala ziurtatuz.
Prozedura hau fidagarria da GTA02 gailuan MOKO11 ezartzeko (flasheatzeko). Huts egiteko aukerak oso urriak dira _zehazki_ jarraitzen badituzu argibideak. Hemen azaldutako bideari jarraituz ez diozu kalterik eragingo zure gailuari.

'''Arreta berezia jarri `dd` agindua eragiterakoan nora kopiatu behar duen esaterakoan, dispositibo *fisikoa* adierazi behar da, esaterako /dev/sdm, eta *ez* partizioa (alegia ez /dev/sdmp1). Horrez gain, mikroSDko partizio guztiak desmontatuta daudela ziur egon `dd` agindua abiarazterakoan'''<br>
Aurrekoaz ziur zaudenean, ''berriz begiratu ea aurreko abisuko baldintza guztiak betetzen dituzun'', gainera, bada ez bada, ondo begiratu ea mikroSD dispositiboa den `dd` aginduari adierazitakoa, izan ere, disko gogorra adieraziz gero disko gogorreko eduki guztia ezabatuko baitu, eta oso erraza da nahastea, alegia, mikroSDa /dev/sdc izan daiteke, baina /dev/sdb disko gogorra izan daiteke. Beraz, '''arreta handiz idatzi agindua'''.

<ol>
<li>Jaitsi eta <tt>untar</tt> (desenpaketatu) http://people.openmoko.org/joerg/calypso_moko_FW/moko11/flash-moko11_uSD-image.tar.gz zeure mahai gaineko PCra. Irakurri <tt>README.tx</tt> fitxategia, untar egiterakoan paketetik aterako da fitxategia.</li>

<li>Zure PCko irakurgailuan sartu mikroSD txartela, eta automatikoki muntatutako partizioak desmuntatu (mikroSDko partizioak, noski), zZein partizio muntatu diren jakiteko <tt>mount</tt> edo <tt>df -h</tt> aginduak erabil ditzakezu. Desmuntatzeko ez erabili "era seguruan atera txartela", <tt>umount</tt> agindua erabili desmuntatzeko.</li>

<li>mikroSD txartelera <tt>flash-moko11-2.image</tt> fitxategian dagoen irudia fisikoki idazteko <tt>dd</tt> agindua erabili. Kontuz agindu honekin: non idatzi behar duen esateko mikroSD txartelaren dispositibo fisikoa zein den esan behar zaio aginduari, ez partizioren bat, baizik eta dispositiboa bera. Gainera, dispositiboan dagoen eduki guztia ezabatuko du eragiketak, beraz, dispositibo okerra esan ezkero, kalte handia sor daiteke. <tt>dd</tt> aginduari disko gogorrari dagokion dispositibo fisikoan kopiatzeko agindua emango bagenio, partizio taula eta bertako eduki guztia ezabatuko du, beraz, sistema osoa berrinstaltu beharko genuke. Eragiketa hau egiteko orduan root erabiltzailearen baimenak eduki behar dira, alegia root bezala sartu behar da sisteman edo sudo agindu erabili beharko da:</li>

% sudo dd if=flash-moko11-2.image of=/dev/mmcblk0

<li>mikroSD txartela atera aurretik <tt>sync</tt> edo <tt>eject <device></tt> aginduak erabiltzea komeni da, izan ere txartelera informazioa guztiz pasa dela ziur egon behar baitugu.</li>

<li>Sartu mikroSD txartela zeure FreeRunner mugikorrera, eta abiarazi gailua '''[[Booting_the_Neo_FreeRunner#Log_into_U-Boot_in_the_NOR_Flash|NOR-U-Boot]]''' bideari jarraituz, eta aukeratu "Boot from microSD" aukera.</li>

<li>Firmwarea flash memoriara kopiatzeko prozesua abiatuko dela ikusiko duzu, eta bukaeran, 6 minutu inguru igaro ondoren, "d_o_n_e" kolore berdez idatzita azalduko da. Une horretan pizteko/itzaltzeko botoiak ezin du Freerunnerra itzali, botoia sakatzeak eten/itzuli funtzioak beteko ditu, baina ez itzaltzekoa. Gutxienez bi eratara itzal dezakezu Freerunnerra, alde batetik, <tt>ssh</tt> aginduaren bidez FreeRunnerrera konektatu usb kable bidez lotutako PC batetik (edo wifi konexio bidez) eta itzaltzeko agindua eragin dezakezu: <br>
# shutdown -h now<br>
Itzaltzeko beste era bat ere badago, askoz ere sinpleagoa da bigarren era hau (baina ez hain dotorea): bateria kendu eta itzali egingo da, a zer erremedio!.
Firmwarea ondo kopiatu dela ikusteko, ssh konexio bidez <tt>mickeyterm</tt> erabil daiteke modemarekin komunikatzeko eta bertsioa begiratzeko</li>
</ol>
====OHARRA====

Zure PCak mikroSD txartelak irakurtzeko gailurik ez badauka, mikroSD txartelera <tt>dd</tt> agindu bidez moko11 irudiaren kopia FreeRunner gailuan bertan egin dezakezu: instalatu <tt>task-base-smbfs</tt>, mikroSD txartela desmuntatu, horretarako <tt>umount /media/card</tt> agindua erabili (partizio gehiago baleuzka eta horiek ere muntatuta baleude guztiak desmuntatu). Une honetan bi aukera dauzkazu gutxienez:
<ol>
<li> Zure PCan dagoen irudia daukan direktorioa FreeRunnerreko fitxategi sisteman muntatu dezakezu, eta ondoren, <tt>dd</tt> agindu bidez zuzenean FreeRunnerrean dagoen mikroSD txartelera kopia dezakezu. Prozesu horrek 12 minutu inguru iraun ditzake. Eragiketa hau FreeRunnerreko shell batetik egin behar da.
</li>
<li>Alderantziz ere jardun daiteke, alegia, PCko shell batean lan egin dezakezu, horretarako, lehenengo FreeRunnerrean mikroSD txartela desmuntatu:<br>
root@om-gta02 ~ $ umount /media/card<br>
Eta ondoren, PCko shell batean (usb edo wifi konexioa eskatzen du honek):<br>
scp flash-moko11-2.image root@192.168.0.202:/dev/mmcblk0
</li>
</ol>
Prozesu horiek azkartu egin daitezke, irudia gzip bidez konprimituz makinatik makinara pasa beharreko informazio-kopurua gutxitu egin daiteke, eta deskonprimitzeko aginduari zuzenean mikroSD txartelera kopiatzeko esan diezaiokegu:

% gzip -d < flash-moko11-2.image.gz > /dev/mmcblk0

Agindu honenkin, eta FreeRunnerreko fitxategi sisteman nahikoa leku libre edukiz gero, ez dogo PCa erabili beharrik, alegia, konprimitutako fitxategia FreeRunnerrean bertan jaso daiteke, eta deskonprimitu mikroSD txartelera. Baina 92MB libre behar ditu gutxi gora behera.

====BIGARREN OHARRA====

Abiorako [[Qi]] instalatuta eduki ala ez (ikusi aurrekoa), pizterakoan NOR menuraino joan behar da (horretarako AUX botoia sakatuta daukazun bitartean pizteko botoia sakatu) eta bertan "Boot from microSD (fat/ext2)" aukeratu behar duzu instalazio prozesua abiatu dadin. (per DocScrutinizer in #openmoko). '''Ez''' utzi Qi abiarazleari mikroSDko partizioa izan dadin sistemaren abioa. Antzekoa dirudien arren, berdez idatzitako "d_o_n_e" ez da azalduko eta ondorioz egin beharrekoa ez du egingo.

You can confirm the firmware version number using the [[OpenmokoFramework/mickeyterm|mickeyterm]] (cmd: "AT+CGMR"). In SHR-Settings, Phone/Modem Information will supply the same number.

===Installing a distribution===

This section describes how to install a distribution on the internal flash memory of the Neo FreeRunner. If you want to install it on the memory card please refer to the guide provided by the distribution.

For installing a new distribution you will need two files, a root file system (rootfs) image and a kernel image. The root file system image usually ends with ".jffs2", and the kernel image ends with ".uimage.bin". You can get these files from http://wiki.openmoko.org/wiki/Download . Use the program NeoTool to install the distribution on your FreeRunner. The flashing process can take up to 15 minutes for a ~70MB image. It is also wise to make sure that your Neo has enough battery charge prior to flashing.

When flashing succeeds the following will be shown:

<pre>
status(0) = No error condition is present
Done!
</pre>

[[Category:Manuals]]

Neo FreeRunner/eu

2010-01-27T23:41:19Z

Joseba:

{{Languages|Neo FreeRunner}}
{{Neo FreeRunner Menu}}

'''Neo FreeRunner''' telefonoa Openmoko softwarea exekutatzeko asmoz sortutako bigarrena da. Lehenengoa [[Neo 1973]] izenez ezagutzen da eta beragandik eratorri da Neo FreeRunnerra.

== Datu teknikoak ==

* Bereizmen handiko ukimenezko pantaila: 2.84” (43mm x 58mm) 480x640 pixel
* 128MB SDRAM memoria
* 256 MBeko flash memoria integratua (mikroSD edo mkroSDHC txartelaz handitu daiteke memoria)
* microSD gunea, 16GBerainoko SDHC (Secure Digital High Capacity) txartelak onartzen dituena ([[Supported microSD cards|Onartutako mikroSD txartelak]])
* Barne [[Neo FreeRunner GPS|GPS]] modulua
* Bluetootha
* 802.11 b/g [[Neo FreeRunner Wifi|WiFia]]
* 400Mhz ARM prozesagailua
* 2 3D azelerometro
* 2 LED, bakoitzak estalkian edo armazoiko ertzean dauden botoi bana argitzen du (bietako batek, pizteko botoiaren azpikoak, bi kolore dauzka [urdin/laranja] eta besteak, AUX botoiarekin doanak, kolore gorria dauka.
* Tri-band GSM eta GPRS
* USB Host funtzioa 500mAko argi-indarrekoa, honen bidez USB gailuei indarra eman dakieke, baina era berean, FreeRunnerraren bateria azkarrago agortu araziko du.

'''Bertsioak''': Neo FreeRunnerra bi bertsiotan eskaintzen da, bata Ipar Ameriketako GSM bandarako (850/1800/1900 Mhz), eta besteamundoko beste eremuetarako GSM bandarentzat (900/1800/1900 Mhz). Besterik esaten ez baduzu, lekuan lekurara egokitutako telefonoa salduko dizu banatzaileak.

FreeRunnerraren hardware espezifikazioen eta osagaien zerrenda osotua [[Neo FreeRunner Hardware|Neo FreeRunner Hardwarea]] orrian aurkituko duzu.

Aurreko telefonoaren, [[Neo 1973| Neo 1973 gailuaren]] eta Neo FreeRunnerraren arteko konparazioa [[Neo 1973 vs Neo FreeRunner]] orrian ikusiko duzu.

== Neo FreeRunner berria erosteko==
[[Image:Freerunner02.gif|200px|right]]

[[distributors|Banatzileengana]] jotzea da Neo FreeRunner berria erosteko aukera onena. Gailuak dakarren softwarea dela-eta, gaur egun garatzaileek eta erabiltzaile aurreratuek ondo erabili ahal izango dute telefonoa, baina erabiltzaile orokorrek, aplikazio multzo egokiarekin, oinarrizko erabilera egin ahal izango dute. Posta elektroniko bidezko ohar eta jakinarazpenak [http://lists.openmoko.org/mailman/listinfo/announce announce mailing list] helbidean lor daitezke. Sarri egiten diren galderei buruzko erantzunak [[FAQ]] orrietan aurkituko dituzu.

== Erabilerak eta erabiltzaileak ==

Neo FreeRunner gailua Linux sistema eragilean oinarritutako eta ukimenezko pantaila duen telefono dotorea da. Bere xedea erabilera orokorrekoa izatea da, bai eta linux sistemen erabiltzaile eta software garatzaileentzat ere.

Linux erabiltzaileek eta software garatzaileek asko estimatuko dute Neo FreeRunnerrak eskaintzen dien askatasun osoa, bai softwarea erabiltzerakoan bai eta FreeRunnerrerako aplikazio berriak garatzerakoaren ere.

Telefono erabiltzaileek bere berezitasuna eta errendimendua estimatu dezakete, eta batez ere, erabili ahal izango duen aplikazio aukera zabala. Gainera, gero eta aplikazio gehiago agertzen eta garatzen ari dira. Horien bidez mugikorraren hardwarearen erabilera osoa egin ahal izango du edozein erabiltzailek, eta bere beharretara egokitu ahal izango ditu aplikazioak. Merkaturatu zenez geroztik, softwarearen aurrerakada eta hobekuntzak azkar hasi dira, neurri handi batean OpenMoko taldea eta gero eta komunitate handiagoa elkarlanean ari direlako.

== Zenbaterainoko erabilgarritasuna dauka? ==

Banaketa gehienekin FreeRunnerra telefono mugikor moduan erabilgarri dago. Hala ere, hainbat arazotxo sortu izan dira eta konpondu egin dira, eta erabilgarritasun aurreratu batzuk ere falta zaizkio, baina azkar aurreratzen du garapenak. GPS moduan ere erabil daiteke FreeRunnerra, horretarako hainbat aplikazio garatu baitira; ibilbideak jasotzeko edota ibilbideak kalkula ditzaketen aplikazioak erabilgarri daude banaketetan. Informazio gehiago nahi izan ezkero ikusi [[Distributions#Features by distribution/release_target|banaketen orriak]].

Arren ikusi [[FreeRunner: Selected Blogs and Articles|aukeratutako blog eta artikuluak]] ikuspegi eta gainbegirada gehiago nahi izan ezkero. [[Neo FreeRunner Hardware Issues|hardware arazoak]] orria ere interesgarria izan daiteke.

== Gehiago ikusteko ==
*[[Manuals/Neo FreeRunner/eu|FreeRunnerrarekin hasteko]]
*[[FAQ]]

== Kanpoko estekak ==

*[http://www.guruworkshop.com/omoko 3D model of Neo FreeRunner, click and drag to rotate]

[[Category:Neo FreeRunner Hardware| ]]

Neo FreeRunner/eu

2010-01-27T23:39:09Z

Joseba:

{{Languages|Neo FreeRunner}}
{{Neo FreeRunner Menu}}

'''Neo FreeRunner''' telefonoa Openmoko softwarea exekutatzeko asmoz sortutako bigarrena da. Lehenengoa [[Neo 1973]] izenez ezagutzen da eta beragandik eratorri da Neo FreeRunnerra.

== Datu teknikoak ==

* Bereizmen handiko ukimenezko pantaila: 2.84” (43mm x 58mm) 480x640 pixel
* 128MB SDRAM memoria
* 256 MBeko flash memoria integratua (mikroSD edo mkroSDHC txartelaz handitu daiteke memoria)
* microSD gunea, 16GBerainoko SDHC (Secure Digital High Capacity) txartelak onartzen dituena ([[Supported microSD cards|Onartutako mikroSD txartelak]])
* Barne [[Neo FreeRunner GPS|GPS]] modulua
* Bluetootha
* 802.11 b/g [[Neo FreeRunner Wifi|WiFia]]
* 400Mhz ARM prozesagailua
* 2 3D azelerometro
* 2 LED, bakoitzak estalkian edo armazoiko ertzean dauden botoi bana argitzen du (bietako batek, pizteko botoiaren azpikoak, bi kolore dauzka [urdin/laranja] eta besteak, AUX botoiarekin doanak, kolore gorria dauka.
* Tri-band GSM eta GPRS
* USB Host funtzioa 500mAko argi-indarrekoa, honen bidez USB gailuei indarra eman dakieke, baina era berean, FreeRunnerraren bateria azkarrago agortu araziko du.

'''Bertsioak''': Neo FreeRunnerra bi bertsiotan eskaintzen da, bata Ipar Ameriketako GSM bandarako (850/1800/1900 Mhz), eta besteamundoko beste eremuetarako GSM bandarentzat (900/1800/1900 Mhz). Besterik esaten ez baduzu, lekuan lekurara egokitutako telefonoa salduko dizu banatzaileak.

FreeRunnerraren hardware espezifikazioen eta osagaien zerrenda osotua [[Neo FreeRunner Hardware|Neo FreeRunner Hardwarea]] orrian aurkituko duzu.

Aurreko telefonoaren, [[Neo 1973| Neo 1973 gailuaren]] eta Neo FreeRunnerraren arteko konparazioa [[Neo 1973 vs Neo FreeRunner]] orrian ikusiko duzu.

== Neo FreeRunner berria erosteko==
[[Image:Freerunner02.gif|200px|right]]

[[distributors|Banatzileengana]] jotzea da Neo FreeRunner berria erosteko aukera onena. Gailuak dakarren softwarea dela-eta, gaur egun garatzaileek eta erabiltzaile aurreratuek ondo erabili ahal izango dute telefonoa, baina erabiltzaile orokorrek, aplikazio multzo egokiarekin, oinarrizko erabilera egin ahal izango dute. Posta elektroniko bidezko ohar eta jakinarazpenak [http://lists.openmoko.org/mailman/listinfo/announce announce mailing list] helbidean lor daitezke. Sarri egiten diren galderei buruzko erantzunak [[FAQ]] orrietan aurkituko dituzu.

== Erabilerak eta erabiltzaileak ==

Neo FreeRunner gailua Linux sistema eragilean oinarritutako eta ukimenezko pantaila duen telefono dotorea da. Bere xedea erabilera orokorrekoa izatea da, bai eta linux sistemen erabiltzaile eta software garatzaileentzat ere.

Linux erabiltzaileek eta software garatzaileek asko estimatuko dute Neo FreeRunnerrak eskaintzen dien askatasun osoa, bai softwarea erabiltzerakoan bai eta FreeRunnerrerako aplikazio berriak garatzerakoaren ere.

Telefono erabiltzaileek bere berezitasuna eta errendimendua estimatu dezakete, eta batez ere, erabili ahal izango duen aplikazio aukera zabala. Gainera, gero eta aplikazio gehiago agertzen eta garatzen ari dira. Horien bidez mugikorraren hardwarearen erabilera osoa egin ahal izango du edozein erabiltzailek, eta bere beharretara egokitu ahal izango ditu aplikazioak. Merkaturatu zenez geroztik, softwarearen aurrerakada eta hobekuntzak azkar hasi dira, neurri handi batean OpenMoko taldea eta gero eta komunitate handiagoa elkarlanean ari direlako.

== Zenbaterainoko erabilgarritasuna dauka? ==

Banaketa gehienekin FreeRunnerra telefono mugikor moduan erabilgarri dago. Hala ere, hainbat arazotxo sortu izan dira eta konpondu egin dira, eta erabilgarritasun aurreratu batzuk ere falta zaizkio, baina azkar aurreratzen du garapenak. GPS moduan ere erabil daiteke FreeRunnerra, horretarako hainbat aplikazio garatu baitira; ibilbideak jasotzeko edota ibilbideak kalkula ditzaketen aplikazioak erabilgarri daude banaketetan. Informazio gehiago nahi izan ezkero ikusi [[Distributions#Features by distribution/release_target|banaketen orriak]].

Arren ikusi [[FreeRunner: Selected Blogs and Articles|aukeratutako blog eta artikuluak]] ikuspegi eta gainbegirada gehiago nahi izan ezkero. [[Neo FreeRunner Hardware Issues|hardware arazoak]] orria ere interesgarria izan daiteke.

== Gehiago ikusteko ==
*[[Getting Started with your Neo FreeRunner/eu|FreeRunnerrarekin hasteko]]
*[[FAQ]]

== Kanpoko estekak ==

*[http://www.guruworkshop.com/omoko 3D model of Neo FreeRunner, click and drag to rotate]

[[Category:Neo FreeRunner Hardware| ]]

Neo FreeRunner/eu

2010-01-27T23:33:25Z

Joseba:

{{Languages|Neo FreeRunner}}
{{Neo FreeRunner Menu}}

'''Neo FreeRunner''' telefonoa Openmoko softwarea exekutatzeko asmoz sortutako bigarrena da. Lehenengoa [[Neo 1973]] izenez ezagutzen da eta beragandik eratorri da Neo FreeRunnerra.

== Datu teknikoak ==

* Bereizmen handiko ukimenezko pantaila: 2.84” (43mm x 58mm) 480x640 pixel
* 128MB SDRAM memoria
* 256 MBeko flash memoria integratua (mikroSD edo mkroSDHC txartelaz handitu daiteke memoria)
* microSD gunea, 16GBerainoko SDHC (Secure Digital High Capacity) txartelak onartzen dituena ([[Supported microSD cards|Onartutako mikroSD txartelak]])
* Barne [[Neo FreeRunner GPS|GPS]] modulua
* Bluetootha
* 802.11 b/g [[Neo FreeRunner Wifi|WiFia]]
* 400Mhz ARM prozesagailua
* 2 3D azelerometro
* 2 LED, bakoitzak estalkian edo armazoiko ertzean dauden botoi bana argitzen du (bietako batek, pizteko botoiaren azpikoak, bi kolore dauzka [urdin/laranja] eta besteak, AUX botoiarekin doanak, kolore gorria dauka.
* Tri-band GSM eta GPRS
* USB Host funtzioa 500mAko argi-indarrekoa, honen bidez USB gailuei indarra eman dakieke, baina era berean, FreeRunnerraren bateria azkarrago agortu araziko du.

'''Bertsioak''': Neo FreeRunnerra bi bertsiotan eskaintzen da, bata Ipar Ameriketako GSM bandarako (850/1800/1900 Mhz), eta besteamundoko beste eremuetarako GSM bandarentzat (900/1800/1900 Mhz). Besterik esaten ez baduzu, lekuan lekurara egokitutako telefonoa salduko dizu banatzaileak.

FreeRunnerraren hardware espezifikazioen eta osagaien zerrenda osotua [[Neo FreeRunner Hardware|Neo FreeRunner Hardwarea]] orrian aurkituko duzu.

Aurreko telefonoaren, [[Neo 1973| Neo 1973 gailuaren]] eta Neo FreeRunnerraren arteko konparazioa [[Neo 1973 vs Neo FreeRunner]] orrian ikusiko duzu.

== Neo FreeRunner berria erosteko==
[[Image:Freerunner02.gif|200px|right]]

[[distributors|Banatzileengana]] jotzea da Neo FreeRunner berria erosteko aukera onena. Gailuak dakarren softwarea dela-eta, gaur egun garatzaileek eta erabiltzaile aurreratuek ondo erabili ahal izango dute telefonoa, baina erabiltzaile orokorrek, aplikazio multzo egokiarekin, oinarrizko erabilera egin ahal izango dute. Posta elektroniko bidezko ohar eta jakinarazpenak [http://lists.openmoko.org/mailman/listinfo/announce announce mailing list] helbidean lor daitezke. Sarri egiten diren galderei buruzko erantzunak [[FAQ]] orrietan aurkituko dituzu.

== Erabilerak eta erabiltzaileak ==

Neo FreeRunner gailua Linux sistema eragilean oinarritutako eta ukimenezko pantaila duen telefono dotorea da. Bere xedea erabilera orokorrekoa izatea da, bai eta linux sistemen erabiltzaile eta software garatzaileentzat ere.

Linux erabiltzaileek eta software garatzaileek asko estimatuko dute Neo FreeRunnerrak eskaintzen dien askatasun osoa, bai softwarea erabiltzerakoan bai eta FreeRunnerrerako aplikazio berriak garatzerakoaren ere.

Telefono erabiltzaileek bere berezitasuna eta errendimendua estimatu dezakete, eta batez ere, erabili ahal izango duen aplikazio aukera zabala. Gainera, gero eta aplikazio gehiago agertzen eta garatzen ari dira. Horien bidez mugikorraren hardwarearen erabilera osoa egin ahal izango du edozein erabiltzailek, eta bere beharretara egokitu ahal izango ditu aplikazioak. Merkaturatu zenez geroztik, softwarearen aurrerakada eta hobekuntzak azkar hasi dira, neurri handi batean OpenMoko taldea eta gero eta komunitate handiagoa elkarlanean ari direlako.

== Zenbaterainoko erabilgarritasuna dauka? ==

Banaketa gehienekin FreeRunnerra telefono mugikor moduan erabilgarri dago. Hala ere, hainbat arazotxo sortu izan dira eta konpondu egin dira, eta erabilgarritasun aurreratu batzuk ere falta zaizkio, baina azkar aurreratzen du garapenak. GPS moduan ere erabil daiteke FreeRunnerra, horretarako hainbat aplikazio garatu baitira; ibilbideak jasotzeko edota ibilbideak kalkula ditzaketen aplikazioak erabilgarri daude banaketetan. Informazio gehiago nahi izan ezkero ikusi [[Distributions#Features by distribution/release_target|banaketen orriak]].

Arren ikusi [[FreeRunner: Selected Blogs and Articles|aukeratutako blog eta artikuluak]] ikuspegi eta gainbegirada gehiago nahi izan ezkero. [[Neo FreeRunner Hardware Issues|hardware arazoak]] orria ere interesgarria izan daiteke.

== Gehiago ikusteko ==
*[[Getting Started with your Neo FreeRunner|FreeRunnerrarekin hasteko]]
*[[FAQ]]

== Kanpoko estekak ==

*[http://www.guruworkshop.com/omoko 3D model of Neo FreeRunner, click and drag to rotate]

[[Category:Neo FreeRunner Hardware| ]]

Neo FreeRunner/eu

2010-01-27T23:07:33Z

Joseba:

{{Languages|Neo FreeRunner}}
{{Neo FreeRunner Menu}}

'''Neo FreeRunner''' telefonoa Openmoko softwarea exekutatzeko asmoz sortutako bigarrena da. Lehenengoa [[Neo 1973]] izenez ezagutzen da eta beragandik eratorri da Neo FreeRunnerra.

== Datu teknikoak ==

* Bereizmen handiko ukimenezko pantaila: 2.84” (43mm x 58mm) 480x640 pixel
* 128MB SDRAM memoria
* 256 MBeko flash memoria integratua (mikroSD edo mkroSDHC txartelaz handitu daiteke memoria)
* microSD gunea, 16GBerainoko SDHC (Secure Digital High Capacity) txartelak onartzen dituena ([[Supported microSD cards|Onartutako mikroSD txartelak]])
* Barne [[Neo FreeRunner GPS|GPS]] modulua
* Bluetootha
* 802.11 b/g [[Neo FreeRunner Wifi|WiFia]]
* 400Mhz ARM prozesagailua
* 2 3D azelerometro
* 2 LED, bakoitzak estalkian edo armazoiko ertzean dauden botoi bana argitzen du (bietako batek, pizteko botoiaren azpikoak, bi kolore dauzka [urdin/laranja] eta besteak, AUX botoiarekin doanak, kolore gorria dauka.
* Tri-band GSM eta GPRS
* USB Host funtzioa 500mAko argi-indarrekoa, honen bidez USB gailuei indarra eman dakieke, baina era berean, FreeRunnerraren bateria azkarrago agortu araziko du.

'''Bertsioak''': Neo FreeRunnerra bi bertsiotan eskaintzen da, bata Ipar Ameriketako GSM bandarako (850/1800/1900 Mhz), eta besteamundoko beste eremuetarako GSM bandarentzat (900/1800/1900 Mhz). Besterik esaten ez baduzu, lekuan lekurara egokitutako telefonoa salduko dizu banatzaileak.

FreeRunnerraren hardware espezifikazioen eta osagaien zerrenda osotua [[Neo FreeRunner Hardware|Neo FreeRunner Hardwarea]] orrian aurkituko duzu.

Aurreko telefonoaren, [[Neo 1973| Neo 1973 gailuaren]] eta Neo FreeRunnerraren arteko konparazioa [[Neo 1973 vs Neo FreeRunner]] orrian ikusiko duzu.

== Neo FreeRunner berria erosteko==
[[Image:Freerunner02.gif|200px|right]]

[[distributors|Banatzileengana]] jotzea da Neo FreeRunner berria erosteko aukera onena. Gailuak dakarren softwarea dela-eta, gaur egun garatzaileek eta erabiltzaile aurreratuek ondo erabili ahal izango dute telefonoa, baina erabiltzaile orokorrek, aplikazio multzo egokiarekin, oinarrizko erabilera egin ahal izango dute. Posta elektroniko bidezko ohar eta jakinarazpenak [http://lists.openmoko.org/mailman/listinfo/announce announce mailing list] helbidean lor daitezke. Sarri egiten diren galderei buruzko erantzunak [[FAQ]] orrietan aurkituko dituzu.

== Erabilerak eta erabiltzaileak ==

Neo FreeRunner gailua Linux sistema eragilean oinarritutako eta ukimenezko pantaila duen telefono dotorea da. Bere xedea erabilera orokorrekoa izatea da, bai eta linux sistemen erabiltzaile eta software garatzaileentzat ere.

Linux erabiltzaileek eta software garatzaileek asko estimatuko dute Neo FreeRunnerrak eskaintzen dien askatasun osoa, bai softwarea erabiltzerakoan bai eta FreeRunnerrerako aplikazio berriak garatzerakoaren ere.

Telefono erabiltzaileek General phone users will eventually appreciate the high spec and performance of the phone and the wide range of free software packages expected to emerge. These will allow users to make the maximum use of the hardware and tailor it to their particular needs. Since launch, the pace of software tweaks and improvements has increased as both the Openmoko team developers and the wider community work together.

== How usable is it? ==

With most distributions the FreeRunner is working as a reliable phone. However it still has usability issues and many advanced features are still missing. (For example with SHR, the most used distribution, the phone keeps ringing for a second after a call has been accepted) For more information see [[Distributions#Features by distribution/release_target|distributions]].

Please see the [[FreeRunner: Selected Blogs and Articles]] to get more reviews. The [[Neo FreeRunner Hardware Issues]] page may also be of interest.

== See also ==
*[[Getting Started with your Neo FreeRunner]]
*[[FAQ]]

== External links ==

*[http://www.guruworkshop.com/omoko 3D model of Neo FreeRunner, click and drag to rotate]

[[Category:Neo FreeRunner Hardware| ]]

Neo FreeRunner/eu

2010-01-27T22:48:58Z

Joseba:

{{Languages|Neo FreeRunner}}
{{Neo FreeRunner Menu}}

'''Neo FreeRunner''' telefonoa Openmoko softwarea exekutatzeko asmoz sortutako bigarrena da. Lehenengoa [[Neo 1973]] izenez ezagutzen da eta beragandik eratorri da Neo FreeRunnerra.

== Datu teknikoak ==

* Bereizmen handiko ukimenezko pantaila: 2.84” (43mm x 58mm) 480x640 pixel
* 128MB SDRAM memoria
* 256 MBeko flash memoria integratua (mikroSD edo mkroSDHC txartelaz handitu daiteke memoria)
* microSD gunea, 16GBerainoko SDHC (Secure Digital High Capacity) txartelak onartzen dituena ([[Supported microSD cards|Onartutako mikroSD txartelak]])
* Barne [[Neo FreeRunner GPS|GPS]] modulua
* Bluetootha
* 802.11 b/g [[Neo FreeRunner Wifi|WiFia]]
* 400Mhz ARM prozesagailua
* 2 3D azelerometro
* 2 LED, bakoitzak estalkian edo armazoiko ertzean dauden botoi bana argitzen du (bietako batek, pizteko botoiaren azpikoak, bi kolore dauzka [urdin/laranja] eta besteak, AUX botoiarekin doanak, kolore gorria dauka.
* Tri-band GSM eta GPRS
* USB Host funtzioa 500mAko argi-indarrekoa, honen bidez USB gailuei indarra eman dakieke, baina era berean, FreeRunnerraren bateria azkarrago agortu araziko du.

'''Bertsioak''': Neo FreeRunnerra bi bertsiotan eskaintzen da, bata Ipar Ameriketako GSM bandarako (850/1800/1900 Mhz), eta besteamundoko beste eremuetarako GSM bandarentzat (900/1800/1900 Mhz). Besterik esaten ez baduzu, lekuan lekurara egokitutako telefonoa salduko dizu banatzaileak.

FreeRunnerraren hardware espezifikazioen eta osagaien zerrenda osotua [[Neo FreeRunner Hardware|Neo FreeRunner Hardwarea]] orrian aurkituko duzu.

Aurreko telefonoaren, [[Neo 1973| Neo 1973 gailuaren]] eta Neo FreeRunnerraren arteko konparazioa [[Neo 1973 vs Neo FreeRunner]] orrian ikusiko duzu.

== Neo FreeRunner erosteko==
[[Image:Freerunner02.gif|200px|right]]

[[distributors|Banatzileengana]] jotzea da Neo FreeRunner berria erosteko aukera onena. Gailuak dakarren softwarea dela-eta, gaur egun garatzaileek eta erabiltzaile aurreratuek ondo erabili ahal izango dute telefonoa, baina erabiltzaile orokorrek, aplikazio multzo egokiarekin, oinarrizko erabilera egin ahal izango dute. Posta elektroniko bidezko ohar eta jakinarazpenak [http://lists.openmoko.org/mailman/listinfo/announce announce mailing list] helbidean lor daitezke. Sarri egiten diren galderei buruzko erantzunak [[FAQ]] orrietan aurkituko dituzu.

== Erabilerak eta erabiltzaileak ==

The Neo FreeRunner is a Linux-based touch screen smart phone ultimately aimed at general consumer use as well as Linux desktop users and software developers.

Linux users and software developers will appreciate the total freedom they have to use and design software for the FreeRunner.

General phone users will eventually appreciate the high spec and performance of the phone and the wide range of free software packages expected to emerge. These will allow users to make the maximum use of the hardware and tailor it to their particular needs. Since launch, the pace of software tweaks and improvements has increased as both the Openmoko team developers and the wider community work together.

== How usable is it? ==

With most distributions the FreeRunner is working as a reliable phone. However it still has usability issues and many advanced features are still missing. (For example with SHR, the most used distribution, the phone keeps ringing for a second after a call has been accepted) For more information see [[Distributions#Features by distribution/release_target|distributions]].

Please see the [[FreeRunner: Selected Blogs and Articles]] to get more reviews. The [[Neo FreeRunner Hardware Issues]] page may also be of interest.

== See also ==
*[[Getting Started with your Neo FreeRunner]]
*[[FAQ]]

== External links ==

*[http://www.guruworkshop.com/omoko 3D model of Neo FreeRunner, click and drag to rotate]

[[Category:Neo FreeRunner Hardware| ]]

Neo FreeRunner/eu

2010-01-27T22:20:30Z

Joseba:

{{Languages|Neo FreeRunner}}
{{Neo FreeRunner Menu}}

'''Neo FreeRunner''' telefonoa Openmoko softwarea exekutatzeko asmoz sortutako bigarrena da. Lehenengoa [[Neo 1973]] izenez ezagutzen da eta beragandik eratorri da Neo FreeRunnerra.

== Datu teknikoak ==

* Bereizmen handiko ukimenezko pantaila: 2.84” (43mm x 58mm) 480x640 pixel
* 128MB SDRAM memoria
* 256 MBeko flash memoria integratua (mikroSD edo mkroSDHC txartelaz handitu daiteke memoria)
* microSD gunea, 16GBerainoko SDHC (Secure Digital High Capacity) txartelak onartzen dituena ([[Supported microSD cards|Onartutako mikroSD txartelak]])
* Barne [[Neo FreeRunner GPS|GPS]] modulua
* Bluetootha
* 802.11 b/g [[Neo FreeRunner Wifi|WiFia]]
* 400Mhz ARM prozesagailua
* 2 3D azelerometro
* 2 LED, bakoitzak estalkian edo armazoiko ertzean dauden botoi bana argitzen du (bietako batek, pizteko botoiaren azpikoak, bi kolore dauzka [urdin/laranja] eta besteak, AUX botoiarekin doanak kolore [gorria] dauka.
* Tri-band GSM eta GPRS
* USB Host funtzioa 500mAko argi-indarrekoa, honen bidez USB gailuei indarra eman dakieke, baina era berean, FreeRunnerraren bateria azkarrago agortu araziko du.

'''Bertsioak''': Neo FreeRunnerra bi bertsiotan eskaintzen da, bata Ipar Ameriketako GSM bandarako (850/1800/1900 Mhz), eta besteamundoko beste eremuetarako GSM bandarentzat (900/1800/1900 Mhz). Besterik esaten ez baduzu, lekuan lekurara egokitutako telefonoa salduko dizu banatzaileak.

FreeRunnerraren hardware espezifikazioen eta osagaien zerrenda osotua [[Neo FreeRunner Hardware|Neo FreeRunner Hardwarea]] orrian aurkituko duzu.

Aurreko telefonoaren, [[Neo 1973| Neo 1973 gailuaren]] eta Neo FreeRunnerraren arteko konparazioa [[Neo 1973 vs Neo FreeRunner]] orrian ikusiko duzu.

== Getting the Neo FreeRunner ==
[[Image:Freerunner02.gif|200px|right]]

The FreeRunner can be purchased from a [[distributors|distributor]]. The software available on the phone makes it suitable for power users and developers only -- it is not yet ready for the general consumer. Email announcements are found on the [http://lists.openmoko.org/mailman/listinfo/announce announce mailing list]. For frequently asked questions please check [[FAQ]].

== Intended use and users ==

The Neo FreeRunner is a Linux-based touch screen smart phone ultimately aimed at general consumer use as well as Linux desktop users and software developers.

Linux users and software developers will appreciate the total freedom they have to use and design software for the FreeRunner.

General phone users will eventually appreciate the high spec and performance of the phone and the wide range of free software packages expected to emerge. These will allow users to make the maximum use of the hardware and tailor it to their particular needs. Since launch, the pace of software tweaks and improvements has increased as both the Openmoko team developers and the wider community work together.

== How usable is it? ==

With most distributions the FreeRunner is working as a reliable phone. However it still has usability issues and many advanced features are still missing. (For example with SHR, the most used distribution, the phone keeps ringing for a second after a call has been accepted) For more information see [[Distributions#Features by distribution/release_target|distributions]].

Please see the [[FreeRunner: Selected Blogs and Articles]] to get more reviews. The [[Neo FreeRunner Hardware Issues]] page may also be of interest.

== See also ==
*[[Getting Started with your Neo FreeRunner]]
*[[FAQ]]

== External links ==

*[http://www.guruworkshop.com/omoko 3D model of Neo FreeRunner, click and drag to rotate]

[[Category:Neo FreeRunner Hardware| ]]

Neo FreeRunner/eu

2010-01-27T22:04:52Z

Joseba:

{{Languages|Neo FreeRunner}}
{{Neo FreeRunner Menu}}

'''Neo FreeRunner''' telefonoa Openmoko softwarea exekutatzeko asmoz sortutako bigarrena da. Lehenengoa [[Neo 1973]] izenez ezagutzen da eta beragandik eratorri da Neo FreeRunnerra.

== Specifications ==

* Bereizmen handiko ukimenezko pantaila: 2.84” (43mm x 58mm) 480x640 pixel
* 128MB SDRAM memoria
* 256 MBeko flash memoria integratua (mikroSD edo mkroSDHC txartelaz handitu daiteke memoria)
* microSD gunea, 16GBerainoko SDHC (Secure Digital High Capacity) txartelak onartzen dituena ([[Supported microSD cards|Onartutako mikroSD txartelak]])
* Barne [[Neo FreeRunner GPS|GPS]] modulua
* Bluetootha
* 802.11 b/g [[Neo FreeRunner Wifi|WiFia]]
* 400Mhz ARM prozesagailua
* 2 3D azelerometro
* 2 LEDs illuminating the two buttons on the rim of the case (one bicolor [blue|orange] behind the power button, 1 unicolor [red] behind the aux button)
* Tri-band GSM and GPRS
* USB Host function with 500mA power, allowing you to power USB devices for short periods (will drain the FreeRunner battery faster)

'''Versions''': The Neo FreeRunner is available in two versions, one for the GSM bands of North America (850/1800/1900 Mhz), and one for the GSM bands in the rest of the world (900/1800/1900 Mhz). Unless you explicitly discuss this, a local reseller may by default send you the version appropriate to the distributors location.

A full list of the hardware specs and components of the Neo FreeRunner can be found at [[Neo FreeRunner Hardware]].

A comparison between [[Neo 1973]] and Neo FreeRunner is available at [[Neo 1973 vs Neo FreeRunner]].

== Getting the Neo FreeRunner ==
[[Image:Freerunner02.gif|200px|right]]

The FreeRunner can be purchased from a [[distributors|distributor]]. The software available on the phone makes it suitable for power users and developers only -- it is not yet ready for the general consumer. Email announcements are found on the [http://lists.openmoko.org/mailman/listinfo/announce announce mailing list]. For frequently asked questions please check [[FAQ]].

== Intended use and users ==

The Neo FreeRunner is a Linux-based touch screen smart phone ultimately aimed at general consumer use as well as Linux desktop users and software developers.

Linux users and software developers will appreciate the total freedom they have to use and design software for the FreeRunner.

General phone users will eventually appreciate the high spec and performance of the phone and the wide range of free software packages expected to emerge. These will allow users to make the maximum use of the hardware and tailor it to their particular needs. Since launch, the pace of software tweaks and improvements has increased as both the Openmoko team developers and the wider community work together.

== How usable is it? ==

With most distributions the FreeRunner is working as a reliable phone. However it still has usability issues and many advanced features are still missing. (For example with SHR, the most used distribution, the phone keeps ringing for a second after a call has been accepted) For more information see [[Distributions#Features by distribution/release_target|distributions]].

Please see the [[FreeRunner: Selected Blogs and Articles]] to get more reviews. The [[Neo FreeRunner Hardware Issues]] page may also be of interest.

== See also ==
*[[Getting Started with your Neo FreeRunner]]
*[[FAQ]]

== External links ==

*[http://www.guruworkshop.com/omoko 3D model of Neo FreeRunner, click and drag to rotate]

[[Category:Neo FreeRunner Hardware| ]]

Neo FreeRunner/eu

2010-01-27T21:53:14Z

Joseba: New page: {{Languages|Neo FreeRunner}} {{Neo FreeRunner Menu}} The '''Neo FreeRunner''' is the second phone designed to run Openmoko software and is the direct descendant of the earlier [[Neo 1973]...

{{Languages|Neo FreeRunner}}
{{Neo FreeRunner Menu}}

The '''Neo FreeRunner''' is the second phone designed to run Openmoko software and is the direct descendant of the earlier [[Neo 1973]].

== Specifications ==

* High resolution touch screen 2.84” (43mm x 58mm) 480x640 pixels
* 128MB SDRAM memory
* 256 MB integrated flash memory (expandable with microSD or microSDHC card)
* microSD slot supporting up to 16GB SDHC (Secure Digital High Capacity) cards ([[Supported microSD cards]])
* Internal [[Neo FreeRunner GPS|GPS]] module
* Bluetooth
* 802.11 b/g [[Neo FreeRunner Wifi|WiFi]]
* 400Mhz ARM processor
* 2 3D accelerometers
* 2 LEDs illuminating the two buttons on the rim of the case (one bicolor [blue|orange] behind the power button, 1 unicolor [red] behind the aux button)
* Tri-band GSM and GPRS
* USB Host function with 500mA power, allowing you to power USB devices for short periods (will drain the FreeRunner battery faster)

'''Versions''': The Neo FreeRunner is available in two versions, one for the GSM bands of North America (850/1800/1900 Mhz), and one for the GSM bands in the rest of the world (900/1800/1900 Mhz). Unless you explicitly discuss this, a local reseller may by default send you the version appropriate to the distributors location.

A full list of the hardware specs and components of the Neo FreeRunner can be found at [[Neo FreeRunner Hardware]].

A comparison between [[Neo 1973]] and Neo FreeRunner is available at [[Neo 1973 vs Neo FreeRunner]].

== Getting the Neo FreeRunner ==
[[Image:Freerunner02.gif|200px|right]]

The FreeRunner can be purchased from a [[distributors|distributor]]. The software available on the phone makes it suitable for power users and developers only -- it is not yet ready for the general consumer. Email announcements are found on the [http://lists.openmoko.org/mailman/listinfo/announce announce mailing list]. For frequently asked questions please check [[FAQ]].

== Intended use and users ==

The Neo FreeRunner is a Linux-based touch screen smart phone ultimately aimed at general consumer use as well as Linux desktop users and software developers.

Linux users and software developers will appreciate the total freedom they have to use and design software for the FreeRunner.

General phone users will eventually appreciate the high spec and performance of the phone and the wide range of free software packages expected to emerge. These will allow users to make the maximum use of the hardware and tailor it to their particular needs. Since launch, the pace of software tweaks and improvements has increased as both the Openmoko team developers and the wider community work together.

== How usable is it? ==

With most distributions the FreeRunner is working as a reliable phone. However it still has usability issues and many advanced features are still missing. (For example with SHR, the most used distribution, the phone keeps ringing for a second after a call has been accepted) For more information see [[Distributions#Features by distribution/release_target|distributions]].

Please see the [[FreeRunner: Selected Blogs and Articles]] to get more reviews. The [[Neo FreeRunner Hardware Issues]] page may also be of interest.

== See also ==
*[[Getting Started with your Neo FreeRunner]]
*[[FAQ]]

== External links ==

*[http://www.guruworkshop.com/omoko 3D model of Neo FreeRunner, click and drag to rotate]

[[Category:Neo FreeRunner Hardware| ]]

Manuals/Neo FreeRunner/eu

2010-01-27T12:58:05Z

Joseba:

{{Languages|Manuals/Neo FreeRunner}}

Mila esker Neo FreeRunner erosteagatik. [[Neo FreeRunner]] telefonoa Openmokorako pentsatutako bigarren hardware plataforma da. Gida honetan hasierako erabilerarako behar duzuna eta tresna berria ezagutzen ikasiko duzu.

[[Image:Freerunner box.png|200px|thumb|Neo FreeRunner Package]]

== Hardwarearen konfigurazioa, Neo Freerunnerra eta bere osagaiak ezagutzen hasi ==

=== Mikro-SD txartelaren, SIM Txartelaren eta bateriaren instalazioa ===

# Neo Freerunnerraren atzeko tapa kendu, horretarako, alboetatik heldu telefonoa, eta goian daukan arteka edo zirrikituan azkazalen laguntzaz atzerantz bultza eta atzeko tapa askatuko da.
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu13.jpg|233px|thumb|zirrikituan azkazalez bultza.|center]]</td>
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu14.jpg|250px|thumb|Atzeko estalkia askatu!|center]]</td>
</tr>
</table>
# Orain bateria jarri behar den kokagunea agerian dago, eta bere azpian telefoniako txartela eta Mikro SD txartela jartzeko guneak ere ikusiko dituzu.
# Lehendabizi SIM txartelaren estalkia askatu behar da, horretarako, beherantz (kanpoko USB entxufe alderantz) bultza metalezko klipa. Kontu handiz ibili, zati delikatua baita hau, eta indarrez eginez gero kalteak eragin daitezke. Norantza ere arretaz aztertu.
[[Image:menu11.jpg|260px|thumb|Jarri SIM eta SD txartelak hemen.|center]]
# Altxa SIM txartela eusteko klipa.
# Mikro-SD txartelak erabili aurretik begiratu [[Supported_microSD_cards |onartzen direla jakina den Mikro-SD txartelen zerrenda]].
# Mikro-SD euskarria bi aldetatik lotuta dago, Errazena alda bakoitza banaka askatzea da. Erditik tiraz bi aldeak batera askatzen saituz gero, loturak indar handiagoa egiten du, beraz, lehendabizi alde bat askatu eta gero bestea. Kontuz labanekin edota bihurkinekin! honako [http://people.openmoko.org/joerg/sdcard-handle/ argazkietan] ikus daiteke euskarria irekita eta txartelak sartuta.
# Sartu Mikro-SD txartela bere euskarrian. Kontuan izan euskarrian txartela eusteko kartolatxoak (eusteko topeak) daudela, kartola horien artetik sartu txartela (tente geratuko da txartela, kontaktuak beheko aldean) eta ondoren itxi euskarria txartela etzanda gera dadin. Txartelaren kontaktuak beheko aldean geratu beharko dute, alegia ez dira ikusiko, eta gainera telefonoaren ertzean egongo dira.
# Mikro-SD txartelaren euskarria etzan ondoren, bi lokailuak ondo itxi direla ziurtatu. Gaizki itxitako euskarriko txartela ez du ikusiko telefonoak.
# SIM txartela bere euskarrian sartu, kontu izan honek ere metalezko bi kartolatxo dauzkala, eta horien artean sartu behar dela.Berriz ere kontaktu elektrikoak beherantz geratu behar dute, eta ebakitako ertza FreeRunner gailuaren kanpo aldetik gertu geratu behar du (GPS antenaren aldean).
# Etzan SIM txartelaren euskarria eta metalezko klipa GPS antenaren aldera labaindu ondo itxita gera dadin.
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">
[[Image:FR_SIM_SD_open.jpg|457px|thumb|SIM and SD euskarriak irekita, eta txartelak beren lekuetan|center]]</td>
<td style="padding: 1px 1em 0; background: #ffffff;">
[[Image:Engchang.jpg|392px|thumb|Gailu batzuek itxura hau daukate, tanta modukoa ez da akatsa|center]]</td>
</tr>
</table>
# Sartu bateria horretarako gunean, bateriaren kontaktuak telefonoaren kontaktuekin elkartuz. Lehendabizi kontaktuen aldea sartu.
# FreeRunnerraren atzeko tapa bere tokian jarri.

{| class="wikitable" style="background#00CC00;border-left:1px solid white;border-right:1px solid white;border-top:0px solid white; border:1px solid #00CC00; float:right; margin: 0 0 1em 1em;"
! style="background:#00cc00;border-left:1px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #00CC00;" |<font color=white>Tips</font>
|-
!style="background:#ffffff;border-left:1px solid white;border-right:1px solid white;border-top:0px solid white; border:1px solid #FFFFff;" |
<div align=left>
[http://video.google.de/videoplay?docid=-8343770443102960945 Bideotxoa] ere ikus dezakezu. Neo gailuaren bertsio zaharrarekin egina den arren, antzeko prozesua da.
</div>

|}

===Neo FreeRunnerra kargatu===

Lehendabiziko erabileraren aurretik Bateria guztiz kargatu behar da. Bateria kargatzeko 1000mA-ko kargatzailea edota 500mA-ko karga eman dezakeen USB portu bat erabil daitezke. Gaur egungo konputagailuek ez daukate inolako arazorik NEO Freerunnera kargatzeko USB portuak erabiliz. '''Itzalita baldin badago, ez da kargatuko''', beraz, piztu eta interfaze grafikoa (GUI edo Graphical User Interface) agertu arte piztu dadila. USB kablea sartzen duzunean (USB kableak konputagailuari konektatuta egon behar du edota 1000mA-ko kargatzaileari, alegia, argi indarra eduki behar du) automatikoki piztuko da. Ez bada bere kabuz pizten, eskuz piztu dezakezu, horretarako, pizteko botoia sakatu (bost edo sei segundo sakatuta eduki). Botoi hau USB entxufearen azpian dago.

Nahiz eta kargatzaileak 2A-ko indarra emateko gaitasuna eduki, Neo Freerunnerraren karga-abiadura 1A-koa da, eta beraz, kargatze-abiadura kargatzailearen gaitasuna baino txikiagoa da.

Entxufeak hiru mota onartzen ditu: berez Ipar Ameriketako entxufea da, baina estalkia kendu eta Europako edota Erresuma Batuko entxufeetarako egokigailua jar daitezke entxufean. Horretarako, entxufearen estalkiaren kisketa sakatu eta estalkia kanporantz labaindu behar da. Kisketa entxufearen estalkiaren testua dagoen kontrako aldean dago. Kontuan izan Ipar Amerikako entxufearen bi konektoreak ez direla askatuko, horien gainetik sartu behar da egokigailua. Egokigailua ere antzera kentzen da.

Bateria kargatzeko denbora sarrerako indarraren araberakoa da,
# 100mA-ko indarraz 12~15 ordu behar dira (kontuan izan etete-egoeran ez badago 100mA baino gehiago behar dituela gailuak)
# sarrerako indarra 500mA-koa bada (PC-en USB konexioa) 2~3 ordu behar dira, eta
#1000mA-ko indarrez (kargatzailea) 1.5~3 ordu behar dira. (90%~100%) <br>
Gailuak 100 mA baino gehiago behar ditu lanean ari denean, beraz, USB bidezko indarra 100mAkoa baldin bada, eteteko egoeran ez badago, gailua ez da kargatuko.

{{Note|ikusi [[Neo_FreeRunner_Hardware_Issues|Neo FreeRunner Hardware arazoak]] bateria guztiz husten ez lagatzeari buruz.}}

===Botoiak eta konexioak ===

<table width="80%" style="clear: both; border-collapse: collapse" valign="top">
<tr>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu9.jpg|370px|thumb|Pizteko botoia, USBa eta kanpoko GPS Antena (ezkerretik eskuinera)|center]]</td>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu8.jpg|370px|thumb|AUX Botoia eta aurikularren jack-a (ezkerretik eskuinera)|center]]</td>
</tr>
<tr>
<td></td>
<td>'''Pizteko''' botoia
Ikututxoa edo kolpetxoa emanaz GTA02 gailua '''etete-egoeran''' jarriko da.

Sakatuta edukiz gero gailua itzali egingo da.</td>
<td></td>
<td>'''Aux''' botoia
Ikututxo bidez edo sakatuz pantaila blokeatuko da.
</td>
</tr>
</table>

'''Aurikularren Jack-a'''

Aurikularren jack-a 2.5mm dituen konektorea da, eta 4 kontaktu dauzka: stereo + MIC. Motorola smartphone (A780,A1200, ...) eta V-360 gailuek erabiltzen dutenarekin bateragarria da.

Informazio gehiago [[Headset|aurikularren]] orrian.

===Zure gailuaren aldaera zein den jakiteko===
Zure gailua zer nolakoa den jakitea komeni zaizu, hau da, gailuaren aldaera (revision) zein den zehaztea komeni da.

# Gogoan jaso data kodea, jaso duzun kutxaren azpian eranskailu batean egongo da.
# irakurri [[Finding_hardware_revision|hardware aldaeraren bila]]

Bi hauek garrantzitsuak dira, zure gailuan, fabrikan, zein irudi flasheatu (ezarri) duten jakiten lagunduko baitizute. (c.f. [[Distributions|banaketak]] eta [[GTA02_revisions | Neo FreeRunner (aka GTA02) aldaerak]]).

==Softwarea instalatu==

Freerunnerrean dagoen software ia guztia aldatu edo eguneratu daiteke, bai eta gailua pizteko beharrezkoa den '''abiarazlea''' eta GSM txipean dagoen softwarea ere.

Izatez, Neo FreeRunnerra berezko [[Distributions| banaketa]] bat barnean ezarrita duela iritsiko zaizu, beraz, hemendik aurrerakorik egin beharrik ez duzu izango. Irakurri [[Om_2008 | OM 2008]] [[Manuals/Om_2008|eskuliburua]] zure telefonoa erabiltzen hasteko. Gerora, zure gailuan [[Distributions|banaketa]] berriagoa edota erabilera zabalagoa duena edota aukera bereziak eskaintzen dituena instalatu nahi zenezake, kasu horretan irakurri ondokoa.

===Abiarazlea instalatu===

Telefonoko sistema eragilea abiarazteko beharrezkoa da bootloader edo abiarazlea. '''Qi''' da gomendatutako abiarazlea Neo FreeRunner gailuan. Horrekin, abiatzeko prozesua azkarragoa baita. Hainbat sistema eragileren artean aukeratu ahal izateko, U-Boot abiarazlea mantendu beharko zenuke, hau abiarazle zaharragoa da. Abiarazlea http://downloads.openmoko.org/distro/testing/NeoFreerunner/ helbidetik har dezakezu eta [[NeoTool]] programaren bidez zure Linux PCan instala dezakezu. (ikusi http://wiki.openmoko.org/wiki/No_Linux ez badaukazu Linuxpean dabilen PCrik, baina hobe zenuke linux banaketa zirraragarriren bat instalatuko bazenio zeure PCari)

===GSM Firmwarea eguneratu===

Gaur egungo GSM Firmwareaaren bertsioak Moko 11 izena du. Zure bertsioa zaharragoa bada bertsio berritzea egin beharko zenuke, horrela telefono gailuaren hainbat funtzionalitate-arazo konponduko baitira.



FreeRunner gailua mikroSD txartelean instalatutako sistemaren bidez abiaraziz hasi behar da, abiaratze honek automatikoki eragingo ditu beharrezkoak diren aginduak eta GSM firmwarea txipera irauliko (flasheatuko?) du. mikroSDra abiarazteko irudia kopiatzea era berezian egin behar izaten da (linuxeko dd agindua erabili beharko duzu ziurrenik) eta mikroSD irudia kopiatzerakoan mikroSDan dagoen informazioa guztiz ezabatuko da. Irudia tentuz jarri mikroSD txartelean, eta era egokian formateatu abiarazteko sistema egokia daukala ziurtatuz.
Prozedura hau fidagarria da GTA02 gailuan MOKO11 ezartzeko (flasheatzeko). Huts egiteko aukerak oso urriak dira _zehazki_ jarraitzen badituzu argibideak. Hemen azaldutako bideari jarraituz ez diozu kalterik eragingo zure gailuari.

'''Arreta berezia jarri `dd` agindua eragiterakoan nora kopiatu behar duen esaterakoan, dispositibo *fisikoa* adierazi behar da, esaterako /dev/sdm, eta *ez* partizioa (alegia ez /dev/sdmp1). Horrez gain, mikroSDko partizio guztiak desmontatuta daudela ziur egon `dd` agindua abiarazterakoan'''<br>
Aurrekoaz ziur zaudenean, ''berriz begiratu ea aurreko abisuko baldintza guztiak betetzen dituzun'', gainera, bada ez bada, ondo begiratu ea mikroSD dispositiboa den `dd` aginduari adierazitakoa, izan ere, disko gogorra adieraziz gero disko gogorreko eduki guztia ezabatuko baitu, eta oso erraza da nahastea, alegia, mikroSDa /dev/sdc izan daiteke, baina /dev/sdb disko gogorra izan daiteke. Beraz, '''arreta handiz idatzi agindua'''.

<ol>
<li>Jaitsi eta <tt>untar</tt> (desenpaketatu) http://people.openmoko.org/joerg/calypso_moko_FW/moko11/flash-moko11_uSD-image.tar.gz zeure mahai gaineko PCra. Irakurri <tt>README.tx</tt> fitxategia, untar egiterakoan paketetik aterako da fitxategia.</li>

<li>Zure PCko irakurgailuan sartu mikroSD txartela, eta automatikoki muntatutako partizioak desmuntatu (mikroSDko partizioak, noski), zZein partizio muntatu diren jakiteko <tt>mount</tt> edo <tt>df -h</tt> aginduak erabil ditzakezu. Desmuntatzeko ez erabili "era seguruan atera txartela", <tt>umount</tt> agindua erabili desmuntatzeko.</li>

<li>mikroSD txartelera <tt>flash-moko11-2.image</tt> fitxategian dagoen irudia fisikoki idazteko <tt>dd</tt> agindua erabili. Kontuz agindu honekin: non idatzi behar duen esateko mikroSD txartelaren dispositibo fisikoa zein den esan behar zaio aginduari, ez partizioren bat, baizik eta dispositiboa bera. Gainera, dispositiboan dagoen eduki guztia ezabatuko du eragiketak, beraz, dispositibo okerra esan ezkero, kalte handia sor daiteke. <tt>dd</tt> aginduari disko gogorrari dagokion dispositibo fisikoan kopiatzeko agindua emango bagenio, partizio taula eta bertako eduki guztia ezabatuko du, beraz, sistema osoa berrinstaltu beharko genuke. Eragiketa hau egiteko orduan root erabiltzailearen baimenak eduki behar dira, alegia root bezala sartu behar da sisteman edo sudo agindu erabili beharko da:</li>

% sudo dd if=flash-moko11-2.image of=/dev/mmcblk0

<li>mikroSD txartela atera aurretik <tt>sync</tt> edo <tt>eject <device></tt> aginduak erabiltzea komeni da, izan ere txartelera informazioa guztiz pasa dela ziur egon behar baitugu.</li>

<li>Sartu mikroSD txartela zeure FreeRunner mugikorrera, eta abiarazi gailua '''[[Booting_the_Neo_FreeRunner#Log_into_U-Boot_in_the_NOR_Flash|NOR-U-Boot]]''' bideari jarraituz, eta aukeratu "Boot from microSD" aukera.</li>

<li>Firmwarea flash memoriara kopiatzeko prozesua abiatuko dela ikusiko duzu, eta bukaeran, 6 minutu inguru igaro ondoren, "d_o_n_e" kolore berdez idatzita azalduko da. Une horretan pizteko/itzaltzeko botoiak ezin du Freerunnerra itzali, botoia sakatzeak eten/itzuli funtzioak beteko ditu, baina ez itzaltzekoa. Gutxienez bi eratara itzal dezakezu Freerunnerra, alde batetik, <tt>ssh</tt> aginduaren bidez FreeRunnerrera konektatu usb kable bidez lotutako PC batetik (edo wifi konexio bidez) eta itzaltzeko agindua eragin dezakezu: <br>
# shutdown -h now<br>
Itzaltzeko beste era bat ere badago, askoz ere sinpleagoa da bigarren era hau (baina ez hain dotorea): bateria kendu eta itzali egingo da, a zer erremedio!.
Firmwarea ondo kopiatu dela ikusteko, ssh konexio bidez <tt>mickeyterm</tt> erabil daiteke modemarekin komunikatzeko eta bertsioa begiratzeko</li>
</ol>
====OHARRA====

Zure PCak mikroSD txartelak irakurtzeko gailurik ez badauka, mikroSD txartelera <tt>dd</tt> agindu bidez moko11 irudiaren kopia FreeRunner gailuan bertan egin dezakezu: instalatu <tt>task-base-smbfs</tt>, mikroSD txartela desmuntatu, horretarako <tt>umount /media/card</tt> agindua erabili (partizio gehiago baleuzka eta horiek ere muntatuta baleude guztiak desmuntatu). Une honetan bi aukera dauzkazu gutxienez:
<ol>
<li> Zure PCan dagoen irudia daukan direktorioa FreeRunnerreko fitxategi sisteman muntatu dezakezu, eta ondoren, <tt>dd</tt> agindu bidez zuzenean FreeRunnerrean dagoen mikroSD txartelera kopia dezakezu. Prozesu horrek 12 minutu inguru iraun ditzake. Eragiketa hau FreeRunnerreko shell batetik egin behar da.
</li>
<li>Alderantziz ere jardun daiteke, alegia, PCko shell batean lan egin dezakezu, horretarako, lehenengo FreeRunnerrean mikroSD txartela desmuntatu:<br>
root@om-gta02 ~ $ umount /media/card<br>
Eta ondoren, PCko shell batean (usb edo wifi konexioa eskatzen du honek):<br>
scp flash-moko11-2.image root@192.168.0.202:/dev/mmcblk0
</li>
</ol>
Prozesu horiek azkartu egin daitezke, irudia gzip bidez konprimituz makinatik makinara pasa beharreko informazio-kopurua gutxitu egin daiteke, eta deskonprimitzeko aginduari zuzenean mikroSD txartelera kopiatzeko esan diezaiokegu:

% gzip -d < flash-moko11-2.image.gz > /dev/mmcblk0

Agindu honenkin, eta FreeRunnerreko fitxategi sisteman nahikoa leku libre edukiz gero, ez dogo PCa erabili beharrik, alegia, konprimitutako fitxategia FreeRunnerrean bertan jaso daiteke, eta deskonprimitu mikroSD txartelera. Baina 92MB libre behar ditu gutxi gora behera.

====BIGARREN OHARRA====

Abiorako [[Qi]] instalatuta eduki ala ez (ikusi aurrekoa), pizterakoan NOR menuraino joan behar da (horretarako AUX botoia sakatuta daukazun bitartean pizteko botoia sakatu) eta bertan "Boot from microSD (fat/ext2)" aukeratu behar duzu instalazio prozesua abiatu dadin. (per DocScrutinizer in #openmoko). '''Ez''' utzi Qi abiarazleari mikroSDko partizioa izan dadin sistemaren abioa. Antzekoa dirudien arren, berdez idatzitako "d_o_n_e" ez da azalduko eta ondorioz egin beharrekoa ez du egingo.

You can confirm the firmware version number using the [[OpenmokoFramework/mickeyterm|mickeyterm]] (cmd: "AT+CGMR"). In SHR-Settings, Phone/Modem Information will supply the same number.

===Installing a distribution===

This section describes how to install a distribution on the internal flash memory of the Neo FreeRunner. If you want to install it on the memory card please refer to the guide provided by the distribution.

For installing a new distribution you will need two files, a root file system (rootfs) image and a kernel image. The root file system image usually ends with ".jffs2", and the kernel image ends with ".uimage.bin". You can get these files from http://wiki.openmoko.org/wiki/Download . Use the program NeoTool to install the distribution on your FreeRunner. The flashing process can take up to 15 minutes for a ~70MB image. It is also wise to make sure that your Neo has enough battery charge prior to flashing.

When flashing succeeds the following will be shown:

<pre>
status(0) = No error condition is present
Done!
</pre>

[[Category:Manuals]]

Manuals/Neo FreeRunner/eu

2010-01-27T12:45:30Z

Joseba:

{{Languages|Manuals/Neo FreeRunner}}

Mila esker Neo FreeRunner erosteagatik. [[Neo FreeRunner]] telefonoa Openmokorako pentsatutako bigarren hardware plataforma da. Gida honetan hasierako erabilerarako behar duzuna eta tresna berria ezagutzen ikasiko duzu.

[[Image:Freerunner box.png|200px|thumb|Neo FreeRunner Package]]

== Hardwarearen konfigurazioa, Neo Freerunnerra eta bere osagaiak ezagutzen hasi ==

=== Mikro-SD txartelaren, SIM Txartelaren eta bateriaren instalazioa ===

# Neo Freerunnerraren atzeko tapa kendu, horretarako, alboetatik heldu telefonoa, eta goian daukan arteka edo zirrikituan azkazalen laguntzaz atzerantz bultza eta atzeko tapa askatuko da.
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu13.jpg|233px|thumb|zirrikituan azkazalez bultza.|center]]</td>
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu14.jpg|250px|thumb|Atzeko estalkia askatu!|center]]</td>
</tr>
</table>
# Orain bateria jarri behar den kokagunea agerian dago, eta bere azpian telefoniako txartela eta Mikro SD txartela jartzeko guneak ere ikusiko dituzu.
# Lehendabizi SIM txartelaren estalkia askatu behar da, horretarako, beherantz (kanpoko USB entxufe alderantz) bultza metalezko klipa. Kontu handiz ibili, zati delikatua baita hau, eta indarrez eginez gero kalteak eragin daitezke. Norantza ere arretaz aztertu.
[[Image:menu11.jpg|260px|thumb|Jarri SIM eta SD txartelak hemen.|center]]
# Altxa SIM txartela eusteko klipa.
# Mikro-SD txartelak erabili aurretik begiratu [[Supported_microSD_cards |onartzen direla jakina den Mikro-SD txartelen zerrenda]].
# Mikro-SD euskarria bi aldetatik lotuta dago, Errazena alda bakoitza banaka askatzea da. Erditik tiraz bi aldeak batera askatzen saituz gero, loturak indar handiagoa egiten du, beraz, lehendabizi alde bat askatu eta gero bestea. Kontuz labanekin edota bihurkinekin! honako [http://people.openmoko.org/joerg/sdcard-handle/ argazkietan] ikus daiteke euskarria irekita eta txartelak sartuta.
# Sartu Mikro-SD txartela bere euskarrian. Kontuan izan euskarrian txartela eusteko kartolatxoak (eusteko topeak) daudela, kartola horien artetik sartu txartela (tente geratuko da txartela, kontaktuak beheko aldean) eta ondoren itxi euskarria txartela etzanda gera dadin. Txartelaren kontaktuak beheko aldean geratu beharko dute, alegia ez dira ikusiko, eta gainera telefonoaren ertzean egongo dira.
# Mikro-SD txartelaren euskarria etzan ondoren, bi lokailuak ondo itxi direla ziurtatu. Gaizki itxitako euskarriko txartela ez du ikusiko telefonoak.
# SIM txartela bere euskarrian sartu, kontu izan honek ere metalezko bi kartolatxo dauzkala, eta horien artean sartu behar dela.Berriz ere kontaktu elektrikoak beherantz geratu behar dute, eta ebakitako ertza FreeRunner gailuaren kanpo aldetik gertu geratu behar du (GPS antenaren aldean).
# Etzan SIM txartelaren euskarria eta metalezko klipa GPS antenaren aldera labaindu ondo itxita gera dadin.
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">
[[Image:FR_SIM_SD_open.jpg|457px|thumb|SIM and SD euskarriak irekita, eta txartelak beren lekuetan|center]]</td>
<td style="padding: 1px 1em 0; background: #ffffff;">
[[Image:Engchang.jpg|392px|thumb|Gailu batzuek itxura hau daukate, tanta modukoa ez da akatsa|center]]</td>
</tr>
</table>
# Sartu bateria horretarako gunean, bateriaren kontaktuak telefonoaren kontaktuekin elkartuz. Lehendabizi kontaktuen aldea sartu.
# FreeRunnerraren atzeko tapa bere tokian jarri.

{| class="wikitable" style="background#00CC00;border-left:1px solid white;border-right:1px solid white;border-top:0px solid white; border:1px solid #00CC00; float:right; margin: 0 0 1em 1em;"
! style="background:#00cc00;border-left:1px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #00CC00;" |<font color=white>Tips</font>
|-
!style="background:#ffffff;border-left:1px solid white;border-right:1px solid white;border-top:0px solid white; border:1px solid #FFFFff;" |
<div align=left>
[http://video.google.de/videoplay?docid=-8343770443102960945 Bideotxoa] ere ikus dezakezu. Neo gailuaren bertsio zaharrarekin egina den arren, antzeko prozesua da.
</div>

|}

===Neo FreeRunnerra kargatu===

Lehendabiziko erabileraren aurretik Bateria guztiz kargatu behar da. Bateria kargatzeko 1000mA-ko kargatzailea edota 500mA-ko karga eman dezakeen USB portu bat erabil daitezke. Gaur egungo konputagailuek ez daukate inolako arazorik NEO Freerunnera kargatzeko USB portuak erabiliz. '''Itzalita baldin badago, ez da kargatuko''', beraz, piztu eta interfaze grafikoa (GUI edo Graphical User Interface) agertu arte piztu dadila. USB kablea sartzen duzunean (USB kableak konputagailuari konektatuta egon behar du edota 1000mA-ko kargatzaileari, alegia, argi indarra eduki behar du) automatikoki piztuko da. Ez bada bere kabuz pizten, eskuz piztu dezakezu, horretarako, pizteko botoia sakatu (bost edo sei segundo sakatuta eduki). Botoi hau USB entxufearen azpian dago.

Nahiz eta kargatzaileak 2A-ko indarra emateko gaitasuna eduki, Neo Freerunnerraren karga-abiadura 1A-koa da, eta beraz, kargatze-abiadura kargatzailearen gaitasuna baino txikiagoa da.

Entxufeak hiru mota onartzen ditu: berez Ipar Ameriketako entxufea da, baina estalkia kendu eta Europako edota Erresuma Batuko entxufeetarako egokigailua jar daitezke entxufean. Horretarako, entxufearen estalkiaren kisketa sakatu eta estalkia kanporantz labaindu behar da. Kisketa entxufearen estalkiaren testua dagoen kontrako aldean dago. Kontuan izan Ipar Amerikako entxufearen bi konektoreak ez direla askatuko, horien gainetik sartu behar da egokigailua. Egokigailua ere antzera kentzen da.

Bateria kargatzeko denbora sarrerako indarraren araberakoa da,
# 100mA-ko indarraz 12~15 ordu behar dira (kontuan izan etete-egoeran ez badago 100mA baino gehiago behar dituela gailuak)
# sarrerako indarra 500mA-koa bada (PC-en USB konexioa) 2~3 ordu behar dira, eta
#1000mA-ko indarrez (kargatzailea) 1.5~3 ordu behar dira. (90%~100%) <br>
Gailuak 100 mA baino gehiago behar ditu lanean ari denean, beraz, USB bidezko indarra 100mAkoa baldin bada, eteteko egoeran ez badago, gailua ez da kargatuko.

{{Note|ikusi [[Neo_FreeRunner_Hardware_Issues|Neo FreeRunner Hardware arazoak]] bateria guztiz husten ez lagatzeari buruz.}}

===Botoiak eta konexioak ===

<table width="80%" style="clear: both; border-collapse: collapse" valign="top">
<tr>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu9.jpg|370px|thumb|Pizteko botoia, USBa eta kanpoko GPS Antena (ezkerretik eskuinera)|center]]</td>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu8.jpg|370px|thumb|AUX Botoia eta aurikularren jack-a (ezkerretik eskuinera)|center]]</td>
</tr>
<tr>
<td></td>
<td>'''Pizteko''' botoia
Ikututxoa edo kolpetxoa emanaz GTA02 gailua '''etete-egoeran''' jarriko da.

Sakatuta edukiz gero gailua itzali egingo da.</td>
<td></td>
<td>'''Aux''' botoia
Ikututxo bidez edo sakatuz pantaila blokeatuko da.
</td>
</tr>
</table>

'''Aurikularren Jack-a'''

Aurikularren jack-a 2.5mm dituen konektorea da, eta 4 kontaktu dauzka: stereo + MIC. Motorola smartphone (A780,A1200, ...) eta V-360 gailuek erabiltzen dutenarekin bateragarria da.

Informazio gehiago [[Headset|aurikularren]] orrian.

===Zure gailuaren aldaera zein den jakiteko===
Zure gailua zer nolakoa den jakitea komeni zaizu, hau da, gailuaren aldaera (revision) zein den zehaztea komeni da.

# Gogoan jaso data kodea, jaso duzun kutxaren azpian eranskailu batean egongo da.
# irakurri [[Finding_hardware_revision|hardware aldaeraren bila]]

Bi hauek garrantzitsuak dira, zure gailuan, fabrikan, zein irudi flasheatu (ezarri) duten jakiten lagunduko baitizute. (c.f. [[Distributions|banaketak]] eta [[GTA02_revisions | Neo FreeRunner (aka GTA02) aldaerak]]).

==Softwarea instalatu==

Freerunnerrean dagoen software ia guztia aldatu edo eguneratu daiteke, bai eta gailua pizteko beharrezkoa den '''abiarazlea''' eta GSM txipean dagoen softwarea ere.

Izatez, Neo FreeRunnerra berezko [[Distributions| banaketa]] bat barnean ezarrita duela iritsiko zaizu, beraz, hemendik aurrerakorik egin beharrik ez duzu izango. Irakurri [[Om_2008 | OM 2008]] [[Manuals/Om_2008|eskuliburua]] zure telefonoa erabiltzen hasteko. Gerora, zure gailuan [[Distributions|banaketa]] berriagoa edota erabilera zabalagoa duena edota aukera bereziak eskaintzen dituena instalatu nahi zenezake, kasu horretan irakurri ondokoa.

===Abiarazlea instalatu===

Telefonoko sistema eragilea abiarazteko beharrezkoa da bootloader edo abiarazlea. '''Qi''' da gomendatutako abiarazlea Neo FreeRunner gailuan. Horrekin, abiatzeko prozesua azkarragoa baita. Hainbat sistema eragileren artean aukeratu ahal izateko, U-Boot abiarazlea mantendu beharko zenuke, hau abiarazle zaharragoa da. Abiarazlea http://downloads.openmoko.org/distro/testing/NeoFreerunner/ helbidetik har dezakezu eta [[NeoTool]] programaren bidez zure Linux PCan instala dezakezu. (ikusi http://wiki.openmoko.org/wiki/No_Linux ez badaukazu Linuxpean dabilen PCrik, baina hobe zenuke linux banaketa zirraragarriren bat instalatuko bazenio zeure PCari)

===GSM Firmwarea eguneratu===

Gaur egungo GSM Firmwareaaren bertsioak Moko 11 izena du. Zure bertsioa zaharragoa bada bertsio berritzea egin beharko zenuke, horrela telefono gailuaren hainbat funtzionalitate-arazo konponduko baitira.



FreeRunner gailua mikroSD txartelean instalatutako sistemaren bidez abiaraziz hasi behar da, abiaratze honek automatikoki eragingo ditu beharrezkoak diren aginduak eta GSM firmwarea txipera irauliko (flasheatuko?) du. mikroSDra abiarazteko irudia kopiatzea era berezian egin behar izaten da (linuxeko dd agindua erabili beharko duzu ziurrenik) eta mikroSD irudia kopiatzerakoan mikroSDan dagoen informazioa guztiz ezabatuko da. Irudia tentuz jarri mikroSD txartelean, eta era egokian formateatu abiarazteko sistema egokia daukala ziurtatuz.
Prozedura hau fidagarria da GTA02 gailuan MOKO11 ezartzeko (flasheatzeko). Huts egiteko aukerak oso urriak dira _zehazki_ jarraitzen badituzu argibideak. Hemen azaldutako bideari jarraituz ez diozu kalterik eragingo zure gailuari.

'''Arreta berezia jarri `dd` agindua eragiterakoan nora kopiatu behar duen esaterakoan, dispositibo *fisikoa* adierazi behar da, esaterako /dev/sdm, eta *ez* partizioa (alegia ez /dev/sdmp1). Horrez gain, mikroSDko partizio guztiak desmontatuta daudela ziur egon `dd` agindua abiarazterakoan'''<br>
Aurrekoaz ziur zaudenean, ''berriz begiratu ea aurreko abisuko baldintza guztiak betetzen dituzun'', gainera, bada ez bada, ondo begiratu ea mikroSD dispositiboa den `dd` aginduari adierazitakoa, izan ere, disko gogorra adieraziz gero disko gogorreko eduki guztia ezabatuko baitu, eta oso erraza da nahastea, alegia, mikroSDa /dev/sdc izan daiteke, baina /dev/sdb disko gogorra izan daiteke. Beraz, '''arreta handiz idatzi agindua'''.

<ol>
<li>Jaitsi eta <tt>untar</tt> (desenpaketatu) http://people.openmoko.org/joerg/calypso_moko_FW/moko11/flash-moko11_uSD-image.tar.gz zeure mahai gaineko PCra. Irakurri <tt>README.tx</tt> fitxategia, untar egiterakoan paketetik aterako da fitxategia.</li>

<li>Zure PCko irakurgailuan sartu mikroSD txartela, eta automatikoki muntatutako partizioak desmuntatu (mikroSDko partizioak, noski), zZein partizio muntatu diren jakiteko <tt>mount</tt> edo <tt>df -h</tt> aginduak erabil ditzakezu. Desmuntatzeko ez erabili "era seguruan atera txartela", <tt>umount</tt> agindua erabili desmuntatzeko.</li>

<li>mikroSD txartelera <tt>flash-moko11-2.image</tt> fitxategian dagoen irudia fisikoki idazteko <tt>dd</tt> agindua erabili. Kontuz agindu honekin: non idatzi behar duen esateko mikroSD txartelaren dispositibo fisikoa zein den esan behar zaio aginduari, ez partizioren bat, baizik eta dispositiboa bera. Gainera, dispositiboan dagoen eduki guztia ezabatuko du eragiketak, beraz, dispositibo okerra esan ezkero, kalte handia sor daiteke. <tt>dd</tt> aginduari disko gogorrari dagokion dispositibo fisikoan kopiatzeko agindua emango bagenio, partizio taula eta bertako eduki guztia ezabatuko du, beraz, sistema osoa berrinstaltu beharko genuke. Eragiketa hau egiteko orduan root erabiltzailearen baimenak eduki behar dira, alegia root bezala sartu behar da sisteman edo sudo agindu erabili beharko da:</li>

% sudo dd if=flash-moko11-2.image of=/dev/mmcblk0

<li>mikroSD txartela atera aurretik <tt>sync</tt> edo <tt>eject <device></tt> aginduak erabiltzea komeni da, izan ere txartelera informazioa guztiz pasa dela ziur egon behar baitugu.</li>

<li>Sartu mikroSD txartela zeure FreeRunner mugikorrera, eta abiarazi gailua '''[[Booting_the_Neo_FreeRunner#Log_into_U-Boot_in_the_NOR_Flash|NOR-U-Boot]]''' bideari jarraituz, eta aukeratu "Boot from microSD" aukera.</li>

<li>Firmwarea flash memoriara kopiatzeko prozesua abiatuko dela ikusiko duzu, eta bukaeran, 6 minutu inguru igaro ondoren, "d_o_n_e" kolore berdez idatzita azalduko da. Une horretan pizteko/itzaltzeko botoiak ezin du Freerunnerra itzali, botoia sakatzeak eten/itzuli funtzioak beteko ditu, baina ez itzaltzekoa. Gutxienez bi eratara itzal dezakezu Freerunnerra, alde batetik, <tt>ssh</tt> aginduaren bidez FreeRunnerrera konektatu usb kable bidez lotutako PC batetik (edo wifi konexio bidez) eta itzaltzeko agindua eragin dezakezu: <br>
# shutdown -h now<br>
Itzaltzeko beste era bat ere badago, askoz ere sinpleagoa da bigarren era hau (baina ez hain dotorea): bateria kendu eta itzali egingo da, a zer erremedio!.
Firmwarea ondo kopiatu dela ikusteko, ssh konexio bidez <tt>mickeyterm</tt> erabil daiteke modemarekin komunikatzeko eta bertsioa begiratzeko</li>
</ol>
====OHARRA====

Zure PCak mikroSD txartelak irakurtzeko gailurik ez badauka, mikroSD txartelera <tt>dd</tt> agindu bidez moko11 irudiaren kopia FreeRunner gailuan bertan egin dezakezu: instalatu <tt>task-base-smbfs</tt>, mikroSD txartela desmuntatu, horretarako <tt>umount /media/card</tt> agindua erabili (partizio gehiago baleuzka eta horiek ere muntatuta baleude guztiak desmuntatu). Une honetan bi aukera dauzkazu gutxienez:
<ol>
<li> Zure PCan dagoen irudia daukan direktorioa FreeRunnerreko fitxategi sisteman muntatu dezakezu, eta ondoren, <tt>dd</tt> agindu bidez zuzenean FreeRunnerrean dagoen mikroSD txartelera kopia dezakezu. Prozesu horrek 12 minutu inguru iraun ditzake. Eragiketa hau FreeRunnerreko shell batetik egin behar da.
</li>
<li>Alderantziz ere jardun daiteke, alegia, PCko shell batean lan egin dezakezu, horretarako, lehenengo FreeRunnerrean mikroSD txartela desmuntatu:<br>
root@om-gta02 ~ $ umount /media/card<br>
Eta ondoren, PCko shell batean (usb edo wifi konexioa eskatzen du honek):<br>
scp flash-moko11-2.image root@192.168.0.202:/dev/mmcblk0
</li>
</ol>
Prozesu horiek azkartu egin daitezke, irudia gzip bidez konprimituz makinatik makinara pasa beharreko informazio-kopurua gutxitu egin daiteke, eta deskonprimitzeko aginduari zuzenean mikroSD txartelera kopiatzeko esan diezaiokegu:

% gzip -d < flash-moko11-2.image.gz > /dev/mmcblk0

Agindu honenkin, eta FreeRunnerreko fitxategi sisteman nahikoa leku libre edukiz gero, ez dogo PCa erabili beharrik, alegia, konprimitutako fitxategia FreeRunnerrean bertan jaso daiteke, eta deskonprimitu mikroSD txartelera. Baina 92MB libre behar ditu gutxi gora behera.

====2. OHARRA====

Whether you have [[Qi]] installed or not (see above) as your boot loader, you must power up to the NoR menu (Hold AUX Key, press Power button) and select "Boot from microSD (fat/ext2)" to begin the installation process (per DocScrutinizer in #openmoko). '''Do not''' let Qi boot the uSD. Although it still seems to flash OK, the green "d_o_n_e" does not show up, to give you the warm feeling that everything is OK.

You can confirm the firmware version number using the [[OpenmokoFramework/mickeyterm|mickeyterm]] (cmd: "AT+CGMR"). In SHR-Settings, Phone/Modem Information will supply the same number.

===Installing a distribution===

This section describes how to install a distribution on the internal flash memory of the Neo FreeRunner. If you want to install it on the memory card please refer to the guide provided by the distribution.

For installing a new distribution you will need two files, a root file system (rootfs) image and a kernel image. The root file system image usually ends with ".jffs2", and the kernel image ends with ".uimage.bin". You can get these files from http://wiki.openmoko.org/wiki/Download . Use the program NeoTool to install the distribution on your FreeRunner. The flashing process can take up to 15 minutes for a ~70MB image. It is also wise to make sure that your Neo has enough battery charge prior to flashing.

When flashing succeeds the following will be shown:

<pre>
status(0) = No error condition is present
Done!
</pre>

[[Category:Manuals]]

Manuals/Neo FreeRunner/eu

2010-01-27T11:54:39Z

Joseba:

{{Languages|Manuals/Neo FreeRunner}}

Mila esker Neo FreeRunner erosteagatik. [[Neo FreeRunner]] telefonoa Openmokorako pentsatutako bigarren hardware plataforma da. Gida honetan hasierako erabilerarako behar duzuna eta tresna berria ezagutzen ikasiko duzu.

[[Image:Freerunner box.png|200px|thumb|Neo FreeRunner Package]]

== Hardwarearen konfigurazioa, Neo Freerunnerra eta bere osagaiak ezagutzen hasi ==

=== Mikro-SD txartelaren, SIM Txartelaren eta bateriaren instalazioa ===

# Neo Freerunnerraren atzeko tapa kendu, horretarako, alboetatik heldu telefonoa, eta goian daukan arteka edo zirrikituan azkazalen laguntzaz atzerantz bultza eta atzeko tapa askatuko da.
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu13.jpg|233px|thumb|zirrikituan azkazalez bultza.|center]]</td>
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu14.jpg|250px|thumb|Atzeko estalkia askatu!|center]]</td>
</tr>
</table>
# Orain bateria jarri behar den kokagunea agerian dago, eta bere azpian telefoniako txartela eta Mikro SD txartela jartzeko guneak ere ikusiko dituzu.
# Lehendabizi SIM txartelaren estalkia askatu behar da, horretarako, beherantz (kanpoko USB entxufe alderantz) bultza metalezko klipa. Kontu handiz ibili, zati delikatua baita hau, eta indarrez eginez gero kalteak eragin daitezke. Norantza ere arretaz aztertu.
[[Image:menu11.jpg|260px|thumb|Jarri SIM eta SD txartelak hemen.|center]]
# Altxa SIM txartela eusteko klipa.
# Mikro-SD txartelak erabili aurretik begiratu [[Supported_microSD_cards |onartzen direla jakina den Mikro-SD txartelen zerrenda]].
# Mikro-SD euskarria bi aldetatik lotuta dago, Errazena alda bakoitza banaka askatzea da. Erditik tiraz bi aldeak batera askatzen saituz gero, loturak indar handiagoa egiten du, beraz, lehendabizi alde bat askatu eta gero bestea. Kontuz labanekin edota bihurkinekin! honako [http://people.openmoko.org/joerg/sdcard-handle/ argazkietan] ikus daiteke euskarria irekita eta txartelak sartuta.
# Sartu Mikro-SD txartela bere euskarrian. Kontuan izan euskarrian txartela eusteko kartolatxoak (eusteko topeak) daudela, kartola horien artetik sartu txartela (tente geratuko da txartela, kontaktuak beheko aldean) eta ondoren itxi euskarria txartela etzanda gera dadin. Txartelaren kontaktuak beheko aldean geratu beharko dute, alegia ez dira ikusiko, eta gainera telefonoaren ertzean egongo dira.
# Mikro-SD txartelaren euskarria etzan ondoren, bi lokailuak ondo itxi direla ziurtatu. Gaizki itxitako euskarriko txartela ez du ikusiko telefonoak.
# SIM txartela bere euskarrian sartu, kontu izan honek ere metalezko bi kartolatxo dauzkala, eta horien artean sartu behar dela.Berriz ere kontaktu elektrikoak beherantz geratu behar dute, eta ebakitako ertza FreeRunner gailuaren kanpo aldetik gertu geratu behar du (GPS antenaren aldean).
# Etzan SIM txartelaren euskarria eta metalezko klipa GPS antenaren aldera labaindu ondo itxita gera dadin.
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;">
<tr valign="top" style="background: #ffffff">
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">
[[Image:FR_SIM_SD_open.jpg|457px|thumb|SIM and SD euskarriak irekita, eta txartelak beren lekuetan|center]]</td>
<td style="padding: 1px 1em 0; background: #ffffff;">
[[Image:Engchang.jpg|392px|thumb|Gailu batzuek itxura hau daukate, tanta modukoa ez da akatsa|center]]</td>
</tr>
</table>
# Sartu bateria horretarako gunean, bateriaren kontaktuak telefonoaren kontaktuekin elkartuz. Lehendabizi kontaktuen aldea sartu.
# FreeRunnerraren atzeko tapa bere tokian jarri.

{| class="wikitable" style="background#00CC00;border-left:1px solid white;border-right:1px solid white;border-top:0px solid white; border:1px solid #00CC00; float:right; margin: 0 0 1em 1em;"
! style="background:#00cc00;border-left:1px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #00CC00;" |<font color=white>Tips</font>
|-
!style="background:#ffffff;border-left:1px solid white;border-right:1px solid white;border-top:0px solid white; border:1px solid #FFFFff;" |
<div align=left>
[http://video.google.de/videoplay?docid=-8343770443102960945 Bideotxoa] ere ikus dezakezu. Neo gailuaren bertsio zaharrarekin egina den arren, antzeko prozesua da.
</div>

|}

===Neo FreeRunnerra kargatu===

Lehendabiziko erabileraren aurretik Bateria guztiz kargatu behar da. Bateria kargatzeko 1000mA-ko kargatzailea edota 500mA-ko karga eman dezakeen USB portu bat erabil daitezke. Gaur egungo konputagailuek ez daukate inolako arazorik NEO Freerunnera kargatzeko USB portuak erabiliz. '''Itzalita baldin badago, ez da kargatuko''', beraz, piztu eta interfaze grafikoa (GUI edo Graphical User Interface) agertu arte piztu dadila. USB kablea sartzen duzunean (USB kableak konputagailuari konektatuta egon behar du edota 1000mA-ko kargatzaileari, alegia, argi indarra eduki behar du) automatikoki piztuko da. Ez bada bere kabuz pizten, eskuz piztu dezakezu, horretarako, pizteko botoia sakatu (bost edo sei segundo sakatuta eduki). Botoi hau USB entxufearen azpian dago.

Nahiz eta kargatzaileak 2A-ko indarra emateko gaitasuna eduki, Neo Freerunnerraren karga-abiadura 1A-koa da, eta beraz, kargatze-abiadura kargatzailearen gaitasuna baino txikiagoa da.

Entxufeak hiru mota onartzen ditu: berez Ipar Ameriketako entxufea da, baina estalkia kendu eta Europako edota Erresuma Batuko entxufeetarako egokigailua jar daitezke entxufean. Horretarako, entxufearen estalkiaren kisketa sakatu eta estalkia kanporantz labaindu behar da. Kisketa entxufearen estalkiaren testua dagoen kontrako aldean dago. Kontuan izan Ipar Amerikako entxufearen bi konektoreak ez direla askatuko, horien gainetik sartu behar da egokigailua. Egokigailua ere antzera kentzen da.

Bateria kargatzeko denbora sarrerako indarraren araberakoa da,
# 100mA-ko indarraz 12~15 ordu behar dira (kontuan izan etete-egoeran ez badago 100mA baino gehiago behar dituela gailuak)
# sarrerako indarra 500mA-koa bada (PC-en USB konexioa) 2~3 ordu behar dira, eta
#1000mA-ko indarrez (kargatzailea) 1.5~3 ordu behar dira. (90%~100%) <br>
Gailuak 100 mA baino gehiago behar ditu lanean ari denean, beraz, USB bidezko indarra 100mAkoa baldin bada, eteteko egoeran ez badago, gailua ez da kargatuko.

{{Note|ikusi [[Neo_FreeRunner_Hardware_Issues|Neo FreeRunner Hardware arazoak]] bateria guztiz husten ez lagatzeari buruz.}}

===Botoiak eta konexioak ===

<table width="80%" style="clear: both; border-collapse: collapse" valign="top">
<tr>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu9.jpg|370px|thumb|Pizteko botoia, USBa eta kanpoko GPS Antena (ezkerretik eskuinera)|center]]</td>
<td style="width: 25px"> </td>
<td style="width: 370px">[[Image:menu8.jpg|370px|thumb|AUX Botoia eta aurikularren jack-a (ezkerretik eskuinera)|center]]</td>
</tr>
<tr>
<td></td>
<td>'''Pizteko''' botoia
Ikututxoa edo kolpetxoa emanaz GTA02 gailua '''etete-egoeran''' jarriko da.

Sakatuta edukiz gero gailua itzali egingo da.</td>
<td></td>
<td>'''Aux''' botoia
Ikututxo bidez edo sakatuz pantaila blokeatuko da.
</td>
</tr>
</table>

'''Aurikularren Jack-a'''

Aurikularren jack-a 2.5mm dituen konektorea da, eta 4 kontaktu dauzka: stereo + MIC. Motorola smartphone (A780,A1200, ...) eta V-360 gailuek erabiltzen dutenarekin bateragarria da.

Informazio gehiago [[Headset|aurikularren]] orrian.

===Zure gailuaren aldaera zein den jakiteko===
Zure gailua zer nolakoa den jakitea komeni zaizu, hau da, gailuaren aldaera (revision) zein den zehaztea komeni da.

# Gogoan jaso data kodea, jaso duzun kutxaren azpian eranskailu batean egongo da.
# irakurri [[Finding_hardware_revision|hardware aldaeraren bila]]

Bi hauek garrantzitsuak dira, zure gailuan, fabrikan, zein irudi flasheatu (ezarri) duten jakiten lagunduko baitizute. (c.f. [[Distributions|banaketak]] eta [[GTA02_revisions | Neo FreeRunner (aka GTA02) aldaerak]]).

==Softwarea instalatu==

Freerunnerrean dagoen software ia guztia aldatu edo eguneratu daiteke, bai eta gailua pizteko beharrezkoa den '''abiarazlea''' eta GSM txipean dagoen softwarea ere.

Izatez, Neo FreeRunnerra berezko [[Distributions| banaketa]] bat barnean ezarrita duela iritsiko zaizu, beraz, hemendik aurrerakorik egin beharrik ez duzu izango. Irakurri [[Om_2008 | OM 2008]] [[Manuals/Om_2008|eskuliburua]] zure telefonoa erabiltzen hasteko. Gerora, zure gailuan [[Distributions|banaketa]] berriagoa edota erabilera zabalagoa duena edota aukera bereziak eskaintzen dituena instalatu nahi zenezake, kasu horretan irakurri ondokoa.

===Abiarazlea instalatu===

Telefonoko sistema eragilea abiarazteko beharrezkoa da bootloader edo abiarazlea. '''Qi''' da gomendatutako abiarazlea Neo FreeRunner gailuan. Horrekin, abiatzeko prozesua azkarragoa baita. Hainbat sistema eragileren artean aukeratu ahal izateko, U-Boot abiarazlea mantendu beharko zenuke, hau abiarazle zaharragoa da. Abiarazlea http://downloads.openmoko.org/distro/testing/NeoFreerunner/ helbidetik har dezakezu eta [[NeoTool]] programaren bidez zure Linux PCan instala dezakezu. (ikusi http://wiki.openmoko.org/wiki/No_Linux ez badaukazu Linuxpean dabilen PCrik, baina hobe zenuke linux banaketa zirraragarriren bat instalatuko bazenio zeure PCari)

===GSM Firmwarea eguneratu===

Gaur egungo GSM Firmwareaaren bertsioak Moko 11 izena du. Zure bertsioa zaharragoa bada bertsio berritzea egin beharko zenuke, horrela telefono gailuaren hainbat funtzionalitate-arazo konponduko baitira.



FreeRunner gailua mikroSD txartelean instalatutako sistemaren bidez abiaraziz hasi behar da, abiaratze honek automatikoki eragingo ditu beharrezkoak diren aginduak eta GSM firmwarea txipera irauliko (flasheatuko?) du. mikroSDra abiarazteko irudia kopiatzea era berezian egin behar izaten da (linuxeko dd agindua erabili beharko duzu ziurrenik) eta mikroSD irudia kopiatzerakoan mikroSDan dagoen informazioa guztiz ezabatuko da. Irudia tentuz jarri mikroSD txartelean, eta era egokian formateatu abiarazteko sistema egokia daukala ziurtatuz.
Prozedura hau fidagarria da GTA02 gailuan MOKO11 ezartzeko (flasheatzeko). Huts egiteko aukerak oso urriak dira _zehazki_ jarraitzen badituzu argibideak. Hemen azaldutako bideari jarraituz ez diozu kalterik eragingo zure gailuari.

'''Arreta berezia jarri `dd` agindua eragiterakoan nora kopiatu behar duen esaterakoan, dispositibo *fisikoa* adierazi behar da, esaterako /dev/sdm, eta *ez* partizioa (alegia ez /dev/sdmp1). Horrez gain, mikroSDko partizio guztiak desmontatuta daudela ziur egon `dd` agindua abiarazterakoan'''<br>
Aurrekoaz ziur zaudenean, ''berriz begiratu ea aurreko abisuko baldintza guztiak betetzen dituzun'', gainera, bada ez bada, ondo begiratu ea mikroSD dispositiboa den `dd` aginduari adierazitakoa, izan ere, disko gogorra adieraziz gero disko gogorreko eduki guztia ezabatuko baitu, eta oso erraza da nahastea, alegia, mikroSDa /dev/sdc izan daiteke, baina /dev/sdb disko gogorra izan daiteke. Beraz, '''arreta handiz idatzi agindua'''.

<ol>
<li>Jaitsi eta <tt>untar</tt> (desenpaketatu) http://people.openmoko.org/joerg/calypso_moko_FW/moko11/flash-moko11_uSD-image.tar.gz zeure mahai gaineko PCra. Irakurri <tt>README.tx</tt> fitxategia, untar egiterakoan paketetik aterako da fitxategia.</li>

<li>Zure PCko irakurgailuan sartu mikroSD txartela, eta automatikoki muntatutako partizioak desmuntatu (mikroSDko partizioak, noski), zZein partizio muntatu diren jakiteko <tt>mount</tt> edo <tt>df -h</tt> aginduak erabil ditzakezu. Desmuntatzeko ez erabili "era seguruan atera txartela", <tt>umount</tt> agindua erabili desmuntatzeko.</li>

<li>mikroSD txartelera <tt>flash-moko11-2.image</tt> fitxategian dagoen irudia fisikoki idazteko <tt>dd</tt> agindua erabili. Kontuz agindu honekin: non idatzi behar duen esateko mikroSD txartelaren dispositibo fisikoa zein den esan behar zaio aginduari, ez partizioren bat, baizik eta dispositiboa bera. Gainera, dispositiboan dagoen eduki guztia ezabatuko du eragiketak, beraz, dispositibo okerra esan ezkero, kalte handia sor daiteke. <tt>dd</tt> aginduari disko gogorrari dagokion dispositibo fisikoan kopiatzeko agindua emango bagenio, partizio taula eta bertako eduki guztia ezabatuko du, beraz, sistema osoa berrinstaltu beharko genuke. Eragiketa hau egiteko orduan root erabiltzailearen baimenak eduki behar dira, alegia root bezala sartu behar da sisteman edo sudo agindu erabili beharko da:</li>

% sudo dd if=flash-moko11-2.image of=/dev/mmcblk0

<li>mikroSD txartela atera aurretik <tt>sync</tt> edo <tt>eject <device></tt> aginduak erabiltzea komeni da, izan ere txartelera informazioa guztiz pasa dela ziur egon behar baitugu.</li>

<li>Sartu mikroSD txartela zeure FreeRunner mugikorrera, eta abiarazi gailua '''[[Booting_the_Neo_FreeRunner#Log_into_U-Boot_in_the_NOR_Flash|NOR-U-Boot]]''' bideari jarraituz, eta aukeratu "Boot from microSD" aukera.</li>

<li>Firmwarea flash memoriara kopiatzeko prozesua abiatuko dela ikusiko duzu, eta bukaeran, 6 minutu inguru igaro ondoren, "d_o_n_e" kolore berdez idatzita azalduko da. Une horretan pizteko/itzaltzeko botoiak ezin du Freerunnerra itzali, botoia sakatzeak eten/itzuli funtzioak beteko ditu, baina ez itzaltzekoa. Gutxienez bi eratara itzal dezakezu Freerunnerra, alde batetik, <tt>ssh</tt> aginduaren bidez FreeRunnerrera konektatu usb kable bidez lotutako PC batetik (edo wifi konexio bidez) eta itzaltzeko agindua eragin dezakezu: <br>
# shutdown -h now<br>
Itzaltzeko beste era bat ere badago, askoz ere sinpleagoa da bigarren era hau (baina ez hain dotorea): bateria kendu eta itzali egingo da, a zer erremedio!.
Firmwarea ondo kopiatu dela ikusteko, ssh konexio bidez <tt>mickeyterm</tt> erabil daiteke modemarekin komunikatzeko eta bertsioa begiratzeko</li>
</ol>
====OHARRA====

Zure PCak mikroSD txartelak irakurtzeko gailurik ez badauka, mikroSD txartelera <tt>dd</tt> agindu bidez moko11 irudiaren kopia FreeRunner gailuan bertan egin dezakezu: instalatu <tt>task-base-smbfs</tt>, mikroSD txartela desmuntatu, horretarako <tt>umount /media/card</tt> agindua erabili (partizio gehiago baleuzka eta horiek ere muntatuta baleude guztiak desmuntatu). Une honetan bi aukera dauzkazu gutxienez:
<ol>
<li> Zure PCan dagoen irudia daukan direktorioa FreeRunnerreko fitxategi sisteman muntatu dezakezu, eta ondoren, <tt>dd</tt> agindu bidez zuzenean FreeRunnerrean dagoen mikroSD txartelera kopia dezakezu. Prozesu horrek 12 minutu inguru iraun ditzake. Eragiketa hau FreeRunnerreko shell batetik egin behar da.
</li>
<li>Alderantziz ere jardun daiteke, alegia, PCko shell batean lan egin dezakezu:
</li>
</ol>
mount the directory in which you have the <tt>flash-moko11-2.image</tt> file and do the <tt>dd</tt> stuff. This will take about 12 minutes.

You can speed this up by re-gziping just the image file and using the following command to decompress it directly to the flash card:

% gzip -d < flash-moko11-2.image.gz > /dev/mmcblk0

Using this gzip method, you can actually do the update with an in place image as long as it is shell enabled and has 92M free on the main file system (all but Android and Neovento right now). Just get the 92M gzip file to the phone, use the above line to extract it to the card after unmounting.

Or, maybe in a more simpler manner:
root@om-gta02 ~ $ umount /media/card
and then from desktop:
scp flash-moko11-2.image root@192.168.0.202:/dev/mmcblk0

====NOTE 2====

Whether you have [[Qi]] installed or not (see above) as your boot loader, you must power up to the NoR menu (Hold AUX Key, press Power button) and select "Boot from microSD (fat/ext2)" to begin the installation process (per DocScrutinizer in #openmoko). '''Do not''' let Qi boot the uSD. Although it still seems to flash OK, the green "d_o_n_e" does not show up, to give you the warm feeling that everything is OK.

You can confirm the firmware version number using the [[OpenmokoFramework/mickeyterm|mickeyterm]] (cmd: "AT+CGMR"). In SHR-Settings, Phone/Modem Information will supply the same number.

===Installing a distribution===

This section describes how to install a distribution on the internal flash memory of the Neo FreeRunner. If you want to install it on the memory card please refer to the guide provided by the distribution.

For installing a new distribution you will need two files, a root file system (rootfs) image and a kernel image. The root file system image usually ends with ".jffs2", and the kernel image ends with ".uimage.bin". You can get these files from http://wiki.openmoko.org/wiki/Download . Use the program NeoTool to install the distribution on your FreeRunner. The flashing process can take up to 15 minutes for a ~70MB image. It is also wise to make sure that your Neo has enough battery charge prior to flashing.

When flashing succeeds the following will be shown:

<pre>
status(0) = No error condition is present
Done!
</pre>

[[Category:Manuals]]